You are not logged in.

#1 2013-09-19 04:49:20

mibadt
Member
Registered: 2009-09-25
Posts: 396

[SOLVED] No (wired) net after boot, yet available with "ip link.."

Hi,
I'm on a fully updated (inc. latest systemd), networkmanager based, Arch-X86-64/KDE system.
The system is connected to the router via eth1 (r8169).
After boot, I have no net connection (see below), yet, I do get connected, once I issue the "ip link set eth1 up" command.
Please advise.
Thanks
-------copy of terminal----------

# journalctl -b | grep eth
Sep 19 07:21:34 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
Sep 19 07:21:34 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Sep 19 07:21:35 Miki_Arch kernel: r8169 0000:05:00.0 eth0: RTL8168d/8111d at 0xffffc900144e4000, 6c:f0:49:ed:b3:e9, XID 083000c0 IRQ 50
Sep 19 07:21:35 Miki_Arch kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 19 07:21:35 Miki_Arch kernel: r8169 0000:06:00.0 eth1: RTL8168d/8111d at 0xffffc900144e6000, 6c:f0:49:ed:b3:eb, XID 083000c0 IRQ 51
Sep 19 07:21:35 Miki_Arch kernel: r8169 0000:06:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 19 07:21:52 Miki_Arch systemd[1]: Starting dhcpcd on eth0...
Sep 19 07:21:52 Miki_Arch systemd[1]: Starting dhcpcd on eth1...
Sep 19 07:21:53 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 19 07:21:53 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 19 07:21:53 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 19 07:21:53 Miki_Arch kernel: r8169 0000:05:00.0 eth0: link down
Sep 19 07:21:53 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 19 07:21:55 Miki_Arch dhcpcd[343]: eth1: waiting for carrier
Sep 19 07:21:55 Miki_Arch dhcpcd[340]: eth0: waiting for carrier
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): carrier is OFF
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): preparing device.
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth0): deactivating device (reason 'managed') [2]
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:07.0/0000:05:00.0/net/eth0
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): carrier is OFF
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): new Ethernet device (driver: 'r8169' ifindex: 3)
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): preparing device.
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> (eth1): deactivating device (reason 'managed') [2]
Sep 19 07:21:58 Miki_Arch NetworkManager[344]: <info> Added default wired connection 'Wired connection 2' for /sys/devices/pci0000:00/0000:00:09.0/0000:06:00.0/net/eth1
Sep 19 07:22:25 Miki_Arch systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Sep 19 07:22:25 Miki_Arch systemd[1]: Failed to start dhcpcd on eth0.
Sep 19 07:22:25 Miki_Arch systemd[1]: Unit dhcpcd@eth0.service entered failed state.
Sep 19 07:22:25 Miki_Arch systemd[1]: dhcpcd@eth1.service: control process exited, code=exited status=1
Sep 19 07:22:25 Miki_Arch systemd[1]: Failed to start dhcpcd on eth1.
Sep 19 07:22:25 Miki_Arch systemd[1]: Unit dhcpcd@eth1.service entered failed state.

Last edited by mibadt (2013-09-20 02:54:28)


Best regards,
Michael Badt

Offline

#2 2013-09-19 08:04:46

Raynman
Member
Registered: 2011-10-22
Posts: 1,539

Re: [SOLVED] No (wired) net after boot, yet available with "ip link.."

Seems like you are running both NetworkManager and dhcpcd@.services. Pick one so they don't have to compete with each other.

Offline

#3 2013-09-19 08:11:33

mibadt
Member
Registered: 2009-09-25
Posts: 396

Re: [SOLVED] No (wired) net after boot, yet available with "ip link.."

Thanks, I'll try!


Best regards,
Michael Badt

Offline

#4 2013-09-20 02:54:00

mibadt
Member
Registered: 2009-09-25
Posts: 396

Re: [SOLVED] No (wired) net after boot, yet available with "ip link.."

Raynman,
Thanks again. Indeed disabling dhcp solved my problem!


Best regards,
Michael Badt

Offline

Board footer

Powered by FluxBB