e1000 not loaded anymore after kernel update to 2.6.20-16.33

Bug #196548 reported by knut
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.20-16-generic

Ubuntu: 7.04
Package: linux-image-2.6.20-16-generic
Version: 2.6.20-16.33

After updating kernel from 2.6.20-16.32 to 2.6.20-16.33 the e1000 module is not loaded at bootup anymore. Also loading manually does not help to make network available. Behaviour still exists in 2.6.20-16.35.
Computer is a Dell Optiplex 755. I attached dmesg + lspci information.

ciao Knut

Revision history for this message
knut (mr-knut) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to test the new kernel using the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Changed in linux-source-2.6.20:
status: New → Incomplete
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!

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

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
knut (mr-knut) wrote :

Feisty:
network driver ist still not working for 2.6.20-17.37 but copiing the e1000.ko from working kernel helps as workaround :)

Hardy:
early version: e1000 is not working
but
updating to the last kernel (2.6.24-19.41) helps. Now e1000e is loaded instead. I've no idea why...

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

Hi knut,

And is the e1000e driver working for you? Based on the vendor and device id in your lspci output, it is supported by the e1000e driver in Hardy. Thanks.

Revision history for this message
knut (mr-knut) wrote :

Hi Leann,

yes, e1000e seems to work :)
it's loaded automatically (as it should) and everything is fine.

ciao Knut

Changed in linux:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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