iav

Currently I not see file rk3328_miniloader_v2.46.bin at https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33 What is current replacement?

Thank you, @chewitt, works for me! but check, isn't it a mistype — "wtd@"? Maybe, there should be "wdt"? t↔d?

Currently no /dev/watchdog device on N2 with -current and -dev armbian kkernel. But watchdog present in -legacy. I see meson-wdt kernel module present on image, I transplant meson_wdt segment from dts file of legacy kernel to dev and current. diff --git a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts index 819afc748828..18990208f269 100644 --- a/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts +++ b/arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts @@ -226,6 +226,20 @@ hdmi_connector_in: endpoint { };

Possible fixed with https://github.com/armbian/build/commit/51566cc4790b4fc0895579fa432e2c7028afabe1

Now RTC patch for N2 in armbian build system. Hope problem is solved.

Currently no /dev/watchdog device on N2 with -current and -dev armbian kkernel. But watchdog present in -legacy. I see meson-wdt kernel module on image, I transplant meson_wdt segment from dts file of legacy kernel to dev and current. No success. No any sign watchdog presence. What I miss? wd5.8-meson-g12b-odroid-n2.dts.patch

And where you got that kernel? Where I can to look into patches? dts and config?

I did a patch to allow armbian build system produce image with root on xfs filesystem. Kernel should have build-in filesystem support, and `RELEASE` have to contain required filesystem utilities. Then all need to be done — add filesystem to build process. Patch for builder attached. Then image have to be build with separate /boot filesystem. command should look like ./compile.sh BOARD=rockpi-4a BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes BOOTSIZE=250 ROOTFS_TYPE=xfs add_xfs_root.patch

Security theater. If it can be good enough for physical console/terminal-oriented distributives not mean it will be good for all forewer. Maximum can be acceptable — create user on first logon (can be skipped!) and propose to lock ssh root login after first successful user logon. All more "secured" scenarios will produce unusable inaccessible devices.

Now i2c3 in armbian patches https://github.com/armbian/build/blob/master/patch/kernel/meson64-current/hardkernel-0007-N2-ARM64-dts-add-i2c2-i2c3-node.patch

TL;DR Where in armbian build system correctly can be make N2-only related changes: 1. /boot ext4 volume have to have symlink . as boot, can be created with command ln -s ./ boot 2. kernel env variable set in boot.ini contain part but it shouldn't. This substring need to be removed if btrfs choosen. 3. /boot ext4 partition have only 4 MB free. I am not sure but think it's too small; for example there no space to run update-initramfs -u. I think it should be larger, like 500 MB. Long: I want to run my oDroid-N2 with root on BTRFS filesystem. I use manua

@martinayotte pleeease. so long present, but not in armbian trunk. @chewitt have same patches too, but not push.

Or via matrix bridge: #freenode_#armbian:matrix.org

yes, I did it already... but I not understand how to avoid manual path creation and dt copying with manual hwclock run. To let it work as it should — set system clock at a boot time.