Services enabled on sys-net:
clocksync
network-manager
As you can see my WiFi adapter is connected to sys-net and therefore it should be possible to use it. I have no clue why it does not.
My sys-net is using fedora-34 template and I am using the 4.1 version of qubes os. Also there are no updates avaiable for all templates.
I also downloaded the official linux driver from intel (iwlwifi-ty-59.601f3a66.0.tgz) and copied it to firmware folder on TemplateVM, which did not help either.
Looks like this also did not help.
Furthermore I noticed I am unable to update dom0.
When using the Qubes Update I get the following details: dom0 Update - Pastebin.com
And when trying to update via Qubes Manager I get the following:
Maybe this could be the problem?
Since I am also only able to select Kernel 5.10x
Getting the AX210 no vPro wifi working: this one has been a pain in the ass. so far, the only way I can get it working is this: Using kernel 5.10.109-1 Install firmware-iwlwifi in template On VM boot:
Get a root terminal
rm /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
modprobe -r iwlmvm && modprobe -r iwlwifi
modprobe iwlwifi && modprobe iwlmvm
This gets the wifi working until I shutdown Further work to be done here for sure
Installed newest non-LTS Kernel via kernel-latest-qubes-vm.
This results in getting the Kernel 5.16.18-2.fc32
I applied this to all qubes and restarted sys-net
-did not work
Installed fedora-35, updated it and used it for sys-net
-did not work
Also I tried to use fedora-35 and debian-11 for sys-net
-both did not work
I do not understand why wifi is not working here, given the fact that it did work in Ubuntu while I used it and even with debian here in qubes it does not work
I start to get crazy about this
If it is needed my notebook is the following: MSI GP66 Leopard 11UG-248
@enmus:
TOR is shutdown anytime I use clearnet and sys-net is configured as UpdateVM. This was not the problem I guess. But it works now, seems that this was only temporary issue.
Sorry but I think I do not understand what I have to put in the part of “XX”, so I have downloaded the newest tar and moved the whole content over to firmware folder and overwrite all existing files. Hope this was correct, I’m still learning
But this did not help either, still no Wifi access in Network-Manager.
Here is the output of the command after mv of this tar: sys-net dmesg2 - Pastebin.com
Ok forget about my previous post, it was for AX201 and its drivers are missing in debian firmware-iwlwifi package so I thought that your driver is missing as well.
I’ve checked your log and this error:
[ 4.191180] iwlwifi 0000:00:06.0: Timeout waiting for PNVM load!
[ 4.191303] iwlwifi 0000:00:06.0: Failed to start RT ucode: -110
Weird, since I am using 5.16.x kernel atm and also I tried fedora-35 before switching back to debian-11 without success as David mentioned this should work.
While running these commands I get no errors, but when I run grep iwl after that, yes same errors.
Also maybe it was broken again after kernel 5.16.5. You can try to use kernel-5.16.5 from Qubes first: sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest-qubes-vm-5.16.5-1.fc32.qubes.x86_64
Then install it in dom0: sudo dnf install /path/to/kernel-latest-qubes-vm-5.16.5-1.fc32.qubes.x86_64.rpm
I’ve linked to the specific topic in document:
Using kernel installed in the VM
Both debian-9 and fedora-26 templates already have grub and related tools preinstalled so if you want to use one of the distribution kernels, all you need to do is clone either template to a new one, then:
If you’d like to use a different kernel than default, continue reading.
Clone your sys-net template (fedora-35 for example) and change cloned template qvm-prefs then select this cloned template as sys-net template and set sys-net kernel to (none).