e1000 fails to load first time "The EEPROM Checksum Is Not Valid"

Bug #140771 reported by Paul Sladen
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

Wired ethernet driver 'e1000' failed to load first time, showing Checksum Error:

dmesg | grep -B3 -A2 e1000.*Checksum
[ 3.960000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 3.960000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 4.000000] Clocksource tsc unstable (delta = -280411482 ns)
[ 4.024000] e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
[ 4.044000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[ 4.044000] e1000: probe of 0000:02:00.0 failed with error -5

$ uname -r
2.6.22-11-generic

$ dpkg -l | grep linux-image-2 | tail -1
ii linux-image-2.6.22-11-generic 2.6.22-11.33

Ideally the driver would just ignore the Checksum mismatch and magically fix things so that the user never boots the machine and experiences a non-functioning NIC.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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 60388, 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 add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.