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
I have the same problem with dom0 updates.
Seems to be a transient problem with repo.
For me it happens from time to time over tor, especially 404s
You can try this from here:
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
Also you can try to install kernel-latest-qubes-vm
and use kernel-latest for your VM.
It helped someone:
So I tried a few things now.
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
Tested the code posted by @tzwcfq
-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.
What do you have in this command output?
sudo dmesg | grep iwl
Check this command output and get the iwlwifi-so-a0-hr-b0-XX.ucode from the output with the latest XX number supported by your kernel from here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/iwlwifi-so-a0-hr-b0-XX.ucode
Or from tar signed archive from here:
https://mirrors.edge.kernel.org/pub/linux/kernel/firmware/
Then copy this file in /lib/firmware.
The output of the command: sys-net dmesg - Pastebin.com
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
Should have been fixed in kernel 5.16:
https://bugzilla.kernel.org/show_bug.cgi?id=212371
Do you have the same error if you run these commands?
sudo rm /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
sudo modprobe -r iwlmvm && sudo modprobe -r iwlwifi
sudo modprobe iwlwifi && sudo modprobe iwlmvm
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.
Maybe there is a problem with kernel from Qubes package.
You can try kernel from fedora/debian template instead maybe it’ll work:
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
Running your command results in: “No match for argument: kernel-latest-qubes-vm-5.16.5-1.fc32.qubes.x86_64”
And for using a VM Kernel, I do not know if I am doing it right:
- Run “sudo qubes-dom0-update qubes-kernel-vm-support kernel-devel” in dom0
- Run “sudo qubes-prepare-vm-kernel 5.10.112-1.fc32.qubes.x86_64 4.1.qubes” in dom0
- Run “sudo apt install linux-image-amd64 linux-headers-amd64 grub2 qubes-kernel-vm-support” in debian-11 template
- Set Kernel of sys-net to “none” since virtualization is HVM?
Output of Debian:
If this was correct, this unfortuantely also did not work ^^
Then you can try to manually download the package and move it in dom0:
https://yum.qubes-os.org/r4.1/current-testing/dom0/fc32/rpm/kernel-latest-qubes-vm-5.16.5-1.fc32.qubes.x86_64.rpm
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:
qvm-prefs <clonetemplatename> virt_mode hvm qvm-prefs <clonetemplatename> kernel ''
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).
Both do not work unfortuanetly.
Additionally I tried to use 5.15.11-1 Kernel, since I used a 5.15.x one on KDE Plasma, but this also did not work
What kernel version do you have installed in fedora-35 template (or what template did you try)?
Yes I used fedora-35
These kernels are installed and I tried all of them currently using the 5.16.5 one
I’m out of ideas for now.
I can suggest you to change the topic name to “Intel Wi-Fi 6E AX210 firmware doesn’t work” or something so someone who has the same Wi-Fi adapter can notice your thread and maybe give advice.