Just upgraded to kernel-6.15.3 and system wont boot with amdgpu. After discussions decided to downgrade amd-ucode and amd-gpu to 20250311-1 and rebuild initramfs. System now boots fine. amd-ucode-firmware and amd-gpu-firmware 20250613-1 is not compatible with kernel-6.15.3 Reproducible: Always
Please state where that particular detail is documented, AMD is generally good with coordinating their updates so coming out with a broad statement as such without links to documentation is not useful. Also provide details of the actual GPU you're having issues with. PS amd-ucode-firmware is irrelevant here as it's early boot firmware, not GPU firmware, and never received updates in the month between updates.
The report from OP is probably a bit unclear or misleading, but there is actually a known upstream regression in linux-firmware for certain AMD iGPUs, and a fix is already available upstream. Please see https://gitlab.freedesktop.org/drm/amd/-/issues/4329. It requires the following MR to work: https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/587. Reverting to the previous version of amd-gpu-firmware also works. I assume this is the same issue that OP reported.
*** Bug 2375201 has been marked as a duplicate of this bug. ***
I've talked to upstream. A new release to hopefully resolve this is imminent.
FWIW I have the same issue with Ryzen 9 9900X iGPU.(In reply to Peter Robinson from comment #1) > Please state where that particular detail is documented, AMD is generally > good with coordinating their updates so coming out with a broad statement as > such without links to documentation is not useful. Also provide details of > the actual GPU you're having issues with. PS amd-ucode-firmware is > irrelevant here as it's early boot firmware, not GPU firmware, and never > received updates in the month between updates. FWIW I have the same issue with Ryzen 9 9900X iGPU.
Upstream release tagged. Tarball will show up soon.
Peter has created builds. We still need bodhi updates.
FEDORA-2025-7feed8b25a (kernel-6.15.4-200.fc42 and linux-firmware-20250627-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7feed8b25a
FEDORA-2025-f6f8526a43 (kernel-6.15.4-100.fc41 and linux-firmware-20250627-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f6f8526a43
FEDORA-2025-7feed8b25a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7feed8b25a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7feed8b25a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-f6f8526a43 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f6f8526a43` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f6f8526a43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Michael Catanzaro from comment #7) > Peter has created builds. We still need bodhi updates. Thank you Michael for explaining how to do updates, I did not know! Like the upstream release there is coordination going on behind the scenes for coordinated kernel updates and various other things :-)
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f6f8526a43 solves this for me. I will close this report when these packages hit updates repos.
FEDORA-2025-7feed8b25a (kernel-6.15.4-200.fc42 and linux-firmware-20250627-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-f6f8526a43 (kernel-6.15.4-100.fc41 and linux-firmware-20250627-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.