On the pc on which SuSE runs, the only consistent way to mount the firewire drive is: 1) In the boot.local file, added the command "/sbin/modprobe ohci1394" 2) In /etc/init.d/rc5, created a file called "s20_sbp2" with a single command "/sbin/modprobe sbp2". For a reason not understood, inserting both commands in the "boot.local" file will lead to the firewore drive being recognised if the pc is cold booted but not if warm booted. Thanks for all your help. In particluar, one person who replied to the post suggested putitng the full command for modprobe (ie /sbin/modprobe) and just modprobe because the path parameter is not available when this file is read. Not being aware of this, the commands did not work. On Wednesday 01 January 2003 21:42, Linux World wrote:
On Tuesday 31 December 2002 13:43, Junk Account - HaHaHa wrote:
On my Redhat 8 box I got my firewire drive to work by doing pretty much is said below.
I am not sure this is the "right" way to do it but it worked for me.
ran each of these commands in this order /sbin/insmod ieee1394 /sbin/insmod ohci1394 /sbin/insmod raw1394 /usr/local/bin/rescan-scsi-bus.sh mount /dev/sda5 /data (you can mount where ever you need to mount)
After a lot of trial and error using
modprobe ieee1394 modprobe ohci 1394 modprobe spb2
gave indiffereent results. The drive was recognised about 40% of the time and not the rest. SuSE 8.1 tries to load some drivers during the hardware recognition but not all.
After a cold boot, running "lsmode | grep 1394" gave the following results:
ohci1394 [unused] ieee1394 [ohci1394]
Only the command "modprobe sbp2" needs to be run followed by the mount command. Not being a Linux or ieee1394 expert, re-loading the ieee1394 and ohci1394 drives a second time causes problems in recognising the drive. Running spb2 only recongnises the drive.
Putting the modprobe commands in boot.local did not help. Does anyone advise in which boot script the "modprobe sbp2" command so that is the last command before logging into linux?
<snip>