GRUB menu appeared after I installed Win 11 my other drive. Now I formatted that drive since i don’t need Windows anymore but GRUB stayed even when Fedora 11 is my only system.
Also may be you want to try to create blank (new) grubenv then add again menu_auto_hide=1.
sudo grub2-editenv - create
sudo grub2-editenv - set menu_auto_hide=1
# Check it with:
sudo cat /boot/grub2/grubenv
# May be you also need to recreate `grub.cfg`
sudo grub2-editenv - create
sudo grub2-editenv - set menu_auto_hide=1
But GRUB menu still appear on boot. I even double checked my /boot/efi/EFI/ partition and there were no traces of Microsoft. GRUB menu does not show any other OS installed, just this Fedora install and 3 older kernels.
Edit: i think I accidentally solved my problem. I had to do like @bluishhumility suggested but I needed to type: sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg to get it work
Thank you all for your time and kindness for helping me!
Hi, btw the default location for grub.cfg should be in /boot/grub2/grub.cfg either for UEFI and non-UEFI. The /boot/efi/EFI/fedora/grub.cfg should not contain complete/real grub.cfg, but only a pointer to other location which /boot/grub2/grub.cfg. Bellow are default contain of /boot/efi/EFI/fedora/grub.cfg
It also explain why your grubenv doesn’t work since the file located in /boot/grub2/ and not in /boot/efi/EFI/fedora/.
You could continue to use /boot/efi/EFI/fedora/grub.cfg as grub2-mkconfig output destination. But if you want to reset it as default Fedora 35, you could use this Fedora wiki on part Instructions for UEFI-based systems.
Thanks for explaining I have no I idea how my config was so messed up. I did the reset you mentioned and now my system boots up straitght to Fedora even without: GRUB_TIMEOUT=0 line.
[quote=“oprizal, post:8, topic:77797”]
You could continue to use /boot/efi/EFI/fedora/grub.cfg as grub2-mkconfig output destination. [/quote]
I would not even offer that option since every later kernel update would update the grub.cfg at /boot/grub2/grub.cfg as well as the grub.env located there. However, booting would never see the updates unless the file /boot/efi/EFI/fedora/grub.cfg were restored to the default content.
Restoring the default content is as easy as deleting the file then running sudo dnf reinstall grub2-efi since that will, by design, include the proper UUID for booting in the new /boot/efi/EFI/fedora/grub.cfg file it will create.
Users of fedora 34 & 35 (and future versions) should be encouraged to use the correct path, which is also linked as /etc/grub2.cfg and /etc/grub2-efi.cfg.
actually, most likely no. Upgrading kernel only create new file inside /boot/loader/entries/ and grub.cfg will load file inside thus folder then showing it on boot loader list.