Grub2 Booting in blind mode due to "invalid video mode specification `text'"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Mathieu Trudel-Lapierre | ||
grub2-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
UEFI users booting VMs on Hyper-V
[Test case]
1) Install Ubuntu 16.04 in a Gen2 VM on Hyper-V (Windows)
2) After install; edit /etc/default/grub to add:
GRUB_GFXPAYLOAD
3) Run 'sudo update-grub'
4) Reboot
Verify whether the system writes an error/warning on console during boot (this shows up and disappears quickly, one must watch the console attentively):
error: invalid video mode specification `text'.
Booting in blind mode
[Regression potential]
There is minimal risk of regression; this is a patch that has been succesfully used in other releases to address the same issue (see bug 1711452). It only affects graphical payload selection in grub to avoid a value that is clearly invalid, thus skipping the error value and falling back to the default text-mode. Care should be taking while testing to identify any possible issues with displaying the grub menu or outputting information from the kernel at console as the system boots (if applicable).
---
In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD
error: invalid video mode specification `text'.
Booting in blind mode
This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/
The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix:
video: skip 'text' gfxpayload if not supported, to fallback to default (https:/
I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https:/
Here this launchpad bug is for Ubuntu 16.04 and 14.04.
tags: | added: id-5cc33192fdf0ba69633c3a45 |
Changed in grub2-signed (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in grub2-signed (Ubuntu): | |
status: | New → Fix Released |
You're mentioning 14.04 here; elsewhere it's only question of 16.04. Is this patch really needed on 14.04 as well?