UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Actually, I think it really is trying to display, but it seems that at the time when that's supposed to happen, my monitor gives me an 'Out of Range' error message and my computer boots into Ubuntu after a few seconds. Had this same problem with Fedora 17 some time ago, openSUSE's GRUB interface displays fine though.
In the simplest case, GRUB will hide the menu if GRUB_HIDDEN_TIMEOUT is set in /etc/default/grub. To show the menu you must comment out this line and update GRUB's boot configuration file.
From a terminal, open the file with gedit as root:
Code:
gksudo gedit /etc/default/grub
Comment out the line:
Code:
#GRUB_HIDDEN_TIMEOUT=5
You may also set the timeout before the default menu entry is booted automatically, by uncommenting this line and changing the timeout value:
Code:
GRUB_TIMEOUT=30
Save the changes and update GRUB's configuration file:
Code:
sudo update-grub
As far as the 'Out of Range' error goes. This may br caused by GRUB trying to set the video mode to one that's unsupported by you card/monitor. You can simply check this by changing this line to:
Code:
GRUB_GFXMODE=1024x768
This set's the video mode to 1024x768 which as far as I know is supported by all VESA cards and monitors.
Save the changes and update GRUB's configuration file as shown above.
Reboot. At this point you should see GRUB's boot menu.
To check the modes that GRUB support for your card, do this.
When the menu is shown press 'c' to go to GRUB's command-line. The GRUB prompt will be shown (grub> ).
Enter this command:
Code:
set pager=on
Check the modes supported with the vbeinfo command:
Code:
vbeinfo
Take a note of the displayed video modes. Note however, that your monitor may not support all of these modes. Select a mode supported by your monitor and set the GRUB_GFXMODE variable to this. Update GRUB's configuration file and your GRUB menu should be shown at the selected video mode.
Weird, the timeout AND graphics mode lines were commented and the timeout value somehow got set to zero. No matter, just uncommented the graphics mode line, left the graphics mode at it's original setting (640x480), uncommented the timeout line, set it to five, and that did the trick.
If GRUB_GFXMODE is commented out, Ubuntu set's it to auto when generating the configuration file. In auto, GRUB selects the first working mode. Depending on the video card, this mode may not work. I have an nVidia FX5200 card, and when set to auto, GRUB selected the 640x400 mode, which resulted in a blank display.
BTW: Auto is also a valid setting for GRUB_GFXMODE. See:
Weird, the timeout AND graphics mode lines were commented and the timeout value somehow got set to zero. No matter, just uncommented the graphics mode line, left the graphics mode at it's original setting (640x480), uncommented the timeout line, set it to five, and that did the trick.
Thank you KYJazzyJeff....I was having the problem where it would show "out of range" instead of displaying the GRUB menu.After fighting with this problem for over a week..i finally fixed it with your help....i would have never realised the solution was so simple.. Great job bro
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,625
Rep:
You should mark this thread Solved. You will find it under Thread Tools at the top of the page here. Only the OP can do that.
People that use the forum search tools for this problem will appreciate it, particularly since this is a common problem.
EDIT
You should be able to see the grub menu when you boot when set to hide by hitting the Shift key when the screen menu should be visible. This is supposed to bring it up in case you need to boot recovery mode or an older kernel.
Thanks for this easy to understand explanation of the `out of range ` problem.
This stopped me from using all Ubuntu releases after 8.04 because of the change from GRUB to GRUB 2. Finally, I see light where before there was darkness.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.