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. Art
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.'
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
Found one article on the internet and tried it: In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394 Then in the /etc/init.d/boot.local file I added: insmod sbp2 After rebooting, still get invalid block device error. If I try insmod on all of the modules, it says they are already installed. Just another puzzle. Art -----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 5:17 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive 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 -- 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
System is Dell Inspiron 8100 w/ Suse 8.0 and KDE 3.0.1 all updated with YaST2 as of last Friday. I have tried the following with no success in run levels 3 & 5 to be able to mount ieee1394 firewire harddisk: (during boot, messages say modules are loaded) In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394 Then in the /etc/init.d/boot.local file I added: modprobe sbp2 No results In /etc/init.d/boot.local insmod ieee1394 insmod ohci1394 no results In /etc/init.d/boot.local insmod ieee1394 insmod ohci1394 insmod sdp2 no results In /etc/init.d/boot.local insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sdp2 no results In /etc/init.d/boot.local modprobe ieee1394 modprobe ohci1394 no results In /etc/init.d/boot.local modprobe ieee1394 modprobe ohci1394 modprobe sbp2 no results I can enter any of the following from the console, then fdisk -l shows /dev/sda1 and I and mount the drive: insmod ieee1394 insmod ohci1394 insmod ieee1394 insmod ohci1394 insmod raw1394 insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sbp2 (will say spd2 module is already installed. insmod ieee1394 insmod ohci1394 insmod sbp2 (will say sbp2 module is already installed. modprobe ieee1394 modprobe ohci1394 modprobe ieee1394 modprobe ohci1394 modprobe raw1394 modprobe ieee1394 modprobe ohci1394 modprobe raw1394 modprobe sbp2 Does anyone have a solution to the puzzle? If so, please let me know, I have run out of things to try and found now info on the suse website or no further info on google internet search. Also tried everything at www.ieee1394.org with no success. Art -----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 8:49 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive Found one article on the internet and tried it: In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394 Then in the /etc/init.d/boot.local file I added: insmod sbp2 After rebooting, still get invalid block device error. If I try insmod on all of the modules, it says they are already installed. Just another puzzle. Art -----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 5:17 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive 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.'
I'm trying to solve this same problem.
The response I received from SuSE which I have not yet
tried out is to create a file calles "modules" under
/etc. Each line should be the name of a module to load
in the correct sequence.
You need to have your fstab modified to mount the
ieee1394 partitions.
After reboot it should work.
Post what happens.
Babu
--- Art Fore
System is Dell Inspiron 8100 w/ Suse 8.0 and KDE 3.0.1 all updated with YaST2 as of last Friday.
I have tried the following with no success in run levels 3 & 5 to be able to mount ieee1394 firewire harddisk: (during boot, messages say modules are loaded)
In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394
Then in the /etc/init.d/boot.local file I added: modprobe sbp2
No results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394
no results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394 insmod sdp2
no results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sdp2
no results
In /etc/init.d/boot.local
modprobe ieee1394 modprobe ohci1394
no results
In /etc/init.d/boot.local
modprobe ieee1394 modprobe ohci1394 modprobe sbp2
no results
I can enter any of the following from the console, then fdisk -l shows /dev/sda1 and I and mount the drive:
insmod ieee1394 insmod ohci1394
insmod ieee1394 insmod ohci1394 insmod raw1394
insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sbp2 (will say spd2 module is already installed.
insmod ieee1394 insmod ohci1394 insmod sbp2 (will say sbp2 module is already installed.
modprobe ieee1394 modprobe ohci1394
modprobe ieee1394 modprobe ohci1394 modprobe raw1394
modprobe ieee1394 modprobe ohci1394 modprobe raw1394 modprobe sbp2
Does anyone have a solution to the puzzle? If so, please let me know, I have run out of things to try and found now info on the suse website or no further info on google internet search. Also tried everything at www.ieee1394.org with no success.
Art
-----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 8:49 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive
Found one article on the internet and tried it:
In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394
Then in the /etc/init.d/boot.local file I added: insmod sbp2
After rebooting, still get invalid block device error.
If I try insmod on all of the modules, it says they are already installed.
Just another puzzle.
Art
-----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 5:17 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive
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 previous thread I said the firwire harddrive
On Tuesday 25 June 2002 18.03, Art Fore wrote: 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.'
=== message truncated === __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
This did not work. Modules were not installed. Also tried installing modules
in the kernel, that really screwed things up. fstab is already modified as I
can do this in the console and then can mount the drive via an icon on the
desktop.
Art
-----Original Message-----
From: babu walad [mailto:vyav@yahoo.com]
Sent: Wednesday, June 26, 2002 10:35 AM
To: art_fore@3mts.com; suse-linux-e@suse.com
Subject: RE: [SLE] insmod & Firewire Harddrive
I'm trying to solve this same problem.
The response I received from SuSE which I have not yet
tried out is to create a file calles "modules" under
/etc. Each line should be the name of a module to load
in the correct sequence.
You need to have your fstab modified to mount the
ieee1394 partitions.
After reboot it should work.
Post what happens.
Babu
--- Art Fore
System is Dell Inspiron 8100 w/ Suse 8.0 and KDE 3.0.1 all updated with YaST2 as of last Friday.
I have tried the following with no success in run levels 3 & 5 to be able to mount ieee1394 firewire harddisk: (during boot, messages say modules are loaded)
In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394
Then in the /etc/init.d/boot.local file I added: modprobe sbp2
No results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394
no results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394 insmod sdp2
no results
In /etc/init.d/boot.local
insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sdp2
no results
In /etc/init.d/boot.local
modprobe ieee1394 modprobe ohci1394
no results
In /etc/init.d/boot.local
modprobe ieee1394 modprobe ohci1394 modprobe sbp2
no results
I can enter any of the following from the console, then fdisk -l shows /dev/sda1 and I and mount the drive:
insmod ieee1394 insmod ohci1394
insmod ieee1394 insmod ohci1394 insmod raw1394
insmod ieee1394 insmod ohci1394 insmod raw1394 insmod sbp2 (will say spd2 module is already installed.
insmod ieee1394 insmod ohci1394 insmod sbp2 (will say sbp2 module is already installed.
modprobe ieee1394 modprobe ohci1394
modprobe ieee1394 modprobe ohci1394 modprobe raw1394
modprobe ieee1394 modprobe ohci1394 modprobe raw1394 modprobe sbp2
Does anyone have a solution to the puzzle? If so, please let me know, I have run out of things to try and found now info on the suse website or no further info on google internet search. Also tried everything at www.ieee1394.org with no success.
Art
-----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 8:49 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive
Found one article on the internet and tried it:
In /etc/modules.conf added the following lines: pre-install ohci1394 modprobe ieee1394 pre-install sbp2 modprobe ohci1394
Then in the /etc/init.d/boot.local file I added: insmod sbp2
After rebooting, still get invalid block device error.
If I try insmod on all of the modules, it says they are already installed.
Just another puzzle.
Art
-----Original Message----- From: Art Fore [mailto:art_fore@3mts.com] Sent: Tuesday, June 25, 2002 5:17 PM To: suse-linux-e@suse.com Subject: RE: [SLE] insmod & Firewire Harddrive
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 previous thread I said the firwire harddrive
On Tuesday 25 June 2002 18.03, Art Fore wrote: 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.'
=== message truncated === __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
participants (3)
-
Anders Johansson -
Art Fore -
babu walad