Engage. Your Community

Ethernet has stopped working (Wireless is ok)

Hi, I am on Korora 26 and about a week or two ago, my Ethernet connection suddenly stopped working. When I boot up my computer, it automatically connects to my router using the wireless connection, which works perfectly fine. However, I'd like to have it prefer the Ethernet connection when both are available because it's faster.

I have one of these computers. I also have a thinkpad one link pro docking station, which is where the ethernet network card sits because the laptop doesn't actually have an ethernet port on it. I don't remember what my settings were before but I think the ethernet device was virbr0. It is down and I can't bring it up for some reason. Here's the output of ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 60:57:18:6a:f6:8f brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.9/24 brd 10.0.0.255 scope global dynamic wlp4s0
       valid_lft 603566sec preferred_lft 603566sec
    inet6 2601:646:8280:6910:6257:18ff:fe6a:f68f/64 scope global noprefixroute dynamic 
       valid_lft 284668sec preferred_lft 284668sec
    inet6 fe80::6257:18ff:fe6a:f68f/64 scope link 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:9b:8d:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:9b:8d:7e brd ff:ff:ff:ff:ff:ff

And my lspci contents:

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)

lsusb:

Bus 001 Device 003: ID 0483:91d1 STMicroelectronics Sensor Hub
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 012: ID 056a:00ec Wacom Co., Ltd TPCEC
Bus 002 Device 008: ID 1bcf:2c79 Sunplus Innovation Technology Inc. 
Bus 002 Device 016: ID 06cb:764a Synaptics, Inc. 
Bus 002 Device 003: ID 8087:0a2a Intel Corp. 
Bus 002 Device 009: ID 413c:2107 Dell Computer Corp. 
Bus 002 Device 011: ID 0bc2:2100 Seagate RSS LLC FreeAgent Go
Bus 002 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 013: ID 17ef:304e Lenovo 
Bus 002 Device 010: ID 0e8d:1887 MediaTek Inc. 
Bus 002 Device 007: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 002 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 002 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And route:

default via 10.0.0.1 dev wlp4s0 proto static metric 600 
10.0.0.0/24 dev wlp4s0 proto kernel scope link src 10.0.0.9 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 

Thanks for your attention!

Have you checked the basics? Try replacing the cables, reboot the modem / router.

Also what happened when the ethernet stopped working? Did you receive an update, install something new?

Yeah I rebooted the router, changed cables and stuff (the lights are working as if there is connection). It could be the docking station, but I don't know how to test that (I only have 1 lenovo laptop.)

I was updating regularly using the update manager and I think I received a few big updates because my system seems more stable than before. I don't remember which updates I did though...

CoryParsnipson wrote:
Yeah I rebooted the router, changed cables and stuff (the lights are working as if there is connection). It could be the docking station, but I don't know how to test that (I only have 1 lenovo laptop.)

I was updating regularly using the update manager and I think I received a few big updates because my system seems more stable than before. I don't remember which updates I did though...

I can't help with the docking station as I've never used one but you could try rebooting to a previous kernel. Occasionally kernel updates break drivers or other things.

You can see the update details with sudo dnf history list which shows the dnf transactions and get the number of the most recent update. Then do sudo dnf history info ## where ## is the transaction number.

BTW which desktop are you using? If Gnome try running in X.org instead of Wayland (or vice versa).

virbr0 isn't the ethernet connection but a bridge. Ethernet is usually enp0s25 or similar. Your list doesn't show that so you could try recreating it but Network Manager will usually create it automatically if it is available.

Does dnf history work for packages updated through the package manager GUI? I'm using KDE, so does your Xorg Wayland tip still apply? (I'm not familiar with wayland).

I understand that about the bridge and I think it's creating this because the ethernet hardware might actually be in the docking station? From what I can infer from googling this it looks like the ethernet device in the docking station should be visible as a usb device, but that's just a guess from me.

Rolling back the kernel is a good idea... It's kind of a pain though, so I might just put up with using wireless all the time if it's not too bad. o_o;;

No, the Wayland comment only applies to Gnome (although KDE is working on Wayland).

Using the previous kernel is simple as it is an option at boot time.

Please Log In to participate with the community.