BipBip1981

Hello, To my side the only way to back to a stable helios64 system is to freeze at kernel version 6.18.10 and use the specific DTB file patch. This patch was include in armbian-config program. I was happy but… Since the kernel version upper that 6.18.10… the helios64 nightmare come back 😞 Keep in touch

Hello, Back again to official Helios64 6.18.10 kernel and old dtb patch file. Too many crash, issues... Keep in touch.

Hello, At cold boot today, system red light blink. Today, I pass to Armbian 26.8.3 official package with last Armbian kernel and dtb. Get:10 https://github.armbian.com/configng stable/main arm64 armbian-config all 26.8.0-trunk.426.0825.193013 [1,160 kB] Get:5 http://apt.armbian.com trixie/trixie-utils arm64 base-files arm64 26.8.3-13.8+deb13u6-trixie [54.8 kB] Get:7 http://armbian.hosthatch.com/apt trixie/main arm64 armbian-bsp-cli-helios64 arm64 26.8.3 [1,292 B] Get:8 http://armbian.hosthatch.com/apt trixie/main arm64 armbian-bsp-cli-helios64-current arm64 26.8.3 [124 kB] Get:9 http://armbian.hosthatch.com/apt trixie/main arm64 armbian-firmware-full all 26.8.3 [764 MB] Get:11 http://armbian.hosthatch.com/apt trixie/main arm64 armbian-plymouth-theme all 26.8.3 [112 kB] Get:12 http://armbian.hosthatch.com/apt trixie/main arm64 linux-dtb-current-rockchip64 arm64 26.8.3 [1,096 kB] Get:13 http://armbian.hosthatch.com/apt trixie/main arm64 linux-image-current-rockchip64 arm64 26.8.3 [52.1 MB] Get:14 http://armbian.hosthatch.com/apt trixie/main arm64 linux-u-boot-helios64-current arm64 26.8.3 [584 kB] I think if I have issues or unstable, i back to official Helios64 6.18.10 kernel and old dtb patch file. for the moment: ---> always one time red blinking on all HDD LED during the boot with Kernel ---> pass LUKS openning RAID Keep in touch.

Hello, 3) for "ls /sys/devices/system/cpu/cpufreq/` and `lsmod | grep cpufreq" paste below: ---> with 6.18.10 root@helios64:~# ls /sys/devices/system/cpu/cpufreq/ boost policy0 policy4 root@helios64:~# lsmod | grep cpufreq cpufreq_dt 16384 0 ---> with 6.18.43 and crash root@helios64:~# ls /sys/devices/system/cpu/cpufreq/ boost policy0 policy4 root@helios64:~# lsmod | grep cpufreq root@helios64:~# 1) Not possible to do it, sorry 2) extraargs=cpufreq.off=1 and 6.18.43 ---> always one time red blinking on all HDD LED during the boot with Kernel ---> pass LUKS openning RAID else: root@helios64:~# ls /sys/devices/system/cpu/cpufreq/ ls: cannot access '/sys/devices/system/cpu/cpufreq/': No such file or directory root@helios64:~# lsmod | grep cpufreq root@helios64:~# ------------ With armbian-config helios64 stability overlay ---> always one time red blinking on all HDD LED during the boot with Kernel ---> pass LUKS openning RAID ------------ with helios64-pcie-perst -----> Crash red light on cold boot or reboot sometime ------------- My armbianEnv.txt root@helios64:~# cat /boot/armbianEnv.txt verbosity=7 bootlogo=false overlay_prefix=rockchip rootdev=/dev/mapper/armbian-root cryptdevice=UUID=da46d5b8-afec-674d-9fc5-dc7c7843e895:armbian-root rootfstype=ext4 overlays=rk3399-helios64-cpu-stability extraargs=cpufreq.off=1 user_overlays=helios64-pcie-perst usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u ------------- I continue to test. For moment, i not fan of "one time red blinking on all HDD LED during the boot with Kernel " ...but if my Helios64 become stable with recent kernel, it Okok for me --------------- Why not cpufreq_dt with or without extraargs=cpufreq.off=1 on 6.18.43 ? Possible to restore it ? root@helios64:~# ls /sys/devices/system/cpu/cpufreq/ ls: cannot access '/sys/devices/system/cpu/cpufreq/': No such file or directory root@helios64:~# lsmod | grep cpufreq For information: root@helios64:~# sudo grep 'ep' /sys/kernel/debug/gpio gpio-28 ( |ep ) out hi gpio-27 ( |beeper ) out lo gpiochip5: 16 GPIOs, parent: i2c/2-0020, 2-0020, can sleep: -------------- If I remove: extraargs=cpufreq.off=1 back to the happy world of boot crash red light system very often or same crash like with kernel up than 6.18.10 😞 (all blue lights fix and not helios64 reponse) Keep in touch

Hello, Thank. I try to do your step 1, 2 and 3 next weekend. For information: I see a one time red blinking on all HDD LED during the boot with Kernel version with crash problem. Keep in touch next week

Hello, For information: Same, crash with official Helios64 6.18.43 kernel and rk3399-helios64-cpu-stability armbian-config overlay. Back to official Helios64 6.18.10 kernel and old dtb patch file. Have a good day.

