alzer89
November 29, 2021, 11:13pm
5
Yes. It was late at night, and I was tired. My bad…
Try this in a dom0 terminal:
qvm-prefs sys-net kernelopts ‘nopat iommu=soft swiotlb=8192 iwlwifi.disable_rxq=1’
There is a possibility that your kernelopts in sys-net are empty. This will fill them with the required parameters that should allow you to use your killer wifi.
Full credit to:
@427F11FD0FAA4B080123 Thanks for the tip, unfortunately none of the PCI troubleshooting steps seem to have helped. I tried:
permissive
no strict reset
both options
Each time I had to reboot the machine (not just restart sys-net) in order to see the Wi-Fi device under the network applet and get the “device not managed” error. If I just restarted sys-net I only got the Ethernet connection.
The additional device that appears alongside WiFi is “vif5.0” which seems to be a Xen thing. (It also say…
Hi,
I don’t get the wifi network in my sys-net network applet.
The chipset (PCI 8086:06f0) is rather new and https://linux-hardware.org/index.php?id=pci:8086-06f0&page=4#status says: "The device is supported by kernel versions 5.7 and newer ". Thank you, @ludovic , for your explanations .
Therefore, I would like to use a newer kernel in sys-net.
sys-net currently uses:
[user@sys-net ~]$ uname -r
4.19.155-1.pvops.qubes.x86_64
Dom0 currently uses:
[cubes@dom0 ~]$ uname -r
5.9.14-1.qubes.x86_6…
2 Likes
