You are not logged in.
My arch desktop has, until today, been working fine with the same wired NIC (on the motherboard) for several years:
$ lspci|grep Eth -m1
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
$ dmesg|grep Ether
[ 7.178564] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
$ lsmod |grep r8169
r8169 58463 0
mii 4035 1 r8169
But today after a reboot it wouldn't connect. /var/log/wicd/wicd.log says:
2014/01/19 18:24:02 :: Flushing the routing table...
2014/01/19 18:24:02 :: /usr/sbin/ip route flush dev enp3s0
2014/01/19 18:24:02 :: Putting interface up...
2014/01/19 18:24:02 :: ifconfig enp3s0 up
2014/01/19 18:24:04 :: Running DHCP with hostname kiwiarch
2014/01/19 18:24:04 :: /usr/sbin/dhcpcd -h kiwiarch --noipv4ll enp3s0
2014/01/19 18:24:04 :: dhcpcd[26612]: version 6.1.0 starting
2014/01/19 18:24:04 ::
2014/01/19 18:24:04 :: dhcpcd[26612]: enp3s0: waiting for carrier
2014/01/19 18:24:04 ::
2014/01/19 18:24:34 :: dhcpcd[26612]: timed out
2014/01/19 18:24:34 ::
2014/01/19 18:24:34 :: DHCP connection failed
2014/01/19 18:24:34 :: exiting connection thread
2014/01/19 18:24:34 :: Sending connection attempt result dhcp_failed
I get this NO-CARRIER thing here:
$ sudo 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: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 00:26:18:98:ab:57 brd ff:ff:ff:ff:ff:ff
3: wlp4s5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:24:01:0d:f0:3d brd ff:ff:ff:ff:ff:ff
and it seems people with the same card have had similar issues. I followed some suggestions from https://bbs.archlinux.org/viewtopic.php?id=159837&p=2 with no luck.
Removing /etc/udev/rules.d/80-net-name-slot.rules gave me less readable device names:
$ dmesg|grep -e eth0 -e enp
[ 7.179254] r8169 0000:03:00.0 eth0: RTL8168d/8111d at 0xffffc90010ffe000, 00:26:18:98:ab:57, XID 083000c0 IRQ 42
[ 7.179261] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 7.654235] systemd-udevd[176]: renamed network interface eth0 to enp3s0
[ 61.445644] r8169 0000:03:00.0 enp3s0: link down
[ 61.445710] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 64.546859] r8169 0000:03:00.0 enp3s0: link down
[ 64.546928] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
but still no connection.
None of the devices in /sys/bus/pci have "auto" power control:
$ grep auto /sys/bus/pci/devices/0000:*/power/control || echo nope
nope
/sys/class/net/enp3s0/power/control did have auto, but running
$ sudo sh -c 'echo on > /sys/class/net/enp3s0/power/control'
had no effect, still times out with "waiting for carrier".
I even tried downgrading linux/linux-headers/linux-firmware
[2014-01-19 16:47] [PACMAN] downgraded linux (3.12.7-2 -> 3.12.6-1)
[2014-01-19 16:48] [PACMAN] downgraded linux-headers (3.12.7-2 -> 3.12.6-1)
[2014-01-19 20:32] [PACMAN] downgraded linux-firmware (20131230.52d77db-1 -> 20131013.7d0c7a8-1)
to no avail.
To check it wasn't just hardware, I tried the cable in my Xubuntu laptop, worked fine there; so I tried booting up the desktop with an old SLAX live CD I found lying around, that worked fine too. So it's not the cable and it's not the NIC.
What else can I try?
Last edited by unhammer (2014-01-19 19:44:48)
Offline
Are the link lights (The LEDs) on on your NIC and Router/Modem?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Are the link lights (The LEDs) on on your NIC and Router/Modem?
Yes, and e.g. blinking when dhcpcd runs.
Also, not sure if this is helpful:
$ dmesg|grep r8169
[ 8.496249] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 8.496262] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 8.496454] r8169 0000:03:00.0: irq 42 for MSI/MSI-X
[ 8.496593] r8169 0000:03:00.0 eth0: RTL8168d/8111d at 0xffffc900113fe000, 00:26:18:98:ab:57, XID 083000c0 IRQ 42
[ 8.496596] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 65.929010] r8169 0000:03:00.0 enp3s0: link down
[ 69.016845] r8169 0000:03:00.0 enp3s0: link down
Offline
Try grabbing r8168 from the repos. I was having some power consumption issues with r8169 a while back, and switched over. Haven't had any problems since then. Of course, YMMV.
Offline
Try grabbing r8168 from the repos. I was having some power consumption issues with r8169 a while back, and switched over. Haven't had any problems since then. Of course, YMMV.
Wow, that worked thank you.
(By the way, do you mean r8169 actually used more of your battery than r8168?)
Offline
cris9288 wrote:Try grabbing r8168 from the repos. I was having some power consumption issues with r8169 a while back, and switched over. Haven't had any problems since then. Of course, YMMV.
Wow, that worked
thank you.
(By the way, do you mean r8169 actually used more of your battery than r8168?)
Well, I'll admit that I was only going by what powertop was reporting and it was reporting that my ethernet's wake-on-lan feature was using up some battery. ethtool was unable to disable wol for some reason and that annoyed me. Using r8168, I was able to disable it without any problems so I kept it.
Offline