Comments

5 Comments

Sync /etc/default/grub on modification to preserve GRUB_CMDLINE_LINUX workflow Mark grubby as obsoleting grubby-deprecated Be less clever about generating cmdline file from grubby

How do you do these things?

sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a3480ad0d3

That command does nothing but waste my time. It does not help anything load. Could you give me further direction

rather than just pass it off because you understand it and are not willing to help someone else?

BZ#2113883 grub2-mkconfig -o /boot/grub2.cfg doesn't update pre-installed kernel cmdline after changing GRUB_CMDLINE_LINUX
BZ#2117817 removal of grubby-deprecated is incorrectly handled
BZ#2118172 GRUB2 isn't updating the list in Fedora 36 Silverblue
BZ#2118287 Updating kernel arguments with grubby --update-kernel=ALL results in kernel not booting after kernel upgrade
BZ#2118292 when installing a custom kernel rhgb quiet are added to kernel argument

It does not load.

I know the difference between a kernel and grub2. This kernel will not load. Period. Why not?

I tried 3 times --> 5.18.13-200.fc36.x86_64 will NOT load

Kernel will not load. Just hangs at load screen.

  • Hard drive does not even click on.

cleared cache each time

dnf clean all --enablerepo=\*

this command:

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

creates:

  • check /etc/kernel/cmdline verify ro rootflags=subvol=root is missing <-- This file

  • Previous notes:

Additional info: running grub2-mkconfig /boot/grub2/grub.cfg appears to correct boot entries. If /etc/kernel/cmdline is removed, it appears to regenerate it with double entries for rhgb quiet: ro rootflags=subvol=root rhgb quiet preempt=full rhgb quiet

then lastly

  • This only occurs if /etc/kernel/cmdline exists, sorry for not catching that earlier. On a fresh F36 install.
  • sudo grub2-mkconfig -o /boot/grub2/grub.cfg
  • This creates /etc/kernel/cmdline, it is correct at this point. cat /etc/kernel/cmdline root=UUID=e1b2eceb-4054-4380-8da4-a9a8993a8db5 ro rootflags=subvol=root rhgb quiet

  • sudo grubby --args="preempt=full" --update-kernel=ALL cat /etc/kernel/cmdline root=UUID=e1b2eceb-4054-4380-8da4-a9a8993a8db5 rhgb quiet preempt=full

I can load

5.17.5.300.fc36.x86_64

Its not the display manager!

When I try and boot 5.18.13-200.fc36.x86_64 ( OR NEWER) Nothing happens. Like No one is home

Thank you! I hope this gives some more clarity?

I am still having trouble navigating my way through this site (newbie to linux sorry) I have seen bits and pieces of how people seem to fix the problem.

running: sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a3480ad0d3

does NOT seem to be the fix that much I have gathered.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-working_with_the_grub_2_boot_loader

I have tried to create that file but I am not sure if that is what I should even be doing?

grubby-bls update how? It seems that people seem to find a file after running

I am just looking for some direction and understanding!

Thank you!