armhf: dtb movement from /lib/firmware/$(uname -r) to /boot/$(uname -r)

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1364035

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

I think most important is that nobody decided where to install them. For example *-chromebook is placing these files at /boot/dt-3.4.0-5-chromebook/ (!).

Seems it also affects other packages:

thopiekar@gate:~$ apt-file find dtb | grep "/boot/"
linux-image-3.4.0-5-chromebook: /boot/dt-3.4.0-5-chromebook/exynos5250-daisy.dtb
linux-image-3.4.0-5-chromebook: /boot/dt-3.4.0-5-chromebook/exynos5250-smdk5250.dtb
linux-image-3.4.0-5-chromebook: /boot/dt-3.4.0-5-chromebook/exynos5250-snow.dtb
thopiekar@gate:~$ apt-file find dtb | grep "/lib/firmware"
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/bcm2709-rpi-2-b.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/ads7846-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/bmp085_i2c-sensor-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/dht11-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/enc28j60-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/gpio-poweroff-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hifiberry-amp-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hifiberry-dac-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hifiberry-dacplus-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hifiberry-digi-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hy28a-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/hy28b-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/i2c-rtc-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/i2s-mmap-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/iqaudio-dac-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/iqaudio-dacplus-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/lirc-rpi-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/mcp2515-can0-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/mcp2515-can1-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/mmc-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/mz61581-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/piscreen-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/pitft28-resistive-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/pps-gpio-overlay.dtb
linux-image-4.2.0-1010-raspi2: /lib/firmware/4.2.0-1010-raspi2/device-tree/overlays/pwm-2ch...

Sorry, hammerhead just has no devicetree support..

AH! This is actually no bug!

The idea is to use flash-kernel to cat the kernel image and dtb into one zImage, which the default u-boot environment can find.
Saving all dtb files to /lib/firmware/ saves space on the (probably) limited boot-partition...

Instructions for the different hardware can be found at /etc/flash-kernel/db

not all boards require that zImage has the dtb appended. In such a case, uboot loads the device tree from the a file, preferable in the boot partition. Loading it from a different partition may require a special uboot hack.

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".