I have looked a little deeper into the packages and have found the
script linux-firmware-raspi2.postinst inside linux-firmware-raspi2. The
script changes the device_tree_address in the config.txt from 0x02000000
to 0x02008000
0x02000000 is the value which is inside the config.txt on my raspi2.
This ensures that the raspi2 can successfully boot after the upgrade.
I think the following lines in the .postinst script could fix the
problem:
if grep -q "device_tree_address=0x100" /boot/firmware/config.txt; then
sed -i.bak
's/device_tree_address=0x100/device_tree_address=0x02008000/'
/boot/firmware/config.txt
fi
if grep -q "device_tree_end=0x8000" /boot/firmware/config.txt; then
sed -i.bak '/device_tree_end=0x8000/d' /boot/firmware/config.txt
fi
I did a quick shell test and the config.txt was changed as expected. Not
shure if it is the best way to handle it, but it should work ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
