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