snakekick

i have now a uptime from 71 Days with your dtb file @ebin-dev do you will commit your fixes to the official version?

Thank you @ebin-dev same here, 6.6.29 (much more) stable with your dtb. I know we are all the community and can make changes but... is it possible for you to make a ticket/change request or as its called to add your changes to the main armbian image? so that we have a good running Helios out of the box? That would be fantastic!

Kernel 5.15.93 (get not "stable" with 6x kernel) linux-u-boot-current-helios64_21.08.9_arm64.deb Uptime 20 Days (but kernel panic after ±30 Days) CPU Speed: MIN_SPEED=600000 MAX_SPEED=1200000 GOVERNOR=ondemand Systemusage: Fileserver (Mergerfs/Snapraid with 5 SSD+1USB HDD with daily diff/scrub/sync ) Webserver 1 Docker Container ./cpufreq-switching-2-b_delay_5000 allocated 64MB test: toggle freq before write 0/100 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 kernelpanic

hello mikeakers, you can test you memory with for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done it is possible that bootloader was also updated during the update to bookworm and that can be a problem if this run 5-6 times without errors you try to limit the cpu speed with armbian-config for me, my system only run "stable" with 600-1200mhz

Hello @prahal and @ebin-dev any news on your stability tests? I also have occasional freezes and reboot problems, so I'm very curious to see if anything will change. Thank you very much for your commitment!

Hi, I have also been testing Bookworm for a week. I start with a clean install and use snapraid. Before bookworm I use kernel 5.15 with Bullseye. To get a stable system I have to limit my cpu to 600>1200mhz on demand. Now with bookworm and kernel 6.1.36 these settings are not enough. Every time I start a snapraid sync I get kernel ops. I'm now back to kernel 5.15 with debian bookworm and it looks more stable (1 full sync successful) //edit. system is still unstable. i found a good fast test for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done give me a free() invalid pointer issue I found in this thread that there can be a problem with memory speed detection? https://github.com/armbian/build/issues/4761 /edit 2 For me, it looks like the new uboot version from here https://github.com/armbian/build/issues/4761 Solved all my problems. Snapraid sync --force-full without any problems (ran 6 hours) and the python3 test (6 times) also without any errors. and best of all, the helios are now running at full speed! 400>1800MHz on demand this was not possible before the uboot update. if i understand correctly. the ddr memory now dects better with correct speed settings. edit3 hahaha Rejoyed too soon kernel:[47341.023705] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Message from syslogd@helios64 at Aug 22 10:59:53 ... kernel:[47341.023705] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Message from syslogd@helios64 at Aug 22 10:59:53 ... kernel:[47341.045273] Code: aa1c03e0 93407c62 2a0803e1 9400819e (a9408261) ;(

Hello, can sombody please explane the current status? is it secure to make a apt update (and reboot) or is update now not possible or recomment

Hi, a new version armbian-bsp-cli-helios64 (21.05.4) released today but still have the same error. ;((

Hello, i don´t have a xserver installed so i don´t have and can use xrandr log´s are here. http://ix.io/3o6R thanks you

Hello, today i try a USB C to HDMI Adapter and i get some picture on tv but it´s really unreadable and my log is full of this: rockchip-vop ff8f0000.vop: [drm:vop_plane_atomic_update [rockchipdrm]] *ERROR* Maximum dst width (3840) exceeded it is possible to restrict the resolution in the terminal? i think this error ocure because to high resolution or wrong detection Thank you

...now i got the same .... 5 SDD SanDisk SDSSDH3 2T00 but yet only with one disk. no zfs but snapraid with daily check and scrub [Sat May 8 20:16:25 2021] ata4.00: exception Emask 0x10 SAct 0x80000 SErr 0xb80100 action 0x6 [Sat May 8 20:16:25 2021] ata4.00: irq_stat 0x08000000 [Sat May 8 20:16:25 2021] ata4: SError: { UnrecovData 10B8B Dispar BadCRC LinkSeq } [Sat May 8 20:16:25 2021] ata4.00: failed command: READ FPDMA QUEUED [Sat May 8 20:16:25 2021] ata4.00: cmd 60/00:98:40:0d:fa/04:00:56:00:00/40 tag 19 ncq dma 524288 in res 40/00:9c:40:0d:fa/00:00:56:00:00/40 Emask 0x10 (ATA bus error) [Sat May 8 20:16:25 2021] ata4.00: status: { DRDY } [Sat May 8 20:16:25 2021] ata4: hard resetting link [Sat May 8 20:16:25 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [Sat May 8 20:16:25 2021] ata4.00: configured for UDMA/133 [Sat May 8 20:16:25 2021] sd 3:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s [Sat May 8 20:16:25 2021] sd 3:0:0:0: [sdd] tag#19 Sense Key : 0x5 [current] [Sat May 8 20:16:25 2021] sd 3:0:0:0: [sdd] tag#19 ASC=0x21 ASCQ=0x4 [Sat May 8 20:16:25 2021] sd 3:0:0:0: [sdd] tag#19 CDB: opcode=0x28 28 00 56 fa 0d 40 00 04 00 00 [Sat May 8 20:16:25 2021] blk_update_request: I/O error, dev sdd, sector 1459227968 op 0x0:(READ) flags 0x80700 phys_seg 127 prio class 0 [Sat May 8 20:16:25 2021] ata4: EH complete

when i now read the Helios64 Production Update 4 https://blog.kobol.io/2020/08/23/helios64-update4/ "Our test successful rate is not as high as we expected. It turned out that our FAT software was a bit too strict resulting in some board failing the FAT while they are actually OK" its get a little bit bad taste...

Hello, i want use and control kodi on my Helios64 with the tv remote. Have someone experiance with that and a recommendation for cables or usb c dockingstation? thank you

hello @SIGSEGV tuned is only a another CPU Scaling Governor or? do you have problems before you switch to tuned and this solve your problems ?