[Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

Timo Aaltonen tjaalton at ubuntu.com
Mon Jul 10 08:44:19 UTC 2017


Hello Zorro, or anyone else affected,

Accepted fwupdate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fwupdate/0.5-2ubuntu5 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

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-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: fwupdate (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  Fix Committed
Status in fwupdate-signed source package in Xenial:
  In Progress
Status in fwupdate source package in Yakkety:
  In Progress
Status in fwupdate-signed source package in Yakkety:
  In Progress
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call:

  https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems.  This is actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+subscriptions



More information about the Ubuntu-sponsors mailing list