Thanks,
I still don't understand how it is that e1000e_recover didn't work for you, but
I admit that
I have been using it as a tool, and don't understand its inner workings.
Let's try another approach to get the invalid NVM content listed, this time
by the driver when it reads the data. I attac
This is unusual, as the
e1000e_nvm -r –d eth0 -o ethtool.dmp
command normally dumps out the 1Gb portion of the system flash even if
it _does_ have a bad checksum, and then I've been fixing the checksum &
content. Are you sure that there isn't an ethtool.dmp file created in
the local direc
I am still contacted about once per month for instructions on how to
recover ethernet functionality on systems that have had their 1Gb flash
content corrupted, possibly by this defect.
If you believe that you are affected by this isssue, you can safely
perform steps 1 through 5 from the bullet lis
Stefan, Beige.
SOrry about the delay. I still have no repro here, though I have taken this up
with our customer issue repro team to keep trying. In the meantime, if you do
decide that you want to restore the EEPROM (to re-enable he WOL capability),
you can do this:
ethtool -E eth0 magic 0x109a
I agree that the temproary fix shohuld be safe. It was a good idea. I've
been trying to debug the issue myself, and though I have not been
sucessful, can still share with you what I have done - it may be of some
use.
I don't have a Toshiba Satellite Pro but have tried to repro on a Lenovo
T60P, wh
While we should expect no further reports of flash corruptions due to
this bug, I would like to know of any systems which did fall foul of the
bug, and have not yet had their flash restored. Pleae let me know if you
have system that had proper (e1000e) LAN functionality proor to
installing a 2.6.27
