About eight months ago I installed SuSE 9.0 Pro on a friend's XP machine on a newly added hard drive as dual boot, with linux default. My friend is *not* what you would call computer literate. I directed him to some beginning linux courses on the web and gave him my 9.0 manuals to read/referrrence. He has slowly become about 75 per cent linux user, booting windoz only for streaming media that we cannot seem to make work in linux. A couple of days ago, he booted windoz for an hour and returned to linux to find that he could not access the net. Previous he had had no problems accessing his cable connection thru a router. I ran ifconfig and it only showed lo, so I ran 'rcnetwork start' and ifconfig showed lo and eth0. Access to the net was restored. I ran yast2 to check that network was enabled in runlevels 2,3,5. It was. Rebooted to see if the network would start normally and again, the network did not start. rcnetwork start restored net access. Knoppix and the SuSE 9.2 Live CD both provide net access w/o user intervention. I do not know what else to check, suggestions welcome. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Wed, Oct 27, 2004 at 07:48:02PM -0500, Patrick Shanahan wrote:
Rebooted to see if the network would start normally and again, the network did not start. rcnetwork start restored net access.
Knoppix and the SuSE 9.2 Live CD both provide net access w/o user intervention. I do not know what else to check, suggestions welcome.
Please look in /var/log/boot.msg. There should be a piece there like the following: <notice>start services (network) Setting up network interfaces: lo done ... <notice>exit status of (network) is (0) If there were any errors, they should have been reported there. Regards, -Kastus
* Kastus
Please look in /var/log/boot.msg. There should be a piece there like the following:
<notice>start services (network) Setting up network interfaces: lo done ...
<notice>exit status of (network) is (0)
Yes, we looked there and /var/log/messages and exit status was '0'. No errors apparent. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Wed, Oct 27, 2004 at 10:00:36PM -0500, Patrick Shanahan wrote:
Yes, we looked there and /var/log/messages and exit status was '0'. No errors apparent.
But did it actually say anything about ethernet interfaces in boot.msg? I checked once again on 9.0 machine, and boot.msg has these lines: Setting up network interfaces: lo done eth0 IP/Netmask: 172.21.1.31 / 255.255.0.0 eth1 IP/Netmask: 172.21.1.32 / 255.255.0.0 Regards, -Kastus
* Kastus
But did it actually say anything about ethernet interfaces in boot.msg?
yes, below
I checked once again on 9.0 machine, and boot.msg has these lines:
Setting up network interfaces: lo done eth0 IP/Netmask: 172.21.1.31 / 255.255.0.0 eth1 IP/Netmask: 172.21.1.32 / 255.255.0.0
<notice>start services (network) Setting up network interfaces: lo done eth0 failed <notice>exit status of (network) is (0) <notice>start services (syslog) there is a router between the box and cable where DHCP is. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
<notice>start services (network) Setting up network interfaces: lo done eth0 failed <notice>exit status of (network) is (0) <notice>start services (syslog)
there is a router between the box and cable where DHCP is.
Is this a laptop by chance? I've seen a similar issue when a laptop tries to initialize the NIC before PCMCIA services have been loaded by the kernel. Do you have access to the DHCP server logs? Is DHCP configured correctly? Jeff
* Jeffrey Laramie
Is this a laptop by chance?
no
I've seen a similar issue when a laptop tries to initialize the NIC before PCMCIA services have been loaded by the kernel.
Do you have access to the DHCP server logs? Is DHCP configured correctly?
performed at the router (automagic), no logs afaik. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Thursday 28 October 2004 09:32, Patrick Shanahan wrote:
* Jeffrey Laramie
[10-28-04 08:29]: Is this a laptop by chance?
no
I've seen a similar issue when a laptop tries to initialize the NIC before PCMCIA services have been loaded by the kernel.
Do you have access to the DHCP server logs? Is DHCP configured correctly?
performed at the router (automagic), no logs afaik.
/etc/sysconfig/network/ifcfg-eth0 STARTMODE='onboot' ? Jeff
* Jeffrey Laramie
/etc/sysconfig/network/ifcfg-eth0 STARTMODE='onboot' ?
yes, 'onboot' -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Thursday 28 October 2004 12:12, Patrick Shanahan wrote:
* Jeffrey Laramie
[10-28-04 08:46]: /etc/sysconfig/network/ifcfg-eth0 STARTMODE='onboot' ?
yes, 'onboot'
I'm out of ideas, sorry. Hopefully Leen or the others can help you track it down. Jeff
On Thursday 28 October 2004 12:12, Patrick Shanahan wrote:
* Jeffrey Laramie
[10-28-04 08:46]: /etc/sysconfig/network/ifcfg-eth0 STARTMODE='onboot' ?
yes, 'onboot'
I'm out of ideas, sorry. Hopefully Leen or the others can help you track it down.
Jeff
On Thursday 28 October 2004 18:32, Jeffrey Laramie wrote: try chkconfig network on -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
* Chadley Wilson
try chkconfig network on
it is set to 'on'. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan wrote:
About eight months ago I installed SuSE 9.0 Pro on a friend's XP machine on a newly added hard drive as dual boot, with linux default. My friend is *not* what you would call computer literate. I directed him to some beginning linux courses on the web and gave him my 9.0 manuals to read/referrrence. He has slowly become about 75 per cent linux user, booting windoz only for streaming media that we cannot seem to make work in linux.
A couple of days ago, he booted windoz for an hour and returned to linux to find that he could not access the net. Previous he had had no problems accessing his cable connection thru a router.
I ran ifconfig and it only showed lo, so I ran 'rcnetwork start' and ifconfig showed lo and eth0. Access to the net was restored.
I ran yast2 to check that network was enabled in runlevels 2,3,5. It was.
Rebooted to see if the network would start normally and again, the network did not start. rcnetwork start restored net access.
Knoppix and the SuSE 9.2 Live CD both provide net access w/o user intervention. I do not know what else to check, suggestions welcome.
Anything in /var/log/boot.msg or dmesg? chkconfig network Network module not loading? Is it still working in Windows? I had some problems here a few days ago where the on-board ethernets were reported as "not yet up" during boot, I could get eth0 up later, but eth1 didn't work. I eventually found eth1 on-board was bad, put in a RealTek PCI ethernet card and it came up as eth1 in place of the bad one. YaST2 configures the bad one as eth2 now, cable is good, but it doesnt work. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
* Sid Boyce
Anything in /var/log/boot.msg or dmesg?
exit status '0', no errors noted.
chkconfig network
yast reports network enabled for 2,3,5
Network module not loading?
must be loading as I can 'rcnetwork start' and reach the net.
Is it still working in Windows?
yes and knoppix and SuSE 9.2 Live-eval.
I had some problems here a few days ago where the on-board ethernets were reported as "not yet up" during boot, I could get eth0 up later, but eth1 didn't work. I eventually found eth1 on-board was bad, put in a RealTek PCI ethernet card and it came up as eth1 in place of the bad one. YaST2 configures the bad one as eth2 now, cable is good, but it doesnt work.
Plugin card, no on-board. Appears to be working fine, re: other system boots and 'rcnetwork start' work. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan wrote:
<snip>
Plugin card, no on-board. Appears to be working fine, re: other system boots and 'rcnetwork start' work.
Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast? I assume you've set the IP address manually? Not that it should mysteriously change on you, but... -- DC Parris http://matheteuo.org/ http://chaddb.sourceforge.net/ "Free software is like God's love - you can share it with anyone anytime anywhere."
* Don Parris
Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast?
yes
I assume you've set the IP address manually?
no, obtained automagically.
Not that it should mysteriously change on you, but...
note: there is a router between box and cable router. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan wrote:
* Don Parris
[10-27-04 23:04]: Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast?
yes
I assume you've set the IP address manually?
no, obtained automagically.
Not that it should mysteriously change on you, but...
note: there is a router between box and cable router.
Could it be a timeout problem?. /etc/sysconfig/network/dhcp # (only dhcpcd does use this setting) # # You can set the timeout (dhcpcd will terminate after this time when it # does not get a reply from the server). # # The default timeout of dhcpcd is 60 seconds. However, we'll set it to a # much longer time. dhcpcd will then run as a daemon in the background and # broadcast a DHCPDISCOVER once in a while, trying to get a lease. # DHCLIENT_TIMEOUT="999999" Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
Sid Boyce wrote:
# The default timeout of dhcpcd is 60 seconds. However, we'll set it to a # much longer time. dhcpcd will then run as a daemon in the background and # broadcast a DHCPDISCOVER once in a while, trying to get a lease. # DHCLIENT_TIMEOUT="999999"
I thought the default value for dameons was 666. ;-)
On Thursday 28 October 2004 14:56, Patrick Shanahan wrote:
* Don Parris
[10-27-04 23:04]: Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast?
yes
I assume you've set the IP address manually?
no, obtained automagically.
Not that it should mysteriously change on you, but...
note: there is a router between box and cable router.
Let's see if we can get more info. I'm on 9.2 right now (this was about 9.0, right?), but I think this has not changed: In /etc/sysconfig/network/config, set the variable 'DEBUG' to 'yes', and report any error messages. Cheers, Leen
On Thursday 28 October 2004 17:29, Leendert Meyer wrote:
On Thursday 28 October 2004 14:56, Patrick Shanahan wrote:
* Don Parris
[10-27-04 23:04]: Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast?
yes
I assume you've set the IP address manually?
no, obtained automagically.
Not that it should mysteriously change on you, but...
note: there is a router between box and cable router.
Let's see if we can get more info. I'm on 9.2 right now (this was about 9.0, right?), but I think this has not changed:
In /etc/sysconfig/network/config, set the variable 'DEBUG' to 'yes', and report any error messages.
Here's another one you could try: In /etc/sysconfig/network/dhcp, set the variable 'DHCLIENT_DEBUG' to 'yes'. In the comment above that declaration is mentioned where the logfile is stored. Also you might want to install the package dhcp-tools, and run the script below like: dhcp-dump eth0 ----[dhcp-dump]---- #! /bin/bash DEV=${1:-eth0} tcpdump -i $DEV -lenx -s 1500 port bootps or port bootpc | dhcpdump ----[dhcp-dump]---- I did have problems in the past, when I frequently booted between 2 OS'es. The point was that the DHCP-lease was not released, so OS1 would request a lease while the DHCP-server thought that OS1 already had a lease, but actually OS2 had the lease. The solution was to release the lease if the network goes down (DHCLIENT_RELEASE_BEFORE_QUIT="yes"). Cheers, Leen
* Leendert Meyer
Let's see if we can get more info. I'm on 9.2 right now (this was about 9.0, right?), but I think this has not changed:
In /etc/sysconfig/network/config, set the variable 'DEBUG' to 'yes', and report any error messages.
good idea, results (boot.mst): S05network [DEBUG] (returned 0)done eth0 ifup [DEBUG] eth0 -o onboot rc ifup [DEBUG] HWDESC = eth0 CONFIG = eth0 INTERFACE = nointerface ifup [DEBUG] Could not get a valid interface name: -> skipped S05network [DEBUG] (returned 7)failed ifup-route [DEBUG] noiface -o onboot rc ifup-route [DEBUG] unknown option rc ignored <notice>exit status of (network) is (0) -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 29 October 2004 03:06, Patrick Shanahan wrote:
* Leendert Meyer
[10-28-04 10:33]: Let's see if we can get more info. I'm on 9.2 right now (this was about 9.0, right?), but I think this has not changed:
In /etc/sysconfig/network/config, set the variable 'DEBUG' to 'yes', and report any error messages.
good idea, results (boot.mst):
S05network [DEBUG] (returned 0)done eth0 ifup [DEBUG] eth0 -o onboot rc ifup [DEBUG] HWDESC = eth0 CONFIG = eth0 INTERFACE = nointerface ifup [DEBUG] Could not get a valid interface name: -> skipped
I did read through 9.0's ifup script, it seems to be a hardware issue: either something with the interface's kernel-module, or the hardware itself. As Knoppix and others work well, I think the hardware is ok. How about the related kernel-module? - Was the kernel updated recently? - What is the related kernel-module? - Anything in /var/log/{messages,warn}? Idea: put a modprobe <kernel-module> in /etc/init.d/boot.local, perhaps followed by a sleep 5 or so to allow the card to settle down. If the kernel-module supports an argument to generate (debugging-) info, enable that.
S05network [DEBUG] (returned 7)failed ifup-route [DEBUG] noiface -o onboot rc ifup-route [DEBUG] unknown option rc ignored
This is not an error - let's disregard it.
<notice>exit status of (network) is (0)
Cheers, Leen
* Leendert Meyer
[10-28-04 10:33]: Let's see if we can get more info. I'm on 9.2 right now (this was about 9.0, right?), but I think this has not changed:
In /etc/sysconfig/network/config, set the variable 'DEBUG' to 'yes', and report any error messages.
good idea, results (boot.mst):
S05network [DEBUG] (returned 0)done eth0 ifup [DEBUG] eth0 -o onboot rc ifup [DEBUG] HWDESC = eth0 CONFIG = eth0 INTERFACE = nointerface [snip] Shouldn't the INTERFACE value show what interface is being used? Perhaps
Patrick Shanahan wrote: the PCMCIA card/modem/interface has gone bottoms up?
ifup [DEBUG] Could not get a valid interface name: -> skipped The fact that the valid interface name was skilled to me says that it couldn't talk to the interface.
S05network [DEBUG] (returned 7)failed ifup-route [DEBUG] noiface -o onboot rc ifup-route [DEBUG] unknown option rc ignored <notice>exit status of (network) is (0) Perhaps there is nothing wrong with the network setup, just the hardware, be it the interface or the interface receptacle, if PCMCIA.
-- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
The Thursday 2004-10-28 at 20:06 -0500, Patrick Shanahan wrote:
eth0 ifup [DEBUG] eth0 -o onboot rc ifup [DEBUG] HWDESC = eth0 CONFIG = eth0 INTERFACE = nointerface ifup [DEBUG] Could not get a valid interface name: -> skipped
I was reading briefly about network things in suse 9.1, and I think I remember that it said that now the eth0, that is, the interface, must be up by the time this script runs. Can't remember where I read that, though. Did you look at the kernel log (/var/log/kernel)? -- Cheers, Carlos Robinson
* Carlos E. R.
I was reading briefly about network things in suse 9.1, and I think I remember that it said that now the eth0, that is, the interface, must be up by the time this script runs. Can't remember where I read that, though.
Did you look at the kernel log (/var/log/kernel)?
no such animal on 9.0 (/var/log/kernel). :^{ -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
The Sunday 2004-10-31 at 22:03 -0500, Patrick Shanahan wrote:
Did you look at the kernel log (/var/log/kernel)?
no such animal on 9.0 (/var/log/kernel). :^{
Then enable it. In '/etc/syslog.conf': kern.* -/var/log/kernel Then, 'rcsyslog restart'. With some kernel problems, this log can grow megabytes per minute, but that's not usual. I keep it active always. -- Cheers, Carlos Robinson
Patrick Shanahan wrote:
* Don Parris
[10-27-04 23:04]: Just out of curiosity, since you haven't stated so explicitly, did you double check the NIC's configuration in Yast?
yes
I assume you've set the IP address manually?
no, obtained automagically.
Not that it should mysteriously change on you, but...
note: there is a router between box and cable router. Is there perhaps anything in the logs of the router on assigning the DHCP?
-- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
Patrick Shanahan wrote:
About eight months ago I installed SuSE 9.0 Pro on a friend's XP machine on a newly added hard drive as dual boot, with linux default. My friend is *not* what you would call computer literate. I directed him to some beginning linux courses on the web and gave him my 9.0 manuals to read/referrrence. He has slowly become about 75 per cent linux user, booting windoz only for streaming media that we cannot seem to make work in linux.
A couple of days ago, he booted windoz for an hour and returned to linux to find that he could not access the net. Previous he had had no problems accessing his cable connection thru a router.
I ran ifconfig and it only showed lo, so I ran 'rcnetwork start' and ifconfig showed lo and eth0. Access to the net was restored.
I ran yast2 to check that network was enabled in runlevels 2,3,5. It was.
Rebooted to see if the network would start normally and again, the network did not start. rcnetwork start restored net access.
Knoppix and the SuSE 9.2 Live CD both provide net access w/o user intervention. I do not know what else to check, suggestions welcome. Why just start it. I would rather stop it, and then start it.
Seems the network files have become corrupted and finding the corruption could take a while. Whilst most of the settings are stored in text files perhaps an RPM upgrade from the RPM holding kdenetwork* would rectify the problem? See the man pages for upgrading rpms :) I'd certainly be interested to find what fices your problem, and what file was edited, if required. The other alternative is to use CLI and check the settings in all the network files, as perhaps one of them has changed 'by itself'. -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
participants (10)
-
Carlos E. R.
-
Chadley Wilson
-
Don Parris
-
Hylton Conacher (ZR1HPC)
-
James Knott
-
Jeffrey Laramie
-
Kastus
-
Leendert Meyer
-
Patrick Shanahan
-
Sid Boyce