Can't see master and slave IDE drives w/ Oxford 911 bridge
Brought to you by:
aeb,
bencollins
Menu
▾
▴
#655 Can't see master and slave IDE drives w/ Oxford 911 bridge
I have a multi-bay firewire enclosure containing 4
oxford 911 firewire-to-ide bridges (the enclosure is
capable of supporting a total of 8 IDE drives). I'm
running a single firewire cable from a port on the
firewire pci card to the firewire-to-ide bridge. I'm
running SUSE 9.1 and have upgraded to the 2.6.8.1
kernel. I'm having trouble with Linux being able to
detect both IDE drives (master and slave) connected to
the firewire bridge in the enclosure. I am seeing the
following behavior:
- when I have one drive plugged in as a master, it is
detected just fine,
- when I have one drive plugged in as a slave, it is
detected just fine
- when I plug in both master and slave drives, only the
slave is detected
When I boot up my old configuration (Redhat 9.0 with
2.4.27 kernel), the drives are recognized just fine
(after running rescan-scsi-bus.sh). As I understand
the 2.6. kernel, I do not need to run
rescan-scsi-bus.sh as the
scsi devices are set up automatically.
# kernel version
tried both 2.6.8.1, 2.6.5
# ieee 1394 version
# libraw version
Not sure, but it is the version that comes with the
above kernel versions
# which driver: TI PCILynx or OHCI
OHCI
# relevant messages from dmesg
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 10 (level,
low) -> IRQ 10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10]
MMIO=[d9001000-d90017ff] Max Packet=[2048]
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 11 (level,
low) -> IRQ 11
ohci1394: fw-host1: OHCI-1394 1.0 (PCI): IRQ=[11]
MMIO=[d9002000-d90027ff] Max Packet=[2048]
ieee1394: Node added: ID:BUS[0-00:1023]
GUID[0030e002ee101bbc]
ieee1394: Host added: ID:BUS[0-01:1023]
GUID[0011060000004618]
ieee1394: Error parsing configrom for node 0-02:1023
ieee1394: The root node is not cycle master capable;
selecting a new root node and resetting...
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-02:1023
ieee1394: Error parsing configrom for node 1-00:1023
ieee1394: Host added: ID:BUS[1-01:1023]
GUID[0011060000003bb6]
ieee1394: Error parsing configrom for node 1-02:1023
ieee1394: The root node is not cycle master capable;
selecting a new root node and resetting...
ieee1394: Error parsing configrom for node 1-00:1023
ieee1394: Error parsing configrom for node 1-01:1023
ieee1394: Node changed: 1-01:1023 -> 1-02:1023
eth0: no IPv6 routers present
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-01:1023: Max speed [S400] - Max
payload [2048]
Vendor: Maxtor 6 Model: Y200P0 Rev:
Type: Direct-Access ANSI SCSI
revision: 06
SCSI device sda: 398297088 512-byte hdwr sectors
(203928 MB)
sda: asking for cache data failed
sda: assuming drive cache: write through
sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0,
lun 0, type 0
h
# output of /sys/bus/ieee1394/devices (if available)
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0011060000003bb6 ->
../../../devices/pci0000:00/0000:00:0d.0/fw-host1/0011060000003bb6
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0011060000003bb6-0 ->
../../../devices/pci0000:00/0000:00:0d.0/fw-host1/0011060000003bb6/0011060000003bb6-0
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0011060000004618 ->
../../../devices/pci0000:00/0000:00:0c.0/fw-host0/0011060000004618
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0011060000004618-0 ->
../../../devices/pci0000:00/0000:00:0c.0/fw-host0/0011060000004618/0011060000004618-0
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0030e002ee101bbc ->
../../../devices/pci0000:00/0000:00:0c.0/fw-host0/0030e002ee101bbc
lrwxrwxrwx 1 root root 0 2004-09-17 21:34
0030e002ee101bbc-0 ->
../../../devices/pci0000:00/0000:00:0c.0/fw-host0/0030e002ee101bbc/0030e002ee101bbc-0
lrwxrwxrwx 1 root root 0 2004-09-17 21:33 fw-host0 ->
../../../devices/pci0000:00/0000:00:0c.0/fw-host0
lrwxrwxrwx 1 root root 0 2004-09-17 21:34 fw-host1 ->
../../../devices/pci0000:00/0000:00:0d.0/fw-host1
# adapter card model and/or OHCI chipset
Inland 1394 Firewire PCI, 3 port
# output of lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc.
VT8363/8365 [KT133/KM133] (rev 03)
0000:00:01.0 PCI bridge: VIA Technologies, Inc.
VT8363/8365 [KT133/KM133 AGP]
0000:00:07.0 ISA bridge: VIA Technologies, Inc.
VT82C686 [Apollo Super South] (rev 40)
0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus
Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. USB
(rev 1a)
0000:00:07.3 USB Controller: VIA Technologies, Inc. USB
(rev 1a)
0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686
[Apollo Super ACPI] (rev 40)
0000:00:07.5 Multimedia audio controller: VIA
Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
0000:00:09.0 Ethernet controller: Realtek Semiconductor
Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:0a.0 VGA compatible controller: 3Dfx
Interactive, Inc. Voodoo 3 (rev 01)
0000:00:0c.0 FireWire (IEEE 1394): VIA Technologies,
Inc. IEEE 1394 Host Controller (rev 46)
0000:00:0d.0 FireWire (IEEE 1394): VIA Technologies,
Inc. IEEE 1394 Host Controller (rev 46)
# version of application or utility (if applicable)
N/A
Logged In: NO
This is a know problem due to that a rewrite in configrom
parser that was implemented in kernel 2.6.3 and later that
causes only the first drive that it sees in the configrom to
be enabled, check the devel-mailinglist and you will find
what happens and for a possible workaround.