[SOLVED] DHCP error during install due to multiple net cards

AMA · 2009-05-03 17:18:32

Hello all,

At the "Setup Network" option during the installation, I choose eth0. Then it asks if I want to use DHCP. I select 'Yes' but get

Failed to run dhcpcd. See /dev/tty7 for details

while polling for DHCP. So I press Alt+F7 and the details are

eth0: dhcpcd 4.0.10 starting
eth0: waiting for carrier
eth0: timed out

When I try to manually set it up (ie select 'No' when asked if I want to use DHCP), it asks for the following: IP address, submask, broadcast, Gateway (optional), DNS Server. Then it says "Network is configured" but I still can't download the packages.

I have a Realtek RTL8139 Family PCI Fast Ethernet NIC card (not wireless) to a Linksys Router. I've set up DHCP on it for 5 users (only two being used). By the way I have WinXP on the same computer which accesses the network fine, and net access also worked during other distros' installation.

Any clues? Thanks.

Last edited by AMA (2009-05-11 13:17:53)

ralvez · 2009-05-03 17:33:58

OK, if I understand the situation this is what you need to do.
1. in /etc/rc.conf you should have (for static IP):

                                                
                                                        
eth0="eth0 192.168.1.21 netmask 255.255.255.0 broadcast 192.168.1.255"   
INTERFACES=(lo eth0)
.
.
.
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

Notice that I choose 192.168.1.x but you can use whatever matches your router's settings. The default gateway points to the green (LAN) address of the router.

2. Also make sure that /etc/resolv.conf has the addresses of your router:
nameserver 192.168.1.1
or if your router is not providing the DNS resolution then add the nameververs your provider gave you, like this:
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx

If you want to use DHCP then use:

eth0 ="dhcp"
.
.
.
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)  <-- Notice the ! before the word gateway (this is important)

In this case the /etc/resolv.conf should be handled by the DCHP server.

Hope this helps.

R.

Last edited by ralvez (2009-05-03 17:35:50)

AMA · 2009-05-03 17:58:48

Thanks for your answer. However, I don't quite understand. My problem occurs during the installation. I don't have access to /etc/rc.conf as I have no Linux OS installed on the computer yet, just a Windows partition.

ralvez · 2009-05-03 18:05:14

I see.
Then try this:
1. Type: "ifconfig eth0 192.168.1.21" (or whatever static address you want to give the Nic)
2. type: "route add default gw 192.168.1.1 eth0 " (use your default gateway here)
3. type: echo "nameserver 234.45.567.89" > /etc/resolv.conf (use the one your ISP gave you)

And that should get your card up and running.

R.

Last edited by ralvez (2009-05-03 18:06:45)

AMA · 2009-05-03 18:23:21

I've done what you said, but the result is still the same "Failed to run dhcpcd" and ping doesn't return anything.

ralvez · 2009-05-03 18:33:41

The way I outlined in my last post does not use DHCP it results in a static address.

What is the result of ifconig?

R.

AMA · 2009-05-03 18:43:53

Please excuse me, I'll type the result of ipconfig (a quite big paragraph) tomorrow, too tired now.

AMA · 2009-05-04 08:43:56

Here's the result of ifconfig:

eth0       Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
           inet addr:172.30.201.6  Bcast:172.30.201.255  Mask 255.255.255.0
           UP 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)

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Does it help?

By the way, in Windows, when I type ipconfig/all in cmd, there's a line with "DHCP Enabled..........: Yes" and another with "DHCP Server..........................: 172.30.201.6". I just don't understand why can't I use DHCP during the install?

ralvez · 2009-05-04 11:23:29

OK. You have an IP address, so that rules out a problem with your Nic card.
Can you explain what are you doing to install Linux? Do you try to run the CD from within Windows or are you placing the CD in the CD bay and re-booting the machine and the CD fails?

R.

AMA · 2009-05-04 12:47:25

ralvez wrote:

OK. You have an IP address, so that rules out a problem with your Nic card.

Sorry I was maybe a little bit unclear on my previous post, but I'm pretty sure that I don't have an IP address during installation. I would like to add some precisions. Here are my observations:

When I type ifconfig immediately after login (as root), it shows

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Then when I run /arch/setup, Configure Network, answer 'Yes' to DHCP, and after the error message (the one on 1st post), ifconfig gives this (which clearly shows that I do NOT have an IP)

eth0       Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
           UP 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)

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Finally, when I answer 'No' to the DHCP question, and after I've entered my IP/Broadcast/Subnet Mask/DNS addresses, the result of ifconfig is the one on the previous post, that is

eth0       Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
           inet addr:172.30.201.6  Bcast:172.30.201.255  Mask 255.255.255.0
           UP 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)

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

