Re: Compaq DL360 Debian kernel 2.4.27-1-386 cannot mount firewire

Stefan wrote:

>Is there at least the full information about the host adapter?

No

<snip>

>If not --- and since you did not quote anything from there I take it
>there is indeed not even the host info ---, then the host was either
not
>fully initialized, or the connection of the disk lead to a state where
>the bus is stuck in an initialization phase, e.g. because of an
electric
>problem.

>I believe now the host adapter was not fully initialized. There should
>have been a line like this shortly after the dmesg lines from ohci1394
>otherwise:
>ieee1394: Host added: ID:BUS[0-00:1023] GUID[00d0f5200800613d]
>(This line would also be missing if ieee1394 was loaded with
>disable_nodemgr=1, but then there would have been another log line
>which was not present in your dmesg.)

>When the log which you quoted was created, was the drive already
>connected? If yes, try also loading the drivers (unload + load the
>various 1394 drivers manually, or reboot) without anything attached to
>the FireWire port and watch whether that line appears and something
>shows up in /proc/bus/ieee1394/devices.

It does show something now.

===reboot whithout anything attached to the firewire port.

# modprobe -r sbp2; modprobe -r sd_mod; modprobe -r ohci1394;

# modprobe ohci1394; modprobe sd_mod; modprobe sbp2;

# dmesg
    .
    .
    .
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
ohci1394_0: Get PHY Reg timeout [0x00000000/0x00000000/100]
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[48] MMIO=[fdff0000-fdff07ff] Max
Packet=[2048]
sbp2: $Rev: 1074 $ Ben Collins <bcollins@debian.org>
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
ohci1394_0: Get PHY Reg timeout [0x04c00000/0x00000000/100]
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[48] MMIO=[fdff0000-fdff07ff] Max
Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010b5000009c83a]

# more /proc/bus/ieee1394/devices
  Node[0-00:1023] GUID[0010b5000009c83a]:
  Vendor ID: `Linux OHCI-1394' [0x000000]
  Capabilities: 0x0083c0
  Bus Options:
    IRMC(1) CMC(1) ISC(1) BMC(0) PMC(0) GEN(0)
    LSPD(2) MAX_REC(2048) CYC_CLK_ACC(0)
  Host Node Status:
    Host Driver : ohci1394
    Nodes connected : 1
    Nodes active : 1
    SelfIDs received: 1
    Irm ID : [0-00:1023]
    BusMgr ID : [0-63:1023]
    In Bus Reset : no
    Root : yes
    Cycle Master : yes
    IRM : yes
    Bus Manager : no

===after I attach the device to the port then:

ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
ohci1394_0: Get PHY Reg timeout [0x00000000/0x00000000/100]
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[48] MMIO=[fdff0000-fdff07ff] Max
Packet=[2048]
sbp2: $Rev: 1074 $ Ben Collins <bcollins@debian.org>
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
ohci1394_0: Get PHY Reg timeout [0x04c00000/0x00000000/100]
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[48] MMIO=[fdff0000-fdff07ff] Max
Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010b5000009c83a]
sbp2: $Rev: 1074 $ Ben Collins <bcollins@debian.org>
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
ohci1394_0: SelfID received, but NodeID invalid (probably new bus reset
occurred): 0800FFC0

It seems clear that when the disk is connected Linux does not get nearly
as far recognizing the Firewire hardware. I wonder if USB2 works any
better.

        Still stuck.

        -Jim

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op%cck
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Fri Feb 25 13:52:00 2005