@alho There are no amdgpu (or any other graphics) changes in this update. Is it possible that firmware was updated and this is the first time booting with the new firmware? Firmware updates do not actually take effect until you put them in the initramfs, which typically means installing a new kernel.
Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.
@maketopsite While not exactly wrong, you are certainly not going to use new firmware without rebooting, it is also incomplete. Bodhi doesn't have a concept of you need to also install a new kernel or rebuild an initramfs to use the update. And the firmware does not do it itself for the same reason that dnf will never remove the running kernel, even if it is the oldest. The running kernel is considered a known good, and the initramfs is a part of that.
@jforbes I don't recall any firmware updates at same time. I afterwards installed both 7.1.1 and 7.1.2 and both works fine. I tried to rebuild the initramfs for 7.0.14 (running 7.1.2) it was a few bytes different, but 7.0.14 still doesn't work for my AMDGPU. What is really strange however, is that initramfs for all other 7.0.x kernels (and 7.1.x) is around 79MB in size, but 7.0.14 is only 44MB
It is not a problem to me, as I have moved on to 7.1.2 - but something is weird with that kernel.
I have never had anything like this happening on this system.
@alho have you tried regenerating the initramfs (sudo dracut -f /boot/initramfs-7.0.14-200.fc44.x86_64.img 7.0.14-200.fc44.x86_64) to see if it was just an incomplete/corrupted build?
It indeed work as expect but just like the previous version, the GPU power limit was set to 220 instead the previous 244 so for now I will use the 7.0.12 kernel instead.
@lordalfredo Yes, I did try to regenerate it, and just did again. The generated initramfs is 44MB in size, where all other 7.0.x and 7.1.x initramfs are 89MB, so something here is weird
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
default & performance tests pass (KVM)
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Working fine here.
Intel NUC NUC13ANHi7 (NUC13ANHi7000) (rev N11225-207) 1 x 13th Gen Intel(R) Core(TM) i7-1360P Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
AMDGPU driver not working. Falls back to 1024x768 AMD Ryzen 3 5300U
@alho There are no amdgpu (or any other graphics) changes in this update. Is it possible that firmware was updated and this is the first time booting with the new firmware? Firmware updates do not actually take effect until you put them in the initramfs, which typically means installing a new kernel.
Framework 13 AMD 7040 with
AMD Ryzen™ 7 7840U w/ Radeon™ 780M Graphics × 16Laptop display nominal at 2256x1504, not able to test with external monitor atm.
no regressions noted in my environment
Works well on a Framework 13 with AMD Ryzen AI 300 Series CPU.
working fine in both x86_64 and aarch64 here, also on top of rawhide/aarch64
Looks good here. Ryzen 7800x3d, Asus B650E-E, Nvidia from rpmfusion w/amdgpu enabled. No problems in dmesg.
Works great! LGTM! =)
@jforbes
FEDORA-2026-f09b583788
So this info is please wrong ?
@maketopsite While not exactly wrong, you are certainly not going to use new firmware without rebooting, it is also incomplete. Bodhi doesn't have a concept of you need to also install a new kernel or rebuild an initramfs to use the update. And the firmware does not do it itself for the same reason that dnf will never remove the running kernel, even if it is the oldest. The running kernel is considered a known good, and the initramfs is a part of that.
Works for me.
Works
AMD 5600G
PASS
@jforbes I don't recall any firmware updates at same time. I afterwards installed both 7.1.1 and 7.1.2 and both works fine. I tried to rebuild the initramfs for 7.0.14 (running 7.1.2) it was a few bytes different, but 7.0.14 still doesn't work for my AMDGPU. What is really strange however, is that initramfs for all other 7.0.x kernels (and 7.1.x) is around 79MB in size, but 7.0.14 is only 44MB It is not a problem to me, as I have moved on to 7.1.2 - but something is weird with that kernel. I have never had anything like this happening on this system.
AMD Ryzen AI 9 HX 370 w/ Radeon 890M
lspci -v | grep amdgpu pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted Kernel driver in use: amdgpu Kernel modules: amdgpu@alho have you tried regenerating the initramfs (
sudo dracut -f /boot/initramfs-7.0.14-200.fc44.x86_64.img 7.0.14-200.fc44.x86_64) to see if it was just an incomplete/corrupted build?It indeed work as expect but just like the previous version, the GPU power limit was set to 220 instead the previous 244 so for now I will use the 7.0.12 kernel instead.
@lordalfredo Yes, I did try to regenerate it, and just did again. The generated initramfs is 44MB in size, where all other 7.0.x and 7.1.x initramfs are 89MB, so something here is weird
test suite completed
This update has been obsoleted by kernel-7.0.14-201.fc44.