Sometimes no Wifi or/and LAN after suspend by NV41 from novacustom #9333
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: networking
C: power management
diagnosed
Technical diagnosis has been performed (see issue comments).
hardware support
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
pr submitted
A pull request has been submitted for this issue.
r4.2-host-stable
r4.3-host-cur-test
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Qubes OS release
R4.2.1
Brief summary
I bought the novacustom NV41 laptop with coreboot and heads (0.9.1) and installed QubesOS on it (without kernel-latest option). The main Template is fedora39-xfce (I will update it next time to the 40). Specially NV41 was reported with working suspend mode.
The network devices are:
Intel Alder Lake-P PCH CNVi WiFi (so, the AX211)
Realtek Semiconductor RTL 8111/8168/8411
As I saw in the news from QubesOS in 2023, AX211 was not under officially supported wifi devices.
I tried the following points with different kernels (6.6.31 / 29 and 21). I even installed the kernel-latest (6.9.2) to check it, because I red in the news thread from Qubes, that it should be installed with this option. Later somebody in the Qubes forum said, that there is no need for it anymore (it would be good to update it in some info about NV41). So now, I use the standard 6.6.31 kernel.
Steps to reproduce
I'm in the working system with sys-net and some other VMs opened, then I close my laptop and after some time open it again. Then I get the problem describes on actual behavior.
If I restart the sys-net, everything works again.
Expected behavior
Everything should work as before suspend.
Actual behavior
Sometimes (I could not reproduce it 100% or even 70%) there is no Wifi and/or LAN if I click on the icon above. I can see the networks if I want to edit them, but they can not be chosen to connect, for they are just not there. Sometimes the networks are there as expected. So it doesn't seem to be a fully reproducible problem.
The text was updated successfully, but these errors were encountered: