include newest e1000 driver, solves problem with some chipsets
Bug #124787 reported by
Wit Wilinski
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-ubuntu-modules-2.6.22 (Ubuntu) |
Fix Released
|
Medium
|
Kyle McMartin | ||
Bug Description
Please include the newest e1000 kernel module (7.6.5) from its website (e1000.sf.net), it solves problem with 82547EI network chipsets found on some motherboards. The driver included in mainstream kernel crashes, rendering network device useless until next boot. The newest driver found on the above website fixes bug for these chipsets.
Revision history for this message
| Leann Ogasawara (leannogasawara) wrote | #1 |
| Changed in linux-source-2.6.22: | |
| assignee: | nobody → leannogasawara |
| status: | New → Incomplete |
Revision history for this message
| Ben Collins (ben-collins) wrote | #2 |
| Changed in linux-source-2.6.22: | |
| assignee: | leannogasawara → kyle |
| importance: | Undecided → Medium |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
For the kernel which crashes, can you provide the following information:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after the kernel crash and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For the kernel with the e1000-7.6.5 module update applied, can you attach the dmesg output, verifying your kernel no longer crashes?
Also, can you point us to the appropriate changelog entry for the e1000-7.6.5 module release which details the fix/patch which resolves the issue you were seeing?
Thanks in advance!