Hi, I recently installed SuSE Linux Professional 10 on an old IBM Aptiva with an even older 3Com Etherlink III card. The card was detected during the installation and works fine once it is started, but even though I specified that it be started on boot, I have to go into YaST after each reboot and start it manually. Since there is new construction going on in our neighborhood, brief power outages are the rule lately, so this is becoming annoying. Is there any way to insure that the interface is started automatically? (Or does anyone have a script that would do the deed without having to fire up YaST?) Thanks in advance, Gordon Keehn
On Friday 27 January 2006 13:41, Gordon Keehn wrote:
Hi, I recently installed SuSE Linux Professional 10 on an old IBM Aptiva with an even older 3Com Etherlink III card. The card was detected during the installation and works fine once it is started, but even though I specified that it be started on boot, I have to go into YaST after each reboot and start it manually. Since there is new construction going on in our neighborhood, brief power outages are the rule lately, so this is becoming annoying. Is there any way to insure that the interface is started automatically? (Or does anyone have a script that would do the deed without having to fire up YaST?) Thanks in advance, Gordon Keehn
Once again, more information needed. What version of SuSE are you running?? With the later kernels, there may be a need to include the module for your NIC in the initrd loaded modules. Do you know what module it is? If not, hwinfo --netcard should tell you.
hi I have VMware 5.0. Is it possible to install it on SuSE10? oliver
Gordon Keehn wrote:
Hi, I recently installed SuSE Linux Professional 10 on an old IBM Aptiva with an even older 3Com Etherlink III card. The card was detected during the installation and works fine once it is started, but even though I specified that it be started on boot, I have to go into YaST after each reboot and start it manually. Since there is new construction going on in our neighborhood, brief power outages are the rule lately, so this is becoming annoying. Is there any way to insure that the interface is started automatically? (Or does anyone have a script that would do the deed without having to fire up YaST?) Thanks in advance, Gordon Keehn
I had a similar problem with SuSE 9.1 on one of the machines I setup. After searching a german list I found a suggestion that the following should be done: in the file /etc/init.d/boot.local add the following line modprobe 3c509 subsitute your ethernet module for the 3c509. It seems to work for me. Your mileage may vary.
Mark wrote:
Gordon Keehn wrote:
I recently installed SuSE Linux Professional 10 on an old IBM Aptiva with an even older 3Com Etherlink III card. The card was detected during the installation and works fine once it is started, but even though I specified that it be started on boot, I have to go into YaST after each reboot and start it manually. Since there is new construction going on in our neighborhood, brief power outages are the rule lately, so this is becoming annoying. Is there any way to insure that the interface is started automatically? (Or does anyone have a script that would do the deed without having to fire up YaST?)
I had a similar problem with SuSE 9.1 on one of the machines I setup. After searching a german list I found a suggestion that the following should be done:
in the file /etc/init.d/boot.local add the following line modprobe 3c509
subsitute your ethernet module for the 3c509.
It seems to work for me. Your mileage may vary.
Thanks, many. Not only did updating /etc/init.d/boot.local work, but entering the modprobe command under su proved a much easier way to activate the card that opening YaST every time the box is rebooted. That about covered both my questions. Cheers, Gordon
participants (5)
-
Bruce Marshall -
Gordon Keehn -
Mark -
S Glasoe -
vince＠complex.elte.hu