Based on you efibootmgr listing, perhaps not. It looks like you are actually booting the uki kernel.
Try going into the BIOS settings and selecting the Fedora entry as the boot device?
(Or some BIOSes have a cut-down boot menu to avoid you going through the full settings.)
That looks exactly like my problem lol, but I never installed virtualbox or any hypervisor in my fedora system
Iâll try but i dont think it will work since what I think happens is the boot to the 0001 entry doesnt go well so it falls back to the next entry which is windows
Actually going into the boot menu with F11 shows that fedora now has become second in order behind windows and upon entering in it the menu actually shows! Sorry for doubting you XD, now we just gotta ensure that it is booted as first
Edit: I just saw in efibootmgr that Bootorder has been changed to 0003,0001 maybe I didnt see it when I deleted entry 0000, ill change the order and let you know
You also have GRUB_ENABLE_BLSCFG="false" in /etc/default/grub, which will cause another problem. In this case, the kernel configuration for grub is not automatically updated when installing a kernel update.
About that, I know it should be set to true, but the fact is when I put it to true i dont know if itâs normal behaviour or not but on:
sudo grep "^menuentry" /boot/grub2/grub.cfg (with blscfg TRUE)
menuentry âWindows Boot Manager (on /dev/nvme0n1p1)â --class windows --class os $menuentry_id_option âosprober-efi-2DE7-3B65â
(with blscfg FALSE)
menuentry âFedora Linux (6.17.6-100.fc41.x86_64+debug) 41 (Workstation Edition)â --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option âgnulinux-6.17.6-100.fc41.x86_64+debug-advanced-22db4ddc-7145-4ae3-8422-2709347c9f81â {
menuentry âFedora Linux (6.17.6-100.fc41.x86_64) 41 (Workstation Edition)â --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option âgnulinux-6.17.6-100.fc41.x86_64-advanced-22db4ddc-7145-4ae3-8422-2709347c9f81â {
menuentry âFedora Linux (6.17.4-100.fc41.x86_64) 41 (Workstation Edition)â --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option âgnulinux-6.17.4-100.fc41.x86_64-advanced-22db4ddc-7145-4ae3-8422-2709347c9f81â {
menuentry âFedora Linux (0-rescue-022440c38d0445ea8da041e033f4949b) 41 (Workstation Edition)â --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option âgnulinux-0-rescue-022440c38d0445ea8da041e033f4949b-advanced-22db4ddc-7145-4ae3-8422-2709347c9f81â {
menuentry âWindows Boot Manager (on /dev/nvme0n1p1)â --class windows --class os $menuentry_id_option âosprober-efi-2DE7-3B65â {
Yes, thatâs normal behaviour.
With GRUB_ENABLE_BLSCFG=âtrueâ, the kernels are discovered dynamically from the contents of /boot/loader/entries at boot time, not at mkconfig time. So mkconfig wonât (and doesnât need to) find and list the kernels.
You should see this in the config file:
insmod blscfg
blscfg
and a little way above it, a comment to explain:
# The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and
# populates the boot menu. Please refer to the Boot Loader Specification documentation
# for the files format: https://systemd.io/BOOT_LOADER_SPECIFICATION/.
Ok, I enabled blscfg and effectively the entries are there, BUT windows is still going as first I dont know why even after I changed boot order with:
$ sudo efibootmgr --bootorder 0001,0003
Now after rebooting with F11 and selecting fedora the order has changed again to 0003,0001 XD
EDIT: an idea popped in my mind, maybe I should remove Windows entry too as Windows is also started from boot menu?
Hmm, my BIOS sometimes likes to be âhelpfulâ by rearranging the boot order for me too.
You could. Before touching anything Windows related, I would make sure you have your Bitlocker recovery key handy. Sometimes booting Windows first from the boot menu, and on a different occasion from GRUB, can trigger it to ask for your recovery code.
hm, I dont think I have it, is it retrievable via Windows?
Edit: Ok I saw that it is easy retrievable via cmd or on the site, so what is your suggested next step? Deleting Windows entry from efibootmgr?
Itâs apparently visible in your MS account.
I dont know if you saw the edited response, so Iâll write you again ahahah, cause I want to be extra careful doing this stuff.
That should work and leave the BIOS with only one option.
To be clear though, what happened when you selected Fedora as the boot option in the BIOS menu? Did it start GRUB that time, but then default to Windows next time you booted?
No I think Iâve been unclear.
First sudo reboot after changing order it went directly to Windows, so I rebooted and pressed F11 and selecting fedora entry it sent me immediately to grub menu where I booted fedora and checked boot order once again, seeing that it had changed I changed it again and sudo rebooting it still sent me to Windows, so upon rebooting again I had to press F11 again to get into grub and fedora (and I saw from terminal that bootorder was changed once again)
Hence the situation right now is:
Booting and touching nothing â Windows
Booting with F11 boot menu and selecting fedora entry â Grub menu
1 Like
OK cool. So I agree, if you use efibootmgr to delete the Windows entries then you should boot straight into Grub every time (and you can use the Grub menu to select Windows when you need it).
That makes sense⌠government and 3rd party want to be able to easily recover your encrypted disk :-))
better have only have a local user account and store the recovery key somewhere safe.
sorry, offtopic
Thats what I thought lol when I saw that it was retrievable through the damn site XD, usual naughty Microsoft
Could it be possible that bitlocker is deactivated since I dont see the key in my account?
Possibly, though I think W11 applies it by default. I think in the Disk Management app in Windows it should show you whether each volume is BitLockered or not.