iav

I see that picture, but not see there airflow direction. Possible this mark should be more clear or bright. Is it so hard to just text something "air should go inside" or draw an arrow?

Thank you for tip. But I not see that on link you provide. Maybe be better to add that info it clear text into document you refer to.

I not see in Helios64 assembling guide, how should be set coolers. Where should be directed airflow? Inside or outside the case?

Fresh-builded armbian image, Helios4. Try to enter armbian-config → system → cpu root@helios4:~# cat /etc/os-release NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Armbian 21.08.0-trunk Hirsute" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute

I try that on my Helios4 with Armbian 21.08.0-trunk Hirsute. Service can't start Jun 15 20:58:54 helios4 kernel: audit: type=1326 audit(1623790734.437:21): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2134 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f9cb68 code=0x80000000 but I can be started from command line, with default options: # haveged --Foreground --verbose=1 haveged: command socket is listening at fd 3 haveged starting up haveged: ver: 1.9.8; arch: generic; vend: ; build: (gcc 10.2.1 CTV); collect: 128K haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 12/40; sz: 15006/57790 haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99541 haveged: fills: 0, generated: 0

Server grade hardware are NOISY. Because of low-profile cases, low-size turbines, they have to send airflow very, very fast — to push enough air through small holes.

This will ruine airflow.

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 { }; }; }; + + wdt: watchdog@0xffd0f0d0 { + compatible = "amlogic, meson-wdt"; + status = "okay"; + default_timeout=<10>; + reset_watchdog_method=<1>; /* 0:sysfs,1:kernel */ + reset_watchdog_time=<2>; + shutdown_timeout=<10>; + firmware_timeout=<6>; + suspend_timeout=<6>; + reg = <0x0 0xffd0f0d0 0x0 0x10>; + clock-names = "xtal"; + clocks = <&xtal>; + }; sound { compatible = "amlogic,axg-sound-card"; No success. No any sign watchdog presence. What I miss?

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 manual on armbian image build and did time ./compile.sh BOARD=odroidn2 BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes ROOTFS_TYPE=btrfs INSTALL_HEADERS=no BUILD_KSRC=no then image Armbian_20.08.0-trunk_Odroidn2_focal_current_5.7.16.img was written to microSD card with BalenaEtcher program, inserted into N2 with serial console connected. cap1.log Then I create simlink ./ boot on boot volume, and get cap2.log Then I remove rootflags=data=writeback from bootargs and successfully boot into shell prompt, cap3.log changes: diff -u boot.ini.org boot.ini.run --- boot.ini.org 2020-08-20 23:08:36.000000000 +0300 +++ boot.ini.run 2020-08-20 23:26:29.000000000 +0300 @@ -20,7 +20,7 @@ fi # Default Console Device Setting -setenv condev "console=${uartconsole} console=tty1 loglevel=1" # on both +setenv condev "console=${uartconsole} console=tty1 loglevel=5" # on both # Auto Detection of Monitor settings based on your Screen information setenv display_autodetect "true" @@ -115,7 +115,7 @@ if ext4load mmc ${devno}:1 0x44000000 /boot/armbianEnv.txt || fatload mmc ${devno}:1 0x44000000 armbianEnv.txt || ext4load mmc ${devno}:1 0x44000000 armbianEnv.txt; then env import -t 0x44000000 ${filesize}; fi # Boot Args -setenv bootargs "root=${rootdev} rootwait rootflags=data=writeback rw rootfstype=${rootfstype} ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} ${bootsplash} cvbscable=${cvbscable} overscan=${overscan} consoleblank=0" +setenv bootargs "root=${rootdev} rootwait rw rootfstype=${rootfstype} ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} ${bootsplash} cvbscable=${cvbscable} overscan=${overscan} consoleblank=0" # Set load addresses setenv dtb_loadaddr "0x1000000" cap1.log cap2.log cap3.log

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

Or via matrix bridge: `#armbian:libera.chat`

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.

What kernel I have to install to got it work? linux-image-current, -dev, -legacy, other sources?

It works! Thank you! Do you think I have to ask armbian kernel builders to include your code into kernel image?

Thank you for help. Could you please point to faq, howto or something like it to read how to "use this overlay source and compile it and load it"? Sorry, I am not "in context" for a while. But I will :)