How can I display the grub during boot?
up vote
2
down vote
favorite
So, I had a dual boot and just nuked the windows partitions, and then got rid of the boot files for windows and updated the grub, and now my PC boots directly into ubuntu. However, I'd like to still have the grub option so I can switch between kernels, and I want to make it permanent.
I've read about the matter and what I found was advice to comment the following line out of the grub file:
GRUB_HIDDEN_TIMEOUT=0
However, there is no such line in the file, which sole content is:
# 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_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
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"
What does this mean? Should I instead comment out the GRUB_TIMEOUT_STYLE=hidden
line, or what?
boot grub2 uefi
add a comment |
up vote
2
down vote
favorite
So, I had a dual boot and just nuked the windows partitions, and then got rid of the boot files for windows and updated the grub, and now my PC boots directly into ubuntu. However, I'd like to still have the grub option so I can switch between kernels, and I want to make it permanent.
I've read about the matter and what I found was advice to comment the following line out of the grub file:
GRUB_HIDDEN_TIMEOUT=0
However, there is no such line in the file, which sole content is:
# 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_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
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"
What does this mean? Should I instead comment out the GRUB_TIMEOUT_STYLE=hidden
line, or what?
boot grub2 uefi
2
It is a valid command. If it's not there for you to uncomment, you can simply put it in and runupdate-grub
.
– Jos
Oct 15 at 11:47
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
So, I had a dual boot and just nuked the windows partitions, and then got rid of the boot files for windows and updated the grub, and now my PC boots directly into ubuntu. However, I'd like to still have the grub option so I can switch between kernels, and I want to make it permanent.
I've read about the matter and what I found was advice to comment the following line out of the grub file:
GRUB_HIDDEN_TIMEOUT=0
However, there is no such line in the file, which sole content is:
# 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_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
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"
What does this mean? Should I instead comment out the GRUB_TIMEOUT_STYLE=hidden
line, or what?
boot grub2 uefi
So, I had a dual boot and just nuked the windows partitions, and then got rid of the boot files for windows and updated the grub, and now my PC boots directly into ubuntu. However, I'd like to still have the grub option so I can switch between kernels, and I want to make it permanent.
I've read about the matter and what I found was advice to comment the following line out of the grub file:
GRUB_HIDDEN_TIMEOUT=0
However, there is no such line in the file, which sole content is:
# 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_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
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"
What does this mean? Should I instead comment out the GRUB_TIMEOUT_STYLE=hidden
line, or what?
boot grub2 uefi
boot grub2 uefi
edited Oct 15 at 14:03
asked Oct 15 at 11:35
aaaaa
206
206
2
It is a valid command. If it's not there for you to uncomment, you can simply put it in and runupdate-grub
.
– Jos
Oct 15 at 11:47
add a comment |
2
It is a valid command. If it's not there for you to uncomment, you can simply put it in and runupdate-grub
.
– Jos
Oct 15 at 11:47
2
2
It is a valid command. If it's not there for you to uncomment, you can simply put it in and run
update-grub
.– Jos
Oct 15 at 11:47
It is a valid command. If it's not there for you to uncomment, you can simply put it in and run
update-grub
.– Jos
Oct 15 at 11:47
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Ypu can change the
GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu
and most importantly
sudo update-grub
sometimes if grub is not installed properly you may need
if boot is legacy
sudo grub-install /dev/sdx
or
sudo grub-install --force /dev/sdx
sdxx being the boot drive sda,sdb or sdc
If boot is EFI you need to specify where your EFI System partition is mounted:
sudo grub-install --efi-directory=<address of efi-directory>(eg. /mnt/efi>
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the messageError: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already didgrub-install /dev/sda
in another context, before making this post. Should I do it again?
– aaaaa
Oct 15 at 13:37
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressingESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.
– aaaaa
Oct 15 at 14:19
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Ypu can change the
GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu
and most importantly
sudo update-grub
sometimes if grub is not installed properly you may need
if boot is legacy
sudo grub-install /dev/sdx
or
sudo grub-install --force /dev/sdx
sdxx being the boot drive sda,sdb or sdc
If boot is EFI you need to specify where your EFI System partition is mounted:
sudo grub-install --efi-directory=<address of efi-directory>(eg. /mnt/efi>
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the messageError: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already didgrub-install /dev/sda
in another context, before making this post. Should I do it again?
– aaaaa
Oct 15 at 13:37
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressingESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.
– aaaaa
Oct 15 at 14:19
add a comment |
up vote
1
down vote
accepted
Ypu can change the
GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu
and most importantly
sudo update-grub
sometimes if grub is not installed properly you may need
if boot is legacy
sudo grub-install /dev/sdx
or
sudo grub-install --force /dev/sdx
sdxx being the boot drive sda,sdb or sdc
If boot is EFI you need to specify where your EFI System partition is mounted:
sudo grub-install --efi-directory=<address of efi-directory>(eg. /mnt/efi>
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the messageError: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already didgrub-install /dev/sda
in another context, before making this post. Should I do it again?
– aaaaa
Oct 15 at 13:37
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressingESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.
– aaaaa
Oct 15 at 14:19
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Ypu can change the
GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu
and most importantly
sudo update-grub
sometimes if grub is not installed properly you may need
if boot is legacy
sudo grub-install /dev/sdx
or
sudo grub-install --force /dev/sdx
sdxx being the boot drive sda,sdb or sdc
If boot is EFI you need to specify where your EFI System partition is mounted:
sudo grub-install --efi-directory=<address of efi-directory>(eg. /mnt/efi>
Ypu can change the
GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu
and most importantly
sudo update-grub
sometimes if grub is not installed properly you may need
if boot is legacy
sudo grub-install /dev/sdx
or
sudo grub-install --force /dev/sdx
sdxx being the boot drive sda,sdb or sdc
If boot is EFI you need to specify where your EFI System partition is mounted:
sudo grub-install --efi-directory=<address of efi-directory>(eg. /mnt/efi>
edited Nov 26 at 12:40
answered Oct 15 at 12:38
Hobbyist
1,178617
1,178617
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the messageError: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already didgrub-install /dev/sda
in another context, before making this post. Should I do it again?
– aaaaa
Oct 15 at 13:37
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressingESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.
– aaaaa
Oct 15 at 14:19
add a comment |
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the messageError: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already didgrub-install /dev/sda
in another context, before making this post. Should I do it again?
– aaaaa
Oct 15 at 13:37
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressingESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.
– aaaaa
Oct 15 at 14:19
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the message
Error: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already did grub-install /dev/sda
in another context, before making this post. Should I do it again?– aaaaa
Oct 15 at 13:37
I switched the style to countdown and updated the grub, and now when I booted not only did the grub still not appear, as it showed the message
Error: unknown command "hwmatch"
, followed by a 10 sec countdown. Should I reinstall, considering that it used to work before I removed the dual boot? I have UEFI, and I already did grub-install /dev/sda
in another context, before making this post. Should I do it again?– aaaaa
Oct 15 at 13:37
1
1
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Search on grub timeout gnu.org/software/grub/manual/grub/grub.html and ‘GRUB_TIMEOUT_STYLE’ If this option is unset or set to ‘menu’, then GRUB will display the menu and then wait for the timeout set by ‘GRUB_TIMEOUT’ to expire before booting the default entry. Pressing a key interrupts the timeout.
– oldfred
Oct 15 at 14:03
Ah, so the countdown mode allows me to access the menu by pressing
ESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.– aaaaa
Oct 15 at 14:19
Ah, so the countdown mode allows me to access the menu by pressing
ESC
during the countdown, and the menu one works straight out of the box! Tried both, and both work. Sticking with the second one. Thanks a lot for that useful link. I now consider my problem solved.– aaaaa
Oct 15 at 14:19
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083904%2fhow-can-i-display-the-grub-during-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
It is a valid command. If it's not there for you to uncomment, you can simply put it in and run
update-grub
.– Jos
Oct 15 at 11:47