search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
4.9k stars 972 forks source link

ath11k/ath12k firmware missing #3621

Open OdinVex opened 6 days ago

OdinVex commented 6 days ago

Describe the issue you are experiencing

I've attempted to add the firmware for ath11k and ath12k (to support my 17cb:1107 WiFi 7 card) to /mnt/data/supervisor/firmware and reboot but I'm not sure it's loading, dmesg's only output is:

[    5.322474] ath12k_pci 0000:06:00.0: BAR 0: assigned [mem 0xf0200000-0xf03fffff 64bit]
[    5.322512] ath12k_pci 0000:06:00.0: enabling device (0100 -> 0102)
[    5.323444] ath12k_pci 0000:06:00.0: failed to get 16 MSI vectors, only -28 available
[    5.323473] ath12k_pci 0000:06:00.0: failed to alloc msi: -28
[    5.325225] ath12k_pci: probe of 0000:06:00.0 failed with error -28

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6.46-haos

Did the problem occur after upgrading the Operating System?

Ongoing

Hardware details

17cb:1107, WiFi 7 Card, a Qualcomm "FastConnect" WCN7850 (WCN7851) M.2 M-Key.

Steps to reproduce the issue

  1. Install an ath11k/ath12k wireless card.
  2. Boot the system
  3. Copy firmware files.
  4. Reboot. ...

Anything in the Supervisor logs that might be useful for us?

N/A, None

Anything in the Host logs that might be useful for us?

[    5.322474] ath12k_pci 0000:06:00.0: BAR 0: assigned [mem 0xf0200000-0xf03fffff 64bit]
[    5.322512] ath12k_pci 0000:06:00.0: enabling device (0100 -> 0102)
[    5.323444] ath12k_pci 0000:06:00.0: failed to get 16 MSI vectors, only -28 available
[    5.323473] ath12k_pci 0000:06:00.0: failed to alloc msi: -28
[    5.325225] ath12k_pci: probe of 0000:06:00.0 failed with error -28

System information

No response

Additional information

Permissions on the files are correct, I even tried just copying ath11k and ath12k folders alone since they don't exist in HAOS, no effect. Rebooting server doesn't change anything.

OdinVex commented 6 days ago

linux-firmware has it and supposedly it's been supported since kernel 6.3. I'm thinking the driver isn't detecting the firmware files because of the whole symlinking deal.