lacie BIGGEST FW800

[Hugh D. <hu...@zo...>]

Hi all.
I've just joined the list - in the main because I've acquired a Lacie 
"Biggest" FW800 - 1Tb of disk space - RAID 1+0 in hardware, with USB 2.0 
and FW800 interfaces.	
Aim is to hook it up to linux workgroup server (in preference to 
existing internal IDE_RAID setup in fact).

Have had varying success (ie. a lot of hair-loss...)

Slackware 10.1 install + custom kernels: versions - 2.4.29, 2.6.10 and 
2.6.12.3
Connected via Lacie FW800 PCI card - which lspci reports thusly (under 
all kernels):
	05:04.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8025 
(rev 01)

It *was* being detected only on warm (re)boots, now not at all.. (it's 
detected and mounted perfectly as a USB2.0 drive btw..)  Yesterday, when 
it was mounted fine, seemingly (under 2.6.10), I put approx 120 Gb of 
data across onto it ok.  Post cold-boot this morning (to put some more 
RAM in) no dice, and no joy with 'reboot' or ctrl-alt-del any more...

Under kernel 2.6.12.3: from a "clean" post-boot situation (modprobe -r 
ohci1394; modprobe -r ieee1394)
modprobe ohci139 produces:
> ieee1394: Initialized config rom entry `ip1394'
> ohci1394: $Rev: 1250 $ Ben Collins <bco...@de...>
> ACPI: PCI Interrupt 0000:05:04.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
> ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10]  MMIO=[f0904000-f09047ff]  Max Packet=[4096]
> ieee1394: Host added: ID:BUS[0-00:1023]  GUID[55aa55aa55aa55aa]
> ieee1394: Error parsing configrom for node 0-01: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

modprobe sbp2 just adds
 > sbp2: $Rev: 1219 $ Ben Collins <bco...@de...>
to the end of dmesg.

Can anyone suggest a line of attack?

H