Ubuntu 9.10 : Intel 82566MM chip seen but not active

[R4v3n]

I just updated my ubuntu 9.04 (thinkpad X61t) to Ubuntu 9.10, and I got a problem with the network chip.
lspci show the card :
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)

So I plugged my network cable (with dhcp on network) and nothing append. ifconfig said I got any IP.
If I clic on the network-manager icon in the gnome panel, I just see for eth0 "deconnect" in gray.
If I give a fixed IP via the network-manager in "Auto eth0", nothing append, and after a reboot, the network-manager icon has disappeared.

Right now, I can get the internet only with my wireless connection, and can do anything with my wired network, that's a big problem.

If you need anything more, just ask for ! :)

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: raven 2803 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8220000 irq 17'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20dd,00100400'
   Controls : 29
   Simple ctrls : 18
Date: Sun Oct 25 18:26:40 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=048c2549-d30f-46b7-a171-8a0238c4e02e
MachineType: LENOVO 776295G
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=eed3eb2b-be2a-43a0-9649-9723b53d8355 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkey reporting is always enabled
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 11/27/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET36WW (1.22 )
dmi.board.name: 776295G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7SET36WW(1.22):bd11/27/2008:svnLENOVO:pn776295G:pvrThinkPadX61Tablet:rvnLENOVO:rn776295G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 776295G
dmi.product.version: ThinkPad X61 Tablet
dmi.sys.vendor: LENOVO

[Christoffer Kjølbæk (ostehamster)]

I get tons of below lines in /var/log/message when a plug in a cable:

Nov 12 00:22:57 christoffer kernel: [10313.425071] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Nov 12 00:22:57 christoffer kernel: [10313.425080] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Nov 12 00:22:58 christoffer kernel: [10315.204237] e1000e: eth0 NIC Link is Down
Nov 12 00:23:16 christoffer kernel: [10333.077063] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Nov 12 00:23:16 christoffer kernel: [10333.077072] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Nov 12 00:23:18 christoffer kernel: [10334.640215] e1000e: eth0 NIC Link is Down
Nov 12 00:23:21 christoffer kernel: [10337.848966] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Nov 12 00:23:21 christoffer kernel: [10337.848969] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Nov 12 00:23:23 christoffer kernel: [10339.440197] e1000e: eth0 NIC Link is Down

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 430361, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.