never solved wonder problem

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

dhcpcd. what is it and why it so quirky?

here's what i've found:
dhcp from net.eth0 -- 2 minutes to fail.
dhcpcd from command line, first run -- 2 minutes, fail, but only some times...
dhcpcd from command line, second run -- 5 seconds, works
dhcpcd from command line, third run -- instant, works
dhcpcd from local.start -- sometimes works in 5 seconds, sometimes hangs computer.

i've had the netmount not started problem in the past and none of the posted solutions worked for that. i can post config files if needed. i've had this problem for 4 months.

pjp · Administrator Joined: 16 Apr 2002 Posts: 20584

dhcpcd is a dhcp client daemon used to get IP address information from a dhcp server.

You might consider something similar described in this thread for when you aren't using networking.
_________________
Quis separabit? Quo animo?

aetius · Tux's lil' helper Joined: 09 Jul 2004 Posts: 118

It would be enormously helpful if you could add the "-d" option to your /etc/conf.d/net dhcpcd option entry. This will log dhcpcd's attempts to obtain a DHCP-delivered address.

Also, we'll need to see the command lines you are running in each instance, or the /etc/conf.d/net file for starting from net.eth0.

Can we assume that you are always connected when bringing up the system? Is there a link to an older post?

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

no the issue is that i am using networking, but dhcdcd has erratic behavior -- sometimes it takes 2 minutes to fail, sometimes it works in 3 seconds... placing any dhcpcd call in the boot order will increase the boot time by 2 minutes...

i will attempt the -d option. who knows, maybe logging will somehow fix it...

i'll try to find my older post where i was trying to fix the "netmount not started" issue. IIRC it came down to a possible IRQ conflict. i figured there had to be some way to automatically fix this at boot because i could do it manually with the dhcp - kill - dhcp thing.

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

update, -d didn't really do much. it only listed my MAC address. possibly this means dhcpcd wasn't attempting to get an address? in anycase, with the extra dhcdpcd calls, it now works, albeit it takes an extra 2 minutes to boot... so i guess it didn't work.

conf.d/net:

ctford0 · Posted: Wed Jul 21, 2004 11:49 pm Post subject:

I had similar problems with my via-rhine card. I ended up having to compile the card in as a module and with the optional support for use MMIO instead of PIO that was available for the via-rhine module. So what I'm saying is that all of my problems related to the network turned out to be my fault for not compiling the correct support into the kernel.

chris

aetius · Tux's lil' helper Joined: 09 Jul 2004 Posts: 118

The purpose of using dhcpcd logging is not to fix the problem, but to find out why dhcpcd is having trouble getting an address. If you're waiting 2 minutes when it tries to start at boot, that usually means your attempt to obtain a DHCP address is failing and timing out. A successful session looks something like this (from /var/log/messages):

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

heh, semi-fixed.

i got love 2.6.8-rc2 to work. amazingly now dhcpcd -d gives a reason for failing (network down) and just fails, outright fails. no waiting, just fail. then my dhcpcd script works its magic and i've got a normal boot.

couple that with bootsplash even partially working, and 2.6.8 seems to be the saviour i hoped it was. if sound isn't messed up, i may just have to name my first child after 2.6.8!