On 4/28/06, Gerhard de Jeger <[EMAIL PROTECTED]> wrote:
I'm also experiencing TX hang problems with the e1000 driver.
I was using the 6.0.60-k2 version previously which shipped with the
2.6.14.2 kernel.
I had no problems with this driver, but after my issues with the 7.0.33
driver I tried to go back to the 6.0.60-k driver. Now when I load the
module, there is an error saying that the EEPROM is corrupt - so I
cannot use the old driver which used to work.
so what kernel are you using now? what kind of hardware do you have?
we need a decent bug report in order to make some progress.
Why is it that I now get the EEPROM error with the older driver?
did you change the kernel?
Any ideas on how to fix the problem (with either the old driver or the
new one)?
it sounds like you may have had a hardware failure? Or maybe a kernel
problem. Did you go back to 2.6.14.2 and try it?
It is highly unusual for the driver to be able to change the eeprom
through regular usage.
Please reply with more specifics
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
