Every time the system returns from "suspend" state the wired network is not being restored correctly. Really annoying as the only way I know how to recover situation is to reboot.
This is happening on a fresh install on zorin 17.1 core.
Every time the system returns from "suspend" state the wired network is not being restored correctly. Really annoying as the only way I know how to recover situation is to reboot.
This is happening on a fresh install on zorin 17.1 core.
It would help to know make and model of network device. On a side note, this is yet another poor incidence of systemd being bad for systems:
Please open a terminal and enter:
sudo lshw -C network
This is the output of the command you suggested:-
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:01:00.0
logical name: enp1s0
version: 15
serial: 70:70:fc:00:44:d7
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.5.0-26-generic duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.22 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:42 ioport:f000(size=256) memory:fcf04000-fcf04fff memory:fcf00000-fcf03fff
*-network
description: Wireless interface
product: MEDIATEK Corp.
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 00
serial: 10:6f:d9:27:d0:57
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=mt7921e driverversion=6.5.0-26-generic firmware=____010000-20231109190959 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:78 memory:e0300000-e03fffff memory:e0400000-e0403fff memory:e0404000-e0404fff
See if the script solution given on this askubuntu thread helps:
Thanks for this.
The bug reported in that post looks identical to what I am seeing so I have registered as being effected by it.
I will turn off system suspension for now in the hope there will be a fix at some point soon.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.