Thanks for this fast and precise answer! > As for why the driver failed to access the EEPROM, I can't tell - > there are several possible error cases. It might be worth trying to > pass the EEPROM contents as a binary file on stdin, instead of trying > to set a single byte. I already tried this, and if I am not wrong in the procedure, this produces the same error: - dump EEPROM from working NIC on another laptop: ethtool --eeprom-dump enp2s1 raw on > dump - write dump file on faulty NIC: ethtool --change-eeprom enp2s1 magic 0x100e8086 < dump > As the e1000 driver is no longer maintained by Intel, I'm afraid these > bugs are unlikely to be fixed. So I will have to try other ways :-( Regards, Yvan
Attachment:
pgpWzgLrGiqHr.pgp
Description: Signature digitale OpenPGP