Please all, keep focused on the very problem we still have here, which is the one without nvidia.
@rairai9 You have no nvidia card. This is why
nvidia-drm.modeset=1 does not suit your kernel.
Concerning 6.2.X kernels, this was about potential issues that are already logged at 6.2.X but that did not cause the 6.2.X kernels to break (so that it feels for you like there is nothing). So, I was seeking a hint that indicates why 6.3.X broke on your system. It was unlikely that 6.2.X already logged something that later caused another kernel to break, but it was worth a try.
Booting a command list
EFI stub: UEFI Secure Boot is enabled.
Unfortunately, this is not indicative for us.
Since kernel 6.3.6 is already on its way, it is worth to hope for it to solve the issue. If you want to check it earlier, feel free to use bodhi to test it already now. For that, see: Fedora hangs on boot after upgrading to kernel 6.3.4 - #37 by py0xc3
If you do so, and if you want to give feedback in bodhi, please keep the “BZ#2211784” option neutral since your issue is a different one. But if 6.3.6 really solves your issue, you can add a comment to bodhi that 6.3.6 solves “BZ#2212012” (which is your bug report). Let’s hope…
If that does not work, I think we have to wait for the bug report to be processed. Unless someone else has time to play with your grub (which would end up in longer time investments). But I am not sure if that would make a difference. It any case, keep watching your bug report, and offer the information that people there ask for. Also, if 6.3.6 solves your issue, please let us know.
Also, you can keep watching F37 - 6.3.4-101.fc37 and 6.3.5-100.fc37 black screen after GRUB on AMD desktop, Nvidia laptop works and its related bug report (if that user adds one) → given that this user’s system is able to mount root, I assume this is a different bug. But since the hardware is completely different while using F37 (you F38), it is also possible that the same bug just behaves different on his system. So it is worth to keep checking if something comes up that solves their issue, and if so, let’s see if that helps you too. If that user finds a solution, feel free to trigger me here with @py0xc3 so that I can transfer his solution to your machine (do not just do what they do! It’s F37).