Raspberry Pi 2 firmware upgrade brick kernel 4.9.57-1

[ILMostro]

It's easy to assume that the issue might be specific to my own device. However, in case it isn't, just wanted to post on here for others to chime in.

After running pacman -Syyu, new linux firmware updates were installed for my raspi2. Performing a reboot left the device unable to boot! The kernel was updated to 4.9.5, IIRC.

Upstream kernel changelog:
https://cdn.kernel.org/pub/linux/kernel ... eLog-4.9.5

[graysky]

I can confirm the recent update renders a Raspberry Pi3 running armv7h unbootable. It just sits on the rainbow screen.


$this->bbcode_second_pass_code('', '
% grep 2017-10-21 /mnt/var/log/pacman.log | grep upgraded
[2017-10-21 06:15] [ALPM] upgraded ffmpeg (1:3.3.4-1 -> 1:3.4-1)
[2017-10-21 06:16] [ALPM] upgraded linux-raspberrypi (4.9.56-1 -> 4.9.57-1)
[2017-10-21 06:16] [ALPM] upgraded raspberrypi-bootloader (20171015-1 -> 20171020-1)
[2017-10-21 06:16] [ALPM] upgraded raspberrypi-bootloader-x (20171015-1 -> 20171020-1)
')

[ILMostro]

Oh, wow.

I'm trying to figure out what the changes were. So far, I can see only the bootloader changes dating back to 2017-10-20. The kernel/firmware changes date back to 2017-10-15, according to http://co.us.mirror.archlinuxarm.org/ar ... m/?C=M;O=D


$this->bbcode_second_pass_code('', 'Index of /armv7h/alarm
[ICO] Name Last modified Size Description
[DIR] Parent Directory -
[ ] alarm.files.tar.gz 20-Oct-2017 20:04 215K
[ ] alarm.files 20-Oct-2017 20:04 215K
[ ] alarm.db.tar.gz 20-Oct-2017 20:04 113K
[ ] alarm.db 20-Oct-2017 20:04 113K
[ ] alarm.files.tar.gz.old 20-Oct-2017 20:04 215K
[ ] alarm.db.tar.gz.old 20-Oct-2017 20:04 112K
[ ] raspberrypi-bootloader-x-20171020-1-any.pkg.tar.xz.sig 20-Oct-2017 20:04 566
[ ] raspberrypi-bootloader-x-20171020-1-any.pkg.tar.xz 20-Oct-2017 20:04 1.7M
[ ] raspberrypi-bootloader-20171020-1-any.pkg.tar.xz.sig 20-Oct-2017 20:04 566
[ ] raspberrypi-bootloader-20171020-1-any.pkg.tar.xz 20-Oct-2017 20:04 2.7M
[ ] raspberrypi-firmware-20171015-1-any.pkg.tar.xz.sig 15-Oct-2017 12:09 566
[ ] raspberrypi-firmware-20171015-1-any.pkg.tar.xz 15-Oct-2017 12:09 1.4M ')

[ILMostro]

Thanks for the additional info @graysky . I've updated the Title of the post to reflect the correct Kernel version.

[graysky]

How to recover without much fuss: viewtopic.php?f=15&t=12159&p=57001#p57001

[haraldwithtwoehs]

has anyone experimented yet to see which package has the problem - the bootloader or the linux kernel?

[graysky]

$this->bbcode_second_pass_quote('haraldwithtwoehs', 'h')as anyone experimented yet to see which package has the problem - the bootloader or the linux kernel?

[haraldwithtwoehs]

I pinned the bootloader packages (raspberrypi-bootloader and raspberrypi-bootloader-x), upgraded to kernel version 4.9.57-1, and the reboot bricked my RPi again.

Then I pinned the kernel (linux-raspberrypi) and upgraded the boot loader to 20171020-1, and the reboot was successful.

This surprised me - but at least now we know...

Working versions (for me):

$this->bbcode_second_pass_code('', '
local/linux-raspberrypi 4.9.56-1
local/raspberrypi-bootloader 20171020-1
local/raspberrypi-bootloader-x 20171020-1
')

[Evils]

Thanks for posting the info here, I've updated today and got burned immediately. Not that the same thing happened about 3 weeks back when a /dev entrypoint was missing after an update that rendered kodi unusable.

I'm thinking about no longer upgrading the linux-raspberrypi package due to these recent events. I'm happy to have had the cache still available, but I can't rely on that and rollbacks don't seem to happen when a major device is bricked by a faulty update.
Can anybody tell me what impacts I would have to fear when doing so?

[graysky]

$this->bbcode_second_pass_quote('haraldwithtwoehs', 'W')orking versions (for me):

$this->bbcode_second_pass_code('', '
local/linux-raspberrypi 4.9.56-1
local/raspberrypi-bootloader 20171020-1
local/raspberrypi-bootloader-x 20171020-1
')