Iāve never have an issue using ax201 with fedora as sys-net since 4.1 rc, how about reinstall qubes ? is that possible ? if not, try installing, kernel-latest-qubes-vm and fedora-35 from testing repository, and create sys-net based on this fedora 35 template, donāt forget to change this vm kernel in qubes settings.
@51lieal makes a good point. In most cases, that should be automatic, but it might be a good idea to check, just in case.
Failing that, any chance of seeing the output of dmesg in sys-net?
One of the most notorious dances in the Linux kernel is that between the mainline kernel devs and the Intel devs. When one releases an update, the other one usually breaks, and it continues ātit-for-tatā
Thereās a chance that your iwlwifi kernel drivers are throwing a lot of errorsā¦
In case you donāt know how to do it (or if anyone else sees this post, as the Intel AX series will become more and more common), type this into a sys-net terminal:
sudo dmesg | grep iwl > dmesg.log
# ^ ^ ^
# | | |
# Show the log | |
# ------------- | |
# Filter out everything |
# except iwlwifi stuff |
# ------------------------- |
# Save the filtered stuff to a file called dmesg.log
# ---------------------------------------------------
That will give you a text file of what we need to figure out what is actually happening.
Feel free to redact any information you feel the need to