[Bug 428519] Re: Unable to enable framebuffer modes with grub 2

[Oliver Joos]

This might help:
If the line 'GRUB_GFXPAYLOAD_LINUX=text' is in /etc/default/grub and I boot with the kernel parameter 'noplymouth' (instead of default 'quiet splash') then the first few messages after the kernel is loaded do appear on a screen with (estimated) VGA size! But only seconds later the resolution changes to the usual maximum of my laptop (1680x1050), and no wonder all the Ctrl+Alt+F1...6 consoles are again 1680x1050 too.
So no matter what GRUB_GFXPAYLOAD or GRUB_GFXPAYLOAD_LINUX is, the resolution of consoles stays at maximum (which in my case is hard to read and memory-consuming).

After some googling and tweaking I bet it is not the fault of grub or
the kernel. It is a component that starts a bit later in the boot
process, e.g. plymouth.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/428519

Title:
  Unable to enable framebuffer modes with grub 2

Status in “grub2” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: grub2

  With grub on jaunty, I used to be able to add the vga=791 parameter to
  the kernel boot command to enable a 1024x768x16 display resolution in
  the console.  Now, the vga parameter has been deprecated by the "set
  gfxpayload" command in grub 2, and this doesn't seem to work on my
  laptop.

  I've tried editing the boot command list from the grub 2 menu and
  inserting "set gfxpayload=1024x768x16, 1024x768" before the kernel
  boot command.  The system boots successfully, but switching to a
  console (CTRL+ALT+F1) just gives a blinking cursor in the top-left of
  on an otherwise black screen.

  I'm not an expert with grub 2/kernel parameters, so please let me know
  what information to attach to help fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/428519/+subscriptions