[Bug 1456443] Re: Skip eMMC device's boot0, boot1 and rpmb partitions

Chris J Arges 1456443 at bugs.launchpad.net
Wed Oct 28 17:23:51 UTC 2015


Hello Tsung-Han, or anyone else affected,

Accepted ubiquity into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.18.8.11
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 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: ubiquity (Ubuntu Trusty)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1456443

Title:
  Skip eMMC device's boot0, boot1 and rpmb partitions

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  New
Status in partman-base package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in partman-base source package in Trusty:
  Fix Committed
Status in ubiquity source package in Trusty:
  Fix Committed
Status in partman-base source package in Vivid:
  Fix Committed
Status in partman-base package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations on specific eMMC devices, where they are shipping with mmcblk0rpmb and mmcblk0boot* partitions. For example, Nvidia Jetson TK-1 ARM boards.

  [Test case]
  Attempt a server installation on the device.

  [Regression potential]
  Minimal; these devices are meant to be read-only and should be treated as such by partman, so it makes sense to explicitly filter them out.

  ---
  During installation,
  partman will scan all the available partitions.
  However, with the eMMC device, especially with its /dev/mmcblk0rpmb partition,
  a popup warning will show up to interrupt the whole installation process.
  One has to manually press the 'Ignore' button to skip that and proceed the installation.
  This seriously impacts some of OEM's auto installation requirements.

  Ref:
  https://lists.debian.org/debian-boot/2014/12/msg00263.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1456443/+subscriptions



More information about the foundations-bugs mailing list