e1000 gives problems with a fresh kernel compile

[Debo~ Dutta]

I am not sure whether its a problem with Feisty or the kernel or the e1000 driver but here is what I do to reproduce them

* Install 7.04
* Install kernel 2.20.3 source
* copy working config to .config
* make menuconfig
* make-kpkg -initrd etc ....
* dpkg -i
* reboot

With the custom kernel

* The on board Intel NIC will not show up in dmesg
* It wont be usable upon insmod

I have seen this on more than 1 machine. For example, on a T60, I observed the following

[ 658.528000] Intel(R) PRO/1000 Network Driver - version 7.3.15-k2-NAPI
[ 658.528000] Copyright (c) 1999-2006 Intel Corporation.
[ 658.528000] ACPI: PCI Interrupt 0000:02: 00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 658.528000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 658.592000] e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
[ 658.612000 ] ACPI: PCI interrupt for device 0000:02:00.0 disabled

If I reboot with the regular kernel, I get

[ 269.388000] Intel(R) PRO/1000 Network Driver - version 7.3.15-k2-NAPI
[ 269.388000] Copyright (c) 1999-2006 Intel Corporation.
[ 269.388000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 269.388000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 269.456000] e1000: 0000:02:00.0: e1000_probe: (PCI Express: 2.5Gb/s:Width x1) 00:15:
58:7e:9e:1b
[ 269.516000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection

Is this a Feisty/Ubuntu issue? Or is this a e1000 interaction issue (with Feisty)?

[jcfp (jcfp)]

Regular kernel apparently still uses that checksum by default when loading the module, ubuntu's doesn't. See duplicate Bug #60388 and Bug #98745 for more information

[Launchpad Janitor (janitor)]

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!