@djurny Sorry for the super late response. Here the answers on your questions: ls -Failh /dev/rtc* 457 lrwxrwxrwx 1 root root 4 Mar 7 01:56 /dev/rtc -> rtc0 107 crw------- 1 root root 253, 0 Mar 7 01:56 /dev/rtc0 542 crw------- 1 root root 253, 1 Mar 7 01:56 /dev/rtc1 ls -Failh /sys/class/rtc/ total 0 3926 drwxr-xr-x 2 root root 0 Jan 1 1970 ./ 10 drwxr-xr-x 63 root root 0 Jan 1 1970 ../ 8295 lrwxrwxrwx 1 root root 0 Jan 1 1970 rtc0 -> ../../devices/platform/soc/1f00000.rtc/rtc/rtc0/ 21463 lrwxrwxrwx 1 root root 0 Sep 3 23:18 rtc1 -> ../../devices/platform/soc/1c2ac00.i2c/i2c-0/0-0068/rtc/rtc1/ egrep -- . /sys/class/rtc/*/name /sys/class/rtc/rtc0/name:sun6i-rtc 1f00000.rtc /sys/class/rtc/rtc1/name:rtc-ds1307 0-0068 dmesg | egrep -i -- 'rtc' [ 1.042165] sun6i-rtc 1f00000.rtc: registered as rtc0 [ 1.042235] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01T00:00:04 UTC (4) [ 1.774229] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.776966] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 19.347508] rtc-ds1307 0-0068: registered as rtc1 sudo hwclock --rtc=/dev/rtc0 # per default this is the H2+ built-in RTC 2025-09-03 23:32:07.935209+10:00 ==> date set to Australia (Tasmania) sudo hwclock --rtc=/dev/rtc1 # per default this is going to be the I2C RTC 2000-01-02 15:51:14.147878+11:00 ==> ?????????? So, I clearly don't understand the system. What do I want? Just the right time when connected to a wireless network. (If not available, my system switches to being an Access Point) If my system is acting as an Access Point, the date and time needs to be correct to, that's why I thought I need an RTC module. If not needed, how do I get the right time when my system operates as an Access Point. Thanks for helping

Hey there. Thanks for the detailed tutorial. I tried following it to install Armbian Trixie minimal on my Raspberry Pi 5's nVME (I'm on a headless setup with SSH access). The SD card that boots and runs the system so far is also an Armbian Trixie minimal installation. Apparently nobody has confirmed the instructions to work for that device / setup in this thread yet. So far I also have failed. After following through all steps my device wouldn't connect via ethernet (the LEDs didn't even blink). For simplifying things and rule out a source for possible mistakes, I then repeated the whole process without encrypting the drive, again without much success. Here's what I suspect to be the problem: The Armbian minimal image for the Raspberry family comes already with two partitions: a boot partition with a number of .dtb files for each device of the Raspberry family a "root" partition with all other files Device Boot Start End Sectors Size Id Type /dev/loop0p1 8192 532479 524288 256M b W95 FAT32 /dev/loop0p2 532480 3088383 2555904 1.2G 83 Linux I suspect it to boot in a different way than the image in the example, which seems to directily have all the files which I find in my second partition of the image. So, what I tried was to just create two partitions, mimicing the ones on the Image: Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 8192 532479 524288 256M b W95 FAT32 /dev/nvme0n1p2 532480 3907029167 3906496688 1.8T 83 Linux I would then just copy the contents of each partition respectively. But even that wouldn't boot the way it did with the SD card. Of course I could just use dd to copy the image to the 2TB nVME but that would take forever (20 h aprox.) and it wouldn't result in an encrypted system. My questions are: Is it even possible to use the way of copying boot files and contents in this tutorial to achieve a bootable nVME? If the image for the Raspi family relies on its own boot partition will I ever be able to use it for decrypting an encrypted drive before booting from it at all? Can I use it for both, booting the device and decrypting the drive, or would that be principally impossible? I'll be happy for any help for making it work or hint if the described procedure cannot work for my setup. Tonight I'll also join an install party and might have the opportunity to plug a screen to my Raspi and see if it gives hints during the boot sequence.

@Nick AHow to use your code repository(https://github.com/NickAlilovic/build) to add a 1.5GB RAM patch.

Here it is: https://paste.armbian.com/ququgojasu

Hi again, It took some time but finally I was able to take a look at it myself. It seems to me that the original kernel patch from @brentr is still a working solution as the affected kernel code didn't change in the current kernel. So by applying the original patch, 10mpbs Ethernet started working again on my Rockpi S. I'm not able I created PR #8575 - Fixes regression of failing 10Mbit built-in Ethernet in Rockpi S to add the patch again. I hope, that's ok as I'm lacking experience in this field so please apologize if I missed something, I just want to help and improve 🙂 Cheers,