Thread: lacie BIGGEST FW800
Brought to you by:
aeb,
bencollins
Menu
▾
▴
linux1394-user
|
From: Hugh D. <hu...@zo...> - 2005-07-20 12:32:46
|
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 |
|
From: Andreas K. <And...@me...> - 2005-07-20 13:02:33
|
On Wednesday 20 July 2005 14:32, Hugh Dixon wrote: > modprobe sbp2 just adds > > > sbp2: $Rev: 1219 $ Ben Collins <bco...@de...> > > to the end of dmesg. sbp2: $Rev: 1288 $ Ben Collins <bco...@de...> You could try using the very latest SVN drivers (from www.linux1394.org). Maybe it helps. It's worth a try in any case. Andreas |
|
From: Hugh D. <hu...@zo...> - 2005-07-20 13:29:02
|
Hi list+Andreas I get the following errors when attempting to do make modules after having downloaded "trunk" ver.1315 tarball and put it into the 2.6.12.3 source tree in place of drivers/ieee1394/ > drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread': > drivers/ieee1394/ieee1394_core.c:1035: error: too few arguments to function `try_to_freeze' > drivers/ieee1394/ieee1394_core.c: In function `ieee1394_init': > drivers/ieee1394/ieee1394_core.c:1113: warning: implicit declaration of function `class_create' > drivers/ieee1394/ieee1394_core.c:1113: warning: assignment makes pointer from integer without a cast > drivers/ieee1394/ieee1394_core.c:1151: warning: implicit declaration of function `class_destroy' > make[2]: *** [drivers/ieee1394/ieee1394_core.o] Error 1 > make[1]: *** [drivers/ieee1394] Error 2 > make: *** [drivers] Error 2 is it me or can others replicate? - I'm not at all familiar with SVN so I may have gone about it rather wrong-end-up... H Also - the TI chip on the FW card has TSB82AA2 on it which I've seen other people's lspci output report "correctly" - significant that it doesn't on my setup? Andreas Klauer wrote: > On Wednesday 20 July 2005 14:32, Hugh Dixon wrote: > >>modprobe sbp2 just adds >> >> > sbp2: $Rev: 1219 $ Ben Collins <bco...@de...> >> >>to the end of dmesg. > > > sbp2: $Rev: 1288 $ Ben Collins <bco...@de...> > > You could try using the very latest SVN drivers (from www.linux1394.org). > Maybe it helps. It's worth a try in any case. > > Andreas > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user > > |
|
From: t35t0r <t3...@gm...> - 2005-07-20 13:58:48
|
Hrmm this is strange. I have the exact same drive with the exact same
FW800 card. Is your FW800 card in a 64bit pci-x slot or a regular
32bit slot? Do you have any FW400 ports you can try it with? Have you
upgraded the firmware on the drive to the latest version? Try using
the latest vanilla kernel with these options all built into the
kernel:
<*> IEEE 1394 (FireWire) support
Subsystem Options
[*] Build in extra config rom entries for certain functionality
<*> OHCI-1394 support
--- Protocol Drivers
<*> SBP-2 support (Harddisks etc.)
[*] Enable Phys DMA support for SBP2 (Debug)
<*> Raw IEEE1394 I/O support
Also you might want to use the CFQ disk scheduler even with USB2.
On 7/20/05, Hugh Dixon <hu...@zo...> wrote:
> Hi list+Andreas
> I get the following errors when attempting to do make modules after
> having downloaded "trunk" ver.1315 tarball and put it into the 2.6.12.3
> source tree in place of drivers/ieee1394/
|
|
From: Hugh D. <hu...@zo...> - 2005-07-20 14:18:03
|
Hi t35t0r+list: Regular slot AFAIK - it's Lacie part # 107755, btw. I'll try the non-modular approach next I think. Don't have any FW400 ports to try it on - though wouldnt' be hard to get hold of a card, just not instantly perhaps. Haven't flashed firmware up - it reports 1.32 at present - what version yours? H t35t0r wrote: > Hrmm this is strange. I have the exact same drive with the exact same > FW800 card. Is your FW800 card in a 64bit pci-x slot or a regular > 32bit slot? Do you have any FW400 ports you can try it with? Have you > upgraded the firmware on the drive to the latest version? Try using > the latest vanilla kernel with these options all built into the > kernel: > > <*> IEEE 1394 (FireWire) support > Subsystem Options > [*] Build in extra config rom entries for certain functionality > <*> OHCI-1394 support > --- Protocol Drivers > <*> SBP-2 support (Harddisks etc.) > [*] Enable Phys DMA support for SBP2 (Debug) > <*> Raw IEEE1394 I/O support > > Also you might want to use the CFQ disk scheduler even with USB2. > > On 7/20/05, Hugh Dixon <hu...@zo...> wrote: |
|
From: t35t0r <t3...@gm...> - 2005-07-20 16:14:48
|
I think the FW800 card in a regular PCI slot will only function at FW400. This (should not but) may be confusing the card or your machine. I think that LaCie FW800 card has a power input on the card, is this connected on to your PSU? If you continue to have these problems you might try a non-LaCie FW400 32 bit card, they're pretty cheap nowadays. I'm not sure about the firmware version, how can you get this information while in linux? I did use the latest firmware which was released June 22, 2005 http://www.lacie.com/support/drivers/ before formatting the drive EXT3. Look for device updater for windows (unfortunately, but I think they have one for macosx too). I wouldn't want to try it using wine, who knows what sort of low level win32asm the flash updater uses. On 7/20/05, Hugh Dixon <hu...@zo...> wrote: > Hi t35t0r+list: >=20 > Regular slot AFAIK - it's Lacie part # 107755, btw. > I'll try the non-modular approach next I think. Don't have any FW400 > ports to try it on - though wouldnt' be hard to get hold of a card, just > not instantly perhaps. Haven't flashed firmware up - it reports 1.32 at > present - what version yours? >=20 > H |
|
From: t35t0r <t3...@gm...> - 2005-07-20 16:55:33
|
Oh now I see we are not talking about the same drive, I have the d2 1tb and I think you have the RAID hotswappable correct? Mine definately does not have the blue LCD status indicator on the front: http://www.lacie.com/products/product.htm?pid=3D10600 <- this is the one you are talking about right? In any case I purchased this part from cdwg: http://www.cdwg.com/shop/products/default.aspx?EDC=3D501261 which does show Mfg. Part: =09107755. lspci -vvv for the card shows: 0000:00:09.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) (prog-if 10 [OHCI]) Subsystem: Unknown device 55aa:55aa Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (1250ns min, 1250ns max), cache line size 10 Interrupt: pin A routed to IRQ 21 Region 0: Memory at e8008000 (32-bit, non-prefetchable) Region 1: Memory at e8000000 (32-bit, non-prefetchable) [size=3D16K= ] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME+ Is yours the same revision? But since you have it stuck into a 32 bit slot, some of the pins are not connected into the mobo correct? Also what is the model of your motherboard? On 7/20/05, Hugh Dixon <hu...@zo...> wrote: > interesting.. - can you confirm that it's teh same lacie part# as yours? > - it makes no mention of PCI slot type anywhere in the blurb ,and when I > did get it to connect up (yesterday...) it was definitely reporting S800 > or whatever it is that implies firewire 800 working. It's a "mac or pc" > card so I dunno what PCI slots that would imply. > It does have a power input and I have it hooked up. >=20 > The firmware I got from the blue screen thingy on the drive - if you hit > "menu" it cycles through a load of diagnostic stuff. > May try updating the firmware from laptop via USB >=20 > H |
|
From: Hugh D. <hu...@zo...> - 2005-07-20 22:09:21
|
Aye - right on both fronts. Odd that your card reports its chipset under lspci.. lscpi -vvv on this box comes back with > 05:04.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8025 (rev 01) (prog-if 10 [OHCI]) > Subsystem: Unknown device 55aa:55aa > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Indeed it doesn't have all the blade connections in-slot.. The machine it's in is an HP dc7100 - intel motherboard of some sort. It makes no mention at all of needing a 64bit slot .. We shall see - I'll have to get my head around Stefan's (excellent) instructions for tweaking the module source code and see if that works. (and look into getting a mobo with a 64 bit slot anyway). H t35t0r wrote: > Oh now I see we are not talking about the same drive, I have the d2 > 1tb and I think you have the RAID hotswappable correct? Mine > definately does not have the blue LCD status indicator on the front: > http://www.lacie.com/products/product.htm?pid=10600 <- this is the one > you are talking about right? > > In any case I purchased this part from cdwg: > http://www.cdwg.com/shop/products/default.aspx?EDC=501261 which does > show Mfg. Part: 107755. > > lspci -vvv for the card shows: > > 0000:00:09.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 |
|
From: Francois R. <ro...@fr...> - 2005-07-20 22:56:36
|
Hugh Dixon <hu...@zo...> : [...] > Indeed it doesn't have all the blade connections in-slot.. The machine > it's in is an HP dc7100 - intel motherboard of some sort. It makes no > mention at all of needing a 64bit slot .. We shall see - I'll have to It does not _need_ a 64 bit slot. Pins allow to detect the width (32/64) of the slot. Then they allow the master and the slave to negotiate the width of the transfer during a PCI transaction. Moreover, assuming I read correctly the spec, the asic should/can not DMA to memory beyond 4Go (no DAC nor register for such addressing). > get my head around Stefan's (excellent) instructions for tweaking the > module source code and see if that works. (and look into getting a mobo > with a 64 bit slot anyway). FWIW you do not necessarily need an high-end system since the asic is not 66MHz capable. You can always buy a mobo with several PCI busses though :o) -- Ueimor |
|
From: Stefan R. <st...@s5...> - 2005-07-20 23:33:50
|
Hugh Dixon wrote:
> Odd that your card reports its chipset under lspci..
> lscpi -vvv on this box comes back with
>
>> 05:04.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8025
>> (rev 01) (prog-if 10 [OHCI])
8025 is OK. Maybe you compiled the kernel without "PCI device name database"
or the entry for the TSB82AA2 is missing from pci.ids for some reason. Older
kernels don't have it.
$ grep TSB82AA2 linux/drivers/pci/pci.ids
8025 TSB82AA2 IEEE-1394b Link Layer Controller
--
Stefan Richter
-=====-=-=-= -=== =-=-=
http://arcgraph.de/sr/
|
|
From: Hugh D. <hu...@zo...> - 2005-07-21 10:17:30
|
OK.. Lots of output (and no success, seemingly) (this is all with the disk plugged in and on, btw) modprobe -r *all-related-to-iee1394 I think* [I'm assuming ohci_hcd is not relevant here?], dmesg = ieee1394: NodeMgr: Exiting thread ieee1394: Node removed: ID:BUS[0-01:1023] GUID[55aa55aa55aa55aa] ohci1394: fw-host0: Soft reset finished ohci1394: fw-host0: Freeing dma_rcv_ctx 0 ohci1394: fw-host0: Freeing dma_rcv_ctx 0 ohci1394: fw-host0: Freeing dma_trm_ctx 0 ohci1394: fw-host0: Freeing dma_trm_ctx 1 ohci1394: fw-host0: Freeing dma_rcv_ctx 0 then: modprobe ieee1394 configrom_num_retries=10 configrom_read_interval=1000 nodescan_wait_interval=16 dmesg = ieee1394: Initialized config rom entry `ip1394' then: modprobe ohci1394 dmesg = ohci1394: $Rev: 1299 $ Ben Collins <bco...@de...> PCI: Found IRQ 10 for device 0000:05:04.0 PCI: Sharing IRQ 10 with 0000:00:02.0 ohci1394: fw-host0: Remapped memory spaces reg 0xf8a9e000 ohci1394: fw-host0: Soft reset finished ohci1394: fw-host0: Iso contexts reg: 000000a8 implemented: 0000000f ohci1394: fw-host0: 4 iso receive contexts available ohci1394: fw-host0: Iso contexts reg: 00000098 implemented: 000000ff ohci1394: fw-host0: 8 iso transmit contexts available ohci1394: fw-host0: Receive DMA ctx=0 initialized ohci1394: fw-host0: Receive DMA ctx=0 initialized ohci1394: fw-host0: Transmit DMA ctx=0 initialized ohci1394: fw-host0: Transmit DMA ctx=1 initialized ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[f0504000-f05047ff] Max Packet=[4096] ohci1394: fw-host0: ATRetries = 00000822 ieee1394: CSR: setting expire to 98, HZ=1000 ohci1394: fw-host0: IntEvent: 00030010 ohci1394: fw-host0: irq_handler: Bus reset requested ohci1394: fw-host0: Cancel request received ohci1394: fw-host0: Got RQPkt interrupt status=0x00008409 ohci1394: fw-host0: SelfID interrupt received (phyid 0, not root) ohci1394: fw-host0: SelfID packet 0x807fcc5a received ieee1394: Including SelfID 0x5acc7f80 ohci1394: fw-host0: SelfID for this node is 0x807fcc5a ohci1394: fw-host0: SelfID packet 0x817fc474 received ieee1394: Including SelfID 0x74c47f81 ohci1394: fw-host0: SelfID complete ohci1394: fw-host0: PhyReqFilter=ffffffffffffffff ieee1394: selfid_complete called with successful SelfID stage ... irm_id: 0xFFC0 node_id: 0xFFC0 ieee1394: NodeMgr: Processing host reset for knodemgrd_0 ohci1394: fw-host0: Single packet rcv'd ohci1394: fw-host0: Got phy packet ctx=0 ... discarded ieee1394: send packet local: ffc00140 ffc0ffff f0000400 ieee1394: received packet: ffc00140 ffc0ffff f0000400 ieee1394: send packet local: ffc00160 ffc00000 00000000 055c0404 ieee1394: received packet: ffc00160 ffc00000 00000000 055c0404 ieee1394: send packet local: ffc00540 ffc0ffff f0000404 ieee1394: received packet: ffc00540 ffc0ffff f0000404 ieee1394: send packet local: ffc00560 ffc00000 00000000 34393331 ieee1394: received packet: ffc00560 ffc00000 00000000 34393331 ieee1394: send packet local: ffc00940 ffc0ffff f0000408 ieee1394: received packet: ffc00940 ffc0ffff f0000408 ieee1394: send packet local: ffc00960 ffc00000 00000000 33b264e0 ieee1394: received packet: ffc00960 ffc00000 00000000 33b264e0 ieee1394: send packet local: ffc00d40 ffc0ffff f000040c ieee1394: received packet: ffc00d40 ffc0ffff f000040c ieee1394: send packet local: ffc00d60 ffc00000 00000000 aa55aa55 ieee1394: received packet: ffc00d60 ffc00000 00000000 aa55aa55 ieee1394: send packet local: ffc01140 ffc0ffff f0000410 ieee1394: received packet: ffc01140 ffc0ffff f0000410 ieee1394: send packet local: ffc01160 ffc00000 00000000 aa55aa55 ieee1394: received packet: ffc01160 ffc00000 00000000 aa55aa55 ieee1394: send packet local: ffc01550 ffc0ffff f0000400 04000000 ieee1394: received packet: ffc01550 ffc0ffff f0000400 04000000 ieee1394: send packet local: ffc01570 ffc00000 00000000 04000000 ieee1394: received packet: ffc01570 ffc00000 00000000 04000000 ieee1394: NodeMgr: raw=0xe064b233 irmc=1 cmc=1 isc=1 bmc=0 pmc=0 cyc_clk_acc=100 max_rec=4096 max_rom=1024 gen=3 lspd=3 ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] ieee1394: send packet 100: ffc10140 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=0, tcode=0x4, speed=3 ohci1394: fw-host0: Starting transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=0 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc10540 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=1, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=1 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc10940 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=2, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=2 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc10d40 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=3, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=3 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc11140 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=4, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=4 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc11540 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=5, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=5 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc11940 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=6, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=6 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc11d40 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=7, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=7 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc12140 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=8, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=8 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc12540 ffc0ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-01:1023, tlabel=9, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 1 tcode=0x4 tLabel=9 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: Error parsing configrom for node 0-01:1023 ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 1f0000c0 ohci1394: fw-host0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0, speed=0 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 ohci1394: fw-host0: Packet sent to node 63 tcode=0x0 tLabel=0 ack=0x11 spd=0 data=0x1F0000C0 ctx=0 ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... ieee1394: send packet 100: 00800000 ff7fffff ohci1394: fw-host0: Inserting packet for node 0-00:0000, tlabel=0, tcode=0x0, speed=0 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 ohci1394: fw-host0: Packet sent to node 0 tcode=0xE tLabel=0 ack=0x11 spd=0 data=0x00000000 ctx=0 ohci1394: fw-host0: IntEvent: 00020010 ohci1394: fw-host0: irq_handler: Bus reset requested ohci1394: fw-host0: Cancel request received ohci1394: fw-host0: Got RQPkt interrupt status=0x00008409 ohci1394: fw-host0: Single packet rcv'd ohci1394: fw-host0: Got phy packet ctx=0 ... discarded ohci1394: fw-host0: IntEvent: 00010000 ohci1394: fw-host0: SelfID interrupt received (phyid 1, root) ohci1394: fw-host0: SelfID packet 0x807fc464 received ieee1394: Including SelfID 0x64c47f80 ohci1394: fw-host0: SelfID packet 0x817fcc5e received ieee1394: Including SelfID 0x5ecc7f81 ohci1394: fw-host0: SelfID for this node is 0x817fcc5e ohci1394: fw-host0: SelfID complete ohci1394: fw-host0: PhyReqFilter=ffffffffffffffff ieee1394: selfid_complete called with successful SelfID stage ... irm_id: 0xFFC1 node_id: 0xFFC1 ohci1394: fw-host0: Cycle master enabled ieee1394: NodeMgr: Processing host reset for knodemgrd_0 ieee1394: send packet 100: ffc01940 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=6, tcode=0x4, speed=3 ohci1394: fw-host0: Starting transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=6 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc01d40 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=7, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=7 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc02140 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=8, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=8 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc02540 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=9, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=9 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc02940 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=10, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=10 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc02d40 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=11, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=11 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc03140 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=12, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=12 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc03540 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=13, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=13 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc03940 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=14, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=14 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: send packet 100: ffc03d40 ffc1ffff f0000400 ohci1394: fw-host0: Inserting packet for node 0-00:1023, tlabel=15, tcode=0x4, speed=3 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008074 ohci1394: fw-host0: Packet sent to node 0 tcode=0x4 tLabel=15 ack=0x14 spd=3 data=0x00000000 ctx=0 ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: send packet local: ffc12940 ffc1ffff f0000400 ieee1394: received packet: ffc12940 ffc1ffff f0000400 ieee1394: send packet local: ffc12960 ffc10000 00000000 055c0404 ieee1394: received packet: ffc12960 ffc10000 00000000 055c0404 ieee1394: send packet local: ffc12d40 ffc1ffff f0000404 ieee1394: received packet: ffc12d40 ffc1ffff f0000404 ieee1394: send packet local: ffc12d60 ffc10000 00000000 34393331 ieee1394: received packet: ffc12d60 ffc10000 00000000 34393331 ieee1394: send packet local: ffc13140 ffc1ffff f0000408 ieee1394: received packet: ffc13140 ffc1ffff f0000408 ieee1394: send packet local: ffc13160 ffc10000 00000000 33b264e0 ieee1394: received packet: ffc13160 ffc10000 00000000 33b264e0 ieee1394: send packet local: ffc13540 ffc1ffff f000040c ieee1394: received packet: ffc13540 ffc1ffff f000040c ieee1394: send packet local: ffc13560 ffc10000 00000000 aa55aa55 ieee1394: received packet: ffc13560 ffc10000 00000000 aa55aa55 ieee1394: send packet local: ffc13940 ffc1ffff f0000410 ieee1394: received packet: ffc13940 ffc1ffff f0000410 ieee1394: send packet local: ffc13960 ffc10000 00000000 aa55aa55 ieee1394: received packet: ffc13960 ffc10000 00000000 aa55aa55 ieee1394: send packet local: ffc13d50 ffc1ffff f0000400 04000000 ieee1394: received packet: ffc13d50 ffc1ffff f0000400 04000000 ieee1394: send packet local: ffc13d70 ffc10000 00000000 04000000 ieee1394: received packet: ffc13d70 ffc10000 00000000 04000000 ieee1394: Node changed: 0-00:1023 -> 0-01:1023 ieee1394: send packet 100: ffff0500 ffc1ffff f0000234 1f0000c0 ohci1394: fw-host0: Inserting packet for node 0-63:1023, tlabel=1, tcode=0x0, speed=0 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 ohci1394: fw-host0: Packet sent to node 63 tcode=0x0 tLabel=1 ack=0x11 spd=0 data=0x1F0000C0 ctx=0 ieee1394: send packet 100: 01800000 fe7fffff ohci1394: fw-host0: Inserting packet for node 0-00:0000, tlabel=0, tcode=0x0, speed=0 ohci1394: fw-host0: Waking transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 ohci1394: fw-host0: Packet sent to node 0 tcode=0xE tLabel=0 ack=0x11 spd=0 data=0x00000000 ctx=0 H I'll show what happens with a module removed, device unplugged and replugged in a second email |
|
From: Hugh D. <hu...@zo...> - 2005-07-21 10:31:31
|
This is without disk attached # modprobe ieee1394 configrom_num_retries=10 configrom_read_interval=1000 nodescan_wait_interval=16 # modprobe ohci1394 dmesg report below, but this is from /var/adm/messages: ["no drivers for .." - relevant?] > Jul 21 11:18:57 dblinuxIII ieee1394.agent[29073]: ... no drivers for IEEE1394 product 0x/0x/0x > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: $Rev: 1299 $ Ben Collins <bco...@de...> > Jul 21 11:18:57 dblinuxIII kernel: PCI: Found IRQ 10 for device 0000:05:04.0 > Jul 21 11:18:57 dblinuxIII kernel: PCI: Sharing IRQ 10 with 0000:00:02.0 > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Remapped memory spaces reg 0xf8c88000 > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Soft reset finished > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Iso contexts reg: 000000a8 implemented: 0000000f > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: 4 iso receive contexts available > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Iso contexts reg: 00000098 implemented: 000000ff > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: 8 iso transmit contexts available > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Receive DMA ctx=0 initialized > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Receive DMA ctx=0 initialized > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Transmit DMA ctx=0 initialized > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Transmit DMA ctx=1 initialized > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[f0504000-f05047ff] Max Packet=[4096] > Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: ATRetries = 00000822 > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: IntEvent: 00030010 > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: irq_handler: Bus reset requested > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: Cancel request received > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: Got RQPkt interrupt status=0x00008409 > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: SelfID interrupt received (phyid 0, root) > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: SelfID packet 0x807fcc56 received > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: SelfID for this node is 0x807fcc56 > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: SelfID complete > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: PhyReqFilter=ffffffffffffffff > Jul 21 11:18:58 dblinuxIII kernel: ohci1394: fw-host0: Single packet rcv'd > Jul 21 11:18:59 dblinuxIII ieee1394.agent[29096]: ... no drivers for IEEE1394 product 0x/0x/0x > Jul 21 11:18:59 dblinuxIII kernel: ohci1394: fw-host0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0, speed=0 > Jul 21 11:18:59 dblinuxIII kernel: ohci1394: fw-host0: Starting transmit DMA ctx=0 > Jul 21 11:18:59 dblinuxIII kernel: ohci1394: fw-host0: IntEvent: 00000001 > Jul 21 11:18:59 dblinuxIII kernel: ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 > Jul 21 11:18:59 dblinuxIII kernel: ohci1394: fw-host0: Packet sent to node 63 tcode=0x0 tLabel=0 ack=0x11 spd=0 data=0x1F0000C0 ctx=0 > Jul 21 11:18:59 dblinuxIII ieee1394.agent[29113]: ... no drivers for IEEE1394 product 0x/0x/0x > Jul 21 11:18:59 dblinuxIII ieee1394.agent[29125]: ... no drivers for IEEE1394 product 0x000000/0x00005e/0x000001 dmesg: ieee1394: Initialized config rom entry `ip1394' ohci1394: $Rev: 1299 $ Ben Collins <bco...@de...> PCI: Found IRQ 10 for device 0000:05:04.0 PCI: Sharing IRQ 10 with 0000:00:02.0 ohci1394: fw-host0: Remapped memory spaces reg 0xf8c88000 ohci1394: fw-host0: Soft reset finished ohci1394: fw-host0: Iso contexts reg: 000000a8 implemented: 0000000f ohci1394: fw-host0: 4 iso receive contexts available ohci1394: fw-host0: Iso contexts reg: 00000098 implemented: 000000ff ohci1394: fw-host0: 8 iso transmit contexts available ohci1394: fw-host0: Receive DMA ctx=0 initialized ohci1394: fw-host0: Receive DMA ctx=0 initialized ohci1394: fw-host0: Transmit DMA ctx=0 initialized ohci1394: fw-host0: Transmit DMA ctx=1 initialized ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[f0504000-f05047ff] Max Packet=[4096] ohci1394: fw-host0: ATRetries = 00000822 ieee1394: CSR: setting expire to 98, HZ=1000 ohci1394: fw-host0: IntEvent: 00030010 ohci1394: fw-host0: irq_handler: Bus reset requested ohci1394: fw-host0: Cancel request received ohci1394: fw-host0: Got RQPkt interrupt status=0x00008409 ohci1394: fw-host0: SelfID interrupt received (phyid 0, root) ohci1394: fw-host0: SelfID packet 0x807fcc56 received ieee1394: Including SelfID 0x56cc7f80 ohci1394: fw-host0: SelfID for this node is 0x807fcc56 ohci1394: fw-host0: SelfID complete ohci1394: fw-host0: PhyReqFilter=ffffffffffffffff ieee1394: selfid_complete called with successful SelfID stage ... irm_id: 0xFFC0 node_id: 0xFFC0 ieee1394: NodeMgr: Processing host reset for knodemgrd_0 ohci1394: fw-host0: Single packet rcv'd ohci1394: fw-host0: Got phy packet ctx=0 ... discarded ieee1394: send packet local: ffc00140 ffc0ffff f0000400 ieee1394: received packet: ffc00140 ffc0ffff f0000400 ieee1394: send packet local: ffc00160 ffc00000 00000000 055c0404 ieee1394: received packet: ffc00160 ffc00000 00000000 055c0404 ieee1394: send packet local: ffc00540 ffc0ffff f0000404 ieee1394: received packet: ffc00540 ffc0ffff f0000404 ieee1394: send packet local: ffc00560 ffc00000 00000000 34393331 ieee1394: received packet: ffc00560 ffc00000 00000000 34393331 ieee1394: send packet local: ffc00940 ffc0ffff f0000408 ieee1394: received packet: ffc00940 ffc0ffff f0000408 ieee1394: send packet local: ffc00960 ffc00000 00000000 33b264e0 ieee1394: received packet: ffc00960 ffc00000 00000000 33b264e0 ieee1394: send packet local: ffc00d40 ffc0ffff f000040c ieee1394: received packet: ffc00d40 ffc0ffff f000040c ieee1394: send packet local: ffc00d60 ffc00000 00000000 aa55aa55 ieee1394: received packet: ffc00d60 ffc00000 00000000 aa55aa55 ieee1394: send packet local: ffc01140 ffc0ffff f0000410 ieee1394: received packet: ffc01140 ffc0ffff f0000410 ieee1394: send packet local: ffc01160 ffc00000 00000000 aa55aa55 ieee1394: received packet: ffc01160 ffc00000 00000000 aa55aa55 ieee1394: send packet local: ffc01550 ffc0ffff f0000400 04000000 ieee1394: received packet: ffc01550 ffc0ffff f0000400 04000000 ieee1394: send packet local: ffc01570 ffc00000 00000000 04000000 ieee1394: received packet: ffc01570 ffc00000 00000000 04000000 ieee1394: NodeMgr: raw=0xe064b233 irmc=1 cmc=1 isc=1 bmc=0 pmc=0 cyc_clk_acc=100 max_rec=4096 max_rom=1024 gen=3 lspd=3 ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 1f0000c0 ohci1394: fw-host0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0, speed=0 ohci1394: fw-host0: Starting transmit DMA ctx=0 ohci1394: fw-host0: IntEvent: 00000001 ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011 ohci1394: fw-host0: Packet sent to node 63 tcode=0x0 tLabel=0 ack=0x11 spd=0 data=0x1F0000C0 ctx=0 |
|
From: Hugh D. <hu...@zo...> - 2005-07-22 08:35:22
|
hmm. I've now tested the card and the disk separately & together under other OS's (not in the same mobo, mind). Disks correctly recognised (but the partitions not actually accessible as they're resiserfs) by OSX via FW800 (on newish G5). Disks correctly recognised and readable using rfstool connected via USB2.0 on WinXP (which was quite cool!) Card recognised, and diskset accessible in disk management under win2K (32 bit slot) via FW800. (took a bit of setting up but it was a fresh ghost image of win2k so the drivers took a bit of settling (and I couldn't get USB to work properly at all)). Noteably, I *did* have it working on this mobo under (I'm nearly sure..) 2.6.10 when warm booted - it was a cold boot to put more RAM in that made it go away.. Reckon I should try a 2.6.13-rc, or a patched 2.4? H Hugh Dixon wrote: > This is without disk attached > # modprobe ieee1394 configrom_num_retries=10 > configrom_read_interval=1000 nodescan_wait_interval=16 > # modprobe ohci1394 > > dmesg report below, but this is from /var/adm/messages: ["no drivers > for .." - relevant?] > >> Jul 21 11:18:57 dblinuxIII ieee1394.agent[29073]: ... no drivers for >> IEEE1394 product 0x/0x/0x >> Jul 21 11:18:57 dblinuxIII kernel: ohci1394: $Rev: 1299 $ Ben Collins >> <bco...@de...> >> Jul 21 11:18:57 dblinuxIII kernel: PCI: Found IRQ 10 for device >> 0000:05:04.0 >> Jul 21 11:18:57 dblinuxIII kernel: PCI: Sharing IRQ 10 with 0000:00:02.0 >> Jul 21 11:18:57 dblinuxIII kernel: ohci1394: fw-host0: Remapped memory |
|
From: Stefan R. <st...@s5...> - 2005-07-22 13:33:06
|
Hugh Dixon wrote: > I've now tested the card and the disk separately & together under other > OS's (not in the same mobo, mind). [...] > Noteably, I *did* have it working on this mobo under (I'm nearly sure..) > 2.6.10 when warm booted - it was a cold boot to put more RAM in that > made it go away.. Could you check the card's GUID under OS X or Windows? (Don't ask me how.) I suspect now that their drivers do some magic to the card that ours does not. There is hardware which works if the machine is booted into Windows, then rebooted into Linux, but doesn't work if cold-booted straight into Linux. > Reckon I should try a 2.6.13-rc, or a patched 2.4? 2.6.13 won't help here. 2.4 perhaps, but I doubt it. -- Stefan Richter -=====-=-=-= -=== =-==- http://arcgraph.de/sr/ |
|
From: Hugh D. <hu...@zo...> - 2005-07-22 13:59:20
|
Thing is, under OSX or Windows, it doesn't show as much besides an "Texas Instruments OHCI compliant ieee1394 Controller" (or words to that effect - didn't install anything Lacie-specific at all). I'll have a go when I'm back in the office - have just compiled and installed 2.6.13-rc3 to try ... and indeed, no joy. I did notice that it seemed to report 2 GUID's yesterday - will look in output again. One that nonsensey 55aa55aa55aa55aa and one more "random/genuine" semingly reported by "the other host" (0-00:1023 vs 0-01:1023) - can't find it now. grrr. OSX would probably have potential as even the GUI system profiler is pretty thorough. Didn't try the card in OSX machine before - will do (Monday most likely) USB 2.0 noteably failed to allow any mounting of partitions yesterday - lots of nasty errors though it did detect the diskset and its partitions. Maybe I'll just hang the RAID box of OSX and set up rsync and samba and the like as I currently have the old setup under linux ... H Stefan Richter wrote: > Hugh Dixon wrote: > >> I've now tested the card and the disk separately & together under >> other OS's (not in the same mobo, mind). > > [...] > >> Noteably, I *did* have it working on this mobo under (I'm nearly >> sure..) 2.6.10 when warm booted - it was a cold boot to put more RAM >> in that made it go away.. > |
|
From: Stefan R. <st...@s5...> - 2005-07-22 16:02:05
|
Hugh Dixon wrote: > Thing is, under OSX or Windows, it doesn't show as much besides an > "Texas Instruments OHCI compliant ieee1394 Controller" (or words to that > effect - didn't install anything Lacie-specific at all). If you have the OS X or Windows box with the LaCie card and a Linux box with another FireWire card in the same room, you could hook them together via FireWire and look up the LaCie card's GUID in Linux' sysfs. But... > I'll have a go when I'm back in the office - have just compiled and > installed 2.6.13-rc3 to try ... and indeed, no joy. I did notice that > it seemed to report 2 GUID's yesterday - will look in output again. One > that nonsensey 55aa55aa55aa55aa and one more "random/genuine" semingly > reported by "the other host" (0-00:1023 vs 0-01:1023) - can't find it > now. grrr. ...if you find it in an old log, the simpler. *However*, the only thing we learn from this is that the LaCie card is indeed not correctly set up under Linux (if it can have a proper GUID under the other OSs). What we still don't know is if this is actually the source of the problems to talk to the disk (I tend to blame the card indeed). And more importantly, we still don't learn how to cure that. OK, there _is_ a quite simple cure with a certain chance for success: Replace the card by a different one, preferably one that someone else reported working under Linux. > Maybe I'll just hang the RAID box of OSX and set up rsync and samba and > the like as I currently have the old setup under linux ... Seems to be an even better solution, since that OS is supported by LaCie. -- Stefan Richter -=====-=-=-= -=== =-==- http://arcgraph.de/sr/ |
|
From: Hugh D. <hu...@zo...> - 2005-07-22 16:10:59
|
I'm keen to help try to get this working (or just generally advance the knowledgebase) - I'll probably bring in a fw400 disk and try hanging it off the card (under linux) and also try the card in OSX to see what GUID etc I can get out of it. I'll also see if I can find a good FW800 card to try - top recommendations people? H Stefan Richter wrote: > Hugh Dixon wrote: > >> Thing is, under OSX or Windows, it doesn't show as much besides an >> "Texas Instruments OHCI compliant ieee1394 Controller" (or words to >> that effect - didn't install anything Lacie-specific at all). > > > If you have the OS X or Windows box with the LaCie card and a Linux box > with another FireWire card in the same room, you could hook them > together via FireWire and look up the LaCie card's GUID in Linux' sysfs. > But... > >> I'll have a go when I'm back in the office - have just compiled and >> installed 2.6.13-rc3 to try ... and indeed, no joy. I did notice that >> it seemed to report 2 GUID's yesterday - will look in output again. >> One that nonsensey 55aa55aa55aa55aa and one more "random/genuine" >> semingly reported by "the other host" (0-00:1023 vs 0-01:1023) - can't >> find it now. grrr. > > > ...if you find it in an old log, the simpler. *However*, the only thing > we learn from this is that the LaCie card is indeed not correctly set up > |
|
From: Hugh D. <hu...@zo...> - 2005-07-26 10:51:28
|
FYI all. Having booted the [Lacie FW800 - TI-chip - ] card in another mobo (still non-64bit I'm afraid), it still reports the nonsense GUID under 2.6.10 at any rate. Time to track down a 64bit mobo I think - will try it in the G5 if that's got one. Hugh Dixon wrote: > I'm keen to help try to get this working (or just generally advance the > knowledgebase) - I'll probably bring in a fw400 disk and try hanging it > off the card (under linux) and also try the card in OSX to see what GUID > etc I can get out of it. I'll also see if I can find a good FW800 card > to try - top recommendations people? > > H > > Stefan Richter wrote: > >> Hugh Dixon wrote: >> >>> Thing is, under OSX or Windows, it doesn't show as much besides an >>> "Texas Instruments OHCI compliant ieee1394 Controller" (or words to >>> that effect - didn't install anything Lacie-specific at all). >> >> >> >> If you have the OS X or Windows box with the LaCie card and a Linux >> box with another FireWire card in the same room, you could hook them >> together via FireWire and look up the LaCie card's GUID in Linux' >> sysfs. But... >> >>> I'll have a go when I'm back in the office - have just compiled and >>> installed 2.6.13-rc3 to try ... and indeed, no joy. I did notice >>> that it seemed to report 2 GUID's yesterday - will look in output >>> again. One that nonsensey 55aa55aa55aa55aa and one more >>> "random/genuine" semingly reported by "the other host" (0-00:1023 vs >>> 0-01:1023) - can't find it now. grrr. >> >> >> >> ...if you find it in an old log, the simpler. *However*, the only >> thing we learn from this is that the LaCie card is indeed not >> correctly set up > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user > > |
|
From: Hugh D. <hu...@zo...> - 2005-07-26 13:19:26
|
Well..!! I feel a bit dumb for not trying this earlier .. Swtiched the Lacie Biggest box off (much bleeping ensued), switched it back on and let it settle. Result: Detected successfully....! This was prompted by the fact that it wasn't being recognised at all via USB either, whereas that was definitely working before (though it was giving a range of horrible errors if I tried to actually mount a partition). I have grabbed a huge stack of dmesg output (the ieee1394/ohci1394 module was compiled with full-verbosity, since switched back off). Key bits: ieee1394 disable_irm=1 appears to be an absolute requirement. noteably it's showing both the nonsense GUID and a 'real' one. this is in a 33Mhz/32bit PCI slot - any suggestions on what to use to test the data transfer rates in the current setup? here's the "transcript" - # = my commandline, > = dmesg output (this is all after I recompiled ieee1394 support without the full-verbosity option - Stefan would you like me to send you the more verbose output? #modprobe ieee1394 (plain) > ieee1394: Initialized config rom entry `ip1394' > ohci1394: $Rev: 1313 $ Ben Collins <bco...@de...> > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 9 (level, low) -> IRQ > 9 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[fe1ff800-fe1fffff] Max > Packet=[4096] > ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node added: ID:BUS[0-01:1023] GUID[00d04b5609081e85] > ieee1394: The root node is not cycle master capable; selecting a new root node a > nd resetting... > ieee1394: Node changed: 0-01:1023 -> 0-00:1023 > ieee1394: Node changed: 0-00:1023 -> 0-01:1023 #modprobe -r sbp2, ohci1394,ieee1394 > ieee1394: Node removed: ID:BUS[0-01:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00d04b5609081e85] #modprobe ieee1394 disable_irm=1 > ieee1394: Initialized config rom entry `ip1394' > ieee1394: IRM functionality disabled #modprobe ohci1394 > ohci1394: $Rev: 1313 $ Ben Collins <bco...@de...> > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 9 (level, low) -> IRQ > 9 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[fe1ff800-fe1fffff] Max > Packet=[4096] > ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node added: ID:BUS[0-01:1023] GUID[00d04b5609081e85] > sbp2: $Rev: 1316 $ Ben Collins <bco...@de...> > scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices > ieee1394: sbp2: Logged into SBP-2 device > ieee1394: Node 0-01:1023: Max speed [S800] - Max payload [4096] > Vendor: LaCie Model: Biggest F800 Rev: 1.32 > Type: Direct-Access ANSI SCSI revision: 06 > SCSI device sda: 976790016 512-byte hdwr sectors (500116 MB) > sda: asking for cache data failed > sda: assuming drive cache: write through > SCSI device sda: 976790016 512-byte hdwr sectors (500116 MB) > sda: asking for cache data failed > sda: assuming drive cache: write through > sda: sda1 sda2 sda3 > Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 > Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0 Bingo! - partitions mounted, rsyncing across from the main server now. H It all makes a bit more sense now, as I had to power the disks down before I could try them in the various other platforms that I reported successul detection from!! Question to ask is whether Lacie should really be able to fix whatever freeze-up is happening I suppose? |
|
From: Stefan R. <st...@s5...> - 2005-07-26 19:42:00
|
Hugh Dixon wrote: > Swtiched the Lacie Biggest box off (much bleeping ensued), switched it > back on and let it settle. > Result: Detected successfully....! So the Biggest Disk's bridge was the culprit, not the host adapter. > ieee1394 disable_irm=1 appears to be an absolute requirement. I will get back to this eventually. We have to tweak nodemgr to work without that parameter. > noteably it's showing both the nonsense GUID and a 'real' one. The real one is of course from the disk. The nonsense GUID won't matter as long as you don't attach another LaCie card to the same bus which features the same (then not exactly globally unique) GUID. > this is in a 33Mhz/32bit PCI slot - any suggestions on what to use to > test the data transfer rates in the current setup? E.g. "hdparm -tT /dev/sdXY" for raw read spead of the block device, bonnie++ for tests with filesystem. Something more sophisticated (or hdparm or bonnie++ together with specifically created partitions) to take physical layout on the disk(s) into account. > Stefan would you like me to send you the more verbose output? If you kept logs from a session without disable_irm and one with, I'd like to have a look at them. > Question to ask is whether Lacie should really be able to fix whatever > freeze-up is happening I suppose? It may be difficult for them to track down how the Biggest Disk got into this state in the first place. We only know how the state looked (disk answering with ack_busy_X all the time). -- Stefan Richter -=====-=-=-= -=== ==-=- http://arcgraph.de/sr/ |
|
From: Hugh D. <hu...@zo...> - 2005-07-27 08:53:51
|
> So the Biggest Disk's bridge was the culprit, not the host adapter. indeed it seems so! (to you at least! - I'm not entirely sure what to read into the ouput still). > E.g. "hdparm -tT /dev/sdXY" for raw read spead of the block This reports about 42Mb/sec for disk reads at the moment. >> Stefan would you like me to send you the more verbose output? > > > If you kept logs from a session without disable_irm and one > with, I'd like to have a look at them. there's a *lot* of stuff there when it connects successfully - I'll do you a set and send you them off-list. Cheers all. Hugh |
|
From: Stefan R. <st...@s5...> - 2005-07-21 21:50:45
|
Hugh Dixon wrote: > OK.. Lots of output (and no success, seemingly) Yes, it's still the same problem AFAICT. > [I'm assuming ohci_hcd is not relevant here?], Yes, ohci_hcd is unrelated to FireWire. -- Stefan Richter -=====-=-=-= -=== =-=-= http://arcgraph.de/sr/ |
|
From: Stefan R. <st...@s5...> - 2005-07-20 14:44:08
|
Hugh Dixon wrote: >> drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread': >> drivers/ieee1394/ieee1394_core.c:1035: error: too few arguments to >> function `try_to_freeze' >> drivers/ieee1394/ieee1394_core.c: In function `ieee1394_init': >> drivers/ieee1394/ieee1394_core.c:1113: warning: implicit declaration >> of function `class_create' That's because of changes of internal interfaces from Linux 2.6.12 to 2.6.13. (See my previous post.) Take version 1299 from http://www.linux1394.org/websvn/listing.php?repname=Linux+1394&path=%2Ftrunk%2F&rev=1299 or from my site, or check it out with the Subversion client: $ svn checkout -r 1299 svn://svn.linux1394.org/ieee1394/trunk/ ieee1394 -- Stefan Richter -=====-=-=-= -=== =-=-- http://arcgraph.de/sr/ |
|
From: Hugh D. <hu...@zo...> - 2005-07-20 15:03:44
|
Yeah - thanks Stefan - I grabbed the 1299 trunk from your link. Compiled fine but it's not happy .. Post reboot (still 2.6.12.3 here), post modprobe -r ieee1394 and ohci1394 modprobe ieee1394 diable_irm=1 : > ieee1394: Initialized config rom entry `ip1394' > ieee1394: IRM functionality disabled modprobe ohci1394 : > ohci1394: $Rev: 1299 $ Ben Collins <bco...@de...> > PCI: Found IRQ 10 for device 0000:05:04.0 > PCI: Sharing IRQ 10 with 0000:00:02.0 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[f0504000-f05047ff] Max Packet=[4096] > ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] > ieee1394: Error parsing configrom for node 0-01:1023 Should I try compiling ieee into the kernel statically? Or is it perhaps some conflict with PCI in this PC ? Thanks guys. Am glad this machine is a 3GHz pIV the amount of kernel/module compilation I've been doing!! H |
|
From: Stefan R. <st...@s5...> - 2005-07-20 15:19:08
|
Hugh Dixon wrote: ... >> ieee1394: Error parsing configrom for node 0-01:1023 > > Should I try compiling ieee into the kernel statically? I always prefer modules (except for drivers that are required before / is mounted) and I doubt that statically linked 1394 drivers would help. > Or is it perhaps some conflict with PCI in this PC ? I don't think so; at least not according to the log messages. > Thanks guys. Am glad this machine is a 3GHz pIV the amount of > kernel/module compilation I've been doing!! Would you "make modules" yet another time, after configuring the 1394 drivers with "excessive debug logging", and post the log? -- Stefan Richter -=====-=-=-= -=== =-=-- http://arcgraph.de/sr/ |
