boot fails after upgrade

[Simon Kropf]

Same bug as in:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1636838

Raspberry Pi 3 Image from: https://wiki.ubuntu.com/ARM/RaspberryPi (06.04.2017)

with Raspi3 after both upgrade & dist-upgrade

this is the output of my again running system after temporary fix (below):

######
System: Ubuntu 16.04.2 LTS
######
######
:~$ dpkg -l | grep -e uboot -e flash-kernel -e firmware -e linux-raspi2 -e u-boot
ii flash-kernel 3.0~rc.4ubuntu64~rpi3.1 armhf utility to make certain embedded devices bootable
ii linux-firmware 1.157.8 all Firmware for Linux kernel drivers
ii linux-firmware-raspi2 1.20161020-0ubuntu1~0.2~rpi3 armhf RaspberryPi2 GPU firmware and bootloaders
ii linux-raspi2 4.4.0.1052.53 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-1052 4.4.0-1052.59 armhf Header files related to Linux kernel version 4.4.0
ii u-boot-rpi:armhf 2016.09+dfsg1-1~rpi3.1 armhf A boot loader for Raspberry PI systems
ii u-boot-tools 2016.09+dfsg1-1~rpi3.1 armhf companion tools for Das U-Boot bootloader
######

used temporary fix with dd:

#did a dd of whole disk before upgrading and extracted boot image from it afterwards
dd if=RASPI-RECOVERY.IMG of=boot.img skip=8192 count=262144

#replaced boot image with old one
dd if=boot.img of=/dev/mmcblk0p1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Carlin (crcarlin)]

If it helps, I figured out what files to copy from the working boot partition to the upgraded one to allow it to boot.

I was trying to debug the issue myself to figure out exactly which package might be breaking the installation, but ran out of time.

I had to copy the following files to make the RPi3 boot after a dist-upgrade:
bcm2710-rpi-3-b.dtb
boot.scr
initrd.img
vmlinuz

Is anyone actually working on RPi3 support? The tone of the wiki page makes it sound like a one man game, with Ryan Finnie doing some work but other than that we might be out of luck.

[Chris Carlin (crcarlin)]

Oh, is it the same bug as this? They found some workarounds over there, it sounds like.

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270

[Simon Kropf (simon-kropf)]

No, it's not a exactly a duplicate.

As you can see in the picture, it gets an error after reading boot.scr

If I look into the content of the boot.scr the fdt_addr_r is set.

So my guess is it should be fairly simple to fix once it's properly setting/reading the environment variable.

#####boot.scr
'V\86\9C\00PX\EA)\D2\00\00
\\00\00\00\00\00\00\00\00oH+\FD\00boot script\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00
T\00\00\00\00setenv fdt_addr_r 0x02008000
fdt addr ${fdt_addr_r}
fdt get value bootargs /chosen bootargs
setenv kernel_addr_r 0x01000000
setenv ramdisk_addr_r 0x02100000
fatload mmc 0:1 ${kernel_addr_r} vmlinuz
fatload mmc 0:1 ${ramdisk_addr_r} initrd.img
setenv initrdsize $filesize
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${initrdsize} ${fdt_addr_r}
#####

[Chris Carlin (crcarlin)]

Oh, right.

I know I was getting the hang after boot.scr at one point, so I'm not sure how I ended up going from there to having a working system using the fix in the other bug. Somehow I did, though.

And you ran into this just last week, installed then updated? It wasn't some installation from back in January where the packages might have had some update since?

[Simon Kropf (simon-kropf)]

Well, yeah that fix is working because it's just booting into an older kernel.

Yes, I downloaded the image on 06.04. und updated & (dist-)upgraded it on the same day.

So in Kernel 4.4.0-1052 I have the error as above in the pic.

If I get the time I will try tomorrow to see which is the latest working kernel until I get this error. (Maybe on the way there I will run into the same bug (1652270) you referenced, we'll see)

[Simon Kropf (simon-kropf)]

I just thought it could also be uboot. I'll try to look into it.

[Simon Kropf (simon-kropf)]

When only updating to 1052 Kernel (no upgrade) I get stuck at "Starting Kernel...".
No messages follow whatsoever. It's not uboot.

[Chris Carlin (crcarlin)]

BTW, I just checked my running system, and 'uname -a' reports 4.4.0-1052 using the workarounds in bug #1652270

I'm not sure if this is relevant to your bug (I don't have time to refresh my memory about the two bugs), but just in case, there you go.