[Bug 1636838] Re: Failed to boot

[Taihsiang Ho]

proposed Xenial looks good. I could boot into the system with the
proposed stack.


The detailed of the system info:

=================================================================================================
Kernel: 4.4.0-1038-raspi2
Ubuntu 16.04.1 LTS
=================================================================================================
### dpkg -l | grep -e uboot -e flash-kernel -e firmware -e linux-raspi2 -e u-boot
ii  flash-kernel                         3.0~rc.4ubuntu62.1.1                       armhf        utility to make certain embedded devices bootable
ii  linux-firmware                       1.157.6                                    all          Firmware for Linux kernel drivers
ii  linux-firmware-raspi2                1.20161020-0ubuntu1~0.1                    armhf        RaspberryPi2 GPU firmware and bootloaders
ii  linux-raspi2                         4.4.0.1038.37                              armhf        Complete Linux kernel for the BCM2709 architecture.
ii  linux-raspi2-headers-4.4.0-1009      4.4.0-1009.10                              armhf        Header files related to Linux kernel version 4.4.0
ii  linux-raspi2-headers-4.4.0-1034      4.4.0-1034.41                              armhf        Header files related to Linux kernel version 4.4.0
ii  linux-raspi2-headers-4.4.0-1038      4.4.0-1038.45                              armhf        Header files related to Linux kernel version 4.4.0
ii  u-boot-rpi:armhf                     2016.01+dfsg1-2ubuntu2                     armhf        A boot loader for Raspberry PI systems
ii  u-boot-tools                         2016.01+dfsg1-2ubuntu2                     armhf        companion tools for Das U-Boot bootloader
=================================================================================================

=================================================================================================
Please refer to this URL to access full dpkg info.
http://paste.ubuntu.com/23637373/
=================================================================================================

-- 
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/1636838

Title:
  Failed to boot

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in u-boot package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Xenial:
  Fix Committed
Status in linux-firmware-raspi2 source package in Xenial:
  Fix Committed
Status in linux-raspi2 source package in Xenial:
  New
Status in u-boot source package in Xenial:
  Fix Committed
Status in flash-kernel source package in Yakkety:
  Fix Committed
Status in linux-firmware-raspi2 source package in Yakkety:
  Fix Committed
Status in u-boot source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * Unable to boot into system after upgrade to 4.4.0-1030.37

  [Test Case]

   * fresh install ubuntu-16.04.1-preinstalled-server-
  armhf+raspi2.img.xz

   * enable -proposed and 'apt full-upgrade'

  [Regression Potential]

   * red led still on, but few green led blinks then stay at the black
  screen(hdmi on)

  [Other Info]

   * restore the working boot partition backup image could recover the
  situation

  [Solution]

  * The latest X/raspi2 kernel in -proposed blows the space the
  bootloader reserves for the DTB, making the board unbootable (it only
  happens with classic rpi2 images created by the Foundation, Snappy is
  fine)

  * Ppa:p-pisati/misc has these 3 new packages that fix it:

   - linux-firmware-raspi2 - contains the latest Broadom fw release, and
     upon installation checks that /boot/firmware/config.txt contains the
     new DTB memory location, and if not, it does the necessary
     modification on behalf of the user
   
   - flash-kernel - modifies uboot.env to find the DTB in the new memory location
   
   - uboot -  update uboot to work with the new boot firmware (aka skip
     serial initialization if already done by the fw), contains the
     mkknlimg required when installing a new u-boot binary and correctly
     installs the uboot binary in the vfat partition

  [How to test it]

  * Install a fresh foundation image, add my misc ppa and the xenial
  -proposed repository, apt-get update && dist-upgrade, once the board
  completes the upgrade reboot it.

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