[Bug 1636838] Re: Failed to boot

This bug has already been marked as fixed & Ubuntu Stable Release Updates Team has already been unsubscribed as it is written here: https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1636838/comments/23 New bug report at https://bugs.launchpad.net/ubuntu/+source/linux-

[Bug 1636838] Re: Failed to boot

This bug has already been marked as fixed & Ubuntu Stable Release Updates Team has already been unsubscribed as it is written here: https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1636838/comments/23 New bug report at https://bugs.launchpad.net/ubuntu/+source/linux-

[Bug 1636838] Re: Failed to boot

Booting with -proposed isn't fixed on Raspberry Pi 3 I don't know if this was expected to be fixed on that device, but I at least wanted to save someone else from trying. Should I file a separate bug about it, or does the unsupported warning mean it's not reportable? -- You received this bug

[Bug 1636838] Re: Failed to boot

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636838

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package linux-firmware-raspi2 - 1.20161020-0ubuntu1~0.1 --- linux-firmware-raspi2 (1.20161020-0ubuntu1~0.1) xenial; urgency=medium * Update to release 1.20161020 * Check that config.txt sets the $device_tree_address, or forcefully set it to 0x0200

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package linux-firmware-raspi2 - 1.20161020-0ubuntu1~1.1 --- linux-firmware-raspi2 (1.20161020-0ubuntu1~1.1) yakkety; urgency=medium * Update to release 1.20161020 * Check that config.txt sets the $device_tree_address, or forcefully set it to 0x0200

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package u-boot - 2016.03+dfsg1-6ubuntu2~1.1 --- u-boot (2016.03+dfsg1-6ubuntu2~1.1) yakkety; urgency=medium * From upstream u-boot: (LP: #1636838) - debian/patches/rpi-import-mkknlimg.patch: import tools/mkknlimg from Xenial/raspi2 -

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package u-boot - 2016.01+dfsg1-2ubuntu2 --- u-boot (2016.01+dfsg1-2ubuntu2) xenial; urgency=medium * From upstream u-boot: (LP: #1636838) - debian/patches/rpi-import-mkknlimg.patch: import tools/mkknlimg from Xenial/raspi2 - scripts/mkknlimg @

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu64.1.1 --- flash-kernel (3.0~rc.4ubuntu64.1.1) yakkety; urgency=medium * Adjust rpi2/3 dtb address from 0x100 to 0x0200 (LP: #1636838) -- Paolo Pisati Wed, 09 Nov 2016 15:41:50 +0200

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu62.1.1 --- flash-kernel (3.0~rc.4ubuntu62.1.1) xenial; urgency=medium * Adjust rpi2 dtb address from 0x100 to 0x0200 (LP: #1636838) -- Paolo Pisati Fri, 28 Oct 2016 13:39:00 +0200 **

[Bug 1636838] Re: Failed to boot

And the upgrade from Xenial (vannila or dist-upgrade) to Yakkety is fine too - i think i covered all the possible upgrade paths combination, please release these packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1636838] Re: Failed to boot

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

[Bug 1636838] Re: Failed to boot

And here is the same for Yakkety: ubuntu@ubuntu:~$ dpkg -l | grep -e uboot -e flash-kernel -e firmware -e linux-raspi2 -e u-boot ii flash-kernel 3.0~rc.4ubuntu64 armhfutility to make certain embedded devices bootable ii

[Bug 1636838] Re: Failed to boot

And for uboot: ubuntu@ubuntu:~$ dpkg -l | grep u-boot 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

[Bug 1636838] Re: Failed to boot

Ok, here's a more verbose version of my testing procedure: -take the rpi2 image: http://cdimage.ubuntu.com/ubuntu/releases/16.04/release/ubuntu-16.04 -preinstalled-server-armhf+raspi2.img.xz -after a fresh install, these are the pkgs version: ubuntu@ubuntu:~$ dpkg -l | grep -e uboot -e

[Bug 1636838] Re: Failed to boot

No, there's no special process required: -take the rpi2 image: http://cdimage.ubuntu.com/ubuntu/releases/16.04/release/ubuntu-16.04 -preinstalled-server-armhf+raspi2.img.xz -enable proposed, and do a dist upgrade and you'll get all the above packages -reboot -does it come back? yes, fine ->

[Bug 1636838] Re: Failed to boot

I don't understand what verification has been done here, or if there is any special process required, so I'm skipping releasing it today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636838 Title:

[Bug 1636838] Re: Failed to boot

This is to get the three packages (flash-kernel, linux-raspi2-firmware and uboot) moving, while the kernel will land later. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1636838] Re: Failed to boot

Hello Yung, or anyone else affected, Accepted u-boot into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2016.03+dfsg1-6ubuntu2~1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1636838] Re: Failed to boot

Hello Yung, or anyone else affected, Accepted u-boot into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2016.01+dfsg1-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package u-boot - 2016.03+dfsg1-6ubuntu2 --- u-boot (2016.03+dfsg1-6ubuntu2) zesty; urgency=medium * From upstream u-boot: (LP: #1636838) - debian/patches/rpi-import-mkknlimg.patch: import tools/mkknlimg from Xenial/raspi2 - scripts/mkknlimg @

[Bug 1636838] Re: Failed to boot

This bug was fixed in the package linux-firmware-raspi2 - 1.20161020 --- linux-firmware-raspi2 (1.20161020) zesty; urgency=medium * Update to release 1.20161020 * Check that config.txt sets the $device_tree_address, or forcefully set it to 0x0200 (LP: #1636838) --

[Bug 1636838] Re: Failed to boot

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 0x0200 (LP: #1636838) -- Paolo Pisati Wed, 09 Nov 2016 15:41:50 +0200 **

[Bug 1636838] Re: Failed to boot

removed the verification-done-xenial tag, since I'm only tested it with ppa:p-pisati/misc. ** Tags removed: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636838 Title:

[Bug 1636838] Re: Failed to boot

In ppa:p-pisati/dtb-lp1636838 are the packages for all the releases affected: Xenial, Yakkety and Zesty. ** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) ** Also

[Bug 1636838] Re: Failed to boot

** Also affects: u-boot (Ubuntu) Importance: Undecided Status: New ** Changed in: u-boot (Ubuntu) Status: New => In Progress ** Changed in: u-boot (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) ** Also affects: u-boot (Ubuntu Xenial) Importance: Undecided

[Bug 1636838] Re: Failed to boot

** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636838 Title: Failed to boot To manage notifications about this bug go to:

[Bug 1636838] Re: Failed to boot

** Description changed: [Impact] - * Unable to boot into system after upgrade to 4.4.0-1030.37 +  * 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 +  * fresh install

[Bug 1636838] Re: Failed to boot

** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636838 Title: Failed to boot To manage notifications

[Bug 1636838] Re: Failed to boot

@p-pisati hey, i think you are correct, this is what I get: U-Boot 2016.01+dfsg1-2ubuntu1 (Feb 12 2016 - 05:55:38 +) DRAM: 944 MiB WARNING: Caches not enabled RPI 2 Model B (0xa21041) MMC: bcm2835_sdhci: 0 reading uboot.env In:serial Out: serial Err: serial Net: Net

[Bug 1636838] Re: Failed to boot

Can you connect a serial cable to the board? You need a TTL serial and it connects like this: http://workshop.raspberrypiaustralia.com/usb/ttl/connecting/2014/08/31/01 -connecting-to-raspberry-pi-via-usb/ then on you pc: screen /dev/ttyUSB0 115200 then plug the power in the board, and you