grub2 fails to insmod keystatus and loadenv when running with secureboot
Bug #1066399 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Release Notes for Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
| Quantal |
Invalid
|
High
|
Unassigned | ||
| grub2 (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
| Quantal |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
When booting my laptop (thinkpad x230) on current quantal, I'm getting error messages from grub complaining that keystatus and loadenv couldn't be loaded because secureboot prevented it.
This is then followed by a "Press any key to continue.." message which appears to timeout after 15-30s then booting the machine just fine.
It looks like we need those two modules added to our grub2 signed efi image which should then give me a perfect boot experience.
Revision history for this message
| Stéphane Graber (stgraber) wrote | #1 |
Revision history for this message
| Steve Langasek (vorlon) wrote | #2 |
| Changed in grub2 (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in grub2 (Ubuntu Quantal): | |
| milestone: | none → quantal-updates |
| Changed in ubuntu-release-notes: | |
| status: | New → Invalid |
| Changed in grub2 (Ubuntu Quantal): | |
| status: | Triaged → In Progress |
| assignee: | nobody → Colin Watson (cjwatson) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in grub2 (Ubuntu Quantal): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
The fix for this is straightforward; we just need to include those modules in the secureboot grub images. The question is whether we're comfortable doing so without first auditing them, since Fedora currently aren't including them in their image.