• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SIGSEGV's Achievements

  1. I'm curious about this issue. Let us know if changing the CPU Voltage has an effect on system stability.
  2. Hello @Igor, @Werner, I'm open to collaborating to the armbian project, my background is on software development and system administration and I have a small Helios64 to test things with.
  3. Enjoy your time off - looking forward to new products from you guys.
  4. My comment might be late to the party - if there was a possibility to add an optional display and a few user-configurable buttons to the Front Panel, that would be great. I know it would mess a bit with the airflow, but it could be used for system monitoring and few other specific use cases.
  5. Thanks @aprayoga. What's new or has changed in the latest SATA firmware image?
  6. @wurmfood The script looks goods. I like the check for main power before the battery level verification, it solves the use case @clostro mentioned. @aprayoga Looking forward to the new release
  7. @wurmfood On my system the helios64-ups.timer is disabled by default. Is this a timer that has to be manually enabled ?? I thought that the Helios would check if it had the battery and activate this automagically. It might be better to have a daemon in the background that checked the battery value every 20 seconds and only printed out output when there was a change.
  8. Thanks for the information @gprovost. From the looks of it - Armbian 21.02.03 seems to install the Rockchip Blob. Where does the U-boot TPL/SPL come from ?? the new beta builds? Regards.
  9. My case is similar to @wurmfood's - latest OS, ZFS and no OMV. @gprovost, how can we check and determine "if you are using rockchip blob or u-boot TPL/SPL"?
  10. Thanks for the tip @ShadowDance, in my case I haven't had any crashes while using ZFS. But I've updated my systemd scripts to take the ZFS scheduler into account. What I did notice was that my data-sets on raid-z1 pool seems to be a bit more snappy (it might be a perception issue on my part). [Unit] Description=HDD-Idle service [Service] Type=oneshot ## Set Power Management parameters to all HDD ExecStart=/bin/sh -c '/usr/sbin/hdparm -qB255S120 /dev/sd[a-e]' ## Allows ZFS to use it's own scheduler for rotating disks. ExecStart=/bin/sh -c 'echo none | tee /sys/block/sd[a-e]/queue/scheduler' [Install]
  11. @oneo - what distro are you trying out?
  12. @allen--smithee Thanks for the feedback.
  13. I did have a few lockups when running my setup scripts that actually install a few of the packages I needed/wanted to run on the Helios64. It would lock sometimes while idle. 'tuned' was one of the packages that is installed on our cloud environments and some options are available through the cockpit management interface. I wouldn't describe 'tuned' as a CPU Scaling Governor. The one thing I noticed was that if configured tuned in the early steps of installation - my scripts would finish running their task and I didn't have lockups (if tuned was not configured early in the process it would freeze at random points). tuned project - their website description is as follows Tuned is a system tuning service for Linux. It: monitors connected devices using the udev device manager tunes system settings according to a selected profile supports various types of configuration like sysctl, sysfs, or kernel boot command line parameters, which are integrated in a plug-in architecture supports hot plugging of devices and can be controlled from the command line or through D-Bus, so it can be easily integrated into existing administering solutions: for example, with Cockpit can be run in no-daemon mode with limited functionality (for example, no support for D-Bus, udev, tuning of newly created processes, and so on) for systems with reduced resources stores all its configuration cleanly in one place – in the Tuned profile – instead of having configuration on multiple places and in custom scripts Take my word with a grain of salt - this is only my experience with the Helios64.
  14. @aprayoga, @gprovost, One thing that has worked for me since I got the board around on Nov of last year is to install package 'tuned' and set the profile to 'server-powersave'. The two BIG cores can go up to 1.8GHz and the little cores go up to 1.4GHz under heavy usage without any lockups - most of the time in idle they stay at 408MHz. apt -y install tuned tuned-adm profile server-powersave systemctl restart tuned
  15. @allen--smithee Nice - having the temperature ramp up slowly is sign that the new thermal pad + heat sink + fans are working better. So from factory only the CPU has a thermal pad? or is there more than one contact point with the heatsink from the factory? I'm much inclined to try this solution on my system - just to get the slow & gentle temperature curve (plus I have a few ARM based handhelds that might need a bit of heatsink modding).