GNU GRUB - Bugs: bug #40836, Document GRUB's preference for the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #40836: Document GRUB's preference for the EFI framebuffer on BIOS systems
Submitter: | Eli <eliptus> | ||
Submitted: | Sat 07 Dec 2013 07:08:53 PM UTC | ||
Category: | Documentation | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | other |
Release: | Reproducibility: | None | |
Planned Release: | 2.03+ |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-03-02 | phcoder | Planned Release | None | 2.03+ |
Powered by Savane 3.13-4448.
Corresponding source code
For background, please refer to https://savannah.gnu.org/bugs/?40552.
I'm currently using grub-2.00_p5107-r2 on Gentoo. GRUB seems to have a preference to use the EFI framebuffer when GRUB_VIDEO_BACKEND is unset, even on BIOS systems, as confirmed by Vladimir on the aforementioned bug. This is nonintuitive, and users are unlikely to consider that they need to add EFI support to their kernel for their BIOS system. There are many forums on this topic that have concluded with disabling graphics support in GRUB, to allow the kernel to successfully use the appropriate framebuffer driver, such as vesafb.
This warrants proper documentation in the GRUB manual.
Summary from Bug 40552:
I'm currently using grub-2.00_p5107-r2 on Gentoo. Using GRUB's default configuration, but setting "GRUB_GFXPAYLOAD_LINUX=1024x768" in /etc/default/grub would result in a blank screen unless I enabled "efifb" in the kernel. This is unexpected since I'm running a BIOS system and the framebuffer is expected to use "vesafb".
As a test, I set "GRUB_VIDEO_BACKEND=true" in /etc/default/grub, disabling GRUB's loading of it's video modules. Doing so resulted in the kernel correctly matching the framebuffer to the "vesafb" driver. Further experimentation showed that setting "GRUB_VIDEO_BACKEND=vbe" also resulted in the correct behavior.
Using "all_video" or any other video module incorrectly resulted in matching of "efifb".