Hi
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.
Thx.
At least this is true of Debian based systems.
My openSuse Tumbleweed /etc/default/grub:
# If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update
# /boot/grub2/grub.cfg.
# 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_DISTRIBUTOR=
GRUB_DEFAULT=saved
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=3
GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-id/ata-Samsung_SSD_850_PRO_256GB_S251NSAG530191H-part2 quiet mitigation>
GRUB_CMDLINE_LINUX=""
# Uncomment to automatically save last booted menu entry in GRUB2 environment
# variable `saved_entry'
# GRUB_SAVEDEFAULT="true"
#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 ...)
# GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
#Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL="gfxterm"
# 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'
GRUB_GFXMODE="auto"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
# GRUB_DISABLE_LINUX_UUID=true
#Uncomment to disable generation of recovery mode menu entries
# GRUB_DISABLE_RECOVERY="true"
#Uncomment to get a beep at grub start
# GRUB_INIT_TUNE="480 440 1"
GRUB_BACKGROUND=
GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
SUSE_BTRFS_SNAPSHOT_BOOTING="true"
GRUB_DISABLE_OS_PROBER="false"
GRUB_ENABLE_CRYPTODISK="n"
GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16"
Is this grub-customizer’s fault & will an in place upgrade overwrite /etc/default/grub?
I have never used “grub customizer”.
My openSuse Tumbleweed /etc/default/grub:
For comparison, here are the non-comment non-blank lines from my “/etc/default/grub”
GRUB_DEFAULT=saved
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=15
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/twleap/swap quiet"
GRUB_CMDLINE_LINUX=""
GRUB_TERMINAL="gfxterm"
GRUB_GFXMODE="auto"
GRUB_BACKGROUND=
GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
SUSE_BTRFS_SNAPSHOT_BOOTING="true"
GRUB_USE_LINUXEFI="true"
GRUB_DISABLE_OS_PROBER="false"
GRUB_ENABLE_CRYPTODISK="y"
GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16"
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,
If you were to boot to any other system, that would see corrupted disk file systems and possibly a loss of data. That it boots only to the hibernated system is the appropriate behavior.
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.
Cheerz, well explained. a feature not a bug. it used to work the other way before an update, but as stated this is correct behaviour.