On Wed, Nov 29, 2023 at 11:01 AM olivares33561 via users < users@lists.fedoraproject.org> wrote:
On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan < pocallaghan@gmail.com> wrote:
On Wed, 2023-11-29 at 14:28 +0000, olivares33561 via users wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Not enough information to go on. What actually happens? Do you see anything onscreen? What happens if you remove the rhgb parameter from the boot line?
poc
I restart and boot with rhgb quiet removed I see [ OK ] ... . but at the end there is a line that says [ OK ] Reached target sysinit.target - System Initialization.
and it just stays there indefinitely. I will restart under previous kernel and remove this one. And retest when another comes by.
Have you looked at journalclt? 6.6.2-201.fc39.x86_64 works for many of us, so it could help to identify what is different about your system. The next step after "systemd[1]: Reached target sysinit.target - System Initialization." is attaching storage devices. Some storage devices have "quirks" that kernel usually works around. For example:
kernel: nvme nvme0: missing or invalid SUBNQN field.
I would take a close look at journalctl entries for a successful boot following the "sysiinit.target" line for informative messages. You can also check specific devices in the Linux Hardware Database -- some have comments that suggest kernel command-line options to enable dodgy hardware.