You are not logged in.
When my machine boots up, it hangs and consistently fails to obtain an IP from the specified DHCP server. The DHCP server is working fine and I am fairly sure there is a config issue or something up with my system. Once my system is fully booted, I then have to login as "root" and then run the command:
dhcpcd eth0
Then my system gets the expected DHCP address. Why does this not happen during boot up? Why do I have to manually run this command everytime?
Here is my rc.conf:
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 10.1.1.1"
ROUTES=(!gateway)
Everything looks right and I would assume if it fails on boot up then it would fail when I attempt to run the command manually but thats not the case...
Please help!
./
Offline
Are you running kernel 2.6.27? I been seeing people have problems with their internet (including myself) after the kernel update
Registered User number: 496613. Show your Tux Pride!
http://counter.li.org
Offline
Fresh install this afternoon via ftp/http. It appeared to install the 2.6.27 kernel from base default.
./
Offline
I'm having the same problem since the kernel update yesterday.
Offline
./
Offline
I just updated to the latest kernel also and have this same problem: no dhcp on boot. i set it manually it works fine. This is the 2nd major issue i found with this kernel!! No sound and no dhcp on boot, and possible compiz install issues.
I tried running echo 0 > /proc/sys/net/ipv4/tcp_timestamps but get a echo write error : invalid argument. typed exactly as shown...
Arch64, AMD64, LXDE
Offline