E100 Driver - EEPROM Corrupted

I have added this patch to my git tree.

> Public bug report changed:
> https://launchpad.net/malone/bugs/30666
>
> Comment:
> I have added this patch to my git tree.
>

What revision do you think this will be fixed in?

Also -- this problem still affects Dapper, as of Flight 3.

Chris

Added bug to dapper also. This problem occurs in both 5.10 (Breezy) and Dapper (as of the latest -- Flight 4).

I am downgrading the status and assigning it to the kernel team.

Baishampayan, do you have any updates on this issue?

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Closing.

I am having the problem too. i used the xubuntu live cd to install. The patch listed here is no longer available to download.

Sorry I forgot to mention what i'm running. I am running ubuntu 8.04 (xubuntu).
Here is my modprobe:

BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
MEM window: fe100000-fe2fffff
PCI: Firmware left 0000:02:09.0 e100 interrupts enabled, disabling
e100 Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
e100: Copyright (c) 1999-2006 Intel Corporation
e100: 0000:02:09.0: e100_eeprom_load: EEPROM corrupted
e100: probe of 0f 0000:02:09.0 failed with error -11

I followed the discussion on the lkml back in 2006 and obvioulsy the Intel guys can't figure out what's wrong, but it's _still_ happening on 2.6.27-7 and 2.6.27-8 (it _didn't_ happen in my 2.6.26 kernel)

I can confirm the issue with 2.6.23 and 2.6.27-7. For me it happens mainly (would say only) when resuming from hibernate - not always, but often. Sometimes I can re-enable eth0 by reloading the e100 module.

Did someone try the fix I just found on Ubuntu geeks [1] ? I will apply it now and report my experiences in some days.

[1] http://www.ubuntugeek.com/fix-for-intel-cards-with-broken-eeprom-e100-driver.html

It doesn't work - the problem persists. When resuming from hibernate the second or third time (2 or 3 times hibernated after a real reboot) I can't use the nic and have to swtich to wireless. It's very annoying!

I just thought a bit about it and now I'm sure:
I didn't have this problem at all with kernel 2.6.23 (self made, without ubuntu patches) but 2.6.22 ! Now I' using 2.6.27-7 with ubuntu patches, also modifed by myself. Maybe I'll go back to 2.6.23 if I can't get it to work reliably.

I upgraded to 2.6.28.3 a week ago - no problems with e100 any more! I'm now using a vanilla kernel from kernel.org without ubuntu-patches. I think I'll try and build another new kernel, this time from the ubuntu repository, and look for EEPRAM corrupted messages again.