Anyone post their standard GRUB file to use as template? I used Grub Customizer a while back & did not realize this is a no no. I learned this on a Mint forum. I totally customizes GRUB without consent & can introduce weird bugs. Right now I hibernate & GRUB does not give me the option of elementary or openSUSE, but errors out & boots straight to Tumbleweed. I did not backup my GRUB.cfg & have traditionally used GRUB Customizer to edit OS entries. I will do it manually from now on.
# If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update
# Uncomment to set your own custom distributor. If you leave it unset or empty, the default
# policy is to determine the value from /etc/os-release
GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-id/ata-Samsung_SSD_850_PRO_256GB_S251NSAG530191H-part2 quiet mitigation>
# Uncomment to automatically save last booted menu entry in GRUB2 environment
# variable `saved_entry'
#Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#Uncomment to disable graphical terminal (grub-pc only)
# The resolution used on graphical terminal
#note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#Uncomment to disable generation of recovery mode menu entries
#Uncomment to get a beep at grub start
# GRUB_INIT_TUNE="480 440 1"
As far as I know, Yast bootloader changes that file.
The USE_LINUXEFI is because this is a UEFI system with secure-boot enabled. I’m not sure whether the “ENABLE_CRYPTODISK” is default, or is because I use an encrypted LVM. My system doesn’t actually need that, because I have a separate unencrypted “/boot”
I am not seeing any obvious problems in the file content that you posted. If there is something that is going wrong, you might do better to just describe that.
Thx for looking.
openSUSE will hijack GRUB when hibernated. When openSUSE is hibernated it will automatically boot back into Tumbleweed only without showing GRUB options to choose OS.
If I do not hibernate but power cycle with a shutdown or restart, then GRUB will show itself & I can select OS.
Of course not. That is where hibernating is for. Just freeze the system as it is. It is NOT neatly shutdown. And "unfreezing’ it when starting again.
When starting a hibernated system would allow you to choose to boot another system, that would be about the same as a kernel break or a power loss situation. Not what most people want, specialy not when they only hibernate,
What is the nature of the customizing you wish to do? You can build a config file from scratch if you please, name it custom.cfg, put it in /boot/grub2/, and it will automatically be called as subroutine through grub.cfg in the Grub menu displayed. Configured via 40/41_custom, custom.cfg entries will be appended. Called by 0[1-9]_custom, they will be prepended.
Well explained, so a feature not a bug. It used to work how I described, but thinking about it I did have some disk corruption issues in the past with other flavours of Linux. Props to SUSE for doing it properly.