Intel 80003ES2LAN gigabit ethernet controller not supported by Feisty beta

Bug #98745 reported by Marc Tardif
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Tim Gardner

Bug Description

I'm running Feisty beta and the two Intel 80003ES2LAN gigabit ethernet controller interfaces do not seem to be supported. When I run the command ifconfig -a, none of the interfaces appear except lo.

Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Tim Gardner (timg-tpi) wrote :

The e1000 module is in the lsmod listing. How about attaching the output from dmesg.

Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
status: Unconfirmed → Needs Info
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Marc, #60388 indicates there is a module parameter that ignores the EEPROM checksum. I also found an URL that talks about this problem: http://www.thinkwiki.org/wiki/Problem_with_e1000:_EEPROM_Checksum_Is_Not_Valid

Revision history for this message
Marc Tardif (cr3) wrote :

First, I tried updating the kernel to 2.6.20-14-generic but that didn't fix the problem.

Second, I tried running modprobe -r e1000 and then modprobe e1000. That didn't fix the problem either.

Third, I tried adding the kernel option e1000.eeprom_bad_csum_allow=1 and made sure the option appeared in /proc/cmdline after booting. That didn't fix the problem either and resulted in the following warning message when booting:

  Unknown boot option: 'e1000.eeprom_bad_csum_allow=1': ignoring

Fourth, I tried disabling and reenabling the network devices in the BIOS but I couldn't figure out how to do this.

During all these tries, a network cable was connected each of the network interfaces. So, is the only solution to update the BIOS?

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Try using modprobe directly:

rmmod e1000
modprobe e1000 eeprom_bad_csum_allow=0

or add it to /etc/modprobe.d/options.

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.