Differences between revisions 2 and 3
Revision 2 as of 2010-04-14 13:57:51
Size: 3634
Editor: 82-69-40-219
Comment: may not actually use efifb
Revision 3 as of 2010-05-10 15:36:22
Size: 3638
Editor: 217
Comment: Fix link to spec
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * '''Launchpad Entry''': UbuntuSpec:foundations-maverick-grub2-efifb  * '''Launchpad Entry''': UbuntuSpec:foundations-m-grub2-boot-framebuffer


GRUB2 supports programming a VBE mode in the boot loader and telling the kernel about it, causing the kernel to use efifb. With Linux 2.6.34, efifb can hand over smoothly to a KMS driver, allowing us to assemble all of this into something very close to a flicker-free boot splash process.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.


We want a smooth boot experience. In the process, we want to not break all the fiddly stuff - non-KMS, suspend/resume, etc.

User stories



You can have subsections that better describe specific parts of the issue.


This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.



  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

Notes from pre-BoF

  • Linux 2.6.34, plus or equivalent to do fbcon handoff

  • Change GRUB packaging to use efifb by default if we have a new enough kernel
  • Default video mode will be a VBE mode, unless Vladimir manages to import KMS drivers into GRUB as suggested
  • Plymouth needs to cope with framebuffer mode change (probably just a bug fix, Scott thinks Plymouth's design is already sufficient)
  • Quirk pm-utils to do VBE state/mode save/restore when using efifb (and vesafb)
  • Suitable GRUB background image, probably reusing Plymouth's logo file (scaling/centring issues?), and set appropriate foreground/background colours
  • Make sure GRUB shows background image even if not showing the menu
  • Build fbcon into the kernel on all architectures (already done on ports)


FoundationsTeam/Grub2BootFramebuffer (last edited 2010-12-15 15:12:08 by 82-69-40-219)