From owner-freebsd-firewire@FreeBSD.ORG Wed Apr 14 04:35:48 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9A9D16A4CE for ; Wed, 14 Apr 2004 04:35:48 -0700 (PDT) Received: from smtp8.wanadoo.nl (smtp8.wanadoo.nl [194.134.35.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EC5D43D5E for ; Wed, 14 Apr 2004 04:35:48 -0700 (PDT) (envelope-from znerd@FreeBSD.org) Received: from [10.0.0.150] (db-c-1b11d.adsl.wanadoo.nl [81.69.207.29]) by smtp8.wanadoo.nl (Postfix) with ESMTP id 5002F58C6F for ; Wed, 14 Apr 2004 13:35:51 +0200 (CEST) From: Ernst de Haan To: freebsd-firewire@freebsd.org Date: Wed, 14 Apr 2004 13:35:51 +0200 User-Agent: KMail/1.6.1 X-Address: Muiderstraat 1, Amsterdam, Netherlands MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404141335.51111.znerd@FreeBSD.org> Subject: Problem connecting Sharp VL-PD3A Digital Video Camera X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 11:35:48 -0000 I'd like to rip Mini-DV tapes from my digital video camera, but I've never done anything like this before. I've got a Firewire card and it's correctly recognized, but when I connect the camera I get the following: fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) firewire0: split transaction timeout dst=0xffc0 tl=0x1 state=2 node0: resp=60 addr=0x400 fw_xfer_free FWXF_START probe failed for 1 node fw_rcv: unknown response tcode=6 src=0xffc0 tl=0x1 rt=1 data=0x6e3d0f04 try ad-hoc work around!! no use... Any ideas? Can I increase the log level somehow? I'm running FreeBSD 5.2.1 on a Pentium 4-2.8 GHz (HT), ACPI disabled, 875P mainboard, 1 GB memory, 800 MHz FSB, USB on mainboard and on an extra PCI card. Here's the dmesg output, my kernel config file and my rc.conf file and the output of pciconf -vl, respectively: http://people.freebsd.org/~znerd/dmesg.20040414.txt http://people.freebsd.org/~znerd/WHISPERER http://people.freebsd.org/~znerd/rc.conf http://people.freebsd.org/~znerd/pciconf.out Any hints are more than welcome... Ernst From owner-freebsd-firewire@FreeBSD.ORG Fri Apr 16 07:40:32 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE84A16A4CE for ; Fri, 16 Apr 2004 07:40:32 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0ECEE43D3F for ; Fri, 16 Apr 2004 07:40:32 -0700 (PDT) (envelope-from freebsd-firewire@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BEUW6-0007Rm-00 for ; Fri, 16 Apr 2004 16:40:30 +0200 Received: from makrothumia.wingnet.net ([206.30.215.5]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Apr 2004 16:40:30 +0200 Received: from jesse by makrothumia.wingnet.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Apr 2004 16:40:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-firewire@freebsd.org From: Jesse Guardiani Date: Fri, 16 Apr 2004 10:40:24 -0400 Organization: WingNET Lines: 52 Message-ID: References: <87u10itsoo.wl@tora.nunu.org> <87r7vj2c0x.wl@tora.nunu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: makrothumia.wingnet.net User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: freebsd 5.2.1-RELEASE, 4 pin laptop firewire ports, and 6 pin firewire hard disk drives X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 14:40:33 -0000 Well, I bought a VIA VT6303 6 pin bus-power-providing controller card for a FreeBSD 4.9-STABLE machine I use here at the office. I tried the same FW hdd on this card and I'm getting the same results: Nothing happens. My firewire device and sbp devices are compiled into the kernel and detected: Apr 16 10:17:10 billmax /kernel: fwohci0: port 0x8000-0x807f mem 0xe4101000-0xe41017ff irq 15 at device 10.0 on pci0 Apr 16 10:17:10 billmax /kernel: fwohci0: OHCI version 1.0 (ROM=1) Apr 16 10:17:10 billmax /kernel: fwohci0: No. of Isochronous channel is 8. Apr 16 10:17:10 billmax /kernel: fwohci0: EUI64 ff:ff:ff:ff:ff:ff:03:4d Apr 16 10:17:10 billmax /kernel: fwohci0: Phy 1394a available S400, 3 ports. Apr 16 10:17:10 billmax /kernel: fwohci0: Link S400, max_rec 2048 bytes. Apr 16 10:17:10 billmax /kernel: firewire0: on fwohci0 Apr 16 10:17:10 billmax /kernel: sbp0: on firewire0 Apr 16 10:17:10 billmax /kernel: fwohci0: Initiate bus reset Apr 16 10:17:10 billmax /kernel: fwohci0: BUS reset Apr 16 10:17:10 billmax /kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode Apr 16 10:17:10 billmax /kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Apr 16 10:17:10 billmax /kernel: firewire0: bus manager 0 (me) But the *ONLY* output I've been able to get when connecting the drive is this: Apr 16 10:19:06 billmax /kernel: WARNING: driver fw should register devices with make_dev() (dev_t = "#fw/0") And I can't make it repeat that output either. I've tried multiple `fwcontrol -r` commands, both before and after connecting the drive. Here's fwcontrol -t: % fwcontrol -t crc_len: 3 generation:1 node_count:1 sid_count:1 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 1 15W - - - 1 0 And fwcontrol -t never seems to change if I connect a drive. I'm going to try this same card and drive on a 5.2.1 machine, but I'm starting to think that something is wrong with FreeBSD's firewire implementation. The drive always works fine on my boss's Powerbook. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net From owner-freebsd-firewire@FreeBSD.ORG Sat Apr 17 11:48:37 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2873716A4CE for ; Sat, 17 Apr 2004 11:48:37 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 868DF43D48 for ; Sat, 17 Apr 2004 11:48:36 -0700 (PDT) (envelope-from freebsd-firewire@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BEurj-0003RW-00 for ; Sat, 17 Apr 2004 20:48:35 +0200 Received: from ppp-62-233.customer.wingnet.net ([206.30.62.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Apr 2004 20:48:35 +0200 Received: from jesse by ppp-62-233.customer.wingnet.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 Apr 2004 20:48:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-firewire@freebsd.org From: Jesse Guardiani Date: Sat, 17 Apr 2004 14:48:30 -0400 Organization: WingNET Lines: 33 Message-ID: References: <87u10itsoo.wl@tora.nunu.org> <87r7vj2c0x.wl@tora.nunu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ppp-62-233.customer.wingnet.net User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: freebsd 5.2.1-RELEASE, 4 pin laptop firewire ports, and 6 pin firewire hard disk drives X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Apr 2004 18:48:37 -0000 Jesse Guardiani wrote: > Well, I bought a VIA VT6303 6 pin bus-power-providing > controller card for a FreeBSD 4.9-STABLE machine I > use here at the office. > > I tried the same FW hdd on this card and I'm getting > the same results: Nothing happens. My firewire device > and sbp devices are compiled into the kernel and detected: [...] > I'm going to try this same card and drive on a 5.2.1 machine, > but I'm starting to think that something is wrong with FreeBSD's > firewire implementation. The drive always works fine on my boss's > Powerbook. The same firewire card/drive combo works in my 5.2.1-RC2 machine. I guess FreeBSD 4.x just doesn't have up-to-date firewire drivers or something. Oh well. 5-STABLE should be here soon, right? So it's good that it works in 5.x. I'd really like to figure out WHY it doesn't work with a 4 pin firewire controller though... The machine with the 4 pin controller is a 5.2.1-RELEASE laptop... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net From owner-freebsd-firewire@FreeBSD.ORG Sat Apr 17 23:39:20 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE07916A4CE; Sat, 17 Apr 2004 23:39:20 -0700 (PDT) Received: from tora.nunu.org (YahooBB219003182070.bbtec.net [219.3.182.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7404C43D1F; Sat, 17 Apr 2004 23:39:19 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id BC9B24CC26; Sun, 18 Apr 2004 15:39:17 +0900 (JST) Date: Sun, 18 Apr 2004 15:39:17 +0900 Message-ID: <8765bxzt62.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Ernst de Haan In-Reply-To: <200404141335.51111.znerd@FreeBSD.org> References: <200404141335.51111.znerd@FreeBSD.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: Problem connecting Sharp VL-PD3A Digital Video Camera X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2004 06:39:21 -0000 At Wed, 14 Apr 2004 13:35:51 +0200, Ernst de Haan wrote: > > I'd like to rip Mini-DV tapes from my digital video camera, but I've never > done anything like this before. I've got a Firewire card and it's correctly > recognized, but when I connect the camera I get the following: > > fwohci0: BUS reset > fwohci0: node_id=0xc000ffc1, gen=2, CYCLEMASTER mode > firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) > firewire0: bus manager 1 (me) > firewire0: split transaction timeout dst=0xffc0 tl=0x1 state=2 > node0: resp=60 addr=0x400 > fw_xfer_free FWXF_START > probe failed for 1 node > fw_rcv: unknown response tcode=6 src=0xffc0 tl=0x1 rt=1 data=0x6e3d0f04 > try ad-hoc work around!! > no use... > > Any ideas? Can I increase the log level somehow? The response from your camera is received too late. Initiate bus reset by 'fwcontorl -r' manually, and see what happens. Have you already tried 'fwcontrol -R' to receive the iso stream? I think you can receive iso stream even when the bus probe failed. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-firewire@FreeBSD.ORG Sat Apr 17 23:44:11 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C946D16A4CE for ; Sat, 17 Apr 2004 23:44:11 -0700 (PDT) Received: from tora.nunu.org (YahooBB219003182070.bbtec.net [219.3.182.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F6E543D39 for ; Sat, 17 Apr 2004 23:44:11 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id A0D034CC26; Sun, 18 Apr 2004 15:44:10 +0900 (JST) Date: Sun, 18 Apr 2004 15:44:10 +0900 Message-ID: <874qrhzsxx.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: jesse@wingnet.net In-Reply-To: References: <87u10itsoo.wl@tora.nunu.org> <87r7vj2c0x.wl@tora.nunu.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: freebsd 5.2.1-RELEASE, 4 pin laptop firewire ports, and 6 pin firewire hard disk drives X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2004 06:44:11 -0000 At Fri, 16 Apr 2004 10:40:24 -0400, Jesse Guardiani wrote: > Apr 16 10:17:10 billmax /kernel: fwohci0: port 0x8000-0x807f mem 0xe4101000-0xe41017ff irq 15 at device 10.0 on pci0 > Apr 16 10:17:10 billmax /kernel: fwohci0: OHCI version 1.0 (ROM=1) > Apr 16 10:17:10 billmax /kernel: fwohci0: No. of Isochronous channel is 8. > Apr 16 10:17:10 billmax /kernel: fwohci0: EUI64 ff:ff:ff:ff:ff:ff:03:4d EUI64 seems invalid. Do you get the same id on FreeBSD-5 and PowerBook? > I'm going to try this same card and drive on a 5.2.1 machine, > but I'm starting to think that something is wrong with FreeBSD's > firewire implementation. The drive always works fine on my boss's > Powerbook. It's not necessary because of firewire implementation. If the parent bus such as PCI/Cardbus is not initialized correctly, the firewire can not work correctly. The firewire codes in -stable and -current are very close. PCI and related codes are very different. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html