Hi, it’s jodi again. Forum stopped me from replying.
So created this account.
This ioapic allowed my trackpad to work. Network still not working even after fedora. Will try to troubleshoot it further.
Should I remove module blacklist parameter now? Or it need to be kept?
Most probably it’s a problem with missing firmware for your WiFi controller in sys-net template.
You’ll need to download the missing firmware from another system and manually move it to the sys-net template.
But it’s not certain that it’s an issue with firmware so it’d be better to look for errors in dmesg output in sys-net.
You should keep the module blacklist for your trackpad to work.
Just asked about this parameter, if there is any vulnerability associated with it.
I will keep it if you say so.
Correction, I’m not sure if it’s needed. If Qubes OS works without blacklisting then you can remove the blacklisting.
I don’t know whatever there is any vulnerability associated with it.
One more thing dmesg has large output in sys-net.
What is relevant?
How to remove blacklist module if I want to?
Some errors related to PCI devices. They may be printed in red color.
You need to find the messages associated with your WiFi controller.
The module blacklisting that you did to boot into Qubes OS installer was temporary and it wasn’t saved anywhere so if you didn’t add the module blacklisting in dom0 after installing Qubes OS then you don’t have it right now.
Module blacklist parameter is there in grub parameters where I put ioapic new
This seems to be the problem, but I’m not sure what’s wrong there. Maybe a problem with firmware of kernel driver.
What’s your WiFi controller PCI ID? Check the output of this command in dom0:
lspci -nn | grep Qualcomm
The PCI ID will be at the end in the brackets like this [XXXX:XXXX].
Then you can try to remove it during Qubes OS boot in GRUB menu for a test the same way you’ve added it for installer. If Qubes OS will boot without an issue then you can remove it from GRUB default config and update the GRUB config.
Seems like it’s missing the firmware:
https://linux.debian.kernel.narkive.com/qyNWUY73/bug-1026028-qualcomm-nfa725a-not-working-on-firmware-linux-nonfree-20221109-4
You’ll have to find and download it on another system and then move it to your sys-net template.
01:00.0
17cb:1103
Seems to be the same Qualcomm NFA725A as in the discussion in my previous link.
Download the files from here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/ath11k/WCN6855/hw2.0
And copy them in sys-net template to this directory:
/lib/firmware/ath11k/WCN6855/hw2.0/
Or you can download the linux-firmware archive with signature and check the signature to be sure that the files are valid:
Import the keys:
gpg --keyserver hkp://keys.gnupg.net --recv-keys 0x632D3A06589DA6B1
gpg --keyserver hkp://keys.gnupg.net --recv-keys 4CDE8575E547BF835FE15807A31B6BD72486CFD6
Go to:
https://cdn.kernel.org/pub/linux/kernel/firmware/
and download linux-firmware-*.tar.xz linux-firmware-*.tar.sign sha256sums.asc
Check the hash:
gpg --verify sha256sums.asc
sha256sum -c sha256sums.asc
Verify the archive:
unxz linux-firmware-*.tar.xz
gpg --verify linux-firmware-*.tar.sign
And then get the files from there.
After copy files there do I need to run any commands?
I have copied 4 files there.
Still after restart not connected.
And trackpad tap for click is not working even now.
No, it should work if missing firmware was the problem.
Can you get the sys-net logs using this command in sys-net:
sudo journalctl -b > journalctl.log
And upload it here so I can check it?
Did you remove the module_blacklist=ucsi_acpi from the GRUB config? Is ioapic_ack=new still present in the config?
For completeness sack, 4 bin files I have put in hw2.0
I haven’t removed anything and all parameters are still there.
When I put journalctl command in sys-net, I have got no result.
My reading comprehension was bad, so I didn’t understand your question right.
To enable tap to click go to Q → gear icon → System Settings → Mouse and Touchpad
Then in the Devices tab open the Touchpad tab and you’ll see the option to enable it.
This command:
sudo journalctl -b > journalctl.log
Will create the log file in the current directory (with /home/user/journalctl.log path by default) and you can copy it from there.
journalctl.log (156.1 KB)
I am replying for below post.
You are right, it wasn’t there but after placing it towards right and reboot, issue not resolved yet. What is the next step, you are really helpful, thank you for that.
I can see your PCI ethernet controller is attached to sys-net but there is no PCI wireless controller there.
Open the sys-net Qubes Settings → Devices tab and make sure that your wireless controller is in the right column. If it’s not then move in from left column to the right column and then try to start sys-net again.