From owner-freebsd-firewire@FreeBSD.ORG Wed Aug 27 00:33:40 2008 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF31A106564A for ; Wed, 27 Aug 2008 00:33:40 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from parsely.rain.com (parsely.rain.com [199.26.172.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1D47A8FC0A for ; Wed, 27 Aug 2008 00:33:39 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by parsely.rain.com (8.11.4/8.11.4) with UUCP id m7R0X8O75434; Tue, 26 Aug 2008 17:33:08 -0700 (PDT) (envelope-from freebsd@sopwith.solgatos.com) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id AAA13884; Wed, 27 Aug 2008 00:31:46 GMT Message-Id: <200808270031.AAA13884@sopwith.solgatos.com> To: Sean Bruno In-reply-to: Your message of "Thu, 21 Aug 2008 19:12:16 PDT." <48AE2080.7050409@miralink.com> Date: Tue, 26 Aug 2008 17:31:46 +0100 From: Dieter Cc: freebsd-firewire@freebsd.org Subject: Re: Something broke :-( Re: fwcontrol update X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2008 00:33:41 -0000 > >> Can you run a live linux distro(unbuntu or knoppix) and see if linux can > >> "reset" > >> your NEC f/w controller? What does penguinix call firewire? (none):~ # dmesg | grep -i fire (none):~ # dmesg | grep -i fw (none):~ # dmesg | grep -i 1394 (none):~ # dmesg | grep -i link audit: initializing netlink socket (disabled) eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] (none):~ # man -k fire fire: nothing appropriate. (none):~ # man -k fw fw: nothing appropriate. (none):~ # man -k 1394 1394: nothing appropriate. (none):~ # man -k link link: nothing appropriate. Anyway, due to a firmware bug I ended up having to power cycle the machine. (switched off at the P/S, so even 5V standby should have been off) I was expecting the power cycle to completely reset the NEC board. But it is not back to normal. I no longer get the spewage from a constant series of bus resets, but fwcontrol -R still doesn't work. fwcontrol_prev is from March, and used to do -R successfully. fwcontrol_prev -R /dv0/test_prev_camera.dv Detected DV format on input. (EAGAIN) (EAGAIN) (EAGAIN) fwcontrol_prev -u 1 -p === base register === 0x00 0x85 0xe2 0x42 0xd7 0x03 0x00 0x00 Physical_ID:0 R:0 CPS:0 RHB:1 IBR:0 Gap_Count:5 Extended:7 Num_Ports:2 PHY_Speed:2 Delay:2 LCtrl:1 C:1 Jitter:2 Pwr_Class:7 WDIE:0 ISBR:0 CTOI:0 CPSI:0 STOI:0 PEI:0 EAA:1 EMC:1 Max_Legacy_SPD:0 BLINK:0 Bridge:0 Page_Select:0 Port_Select0 === page 0 port 0 === 0x08 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Astat:0 BStat:0 Ch:1 Con:0 RXOK:0 Dis:0 Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0 DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0 Connection_unreliable:0 Beta_mode:0 Port_error:0x0 Loop_disable:0 In_standby:0 Hard_disable:0 === page 0 port 1 === 0xf6 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Astat:3 BStat:3 Ch:0 Con:1 RXOK:1 Dis:0 Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0 DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0 Connection_unreliable:0 Beta_mode:0 Port_error:0x0 Loop_disable:0 In_standby:0 Hard_disable:0 === page 1 === 0x01 0x00 0x00 0x00 0x4c 0x02 0x00 0x00 Compliance:1 Vendor_ID:0x00004c Product_ID:0x020000 fwcontrol_prev -u 1 -t crc_len: 4 generation:6 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S400 0 1 -9W - P 1 0 01 1 5 S100 0 1 0W - C 0 0 Now what?