My hardware (ASUS A8V-VM SE (via K8M890), and 1gbit NIC Intel PRO/1000 PT desktop adapter (PCI express card!!!)) worked out of the box with openSUSE 10.3 (even the livecd) but the NIC does not work/connect with the network openSUSE 11. No changes were made to the hardware or network.
Any help would be great
egrep eth3|Intel /var/log/messages:
Jun 21 16:21:49 hummer ifup: eth3 device: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
Jun 21 16:21:49 hummer kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jun 21 16:21:49 hummer ifup: eth3
Jun 21 16:21:53 hummer avahi-daemon[3063]: Joining mDNS multicast group on interface eth3.IPv4 with address 192.168.110.251.
Jun 21 16:21:53 hummer avahi-daemon[3063]: New relevant interface eth3.IPv4 for mDNS.
Jun 21 16:21:53 hummer avahi-daemon[3063]: Registering new address record for 192.168.110.251 on eth3.IPv4.
It seems to me that the nic drivers have loaded ok.
Check with ā ethtool eth3 ā to see if link is detected and speed is set correctly.
Some other thoughts:
Have you done an upgrade from 10.3 to 11 or a new install?
What I think is strange is that the nic is showing as eth3ā¦ are there other nics in the system?
Also, the ip you have listed, did you configure it statically or by dhcp? Check to see how the card settings are listed in YaST and maybe also whats listed in /etc/sysconfig/network/<interface file>
Itās eth3 because I added other NICs (different vendors/hardware) to be able to get the lspci output off the machine. Those NICs connect to the network without a problemā¦
I gave eth3 a static IP address, after I noticed it did not work (so I couldnāt rely on an external DHCP server on that network for an IP address). Done that in YAST, and everything looks ok to me in YAST and in /etc/sysconfig/network.
if the other nics are working normally it might be good to report this as a bug as it could be a driver issue?! Seems like your setup is as it should be. Maybe first try developers irc or mailinglists to see if they have other suggestionsā¦
Any messages with dmesg when loading/unloading the driver?
Quick addition from the OP.
It looks this problem could be related to the e1000 -> e1000e migration for many Intel NICās. (See e1000 v e1000e)
modinfo shows my nic is reported in e100e supported devices list , and is not in e1000. Is openSUSE11 providing driver versions that suffer from this problems-causing device migration issue? Will they be superseeded by something new soon?
Iām not skilled in compiling updated modules myself. Is there a way for me to force my card to run using the e1000 driver even wtihout it being in itās list of supported devices (as a test) ?
You could try unloading the current driver (lsmod -r ādrvernameā) and reloading the one you want.
If that works itās probably a question of blacklisting the unwanted driver so it does not get loaded.
Iāve tried compiling my own driver a year or two ago, and that was no successā¦ but back then I had less clues of what I was doing so it may not be as complex as i remember.
As a note, if this is what you need to do to get things running I would consider this a bug, & reporting it so will get you good help from the devs that know what they are doing.
My problem was solved with the help from the people on the e1000/e1000e development mailing list. Many thanks to them. Posting this to help out others that might stumble onto this thread in the futureā¦
Jesse Brandeburg wrote in an e-mail:
Please boot your kernel with pci=nomsi[/size][/size][/size]
your adapter is not getting any interrupts due to a broken pci-express to hypertransport bridge common to systems like yours.
After doing this the device worked fine after rebootingā¦[/size]