NB: I have entered the same addresses that I use normally (ie with Windows, the ones I see in cmd->ipconfig /all), but I could have entered whatever addresses I wanted. And I still don't have net access during install (ping does not return anything).

Can you explain what are you doing to install Linux? Do you try to run the CD from within Windows or are you placing the CD in the CD bay and re-booting the machine and the CD fails?

Of course I am booting the cd at startup (not within windows)! And the CD does not fail, or at least does not seem. Everything runs fine except the DHCP thing. So the problem is not the CD, but my computer. I'm finding a way to get DHCP working during the installation.

AMA · 2009-05-04 17:01:41

At the beginning of the installation, a message says that I can load the ethernet modules manually on another console.

How do I do that?

Thanks.

ralvez · 2009-05-04 21:54:34

Ama,

It may be that your card NIC is not recognized by Linux and therefore does not load. I have _NEVER_ had such a situation, except waaaaaay back (read +/- 8 years) when things were not as up to date with drivers.
To load the drivers you would have to have Linux drivers for your NIC, do you? Do you know what card is it?

Are you behind a firewall? The address you give does not seem to be in the private rage (172.16.x.x) or is that just an example?

R.

AMA · 2009-05-05 04:52:03

ralvez wrote:

Ama,
It may be that your card NIC is not recognized by Linux and therefore does not load.

It may be that my NIC is not recongized by Arch only, because there were no network problems during Ubuntu installation.

By the way, as written in the first post, my card is a Realtek RTL8139 Family PCI Fast Ethernet NIC. I'm not behind a firewall. And also, the addresses I gave are the real addresses I use now.

Don't hesitate if you need more info.

yingwuzhao · 2009-05-05 05:49:30

Hey, if your net card light is off during your installation, that means the "wake on lan" feature is off, thus you need to turn it on first before your installation.

Turn the "wake on lan" in bios, and you might need to look for it a little bit, it have different names in different bios.
Or
If your old system is still bootable, boot into it and pacman -S ethtool and do:

sudo ethtool -s eth0 wol g

See my post here:
http://bbs.archlinux.org/viewtopic.php?id=69733

:)

AMA · 2009-05-05 07:04:45

Hi yingwuzhao,
thanks for your answer, but unfortunately it still doesn't work. I enabled the "Wake-up on LAN" option is BIOS, restarted the installation twice, prayed in front of the screen, but still the same error.
Also, my NIC green light has always been on during the installation (before and after I enabled wol).

Don't hesitate if you need more info.

R00KIE · 2009-05-05 10:14:57

I have seen reports here on the forum of other people not being able to get a proper network configuration when using dhcp + dhcpcd even with the system already installed.

On my real system everything works fine but when using virtualbox dhcpcd gets everything right except the dns servers.

As a workaround, take not of the ip/route you get in a system that works, algo take note of the dns servers being used then input that manually on arch setup. After you get it working then install dhclient which seems to work fine when dhcpcd fails, the only drawback (that I could see) is that the normal network setup of arch cannot be used (as in configuring things in rc.conf).

dunz0r · 2009-05-05 10:59:13

Your network card is supported. That particular card is one of the most common chipsets around.

ralvez · 2009-05-05 11:42:03

Ama,

The previous answers told you essentially what I would have, so no need to re-iterate.
What I would do at this stage is, as Rookie sugested:

1. Type: "ifconfig eth0 172.30.201.6"
2. type: "route add default gw 172.30.201.1 eth0 " (or if you are not sure that is the correct IP then type "route" to get the IP used by your system)
3. type: echo "nameserver 234.45.567.89" > /etc/resolv.conf (use the ones your windows system has)

and you should have a system ready to go.

You can, after you install Arch, keep the same addresses in /etc/rc.conf (which will make your system run on a static IP) and you will be fine.

Hope this helps.

R.

AMA · 2009-05-05 14:26:42

Hello ralvez, I've tried again, exactly as you told, but still not net access .
Here's my Windows ipconfig /all, maybe it could help

Windows IP Configuration
        Host Name . . . . . . . . . . . . : ama
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : lan
        Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
        Physical Address. . . . . . . . . : 00-19-E0-19-53-95
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 172.30.201.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.30.201.6
        DHCP Server . . . . . . . . . . . : 172.30.201.6
        DNS Servers . . . . . . . . . . . : 202.106.195.68
                                            202.106.46.151
        Lease Obtained. . . . . . . . . . : mardi 5 mai 2009 21:49:42
        Lease Expires . . . . . . . . . . : mercredi 6 mai 2009 21:49:42

