x60s and problems with e1000 module

Solaris, RedHat, FreeBSD and the like
Post Reply
Message
Author
profilek
Posts: 6
Joined: Thu Apr 20, 2006 12:19 pm

x60s and problems with e1000 module

#1 Post by profilek » Thu Apr 20, 2006 2:56 pm

I have a problem with creating the interface by loading the e1000 module (kernel from 2.6.16 to 2.6.17-rc2). The card is in X60s and it's pci-express. Sometimes i after loading e1000 module I get in logs

Code: Select all

e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
the module is loaded but there is no interface (ifconfig -a).
This is happening only sometimes, however I cannot figure out what are the conditions which cause this problem. Of course there is no problem under "other" system. I did full check of the card using pc doctor programm and the test is ok.

I found a comment on intel site that such thing can happen due to a driver error or a systemboard failure. I hope it's not the latter...

Does anybody have such problem with with X60 / X60s ?

If I force driver to load with the EEPROM error (commenting one line in e1000_main.c) the driver seems acting correctly, however one time I got wrong MAC address (which is not strange if the checksum is wrong I guess).

After forcing module to continue after EEPROM failure check I don't have any debug info (with debugging messages on) in logs and it seems that the card is working correctly.

Any ideas?
How to check the EEPROM card ?
How to find out if the systemboard is correct?
Can be this MSI or PCI-Express issue?

cheers

jescombe
Posts: 9
Joined: Sat Apr 30, 2005 7:36 am
Location: U.K.

#2 Post by jescombe » Wed Apr 26, 2006 11:50 am

I've seen this when udev goes a bit mad (admittedly with my help ;) and tries to assign the same ethx port to both wireless and wired interfaces.. If you're running FC5, this appears to be fixed by an initscripts update in the updates-testing repo.

Basically, the wireless interface was getting eth0 when no cable was inserted, and I also had e1000 aliased to eth0.

Hope this helps,
Jon.

revolutionary_one
Sophomore Member
Posts: 217
Joined: Sun Apr 24, 2005 9:13 pm
Location: Dallas, Texas

#3 Post by revolutionary_one » Thu Apr 27, 2006 6:08 pm

Depending on the distro you are using with the available modules for that specific kernel version, e1000 might be broken and you might wanna try using e100.

Cheers.
T42 2378FVU -- PM 735 1.7Ghz, 768MB RAM, 40GB 5400rpm HDD, 14.1 SXGA+(1400x1050) TFT LCD, 64MB ATI Radeon 9600, 24x24x24x/8x CD-RW/DVD, Intel 802.11b/g, Modem(CDC), Gigabit Lan, 6 cell Li-Ion battery, WinXP Pro | UbuntuLinux (Dapper Drake)

profilek
Posts: 6
Joined: Thu Apr 20, 2006 12:19 pm

#4 Post by profilek » Sat Apr 29, 2006 11:50 am

thanks for replays :)

it seems that the driver is loading correctly if i plug the cable in before the boot. if it's unplugged then i need to ignore the error report about the EEPROM checksum. After that i got fully working card.

I haven't tried e100 driver. I didn't even know it works with 1Gb versions.

cheers

squashball
Posts: 37
Joined: Wed Jun 07, 2006 10:56 am
Location: Germany

#5 Post by squashball » Wed Jun 07, 2006 1:05 pm

Hm, same problem here with a t60...
I also commented the goto line in e1000_main.c, so everything seems to work, but thats not realy a good solution ;-)
Are there any new informations?
Florian

Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “Linux Questions”

Who is online

Users browsing this forum: micrex22 and 3 guests