Home Home > 2008 > 10 > 03 > Status of the e1000e Issue
Sign up | Login

Status of the e1000e Issue

October 3rd, 2008 by

This is an update on the status of the e1000e issue. Our openSUSE 11.1 Beta 1 release contained a bug that would cause the non-volatile memory (NVM) of the e1000e controller to be corrupted in certain hardware combinations. This NVM is shared with other components of the system.

We are still working on root-causing the issue, in close cooperation with developers from Intel and the general Linux community.

In the Beta 2 release, the e1000e driver has been augmented with several kernel patches that prevent all of the plausible scenarios where the NVM would be overwritten. This includes a patch that enables write-protection of the NVM. In order to corrupt the NVM with this patch in place, an application or kernel module would have to undo this write protection explicitly before being able to erase the NVM. Most of these protective measures have been implemented within the e1000e driver.

All tests performed so far have shown that with these protections in place, we are unable to reproduce the NVM corruption that could be seen with beta1. On some machines that were tested, a beta1 installation could lead to NVM corruption within 10-30 reboots, whereas a beta2 installation would perform 270 reboots without corrupting the NVM.

Therefore, we have made a conscious decision to leave the e1000e driver enabled by default. We think with the additional safeguards in place (most of which are part of the e1000e driver), the NVM is better protected than without loading the driver. This is based on the assumption that the e1000e driver shares the NVM with other parts of the system.

Nevertheless, users have the option to install beta2 with the e1000e driver disabled, by adding the following to the kernel command line when booting from the installation CD/DVD:


This will prevent the driver from being loaded during installation, and will also add it to the file /etc/modprobe.d/blacklist, which will prevent it from being loaded automatically in the future. Ist das im falle gehen Sie hier von tagungen, bei denen es mehrere vortragende gibt, fr die moderatorinnen bzw

Both comments and pings are currently closed.

2 Responses to “Status of the e1000e Issue”

  1. dragon788

    Hi guys, glad to see you’ve addressed this issue so promptly and mentioned it on the main page of your site. I noticed Ubuntu got some grief from a number of people that were testing the Intrepid Alpha that felt they hadn’t done enough to prevent users from corrupting their machines with this issue, I don’t know if you had to go to the extent those users wished which was to remove the availability of the affected ISOs, but this fix is better than doing nothing and it still allows the driver to be used.

  2. bonux

    Where can I get the fix for 11.0 I need to download it and fix my Lenovo T60. It isn’t working at the moment.. I am desperate, please help…I know this might be the wrong place for this but I can’t help myself. The eth0 does not even appear on my list of interfaces