I have good experience with Linux but I have recently installed Qubes OS, so I may have committed some naiveté. Until two days ago, the wifi interface worked perfectly, as did everything else, and I was thrilled to have even gotten a windows 10 qube working for work purposes.
I have read several dozen posts with similar problems, not only in this forum but also related to debian and archlinux. No one has solved the problem for me.
I don’t know how to interpret the kernel message “iwlwifi 0000:00:06.0: retry init count 2”.
Does anyone have any advice on how to proceed with diagnosis?
Regards
Emanuele
Qubes OS 4.1
kernel 5.15.89-1.fc32
default template debian-11
Did you change vm kernel by any chance?
Is sys-net disposable?
Have you tried changing its template to Fedora?
Are you willing to try with kernel-latest (and Debian)?
Have you tried detaching and re-attaching the pci device with qvm-pci? (Shut down sys-net before you do this)
Perhaps you might’ve made some unintentional modifications.
Try creating a new AppVM (we’ll only use this for testing), make sure it’s a service VM, don’t assign it any netvm.
Shut down sys-net and only then attach the network PCI device to this newly created VM. Then try using it as netvm for your other VMs.
If Debian doesn’t work, try creating a new one but with Fedora (by creating a new one with a different template we can rule out some modifications made on the template itself).
If this doesn’t work, try with the suggestion below:
In dom0, install kernel-latest-qubes-vm. This will make available the 6.1.11 kernel version for VMs. You can then check if using it makes a difference.
I already did a test with a new AppVM named sys-net-2, based on Fedora template, as you described, getting no change.
Today I moved to the office, without shutting down Qubes OS, just closing the laptop lid. In this case my power manager config does not hibernate, just lock screen.
I opened Qubes OS at the office and ta-da!
Magically now wifi is working again.
user@sys-net:~$ nmcli device
DEVICE TYPE STATE CONNECTION
wls6 wifi connected IntesiGroupGuest
p2p-dev-wls6 wifi-p2p disconnected --
ens7 ethernet unavailable --
vif42.0 ethernet unmanaged --
lo loopback unmanaged --
Now I must exclude a problem in the sys-net AppVM configuration because currently it is working fine.
Is it possible that the lid closing/opening action interacts with the wifi driver, not removing the device (it was detected by lspci) but turning it off/on in some way? If this is possible, I can just speculate a bug in the firmware and an intermittent occurrence of it.
Intermittent faults are the worst issues I ever encountered in my career, and this seems to be one of them. But I have no more ideas.