Boot fails/hangs and cannot read console messages

[fhuddles]

I've been running Arch Linux on my Raspberry Pi 3 Model B for several years. I recently did a software upgrage, using yay. There were quite a few items as I remember. Upon rebooting, the computer did not return to availability on the network, so I connected the HDMI to a screen. Upon rebooting, I saw the usual rainbow square, then a lot of text that scrolled rapidly by and just disappeared.
I've removed the MicroSD card, run fsck on both partitions, and looked at their contents. Everything looks normal as far as I can tell.
journalctl on the journal file does not provide timely enough information. I assume the really useful information, if any, would be in the kernel ring buffer, which isn't available.
So: can anyone suggest a way to find out what's happening?

[Rapty]

What kernel do you have ?
Do you have a way to revert ?

[fhuddles]

Thanks for your reply.
From the saved journal file, I see this warning:
Warning! Reported kernel version 5.10.92-2-rpi-legacy-ARCH is older than systemd's required baseline kernel version 5.14. Your mileage may vary.
I was aware that the Arch Linux version was considerably behind the ones on my other computers running Arch, but I just figured that's because this was ARM. This is the first time I've seen an actual warning about that.
I don't know of an easy way to revert. I could install from scratch if necessary.

[Rapty]

I haven't try this yet but you have to find a way to do an arch-chroot into your system.
Maybe install another ALARM on USB key and boot on USB ?

[graysky]

Are you running armv7h or aarch64? See: https:// archlinuxarm.org/forum/viewtopic.php?f=60&t=17406

[fhuddles]

Thanks for the responses. Looks like I am running arm7 and quite an old kernel. I was able to install a new Raspian instance on a usb stick and boot from that. I'm just doing to do an install of another system.
I did try adding the arm_freq=1400 to config.txt but that didn't work at all. Don't know if it was appropriate for my hardware.
I just didn't want to leave this thread hanging completely. I'm assuming that running an arm7 version finally became unusable.

[lmn]

> and removing arm_boost=1.

I had to remove the arm_boost parameter as well as setting the arm_freq to get the system to boot.