Description of problem: It appears that linux-firmware update is not rebuilding initramfs as it should. Please pay close attention to the timestamps: $ sudo _TRANSPORT=kernel journalctl --output=short-full -S "Fri 2021-12-17 20:00:41 CET" | grep -P '(?<![=|])(DMUB.*PSP|Linux version)' Fri 2021-12-17 20:00:41 CET snowball3 kernel: Linux version 5.15.10-200.s0ix01.fc35.x86_64 (mockbuild@napoleon2) (gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7), GNU ld version 2.37-10.fc35) #1 SMP Fri Dec 17 19:23:58 CET 2021 Fri 2021-12-17 20:00:43 CET snowball3 kernel: [drm] Loading DMUB firmware via PSP: version=0x01010019 Mon 2021-12-20 13:06:06 CET snowball3 kernel: Linux version 5.15.10-200.s0ix01.fc35.x86_64 (mockbuild@napoleon2) (gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7), GNU ld version 2.37-10.fc35) #1 SMP Fri Dec 17 19:23:58 CET 2021 Mon 2021-12-20 13:06:07 CET snowball3 kernel: [drm] Loading DMUB firmware via PSP: version=0x01010019 Wed 2021-12-22 19:13:35 CET snowball3 kernel: Linux version 5.15.11-200.s0ix01.fc35.x86_64 (mockbuild@napoleon2) (gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7), GNU ld version 2.37-10.fc35) #1 SMP Wed Dec 22 18:33:22 CET 2021 Wed 2021-12-22 19:13:36 CET snowball3 kernel: [drm] Loading DMUB firmware via PSP: version=0x0101001C $ LANG=C sudo dnf history linux-firmware ID | Command line | Date and time | Action(s) | Altered ------------------------------------------------------------------------------------------------------------------------------------ 591 | --enablerepo=rpmfusion-free-updates-testing --enablerepo=rpmfusion-nonfree-up | 2021-12-20 13:02 | Upgrade | 20 < Even though I updated linux-firmware on 20th December and rebooted directly afterwards, newer 0x0101001C firmware was not being used until I installed an updated kernel and rebooted two days later. This is very bad as the update takes an effect with an indeterminate delay, which can lead to all sorts of issues when testing firmware bugfixes or looking for regressions. Is there a rationale behind this behaviour or is this just an oversight?
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.