So, booting used to go by the standard device locations mapped by the BIOS, as in /dev/sda the problem is, searching for devices at bootup is sometimes inconsistent using the mapped locations, so it was determined it’s better to use the device ID for the particular partition/sub-volume combination of whatever particular OS/Distro was booting since this ID is unique to each.
Anyway, my system hangs looking for a swap partition with a particular UUID (Universally Unique Identification) that does not exist anymore, and it used to time out after 45 sec (the set limit for the bootup target) and now that limit has been set to infinite, so never stops. Technically it’s not hung, just waiting for something that will never happen.
1 Like
Thanks for the explanation 
I have noticed that in the screenshots posted by people in this thread, they can see the text output of the bootup process, whereas I see only a completely dark screen. Is there anyway I can access the text output?
[ESC] key
1 Like
Pressing the escape key only shows something meaningful after the OS logo appears. This doesn’t happen in kernel version 6.8.10, however. It doesn’t really show anything and just stays at that screen indefinitely.
Other people can access the text output, so I’m assuming they see the OS logo first? So do we have different issues?
Yeah mine happens after the Plymouth screen is loading/loaded. The others could be booting in non quiet mode, so messages are displayed from start to finish
So it seems we might have different issues. Any idea what’s going on with my system?
For temporary showing of the text you can use the grub boot menu and press the e key while the menu is displayed. Then on the line that begins with linux, if you remove the rhgb and quiet from that line before continuing the boot it should show the text as it is progressing through the boot.
1 Like
Will try this in some time
1 Like
Not off the top of my head. Also not sure this isn’t related, but we should watch closely since if it is, the two problems deserve their own topic. I or another moderator can/will split it if that is the case.
1 Like
Hi @privacyfreak84 ,
This is definitely a different issue than what I am experiencing. You’re getting a kernel panic so it doesn’t even make it to the Plymouth bootsplash. I’m going to make a new topic from my first comment to split this off, I’ll try to capture all of the comments related to my and others issue with the recent kernel update so as to clean up this topic for you.
OK. Any idea how I can fix it?
Ahh, no. I’m still trying to work through my issue. I’m sure @computersavvy is looking at what you posted and will respond in due course. For now, boot the earlier kernel like I am and continue to try to troubleshoot it. At least the system is usable on 6.8.9 so there is that.
1 Like
Here’s hoping both our issues get resolved soon 
Created a new topic for this: Kernel Panic due to missing dependency libsystemd-core
RIP
at the bottom of the screenshot. . . I had to chuckle. 
1 Like
Solved by reinstalling kernel:
sudo dnf reinstall kernel*
2 Likes
reinstalling kernel haven’t worked for me.