iav

yes. at least it works for me now.

In current thread that means "Armbian was not available for Helios64 hardware for a time. But then it fixed, and anyone can make sdcard with fresh armbian system for Helios64 device". u-boot — software, use by armbian on first seconds after device powered on.

Then, thanks to Prahal, bootable images for Helios64 can be build again.

I think moving to media group will be too much for NAS device.

I will run build and boot result image on Helios64 hardware in case somebody fix error.

yes

serial console works as usual. grub menu selectable, in edit mode text can be edited. with 6.0.1 system cooler runs on full speed, armbian-config not provide processor frequences to choose min and max.

debian version — console jammy.0.txt diagnostic http://ix.io/4cXz all the same.

I run headless, with serial console. jammy.0.txt `reboot` does reboot, `poweroff` not power off after shutdown. boot takes a lot of time, you can see by timestamps. `armbian-config` allows me to set scheduler to schedutil and set min and max frequences. System cooler was off until I setup 7zip and run benchmark `7zz b`. then system cooler turns on until test was completed, then turns off. system diagnostics http://ix.io/4cXm

shutdown and reboot commands stays system shutted down but powered on.

Sorry, there nothing to connect to HDMI. And there no login prompt on serial console. But yes, network scan found an IP obtained with DHCP, then I successful login into armbian first login wizard. System cooler works on full speed all the time.

there boot log on Helios64, image from yandex disk screen.txt

I go by tree from ytour post /sys/devices/platform/p6-fan/hwmon/hwmon6 ans see no hwmon in /sys/devices/platform/p6-fan(begin of lines removed): root@helios64:/sys/devices/platform/p6-fan# ls -l driver_override modalias of_node -> ../../../firmware/devicetree/base/p6-fan power subsystem -> ../../../bus/platform supplier:platform:ff420010.pwm -> ../../virtual/devlink/platform:ff420010.pwm--platform:p6-fan uevent waiting_for_supplier I build this kernel with armbian default kernel config. How can we have different trees in /sys on same hardware?

Fresh build edge bullseye image with kernel Linux helios 5.18.0-rockchip64 #trunk SMP PREEMPT Sun May 29 20:19:27 EEST 2022 aarch64 GNU/Linux fancontrol not work, because there no /dev/fan devices How to get fancontrol back to work?

How to use kdump on SBC, with armbian, and kernel, builded in armbian build system and installed as .deb packets?

can you provide hints on setting up kdump with armbian?

Still not work with fresh-build edge images. No simlink /dev/thermal-cpu, fancontrol start to work if manualy do ln -s /sys/devices/virtual/thermal/thermal_zone0/hwmon0 /dev/thermal-cpu TL;DR: in /etc/udev/rules.d/90-helios64-hwmon.rules an line 16 set ATTR{name}=="cpu|cpu_thermal".instead of ATTR{name}=="cpu" ... and I see two extra simlinks in root: hwmon0 -> /sys/devices/virtual/thermal/thermal_zone0/hwmon0 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 I look for /sys/devices/virtual/thermal/thermal_zone0/hwmon0 in udev: udevadm info -q all -a /sys/devices/virtual/thermal/thermal_zone0/hwmon0 Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/virtual/thermal/thermal_zone0/hwmon0': KERNEL=="hwmon0" SUBSYSTEM=="hwmon" DRIVER=="" ATTR{name}=="cpu_thermal" ATTR{power/control}=="auto" ATTR{power/runtime_active_time}=="0" ATTR{power/runtime_status}=="unsupported" ATTR{power/runtime_suspended_time}=="0" ATTR{temp1_crit}=="100000" ATTR{temp1_input}=="34444" looking at parent device '/devices/virtual/thermal/thermal_zone0': KERNELS=="thermal_zone0" SUBSYSTEMS=="thermal" DRIVERS=="" ATTRS{available_policies}=="user_space step_wise bang_bang fair_share " ATTRS{cdev0_trip_point}=="1" ATTRS{cdev0_weight}=="0" ATTRS{cdev1_trip_point}=="0" ATTRS{cdev1_weight}=="0" ATTRS{cdev2_trip_point}=="1" ATTRS{cdev2_weight}=="0" ATTRS{integral_cutoff}=="0" ATTRS{k_d}=="0" ATTRS{k_i}=="0" ATTRS{k_po}=="0" ATTRS{k_pu}=="0" ATTRS{mode}=="enabled" ATTRS{offset}=="0" ATTRS{policy}=="step_wise" ATTRS{power/control}=="auto" ATTRS{power/runtime_active_time}=="0" ATTRS{power/runtime_status}=="unsupported" ATTRS{power/runtime_suspended_time}=="0" ATTRS{slope}=="1" ATTRS{sustainable_power}=="0" ATTRS{temp}=="33888" ATTRS{trip_point_0_hyst}=="2000" ATTRS{trip_point_0_temp}=="85000" ATTRS{trip_point_0_type}=="passive" ATTRS{trip_point_1_hyst}=="2000" ATTRS{trip_point_1_temp}=="95000" ATTRS{trip_point_1_type}=="passive" ATTRS{trip_point_2_hyst}=="2000" ATTRS{trip_point_2_temp}=="100000" ATTRS{trip_point_2_type}=="critical" ATTRS{type}=="cpu-thermal" I see there ATTR{name}=="cpu_thermal" have to be choosed. an line 16 set ATTR{name}=="cpu|cpu_thermal". Victory, now /dev contains link thermal-cpu -> /sys/devices/virtual/thermal/thermal_zone0/hwmon0 fancontrol works @Heisath? upd: checked in https://github.com/armbian/build/commit/37662d8ed3cbcdb8c975e21bc2e709c365441d1e

error text was ``` [ o.k. ] Installing base system [ Stage 2/2 ] /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) W: Failure trying to run: mount -t proc proc /proc W: See //debootstrap/debootstrap.log for details W: Failure trying to run: /sbin/ldconfig W: See //debootstrap/debootstrap.log for details [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:212 ] [ error ] Debootstrap base system for current rockpi-4a hirsute no second stage failed [ o.k. ] Process terminated ``` Main string is `W: Failure trying to run: /sbin/ldconfig`

I got similar error: on my x64 builder with Ubuntu Focal trying to build rootfs for `hirsute` or `impish` ``` [ o.k. ] Installing base system [ Stage 2/2 ] /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) W: Failure trying to run: mount -t proc proc /proc W: See //debootstrap/debootstrap.log for details W: Failure trying to run: /sbin/ldconfig W: See //debootstrap/debootstrap.log for details [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:212 ] [ error ] Debootstrap base system for current rockpi-4a hirsute no second stage failed [ o.k. ] Process terminated ``` Main string is `W: Failure trying to run: /sbin/ldconfig` failure gone when I refresh qemu-user-static setup with text `docker run --rm --privileged multiarch/qemu-user-static --reset -p yes`

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.