Bug 2361136 - Firmware fails to load for Intel(R) Wireless-AC 9560 160MHz
Summary: Firmware fails to load for Intel(R) Wireless-AC 9560 160MHz
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
: 2362529 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-19 17:06 UTC by Wilbur Jaywright
Modified: 2025-04-30 13:50 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-04-30 13:50:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Dmesg log (265.09 KB, text/plain)
2025-04-19 17:56 UTC, Wilbur Jaywright
no flags Details

Description Wilbur Jaywright 2025-04-19 17:06:42 UTC
After the in-place upgrade from Fedora 41 spin KDE Plasma to 42 (now an official version instead of a spin but still KDE Plasma), WiFi does not work on my StarLite Mk V. No WiFi networks show in the system tray menu, only Bluetooth tethers, and there is no WiFi on/off switch shown either. Rebooting to an older kernel restores WiFi. As mentioned in the linked Fedora Discussions page, `dmesg` shows “Direct firmware load for iwlwifi-so-a0-jf-b0-[number].ucode failed with error -2” repeated several times, with [number] counting down from 89 to 78. Using Bluetooth tethering, I reinstalled linux-firmware but to no effect.

Reproducible: Always

Steps to Reproduce:
1. Have my hardware running Fedora 41.
2. Perform in-place upgrade to Fedora 42.
3. Attempt to connect to WiFi.
Actual Results:
The system acts as if there is no WiFi card. Dmesg confirms that the WiFi card was detected but firmware failed to load.

Expected Results:
WiFi continues to work as it did using Fedora 41.

Comment 1 Peter Robinson 2025-04-19 17:24:45 UTC
What kernel do you have?
Is the iwlwifi-mvm-firmware package installed after upgrade, if so what version.
Do you have weak dependencies enabled or disabled.
Please attach the dmesg output as a text file.

> As mentioned in the linked Fedora Discussions page

What linked discussion page?

Comment 2 Wilbur Jaywright 2025-04-19 17:54:42 UTC
I put the discussions URL in the “URL showing the issue” field, but apparently that’s an advanced field And doesn’t show by default, anyways here it is: https://discussion.fedoraproject.org/t/fedora-42-in-place-update-completely-broke-wi-fi-on-my-starlite-mk-v/149147

Fedora 42 is using kernel version 6.14.2-300, and the old 41 kernel I used that has working WiFi is 6.13.11-200.

The iwlwifi-mvm-firmware package (with the new Fedora 42 kernel booted) says it is version 20250410, and it is installed.

I do not know if weak dependencies is enabled. I don’t think I enabled it, but I’m not sure how to check. /etc/dnf/dnf.conf does not show anything besides a comment and the [main] header, so I would assume it is not enabled.

Comment 3 Wilbur Jaywright 2025-04-19 17:56:20 UTC
Created attachment 2085886 [details]
Dmesg log

Comment 4 Peter Robinson 2025-04-19 19:30:35 UTC
(In reply to Wilbur Jaywright from comment #3)
> Created attachment 2085886 [details]
> Dmesg log

That's not the complete dmesg, it starts 70 seconds into the boot.

Comment 5 Peter Robinson 2025-04-19 19:35:52 UTC
[  128.917026] iwlwifi 0000:00:14.3: loaded firmware version 77.f92b5fed.0 so-a0-jf-b0-77.ucode op_mode iwlmvm

That shows the latest firmware in the firmware package is loaded (the 9560 devices are quite old so rarely get updated now).

[  129.019586] iwlwifi 0000:00:14.3: Detected RF JF, rfid=0x105110
[  129.020621] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4

What does 'sudo rfkill' report? It looks like it's putting itself in airplane mode somehow.

Comment 6 Wilbur Jaywright 2025-04-19 21:31:15 UTC
> That's not the complete dmesg, it starts 70 seconds into the boot.

I have no idea how to fix that. I censored a hardware address, and I did clear the log before rebooting, but other than that I didn’t trim the file.

> What does 'sudo rfkill' report?

One device. ID 0, type “Bluetooth”, device “hci0”, soft “unblocked”, hard “unblocked”.

Comment 7 Peter Robinson 2025-04-19 23:15:44 UTC
Can you add "pci=realloc=off" and see if that helps out?

sudo vi /boot/loader/entries/*-6.14.2-300.fc42.x86_64.conf

add "pci=realloc=off" to the end of the line that begins with "options root=/dev/" if you're unsure

Of course use what ever is your preferred editor.

Comment 8 Wilbur Jaywright 2025-04-19 23:55:56 UTC
> Of course use what ever is your preferred editor.

Only the high monks of Quadruno prefer Vim.

Comment 9 Wilbur Jaywright 2025-04-20 00:01:09 UTC
For what it’s worth, that asterisk didn’t work trying to open the file with Nano. I had to put the whole filename with the serial identifier.

Comment 10 Wilbur Jaywright 2025-04-20 00:02:22 UTC
> add "pci=realloc=off" to the end of the line that begins with "options root=/dev/" if you're unsure

Did that and rebooted, no effect.

Comment 11 Peter Robinson 2025-04-20 18:53:47 UTC
This is a kernel regression, not the firmware, the required firmware is there and hasn't changed recently.

Comment 12 Heber Vazquez 2025-04-24 13:02:02 UTC
The new rc3 resolve the wifi problem in my computer.
kernel-6.15.0-0.rc3.20250422gita33b5a08cbbd.29.fc43.x86_64.rpm

dnf install koji
mkdir kernel615; cd kernel615
koji download-build --arch=x86_64 kernel-6.15.0-0.rc3.20250422gita33b5a08cbbd.29.fc43

and install all the kernel packages that you need on your system.

Comment 13 Wilbur Jaywright 2025-04-25 12:40:43 UTC
> and install all the kernel packages that you need on your system.

No idea what that entails. I assume that's just any kmods I installed, but IDK how I would need to do that differently.

Comment 14 Wilbur Jaywright 2025-04-25 12:48:38 UTC
...Oh THOSE packages. Okay, was wondering how I would install the kernel once I had it.

The selftest package failed, but thankfully nothing else did. I ended up running `dnf install --skip-broken ./*` in the kernel 615 directory.

Comment 15 Peter Robinson 2025-04-27 18:35:38 UTC
*** Bug 2362529 has been marked as a duplicate of this bug. ***

Comment 16 aldo@gigantesco.org 2025-04-29 13:22:12 UTC
The new release 6.14.4-200 solved my problem.
Many thanks to the solver.

Comment 17 Wilbur Jaywright 2025-04-30 13:50:17 UTC
The new 6.14.4 kernel package, now available from Fedora, fixes the issue. I will note that the 6.15.0-rc3 kernel also had the fix. I had to do some puzzling, installing and uninstalling things in the right order, to get that rc3 kernel to uninstall though, do not recommend if this is not something you're comfortable with doing.


Note You need to log in before you can comment on or make changes to this bug.