Hello,
New user here. More of a linux user than a power-user which means that not that familiar with linux commands.

I am having issues with my ethernet connection since last week. Noticed that on my laptop, ethernet connection is not recognized after waking up my laptop from sleep. However, the ethernet connection is recognized and connected once I restart my system.

I am using KDE Neon Plasma 5.22.4 and Neon is the only OS on my laptop. My laptop specs

Code: Select all

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-25-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

lspci | egrep -i --color 'network|ethernet'
01:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10)
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)


How do I go about diagnosing the issue and hopefully resolving it? I never had issue with Network cards in Linux since I bought this laptop...this is the first time. Currently, connecting to internet using Wireless but I would prefer Ethernet due to better connection stability & speed.

Tried doing a Google search but I am not getting relevant results.

Regards,
-Burner

I am still facing the above issues. Would appreciate some pointers on troubleshooting the above. Is there any official Neon forums or this is it? I will try posting on KDE Reddit as well this weekend.

So after some more research I found out that Ethernet connection is being disabled after waking up. I tried restarting Network manager using

Code: Select all

sudo service networking restart

The wired connection is now recognised but can't connect

Code: Select all

Wired Interface (enp1s0) The device could not be configured

Here are the output of sudo lshw -C network after system restart

Code: Select all

sudo lshw -C network
[sudo] password for <xxx>:
  *-network                 
       description: Ethernet interface
       product: AR8162 Fast Ethernet
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0
       version: 10
       serial: 20:89:84:41:97:d5
       size: 100Mbit/s
       capacity: 100Mbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=alx driverversion=5.11.0-27-generic duplex=full ip=192.168.1.3 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:16 memory:e0500000-e053ffff ioport:2000(size=128)
  *-network
       description: Wireless interface
       product: AR9485 Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 01
       serial: 2c:d0:5a:34:42:66
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=5.11.0-27-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:e0400000-e047ffff memory:e0480000-e048ffff

output of sudo lshw -C network after waking up from sleep

Code: Select all

sudo lshw -C network
  *-network DISABLED       
       description: Ethernet interface
       product: AR8162 Fast Ethernet
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0
       version: 10
       serial: 20:89:84:41:97:d5
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=alx latency=0 multicast=yes
       resources: irq:16 memory:e0500000-e053ffff ioport:2000(size=128)
  *-network
       description: Wireless interface
       product: AR9485 Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 01
       serial: 2c:d0:5a:34:42:66
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=5.11.0-27-generic firmware=N/A ip=192.168.1.5 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:e0400000-e047ffff memory:e0480000-e048ffff

And output of

Code: Select all

lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8162 Fast Ethernet [1969:1090] (rev 10)
02:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)


Any ideas on how I can proceed from here. Not sure if updating the driver helps. If yes, how can I install updated drivers?

Is my issue so unique that it has stumped folks? Cause I've posted this same query in a few Linux forums and no replies.

burner wrote:Is my issue so unique that it has stumped folks? Cause I've posted this same query in a few Linux forums and no replies.

Hi!

I think so. Most problems are based on wifi chips and the need of installing blobs (proprietary software/drivers). Ethernet just has to run out of the box and normally does this for years now.
What you can do is read about UDEV, test with `udevadm trigger` and check your logfiles for issues, using `journalctl -b -xep 0..4` to get a hint. If you have collected enough information, open a bug report or write a mail to the kernel-mailing list to make them aware of it.

As an easy workaround you could write a wakeup-hook and restart the network after suspend. Btw: `sudo service stuff` is quite old, nowadays there is systemd and you should find a lot of examples for 'after wakeup stuff'. I'd use a timer unit for it to wait for some seconds after suspend, or write a custom udev-rule.

koffeinfriedhof wrote:

burner wrote:Is my issue so unique that it has stumped folks? Cause I've posted this same query in a few Linux forums and no replies.

Hi!

I think so. Most problems are based on wifi chips and the need of installing blobs (proprietary software/drivers). Ethernet just has to run out of the box and normally does this for years now.
What you can do is read about UDEV, test with `udevadm trigger` and check your logfiles for issues, using `journalctl -b -xep 0..4` to get a hint. If you have collected enough information, open a bug report or write a mail to the kernel-mailing list to make them aware of it.

As an easy workaround you could write a wakeup-hook and restart the network after suspend. Btw: `sudo service stuff` is quite old, nowadays there is systemd and you should find a lot of examples for 'after wakeup stuff'. I'd use a timer unit for it to wait for some seconds after suspend, or write a custom udev-rule.

Hi koffeinfriedhof, firstly thanks for replying and sorry for my late response. Unfortunately I don't know how to do any of the above. But I will try to look it up. Anyways, for now Wi-Fi is working and I guess I will continue using the same. Anyways, my laptop is aging and I may replace it sometime next year.

I had this same issue - no ethernet after sleep/suspend and attempts to restart the network service did not work either. Only a reboot would restore ethernet access.

For reference it appears to have been fixed in the upgrade to Plasma 5.22.5 and I think was tracked below as a kernel bug.

https://bugs.launchpad.net/ubuntu/+sour ... ug/1931301