Comment 271 for bug 263555

Revision history for this message
In , Jkosina-d (jkosina-d) wrote :

(In reply to comment #38 from Andi N Kleen)
> Those would first need to fix their mac addresses to try again right?
> Also is there other vital information in that EEPROM?

By the way the current driver doesn't get even bound to the card that has wrong EEPROM CRC, right? So it's even not possible to easily fix its contents up using ethtool from within default installation.

Karsten already patched and built the kernel so that it binds the driver to the card even in cases of broken EEPROM checksum.