Arch Linux

vorom

Member

Registered: 2015-01-11

Posts: 6

[SOLVED] Unable to connect to wired network during install

Having completed one Arch install easily enough, I'm trying my hand at a second, and I'm just about at wit's end trying to get the networking on.  The wireless isn't working, but I'll limit the scope of the post to the wired network, since that's what I mostly plan to be using, and it should be easier to get working in the first place.

My computer is connected to the router, which is successfully connecting several other devices, including a laptop running Arch to the internet.

I'm just coming from a Windows 7 install, where the wired network adapter worked perfectly.  Upon booting from a linux image on a USB drive, copied over via dd and downloaded via torrent, dhcpcd does not successfully connect automatically to the network.  So, I check the adapter's name, enp3s0, check to make sure it's active, and I try dhcpcd again:

#dhcpcd enp3s0
dhcpcd[2552]: version 6.6.7 is starting
DUID 00:01:00:01:1c:6b:da:fc:aa:14:04:7b:e0
enp3s0: IAID 14:04:7b:e0
enp3s0: soliciting an IPv6 router
enp3s0: soliciting a DHCP lease
enp3s0: Router Advetisement from fe80::222:75ff:fea0:5288
enp3s0: adding addresses 2002:c0a8:161:1234:9412:8928:a556:6d24/64
enp3s0: adding route to 2002:...:1234::/64
enp3s0: adding default route via fe80::222:75ff:fea0:5288
enp3s0: requesting DHCPv6 information
timed out
exited

I tried adding --timeout 60 to the arguments, and I sometimes managed to get a lease and a message about dhcpcd forking to the background, but I can't reproduce it at the moment with --timeout 0.  When I have managed to get a lease, I still typically get "unknown host" in response to pings, or connect:Network is unreachable.  Occasionally, usually after a 'successful' dhcp lease, I'll manage a timeout, and there was one brief moment in a long string of pings where my pings to google.com were returned within ~50ms.  I have also rarely sighted the computer on the dhcp client list on the router's side.  I have tried resetting the router to factory settings, which did not change the result.

Some basic outputs:

# ip link
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 65536 qdisc nonqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether fc:aa:14:04:7b:e0 brd ff:ff:ff:ff:ff:ff

lspci -v shows:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RLT8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
           Subsystem: Gigabyte Technology Co., Ltd Motherboard
           Flags: bus master, fast devsel, latency 0, IRQ 27
           I/O ports at d000 [size=256]
           Memory at fe8000000 (64-bit, non-prefetchable) [size=4K]
           Memory at d00000000 (64-bit, prefetchable) [size=16k]
           Capabilities: <snip>
           Kernel driver in use: r8169
           Kernel modules: r8169

I'm using a Belkin N+ as a router, if that could be relevant.

Last edited by vorom (2015-02-12 18:15:35)

vorom

Member

Registered: 2015-01-11

Posts: 6

Re: [SOLVED] Unable to connect to wired network during install

I solved the problem by connecting to the internet with another device, and installing the r8168 drivers for the ethernet controller.