I tried to update my grub config file to timeout to 0 value, so OS starts quickly. I modified /etc/default/grub
configuration file on my Ubuntu 18.04 and then ran:
sudo update-grub
and it didn't work. I also ran:
sudo grub-mkconfig
sudo update-grub
but they didn't work.
I searched a lot on the web to solve this issue, but all guides say to run the update-grub command to update grub by /etc/default/grub
config file.
I don't know if is Ubuntu 18.04 that handles grub files in a different way, but I cannot update my grub with my parameters.
This is my /etc/default/grub
file:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# 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=console
# 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=640x480
# 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"
In
/boot/grub/grub.cfg
file there is a condition, almost at the end of the file, that sets the timeout to 10 if the timeout is set to 0. In other words, if you set the timeout to 0 in your/etc/default/grub
and then update grub, the condition above reset it to 10 seconds.However,
/boot/grub/grub.cfg
is a read-only file and I cannot remove that condition. I made some tests with different values of the timeout in/etc/default/grub
. I tried with 1ms (0.001), 0.1s and 1s and I found out that values below 1 (like 0.1 and 0.001) work in the same way and almost like timeout set to 0.In my case, the problem was that my system didn't support "recordfail" which caused a separate block to get added to the grub.cfg which defaults to a timeout of 30 seconds. The relevant code in
/etc/grub.d/00_header
:The fix is simply to add a value for
GRUB_RECORDFAIL_TIMEOUT
in/etc/default/grub
and runupdate-grub
again. For example:Like the other answers say, uncomment
GRUB_HIDDEN_TIMEOUT
and runupdate-grub
. Then comment out thesection in
/boot/grub/grub.cfg
. In vim you can just override the read-only property with an exclamation point:x!
. Or you can runto temporarily have write permission while editing the file.
You can set
GRUB_TIMEOUT
to0
.The part overwriting timeout value is written in
ajust_timeout
function in the top of/etc/grub.d/30_os-prober
.So, you can set the value by editing the file and comment out if-block.
Uncomment
GRUB_HIDDEN_TIMEOUT=0
and runupdate-grub
again.You can set
GRUB_TIMEOUT
to-1
.This behaviour is experienced in both Ubuntu 18.04 and 20.04 and even though some of the other answers has solutions that work as expected, either files that has on the header an "do not edit this file" notice such as the
/boot/grub/grub.cfg
are manually edited, or the changes are not persistent after system updates or regenerating grub configuration files (at least weren't for me). Here's a step by step of what I've been doing to change such behaviour in a persistent fashion.Step 1 - Modify the template file
/etc/grub.d/30_os-prober
Grub uses some template files located at
/etc/grub.d
in order to generate the/boot/grub/grub.cfg
. Edit the file with your editor of choice...... and either comment or remove the lines below that override the timeout when it's set to zero.
Step 2 - Modify the file
/etc/default/grub
Grub uses this file to set configuration values in order to generate the
/boot/grub/grub.cfg
. Edit the file with your editor of choice...... and set the timeout for zero (use the second option if the
GRUB_TIMEOUT_STYLE
is set tohidden
)Step 3 - Generate the file
/boot/grub/grub.cfg
... and after the next machine reboot the expected behaviour is having a timeout of zero on grub menu.
We can simply add the line
to
/etc/grub.d/40_custom
, make the file executable withand run
to generate the new
/boot/grub/grub.cfg
-file. Theset timeout
-command we added is the lastset timeout
-command in/boot/grub/grub.cfg
now, that is what counts.The solution is to add
to
/etc/default/grub
.All other solutions will be reset on grub updates.