iav

  • Posts

    28
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Latvia

Contact Methods

  • Matrix
    shtripok@gmail.com
  • Github
    iav

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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.
  3. I not see in Helios64 assembling guide, how should be set coolers. Where should be directed airflow? Inside or outside the case?
  4. 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
  5. 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
  6. 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.
  7. 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?
  8. Thank you, @chewitt, works for me! but check, isn't it a mistype — "wtd@"? Maybe, there should be "wdt"? t↔d?
  9. 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?
  10. Possible fixed with https://github.com/armbian/build/commit/51566cc4790b4fc0895579fa432e2c7028afabe1
  11. 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
  12. And where you got that kernel? Where I can to look into patches? dts and config?
  13. 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