[SOLVED] Can't bring ethernet interface up

navi_se · 2017-10-19 14:49:26

I have a new box I'm installing arch linux on.

The output of ip link shows both ethernet and wifi card detected.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s10: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:8c:d7:ca:9d brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 18:d6:c7:af:a3:7d brd ff:ff:ff:ff:ff:ff

The wifi card is working fine, but the ethernet interface is always down and ip link set up has no effect.

The ethernet card has a its kernel module called forcedeth

# lspci | grep Ethernet
00:0a.0 Ethernet controller: NVIDIA Corporation MCP77 Ethernet (rev a2)

# dmesg | grep forcedeth
[    4.882462] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[    4.947713] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 3, addr 00:24:8c:d7:ca:9d
[    4.947715] forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt gbit lnktim msi desc-v3
[   10.728984] forcedeth 0000:00:0a.0 enp0s10: renamed from eth0
[   13.953149] forcedeth 0000:00:0a.0 enp0s10: MSI enabled
[   18.587162] forcedeth 0000:00:0a.0 enp0s10: link down
[   20.539185] forcedeth 0000:00:0a.0 enp0s10: link up
[   44.382115] forcedeth 0000:00:0a.0 enp0s10: link down

It seems the module is fine but the link goes down up and then down?

The dhchpd.service is running but it is silent on the ethernet interface.

