PÁLI Gábor János

Unfortunately, I have just noticed that this patch has been made part of both Linux 6.6.50 and Linux 6.10.9 that are integrated into `wifibox-alpine` `20240911`. This means that the problem...

Based on [my earlier comment above](https://github.com/pgj/freebsd-wifibox/issues/137#issuecomment-2456476641), I believe the reason for what you see is that the `ath11k` driver still does not know how to deal with virtualization. There seems...

Uhm, that is interesting. I assume that the patch above would not help that much.

Aw, now I see. MSI is not enabled for the card, hence we have these empty values. That is indicated by `Enable-`.

I am curious then what the following command says for you: ```shell sysctl hw.pci.enable_msi ```

Yeah, thanks for the response. For what it is worth, that is what I expected. The [Linux MSI documentation](https://www.kernel.org/doc/Documentation/PCI/msi-howto.rst) (since `lspci` is a Linux tool) has some hints about the...

Changing anything around the MSI will not help immediately, I believe. That is because the `ath11k_pci` Linux driver will not be able to discover the MSI vectors automatically. We will...

What does `pciconf` say by the way? ``` pciconf -lc pci0:2:0:0 | fgrep MSI ```

Apparently, `pciutils` has another tool, called `setpci`, which [can be used to enable MSI explicitly](https://www.linux.org/threads/how-to-configure-and-use-msi-interrupts-in-pcie.45973/) as follows: ``` setpci -s 2:0.0 COMMAND=0510 ```

For what it is worth, it worked for me... Even though the MSI was enabled, `setpci` seemed to trigger the recreation of the vector as its coordinates changed. It confused...