You are not logged in.
Hi,
My fully updated Arch_X86-64/KDE is connected to the Internet router via (on-board wired) eth1, and is configured to get an auto IP address.
This has worked flawlessly for years till two days ago.
Ever since, eth1 service fails during boot, and requires several manual dhcpcd command to finally kick in. The same applies after waking from sleep mode. (see terminal output below)
As can be seen the system is configured to load the (correct) r8169 mode.
Please advise.
Thanks
Miki Badt
---------copy of respective commands---------------
# journalctl -b | grep eth
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: RTL8168d/8111d at 0xffffc900119d2000, 6c:f0:49:ed:b3:e9, XID 083000c0 IRQ 49
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: RTL8168d/8111d at 0xffffc900119e6000, 6c:f0:49:ed:b3:eb, XID 083000c0 IRQ 50
Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Sep 15 15:50:23 Miki_Arch dhcpcd[339]: eth1: waiting for carrier
Sep 15 15:50:23 Miki_Arch dhcpcd[336]: eth0: waiting for carrier
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:05:00.0 eth0: link down
Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 15:50:53 Miki_Arch systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth0.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit dhcpcd@eth0.service entered failed state.
Sep 15 15:50:53 Miki_Arch systemd[1]: dhcpcd@eth1.service: control process exited, code=exited status=1
Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth1.
Sep 15 15:50:53 Miki_Arch systemd[1]: Unit dhcpcd@eth1.service entered failed state.
#manual commands
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1039]: version 6.0.5 starting
dhcpcd[1039]: eth1: waiting for carrier
dhcpcd[1039]: timed out
dhcpcd[1039]: exited
[root@Miki_Arch miki]# ping www.ynet.co.il
ping: unknown host www.ynet.co.il
[root@Miki_Arch miki]# dhcpcd eth1
dhcpcd[1046]: version 6.0.5 starting
dhcpcd[1046]: eth1: soliciting an IPv6 router
dhcpcd[1046]: eth1: rebinding lease of 192.168.1.13
dhcpcd[1046]: eth1: leased 192.168.1.13 for 3600 seconds
dhcpcd[1046]: eth1: adding host route to 192.168.1.13 via 127.0.0.1
dhcpcd[1046]: eth1: adding route to 192.168.1.0/24
dhcpcd[1046]: eth1: adding default route via 192.168.1.1
lspci -v | grep Ethernet
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
lspci -k
......
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
cat /etc/modules-load.d/realtek.conf
r8169Last edited by mibadt (2013-09-15 13:29:25)
Best regards,
Michael Badt
Offline
Hi,
I've some errors with the new dhcpcd, you should downgrade.
https://wiki.archlinux.org/index.php/Do … g_Packages
Offline