> Thanks for all the work here. However, please be careful in doing this. If you write the wrong EEPROM image to > your corrupted EERPOM you could brick your NIC/LOM worse than it is already. You could get it into such a > state that it won't even show up on the PCI bus. I totally understand where you are going with this and while > it may help some it could also hurt others who use an incompatible EEPROM image as the "good" source for the > EEPROM. In addition, since you are using LOM devices in this example, the maker of the platform that has the > LOM on it can have specialized parameters in the EEPROM which might not be set unless the exact EEPROM image > is burned to the device. This may enable or disable features the manufacturer wants to have enabled or > disabled for various reasons. So if > the exact EEPROM image is not used to correct the corrupted EEPROM, there can be problems with doing this.
Hi, My ethtool -E command is executing without error . However the changes are not getting reflected. Please guide. REgards Richa ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired