UPDATE 3: now it works on my headless raspi 4B
So I made the switch to 64bit. The aarch64 installation mentioned on
https://archlinuxarm.org/platforms/armv ... berry-pi-4 did not work in my headless scenario, so after digging around in the forums I made it work like this:
- - Preprared an aarch64 based SD card as in https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-4
- - Following https://archlinuxarm.org/forum/viewtopic.php?f=65&t=16212&start=30#p70257, I installed
- . arch-install-scripts (for arch-chroot)
- . qemu-user-static (for qemu-aarch64-static)
- . qemu-user-static-binfmt (bin format rules)
on my arch linux based laptop - - arch-chrooted into the sd card with / and /boot mounted to /mnt/sd and /mnt/sd/boot
- - updated the system with
$this->bbcode_second_pass_code('', '
pacman-key --init
pacman-key --populate archlinuxarm
pacman -Syuuv
') - - enabled some additional mirrors in /etc/pacman.d/mirrorlist
- - following https://archlinuxarm.org/forum/viewtopic.php?f=65&t=16243#p70273, I switched the kernel and got rid of the uboot booloader with $this->bbcode_second_pass_code('', 'pacman -S --needed linux-rpi raspberrypi-bootloader raspberrypi-firmware')
- - then I did some adaptions in /etc (setting hostname, edited locale.gen and alike)
- - synced and unmounted the sd card
- - after that I could properly boot my raspi and finish the setup there.
UPDATE 2: after a retry, the raspi crashed completely and was unreachable
UPDATE: after choking on a 15G file, the oom-killer went nuts again:(
I had the same problem with the 6.1.27 kernel, but the latest update to 6.1.28-3-rpi-ARCH does not (yet) have the same problem on my pi.
$this->bbcode_second_pass_code('', '
$ grep Model /proc/cpuinfo
Model : Raspberry Pi 4 Model B Rev 1.5
$ vcgencmd version
Apr 25 2023 18:26:03
Copyright (c) 2012 Broadcom
version d7f9c2b4ef7e4a8c0b04374a879ce89d7a948453 (clean) (release) (start)
$ rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Wed Jan 11 05:40:52 PM UTC 2023 (1673458852)
LATEST: Wed Jan 11 05:40:52 PM UTC 2023 (1673458852)
RELEASE: critical (/lib/firmware/raspberrypi/bootloader/critical)
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
$ cat /sys/kernel/mm/lru_gen/enabled
0x0000
')
I also did a rpi-eeprom-update.
For me it occured whenever I tried to rsync a file > 2GB to my raspi.