Factory Installation w/ secure boot needs a force flag
Bug #1105289 reported by
Mario Limonciello
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub-installer (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
At least in the Dell factory implementation, secure boot is not enabled in the firmware until the end of the software install process after validation that everything installed properly.
This means that the current method of looking for secure boot to be marked enabled in grub-installer won't work since it's not yet turned on when the Ubuntu install runs.
To solve this, I'd like to propose adding a new template to grub-installer that could be preseeded to force installing the secure boot binaries even if secure boot doesn't appear to be in the environment.
Related branches
tags: | added: patch |
no longer affects: | grub2 (Ubuntu) |
no longer affects: | grub2 (Ubuntu Precise) |
no longer affects: | grub2 (Ubuntu Raring) |
Changed in grub-installer (Ubuntu Precise): | |
status: | New → Won't Fix |
Changed in grub-installer (Ubuntu Raring): | |
status: | New → Won't Fix |
To post a comment you must log in.
Couldn't find the bzr branch for precise, so here's a debdiff for precise.