search

fedora-silverblue / issue-tracker

Fedora Silverblue issue tracker
https://fedoraproject.org/atomic-desktops/silverblue/
125 stars 3 forks source link

Use bootupd and remove ostree-grub2 (was: All deployments are shown twice in grub) #120

Open YaLTeR opened 3 years ago

YaLTeR commented 3 years ago

boot-entry-issue

F33, ThinkPad T495s

secretmango commented 1 year 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?

travier commented 1 year ago

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.

secretmango commented 1 year ago

@travier Thanks for the clarification! Sorry when I dont really know the technical details, is there a manual way to update the bootloader?

travier commented 1 year ago

No manual way supported right now. There are workaround in the issue here and linked one. Everything is at your own risk.

yann-soubeyrand commented 1 year ago

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.

jmaibaum commented 1 year ago

Thanks @yann-soubeyrand , this did work for me now as well.

travier commented 1 year ago

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.

Verhoeckx commented 1 year ago

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?

Verhoeckx commented 1 year ago

@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)?

juhp commented 1 year ago

Is this still in current Silverblue/Kinoite? I am not seeing it in either 39 or Rawhide, but if so what to look for?

travier commented 1 year ago

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.

travier commented 12 months ago

Pushed back to Fedora 40. Might come as an update to F39 if we backport the support.

travier commented 9 months ago

bootupd support in Anaconda got merged 🎉

0rzech commented 8 months ago

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?

travier commented 4 months ago

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.

scottwillmoore commented 4 months ago

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?

davidstrauss commented 4 months ago

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.

travier commented 4 months ago

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.

Malix-Labs commented 1 month ago

Hello @travier, any update about the backport to F40?

travier commented 1 month ago

We can only consider backporting to F40 after it lands in F41. Status is tracked in https://gitlab.com/fedora/ostree/sig/-/issues/1