[Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3

[Florian Friedrich]

Same for me. Using Ubuntu 16.04.1 LTS on a RasPi3.
Adding the line

    fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb

to /usr/share/flash-kernel/bootscript/bootscr.rpi3 helped me, too. Thanks @mbirth!
Also, I have the same issue with the MAC address. I'm currently using macchanger to set it back to what it should be on every launch.

This is the content of my /boot/firmware/config.txt:

# For more options and information see 
	# http://www.raspberrypi.org/documentation/configuration/config-txt.md
	# Some settings may impact device functionality. See link above for details

        kernel=uboot.bin

	# enable uart (needed for u-boot on RPi3)
	enable_uart=1

	# set extended DT area
	device_tree_address=0x100
	device_tree_end=0x8000

	# enable i2c
	dtparam=i2c_arm=on
	dtparam=spi=on

	# uncomment if you get no picture on HDMI for a default "safe" mode
	#hdmi_safe=1

	# uncomment this if your display has a black border of unused pixels visible
	# and your display can output without overscan
	#disable_overscan=1

	# uncomment the following to adjust overscan. Use positive numbers if console
	# goes off screen, and negative if there is too much border
	#overscan_left=16
	#overscan_right=16
	#overscan_top=16
	#overscan_bottom=16

	# uncomment to force a console size. By default it will be display's size minus
	# overscan.
	#framebuffer_width=1280
	#framebuffer_height=720

	# uncomment if hdmi display is not detected and composite is being output
	#hdmi_force_hotplug=1

	# uncomment to force a specific HDMI mode (this will force VGA)
	#hdmi_group=1
	#hdmi_mode=1

	# uncomment to force a HDMI mode rather than DVI. This can make audio work in
	# DMT (computer monitor) modes
	#hdmi_drive=2

	# uncomment to increase signal to HDMI, if you have interference, blanking, or
	# no display
	#config_hdmi_boost=4

	# uncomment for composite PAL
	#sdtv_mode=2

	#uncomment to overclock the arm. 700 MHz is the default.
	#arm_freq=800


I guess the following part is the problem?

	# set extended DT area
	device_tree_address=0x100
	device_tree_end=0x8000

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

Title:
  Recent updates broke Ubuntu on Raspberry Pi 3

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've been running Raspberry Pi 3 with Ubuntu as described here https://wiki.ubuntu.com/ARM/RaspberryPi

  I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been
  using this setup successfully since October up until last week.
  Unfortunately one of the latest kernel updates broke the installation
  and I found out the same happened for Ubuntu 16.04 LTS - and therefore
  I can no longer run up-to-date Ubuntu installation (with updated
  kernel) on my RPI.

  I am getting this error:
  Error image is not a fdt - must reset the board to recover

  I also tried this but it didn't help me:
  https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=168838

  Now I know running Ubuntu on RPI3 this way is not officially
  supported, but since Ubuntu Snappy is supported I thought someone here
  could know what is going on.

  Thank you very much.

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