Fedora does not boot after upgrade to kernel 6.15.3 with amdgpu drm error

I have had the same problem. With a kernel panic after an update and moving to kernel 6.15-200-fc42.

I also use LUKS as well as an AMD 8845HS with an integrated 790M GPU.

I found this thread. Fedora DEAD after Kernel 6.15.3-200 update - No initramfs - Kernel panic: unable to mount root fs on unknown-block(0 0)

After running the following command followed by a reboot, the problem is solved for me.

sudo dracut --regenerate-all --force

So this may be worth a try. I did not downgrade any AMD packages.

The simpler instruction is

initrd=/boot/initramfs-6.14.11-300.fc42.x86_64.img
sudo lsinitrd --unpackearly $initrd
sudo lsinitrd --unpack $initrd

For more information, run man lsinitrd.

1 Like

I was thinking that folks would be more interested in just listing the files rather than unpacking them.

In any case, I could’ve avoided doing all of this:

sudo cpio -tvF /boot/initramfs-6.15.3-200.fc42.x86_64.img
sudo dd if=/boot/initramfs-6.15.3-200.fc42.x86_64.img skip=46|unzstd|cpio -tv

if I’d just done the second part of their instructions, or followed your advice and read the man page for lsinitrd. :slight_smile:

sudo lsinitrd /boot/initramfs-6.15.3-200.fc42.x86_64.img
1 Like

@barryascott, I’ve reported this, and have an AMD Radeon RX 5700:

There are new updates to kernel and the firmware.

1 Like

Well, I’m on Fedora 42 and initramfs (/boot/efi/e7c709f5753d440cb90d54c186a740eb/6.15.4-200.fc42.x86_64/initrd) is indeed compressed with gzip:

$ file main_archive                                  
main_archive: gzip compressed data, max compression, from Unix, original size modulo 2^32 95706112

New kernel & firmware, new problems. Now the waking up from standby fails with message ā€œThe screen locker is broken ā€¦ā€ and when pressing Ctrl+Alt+F1 it all goes to black.
This is probably material for a new topic?
Update: seems like a known issue with qt

Can someone please tell me if my problem is related to this?

The btrfs error is concerning. Unsafe shutdown with btrfs may loose some data but should be repairable.

With 6.15.3 you may not be getting far enough in the boot process to see the btrfs problem. Do you have a KDE Installer USB? That will allow you to read man 8 btrfs-rescue, try mounting the system drive and view btrfs errors if there is a problem.

I don’t think I do. I am a noob to linux, so could you please share any steps I should take? Also, can the conversation please continue in the new thread relating to this issue?