-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to load firmware for wlan adapter #3643
Comments
Your conclusion is (almost) correct, WiFi is indeed initialized too early and adding the firmware to the symlinked directory doesn't work. However, the problem isn't the inconsistency between firmware versions and kernel - the firmware for BE200 is simply not installed by the As a remedy for your problem, the solution would be to add the firmware to the list of installed firmwares for Intel WiFi cards. Unlike other distributions we don't to that pre-emptively, as we need to cope with rootfs space constraints, but given that this WiFi cards doesn't seem to be an obscure one, adding support for it makes sense to me. |
``
Hm...strange, my memory tells me that I spotted somewhere firmware, but wrong versions, bellow iwlwifi-gl-c0-fm-c0-80 or above iwlwifi-gl-c0-fm-c0-83. But maybe my memory didn't serve well :) |
so, question is...any workaround? before firmware find its way into hassos? |
OK, to simplify life for everyone, I added PRs to two repos merge of those should add driver for |
and, as temporary workaround, I built my pwn image with provided patches, and updated with rauc. So, patches are also checked to work. |
Add iwlwifi-gl firmware, which is required for Intel BE200 card. Targets are generic_aarch64, generic_x86_64 and ova. * buildroot 19027bc796...1d7407c66b (1): > package/linux-firmware: add iwlwifi gl firmware Closes #3643.
Describe the issue you are experiencing
I am trying to get Intel BE200 working. Out of the box it does not work, as HAOS packs outdated firmware. Trying to update firmware using workaround #2225 does not work either, as it seems that
/mnt/data/supervisor/firmware
is mounted way too late, afteriwlwifi
is already loaded with an error.if after boot finished, in console I do
then module will load firmware and I get working interface. And then dmesg will show proper load.
so, workaround #2225 is only half-working. Suitable only for firmware loading at later stages.
so, we need either to mount
/mnt/data
very early in boot (but still unlikely to be good enough) or find a way to inject firmware to initrd or, ideally, have consistency between kernel modules and firmware versions :)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?
13.2
Did the problem occur after upgrading the Operating System?
No
Hardware details
QEMU/KVM 9.0.2
PCI (WLAN) and USB(BT) passthrough for BE200
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
relevant part of dmesg # dmesg | grep iwl [ 1.842538] iwlwifi 0000:01:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x80000000 [ 1.842553] iwlwifi 0000:01:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200 [ 1.844152] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-83.ucode failed with error -2 [ 1.845194] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-82.ucode failed with error -2 [ 1.845731] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-81.ucode failed with error -2 [ 1.847859] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-80.ucode failed with error -2 [ 1.848489] iwlwifi 0000:01:00.0: no suitable firmware found! [ 1.848490] iwlwifi 0000:01:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-80 [ 1.848491] iwlwifi 0000:01:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-83 [ 1.848492] iwlwifi 0000:01:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
The text was updated successfully, but these errors were encountered: