[SLE] SuSE 9.2 and startup
From: P.M. Groen (p.m.groen_at_xs4all.nl)
Date: 11/29/04
- Previous message: Graham Smith: "Re: [SLE] Stiffy recovery tools"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Mon, 29 Nov 2004 14:25:46 +0100
Hi there,
I'm running 9.2 for a month now and no real problems... Except for one thing.
After boot, the network is not available while there are no errors during
boot. After issu'ing /etc/init.d/network restart the network is available.
When the script brings eth0 down, there is a line saying "eth0 does not
exist". When I run it the second time, there is the same message stating that
device lo doesn't exist..... Hm...
Like I said, no real problems, just some annoyance.
In the boot.msg there are lines:
<4>eth0: 3Com Gigabit LOM (3C940)
done eth0 device: 3Com Corporation 3c940 10/100/1000Base-T [Marvell]
(rev 12)
eth0 configuration: eth-id-00:0c:6e:60:c6:54
eth0 IP address: 192.168.0.4/24
and it looks like no problem. Except for the fact that it doesn't work
directly.
In /var/log/messages there are lines like:
Nov 29 11:04:18 quasar kernel: eth0: network connection up using port A
Nov 29 11:04:18 quasar kernel: speed: 100
Nov 29 11:04:18 quasar kernel: autonegotiation: yes
Nov 29 11:04:18 quasar kernel: duplex mode: full
Nov 29 11:04:18 quasar kernel: flowctrl: symmetric
Nov 29 11:04:18 quasar kernel: irq moderation: disabled
Nov 29 11:04:18 quasar kernel: scatter-gather: enabled
Nov 29 11:04:18 quasar kernel: rx-polling: enabled
And after the network restart:
Nov 29 11:17:35 quasar kernel: eth0: network connection down
Nov 29 11:17:37 quasar kernel: eth0: network connection up using port A
Nov 29 11:17:37 quasar kernel: speed: 100
Nov 29 11:17:37 quasar kernel: autonegotiation: yes
Nov 29 11:17:37 quasar kernel: duplex mode: full
Nov 29 11:17:37 quasar kernel: flowctrl: symmetric
Nov 29 11:17:37 quasar kernel: irq moderation: disabled
Nov 29 11:17:37 quasar kernel: scatter-gather: enabled
Nov 29 11:17:37 quasar kernel: rx-polling: enabled
I can't find any differences.
The Mainboard is a Asus P4P800 with an onboard Asustek (3C940 ) using the
sk98lin driver.
Regards,
Peter
-- 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
- Previous message: Graham Smith: "Re: [SLE] Stiffy recovery tools"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: How to trouble shoot eth0 FAILED?
... At this point ifplugd is trying to detect link status of eth0 and ... Ifplug
is fetching network setup info for your computer. ... That's the error message you see
at boot. ... (comp.os.linux) - Strange Network issues under FC2 SMP kernel
... Whenever I boot my computer with the 2.6.x.FC2smp kernel, my network ...
connections time out completely. ... eth0: transmit timed out, tx_status 00 status
e601. ... (Fedora) - Re: eth0 not starting on bootup
... > on boot is eth0. ... the eth0 interface is now no longer starting
when the ... might be here instead of or in addition to in network. ... (RedHat) - [opensuse] Re: 3C509 (EtherLink III) Not Started at Boot
... home network via an even older 3C509 NIC. ... boot and set up the card
manually to get it to start. ... ifdown eth0 ... (SuSE) - Re: iptables at boot
... Subject: iptables at boot ... > disabling all network activity
during the ... iface eth0 inet static ... (Debian-User)