New kernel e1000e problem, v1.4?

  • Thread starter Thread starter vlad
  • Start date Start date
V

vlad

Guest
Just upgraded my install and lost network connection. The driver e1000e gives "The EEPROM Checksum Is Not Valid" and "failed with error -5".

Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)

Kernel 2.6.24-7-pve works fine.

Thanks,
--Vlad
 
vlad said:
The driver e1000e gives "The EEPROM Checksum Is Not Valid" and "failed with error -5".
Click to expand...

Strange, I cant find that message inside the e1000e source code - that seems to be a message of the e1000 od igb drivers instead - confused. What is the pci id of that card?

I have a system with such card here - lspci gives me:
Code: 
00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network Connection (rev 02)

When I boot the system i get the following messages (dmesg):

Code: 
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2.5-NAPI
e1000e: Copyright(c) 1999 - 2009 Intel Corporation.

Everything works as expected here. So please can you send me the boot log (reboot the server, run 'dmesg' to get the log).
 
I killed motherboard while trying to upgrade bios but I got two other machines with same motherboard. I'll try to replace motherboard today and tomorrow or so will deal with this again. I'll give you more info if I'll re-produce it again.

Also I'm sure it was e1000e because I had to force it with modprobe, it did not auto load on start-up. I hope it just was faulty motherboard...

Thanks,
--Vlad
 
Okay, I got to other machine sooner than I expected, and same thing happened, here is the info:

dmesg | grep e100
Code: 
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2.5-NAPI
e1000e: Copyright(c) 1999 - 2009 Intel Corporation.
e1000e: probe of 0000:00:19.0 failed with error -5
modinfo e1000e|grep version
Code: 
version:        1.0.2.5-NAPI
srcversion:     DDEDB7A50AA70D823257BD7
The e1000e driver actually loaded this time on start but failed. I guess I've got two options, use older kernel 2.6.24-7-pve or try install e1000 driver from sources. Upgrading bios again seems to be risky.

Thanks,
--Vlad
 
Fixed the issue by going back to 0.5.8.2 driver(e1000e-0.5.8.2.tar.gz). Also submitted bug at SF.

Thanks,
--Vlad
 
Looks like the 1.0.2.5 driver is not the the newest one and has some issues. I just realized 1.0.15 is newer, and after upgrading to that, this issue was gone.
Thanks,
--Vlad
 
vlad said:
Looks like the 1.0.2.5 driver is not the the newest one and has some issues. I just realized 1.0.15 is newer, and after upgrading to that, this issue was gone.
Click to expand...

Thanks for that hint - i will include it with the next kernel update.
 
You must log in or register to reply here.
Top Bottom