# systemctl status dhchpd.service
dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-10-19 14:11:10 UTC; 18min ago
  Process: 1082 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
 Main PID: 1083 (dhcpcd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/dhcpcd.service
           â””â”€1083 /usr/bin/dhcpcd -q -b

Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: Router Advertisement from fe80::9221:6ff:feb9:51fc
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: adding address fd41:cfe7:7754:0:944c:d865:db53:48c7/64
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: adding address 2a02:c7d:76a8:5d00:4e15:4d56:f19a:dd0e/64
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: adding route to fd41:cfe7:7754::/64
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: adding route to 2a02:c7d:76a8:5d00::/64
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: adding default route via fe80::9221:6ff:feb9:51fc
Oct 19 14:16:54 archiso dhcpcd[1083]: wlp4s0: requesting DHCPv6 information
Oct 19 14:16:58 archiso dhcpcd[1083]: wlp4s0: leased 192.168.0.74 for 86400 seconds
Oct 19 14:16:58 archiso dhcpcd[1083]: wlp4s0: adding route to 192.168.0.0/24
Oct 19 14:16:58 archiso dhcpcd[1083]: wlp4s0: adding default route via 192.168.0.1

Tried starting a dhcpcd@enp0s10.service (which I don't think I actually should, my other computer is fine with just dhcpcd.service which picks up the ethernet fine) but to no avail. Errors from dmesg and journalctl -xe simply mention timeout.

Oct 19 13:41:34 archiso kernel: forcedeth 0000:00:0a.0 enp0s10: renamed from eth0
Oct 19 13:41:37 archiso systemd[1]: Starting dhcpcd on enp0s10...
-- Subject: Unit dhcpcd@enp0s10.service has begun start-up
-- Unit dhcpcd@enp0s10.service has begun starting up.
Oct 19 13:41:37 archiso kernel: forcedeth 0000:00:0a.0 enp0s10: MSI enabled
Oct 19 13:41:37 archiso dhcpcd[329]: enp0s10: waiting for carrier
Oct 19 13:41:37 archiso dhcpcd[329]: enp0s10: carrier acquired
Oct 19 13:41:37 archiso dhcpcd[329]: enp0s10: IAID 8c:d7:ca:9d
Oct 19 13:41:37 archiso dhcpcd[329]: enp0s10: adding address fe80::2b02:3d55:64c0:b9b2
Oct 19 13:41:37 archiso dhcpcd[329]: enp0s10: soliciting an IPv6 router
Oct 19 13:41:38 archiso dhcpcd[329]: enp0s10: soliciting a DHCP lease
Oct 19 13:41:42 archiso dhcpcd[329]: enp0s10: carrier lost
Oct 19 13:41:42 archiso kernel: forcedeth 0000:00:0a.0 enp0s10: link down
Oct 19 13:41:42 archiso dhcpcd[329]: enp0s10: deleting address fe80::2b02:3d55:64c0:b9b2
Oct 19 13:41:44 archiso kernel: forcedeth 0000:00:0a.0 enp0s10: link up
Oct 19 13:41:44 archiso dhcpcd[329]: enp0s10: carrier acquired
Oct 19 13:41:44 archiso dhcpcd[329]: enp0s10: IAID 8c:d7:ca:9d
Oct 19 13:41:44 archiso dhcpcd[329]: enp0s10: adding address fe80::2b02:3d55:64c0:b9b2
Oct 19 13:41:44 archiso dhcpcd[329]: enp0s10: soliciting an IPv6 router
Oct 19 13:41:44 archiso dhcpcd[329]: enp0s10: soliciting a DHCP lease
Oct 19 13:41:57 archiso dhcpcd[329]: enp0s10: no IPv6 Routers available
Oct 19 13:42:07 archiso systemd[1]: dhcpcd@enp0s10.service: Control process exited, code=exited status=1
Oct 19 13:42:07 archiso systemd[1]: Failed to start dhcpcd on enp0s10.
-- Subject: Unit dhcpcd@enp0s10.service has failed
-- Unit dhcpcd@enp0s10.service has failed.
Oct 19 13:42:07 archiso systemd[1]: dhcpcd@enp0s10.service: Unit entered failed state.
Oct 19 13:42:07 archiso systemd[1]: dhcpcd@enp0s10.service: Failed with result 'exit-code'.
Oct 19 13:42:08 archiso kernel: forcedeth 0000:00:0a.0 enp0s10: link down
Oct 19 13:59:40 archiso systemd[1]: Starting dhcpcd on enp0s10...
-- Subject: Unit dhcpcd@enp0s10.service has begun start-up
-- Unit dhcpcd@enp0s10.service has begun starting up.
Oct 19 13:59:40 archiso dhcpcd[791]: enp0s10: waiting for carrier
Oct 19 14:00:10 archiso systemd[1]: dhcpcd@enp0s10.service: Control process exited, code=exited status=1
Oct 19 14:00:10 archiso systemd[1]: Failed to start dhcpcd on enp0s10.
-- Subject: Unit dhcpcd@enp0s10.service has failed
-- Unit dhcpcd@enp0s10.service has failed.
Oct 19 14:00:10 archiso systemd[1]: dhcpcd@enp0s10.service: Unit entered failed state.
Oct 19 14:00:10 archiso systemd[1]: dhcpcd@enp0s10.service: Failed with result 'exit-code'.
Oct 19 14:11:10 archiso dhcpcd[1083]: enp0s10: waiting for carrier
Oct 19 14:12:05 archiso systemd[1]: Starting dhcpcd on enp0s10...
-- Subject: Unit dhcpcd@enp0s10.service has begun start-up
-- Unit dhcpcd@enp0s10.service has begun starting up.
Oct 19 14:12:05 archiso dhcpcd[1083]: control command: /usr/bin/dhcpcd -q -w enp0s10
Oct 19 14:12:05 archiso systemd[1]: dhcpcd@enp0s10.service: PID file /run/dhcpcd-enp0s10.pid not readable (yet?) after start: No such file or directory
Oct 19 14:12:05 archiso systemd[1]: Failed to start dhcpcd on enp0s10.
-- Subject: Unit dhcpcd@enp0s10.service has failed
-- Unit dhcpcd@enp0s10.service has failed.
Oct 19 14:12:05 archiso systemd[1]: dhcpcd@enp0s10.service: Unit entered failed state.
Oct 19 14:12:05 archiso systemd[1]: dhcpcd@enp0s10.service: Failed with result 'protocol'.
Oct 19 14:12:49 archiso systemd[1]: Starting dhcpcd on enp0s10...
-- Subject: Unit dhcpcd@enp0s10.service has begun start-up
-- Unit dhcpcd@enp0s10.service has begun starting up.
Oct 19 14:12:49 archiso dhcpcd[1083]: control command: /usr/bin/dhcpcd -q -w enp0s10
Oct 19 14:12:49 archiso systemd[1]: dhcpcd@enp0s10.service: PID file /run/dhcpcd-enp0s10.pid not readable (yet?) after start: No such file or directory
Oct 19 14:12:49 archiso systemd[1]: Failed to start dhcpcd on enp0s10.
-- Subject: Unit dhcpcd@enp0s10.service has failed
-- Unit dhcpcd@enp0s10.service has failed.
Oct 19 14:12:49 archiso systemd[1]: dhcpcd@enp0s10.service: Unit entered failed state.
Oct 19 14:12:49 archiso systemd[1]: dhcpcd@enp0s10.service: Failed with result 'protocol'.

Is possible this is an issue with the card? I am wondering, since the wifi card is external if that didn't conflict somehow with the other one? Not sure what else to probe here.

Last edited by navi_se (2017-10-20 18:08:58)

seth · 2017-10-19 20:31:07

The interface /is/ up, you just got no carrier (the stuff inside the <> counts)
Could be the ethernet cable or the plugs.

systemctl list-units| grep -iE '(net|wicd|dhcp|conn)'

ewaller · 2017-10-19 21:17:54

Not meaning to be snarky, but plug a cable in that is attached to a router. What happens?

Trilby · 2017-10-19 21:30:37

In addition to the above (or as the next step from seth's question) I'd recommend disabling all dhcpcd/networking services for now. Run dhcpcd manually - it is easier to troubleshoot this way as you know when the process starts and stops (it only forks to the background upon success).

navi_se · 2017-10-20 12:40:33

So here's:

# systemctl list-units| grep -iE '(net|wicd|dhcp|conn)'

sys-devices-pci0000:00-0000:00:0a.0-net-enp0s10.device                                                loaded active plugged   MCP77 Ethernet                                                    
  sys-devices-pci0000:00-0000:00:12.0-0000:04:00.0-net-wlp4s0.device                                    loaded active plugged   AR9287 Wireless Network Adapter (PCI-Express)                     
  sys-subsystem-net-devices-enp0s10.device                                                             loaded active plugged   MCP77 Ethernet                                                    
  sys-subsystem-net-devices-wlp4s0.device                                                                loaded active plugged   AR9287 Wireless Network Adapter (PCI-Express)                     
● netctl@wlp4s0\x2dSKY673AC.service                                                                     loaded failed failed    Manually generated config                                         
  system-netctl.slice                                                                                                    loaded active active    system-netctl.slice                                               
  network.target                                                                                                          loaded active active    Network

netctl fails as I don't have wpa-supplicant installed at the moment (but I was successfully using the wireless card from the live medium).

I disabled dhcpcd.service and launched dhcpcd and I get

dev:loaded udev
no interfaces have a carrier
forked to background, child pid ###

If relevant: my resolv.conf is currently empty (but dhcpcd should fill it up automatically, if I understand the man page).

As far as the cable goes: I am attached to a wire that goes through a power link, since the physical router is a couple of stories below me. It works fine and without any configuration on my behalf on my laptop (and I can see when it is using the ethernet interface instead of the wifi one, so it works for sure). If you tell me the issue might lie with the power link I'll go through the hassle of moving the whole box downstair.

Slithery · 2017-10-20 12:43:11

no interfaces have a carrier

Means exactly that, either the cable is broken/not plugged in correctly or there is nothing responding on the other end.

seth · 2017-10-20 13:05:20

Powerline reacts badly to non-linear resitances in the grid - the coolest thing I've experienced was a carrier in direct relation to a ceiling lamp in the room ... the room had an internet switch on the wall
Cat5 cables can be up to 100m - if that's a more charming alternative to moving around a PC box ...

navi_se · 2017-10-20 13:10:05

But how's it possible that my laptop can use that very same ethernet cable with zero problem? Couldn't it be the port/connection of the ethernet card that is faulty?

Anyway, I'll try and test with direct router connection.

navi_se · 2017-10-20 13:13:08

Seems like rejiggling the cable and moving the power link to a different outlet did the trick XD

seth · 2017-10-20 14:48:40

Please always remember to mark threads as [SOLVED] once you're fine with outcome.

Arch Linux

#1 2017-10-19 14:49:26

[SOLVED] Can't bring ethernet interface up

#2 2017-10-19 20:31:07

Re: [SOLVED] Can't bring ethernet interface up

#3 2017-10-19 21:17:54

Re: [SOLVED] Can't bring ethernet interface up

#4 2017-10-19 21:30:37

Re: [SOLVED] Can't bring ethernet interface up

#5 2017-10-20 12:40:33

Re: [SOLVED] Can't bring ethernet interface up

#6 2017-10-20 12:43:11

Re: [SOLVED] Can't bring ethernet interface up

#7 2017-10-20 13:05:20

Re: [SOLVED] Can't bring ethernet interface up

#8 2017-10-20 13:10:05

Re: [SOLVED] Can't bring ethernet interface up

#9 2017-10-20 13:13:08

Re: [SOLVED] Can't bring ethernet interface up

#10 2017-10-20 14:48:40

Re: [SOLVED] Can't bring ethernet interface up

Board footer