Ethernet Connection Stopped Working

[embeehere]

I have a very peculiar problem. My ethernet stopped working after a normal system shutdown. I've tried to troubleshoot all hardware related issues and found that it is not hardware related (new cable, verified bios, booted into WinXP and works).

My /etc/network/interfaces contains\
auto lo
iface lo inet loopback
Under Network Management, I've set NetworkingEnabled=true
nm-tool says State: unavailable

As per thread http://ubuntuforums.org/showthread.php?t=2119493, I have tried all the stuff, including removing resolvconf, yet no luck.

When I re-boot, I see that the lights on my router port are green and at a certain point the lights go away and there is no wired connection.

I'm using 12.10 with 3.5.0-25 kernel. Can you please help?

[praseodym]

Hi,

please show

lspci -nnk | grep -iA2 net
cat /etc/resolv.conf
route -n
ifconfig -a

Does it work with an earlier kernel?

[embeehere]

I'm using 12.10 with 3.5.0-25 kernel. Can you please help?

Correction. I am using 12.04.

[embeehere]

Hi,

please show

lspci -nnk | grep -iA2 net
cat /etc/resolv.conf
route -n
ifconfig -a

Does it work with an earlier kernel?

Here it is:

lspci
00:19.0 Ethernet controller [0200]: Intel Corporation 82562V 10/100 Network Connection [8086:104c] (rev 02)
        Subsystem: Dell Device [1028:01dc]
        Kernel driver in use: e1000e

ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:76:cf:83:b6
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21 Memory:dffe0000-e0000000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:960 (960.0 B)  TX bytes:960 (960.0 B)

resolv.conf
# Generated by NetworkManager
nameserver 192.168.0.1

route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

[embeehere]

More info:

lshw -C network
  *-network
       description: Ethernet interface
       product: 82562V 10/100 Network Connection
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eth0
       version: 02
       serial: 00:16:76:cf:83:b6
       capacity: 100Mbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.0.0-k firmware=1.1-2 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:43 memory:dffe0000-dfffffff memory:dffdb000-dffdbfff ioport:ecc0(size=32)

/etc/network/interfaces
auto lo
iface lo inet loopback

[embeehere]

Any help? Any body please? I am clueless and stuck at this point.

[steeldriver]

Did your 'route -n' output get cut off when you pasted it, or is the routing table really empty?

Can you narrow down exactly where it's not working?

- can you ping your gateway / router by IP?
- can you ping an external host by IP?
- ... external host by name?
- etc.

If the interface itself is not coming up you may also get some diagnostic messages in dmesg

dmesg | grep eth0

[embeehere]

Did your 'route -n' output get cut off when you pasted it, or is the routing table really empty?

Can you narrow down exactly where it's not working?

- can you ping your gateway / router by IP?
- can you ping an external host by IP?
- ... external host by name?
- etc.

If the interface itself is not coming up you may also get some diagnostic messages in dmesg

dmesg | grep eth0

route -n is actually empty

The interface itself is not coming up. It seems like an Ethernet card does not exist on the system. So Cannot ping router/gateway; Cannot ping any external IP.

Here is the dmesg output.

[    2.862019] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:16:76:cf:83:b6
[    2.862025] e1000e 0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
[    2.862051] e1000e 0000:00:19.0: eth0: MAC: 6, PHY: 7, PBA No: 1021FF-0FF
[   20.300106] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.728514] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.728946] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[steeldriver]

Hmm... strange that it is jumping straight to IPv6 - I have an Intel wired card using e1000e on 12.04 in one of my laptops and what I see is

[   11.571790] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.388836] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   22.065060] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[   22.065297] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   32.608024] eth0: no IPv6 routers present

Is this a default wired connection or did you manually configure it via the Network Manager applet? What is the output of

nmcli dev list iface eth0

[embeehere]

This is the default wired connection. This has been working without any issues for about 4 years. Never did/had to configure anything via the NM applet.

Even today the card works on the same WinXP dual boot. What is puzzling is that the system underwent a normal shutdown. (We were expecting a power outage and our battery back-up is only for 30 mins). After about 24 hours, it was a normal boot and bingo - eth0 refuses to come alive.

sudo nmcli dev list iface eth0

GENERAL.DEVICE:                         eth0
GENERAL.TYPE:                           802-3-ethernet
GENERAL.VENDOR:                         Intel Corporation
GENERAL.PRODUCT:                        82562V 10/100 Network Connection
GENERAL.DRIVER:                         e1000e
GENERAL.DRIVER-VERSION:                 2.0.0-k
GENERAL.FIRMWARE-VERSION:               1.1-2
GENERAL.HWADDR:                         00:16:76:CF:83:B6
GENERAL.STATE:                          20 (unavailable)
GENERAL.REASON:                         2 (Device is now managed)
GENERAL.UDI:                            /sys/devices/pci0000:00/0000:00:19.0/net/eth0
GENERAL.IP-IFACE:                       
GENERAL.NM-MANAGED:                     yes
GENERAL.AUTOCONNECT:                    yes
GENERAL.FIRMWARE-MISSING:               no
GENERAL.CONNECTION:                     not connected
CAPABILITIES.CARRIER-DETECT:            yes
CAPABILITIES.SPEED:                     unknown
WIRED-PROPERTIES.CARRIER:               off

After seeing dmesg output, I went to the NM applet and selected the Wired Connection and in the IPv6 Settings tab, selected Method=Ignore. Still no luck.