by Antiz » Sat Jul 16, 2022 10:20 am
Hi robg,
$this->bbcode_second_pass_quote('robg', ' ')I suggest you do the following:
After running `pacman -Syu` on your fresh install of ALARM, copy the latest uboot-raspberrypi package from a working device (found in /var/cache/pacman/pkg), and install it. Then, double-check (by comparing sha256sums) that all installed files (as listed by `pacman -Ql uboot-raspberrypi`) are the same on the two devices. Finally, reboot the device. This should either confirm or rule out uboot as the culprit.
Unfortunately, I couldn't find the uboot-raspberrypi package in pacman's cache on a working install.
I'm quite sure I cleaned the pacman's cache at some point for some reason on my working installs, and as the package hasn't been updated in about a year, I did not get any other version of this package in my pacman's cache since the day I cleaned it.
Anyway, I still compared the sha256sums of all the files involved in the uboot-raspberrypi package between the working and the fresh faulty install (with `for i in $(pacman -Ql uboot-raspberrypi | awk '{print $2}'); do sha256sum $i 2>/dev/null ; done`) and they're all the same.
I reinstalled the uboot-raspberrypi package by grabbing the .tar.xz file directly from the Arch Linux ARM repo on the faulty install just to make sure the sha256sums we're still the same after that, and they were. I know it doesn't make much sense to reinstall it as the sha256sums we're already good before but... I rebooted the raspberrypi after that and, strangely,
it worked this time ! It didn't fall to the U-Boot screen like it did the numerous times before.
The only thing I did differently compared to the last times is that I reinstalled the uboot-raspberrypi package after updating the system and rebooting.
I'm gonna try to reproduce this today by rebooting with and without reinstalling the uboot-raspberrypi package before. I'll edit this post with the results as soon as I can.
$this->bbcode_second_pass_quote('', 'A')lso, could you kindly check if, on any of your working instances of ALARM, there are .pacsave or .pacnew files in the /boot directory?
I'm confused... I tried to reproduced the behavior I described earlier in this post but, for an unknown reason, everything is working well now.
) with no extra steps or modifications whatsoever + updating the system (`pacman -Syy && pacman -Syu`).
I thought that I needed to reinstall uboot-raspberrypi after performing an update for some reason (according to what I wrote earlier in this post), but I didn't even had to do it this time. I could reboot after an update without any issue.
I've check the uboot-raspberrypi package and it didn't had an update recently (nor the latest aarch64 archive).
My guess it that there was something causing this issue inside one of the packages marked for update after a fresh install that has been patched since my previous test ? Otherwise, I have no clue why it didn't work then and why it works now...
I wish I could figure this out and help more but this issue seems it has resolved itself somehow.
Anyway, it seems to be working now at least 
