Can't set interface state to UP!

LonelyArchFan · 2016-03-12 11:33:49

Hi!

Problem: Recently, maybe because of the recent Linux 4.4.5-1-ARCH kernel update, I can't use "ip link set enp2s0 up" or any other commands like it to set my ethernet interface to up.
I'm having this issue on a custom-built PC with a Realtek ethernet controller (kernel driver: r8169) which is built into the motherboard and a Rosewill N900PCE PCI-Express Wi-Fi adapter (kernel driver: ath9k).

When I run the above command, or the same command targeting wlp3s0 instead, I don't get any output at all, just like what would happen if it had worked.
I have the dhcpcd@enp2s0.service service enabled, which fails now.

I can establish a Wi-Fi connection using wifi-menu, which is somehow able to get my wlp3s0 interface up, but the connection is much slower than usual, only around 4 Mbps.

How can I have things back to normal, working properly?

Thank you!

bstaletic · 2016-03-12 12:02:21

Is there anything of interest in dmesg? How about journalctl?

Trilby · 2016-03-12 12:10:19

Please post *something* we can use. logs, error message, anything. The output of the following would be a good start:

ip a
ip link set enp2s0 up
ip a
dhcpcd enp2s0

LonelyArchFan · 2016-03-12 13:50:41

Sorry, it's my first time posting here.

Output of "dmesg | grep enp2s0":

[   39.661348] r8169 0000:02:00.0 enp2s0: renamed from eth0
[   41.051436] r8169 0000:02:00.0 enp2s0: link down
[   41.051536] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready

Output of "journalctl -xe | grep enp2s0":

Mar 12 02:35:12 sleigh kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0
-- Subject: Unit sys-subsystem-net-devices-enp2s0.device has finished start-up
-- Unit sys-subsystem-net-devices-enp2s0.device has finished starting up.
Mar 12 02:35:13 sleigh systemd[1]: Starting dhcpcd on enp2s0...
-- Subject: Unit dhcpcd@enp2s0.service has begun start-up
-- Unit dhcpcd@enp2s0.service has begun starting up.
Mar 12 02:35:14 sleigh kernel: r8169 0000:02:00.0 enp2s0: link down
Mar 12 02:35:14 sleigh kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Mar 12 02:35:14 sleigh dhcpcd[501]: enp2s0: waiting for carrier
Mar 12 02:35:43 sleigh systemd[1]: dhcpcd@enp2s0.service: Control process exited, code=exited status=1
Mar 12 02:35:43 sleigh systemd[1]: Failed to start dhcpcd on enp2s0.
-- Subject: Unit dhcpcd@enp2s0.service has failed
-- Unit dhcpcd@enp2s0.service has failed.
Mar 12 02:35:43 sleigh systemd[1]: dhcpcd@enp2s0.service: Unit entered failed state.
Mar 12 02:35:43 sleigh systemd[1]: dhcpcd@enp2s0.service: Failed with result 'exit-code'.

Output of "ip a" (wlp3s0 connected via wifi-menu):

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 02:1f:12:29:61:fd brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 68:1c:a2:01:3b:d9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.114/24 brd 192.168.0.255 scope global wlp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::6a1c:a2ff:fe01:3bd9/64 scope link 
       valid_lft forever preferred_lft forever

"sudo ip link set enp2s0 up" provides no output.

Output of "sudo dhcpcd enp2s0":

enp2s0: waiting for carrier
timed out
dhcpcd exited

Last edited by LonelyArchFan (2016-03-12 13:53:26)

Trilby · 2016-03-12 14:28:25

Your ethernet interface is up. It's just not connected to anything.

I see you wireless is also up and connected. I'm not sure dhcpcd can connect to wired while it is already running on a wireless interface (at least not without additional configuration).

Why are you trying to connect both at the same time?

bstaletic · 2016-03-12 22:42:58

Trilby,

Dhcpcd can connect to wired after successfully connecting to wireless network. I tried it on my laptop.

LonelyArchFan,

Everything seems to be fine, just as Trilby noted. Try manually adding the ip and route for the wired connection.

Arch Linux

#1 2016-03-12 11:33:49

Can't set interface state to UP!

#2 2016-03-12 12:02:21

Re: Can't set interface state to UP!

#3 2016-03-12 12:10:19

Re: Can't set interface state to UP!

#4 2016-03-12 13:50:41

Re: Can't set interface state to UP!

#5 2016-03-12 14:28:25

Re: Can't set interface state to UP!

#6 2016-03-12 22:42:58

Re: Can't set interface state to UP!

Board footer