A firewire PCI host adapter is attached to a PC running SuSE 8.1. The controller has been detected by SuSE. An Iomega Perless firewire drive is attached to the controller but cannot be accessed. During the boot process, the lights flash and stay on while the PC is switched. On another PC, which is a Toshiba laptop, with a PCMCIA firewire adapter the drive is automatically recognised and ready for use using Linux. Can anyone offer any assistance to install the drive on the first PC?
Found a post on this list dated 24 Oct 2002 by Josef Demergis. After booting, the following two commands have to run: 1) modprobe ieee1394 2) modprobe ohci 1394. The firewire drive is then visible and can be mounted. Follwing the guidance from another post, the "boot.local" file was edited and the following commands added: modprobe ieee1394 modprobe ohci 1394 modprobe raw1394 Line was added to fstab file to mount /dev/sdb4 to /media/sdb4. This does not work. Any ideas how to amend the configuration files so that after the boot process the firewire drive is mounted and ready for use? On Monday 30 December 2002 20:01, Linux World 999 wrote:
A firewire PCI host adapter is attached to a PC running SuSE 8.1. The controller has been detected by SuSE. An Iomega Perless firewire drive is attached to the controller but cannot be accessed. During the boot process, the lights flash and stay on while the PC is switched.
On another PC, which is a Toshiba laptop, with a PCMCIA firewire adapter the drive is automatically recognised and ready for use using Linux.
Can anyone offer any assistance to install the drive on the first PC?
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) I got the rescan-scsi-bus.sh from http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh i did a quick tail on my log file with this command: tail -100 /var/log/messages|grep scsi This produced: Dec 31 08:26:06 reddot kernel: scsi singledevice 0 0 7 0 Dec 31 08:26:06 reddot kernel: scsi singledevice 1 0 0 0 Dec 31 08:26:06 reddot kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 Dec 31 08:26:06 reddot kernel: scsi singledevice 1 0 1 0 now i know that the firewire drive is "sda". From this point i can now create the fdisk it and create the file system. Once the file system is created/formated you can add the first group of 5 commands to your rc.local (boot.local on SuSE). Scott Linux World 999 wrote:
Found a post on this list dated 24 Oct 2002 by Josef Demergis. After booting, the following two commands have to run:
1) modprobe ieee1394 2) modprobe ohci 1394.
The firewire drive is then visible and can be mounted.
Follwing the guidance from another post, the "boot.local" file was edited and the following commands added:
modprobe ieee1394 modprobe ohci 1394 modprobe raw1394
Line was added to fstab file to mount /dev/sdb4 to /media/sdb4.
This does not work. Any ideas how to amend the configuration files so that after the boot process the firewire drive is mounted and ready for use?
On Monday 30 December 2002 20:01, Linux World 999 wrote:
A firewire PCI host adapter is attached to a PC running SuSE 8.1. The controller has been detected by SuSE. An Iomega Perless firewire drive is attached to the controller but cannot be accessed. During the boot process, the lights flash and stay on while the PC is switched.
On another PC, which is a Toshiba laptop, with a PCMCIA firewire adapter the drive is automatically recognised and ready for use using Linux.
Can anyone offer any assistance to install the drive on the first PC?
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>
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>
You must type /sbin/modprobe in boot.local since the path hasn't been set up yet when boot.local is run. Op maandag 30 december 2002 23:20, schreef Linux World 999:
Found a post on this list dated 24 Oct 2002 by Josef Demergis. After booting, the following two commands have to run:
1) modprobe ieee1394 2) modprobe ohci 1394.
The firewire drive is then visible and can be mounted.
Follwing the guidance from another post, the "boot.local" file was edited and the following commands added:
modprobe ieee1394 modprobe ohci 1394 modprobe raw1394
Line was added to fstab file to mount /dev/sdb4 to /media/sdb4.
This does not work. Any ideas how to amend the configuration files so that after the boot process the firewire drive is mounted and ready for use?
On Monday 30 December 2002 20:01, Linux World 999 wrote:
A firewire PCI host adapter is attached to a PC running SuSE 8.1. The controller has been detected by SuSE. An Iomega Perless firewire drive is attached to the controller but cannot be accessed. During the boot process, the lights flash and stay on while the PC is switched.
On another PC, which is a Toshiba laptop, with a PCMCIA firewire adapter the drive is automatically recognised and ready for use using Linux.
Can anyone offer any assistance to install the drive on the first PC?
participants (4)
-
Junk Account - HaHaHa -
Linux World -
Linux World 999
-
Z_God