Hello, For information: Same, crash with official Helios64 6.18.43 kernel and rk3399-helios64-cpu-stability armbian-config overlay. Back to official Helios64 6.18.10 kernel and old dtb patch file. Have a good day.

Hello, I make two away with both kernel version. With officiel 6.18.35 and a build by me 6.18.37 with armbian build framework. see here: For the moment, i freeze to version kernel 6.18.10 and DTB file patch and all is Okok. Have a good day.

Hello, I use with 6.18.15 the two way below. - new way with armbian-config and choses the overlay stabilty file for helios64 - the old way with my old dtb file for 6.18.xx kernel that i downloaded in this forum and work good with all 6.18.xx kernel until 6.18.10 kernel (rk3399-kobol-helios64.dtb-6.18.18-opp.zip) Have a good day

Hi SymbiosisSystems, Same problem like you with kernel 6.18.35 and 6.18.37, all it's Okok with 6.18.10 like I said in this post:

Hi, thank, I forget this method. new result... same with 6.18.37: With 6.18.10-current-rockchip64 and rk3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ok With 6.18.37-current-rockchip64 and overlay helios64 patch with armbian-config, Ko With 6.18.37-current-rockchip64 and k3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ko more information: On "Cold Boot": System blink red After "Reset": Same crash like without DTB file patch on previous Kernel like 6.18.10... I try edge with 7.1 kernel but not compile, finish with error during process. Back to 6.18.10 with dtb file patch and freeze with this stable config and kernel for this time, I don't have time to investigate more at this time. Have a nice day

Hello everybody, With 6.18.10-current-rockchip64 and rk3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ok With 6.18.35-current-rockchip64 and overlay helios64 patch with armbian-config, Ko With 6.18.35-current-rockchip64 and k3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ko The crash is random... sometime crash: - At the boot with red system light blinking - At the opening of my LUKS ciffers drives - At a high cpu load - With nothing special, all led are blue, system blinking but network and ssh is Ko Is it possible to explain me how to see the problem or how to have log because I am in blind to have more details ? Is it possible to explain me how to pass to the last 6.18.36 kernel to seen if it is better than 6.18.35 ? Thanks a lot.

Thank @iav

Hello, I use this patch since many year now, me and my brother, with out it, our helios64 are unstable and unusable... with it, our helios64 work fine for more than two year, my opinion is, push the file in mainline or distrib the file in mainline with a script that install it fast with only one command run as soon has possible when not crash on the boot.. Bye.

Boot on a from scratch helios64 sdcard image, cross fingers and copy / rename / replace original dtb file with ebin-dev file or mount sdcard with scratch helios64 on another computer, do the change, then boot with you ready sdcard on the helios64

Hi SymbiosisSystems, here: But I think you find it 😉

Thank a lot !

Hello, I hope you don't have any problem. Maybe me and my brother have defective or more unstable helios64 than you. Only thing I can say that Prahal share here the specifics files rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp in this forum since two years ago my helios64 and my brother's helios64 work stable only with it. I back to 6.12.58 Kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file and freeze firmware/kernel with armbian-config.

For information: First reboot and crash same that before use rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp. 😞 Back to 6.12.58, rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze to this setting Me and my brother have helios64 with 6.18.10 Kernel : RAID 10 / LVM / LUKS and crash always when "cryptsetup open..." start Crash when many I/O Crash when use Full CPUs With rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and Kernel 6.12.58 or 6.12.(XX below): Me, never crash but I reboot often and power off often for personal choice. My brother have uptime upper than 100 or 200 days with problem, freeze or crash Bye

Hi everybody, I running Helios64 with kernel 6.12.58 since a long time and the prahal dtb file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and my helios64 work well. Today, Armbian upgrade to 6.18.10 kernel. Is this update use the same change or patch like in rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp ? Is rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp work with 6..18.10 kernel ? Is I must to downgrade to 6.12.58 kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze at this kernel version ? Thanks for answer.

Hi, In 2025, Helios64 is now stable for me and for my brother, who also uses it. The only thing to do is, just after installation or after any upgrade, you must reinstall the special file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp because I think the specific tuning in this file is not included in the official image. For me, I suggest keeping it, using it, and saving your money for other things. Bye.

Hi, my feedback with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and agressif fancontrol setting like this: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 FCTEMPS=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input MINTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=30 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=30 MAXTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=50 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=50 MINSTART=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINSTOP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINPWM=20 is: All it's Okok Without the tunning file DTB and Fancontrol, the nighmare restart. Today, update, original DTB file restore and CRASH when Luks begin to unciffer my DDs Il restore DTB file and my fancontrol setting and: Return to Okok situation. To conclude, i use my helios without problem when this files is installed. My helios64 always crash if i return to original setting after a update.

Hi, my feedback for fancontrol service here : for 2.5Gbits, i don't use. for rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp, same has i writed up: "It is better to have a good solution in time than a perfect one too late.", my helios64 going to the trash without this workaround.

Hi, To my side, below work in root but not with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu #INTERVAL=10 INTERVAL=30 FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=50 /dev/fan-p7/pwm1=50 MINSTART=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINSTOP=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINPWM=20 To my side, below work in root and with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 FCTEMPS=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input MINTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=40 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=40 MAXTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=50 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=50 MINSTART=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINSTOP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20