On my new laptop (HP 845 G9) the WiFi controller is not working. The device has been forwarded to sys-net but it fails to configure the device and add a network interface for it.
Not sure if this is relevant for the issue, in order to get Qubes running at all on this latpop I had to add x2apic=false to the Xen boot parameters.
dmesg shows the following error messages related to it:
[user@sys-net ~]$ sudo dmesg|grep -v audit|grep -iP '(ath11|mhi)'
[ 2.693245] ath11k_pci 0000:00:09.0: BAR 0: assigned [mem 0xf2000000-0xf21fffff 64bit]
[ 2.697604] ath11k_pci 0000:00:09.0: MSI vectors: 1
[ 2.698198] ath11k_pci 0000:00:09.0: wcn6855 hw2.1
[ 2.903740] mhi mhi0: Requested to power ON
[ 2.903757] mhi mhi0: Power on setup success
[ 95.397747] mhi mhi0: MHI did not load image over BHI, ret: -5
[ 192.609086] mhi mhi0: Device failed to clear MHI Reset
[ 192.609142] mhi mhi0: Error moving from PM state: Firmware Download Error to: DISABLE
[ 192.609385] ath11k_pci 0000:00:09.0: failed to power up mhi: -110
[ 192.609416] ath11k_pci 0000:00:09.0: failed to start mhi: -110
[ 192.609440] ath11k_pci 0000:00:09.0: failed to power up :-110
[ 192.615038] ath11k_pci 0000:00:09.0: failed to create soc core: -110
[ 192.615078] ath11k_pci 0000:00:09.0: failed to init core: -110
[ 192.687477] ath11k_pci: probe of 0000:00:09.0 failed with error -110
I’ve already upgraded sys-net to kernel 6.0.2-2.fc32.qubes.x86_64 (via the kernel-latest-qubes-vm in dom0, kernel selected in the qubes settings of sys-net).
Any hints on how to get WiFi working on this device? Already tried “Configure strict reset for PCI devices” in the settings without success.
It’s using the default (Fedora 36). Will try again with Debian tonight but I don’t really expect the distro to change anything if the kernel remains the same (from kernel-latest-qubes-vm).
I’ve already gotten the package linux-firmware-20221109-144.fc36.noarch installed in sys-net and the latest version on kernel.org is also 20221109, so it should be exactly the same version.
Does it matter that modinfo only lists the hw2.0 firmware for ath11k_pci (and not the hw2.1 firmware)?
Can you please give me some more details/commands on how to check this (sorry I’m still new to Qubes and I don’t have much experience with debugging that kind of driver issues)? Didn’t find anything related to msi in the Qube Manager and a Google search for qubes "msi_bus" also didn’t return anything useful.
In the mean time I’ve also booted up a FC37 live iso (also using Kernel 6.0) and there it is working. The first notable difference in the dmesg is that it says MSI vectors: 32 with the live system while it only says MSI vectors: 1 in sys-net in Qubes, this may confirm that it is indeed related to MSI.
Well I’m sorry, but I can’t be of a bigger help then. I’m still confused there’s no “kernel driver in use” line in your lspci's output, and "Enable - " should definitely indicate MSI is disabled. I never heard of the opposite.
Gotten another lspci output within the first 90 seconds and there the ath11k_pci driver is connected, so I assume that the driver only disconnects due to an error:
In the beginning lsmod says that ath11k_pci is in use, only later on after a timeout it gets unused (and also the “Kernel driver in use:” in lspci disappears.
Removing and reloading the ath11k_pci module in sys-net will freeze the whole system (including dom0) so that it doesn’t react to keyboard/mouse input any more, requiring a hard powerdown to recover. But it isn’t a kernel panic, the clock in the xfce panel is still updating so something is still running.