c0rnelius

@laibsch That first one you posted is one of the ones I boot tested a week ago. It is still in my Download dir. Booted for me.

You should try erasing the eMMC or re-flashing U-Boot to it. I don't see why that would be necessary, as it wasn't for me. But I did read somewhere on their wiki at one point that in some use cases erasing the eMMC is a work around when getting boot fails.

Plus the kernel source is getting pulled from their repo. If they did make a change, you should see it on Armbian.

I don't see anything in the history that would suggest they made any changes? I could submit a RTW88 patch I put together from the lwfinger/rtw88 repo. But seeing as the pi guys haven't appeared to have changed anything on their end, it is probs more trouble than it is worth.

Run a diff on the pi and armbian defconfig. https://github.com/raspberrypi/linux/tree/rpi-6.12.y/arch/arm64/configs

Well apparently it is an issue, as stated above by @JFL. Also, after a RECALL, I'm the one who did the PR to change it from =y to =m. https://github.com/armbian/build/pull/8300/commits/bb71177580b34c1aeaeb601696d603b6dc49d326 As for udev and delay, you could edit the udev system file; /lib/udev/rules.d/50-udev-default.rules The line you want to edit is about 15 lines down. Change from rtc0 to rtc1.

For those without a battery connected wouldn't this be an issue?

@OleksandrK Would changing the symlink suffice? ls -ls /dev/rtc* 0 lrwxrwxrwx 1 root root 4 Aug 25 11:14 /dev/rtc -> rtc1 0 crw------- 1 root root 252, 0 Aug 25 11:14 /dev/rtc0 0 crw------- 1 root root 252, 1 Aug 25 11:14 /dev/rtc1 echo 'SUBSYSTEM=="rtc", KERNEL=="rtc1", SYMLINK+="rtc" OPTIONS+="link_priority=-100"' | sudo tee /etc/udev/rules.d/10-hym8563-rtc.rules This way both get loaded, but /dev/rtc is linked to rtc1 "hym8563".

On other platforms we can usually set an alias in the DTS for the rtc. On RK I'm not seeing that as an option, but what we can do is make it so one module loads before the other. In short, we set `CONFIG_RTC_DRV_HYM8563=y` and leave `CONFIG_RTC_DRV_RK808=m`. Which will force a hierarchy in the way things load. Case in point; patrick@nanopir3s:~$ dmesg | grep rtc [ 4.646223] rtc-hym8563 1-0051: registered as rtc0 [ 4.647295] rtc-hym8563 1-0051: setting system clock to 2025-08-25T01:34:16 UTC (1756085656) [ 5.548534] rk808-rtc rk808-rtc.5.auto: registered as rtc1 [ 5.605731] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 5.605810] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes We may also be able to achieve this with a udev rule? I'll do a PR after further testing.

Before loading the module `sudo modprobe cfg80211`

Try the devel repo: https://github.com/lwfinger/rtw88

Why not do a PR and add the needed modules to the EDGE config?

Try the following: Armbian_25.8.1_Nanopi-r3s-lts_bookworm_current_6.12.41_minimal.img https://dl.armbian.com/nanopi-r3s-lts/Bookworm_current_minimal

Yes. I also used gnome-disks and didn't bother to decompress, as it is not required to do so. Which img are you writing exactly?

@OleksandrK I wrote both the Bookworm and Noble img and in both cases the partition table looked fine. I booted the Noble img; _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.8.1 for NanoPi R3S LTS running Armbian Linux 6.12.41-current-rockchip64 Packages: Ubuntu stable (noble) IPv4: (LAN) 10.0.0.xxx (WAN) xx.xxx.xxx.xx IPv6: 2601:xx:xxx:a200::b05b, 2601:xx:xxx:a200:510c:3033:d120:7b0d (WAN) 2601:xx:xxx:a200:e489:6cce:bd44:57dc Performance: Load: 25% Uptime: 1 min Memory usage: 8% of 1.92G CPU temp: 30°C Usage of /: 10% of 29G RX today: 127 KiB Commands: Configuration : armbian-config Monitoring : htop Last login: Fri Aug 22 09:00:15 2025 from 10.0.0.36 root@nanopi-r3s-lts:~# As asked before, did you decompress the img before writing?