[DESKTOP] After resuming from sleep or hibernation, network card disabled

[wonder]

I think this has been happening to me since 22.04, so it may be a kernel issue, I don't know.

Sometimes, when resuming from sleep or hibernation, the network card icon is grayed out and it no longer reloads and becomes operational, it stays grayed out.

Whatever I do, it doesn't pick up the network.

Is there a command or something similar to restart the network? Because at the moment, the only solution is to restart the entire computer.

Thanks in advance.

[claydoh]

Thius recent thread may be relevant
https://www.kubuntuforums.net/forum/...-after-suspend

suspend and hibernation are tricky for Linux to get working reliable, on some systems.
Some drivers don't like reloading after suspend or some boards don't reinitialize the hardware, or do so in a non-standard way.
But we'll need some info about your networking hardware, Then we can test a few things to find out which direction to go. Most likely it will be to tell the OS to unload the driver before, then re-load it after resume.
The other option is to have it disconnect from the network then reconnect. But if this was the case, you probably would be able to reconnect from the tray icon.

[wonder]

I hadn't seen that thread and it's exactly what happens to me...

I would like to comment that I think it's when I resume from hibernation, not from suspension (but I'm not 100% sure).

Some drivers don't like reloading after suspend or some boards don't reinitialize the hardware, or do so in a non-standard way.

But this happens to me in kubuntu 22.04, I think, since the latest kernels and in 24.04, since I installed it a couple or three weeks ago.
So I think that maybe, just maybe, it's a kernel thing...
Since in another distro, with an older kernel, it doesn't happen to me...

But we will need information about the network hardware. Then, we can try a few things to figure out what to do.

As I've seen in the other thread...if I put my info and continue there, the information of the two users will be mixed, if admins see fit, I'll continue in this one.

The other option is to disconnect it from the network and then reconnect it. But if this was the case, I could probably reconnect from the tray icon.

Right, I already tried from the icon, without result, and disconnecting and connecting the cable, it does nothing...

My system:

Desktop PC
Version: Kubuntu 24.04.01
KDE-Plasma-Version: 5.27.11
KDE-Frameworks-Version: 5.115.0
Qt-Version: 5.15.13
Kernel-Version: 6.8.0-45-generic (64-bit)
Graphic Platform: X11
Processors: AMD Ryzen 3600
Ram: 15.5 GiB
GPU: Radeon RX 480 Armor 8G

Network:

~$ ifconfig
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2a0c:5a85:d304:7400:8b49:d8b:9316:7c0f prefixlen 64 scopeid 0x0<global>
inet6 fe80::daff:691e:4cb8:8890 prefixlen 64 scopeid 0x20<link>
inet6 2a0c:5a85:d304:7400:1ff:fe18:8cf6:98f0 prefixlen 64 scopeid 0x0<global>
ether b4:2e:99:30:90:66 txqueuelen 1000 (Ethernet)
RX packets 17173 bytes 14888284 (14.8 MB)
RX errors 0 dropped 36 overruns 0 frame 0
TX packets 9823 bytes 3703520 (3.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xfcc00000-fcc1ffff

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Bucle local)
RX packets 39342 bytes 4281660 (4.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 39342 bytes 4281660 (4.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

~$ netplan --all status
Online state: online
DNS Addresses: 127.0.0.53 (stub)
DNS Search: .

● 1: lo ethernet UNKNOWN/UP (unmanaged)
MAC Address: 00:00:00:00:00:00
Addresses: 127.0.0.1/8
::1/128

● 2: enp7s0 ethernet UP (unmanaged)
MAC Address: b4:2e: xx:30:90: xx (Intel Corporation)
Addresses: 192.168.1.10/24 (dhcp)
2a0c:5a85:d304: xxxx:1ff:fe18:8cf6:98f0/64
2a0c:5a85:d304: xxxx:8b49:d8b:9316:7c0f/64
fe80::daff:691e:4cb8:8890/64 (link)
DNS Addresses: 1.1.1.1
2001:4860:4860::8888
2606:4700:4700::1111
2606:4700:4700::1001
2a0c:5a80:0:2::1
2a0c:5a84:0:2::1
fe80::1
Routes: default via 192.168.1.1 from 192.168.1.10 metric 100 (dhcp)
192.168.1.0/24 from 192.168.1.10 metric 100 (link)
2a0c:5a85:d304:7400::/64 metric 100 (ra)
fe80::/64 metric 1024
default via fe80::1 metric 100 (ra)

If you need any other information, please let me know.

Thanks in advance.

[claydoh]

But this happens to me in kubuntu 22.04, I think, since the latest kernels and in 24.04, since I installed it a couple or three weeks ago.
So I think that maybe, just maybe, it's a kernel thing...

Sure, as 22.04 and 24.04 can be on the same kernel, which also will come with the same drivers for this, which can be what doesn't like your computer's suspend/hibernation hardware/firmware setup.


Will need the hardware IDs for your ethernet card, as this is not exactly like the other thread.

lspci | grep -E -i  'network|ethernet|wireless|wi-fi'​

[wonder]

Sure, as 22.04 and 24.04 can be on the same kernel, which also will come with the same drivers for this, which can be what doesn't like your computer's suspend/hibernation hardware/firmware setup.


Will need the hardware IDs for your ethernet card, as this is not exactly like the other thread.

lspci | grep -E -i 'network|ethernet|wireless|wi-fi'​

Yes, they use both kernels, but since 24.04.1 came out I've switched to this one to see if I could stay here permanently...

Ok, yes, I've seen that it's not exactly the same as in the other thread.

I'm waiting for it to happen again, I'm betting it's when resuming from hibernation (you see the icon as reload and it picks up the network) but other times it stays grey, but maybe it's also happened when coming out after sleeping (I'm not sure...).

~$ lspci | grep -E -i 'network|ethernet|wireless|wi-fi'
07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

Thanks in advance

[claydoh]

oops, I forgot to use the proper switches to show the hardware IDs and make a more posting-friendly output:

​lspci -nn -vvv | egrep -E -i --color=never 'network|ethernet'

[wonder]

oops, I forgot to use the proper switches to show the hardware IDs and make a more posting-friendly output:

​lspci -nn -vvv | egrep -E -i --color=never 'network|ethernet'

No problem!

~$ lspci -nn -vvv | egrep -E -i --color=never 'network|ethernet'
07:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
Subsystem: Gigabyte Technology Co., Ltd I211 Gigabit Network Connection [1458:e000]
​