Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #57096
| From | Yvan Masson <yvan.masson@openmailbox.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#856049: ethtool: Can not use --change-eeprom option |
| Date | 2017-02-24 22:20 +0100 |
| Message-ID | <tevrr-5ZH-11@gated-at.bofh.it> (permalink) |
| References | <tetfX-4fK-5@gated-at.bofh.it> <tetSG-4P4-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
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
Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread
Bug#856049: ethtool: Can not use --change-eeprom option Yvan Masson <yvan.masson@openmailbox.org> - 2017-02-24 22:20 +0100
csiph-web