Description of problem:
With kernel 188.8.131.52-33.fc7 my computer is not able to get IP address from DHCP
server for both network cards (LAN and WiFi).
With kernel 184.108.40.206-27.fc7 it works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set your computer to use DHCP on LAN card
2. Upgrade to 220.127.116.11-33.fc7 kernel
3. Reboot and log in as normal user or root.
Network card doesn't get IP address assigned from DHCP server, but ZeroConf is
Network card gets IP address assigned from DHCP server.
*** Bug 249699 has been marked as a duplicate of this bug. ***
I have the same probelm.
Reverting "cfs update" seems to solve the problem.
(replce linux-2.6-sched-cfs.patch with 18.104.22.168-27.fc7's one)
>* Fri Jul 20 2007 Chuck Ebbert <firstname.lastname@example.org>
>- utrace update
>- CFS scheduler update
Need more information? Please let me know.
CFS timer changes have been synced with what is upstream.
The next kernel will be out very shortly, it should be fixed.
I have the same problem.
dhclient get DHCPINFORM message, but nothing happen then.
NetworkManager says that not reply received from DHCP server and interface
configured using ZeroConf.
Even after manually configuration IP address on NIC, openvpn tunnel, based on
UDP protocol, can't start :(
I confirm the bug I am using FC 7 on Nforce 2 Mainboard ASUS A7N8X-X and i have
the same problem. IP adress is offered bye DHCP server (Cable Modem)but not
network card dont get IP adress.
Having the same problem with my desktop PC (AMD, Athlon).
Additionally I found out: Booting to single user mode, then calling
"/etc/init.d/network start" by hand gets well an IP address by dhcp. But during
normalboot sequences (to init mode 3 or 5), it will hang. Race condition problem?
I can confirm that 22.214.171.124-27.fc7 boots fine.
I am having this problem too.
Hardware is: VMWare Server 1.0.3
When booting 126.96.36.199-33.fc7, it is hang on "determining IP information for
eth0...". But if I choose old 188.8.131.52-27.fc7, it works fine.
I confirm that 184.108.40.206-41.fc7 from koji fixed this problem.
Confirming also. -41 resolves the issue. Thanks.
Yes, installation of 220.127.116.11-41.fc7 was fixed this bug. Thanks! :-)
The latest kernel-18.104.22.168-41.fc7 solves the problem. Please reopen or create
new bugreport if your problem persist. See bug #250003 for more info.
*** This bug has been marked as a duplicate of 250003 ***