[SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

trusktr · 2010-06-29 21:47:49

I can't get my network running for the life of me on a new install.

network daemon fails at boot and if i try setting up the network as described in various places in the wiki, i get "dhcpcd: timed out".

I've double checked all of my settings. My Arch on my desktop works just fine. I just can't get the network to work on this laptop.

Any ideas? Thanks.

Last edited by trusktr (2010-07-28 20:14:07)

ralvez · 2010-06-29 22:02:01

Yup ... for starters you have to be more specific
What type of connection are you working on Wifi or wired?
What is the result of "ifconfig" what's the output of "route"

What type of physical card do you have?

R.

trusktr · 2010-06-29 22:12:06

It's just the wired connection (eth0).

ifconfig eth0:

eth0      Link encap:Ethernet  HWaddr 00:30:67:5E:2C:72
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0x2000

It's clearly missing the inet addresses that should (it would seem) appear automatically with no problems straight out of the box with the correct settings (rc.conf, hosts, etc).

The card i'm using: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
The driver in use by the kernel: natsemi
module: natsemi

Last edited by trusktr (2010-06-29 22:12:59)

hokasch · 2010-06-29 22:21:38

Can you connect with a static adress from command line? Any related messages in dmesg?

edit: if you suspect a bug in dhcpd, try dhclient. example for setting static IP:

#ifconfig eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
#route add default gw 192.168.0.1

Last edited by hokasch (2010-06-29 23:03:26)

karol · 2010-06-29 22:32:57

How do you connect to the internet? It can be a hardware problem - is the cable working? Try the one you use for your desktop.
What's the exact problem w/ dhcpcd - is it broadcasting for a lease and timing out or sth else?

Mr.Elendig · 2010-06-29 22:43:25

ifconfig -a and iwconfig output please.

combuster · 2010-06-29 23:03:21

I had to increase timeout value from 2 to 30 in network script inside /etc/rc.d for dhcpcd to obtain an IP. I'm using wireless but u can try it too and see if it fixes your problem with ethernet connection.

In your case, you could try to add the following to /etc/conf.d/dhcpcd

DHCPCD_ARGS="-q -t 10"

trusktr · 2010-06-29 23:17:34

That's the thing, I don't connect to the internet. This is a brand new install. There's no way for me to download dhclient or any other packages (like firmware for my wireless for example) without first having a connection.

There are only two messages in dmesg relating to eth0: one that shows the "natsemi" driver loaded, and the other that says "DSPCFG accepted after 0 usec".

Mr.Elendig, ifconfig is already shown above, i have only omitted the "lo" interface. iwconfig is not necessary because i'm not using wireless.

dhcpcd times out while "Broadcasting for a lease".

I'll try your suggestion combuster and see what happens.

ralvez · 2010-06-29 23:24:51

You clearly are not getting an address, as you well pointed out.
What's the output of su -c 'mii-tool', that should tell us whether or not your card is negotiating for an address or not even connecting at all.

R.

trusktr · 2010-06-29 23:32:33

hey ralvez, that command shows "eth0: no link"

karol · 2010-06-29 23:40:03

> This is a brand new install.
What was previously installed on this notebook? Any problems with the wired internet? If you've recently used it (before you've installed Arch) and it was fine, we're 99% sure it's not a hardware failure of the card. Maybe it's the ethernet cable - did you check it?

How 'bout

su -c 'mii-tool -vv'

Last edited by karol (2010-06-29 23:46:02)

ralvez · 2010-06-29 23:51:02

trusktr wrote:

hey ralvez, that command shows "eth0: no link"

OK then... it may be a problem with your card.
Or the driver you are using does not work with the card or it could also be a cable problem.'

R.

Edit: BTW what's the configuration of your /etc/rc.conf?

Last edited by ralvez (2010-06-29 23:54:31)

trusktr · 2010-06-29 23:59:36

Hey karol, that command seems to show everything fine except for the "no link".

The previous OS was Windows XP and it worked with the same cable and card, no hardware difference. The cable also works on my other desktop.

If it happens to be the driver, ralvez, how would i go about installing the correct one with no connection? Would i have to add it to the install ISO?

karol · 2010-06-30 00:35:48

According to http://hardware4linux.info/component/19239/ natsemi is the correct driver for your card.
http://hardware4linux.info/module/natsemi/ show almost not problems w/ the driver.

If you're using a hub/switch/router, try inserting the cable into another another socket.

