BipBip1981

Hello, Yes i set fixed frequency to 1200. For power consumption, i my case off use it's not a problem because i start when use it and stop helios64 when i don't use. My big problem isn't unstability during long time but during intense use. For example: 400Mhz - 1400mhz is okok if helios do nothing... but when fast i/O network or Disk I/O, Helios64 crash or freeze. With 5.1X Kernel, Helios is stable at 400-1400MHZ Schedutil With first 6.X Kernel, Helios is stable at 400-14000MHZ Schedutil With 6.6 Kernel and upper my pattern to test stabilty crash when i use setting above and not crash with 1200 Fixed frequency. At 1400 or more with my pattern to test Helios crash. My configuration is: 8To x 4 Raid 10 -> LVM -> Lucks -> LVM -> BTRFS. To test stabilty i do: - Scrubbing RAID and at same time i do a BTRFS with Checksum check, that do a lot of I/O and Frequency change... Since i pass to Kernel 6.6.X, this pattern to test fail always. With 5.1X Kernel 400-1400MHZ Schedutil and 6.X Kernel 400-14000MHZ Schedutil and at 1200 Fixed, always pass and always crash at 400-1200MHZ. I advise you if you want stable online setting to Keep a 5.1X Kernel with 400-1400MHz. That not my choice because i prefer to follow most update Kernel and i believe (or dreaming) adevelloper find problem with Helios RockChip and correct it one day.

Hello, Try: 1200MHZ 1200MHZ Performance The only stable settings for me since passed to 6.6.X Kernel with Armbian Bookworm

hi, okok, from my side kernel 6.6.12 1200MHz Performance, i do podman run hello-world, no problem and my helios run from 2 days with my freeze test pattern and not freeze for moment. good night or day

okok keep in touch, i am interesting by your feedback.

Hi, try: 1200mhz min freq 1200mhz max freq governor performance in armbian-config program. The best stable configuration in my helios64

Hi, My return, best result and best stabilty is this setting: 1200Mhz max performance with upper frequency random crash... some time just when reconnect to network (ex: restart my router, many samba access) or launch docker container... or just unlock drive with cryptosetup... or during "btrfs check" Have a good day

Hi, It's running with Armbian Brookworm build by me with official script. Two different crash arrive, one with fault led red system flashing, second with all blue led are fix, lost network and lost console access with usb-c cable. In log, they are nothing important, crash append but i not found information in log (My log isn't in ramlog, i disable this shit feature...). I have 4 8TO raid 10 with BTRFS over Luks, i reproduce crash by run btrfs check file system with checksum and mdadm check raid at same time. My brother have helios64 and he crash his Helios simply crash on waiting with docker container active and do nothing and without any HD drive with all last official Kobol Armbian build or with my own build. I will test next week with this image system (https://dl.slarm64.org/slackware/images/helios64/) simply to know if armbian specific problem or hardware problem. Have a good day.

Hi, Game Over for me... again... crash with CPU @400-1200MHz with "on demand" Governor Kernel... in less than 24h... I retry same test with "schedutil" and the last main build by me... I not hope many thing... Return next week Bye

Hi, not crash again 😞 i try step by step "configuration crash" (btrfs check my file system and mdadm check raid at same time, 2 days by pass) with my custom fancontrol file and step by step up cpu frequency with performance governor to not use auto scale frequency. For moment, it stable at 1000mhz, i start a minimum 7 days ago Keep in touch result Bye.

Hi, I use Helios64 from the begin and this board is very unstable according to my experience and many posts here... After many dialogue here and settings shared about Frequency and Governor Kernel... maybe i find the problem and i ask anyone return of experiences about the procedure and setting belong: - Connect USB Wireless Dongle or USB(-c) Ethernet Plug - Configure it - Disconnect all ethernet cable to the board - Use with last time crash configuration and do a endurance test your helios64 board Have a good day

Hi, Today i make upgrade to 23.11 armbian on my Helios64. It's in bookworm version (apt source list is good, no change since 23.08) but now it display this: Welcome to Armbian 23.11.1 Buster with Linux 6.1.63-current-rockchip64 No end-user support: community creations & unsupported (buster) userspace! it's a bug? thank have a nice day