Kernel 5.4 iwlwifi firmware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm running Fedora 31 on my laptop with a Killer Wi-Fi 6 AX1650 network
card. Under 5.3 kernel series my card worked fine but I've noticed that
under the 5.4 series the firmware fails to load with the following
kernel message:

iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
iwlwifi 0000:00:14.3: Direct firmware load for
iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2
iwlwifi 0000:00:14.3: Direct firmware load for
iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2
iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM
iwlwifi 0000:00:14.3: Found debug configuration: 0
iwlwifi 0000:00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
iwlwifi 0000:00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless
Network Adapter (201NGW), REV=0x338
iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor.
iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
iwlwifi 0000:00:14.3: Status: 0x00000000, count: 2127625685
iwlwifi 0000:00:14.3: Loaded firmware version: 48.4fa0041f.0
iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor.
iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:

It then produces a longish error dump probably better suited for a
bugtracker than a mail list. I can provide it here if that's help though!

Booting back into any of the 5.3 kernels does not produce this error and
the card works fine, all three released 5.4 kernels for F31 have done
this so far. dnf reports my system as up-to-date and I have the
available iwlwifi firmware packages installed. It looks like they just
aren't updated for the 5.4 kernel or something? I know I can head to
kernel.org, grab the firmware tarball and extract it to /lib/firmware
but I'd like to avoid that if possible.

Anyone else with this card having issues?

Thanks!



-- 
---
Leander Hutton
leander@xxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux