I'm running the 3.5.0-22 kernel and am still getting the error. The
system boots, but hangs for several seconds after the error.
I am not getting the error on my 64 bit partition, also running
3.5.0-22.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Martin-Eric
Were you able to take a look at the documentation Colin suggested in
Comment #7? It doesn't sound like the /etc/default/grub file will be
extended with commented-out documentation. Marking as wont-fix.
** Changed in: linux (Ubuntu)
Status: Confirmed = Won't Fix
--
You
This issue was not about putting extra comments into /etc/default/grub
as much as about properly documenting the differences between adding
vga=xxx in cmdline, versus exporting the GFX_MODE, and that is still not
properly documented. For instance, I haven't found any place which
states that the
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864803
Title:
GRUB_GFXMODE not passed to the kernel
To manage notifications about
** Description changed:
In the process of trying to figure out where to set GFXPAYLOAD when
- GRUB2 complained that vga=mode no longer is the proper way to pass the
+ GRUB2 complained that vga=795 no longer is the proper way to pass the
framebuffer resolution to the Linux kernel, it appears
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864803
Title:
GRUB_GFXMODE not passed to the kernel
To manage notifications about this
I think you were either misinformed or misunderstood. GRUB_GFXMODE is
not sufficient to cause GRUB to pass a video mode to the Linux kernel;
you must also set GRUB_GFXPAYLOAD_LINUX=keep or
GRUB_GFXPAYLOAD_LINUX=some other video mode. See GRUB's info
documentation.
--
You received this bug
There doesn't seem to be any GRUB_GFXPAYLOAD_LINUX defined or commented
out in /etc/default/grub. If people are expected to stop putting
vga=mode in GRUB_CMDLINE_LINUX, then the correct upgrade past must be
properly documented.
--
You received this bug notification because you are a member of
Adding GRUB_GFXPAYLOAD_LINUX=keep to /etc/default/grub still doesn't
offer a proper substitute for putting vga=mode in GRUB_CMDLINE_LINUX.
Again, it's pointless to make GRUB complain that vga=mode is deprecated
if the procedure for setting gfxpayload is not gonna be documented.
--
You received
Adding GRUB_GFXPAYLOAD_LINUX=keep to /etc/default/grub and running
update-grub only seems to make the framebuffer load up much later in the
boot cycle, just before GDM appears. By comparison, vga=mode makes the
kernel switch mode much earlier during the bootup process. Also, while
vga=mode is
Getting the Plymouth graphic logo to start showing early as previously
with vga=mode required this additional step:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
...followed by update-grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It is properly documented in:
http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration
That's also installed in 'info grub', and if you would care to do some
basic searching, it also discusses issues with vga=.
I do not care to continue extending /etc/default/grub with
13 matches
Mail list logo
