On Sun, 2005-01-02 at 05:59, Alexandre Oliva wrote: > On Dec 30, 2004, Les Mikesell <les@xxxxxxxxxxxxxxxx> wrote: > > > Is firewire support still broken in the current FC3 kernel > > Works fine for me. FC2 took some patching, but FC3 has it out of the > box. There are some notes about Firewire on FC2 in my home page, URL > below. Thanks, I though it was supposed to work. Maybe it is the drive adapter chipset, although it works on FC1 and the same drive works with a USB connection. Here's what I see in dmesg: ohci1394: $Rev: 1223 $ Ben Collins <bcollins@xxxxxxxxxx> ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[169] MMIO=[fe004000-fe0047ff] Max Packet=[2048] ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting... ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050770e00071002] ieee1394: Host added: ID:BUS[0-01:1023] GUID[00309500a0023749] ieee1394: unsolicited response packet received - no tlabel match sbp2: $Rev: 1219 $ Ben Collins <bcollins@xxxxxxxxxx> scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices ieee1394: sbp2: Logged into SBP-2 device ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Vendor: HDS72251 Model: 6VLAT80 Rev: Type: Direct-Access ANSI SCSI revision: 06 SCSI device sdc: 321672960 512-byte hdwr sectors (164697 MB) sdc: asking for cache data failed sdc: assuming drive cache: write through sdc:<6>EXT3 FS on dm-0, internal journal ieee1394: sbp2: aborting sbp2 command Read (10) 00 00 00 00 00 00 00 08 00 ieee1394: sbp2: aborting sbp2 command Test Unit Ready 00 00 00 00 00 ieee1394: sbp2: aborting sbp2 command Read (10) 00 13 2c 56 80 00 00 08 00 ieee1394: sbp2: aborting sbp2 command --- Les Mikesell les@xxxxxxxxxxxxxxxx
