Arch Linux

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Fresh install and dhcp not working during boot [SOLVED].

Hi All

I have finally switched my main box over to arch.  The install went without a hitch except that eth0 does not come up during boot.  Checking the logs gives:

May 28 14:08:30 delos dhcpcd[3151]: timed out waiting for a valid DHCP server response

However, I can start the network without issue once I log in.

/etc/rc.d/network start

Can anyone give me a hint as to what to do next?

Thanks
Kevin

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: Fresh install and dhcp not working during boot [SOLVED].

do you have network loading before hotplug? Please post your /etc/rc.conf.

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

Hi There

Below is my rc.conf and hotplug is before network.  Is that OK!

Kev

HARDWARECLOCK="localtime"
TIMEZONE=Canada/Pacific
KEYMAP=us
CONSOLEFONT=
USECOLOR="yes"
USELVM="no"
HOSTNAME="delos"
MODULES=(!usbserial !ide-scsi eepro100 radeon)
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(!gateway)
DAEMONS=(syslog-ng hotplug !pcmcia network netfs crond sshd)

iBertus

Member

From: Greenville, NC

Registered: 2004-11-04

Posts: 2,228

Re: Fresh install and dhcp not working during boot [SOLVED].

That should be fine. Does hotplug correctly detect your ethernet hardware and load the proper module? Is this DHCP server one provided by an ISP?

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

The dhcp server is a linksys router (BEFSR41) and lsmod shows that eepro100 is loaded when I login.  I guess this means that hotplug worked.  Any more thoughts?

Thanks
Kevin

iBertus

Member

From: Greenville, NC

Registered: 2004-11-04

Posts: 2,228

Re: Fresh install and dhcp not working during boot [SOLVED].

Ensure that the router is configured for dhcp and that you have the correct number of clients specified in the dhcp config. If know for sure that eepro100 is the correct ethernet module you can just put that in your MODULES array in rc.conf to save any guesswork.

Last time I had any dhcp problems with one of those routers it was because of a bad router config.

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

Is there any clues in the fact that I can start "network" manually?  I haven't touch the router config in quite a while and I simple switched distros.

One thing to add that I hadn't noticed is that hotplug loads e100 not eepro100. I had added eepro100 to MODULES, so that is why it was there. I removed eepro100 from MODULES and I have the same issue.  That is, network won't start at boot but I can start it by hand.

Thanks
Kev

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: Fresh install and dhcp not working during boot [SOLVED].

You can add any modules you don't want to load in /etc/hotplug/blacklist, then add the one you want in MODULES() array. THat might help narrow down the module. Maybe its one that hotplug isn't loading, but really the one you explicitly told to load in modules() and the other from hotplug screwed it up. What does dmesg | grep eth0 give you? This is a very strange problem...Any other info you can provide about the matter would help.

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

Hi There

This is the output with e100 loaded,

e100: eth0: e100_probe: addr 0xdfffe000, irq 5, MAC addr 00:D0:B7:4D:AA:AD
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth0: no IPv6 routers present

and this is the output with e100 blacklisted with eepro100, which is the modules that I used in my previous distro.

eth0: 0000:00:0b.0, 00:D0:B7:4D:AA:AD, IRQ 5.
eth0: no IPv6 routers present

I am guessing that "eth0: no IPv6 routers present" means something.  Both modules have the same results.  Doesn't work at boot but I can start them manually.

Any thoughts,
Kev

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: Fresh install and dhcp not working during boot [SOLVED].

Your e100 module looks more similar to the output of my tg3 module than the other with the full duplex messages. IPv6 is a new internet protocol that is rarely used so, it should say not present. I really have no other suggestions than to be sure your system is up-to-date (pacman -Syu), disconnect any other nic cards you may have, and/or maybe to try reinstalling as a last resort.

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

I was hoping to avoid a reinstall - I don't get much time with two small children and a car restoration.  Anyway, here is yet another interesting observation.  I completely disabled networking and started it manually.

[root@delos ~]# /etc/rc.d/network start
:: Starting Network                                                      [FAIL]
[root@delos ~]# /etc/rc.d/network start
:: Starting Network                                                      [DONE]
[root@delos ~]#

The first try fails and the second works.  The logs show that dhcpcd timeout out at the first attempt.

Kev

iKevin

Member

From: Ann Arbor, MI

Registered: 2003-07-20

Posts: 132

Re: Fresh install and dhcp not working during boot [SOLVED].

Well, I finally got it to work, though I don't know why it was an issue.  I had the router configure for a maximum number of DHCP clients of 3 (I have 3 computers).  I just set that number to 10 and it worked. 

I just don't get it.

Thanks for all your help.
Kevin

T-Dawg

Forum Fellow

From: Charlotte, NC

Registered: 2005-01-29

Posts: 2,736

Re: Fresh install and dhcp not working during boot [SOLVED].

:shock:
Maybe the controller module is wrong....
You could try the testing kernel, maybe that'll work.