And I've noticed one thing : the MAC address displayed here is NOT the same MAC address I see during the installation (ie when I need to choose which ethernet to use, in my case I only have one choice which is eth0, but next to 'eth0' is displayed the MAC address of eth0, and I'm absolutely sure it's different from the one I see in ipconfig in Windows).

Oh and I would like to add that I have several net cards on the computer:
- 1394 Net Adapter
- Toshiba Wireless LAN Mini PCI Card
- Intel(R) PRO/100 VE Network Connection
- Realtek RTL8139 Family PCI Fast Ethernet NIC

I'm only using the last one, the three others are disabled under Windows. I thought maybe Arch loaded the third card, and maybe that's why it didn't work.

Hope to finish with this problem soon...

ralvez · 2009-05-05 21:59:02

Ama,

If you did put things "exactly" as I posted it, it _had_ to fail because there were some things that do not match your settings... I sort of sent a `best guess` example.
This is what you should use, given the information you just sent:

1. Type: "ifconfig eth0 172.30.201.101"
2. Type: "route add default gw 172.30.201.6 eth0 "
3. Type: echo "nameserver 202.106.195.68" > /etc/resolv.conf

and try again.

Now just to be sure it works, after you run all those commands, please run "ifconfig" and "route" and post the results so I can make sure all is at is should be.

Hope this helps.

R.

AMA · 2009-05-06 11:44:58

Hello ralvez, thanks again for your help, I really appreciate your patience, but unfortunately it still fails to access the net.
Here's (exactly) what I've done:

[root@archiso ~]# ifconfig eth0 172.30.201.101
[root@archiso ~]# route add default gw 172.30.201.6 eth0
[root@archiso ~]# echo "nameserver 202.106 195.68" >/etc/resolv.conf
[root@archiso ~]# ifconfig
unionfs: new lower inode mtime (bindex=0, name=etc)
eth0       Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
           inet addr:172.30.201.101  Bcast:172.30.255.255  Mask 255.255.0.0
           UP 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)

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
[root@archiso ~]# route
Kernel IP routing table
Destination  Gateway         Genmask      Flags  Metric  Ref  Use  Iface
172.30.0.0   *               255.255.0.0    U       0     0    0   eth0
default      172.30.201.6    0.0.0.0        UG      0     0    0   eth0

Notice that it's the first time that I see the the first line of ipconfig (the unionfs line) : are we getting closer?:)

But then I saw that the subnet mask was not correct, so I started the installation over again, and done this:

[root@archiso ~]# ifconfig eth0 172.30.201.101 netmask 255.255.255.0
[root@archiso ~]# route add default gw 172.30.201.6 eth0
[root@archiso ~]# echo "nameserver 202.106 195.68" >/etc/resolv.conf
[root@archiso ~]# ifconfig
unionfs: new lower inode mtime (bindex=0, name=etc)
eth0       Link encap:Ethernet HWaddr 00:00:39:63:8C:EE
           inet addr:172.30.201.101  Bcast:172.30.201.255  Mask 255.255.255.0
           UP 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)

lo         Link encap:Local loopback
           inet addr:127.0.0.1  Mask 255.0.0.0
           UP LOOPBACK RUNNING MTU:16436  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:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
[root@archiso ~]# route
Kernel IP routing table
Destination  Gateway         Genmask      Flags  Metric  Ref  Use  Iface
172.30.201.0 *               255.255.255.0  U       0     0    0   eth0
default      172.30.201.6    0.0.0.0        UG      0     0    0   eth0

Any clues?

PS: Should I post this thread in the "Networking, Server, and Protection" forum?

R00KIE · 2009-05-06 12:20:30

It sounds a lot like you need to try this http://wiki.archlinux.org/index.php/Con … _WOL_issue

AMA · 2009-05-06 16:12:39

've got some news here. Bad news and good news.

First the bad news. I've enabled WOL as ROOKIE suggested (methods 2 and 4 of the wiki), but the same problem persists.

