I went for “ok, I didnt play arount with grub, next update will make this go away!” Turns out it didnt. The recent update to 5.19.4-200 fails to boot as well with the same output.
There was an error message when I booted with 5.18.18-200 indicating problems with the contents of this repo:
I need this as a dependency for my power management in tuxedo-control-center.
I wanted to take care of this later and put the laptop in suspend. On wake up the system froze (again…) and I was unable to capture the error message since it did not reappear.
I have seen 2 different possible fixes for this issue.
update the grub.cfg file with sudo grub2-mkconfig -o /boot/grub2/grub.cfg which sometimes works.
reinstall the kernel which fails to boot properly with dnf reinstall kernel*5.19.4* (or completely remove it with dnf remove kernel*5.19.4* --noautoremove followed by dnf upgrade to reinstall it)
Depending upon the system it seems that one of those may be the workaround to get the newer kernel to boot properly. If step 1 does not work then try step 2.
I seem to recall this has been an issue for several since the release of kernel 5.18.17 but does not seem to affect everyone. Maybe it is related to what else is getting upgraded at the same time.
I had the same issue but a slightly different solution. For me the issue was the presence of %{_dracutopts} in the grub config. I deleted it from /etc/kernel/cmdline, but it was still in the grub config after grub2-mkconfig. So I found it also in /etc/default/grub, and after removing it from there and running grub2-mkconfig again, it was finally removed from grub.cfg.