Post your /etc/resolv.conf.

harryNID · 2010-06-30 00:39:03

Hi trusktr

This might seem stupid but are you sure you are using "eth0" and not "eth1" etc.? As an example I have two on-board lans and I'm plugged into eth1. I had to change rc.conf as it defaults to using eth0.

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(eth1)

Since I am using eth1 and not eth0 here is what I get when I try:

ifconfig eth0:

eth0 Link encap:Ethernet HWaddr 00:04:4B:00:88:0E
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:23 Base address:0x6000

Look familiar?

I'm not saying this is the case but it could be something as simple as that.

ifconfig -a

should show you how many lans you have.

Thought I would drop the obvious first in case that's all it is.

trusktr · 2010-06-30 00:48:37

My resolv.conf is empty:

# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line

I only have one socket to connect to on the back of the laptop.

I also tried using eth1 in rc.conf but that didn't work and it said the interface was not detected. ifconfig -a shows only eth0.

This is so strange!

karol · 2010-06-30 00:51:39

> I only have one socket to connect to on the back of the laptop.
I meant the socket in your hub/switch/router if you're using one.

What kind of notebook is that?

Last edited by karol (2010-06-30 00:53:06)

trusktr · 2010-06-30 00:56:32

Oh, lol, let me try that Karol, although the router light is on for that socket.

The notebook is a Compaq (hp) Presario 2182.

I also tried increasing the timeout for dhcpcd (-t 30) but that didn't work.

Last edited by trusktr (2010-06-30 01:11:22)

trusktr · 2010-06-30 00:59:41

Changing the socket didn't seem to work.

karol · 2010-06-30 01:50:17

What kind of notebook is that?
Post your rc.conf.

trusktr wrote:

There's no way for me to download dhclient or any other packages (like firmware for my wireless for example) without first having a connection.

You can use your desktop. A bit tedious but doable.

Is it possible that eth0 is the wireless interface?

ralvez · 2010-06-30 02:12:46

Assuming your driver is not corrupted or something then post your /etc/rc.conf
You should have it configured to run DHCP like this:

eth0="dhcp"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(!gateway) <-- Notice the ! before gateway (DHCP will configure the gateway and your /etc/resolv.conf)

R.

karol · 2010-06-30 02:14:38

> Assuming your driver is not corrupted or something
Checksum the iso you downloaded and maybe "simply" reinstall the system.

trusktr · 2010-06-30 02:29:58

Yeah, my rc.conf looks exactly like that, trust me, but thanks for the advice ralvez.

Seems like there is some bug or error somewhere. I'll check the sums when i get home in a bit. good idea Karol. I don't think that eth0 is the wireless device though because dmesg shows it as wlan0.

So far this is the 4th install of Arch i've ever performed. The last all worked just fine with no problems.

ralvez · 2010-06-30 02:42:40

Well ... one thing you can do for a test is download Linux Mint live CD and run it.
If it connects and works fine in general then take a look at what driver it's using.
I've done things like that in the past when I find a problem that seem lacking in "logical solutions" so I have a new "point of reference".

Hope this helps.

R

trusktr · 2010-06-30 02:54:11

Cool, good idea ralvez. I'll try it when I get home.

Arch Linux

#1 2010-06-29 21:47:49

[SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#2 2010-06-29 22:02:01

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#3 2010-06-29 22:12:06

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#4 2010-06-29 22:21:38

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#5 2010-06-29 22:32:57

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#6 2010-06-29 22:43:25

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#7 2010-06-29 23:03:21

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#8 2010-06-29 23:17:34

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#9 2010-06-29 23:24:51

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#10 2010-06-29 23:32:33

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#11 2010-06-29 23:40:03

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#12 2010-06-29 23:51:02

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#13 2010-06-29 23:59:36

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#14 2010-06-30 00:35:48

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#15 2010-06-30 00:39:03

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#16 2010-06-30 00:48:37

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#17 2010-06-30 00:51:39

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#18 2010-06-30 00:56:32

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#19 2010-06-30 00:59:41

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#20 2010-06-30 01:50:17

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#21 2010-06-30 02:12:46

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#22 2010-06-30 02:14:38

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#23 2010-06-30 02:29:58

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#24 2010-06-30 02:42:40

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

#25 2010-06-30 02:54:11

Re: [SOLVED] "dhcpcd: timed out" on a new Arch Install. Very wierd... Bug?

Board footer