Note that if you have tested a recent grub2/grubby update, you will need to remove /etc/kernel/cmdline before testing this one.
Since there are many bugs/people involved and this has been previously requested, I'm testing a higher stable karma threshold for this update.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2022-a3480ad0d3Please login to add feedback.
This update has been submitted for testing by rharwood.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
Works
This update can be pushed to stable now if the maintainer wishes
This is still broken on 32 bit arm
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
rharwood edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by rharwood.
@ausil thanks - can you retest with -66 please?
works
works
-66 looks to be okay
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
I'm still able to reproduce, BZ#2118287 Thanks
Fixed the issue in the IoT compose
No issues noted on x86_64 desktop.
@rharwood any chance getting this stable soon? thanks for your work.
Something is still broken here. I just installed 6.0-RC1 build from Rawhide (https://koji.fedoraproject.org/koji/buildinfo?buildID=2048930) on F36 (for testing purposes), using dnf. The ro and subvol stuff was removed in /boot/loader/entries conf file for that particular kernel. The previous two kernels, which I installed from koji as well (5.18.19 for F36 and 5.19.3 for F37) did not exhibit this problem.
I relation to my previous command, grubby was run to add some options between installing F36/F37 kernels and Rawhide ones. Subsequent reinstallation of F37 kernel, for example, also ended up broken entries.
no regressions noted
no regressions noted
This update has been unpushed.
rharwood edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by rharwood.
@awee85 I appreciate your interest (and testing). People need to stop finding bugs in it first :)
More seriously, a higher karma threshold was requested by @kparal and while I still don't know how I feel about that in the general case, I do appreciate having issues like @bojan's caught before these fixes hit users. Right now, issues in these packages are only getting caught when I submit them to bodhi - there isn't this kind of testing for my rawhide builds - which also makes them take longer, unfortunately.
Works, thanks!
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Release -67 of grubby looks OK. Thanks!
Works fine!
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-a3480ad0d3does 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_loaderI 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!
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@flawedlogic I'm not sure what you're trying to do (or test) or which file you're referring to.
I tried 3 times --> 5.18.13-200.fc36.x86_64 will NOT load
Kernel will not load. Just hangs at load screen.
cleared cache each time
dnf clean all --enablerepo=\*this command:
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfgcreates:
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 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?
Okay, that's a kernel version, not grub2 version or a grubby version.
Not sure what this is for.
This destroys the stub configuration at that location. The correct command is
grub2-mkconfig -o /etc/grub2.cfg, but I don't know what you're doing that needs to run that, unless you're trying to test #2117817?At the top of this update, I stated: "Note that if you have tested a recent grub2/grubby update, you will need to remove /etc/kernel/cmdline before testing this one.". This is why.
If, after removing /etc/kernel/cmdline and applying this update, what you're trying to do works, then I believe everything is working as expected.
This update has been submitted for stable by rharwood.
It does not load.
I know the difference between a kernel and grub2. This kernel will not load. Period. Why not?
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?
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?
This update has been pushed to stable.