External Firewire Drive

Mike Shambaugh yellowdog-general@lists.terrasoftsolutions.com
Wed Sep 17 08:50:01 2003


I'm currently unable to mount an external firewire drive through Yellow Dog
Linux 3.0. I've seen other mentions of similar issues in the archives of the
list, but no solutions.

Yellow Dog 3.0 was successfully installed on a B&W G3 with built-in firewire
ports. Everything else about the machine is running perfectly, but I can't
get to the point where I can mount my external drive.

"rpm -qa | grep kernel" on this machine yields: kernel-2.4.20-8d


With respect to firewire, lspci -vv yields:

==================================================================
01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE 1394
Link Layer Controller (rev 02) (prog-if 00 [Generic])
        Subsystem: Apple Computer Inc.: Unknown device 001c
        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-
        Latency: 16 (750ns min, 1000ns max), cache line size 20
        Interrupt: pin A routed to IRQ 21
        Region 0: Memory at 80881000 (32-bit, non-prefetchable) [disabled]
[size=4K]
        Region 1: Memory at 808b0000 (32-bit, non-prefetchable) [disabled]
[size=64K]
        Region 2: Memory at 808a0000 (32-bit, non-prefetchable) [disabled]
[size=64K]
        Expansion ROM at 80890000 [disabled] [size=64K]
==================================================================


Attempts to "modprobe ieee1394" yield no output on the console or in dmesg
(apparently a good sign), but attempts to "modprobe ohci1394" as instructed
at linux1394.org yield the following error:

==================================================================
/lib/modules/2.4.20-8d/kernel/drivers/ieee1394/ohci1394.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8d/kernel/drivers/ieee1394/ohci1394.o: insmod
/lib/modules/2.4.20-8d/kernel/drivers/ieee1394/ohci1394.o failed
/lib/modules/2.4.20-8d/kernel/drivers/ieee1394/ohci1394.o: insmod ohci1394
failed
==================================================================


What do I need to do to get the "ohci1394" module to load? I'm assuming that
that module should load even if there isn't a drive connected (it is
FireWire, after all). Is that incorrect? Do I need to change something in
relation to the kernel?

I appreciate any help anyone can give. Thanks,


----------------------------------------------------
Mike Shambaugh
Chief Technology Officer
Nucleus Medical Art, Inc.
http://www.nucleusmedicalart.com/
http://www.medicallegalart.com/
1275 Shiloh Road
Suite 3130
Kennesaw, GA 30144
Voice: (800) 333-0753
----------------------------------------------------