Update bricks aarch64 on Pi 4

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

Update bricks aarch64 on Pi 4

Postby frednet » Wed Sep 16, 2020 12:07 am

I'm following this tutorialhttps://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-4 to install Arch AArch64 on a Raspberry Pi 4 but the first time I update it bricks the system. The problem I get is the system installs and boots up but when I run a system update the next time I reboot I get the system freeze with the four colour bootscreen in a frozen state.
I'm wondering if the problem is due to a message that asks if you want to $this->bbcode_second_pass_quote('', 'r')eplace libutil-linux with core/util-linux-libs

Is anyone else experiencing this issue? I've tried replacing the contents of 'boot' from the original tar.gz file and I can then reboot successfully but it screws up the kernel drivers as the keyboard stops working so I can't log in to fix it properly.
frednet
 
Posts: 4
Joined: Tue Sep 15, 2020 11:54 pm

Re: Update bricks aarch64 on Pi 4

Postby dhaines » Wed Sep 16, 2020 4:25 am

I had the same on a 3B+ and am still in recovery from it.
dhaines
 
Posts: 3
Joined: Sun Jun 28, 2020 2:34 pm

Re: Update bricks aarch64 on Pi 4

Postby tristess » Wed Sep 16, 2020 7:36 am

Hello,

I am not sure that this is exactly the same issue I faced, but the latest update of raspberrypi-bootloader which is raspberrypi-bootloader 20200915-1 also "bricked" my Pi. When I rebooted, it remained on the rainbow screen.

I solved the issue by manually reverting to version raspberrypi-bootloader-20200911-1-any.pkg.tar.xz which I found on this "unofficial" rollback machine here : http://tardis.tiny-vps.com/aarm/package ... pkg.tar.xz

I just unzipped it and overwrote the content in the boot partition.

So it looks that this latest update is bricking some Pi's (mine is a Rpi 4B 4G)

Hope it helps.
tristess
 
Posts: 6
Joined: Wed Sep 16, 2020 7:30 am

Re: Update bricks aarch64 on Pi 4

Postby acorbi » Wed Sep 16, 2020 8:59 am

I can also confirm that the latest update for the raspberrypi-bootloader (15th september) makes the pi4 unbootable.
acorbi
 
Posts: 26
Joined: Wed Aug 05, 2020 10:31 am

Re: Update bricks aarch64 on Pi 4

Postby graysky » Wed Sep 16, 2020 2:11 pm

Please try raspberrypi-bootloader-20200916-1 when it hits the mirrors. It contains a fix by upstream, see: https://github.com/raspberrypi/firmware/issues/1467
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Update bricks aarch64 on Pi 4

Postby 2c982m9 » Wed Sep 16, 2020 4:50 pm

raspberrypi-bootloader-20200916-1 does not fix this for me on rpi3b+; I had to go back to 20200901-1 for now.
2c982m9
 
Posts: 12
Joined: Mon Dec 17, 2018 5:57 pm

Re: Update bricks aarch64 on Pi 4

Postby frednet » Wed Sep 16, 2020 5:48 pm

Thanks for the help, your fix worked perfectly!
frednet
 
Posts: 4
Joined: Tue Sep 15, 2020 11:54 pm

Re: Update bricks aarch64 on Pi 4

Postby dhaines » Wed Sep 16, 2020 6:07 pm

3b+ remains just as broken for me as well.
dhaines
 
Posts: 3
Joined: Sun Jun 28, 2020 2:34 pm

Re: Update bricks aarch64 on Pi 4

Postby graysky » Wed Sep 16, 2020 7:49 pm

$this->bbcode_second_pass_quote('ncguk', 'A') clean install on a Pi 4 with 1GB of RAM updated via pacman to bootloader 20200916-1 does not boot for me. Stuck at the rainbow square boot screen.


I can confirm the same behavior for aarch64 but not for arm7h on RPi4. https://github.com/raspberrypi/firmware ... -693638255

See the upstream issue: https://github.com/raspberrypi/firmware ... -693699215
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Update bricks aarch64 on Pi 4

Postby graysky » Thu Sep 17, 2020 1:29 pm

$this->bbcode_second_pass_quote('ncguk', 'P')elwell on the raspberrypi/firmware github has posted a workaround for non-booting aarch64 installs - add $this->bbcode_second_pass_code('', 'kernel_address=0x80000') to config.txt. A proper fix has been made and, presumably, this will appear for Arch users shortly.


If you can wait until the build system gets it, and it gets out to the mirrors, you can update to alarm/raspberrypi-bootloader to 20200917-1 which will fix it without any modifications.
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000
Top


Return to ARMv8

Who is online

Users browsing this forum: Google [Bot] and 0 guests