9.1 unable to find ethernet card at boot
Apologies for a second post on this theme, because it's critical and will require the machine to be reverted to an earlier version (all of which worked) if unsolved. I'm hoping a few more people have 9.1 on by now. I've never backed out a new SuSE version, and am not anxious to have to start now, so if anyone has a clue ... The machine, all hardware unchanged for many years and ultra-reliable, cannot find its Etherlink III card at boot after 9.1 install, here's part of /var/ log/boot.msg: Initializing random number generatordone <notice>exit status of (random isdn hotplug) is (0 0 0) <notice>start services (coldplug) coldplug scanning input: done scanning pci: ***.**Wdone scanning usb: done . . . . . . . . . . . . . . . . . . . . . . . .done <notice>exit status of (coldplug) is (0) <notice>start services (network) Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:50:da:3c:65:34 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 2 1 0 eth-id-00:50:da:3c:65:34 No interface found failed Setting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) <notice>start services (syslog) Ifconfig of course can't see the card, and I can only get a network back by going into YaST and opening the network devices section, where the card is correctly described and configured. This alone, not changing anything, is enough to bring eth0 up. My question is essentially what has changed in this version of SuSE to break things, and how can they be fixed? -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Thursday 13 May 2004 06:14 am, Fergus Wilde wrote:
Apologies for a second post on this theme, because it's critical and will require the machine to be reverted to an earlier version (all of which worked) if unsolved. I'm hoping a few more people have 9.1 on by now. I've never backed out a new SuSE version, and am not anxious to have to start now, so if anyone has a clue ...
The machine, all hardware unchanged for many years and ultra-reliable, cannot find its Etherlink III card at boot after 9.1 install, here's part of /var/ log/boot.msg:
Initializing random number generatordone <notice>exit status of (random isdn hotplug) is (0 0 0) <notice>start services (coldplug) coldplug scanning input: done scanning pci: ***.**Wdone scanning usb: done . . . . . . . . . . . . . . . . . . . . . . . .done <notice>exit status of (coldplug) is (0) <notice>start services (network) Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:50:da:3c:65:34 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 2 1 0 eth-id-00:50:da:3c:65:34 No interface found failed Setting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) <notice>start services (syslog)
Ifconfig of course can't see the card, and I can only get a network back by going into YaST and opening the network devices section, where the card is correctly described and configured. This alone, not changing anything, is enough to bring eth0 up.
My question is essentially what has changed in this version of SuSE to break things, and how can they be fixed?
Have you looked to see what modules are included in /boot/initrd? Look in /etc/sysconfig/kernel under INITRD_MODULES. If the module for your card isn't included in that line, add it in. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/13/04 07:14 + +----------------------------------------------------------------------------+ 'Doo onto others before they doo onto you.' Big Bird
Try Checking lsmod before and after yast2 to see if a module is not being loaded? Jerry On Thu, 2004-05-13 at 12:14, Fergus Wilde wrote:
Apologies for a second post on this theme, because it's critical and will require the machine to be reverted to an earlier version (all of which worked) if unsolved. I'm hoping a few more people have 9.1 on by now. I've never backed out a new SuSE version, and am not anxious to have to start now, so if anyone has a clue ...
The machine, all hardware unchanged for many years and ultra-reliable, cannot find its Etherlink III card at boot after 9.1 install, here's part of /var/ log/boot.msg:
Initializing random number generatordone <notice>exit status of (random isdn hotplug) is (0 0 0) <notice>start services (coldplug) coldplug scanning input: done scanning pci: ***.**Wdone scanning usb: done . . . . . . . . . . . . . . . . . . . . . . . .done <notice>exit status of (coldplug) is (0) <notice>start services (network) Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:50:da:3c:65:34 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 2 1 0 eth-id-00:50:da:3c:65:34 No interface found failed Setting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) <notice>start services (syslog)
Ifconfig of course can't see the card, and I can only get a network back by going into YaST and opening the network devices section, where the card is correctly described and configured. This alone, not changing anything, is enough to bring eth0 up.
My question is essentially what has changed in this version of SuSE to break things, and how can they be fixed?
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
What happens if you force load the module? i.e. modprobe modulename? -----Original Message----- From: Jerome R. Westrick [mailto:jerry@Westrick.com] Sent: Thursday, May 13, 2004 12:20 PM To: Suse Users Subject: Re: [SLE] 9.1 unable to find ethernet card at boot Try Checking lsmod before and after yast2 to see if a module is not being loaded? Jerry On Thu, 2004-05-13 at 12:14, Fergus Wilde wrote:
Apologies for a second post on this theme, because it's critical and will require the machine to be reverted to an earlier version (all of which
worked) if unsolved. I'm hoping a few more people have 9.1 on by now. I've never backed out a new SuSE version, and am not anxious to have to start now, so if anyone has a clue ...
The machine, all hardware unchanged for many years and ultra-reliable, cannot find its Etherlink III card at boot after 9.1 install, here's part of /var/ log/boot.msg:
Initializing random number generatordone <notice>exit status of (random isdn hotplug) is (0 0 0) <notice>start services (coldplug) coldplug scanning input: done scanning pci: ***.**Wdone scanning usb: done . . . . . . . . . . . . . . . . . . . . . . . .done <notice>exit status of (coldplug) is (0) <notice>start services (network) Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:50:da:3c:65:34 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 2 1 0 eth-id-00:50:da:3c:65:34 No interface found failed Setting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) <notice>start services (syslog)
Ifconfig of course can't see the card, and I can only get a network back by going into YaST and opening the network devices section, where the card is correctly described and configured. This alone, not changing anything, is enough to bring eth0 up.
My question is essentially what has changed in this version of SuSE to break things, and how can they be fixed?
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi, I've several machines that were running Suse 9.0 with Intel network cards which use the E100 module. Normally I add 'options e100 e100_speed_duplex=4' to '/etc/modules.conf' to force the card to 100Mb/s Full Duplex. I upgraded my 9.0 machines to the beta version of the 2.6 Kernel and moved the above line to '/etc/modprobe.conf' as the above file is no longer used which still worked. However after upgrading the machines to Suse 9.1 I no longer have this option, typing 'lsmod e100' reveals no available options for setting the speed and duplex. This is frustrating as I run an online games service where low latency is critical, my Cisco switches are set to 100Mb/s Full Duplex but if I leave the cards on auto they always set themselves to Half Duplex and everything runs like a dog. mii-tool doesn't work with the e100 module so I can't use that. Does anyone know of a work around or should I drop back to 9.0 and the beta which worked without problems, however the CPU load is lower on 9.1 so I'd rather keep this if possible? Can you use a 2.6 beta module with 9.1? Thanks in advance. Matthew
On Thursday 13 May 2004 21.14, Matthew Stringer wrote:
mii-tool doesn't work with the e100 module so I can't use that.
The source claims that it's mii compatible?! What happens when you try Incidentally, did you try the e100-intel module? It claims to support the same cards, and it has the e100_speed_duplex parameter
I'll try that driver. mii-tool gives me this: gs12:~ # mii-tool SIOCGMIIPHY on 'eth0' failed: Operation not supported no MII interfaces found Cheers Matthew -----Original Message----- From: Anders Johansson [mailto:andjoh@rydsbo.net] Sent: Thursday, May 13, 2004 8:42 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Forcing 100Mb/s Full Duplex in 9.1 On Thursday 13 May 2004 21.14, Matthew Stringer wrote:
mii-tool doesn't work with the e100 module so I can't use that.
The source claims that it's mii compatible?! What happens when you try Incidentally, did you try the e100-intel module? It claims to support the same cards, and it has the e100_speed_duplex parameter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"man ethtool" if it has not been tried. duplex half|full Set full or half duplex mode. Regards Sid. Matthew Stringer wrote:
I'll try that driver.
mii-tool gives me this:
gs12:~ # mii-tool SIOCGMIIPHY on 'eth0' failed: Operation not supported no MII interfaces found
Cheers
Matthew
-----Original Message----- From: Anders Johansson [mailto:andjoh@rydsbo.net] Sent: Thursday, May 13, 2004 8:42 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Forcing 100Mb/s Full Duplex in 9.1
On Thursday 13 May 2004 21.14, Matthew Stringer wrote:
mii-tool doesn't work with the e100 module so I can't use that.
The source claims that it's mii compatible?! What happens when you try
Incidentally, did you try the e100-intel module? It claims to support the same cards, and it has the e100_speed_duplex parameter
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
On Thursday 13 May 2004 11:14, Fergus Wilde wrote:
Apologies for a second post on this theme, because it's critical and will require the machine to be reverted to an earlier version (all of which worked) if unsolved. I'm hoping a few more people have 9.1 on by now. I've never backed out a new SuSE version, and am not anxious to have to start now, so if anyone has a clue ...
The machine, all hardware unchanged for many years and ultra-reliable, cannot find its Etherlink III card at boot after 9.1 install, here's part of /var/ log/boot.msg:
Initializing random number generatordone <notice>exit status of (random isdn hotplug) is (0 0 0) <notice>start services (coldplug) coldplug scanning input: done scanning pci: ***.**Wdone scanning usb: done . . . . . . . . . . . . . . . . . . . . . . . .done <notice>exit status of (coldplug) is (0) <notice>start services (network) Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:50:da:3c:65:34 19 18 17 16 15 14 13 11 10 9 8 7 6 5 4 2 1 0 eth-id-00:50:da:3c:65:34 No interface found failed Setting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) <notice>start services (syslog)
Ifconfig of course can't see the card, and I can only get a network back by going into YaST and opening the network devices section, where the card is correctly described and configured. This alone, not changing anything, is enough to bring eth0 up.
My question is essentially what has changed in this version of SuSE to break things, and how can they be fixed?
Thanks to Bruce Marshall and Jerry Westrick for pointing out that the module (in this case 3c509) for the network card had probably been omitted from the mkinitrd process and thus from the initial ramdisk. As Bruce said that means going to /etc/sysconfig/kernel, and editing thus: ## Path: System/Kernel ## Description: Modules to load from initrd ## Type: string ## Command: /sbin/mkinitrd # # This variable contains the list of modules to be added to the initial # ramdisk by calling the script "mk_initrd" # (like drivers for scsi-controllers, for lvm or reiserfs) # INITRD_MODULES="reiserfs 3c509" ^^^^^^ ## Path: System/Kernel ## Description: Modules to load after initial boot ## Type: string ## ServiceRestart: boot.loadmodules # # This variable contains the list of modules to be loaded # once the main filesystem is active ... <etc> So that your network card is in the INITRD_MODULES section. Don't know why the install didn't get it in there, but now I can do remote boots I'm a happy bunny on that score. Best Fergus
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Thursday 13 May 2004 14.57, Fergus Wilde wrote:
So that your network card is in the INITRD_MODULES section. Don't know why the install didn't get it in there
Perhaps because it's not supposed to be in there (unless by some chance your root partition is accessed over a network link). It only consumes needless disk space. The proper solution is to set up /etc/modprobe.conf so the module loader can find the right module
On Thu, 2004-05-13 at 14:57, Fergus Wilde wrote:
Thanks to Bruce Marshall and Jerry Westrick for pointing out that the module (in this case 3c509) for the network card had probably been omitted from the mkinitrd process and thus from the initial ramdisk.
<snip>
So that your network card is in the INITRD_MODULES section. Don't know why the install didn't get it in there, but now I can do remote boots I'm a happy bunny on that score. <snip>
I wonder if you loaded the network driver before starting the install? I sometime do this when I want to do a network install, haven't tried it yet on 9.1, but this problem didn't apper on 9.0... 9.1 has the new F-Key for network install, did you use that? Jerry
On Thursday 13 May 2004 14:33, Jerome R. Westrick wrote:
On Thu, 2004-05-13 at 14:57, Fergus Wilde wrote:
Thanks to Bruce Marshall and Jerry Westrick for pointing out that the module (in this case 3c509) for the network card had probably been omitted from the mkinitrd process and thus from the initial ramdisk. <snip>
So that your network card is in the INITRD_MODULES section. Don't know why the install didn't get it in there, but now I can do remote boots I'm a happy bunny on that score.
<snip>
I wonder if you loaded the network driver before starting the install? I sometime do this when I want to do a network install, haven't tried it yet on 9.1, but this problem didn't apper on 9.0...
No, it was a CD install, all perfectly normal. I don't remember this matter needing any intervention before - but now Anders has made his point about the modules.conf, I will look at that and see what it says ... Thanks Fergus
9.1 has the new F-Key for network install, did you use that?
Jerry
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Thursday 13 May 2004 15.42, Fergus Wilde wrote:
but now Anders has made his point about the modules.conf
No, modprobe.conf is the kernel 2.6 name of it. That, and in the included files modprobe.conf.local and /etc/modprobe.d/*, is where the module config is to be found now. I had a problem where the tulip driver claimed my NIC so the (proper) dmfe driver couldn't get it. Of course the tulip driver then proceeded to completely fail to drive the NIC.
participants (6)
-
Anders Johansson -
Bruce Marshall -
Fergus Wilde -
Jerome R. Westrick -
Matthew Stringer -
Sid Boyce