After upgrade lucid -> maverick eth0 interface is gone

Also tried on kernel: 2.6.34-020634 and eth0 is gone there too.
However, kernel 2.6.32 seems to work fine re: network (video is awful).

Attaching the output of:

nessita@dali:~$ dmesg > nessita.dmesg.`uname -r`.log

Output of:

nessita@dali:~$ dmesg > nessita.dmesg.`uname -r`.log

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

nessita@dali:~$ sudo dmidecode
[sudo] password for nessita:
# dmidecode 2.9
SMBIOS 2.5 present.
28 structures occupying 1507 bytes.
Table at 0x000EB180.

Handle 0x0000, DMI type 4, 35 bytes
Processor Information
 Socket Designation: J1PR
 Type: Central Processor
 Family: Unknown
 Manufacturer: Intel(R) Corporation
 ID: E5 06 01 00 FF FB EB BF
 Version: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
 Voltage: 1.1 V
 External Clock: 133 MHz
 Max Speed: 4000 MHz
 Current Speed: 2668 MHz
 Status: Populated, Enabled
 Upgrade: Other
 L1 Cache Handle: 0x0004
 L2 Cache Handle: 0x0003
 L3 Cache Handle: 0x0001
 Serial Number: Not Specified
 Asset Tag: Not Specified
 Part Number: Not Specified

Handle 0x0001, DMI type 7, 19 bytes
Cache Information
 Socket Designation: Unknown
 Configuration: Enabled, Not Socketed, Level 3
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 8192 KB
 Maximum Size: 8192 KB
 Supported SRAM Types:
  Asynchronous
 Installed SRAM Type: Asynchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Unified
 Associativity: 16-way Set-associative

Handle 0x0002, DMI type 7, 19 bytes
Cache Information
 Socket Designation: Unknown
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 32 KB
 Maximum Size: 32 KB
 Supported SRAM Types:
  Asynchronous
 Installed SRAM Type: Asynchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Data
 Associativity: 8-way Set-associative

Handle 0x0003, DMI type 7, 19 bytes
Cache Information
 Socket Designation: Unknown
 Configuration: Enabled, Not Socketed, Level 2
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 256 KB
 Maximum Size: 256 KB
 Supported SRAM Types:
  Asynchronous
 Installed SRAM Type: Asynchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Unified
 Associativity: 8-way Set-associative

Handle 0x0004, DMI type 7, 19 bytes
Cache Information
 Socket Designation: Unknown
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 32 KB
 Maximum Size: 32 KB
 Supported SRAM Types:
  Asynchronous
 Installed SRAM Type: Asynchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Instruction
 Associativity: 4-way Set-associative

Handle 0x0005, DMI type 0, 24 bytes
BIOS Information
 Vendor: Intel Corp.
 Version: KGIBX10J.86A.3206.2009.0805.1855
 Release Date: 08/05/2009
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 2048 kB
 Characteristics:
  PCI is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  CGA/mono video services are supported (int 10h)
  ACPI is supported
  USB legacy is supported
  ATAPI Zip drive boot is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
 BIOS Revision: 0.0
 Firmware Revision: 0.0

Handle 0x0006, DMI type 1, 27 byt...

Tim,

I installed Lucid LTS server on a different partition and saved the dmesg ouput of that (kernel 2.6.32-21-server) and then I installed the backported kernel, rebooted and saved the dmesg output again. Both files are attached.
On the backported kernel, there is no eth0 (ah no oops in the dmesg output).

Testing a vanilla upstream kernel in a Lucid server installation (same error, no eth0 yet).

Naty - any luck with the BIOS upgrade as was suggested by Intel?

Not likely to hit the Maverick Alpha2 milestone, bumping to Alpha 3.

I'm seeing this issue with the Intel 82566DC, which seems to use the e1000 driver.

@Dave,

It actually uses the e1000e driver. Can you attach your /etc/udev/rules.d/70-persistent-net.rules file please.

No response from original reporter for 3 weeks.

I can confirm this bug still being there in (K)ubuntu 10.10 RC1 amd64 ISO image.

My hardware is an Intel DG965WH mainboard with an Intel 82566DC Ethernet chip that's driven by the e1000e module. An update to the most recent BIOS provided by Intel did not solve the problem.

As for example is stated in [1] this issue seems to be an upstream one from 2.6.35 kernel series. I had the same behaviour while running Arch Linux on the said machine when the kernel was upgraded from 2.6.34->2.6.35.

However, I think that this is an issue that would be very good to have solved before releasing Maverick because these Intel Chips seem to be very common and thus there's a potential for many people to be affected by this when upgrading from lucid.

Of course I can provide more details if needed.

[1] http://kerneltrap.org/mailarchive/linux-netdev/2010/7/29/6282004/thread

I also have an Intel 82566DC Ethernet interface that doesn't work with Maverick 64bit. Under Lucid 32bit it works fine, with the driver listed as e1000e. From the Maverick RC LiveCD no connection can be established, nor from an actual install of the Release Candidate.

In case this is a duplicate, but the fix from 2.6.35-rc6 worked for me. I also have a 82566DC

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/619841

same problem as seanlano: intel 82566dc not working on Maverick RC 64bit (it worked on Lucid 64bit).

same problem as Golgoth: intel 82566DM (rev 02) not working on Maverick RC 64bit and on other distro with kernel 2.6.35.x (it worked on Lucid 64bit). It seems that after a while the card is connected at 10Mbps

same problem, intel 82566DC not working on Maverick RC 64 and 32 bit versions

also the same problem with Intel 82541PI on Maverick RC 64 & 32 bit versions

Hi therei,

Happens here as well. 82566DC Network card. I need to rmmod && modprobe the kernel driver many times until I have luck with stock ubuntu 10.10 kernel. adm64 arch.

Here's the file missing:

/etc/udev/rules.d$ cat 70-persistent-net.rules
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x8086:0x104b (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:76:dc:45:a8", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

I've got Intel 82566DC (rev 02) and i think i'm affected by this bug too. The network manager could recognize the card, but won't be able to connect to any network. DHCP failed, force IP address also failed.

whats the latest with this? i've installed a fresh copy of x64 and done all update (via wireless) but still am unable to the 82566dc to work.

Even with the latest kernel 2.6.35-22 in Maverick 10.10 the Intel Pro/1000GT nic (82566DC & 82541PI) does not work :-(

There seem to be lots of issues with the e1000e driver, e.g. I can't use it at full speed (bug #655967). And I've seen other reports all over the internet about this driver, although the exact symptoms seem to differ depending on the exact chip or system or kernel version (from slower speeds to no connection at all).

Maybe the same bug is causing this all, and the symptoms depend on whether you're lucky (slower connection) or not (no connection)?

I experienced this bug as well and reported it separately (see #616984). Based on Albert's hints, I tried Natty Alpha 1 with a 2.6.37 kernel and my network works again. Thus, I believe this is a duplicate of #619841.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/619841

Natalia Bidart, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

linux (Ubuntu) Maverick -> Won't Fix

I experienced this problem (apparently, although I do not recall it since it was a while ago), and I can confirm that the problem is gone in Oneiric, and also the Precise testing releases I have used.
In fact, as a little side-note, Precise seems to be working better than Oneiric did - a problem I had with the headphones port on my laptop is fixed, for example. It's nice to see devs working to close bugs. :)

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]