Wired connection stopped working on Dell D620, help :(
 

I'm not currently able to connect through to my wired connection (though I was able to yesterday) but am able to just fine wirelessly, not sure what happened?

I get a light when the ethernet cable is attached & others can connect through the same cable just fine. When I go through Network Manger to try to edit the eth0 settings & click apply, I can see that it tries to negotiate a connection but after some time just fails.

lspci:
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 01)

interfaces;
auto lo
iface lo inet loopback

dhclient eth0;
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:15:c5:50:c7:86
Sending on LPF/eth0/00:15:c5:50:c7:86
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



I'm on a Dell D620 running the latest Karmic Koala release;
Linux dell-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux


Any help that would get me connected would be appreciated.

Is the router setup for dhcp ?

Yes, it was working fine yesterday & everyone else seems to be able to connect through the same connection. Just not this laptop :(

Yes, but when you tried to get IP from router DHCP, can others did the came?

What is LAN address of the router?

Post please output for:
ifconfig

Thanks.

Weird, doesn't show my eth0 now?

eth1 Link encap:Ethernet HWaddr 00:16:cf:61:81:ec
inet addr:10.92.0.127 Bcast:10.92.3.255 Mask:255.255.252.0
inet6 addr: fe80::216:cfff:fe61:81ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1121 errors:0 dropped:0 overruns:0 frame:1889
TX packets:1210 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:752958 (752.9 KB) TX bytes:284501 (284.5 KB)
Interrupt:17 Base address:0xc000

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:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1616 (1.6 KB) TX bytes:1616 (1.6 KB)


And if I try to bring it up;

sudo ifconfig eth0 up
eth0: ERROR while getting interface flags: No such device


What gives?

How about to reboot comp.?

After reboot, here is my ifconfig output

eth0 Link encap:Ethernet HWaddr 00:15:c5:50:c7:86
inet6 addr: fe80::215:c5ff:fe50:c786/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1362 errors:0 dropped:2304 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:115700 (115.7 KB) TX bytes:0 (0.0 B)
Interrupt:18

eth1 Link encap:Ethernet HWaddr 00:16:cf:61:81:ec
inet addr:10.92.0.127 Bcast:10.92.3.255 Mask:255.255.252.0
inet6 addr: fe80::216:cfff:fe61:81ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7839 errors:0 dropped:0 overruns:0 frame:7327
TX packets:7457 errors:32 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7433096 (7.4 MB) TX bytes:1305876 (1.3 MB)
Interrupt:17 Base address:0xc000

eth0:avahi Link encap:Ethernet HWaddr 00:15:c5:50:c7:86
inet addr:169.254.9.74 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:18

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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)


Now it reads WIRED NETWORK device not managed

Where did it come from: device not managed?

Looks like I discovered some strange Bug with this latest Kernel version, 2.6.31-14. When I revert back to previous Kernel, 2.6.28-16, I can connect through the wired network just fine :)