[Solved with dhcpcd-5.1.5-1] dhcpcd-5.1.4-1, timed out

Question

Hello,
I experienced a timed out issue with the new release of dhcpcd. When launched, it indicates a time out, so it can't get information about the network. Downgrading to dhcpcd-5.1.3-1 is the only fix I found.
Is anyone else experiencing this upgrade issue ?
My ethernet card :
Ethernet controller: nVidia Corporation nForce2 Ethernet Controller
Last edited by keronn (2010-02-04 08:17:09)

Answer 1

I have the same problem. Thought it had something to do with the new version of dhcpcd, so I did a fresh install (it's a test machine), added dhcpcd in the IGNORE list and updated the system. The version of dhcpcd is 4.0.10-1 and the kernel is 2.6.32.3-1
Upon first reboot after the system update eth0 received an address, but every reboot since I experience the timeout problem. The DHCP server does acknowledge the test-machine, but the test-machine doesn't apply the address. Anyway it seems the problem isn't dhcpd as such, maybe a problem with a network driver in 2.6.32?
Edit:
Hmm.. There's 2 NIC's in the test-machine, but it seems random which module is loaded first and apparently what interface get the name eth0 and eth1. I remember that listing the modules in the right order in rc.conf can help, and upon reboot the test-machine correctly received a DHCP address! There's just one strange thing.. The 2. NIC (eth1) is set to a static address, but during my "debugging" I set it to DHCP so both NIC's should get an address from DHCP. However, when restarting the network ifconfig still reported that eth1 was set to the static address?? How could the static address be used when I commented that line out? As if rc.conf was not read?
Edit2:
So besides the weird static address thing (which doesn't matter now), DHCP works every time now when rebooting. BUT this is with the old dhcpcd. I haven't tried upgrading it and dhcpcd is still ignored in pacman.conf. Now that the test-machine is behaving I think I'll let it be, sorry to be such a chicken.. I'll keep an eye on this issue and hope it'll work with a new version of dhcpcd soon.
Last edited by numasan (2010-01-20 21:58:19)