Then the good news. As I've told, I have more than one NIC on my PC (see post #19):
- 1394 Net Adapter (no idea what it's for)
- Toshiba Wireless LAN Mini PCI Card
- Intel(R) PRO/100 VE Network Connection
- Realtek RTL8139 Family PCI Fast Ethernet NIC
I've enabled all of them (in Windows XP) and ipconfig /all gives:

Windows IP Configuration
        Host Name . . . . . . . . . . . . : ama-459a51cfdfd
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : lan
        Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
        Physical Address. . . . . . . . . : 00-19-E0-19-53-95
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 172.30.201.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.30.201.6
        DHCP Server . . . . . . . . . . . : 172.30.201.6
        DNS Servers . . . . . . . . . . . : 202.106.195.68
                                            202.106.46.151
        Lease Obtained. . . . . . . . . . : mercredi 6 mai 2009 23:44:34
        Lease Expires . . . . . . . . . . : jeudi 7 mai 2009 23:44:34

Ethernet adapter Local Area Connection 2:
        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
        Physical Address. . . . . . . . . : 00-00-39-63-8C-EE

Ethernet adapter Wireless Network Connection:
        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Toshiba Wireless LAN Mini PCI Card
        Physical Address. . . . . . . . . : 00-02-2D-69-31-74

The thing is that during the installation, on the "Setup network" page, I _normally_ have a choice between several NICs (eth0, eth1...), well in my case there was only one choice, namely eth0, and next to it was displayed the MAC address of eth0, which appeared to be.........00-00-39-63-8C-EE ! That corresponds to the Intel card, which I don't use at all.
So my conclusion (which was a hypothesis in post #19) is that Arch does not load the Realtek card during installation. I should have two choices during at that stage.

However, the strange part is that the NIC's green light is on during installation. At bootup it's off, and turns on when Arch prepares the installation, precisely during udev uevents. There's also something I didn't mention, that is the fact the Udev uevents takes a long time to finish (around 180000ms !) and now I think that it's because it's trying to load the Realtek card, but can't. Why?

It's not real good news, I admit. But at least I know where the problem is. So I'm turning towards you, great members of the Arch Community. Is there a way to let Arch load the NIC (maybe manually) ?

Thanks in advance.

karol · 2009-05-06 19:07:16

Is your network running now?
There's a problem w/ network interfaces swap at boot - I have two cards, but I only use one and when I have only eth0 specified as my interface I have about 50% chances of having network running. Otherwise I have to start it manually

dhcpcd eth0

If I get "waiting for carrier" I kill it w/ Ctrl-C and

dhcpcd eth1

I get "broadcasting for a lease" and all goes well.

I think I'm just going to take the other card out :-) but you are free to google for some better ways to solve it.

ralvez · 2009-05-06 22:11:49

Ama,

karol's idea may be a good way to go, since your problems may arise due to the multiple cards in the system.
Give it a try and let us know it it works.

R.

Arch Linux

#1 2009-05-03 17:18:32

[SOLVED] DHCP error during install due to multiple net cards

#2 2009-05-03 17:33:58

Re: [SOLVED] DHCP error during install due to multiple net cards

#3 2009-05-03 17:58:48

Re: [SOLVED] DHCP error during install due to multiple net cards

#4 2009-05-03 18:05:14

Re: [SOLVED] DHCP error during install due to multiple net cards

#5 2009-05-03 18:23:21

Re: [SOLVED] DHCP error during install due to multiple net cards

#6 2009-05-03 18:33:41

Re: [SOLVED] DHCP error during install due to multiple net cards

#7 2009-05-03 18:43:53

Re: [SOLVED] DHCP error during install due to multiple net cards

#8 2009-05-04 08:43:56

Re: [SOLVED] DHCP error during install due to multiple net cards

#9 2009-05-04 11:23:29

Re: [SOLVED] DHCP error during install due to multiple net cards

#10 2009-05-04 12:47:25

Re: [SOLVED] DHCP error during install due to multiple net cards

#11 2009-05-04 17:01:41

Re: [SOLVED] DHCP error during install due to multiple net cards

#12 2009-05-04 21:54:34

Re: [SOLVED] DHCP error during install due to multiple net cards

#13 2009-05-05 04:52:03

Re: [SOLVED] DHCP error during install due to multiple net cards

#14 2009-05-05 05:49:30

Re: [SOLVED] DHCP error during install due to multiple net cards

#15 2009-05-05 07:04:45

Re: [SOLVED] DHCP error during install due to multiple net cards

#16 2009-05-05 10:14:57

Re: [SOLVED] DHCP error during install due to multiple net cards

#17 2009-05-05 10:59:13

Re: [SOLVED] DHCP error during install due to multiple net cards

#18 2009-05-05 11:42:03

Re: [SOLVED] DHCP error during install due to multiple net cards

#19 2009-05-05 14:26:42

Re: [SOLVED] DHCP error during install due to multiple net cards

#20 2009-05-05 21:59:02

Re: [SOLVED] DHCP error during install due to multiple net cards

#21 2009-05-06 11:44:58

Re: [SOLVED] DHCP error during install due to multiple net cards

#22 2009-05-06 12:20:30

Re: [SOLVED] DHCP error during install due to multiple net cards

#23 2009-05-06 16:12:39

Re: [SOLVED] DHCP error during install due to multiple net cards

#24 2009-05-06 19:07:16

Re: [SOLVED] DHCP error during install due to multiple net cards

#25 2009-05-06 22:11:49

Re: [SOLVED] DHCP error during install due to multiple net cards

Board footer