Description of problem: Determining IP information for eth0... can't get ip info. Boot just stops there if the cable is connected. Version-Release number of selected component (if applicable): f7t3 fully updated 4/17/2007 How reproducible: Unknown. Somehow I got it working yesterday and was able to yum update. Now it just waits forever for the ip. Steps to Reproduce: 1. ifup eth0 2. 3. Actual results: Nothing happens. Still waiting.. Expected results: Done. Working connection. Additional info: HP Pavilion laptop dv9000 series (dv9237eu). AMD Turion64 X2. /var/log/messages output: Apr 17 15:41:48 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Apr 17 15:41:49 localhost dhclient: DHCPOFFER from 172.16.20.5 Apr 17 15:41:49 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 17 15:41:53 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 17 15:42:06 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Apr 17 15:42:06 localhost dhclient: DHCPOFFER from 172.16.20.5 Apr 17 15:42:06 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 17 15:42:12 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 17 15:42:17 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Apr 17 15:42:18 localhost dhclient: DHCPOFFER from 172.16.20.5 Apr 17 15:42:18 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Created attachment 152883 [details] lspci -vvv
Maybe I was too hasty filing a bug. It finally got the ip, only took half an hour... Though some might consider 30 minute boot time rather long. :)
Can you try installing the latest kernel update from http://people.redhat.com/davej/kernels/Fedora ? (todays rawhide is kinda broken, so that's the easiest way to get a working build) We fixed a forcedeth bug just after test3 which /may/ have been reponsible for this.
I'll try that next, problem is still there with 3094. Dunno if related but I've had a lot of problems, now I found out that it all comes to this one bug http://bugzilla.kernel.org/show_bug.cgi?id=8186 pci=noacpi helps that finally I can use X. Since there is a problem probing pci bus, could this be symptom of that?
Crap. Now I'm not sure this even is Linux bug. Yesterday I had some trouble with my adsl-connection that I had to call my isp to get it fixed. Long story short, the problem might be on my adsl-modem.
The problem probably was with my modem.. or it is fixed. I'll mark this as notabug.