[Bug 1306841] Please test proposed package

[Brian Murray]

Hello Benjamin, or anyone else affected,

Accepted flash-kernel into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.0~rc.4ubuntu49.6 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!

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

Title:
  Wandboard i.MX6 Quad Board has different boot device

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Trusty:
  Fix Committed
Status in flash-kernel source package in Vivid:
  Fix Committed

Bug description:
  == Rationale ==
  The wandboards have two microsd slots, one directly tied to the SoC and one on the main board. The wandboard only boots from the one tied to the SoC.

  Unfortunately, the device numbering is wrong, in that when only the
  SoC slot is populated, it'll appear as mmcblk0, but when both slots
  are, the SoC slot becomes mmcblk1.

  So far flash-kernel has only supported the configuration with both
  slots populated, but it's reasonably common for people to only use the
  SoC slot and then use the SATA port to attach more storage.

  The fix is to use the constant path name from udev which always points
  to the right slot.

  == Testcase ==
   - Run flash-kernel before update => fails to find sdcard
   - Run flash-kernel after update => finds sdcard and install kernel
   - Reboot to check that things boot as expected

  == Regression potential ==
  Should a system somehow miss the /dev/disk/by-path symlink, flash-kernel may fail to install the new kernel. Note that testing on 5 different boards showed that this symlink is constant, regardless of storage configuration, so this shouldn't be an actual problem.

  == Original bug report ==
  The Wandboard i.MX6 Quad Board has two sdcard slots. The boot device is set to "/dev/mmcblk1p1", but this device only exists if both sdcard slots are used. I use just one sdcard and my boot device is called "/dev/mmcblk0p1".

  flash-kernel need to dynamically detect the correct sdcard slot or use
  a unique device name.

  I have following device symlink on my system:
  /dev/disk/by-id/mmc-SD16G_0xd62aac9a-part1
  /dev/disk/by-path/platform-2198000.usdhc-part1
  /dev/block/179:1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1306841/+subscriptions