Red Hat Bugzilla – Bug 179805
e1000 kernel module does not accept DHCP IP addresses
Last modified: 2007-11-30 17:11:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5
Description of problem:
Installed FC5T2, e1000 onboard NIC would not work. Installed a e100 NIC, updated to the current rawhide kernel (as per advise from Dave Jones). e1000 still does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install and run FC Rawhide
Actual Results: lspci shows:
03:00.0 Ethernet Controller: Intel Corpation 82573E Gigabit Ethernet Controller (Copper) (rev 0.3)
ifconfig shows the link is up, but no address is asigned.
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog_task: NIC Link is up 100Mbps Full Duplex.
Expected Results: to see an IP address in "ifconfig"
The motherboard is a SuperMicro PDSGE.
Same applies for 2.6.15-1.1895_FC5
Please attach the output of running "sysreport"...thanks!
Created attachment 124224 [details]
output of sysreport
This relates to the problem described in the fedora-devel-list thread "e1000
in rawhide kernel", correct?
From that thread, the interface works correctly if you use a static IP address
configuration. Is that correct? Just establishing the baseline... :-)
Can you provide the output of running "tcpdump -n -i eth0" while you do "ifup
eth0" in another window (using the DHCP configuration)? Thanks!
I have the same problem except that I can not even connect using a static IP. I
have an Intel EtherExpress/1000 gigabit (Intel Copporation 82573V Gigabit
Ethernet Controller (Copper)).
In the system-config-network thingy I am not given the possibility to setup
dhcp: It is grayed out in the configuration dialog.
On logout the system hangs with 'Removing IPtables modules'; I can not even
Ctrl-Alt-Del, but have to hard-reset the machine.
Output of sysreport -norpm and tcpdump -n -i eth0 will follow shortly.
Created attachment 124427 [details]
Created attachment 124428 [details]
Output of running tcpdump -n -i eth0
I did an 'ifdown eth0' just before doing 'ifup eth0'.
Comment on attachment 124427 [details]
Corrected .gz to .bz2 (and updated MIME Type).
Created attachment 124443 [details]
Output of running lspci
I do not know whether this helps but Mr. Knox provided it, so I will do the
I have FC5 test kernels w/ an e1000 update available here:
Please give them a try and post the results here...thanks!
I did 'rpm -Uvh kernel...' logged out and back in using the new kernel:
Unfortunately there is no change at all :-(
If any new data is needed, then just tell me so :-)
Not 100% sure, but I think you should install kernel packages as "rpm -ihv"
instead. Also, does "logged out and back in using the new kernel" imply a
reboot? You will need to reboot for the new kernel to take effect.
Just to be sure, please post the output of "uname -a"...thanks!
It did include a reboot. Just to be sure, I re-installed the kernel using 'rpm
-ivh --force kernel...'. Then I rebooted.
The output of uname is:
# uname -a
Linux localhost.localdomain 2.6.15-1.1941.2.1_FC5.jwltest.8 #1 Mon Feb 13
13:00:42 EST 2006 i686 i686 i386 GNU/Linux
When I click the 'Probe' button in system-config-network, to probe the
MAC-address, then it finds 00:00:00:00
Something has changed with the new kernel: During startup I get a green 'OK'
when initializing eth0. It still takes a long time, so I do not really trust the
I have done a new tcpdump, which will be uploaded shortly.
Created attachment 124623 [details]
tcpdump, done with the jwltest-8 kernel
This seems fixed in FC5 test 3.
I do get some periodic spikes in network traffic, but I will have to investigate
further. If it is a problem I will open a seperate bug on it.
I think this bug could be closed.
So you can get an IP address and use the NIC as one would expect? I sadly have
not had any time to test this further, but do have a machine and some time next
week too look.
Yes: DHCP, probing for a MAC address, using the network in general - it all
works. I can configure an activate/deactivate the NIC from the
system-config-network gui etc.
I'm going to go ahead and close this based on ligaard's reports. Micheal,
plese reopen this if you still experience the issue. Thanks!