sys-net fails to load ath10k_pci after fedora-29 update

[seaclue]

After a fresh Qubes os install (4.0.1), wifi works fine, after fedora-29 update, sysnet can't load the firmware,

[user@sys-net ~]$ sudo dmesg | grep ath10k

[   12.294827] ath10k_pci 0000:00:06.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0

[   13.386937] ath10k_pci 0000:00:06.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:06.0.bin failed with error -2

[   13.386998] ath10k_pci 0000:00:06.0: Direct firmware load for ath10k/cal-pci-0000:00:06.0.bin failed with error -2

[   13.614850] ath10k_pci 0000:00:06.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901

[   13.614952] ath10k_pci 0000:00:06.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0

[   13.615566] ath10k_pci 0000:00:06.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877

[   16.681014] ath10k_pci 0000:00:06.0: unable to read from the device

[   16.681038] ath10k_pci 0000:00:06.0: could not execute otp for board id check: -110

[   16.681061] ath10k_pci 0000:00:06.0: failed to get board id from otp: -110

[   16.681106] ath10k_pci 0000:00:06.0: could not probe fw (-110)

[user@sys-net ~]$

Same thing happens with an updated fedora-28, I had to keep an outdated fedora-29 clone for the wifi to work. I updated dom0, still the same.

Thanks

[awokd]

'seaclue' via qubes-users:

Try Debian too. Maybe Fedora broke one of their packages.

[seaclue]

'awokd' wrote:

> Try Debian too. Maybe Fedora broke one of their packages.

Tried it, didn't work.

[seaclue]

I switched to kernel-latest and now it's working.

[awokd]

'seaclue' via qubes-users wrote on 3/18/19 3:32 PM:

> I switched to kernel-latest and now it's working.
>

Interesting- in the template or dom0?

[seaclue]

> Interesting- in the template or dom0?

both.

[brenda...@gmail.com]

On Monday, March 18, 2019 at 11:33:03 AM UTC-4, seaclue wrote:
> I switched to kernel-latest and now it's working.

Can confirm: same wifi chipset and my fedora-29 networking was broken for me...as my system default VM kernel was rather old (being a 4.0 install from last year, upgraded regularly).

I suspect that one of the later QubesOS R4 ISO re-spins changed the default kernel for VMs (otherwise, I suspect we'd hear about this more). By changing my global default* kernel in VMs to one of the 4.19 branches (kernel-latest) from current-testing, networking miraculously worked again in post Fedora-26 templates.

Notably, the wifi firmware version in both f26 and f29 were the same, so it didn't occur to me that there would be a set of software in the newer templates that failed to work with older kernels (kernels which had worked in older templates).

Thanks,
Brendan

* I initially fixed it by setting the sys-net kernel to the 4.19 branch, but then decided to just go with it everywhere, reverted that change to default and then changed the global default.

[Anhangá]

Em segunda-feira, 18 de março de 2019 12:33:03 UTC-3, seaclue escreveu:
> I switched to kernel-latest and now it's working.

Sorry, but how you did that?

On dom0 I did sudo qubes-dom0-update kernel-latest and installed the kernel 5.1.2-1 as explained on (https://www.qubes-os.org/doc/managing-vm-kernel/) and checked using uname -r after reboot. But on Global settings of dom0 the default kernel still 4.14.119-2 and there's no option for kernel-latest or 5.1.2-1. Same situation on every AppVM.

So, how can I set kernel-latest or 5.1.2-1 as an option for my dom0 or AppVMs?

[Brendan Hoar]

I think it was the kernel-latest-qubes-vm package from the -testing repo.

[awokd]

Brendan Hoar:

> I think it was the kernel-latest-qubes-vm package from the -testing repo.
>

If upgrading the kernel doesn't help, try changing your sys-net to use
the Debian template.

[Anhangá]

Following the Kernel Upgrade section in (https://www.qubes-os.org/doc/software-update-dom0/) solved my problem.
I have a wireless card that uses QCA9377 chipset and ath10k_pci driver. For some reason, the newest kernel version available on testing repo can handle correctly the ath10k_pci driver.