[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Console Resolution with GRUB2

From: D.J.J. Ring, Jr.
Subject: Re: Console Resolution with GRUB2
Date: Wed, 6 Mar 2013 15:00:16 -0500

Hello Jordan,

Thanks for your kind help.

Unfortunately I was in terrible pain due to illness and I'm blaming it for overlooking a dependency or step I needed to follow when installing grub-legacy.

It failed and I can no longer boot  my computer.  Since the program doesn't seem to have set up correctly SuperGrub and the other Grub fixing CDs won't work.  Also since I have no native driver for either eth0 or wifi on the computer, I cannot just reinstall the system.  I need to but the hard drive on another computer and install the kernel modules then pop it in my computer, but this takes time and another computer. I hope I can borrow my friend's computer where I write this.

I saved grub and grub-install --version from GRUB2 on my gmail account in case I had problems putting Grub Legacy back on this computer.

I should have tried Andrey Borzenkov's suggeston about vga= line now working.  Has it worked for the start, we would not have had such trouble.  The command line community has been hacking up keep gfxpayload and other parameters.   Hopefully the developers of GRUB will put in a line # To Keep GRUB console resolution in virtual consoles uncomment the next line by removing #.  Would solve the problem for us.

More later.

Thanks again to all.

David J. Ring, Jr., N1EA  Radio-Officers Group -- Join CW email list -- Historic Morse Recordings 
Gopher Hole:  gopher:// (native or with Firefox's Overbite extension) or via http to gopher gateway
Chat Skype: djringjr MSN: address@hidden AIM: N1EA icq: 27380609


On Sat, Mar 2, 2013 at 3:14 AM, Jordan Uggla <address@hidden> wrote:
On Fri, Mar 1, 2013 at 10:56 PM, D.J.J. Ring, Jr. <address@hidden> wrote:
> Chris,
> That doesn't explain why if I go back to grub-legacy everything works.  I

My guess is that you simply didn't have the same mode configured in
grub legacy as you do in grub2. If you don't think that's the case
then please give us some data to work with to determine what the
difference actually is.

Assuming that you're currently using grub2, and that you want a
console and grub menu resolution of 1024x768 please do the following,
in the order given:

1: Ensure that GRUB_GFXMODE in /etc/default/grub is set to "1024x768",
that GRUB_GFXPAYLOAD is either not set, set to "keep" or also set to

2: Run "grub-mkconfig -o /boot/grub/grub.cfg" to ensure that these
settings have been applied to the grub.cfg in use.

3: Save the full contents of both /etc/default/grub and
/boot/grub/grub.cfg so that you can include them in your reply email.

4: Save the output of "grub-install --version".

5: Reboot and confirm that your console resolution is not 1024x768.

6: Install grub legacy.

7: Configure grub legacy to hand off a mode of 1024x768.

8: Save the full contents of your /boot/grub/menu.lst .

9: Save the output of "grub-install --version" again.

10: Reboot and confirm that your console resolution *is* 1024x768.

Then reply with the two saved outputs of "grub-install --version" and
the full contents of /etc/default/grub, /boot/grub/grub.cfg, and
/boot/grub/menu.lst .

Please do not reply with any other unrelated discussion for now, I
would like to stick to one thing at a time to prevent this thread from
getting more chaotic.

Jordan Uggla (Jordan_U on

Grub-devel mailing list

Attachment: grub
Description: Binary data

Attachment: grub-install-version
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]