MichaIng

Many thanks for your report. The RAM size is obtained by the bootloader. How old is your system/image, and in case did you flash the new bootloader build? ```sh /boot/dietpi/func/dietpi-set_hardware...

Do you have a USB-UART adapter, to check bootloader output via serial console? So far have not heard about issues with RAM size detection. There was a problem with 1.5...

Thanks, well outlined the difference. Weird that it detects 16 b/raw sometimes, and 15 b/raw the other times, as this should be a static hardware value 🤔.

In general DRAM init code for this SoC is here: https://github.com/u-boot/u-boot/blob/master/arch/arm/mach-sunxi/dram_sun50i_h616.c ... ahh and now I find these messages in an Armbian patch: https://github.com/armbian/build/blob/main/patch/u-boot/u-boot-sunxi/opizero3-1.5GB-trim-from-u-boot-v2024.01.patch The upper part is needed to...

I mailed the author of the U-Boot patch, in the hope he might have some idea how this can go randomly wrong.

@jozefSCK Not great (that such is needed), but a workaround indeed. May you provide the content of your `ram_check.sh` as well? For the systemd unit: It runs very late after...

I pushed new kernel and U-Boot packages to our APT repository. Could you test whether this fixes things, the U-Boot upgrade in particular? ```sh sudo apt update sudo apt upgrade...

Does this other distro not suffer from the by times false RAM size detection? In case its bootloader is generally based on mainline U-Boot, we might derive the needed patch...

Okay, thanks for testing. Probably I also just need to restart my 2 GiB model more often to see it having 4 GiB assinged once. If so, I can add...

@jozefSCK Hmm, if it was fixed in Armbian, it would be fixed in DietPi as well, as we use the same kernel and U-Boot sources. It is as well Linux...