Network start problems in 9.1
I just updated a solid 9.0 setup to 9.1 and am having a very odd problem. When I boot the system, I get the following errors in the boot log: Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: bus-pci-0000:02:01.0 eth-id-00:0c:f1:6d:25:31 20 19 18 17 16 14 12 11 10 9 8 7 6 5 4 3 2 1 0 bus-pci-0000:02:01.0 No interface found failed eth-id-00:0c:f1:6d:25:31 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7) If I go to YAST, the network device is all nicely setup. All I have to do is click Finish and everything works fine...until the next reboot when the process starts all over. The system is a vanilla Intel motherboard with a single builtin ethernet adapter (which makes the bus-pci and eth-id entries kind of odd). Any ideas? Thanks, mike.
Mike wrote:
I just updated a solid 9.0 setup to 9.1 and am having a very odd problem. When I boot the system, I get the following errors in the boot log:
Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: bus-pci-0000:02:01.0 eth-id-00:0c:f1:6d:25:31 20 19 18 17 16 14 12 11 10 9 8 7 6 5 4 3 2 1 0 bus-pci-0000:02:01.0 No interface found failed eth-id-00:0c:f1:6d:25:31 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7)
If I go to YAST, the network device is all nicely setup. All I have to do is click Finish and everything works fine...until the next reboot when the process starts all over.
The system is a vanilla Intel motherboard with a single builtin ethernet adapter (which makes the bus-pci and eth-id entries kind of odd).
Any ideas?
Thanks, mike.
Before going into YaST, check if the ethernet module is loaded. If not loaded try "rcnetwork restart". The bus-pci etc. entries are OK, see /etc/sysconfig/network/ifcfg-eth-id-00:0c:f1:6d:25:31, the 20-0 is the 20 second timeout value countdown for the interface to become active. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
Did you notice that there was an upgrade of that part of YAST last night !!! ;-) Johan Torsdag 20 maj 2004 06:31 skrev Sid Boyce:
Mike wrote:
I just updated a solid 9.0 setup to 9.1 and am having a very odd problem. When I boot the system, I get the following errors in the boot log:
Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: bus-pci-0000:02:01.0 eth-id-00:0c:f1:6d:25:31 20 19 18 17 16 14 12 11 10 9 8 7 6 5 4 3 2 1 0 bus-pci-0000:02:01.0 No interface found failed eth-id-00:0c:f1:6d:25:31 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7)
If I go to YAST, the network device is all nicely setup. All I have to do is click Finish and everything works fine...until the next reboot when the process starts all over.
The system is a vanilla Intel motherboard with a single builtin ethernet adapter (which makes the bus-pci and eth-id entries kind of odd).
Any ideas?
Thanks, mike.
Before going into YaST, check if the ethernet module is loaded. If not loaded try "rcnetwork restart". The bus-pci etc. entries are OK, see /etc/sysconfig/network/ifcfg-eth-id-00:0c:f1:6d:25:31, the 20-0 is the 20 second timeout value countdown for the interface to become active.
Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
On Thursday 20 May 2004 11:27, Johan wrote:
Did you notice that there was an upgrade of that part of YAST last night !!! ;-)
Thanks, Johan - sadly the upgrade doesn't fix my eth0 issues, which are near-identical problems to those Mike is having. I'd be interested to hear whether they fix Mike's difficulties. YaST doesn't seem to be able to set up an Etherlink III so that it is found at boot in 9.1. It would be nice if this were fixed. Since 9.1 is overtly aimed at the newcomer and convert from windows, an issue like this is liable to put them right off. I can find a workaround, but most non-technical people will just leave, and given they won't have any network connectivity they'll likely leave before even finding this list. Why was this working for so many versions and broken now? Best Fergus
Torsdag 20 maj 2004 06:31 skrev Sid Boyce:
Mike wrote:
I just updated a solid 9.0 setup to 9.1 and am having a very odd problem. When I boot the system, I get the following errors in the boot log:
Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: bus-pci-0000:02:01.0 eth-id-00:0c:f1:6d:25:31 20 19 18 17 16 14 12 11 10 9 8 7 6 5 4 3 2 1 0 bus-pci-0000:02:01.0 No interface found failed eth-id-00:0c:f1:6d:25:31 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7)
If I go to YAST, the network device is all nicely setup. All I have to do is click Finish and everything works fine...until the next reboot when the process starts all over.
The system is a vanilla Intel motherboard with a single builtin ethernet adapter (which makes the bus-pci and eth-id entries kind of odd).
Any ideas?
Thanks, mike.
Before going into YaST, check if the ethernet module is loaded. If not loaded try "rcnetwork restart". The bus-pci etc. entries are OK, see /etc/sysconfig/network/ifcfg-eth-id-00:0c:f1:6d:25:31, the 20-0 is the 20 second timeout value countdown for the interface to become active.
Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
-- 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
Fergus Wilde wrote:
On Thursday 20 May 2004 11:27, Johan wrote:
Did you notice that there was an upgrade of that part of YAST last night !!! ;-)
Thanks, Johan - sadly the upgrade doesn't fix my eth0 issues, which are near-identical problems to those Mike is having. I'd be interested to hear whether they fix Mike's difficulties. YaST doesn't seem to be able to set up an Etherlink III so that it is found at boot in 9.1.
It would be nice if this were fixed. Since 9.1 is overtly aimed at the newcomer and convert from windows, an issue like this is liable to put them right off. I can find a workaround, but most non-technical people will just leave, and given they won't have any network connectivity they'll likely leave before even finding this list. Why was this working for so many versions and broken now?
Best Fergus
I think 9.1 was rushed, also some pressure must have been felt putting together x86 and x86_64 versions. There are things that do not work or do not work properly, e.g the "grub-install" script does not point correctly to where the stage files are kept, it says /usr/lib whereas they are in /usr/lib/grub/i386-suse/ and /boot/grub/. On x86_64 I can't get linux32 to do what it's supposed to and some 64-bit apps don't build. I suppose these are teething problems that will be ironed out later. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
Torsdag 20 maj 2004 19:48 skrev Sid Boyce:
Fergus Wilde wrote:
On Thursday 20 May 2004 11:27, Johan wrote:
Did you notice that there was an upgrade of that part of YAST last night !!! ;-)
Thanks, Johan - sadly the upgrade doesn't fix my eth0 issues, which are near-identical problems to those Mike is having. I'd be interested to hear whether they fix Mike's difficulties. YaST doesn't seem to be able to set up an Etherlink III so that it is found at boot in 9.1.
It would be nice if this were fixed. Since 9.1 is overtly aimed at the newcomer and convert from windows, an issue like this is liable to put them right off. I can find a workaround, but most non-technical people will just leave, and given they won't have any network connectivity they'll likely leave before even finding this list. Why was this working for so many versions and broken now?
Best Fergus
I think 9.1 was rushed, also some pressure must have been felt putting together x86 and x86_64 versions. There are things that do not work or do not work properly, e.g the "grub-install" script does not point correctly to where the stage files are kept, it says /usr/lib whereas they are in /usr/lib/grub/i386-suse/ and /boot/grub/. On x86_64 I can't get linux32 to do what it's supposed to and some 64-bit apps don't build. I suppose these are teething problems that will be ironed out later. Regards Sid.
Yes .... I feel very tempted to spam feedback@suse.com /@suse.de in both languages. And just the size of the regular letter would conform to spam ..... I must say .... I'm >< this close to call it quits (at least I started to CC all my postings in here to feedback@suse.com) Johan
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
Mike wrote:
I just updated a solid 9.0 setup to 9.1 and am having a very odd problem. When I boot the system, I get the following errors in the boot log:
Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: bus-pci-0000:02:01.0 eth-id-00:0c:f1:6d:25:31 20 19 18 17 16 14 12 11 10 9 8 7 6 5 4 3 2 1 0 bus-pci-0000:02:01.0 No interface found failed eth-id-00:0c:f1:6d:25:31 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed <notice>exit status of (network) is (7)
If I go to YAST, the network device is all nicely setup. All I have to do is click Finish and everything works fine...until the next reboot when the process starts all over.
The system is a vanilla Intel motherboard with a single builtin ethernet adapter (which makes the bus-pci and eth-id entries kind of odd).
Any ideas?
Thanks, mike.
I had this problem 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.
participants (5)
-
Fergus Wilde -
Johan -
Mark Knudson -
Mike -
Sid Boyce