| |||||||||||||
|
| |||||||||||||
Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1Posted Sep 23, 2008 16:28 UTC (Tue) by ssam (subscriber, #46587)Parent article: Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1
is there a simple way to tell if your network card is vulnerable?
i have a 80003ES2LAN Gigabit Ethernet Controller (Copper) according to lshw. googleing finds http://hardware4linux.info/component/13943/ which says it can use both e1000 and e1000e. lshw says that it is using e1000 (with kernel 2.6.24).
http://lwn.net/Articles/278016/ says that at some point card that work with both drivers will be switched to e1000e.
i guess i should not even try booting a 2.6.27 kernel to find out.
(Log in to post comments)
Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1 Posted Sep 23, 2008 20:08 UTC (Tue) by nix (subscriber, #2304) [Link]
If you dump the eeprom to a file with 'ethtool -e ethX > ...' (with
obvious replacements) then you... are still stuck, but less stuck, because at least you have the eeprom's original contents so that *someone* can try to get it back onto the card.
Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1 Posted Sep 24, 2008 5:27 UTC (Wed) by aj (subscriber, #39001) [Link]
AFAIK the current theory is that it only happens on Laptops where the EEPROM is part of the NVRAM - and that it gets destroyed by another driver during a crash/OOPS, e.g. the graphics driver. But to confirm this, we need to reproduce it first.
But today there's AFAIK nothing concrete enough that I can tell you whether a system is affected or not. I suggest to save the eeprom as others commented.
Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1 Posted Sep 24, 2008 8:13 UTC (Wed) by aj (subscriber, #39001) [Link]
I have to correct myself: It might happen with non-Laptops as well (happened with machine with onboard e1000).
|
|
||||||||||||