snakekick

@BipBip1981In your first post you wrote that 6.18.10 works, while 6.18.35 and 6.18.37 don't. Did you test both the new Armbian overlay and the old DTB with 6.18.35, or only one of them? I'm trying to find out whether the DTB makes any difference on 6.18.35.

Hello @BipBip1981, with Kernel 6.18.35 / Armbian 26.5.1, are you using @iav's new DTP patch or the old DTP file? I'm not sure if it makes any difference, so I was curious what you're using.

This is my current uptime, with a running smb, torrent server, and 4 docker containers. It's a shame that the voltage fix never seems to be “officially” adopted. A system hardly needs to be any more stable than this

Hello @prahal with your voltage fix I have an uptime of 158 days. Without, maybe 3-4 days if it boots at all. Your other fixes are also great. But they don't have the same impact by far. Even if the voltage is not a 100% fix in your eyes, for most people it is a game changer and enables operation in the first place, so I am surprised that you see so little priority there. Please don't get me wrong, I'm very grateful for the fix, I just think it should be implemented first, as I think stable operation is more important than how an LED flashes

Hello @prahal, sorry if I'm annoying. 25.2 is out, did it work out that you could bring in your fixes? many thanks

Hello @prahal do you think you will impementing your dtb changes to official sources so we can upgrade to newer kernel without manuell changes are needed? Thank you

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!