Yesterday I did a Yast online update, which seemed to go uneventfully. However, it included a new version of the kernel, with the note that I should reboot the system after the install was completed. I did so but then (as I remember) walked away from the machine and left it running overnight without doing anything more. Today I came back to find that I had no network connection -- all addresses were unreachable. The little light next to the ethernet jack was on, and the lights on the hub to which the machine directly connects were also on. I tried (in Yast) uninstalling and reinstalling the network interface card; that had no effect. I can think of four possible causes for the failure: 1. The Ethernet hardware failed some time during the night. 2. There's a cabling problem (other machines on the net are working fine). 3. There's a software problem induced by the online update. 4. There's some other software problem. Any suggestions on how to go about diagnosing the failure? Paul Abrahams
On Saturday, 30 October 2004 06.08, Paul W. Abrahams wrote:
Today I came back to find that I had no network connection -- all addresses were unreachable. The little light next to the ethernet jack was on, and the lights on the hub to which the machine directly connects were also on. I tried (in Yast) uninstalling and reinstalling the network interface card; that had no effect. <snip> Any suggestions on how to go about diagnosing the failure?
first establish if you have an IP address (look at the output of ifconfig) and if you get a bunch of errors (also shown in the output of ifconfig) Then look at your routing table (route -n) and compare with the machines that work If the above checks out, try pinging an internal IP address and an external (try 195.135.220.3 for example, that's www.suse.de) If the above checks out, look at your name servers in /etc/resolv.conf and compare with the machines that work
I now have more info on the problem: disabling the on-board ethernet module and installing a separate card brought me my connection back. That would seem to indicate a hardware failure. But to verify or refute that, here's the beginning of what showed up in the system log: eth0: Transmit timed out, status 003, PHY status 786d, resetting IRQ 10: nobody cared! Can anyone interpret that? Am I dealing with a driver problem or a hardware problem? Just to clarify: ping localhost worked but pinging anything other than the host led to "network unreachable" errors. Paul
On Thursday 04 November 2004 00:48, Paul W. Abrahams wrote:
I now have more info on the problem: disabling the on-board ethernet module and installing a separate card brought me my connection back. That would seem to indicate a hardware failure. But to verify or refute that, here's the beginning of what showed up in the system log:
eth0: Transmit timed out, status 003, PHY status 786d, resetting IRQ 10: nobody cared!
Can anyone interpret that? Am I dealing with a driver problem or a hardware problem?
Just to clarify: ping localhost worked but pinging anything other than the host led to "network unreachable" errors.
Probably a driver problem. After switching NICs, did you change the driver module with YaST? I usually remove the existing device entirely, and start all over again, and let YaST figure out what module it needs. Cheers, Leen
On Wednesday 03 November 2004 8:10 pm, Leendert Meyer wrote:
Probably a driver problem. After switching NICs, did you change the driver module with YaST? I usually remove the existing device entirely, and start all over again, and let YaST figure out what module it needs.
I removed the Yast entry for the original NIC and allowed Yast to find the new NIC (they were of different types). But I had also tried removing the Yast entry for the original NIC before I had done the swap-out and letting Yast reconstruct it; that did not help. Paul
1. The Ethernet hardware failed some time during the night.
Try mii-tool or ethtool to check the hardware but I doubt that you have a hardware problem.
3. There's a software problem induced by the online update.
Try compiling the driver for your network card from source with the new kernel. Don't install it just rmmod the current one and insmod the one you compiled and see if your network is working. Brana
* Paul W. Abrahams <abrahams@acm.org> [10-29-04 23:09]:
Today I came back to find that I had no network connection -- all addresses were unreachable. The little light next to the ethernet jack was on, and the lights on the hub to which the machine directly connects were also on. I tried (in Yast) uninstalling and reinstalling the network interface card; that had no effect. ... Any suggestions on how to go about diagnosing the failure?
the *first* thing that I would try: rcnetwork start -- 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
participants (5)
-
Anders Johansson -
Branimir Vasilic -
Leendert Meyer -
Patrick Shanahan -
Paul W. Abrahams