[Solved] Cannot solicit DHCP lease via ethernet

Gazok · 2014-09-03 01:54:31

Edit

Made the mistake of posting without a thorough search. The problem is caused by the buggy r8169 module. Fixed according to https://bbs.archlinux.org/viewtopic.php?id=101836 using the 8168 package from the AUR. If this solution doesn't work for you, there are other possible solutions discussed here.

Original post

I recently replaced my old motherboard with a GIGABYTE 990XA-UDP. Since then, with a fresh install of Arch (or any linux-based distro), dhcpcd is unable to successfully connect to my home network. On Windows 7, everything functions correctly.

Connecting my laptop via the same ethernet cable, everything works fine:

$ sudo dhcpcd -4
dhcpcd[13699]: version 6.4.3 starting
dhcpcd[13699]: DUID 00:01:00:01:19:95:67:c6:60:d8:19:d3:19:b1
dhcpcd[13699]: enp1s0: IAID f1:e4:6b:3f
dhcpcd[13699]: enp1s0: soliciting a DHCP lease
dhcpcd[13699]: enp1s0: offered 192.168.1.9 from 192.168.1.1
dhcpcd[13699]: enp1s0: leased 192.168.1.9 for 86400 seconds
dhcpcd[13699]: enp1s0: adding route to 192.168.1.0/24
dhcpcd[13699]: enp1s0: adding default route via 192.168.1.1
dhcpcd[13699]: forked to background, child pid 13760

On my desktop:

~  ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 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 pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 74:d4:35:96:be:a2 brd ff:ff:ff:ff:ff:ff

~  sudo dhcpcd -4
dhcpcd[4259]: version 6.4.3 starting
dhcpcd[4259]: DUID 00:01:00:01:1b:96:be:4c:24:3c:20:07:a5:93
dhcpcd[4259]: enp3s0: IAID 35:96:be:a2
dhcpcd[4259]: enp3s0: soliciting a DHCP lease
dhcpcd[4259]: timed out
dhcpcd[4259]: forked to background, child pid 4301

I also attempted static routing according to the Beginner's Guide, using both the suggested nameservers and Google's 8.8.8.8. This yielded a connection which would typically last around a minute before mysteriously going down again.

I expect that this is a hardware issue, but before going down that route, I was wondering if anyone has any suggestions for troubleshooting this.

Thanks.

Last edited by Gazok (2014-09-03 16:24:25)

loqs · 2014-09-03 12:59:40

Seems similar to https://bbs.archlinux.org/viewtopic.php?id=186255

Trilby · 2014-09-03 13:35:36

Gazok - no worries about finding the solution only after you posted. I frequently am only able to do the correct searches after I have taken the time to clearly elaborate the problem. So simply posting clearly often leads to the solution.

If this is fully resolved please mark the thread as [SOLVED] so others may find it as a resource. If it is not could you breifly highlight what still needs to be acheived?

Gazok · 2014-09-03 16:26:41

@Trilby: Just came back to mark [Solved]. I finished this up at 5AM and didn't remember @_@. Thanks

Arch Linux

#1 2014-09-03 01:54:31

[Solved] Cannot solicit DHCP lease via ethernet

#2 2014-09-03 12:59:40

Re: [Solved] Cannot solicit DHCP lease via ethernet

#3 2014-09-03 13:35:36

Re: [Solved] Cannot solicit DHCP lease via ethernet

#4 2014-09-03 16:26:41

Re: [Solved] Cannot solicit DHCP lease via ethernet

Board footer