https://bugzilla.novell.com/show_bug.cgi?id=177440 ------- Comment #4 from john.ronciak@intel.com 2006-12-01 17:38 MST ------- Please be careful using this. Dave Miller added this without any public debate on this W/A. The problem could still be that the values loaded from the EEPROM by the HW could be incorrect. This could mean that the HW isn't configured correctly or not as it's expected to be. Like programming PHY configurations dealing with cable lengths. This is why we have always had the driver fail the load when this happens, you would never know what got loaded. In most cases it will still work but it may not be working correctly. So now when problems are reported, especially cable and PHY related issues, the first this that needs to be looked at is a message saying that this has happened. If this isn't done, a lot of time could be spent ebugging the problem that is due to a corrupted EEPROM or a EEPROM that wasn't programmed at all. Please use with caution. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.