group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1636838@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu65

---------------
flash-kernel (3.0~rc.4ubuntu65) zesty; urgency=medium

  * Adjust rpi2/3 dtb address from 0x100 to 0x02000000 (LP: #1636838)

 -- Paolo Pisati <paolo.pisati@xxxxxxxxxxxxx>  Wed, 09 Nov 2016 15:41:50
+0200

** Changed in: flash-kernel (Ubuntu)
       Status: In Progress => Fix Released

** Changed in: linux-firmware-raspi2 (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  In Progress
Status in flash-kernel source package in Xenial:
  New
Status in linux-firmware-raspi2 source package in Xenial:
  New
Status in linux-raspi2 source package in Xenial:
  New
Status in u-boot source package in Xenial:
  New

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