| Summary: | dhcpcd started elsewhere during init | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | gentoo |
| Component: | [OLD] baselayout | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | decibels.2862, kanelxake, ladanyi |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
gentoo
2005-02-11 06:43:01 UTC
and if you disable hot/cold plugging does it work fine ? without coldplug: * Setting system clock to hardware clock dhcpcd[5809]: broadcasting DHCP_REQUEST for ... * Configuring kernel parameters ... * Setting terminal encoding to ASCII dhcpcd[5809]: timed out waiting for DHCP_ACK response dhcpcd[5809]: broadcasting DHCP_DISCOVER * Setting user font dhcpcd[5809]: DHCP_ACK received from (...) dhcpcd[5809]: No resolv.conf.sv to store * Starting lo ... after * Setting user font i've left out some lines Intersesting: reenabling coldplug fixed (for this one startup) the occuring messages, as expected: * Running dhcpcd dhcpcd: MAC address = ... dhcpcd: your IP address = * eth0 received address ... but still connection only after "/etc/init.d/net.eth0 restart" another reboot with coldplug enabled restores the initially described behavior Are you loading your NIC kernel *** This bug has been marked as a duplicate of 78495 *** What I meant to say is that hotplug is starting the network script by itself as in comment #2 it also "works" without hotplug/coldplug Doesn't matter - if hotplug is installed then what do describe will happen regardless of hotplug or coldplug being in any runlevels I encountered the same problem, and seem to have worked around it by *removing* the net.eth0 service from all runlevels. The prevents dhcpcd from trying to start a second time, and the rest of the network services start normally. I had hotplug in the default runlevel, but removing this and adding coldplug instead didn't make any difference. I have to load the network driver (sk98lin) in /etc/modules.autoload.d/kernel-2.6, otherwise it is never detected. This may be what is triggering dhcpcd to run before the net.eth0 script starts, but I'm not sure. Boy, same thing was happening to me today. Wasted a lot of time on it. Besides restarting the eth0, I could send dhcpcd a command it it would work. I thought it was the dhcp hostname at first, but then found that didn't matter either. Also unmerged dhcpcd and emerge dhcp and instead of "dhcpcd is already running on eth0" it would just be "dhclient is already running on eth0". At least that made me think it might be a init script, but couldn't find where. So to get it working had to: 1) /etc/init.d/net.eth0 restart 2) dhcpcd -h anyname eth0 (didn't matter what hostname gave) 3) dhcpcd -HD eth0 4) dhcpcd -d eth0 Probably any combination of dhcpcd commands would have worked. I ended up putting net.eth0 restart in the local.start just to get it up for them. The only problem after that, they would loose the internet connection after about 30 min or so. Did any of you test that out? Like it was setting the lease too short. I ended up taking the easy way out, cause had tried numerous things all day. Put a router on it and setup static ip's. "I have to load the network driver (sk98lin) in /etc/modules.autoload.d/kernel-2.6" I meant to add that I am using the sk98lin also, not the one from the kernel cause it doesn't work correctly, but from syskonnect. Seems to be fixed with baselayout-1.11.11 Thanks a lot, Marcus |
