I added the following lines to the /etc/init.d/boot.local insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sbp2 When I reboot, during boot it comes up with messages using library xxxxx.o for each line. When I do fdisk -1 after boot, the firewire drive is not there. If I do not have these line in the boot.local file, then I can enter the insmod commands shown above, and then I can see the firewire drive. It also does not work if I use modprobe. Could any explain why this does not work and a solution for it? I did not try the modules.conf file as it was far too complex for a non-programmer like me. Art -----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Tuesday, June 25, 2002 9:06 AM To: suse-linux-e@suse.com Subject: Re: [SLE] insmod On Tuesday 25 June 2002 18.03, Art Fore wrote:
On previous thread I said the firwire harddrive problem was solved. It was until I rebooted. How can I get the insmod ochi1394 and insmod ieee1394 to hold permanently? I am rather new to Linux and still learning.
You could probably put a line or two in /etc/modules.conf, but the simplest solution is to put the insmod lines in /etc/init.d/boot.local. That gets run as the very first thing on bootup. regards Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.' -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com