[Impact]
We should ship fwupdate in 15.04 (hardware enablement tool; a firmware updater tool). It is used to apply firmware updates to BIOS or other components on systems for which their BIOS supports the EFI Capsule specification.
fwupdate-signed ships the signed fwupdate images, and should be updated alongside fwupdate.
[Test Case]
<requires a system with EFI Capsule support>
1) Run 'fwupdate -s' to check that EFI capsule is supported.
2) Run 'fwupdate -l' to list device UUIDs supporting EFI Capsule updates.
3) Acquire a firmware update binary from your hardware vendor.
4) sudo fwupdate -a `sudo fwupdate -l | sed -e 's/.*{\(.*\)}.*/\1/'` firmware.bin
5) sudo efibootmgr -v # should list the LinuxFirmwareUpdate entry, along with the same value in BootNext.
6) Reboot the system and watch the update being applied.
The fwupdate tool should succeed for every call. Following the last, one should see a new "LinuxFirmwareUpdater" entry reported by efibootmgr, and upon rebooting one should see the system applying the new firmware update, which may be recognizable as vendor-specific code (some vendors may show their own logo once the firmware update gets run).
[Regression Potential]
Limited to EFI installations. Failure to execute the firmware updater may result in shim loading the MokManager (EFI certificate management tool) instead, before allowing one to continue with normal boot. Otherwise, one may notice other issues in booting the system, in the form of a freeze when the firmware updater attempts to run. Rebooting should fix issues in all cases since the system should only boot *once* to the updater (what BootNext is supposed to do). Repeatedly booting in the firmware updater would constitute a regression.
Hello Mathieu, or anyone else affected,
Accepted fwupdate-signed into vivid-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/