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,
Control: reassign -1 src:linux 4.9.6-3
Control: retitle -1 e1000: EEPROM write failed on 82540EM
Control: tag -1 upstream
On Fri, 2017-02-24 at 19:52 +0100, Yvan Masson wrote:
> Package: ethtool
> Version: 1:4.8-1
> Severity: normal
>
> Dear maintainer,
>
> The EEPROM of my Ethernet NIC has been
Package: ethtool
Version: 1:4.8-1
Severity: normal
Dear maintainer,
The EEPROM of my Ethernet NIC has been flushed for some unknown reason.
I would like to use ethtool to restore my EEPROM (fortunately I have a
dump).
Here is one simple "test command" I tried and which should be valid
according
3 matches
Mail list logo
