Open YaLTeR opened 3 years ago
A current workaround for this is:
if [ -d /sys/firmware/efi ]; then grub2-switch-to-blscfg grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg else block_device=$(lsblk -spnlo name $(grub2-probe --target=device /boot/grub2) | tail -n1) grub2-install $block_device touch /boot/grub2/.grub2-blscfg-supported grub2-mkconfig -o /boot/grub2/grub.cfg fi
This will only works if your bootloader is recent enough to have BLS support. Otherwise you'll get no boot entries.
Bootloader means grub right? Because I am on ooold Bios and it works perfectly. Grub should be up to date on Fedora or not?
The bootloader (GRUB) is not automatically updated in rpm-ostree based systems. This is the whole point of this issue (adding bootupd) to let folks do it.
@travier Thanks for the clarification! Sorry when I dont really know the technical details, is there a manual way to update the bootloader?
No manual way supported right now. There are workaround in the issue here and linked one. Everything is at your own risk.
Hello,
Inspired by https://github.com/fedora-silverblue/issue-tracker/issues/120#issuecomment-1177515110, I also did
sudo rpm-ostree usroverlay
wget https://kojipkgs.fedoraproject.org//packages/grub2/2.06/95.fc38/x86_64/grub2-efi-x64-2.06-95.fc38.x86_64.rpm
sudo rpm -i --reinstall grub2-efi-x64-2.06-95.fc38.x86_64.rpm
and I was able to re-enable secure boot.
Thanks @yann-soubeyrand , this did work for me now as well.
I've merged in Rawhide: https://pagure.io/workstation-ostree-config/pull-request/330
My test images (https://gitlab.com/fedora/ostree/ci-test) also include this already.
I've merged in Rawhide: https://pagure.io/workstation-ostree-config/pull-request/330
My test images (https://gitlab.com/fedora/ostree/ci-test) also include this already.
Will this be available in Fedora 39?
The solution in the above comment, didn't work for me. Will your merge request solve the problem?
@yann-soubeyrand
I executed the three lines that you mention in the above comment and when I now execute (after a reboot) rpm-ostree upgrade
, I get the following error: error: loading sysroot: opendirat: Permission denied
. Do I need the execute some other command after the three lines you mention (to close the overlay)?
Is this still in current Silverblue/Kinoite? I am not seeing it in either 39 or Rawhide, but if so what to look for?
This is still planned to be included in F39 but not there yet due to https://pagure.io/workstation-ostree-config/pull-request/330#comment-190406 (the PR has been reverted).
The test images (gitlab.com/fedora/ostree/ci-test) include this already. The Universal Blue images should as well.
Pushed back to Fedora 40. Might come as an update to F39 if we backport the support.
bootupd support in Anaconda got merged 🎉
I executed the three lines that you mention in the above comment and when I now execute (after a reboot)
rpm-ostree upgrade
, I get the following error:error: loading sysroot: opendirat: Permission denied
. Do I need the execute some other command after the three lines you mention (to close the overlay)?
@Verhoeckx Did you find any solution to this? I've just stumbled upon this error too.
@travier Is this a problem? While I got the same error, rpm-ostree status
did display new deployment as usual. If it is a problem, how to fix these permissions?
See https://github.com/fedora-silverblue/issue-tracker/issues/543#issuecomment-2048350047 for a lightly tested set of commands to update your EFI bootloader until we have full bootupd support in Fedora Atomic Desktops.
I'm confused :confused:, did bootupd
make it into 40, or was it deferred until 41? At least from the threads below it looks like it was pushed back to 41, but then was ready for 40, however I don't see bootupd
on my installation?
Under the assumption bootupd
is not included with 40, is it possible to still use it?
I researched that exact question about deferral earlier today. I found at least one comment (I think on Bugzilla) that confirmed deferral to F41. I also noticed that most F40 docs fail to reflect that.
I've updated everything to point to F41 as we did not land it in F40. We'll try to backport things to F40 as much as possible.
Hello @travier, any update about the backport to F40?
We can only consider backporting to F40 after it lands in F41. Status is tracked in https://gitlab.com/fedora/ostree/sig/-/issues/1
F33, ThinkPad T495s