Raspberry Pi bootloader 20171020-1 does not boot

[lucsansag]

Will it boot if I don't run mkinitcpio?

[sinatosk]

it did with me, yes, but I used a default "mkinitcpio.conf" so there were not additional kernel modules

edit1: when you run the "pacman -U --force linux-raspberrypi-4.9.56-1-armv7h.pkg.tar.xz raspberrypi-bootloader-20171015-1-any.pkg.tar.xz raspberrypi-bootloader-x-20171015-1-any.pkg.tar.xz" near the last steps... that will implicity do an mkinitcpio

[graysky]

$this->bbcode_second_pass_quote('sinatosk', '')$this->bbcode_second_pass_quote('graysky', '')$this->bbcode_second_pass_quote('sinatosk', '*')** DO THE FOLLOWING AS ROOT ***

I have a laptop with arch linux on it with an sdcard reader on it so I put my sdcard in that
..

[bulletmark]

I was using a Beaglebone Black remotely but recently changed it to an old RPi model 1 because a few recent kernel updates had broken the BB booting so I wanted more reliable kernel updates. Now my remote RPi has been killed also. I hope the Arch Arm devs can improve kernel update reliability a little more.

[thelaoshi]

Does linux-raspberrypi 4.9.57-2 fix this ?
I had the problem with *-1

[andre]

According to this thread viewtopic.php?f=60&t=12161&start=10 it does

[russelljt]

The graysky solution worked for me, which I would recommend if you do have access to another system running Arch, and an SD to USB reader.

$this->bbcode_second_pass_code('', '
mount /dev/sdb2 /mnt
mount /dev/sdb1 /mnt/boot
arch-chroot /mnt
')

Rather than downgrade to 4.9.56-1, I just ran pacman -Syu to upgrade to linux-raspberrypi 4.9.57-2, which allowed the device to boot.