greg396

tested sd card: No difference iperf3 from client to Helios around 20mb/s I tested another local 2.5Gbit transfer client (arch arm) - server (armbian) 2.34Gbit/s (292mbit/s) and reverse 326mbit/s (40mb/s) Maybe a setup problem with the switch or with arm-arch client drivers Nevertheless thank you for your help! ;)

I switched back to actual kernel 6.12.22 and if I need to transfer from NAS to Client I'll just use another LAN-cable with 1Gbit and have around 100mb/s And you are right, installing a new image would be the best. But configering OMV again and can't use a simple settings-backup is a nightmare for me I upgraded from Debian11 to 12 (Bullseye) and the upgrading process worked without issues, but maybe that upgrading could bring up the speed issue. sudo ethtool -i end1 Cannot get driver information: No such device In /lib/firmware/rtl_nic/ are all firmware versions... Is ther anything I need to fix?

After shutdown client, Nas, switch I tested the NAS with the downgraded kernel 6.6.87. Using the dtb for 6.6 from here https://forum.armbian.com/applications/core/interface/file/attachment.php?id=13745&key=de08de7cf5b1684faa2f41605ea19a5f Including your optimizations here /etc/rc.local -> done No difference! Speed from NAS to client remains at 200Mbit/s! :( armbian-hardware-optimization is disabled on your system -> how do i do this? make_nas_processes_faster.sh "if iperf3 tests are performed or if helios64 is mounted as a remote drive I call the following script that assigns a big core and a preferred" -> I copied the script to /usr/local/bin/make_nas_processes_faster.sh but how should it'll be started? ./make_nas_processes_faster.sh pgrep: pattern that searches for process name longer than 15 characters will result in zero matches Try `pgrep -f' option to match against the complete command line. Anything I can try?

Dear ebin-dev, I downgraded, got an error concerning linux-headers-current-rockchip64, could solve it with sudo apt --fix-broken install, but hesitating to reboot if I am not shure if the downgrade was 100% sucessful Is there any possibility to check before reboot if anything is well and system will reboot sucessful? sudo dpkg -i linux-* dpkg: warning: downgrading linux-dtb-current-rockchip64 from 25.2.3 to 24.11.0-trunk (Reading database ... 52529 files and directories currently installed.) Preparing to unpack linux-dtb-current-rockchip64_24.11.0-trunk_arm64__6.6.87-S8146-D0531-P5324-C702eH5c21-HK01ba-Vc222-B59f0-R448a.deb ... Armbian 'linux-dtb-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' starting. Armbian 'linux-dtb-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' finishing. Unpacking linux-dtb-current-rockchip64 (24.11.0-trunk) over (25.2.3) ... Selecting previously unselected package linux-headers-current-rockchip64. Preparing to unpack linux-headers-current-rockchip64_24.11.0-trunk_arm64__6.6.87-S8146-D0531-P5324-C702eH5c21-HK01ba-Vc222-B59f0-R448a.deb ... Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' starting. Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' finishing. Unpacking linux-headers-current-rockchip64 (24.11.0-trunk) ... dpkg: warning: downgrading linux-image-current-rockchip64 from 25.2.3 to 24.11.0-trunk Preparing to unpack linux-image-current-rockchip64_24.11.0-trunk_arm64__6.6.87-S8146-D0531-P5324-C702eH5c21-HK01ba-Vc222-B59f0-R448a.deb ... Armbian 'linux-image-current-rockchip64' for '6.12.22-current-rockchip64': 'prerm' starting. Armbian 'linux-image-current-rockchip64' for '6.12.22-current-rockchip64': 'prerm' finishing. Armbian 'linux-image-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' starting. ls: cannot access '/var/lib/initramfs-tools': No such file or directory Armbian 'linux-image-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' finishing. Unpacking linux-image-current-rockchip64 (24.11.0-trunk) over (25.2.3) ... Armbian 'linux-image-current-rockchip64' for '6.12.22-current-rockchip64': 'postrm' starting. Armbian 'linux-image-current-rockchip64' for '6.12.22-current-rockchip64': 'postrm' finishing. Setting up linux-dtb-current-rockchip64 (24.11.0-trunk) ... Armbian 'linux-dtb-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.87-current-rockchip64... 'dtb' -> 'dtb-6.6.87-current-rockchip64' Armbian 'linux-dtb-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' finishing. dpkg: dependency problems prevent configuration of linux-headers-current-rockchip64: linux-headers-current-rockchip64 depends on libelf-dev; however: Package libelf-dev is not installed. dpkg: error processing package linux-headers-current-rockchip64 (--install): dependency problems - leaving unconfigured Setting up linux-image-current-rockchip64 (24.11.0-trunk) ... Armbian 'linux-image-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.6.87-current-rockchip64 update-initramfs: Converting to u-boot format Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.6.87-current-rockchip64' Armbian: Debian compat: linux-update-symlinks install 6.6.87-current-rockchip64 boot/vmlinuz-6.6.87-current-rockchip64 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.87-current-rockchip64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.87-current-rockchip64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.87-current-rockchip64 I: /initrd.img is now a symlink to boot/initrd.img-6.6.87-current-rockchip64 Armbian 'linux-image-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' finishing. Errors were encountered while processing: linux-headers-current-rockchip64 sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libelf-dev zlib1g-dev The following NEW packages will be installed: libelf-dev zlib1g-dev 0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. Need to get 987 kB of archives. After this operation, 1716 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://deb.debian.org/debian bookworm/main arm64 zlib1g-dev arm64 1:1.2.13.dfsg-1 [913 kB] Get:2 http://deb.debian.org/debian bookworm/main arm64 libelf-dev arm64 0.188-2.1 [73.8 kB] Fetched 987 kB in 0s (2258 kB/s) Selecting previously unselected package zlib1g-dev:arm64. (Reading database ... 78145 files and directories currently installed.) Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-1_arm64.deb ... Unpacking zlib1g-dev:arm64 (1:1.2.13.dfsg-1) ... Selecting previously unselected package libelf-dev:arm64. Preparing to unpack .../libelf-dev_0.188-2.1_arm64.deb ... Unpacking libelf-dev:arm64 (0.188-2.1) ... Setting up zlib1g-dev:arm64 (1:1.2.13.dfsg-1) ... Setting up libelf-dev:arm64 (0.188-2.1) ... Setting up linux-headers-current-rockchip64 (24.11.0-trunk) ... Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' starting. Compiling kernel-headers tools (6.6.87-current-rockchip64) using 6 CPUs - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/insert-sys-cert HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/symsearch.o UPD scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers tools (6.6.87-current-rockchip64). Done compiling kernel-headers tools (6.6.87-current-rockchip64). Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' finishing. Processing triggers for man-db (2.11.2-2) ... sudo dpkg -i linux-headers-current-rockchip64_24.11.0-trunk_arm64__6.6.87-S8146-D0531-P5324-C702eH5c21-HK01ba-Vc222-B59f0-R448a.deb (Reading database ... 78194 files and directories currently installed.) Preparing to unpack linux-headers-current-rockchip64_24.11.0-trunk_arm64__6.6.87-S8146-D0531-P5324-C702eH5c21-HK01ba-Vc222-B59f0-R448a.deb ... Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.6.87-current-rockchip64 ... Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'prerm' finishing. Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' starting. Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'preinst' finishing. Unpacking linux-headers-current-rockchip64 (24.11.0-trunk) over (24.11.0-trunk) ... Setting up linux-headers-current-rockchip64 (24.11.0-trunk) ... Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' starting. Compiling kernel-headers tools (6.6.87-current-rockchip64) using 6 CPUs - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/insert-sys-cert HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s MKELF scripts/mod/elfconfig.h UPD scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/symsearch.o HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers tools (6.6.87-current-rockchip64). Done compiling kernel-headers tools (6.6.87-current-rockchip64). Armbian 'linux-headers-current-rockchip64' for '6.6.87-current-rockchip64': 'postinst' finishing. sudo cp rk3399-kobol-helios64.dtb /boot/dtb/rockchip/ sudo update-initramfs -u

Dear ebin-dev, the rtl_nic firmware from your link are already in /lib/firmware/rtl_nic - anything I should do? the modified dtb for 6.12 are installed already in march - without any changes. Your suggestion should be to downgrade the kernel, but how can I downgrade from actual kernel 6.12.x to your recommended deb-package 6.6.87 without getting into trouble and how I should disable kernel updates?

Today I did also the hardware fix for the 2.5Gbit Port & I can confirm nothing changed concerning the speed: Helios64 -> client around 200Mbit/s Client -> Helios64 2.35Gbit/s but unstable connection compared to 1Gbit Port, the transfer drops The switch monitoring indicates now 1 error. My Conclusion for 2.5Gbit Port: Not usable at all!

If I transfer from Helios64 2.5Gbit Port to a client 2.5Gbit port I'll got a very slow transfer rate (Helios -> client around 200Mbit/s), vice versa full speed, switch is 2.5Gbit (Rj45 ethernet Cat7 cable).Testet with iperf. The switch monitoring indicates always 2 errors. I know about the Hardware issue of Lan-Port2, but it only effect 1Gbit transfer. Nevertheless in the Network are also mixed with 1Gbit clients. Is there anything I'll can try to get full 2.5Gbit speed?

Hello thank you for your efforts, it's very kind from you! I bought an adapter and a Molex PicoBlade with two red and black wire and soldered that to the adapter. The fan works well, but it's only active if the cpu temperature gets up I think 50 degrees Celsius blue (PWM) to (1) and black (GND) to (2) to the two-pin connector It's safer to change this to Yellow +5V -> fan 5V pin1 (Black - GND -> fan pin2) And the fan wouldn't be active all the time and only if the cpu temperature raises to 50 degrees?

I think the easiest way should be just using an external NVMe-Drive and cloning the USB-drive from a X64-PC/Laptop. The other way could be to flash a different boatloader with UEFI-support, but I couldn't find any stable U-Boot.

Thank you going! Yes, I would prefer the 2pin fan connector, but I need to find out getting the right adapter from 4pin Noctua NF-A4x10 5V (black & blue wire to the left & right) to Molex PicoBlade 2pin connector

Thank you for your efforts royk! Sorry, I mention the Opi5 Plus and this is the correct 40pin table (page 233 actual manual) Can someone please help to find the best connection for a 4 Pin PWM Fan (NF-A4x10 5V) to the 40pin interface? Yellow +5V -> 5V -> pin2 or pin4 Black - GND -> pin6 ???? Blue PWM Signal -> pin7 (GPIO_D6 / PWM14_M2 febf0020)

Can someone please help to find the right connection for a 4 Pin PWM Fan (NF-A4x10 5V) to the 40pin interface? Yellow +5V -> 5V -> 1. pin right side Black - GND -> 3rd pin right side Blue PWM Signal -> 6. pin left side GIO04_B2 PWM14_M1 How does I configure wiringOP in this case? Best wishes Greg

Does the Opi5 Plus provide more than 60Hz in 1080p with HDMI 2.1 or USB-C Alt DP-Mode? Is there any possibility to make an image backup of you system (NVme SSD) i.e. CloneZilla Arm64 booting? Are there bootloader images who support USB-Booting? Best wishes Greg

No error anymore, working expected. After restart the fan spins get quiet after a short time :)

Thank you. You just need to exchange this fix here https://github.com/useful64/build/commit/b9f17bdffa24cc3309dc20de487aaa19bb5c481d -> ATTR{name}=="cpu|cpu_thermal", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" is missing above et voila ls -l /dev/thermal-cpu/ total 0 device -> ../../thermal_zone0 subsystem -> ../../../../../class/hwmon temp1_crit temp1_input uevent so the working /etc/udev/rules.d/90-helios64-hwmon.rules looks like # Helios64 persistent hwmon ACTION=="remove", GOTO="helios64_hwmon_end" # KERNELS=="p6-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p6", ENV{_IS_HELIOS64_FAN_}="1", EN> KERNELS=="p7-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p7", ENV{_IS_HELIOS64_FAN_}="1", EN> KERNELS=="2-004c", SUBSYSTEMS=="i2c", DRIVERS=="lm75", ENV{IS_HELIOS64_HWMON}="1" KERNELS=="thermal_zone0", SUBSYSTEMS=="thermal", ENV{IS_HELIOS64_HWMON}="1" SUBSYSTEM!="hwmon|thermal", GOTO="helios64_hwmon_end" ENV{HWMON_PATH}="/sys%p" # ATTR{type}=="soc-thermal", ENV{HWMON_PATH}="/sys%p/temp", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu/t> ATTR{name}=="cpu", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" ATTR{name}=="cpu|cpu_thermal", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" # ENV{IS_HELIOS64_HWMON}=="1", ATTR{name}=="lm75", ENV{HELIOS64_SYMLINK}="/dev/thermal-board" ENV{_IS_HELIOS64_FAN_}=="1", ENV{HELIOS64_SYMLINK}="/dev/fan-$env{_HELIOS64_FAN_}" # ENV{IS_HELIOS64_HWMON}=="1", RUN+="/bin/ln -sf $env{HWMON_PATH} $env{HELIOS64_SYMLINK}" LABEL="helios64_hwmon_end"

Dear allen--smithee, thank you for taking you time! Yes, indeed the service won't start automatic after a reboot status fancontrol.service shows these errors: Error: file /dev/fan-p5/pwm1 doesn't exist Error: file /dev/thermal-cpu/temp1_input doesn't exist Error: file /dev/thermal-cpu/temp1_input doesn't exist I could fix it with sudo ln -s /sys/devices/virtual/thermal/thermal_zone0/hwmon0 /dev/thermal-cpu and then starting the service manual but after a reboot it's gone I don't understand how I can apply it permantent fancontrol.service ● fancontrol.service - fan speed regulator Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/fancontrol.service.d └─pid.conf Active: failed (Result: exit-code) since Fri 2022-09-16 17:53:17 UTC; 4s ago Docs: man:fancontrol(8) man:pwmconfig(8) Process: 3011 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=0/SUCCESS) Process: 3144 ExecStart=/usr/sbin/fancontrol (code=exited, status=1/FAILURE) Main PID: 3144 (code=exited, status=1/FAILURE) CPU: 1.362s Sep 16 17:53:17 helios64 fancontrol[3144]: AVERAGE=1 Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/fan-p5/pwm1 doesn't exist Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/thermal-cpu/temp1_input doesn't exist Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/thermal-cpu/temp1_input doesn't exist Sep 16 17:53:17 helios64 fancontrol[3144]: At least one referenced file is missing. Either some req> Sep 16 17:53:17 helios64 fancontrol[3144]: modules haven't been loaded, or your configuration file > Sep 16 17:53:17 helios64 fancontrol[3144]: In the latter case, you should run pwmconfig again. Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Main process exited, code=exited, status=1> Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Failed with result 'exit-code'. Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Consumed 1.362s CPU time. lines 1-22/22 (END) s -l /sys/class/hwmon | grep fan lrwxrwxrwx 1 root root 0 Sep 16 17:55 hwmon4 -> ../../devices/platform/p7-fan/hwmon/hwmon4 lrwxrwxrwx 1 root root 0 Sep 16 17:51 hwmon5 -> ../../devices/platform/p6-fan/hwmon/hwmon5 ls -l /etc/udev/rules.d/ total 56 -rw-r--r-- 1 root root 70 Nov 19 2020 10-wifi-disable-powermanagement.rules -rw-r--r-- 1 root root 45 Feb 3 2021 50-mali.rules -rw-r--r-- 1 root root 138 Feb 3 2021 50-rk3399-vpu.rules -rw-r--r-- 1 root root 3132 Feb 3 2021 50-usb-realtek-net.rules -rw-r--r-- 1 root root 20275 Aug 31 20:17 61-openmediavault-dev-disk-by-id.rules -rw-r--r-- 1 root root 79 Feb 3 2021 70-keep-usb-lan-as-eth1.rules -rw-r--r-- 1 root root 866 Feb 3 2021 90-helios64-hwmon.rules -rw-r--r-- 1 root root 424 Feb 3 2021 90-helios64-ups.rules -rw-r--r-- 1 root root 1348 Jan 20 2022 99-openmediavault-md-raid.rules -rw-r--r-- 1 root root 1647 Jan 20 2022 99-openmediavault-nonrot.rules cat /etc/udev/rules.d/90-helios64-hwmon.rules # Helios64 persistent hwmon ACTION=="remove", GOTO="helios64_hwmon_end" # KERNELS=="p6-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p6", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1" KERNELS=="p7-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p7", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1" KERNELS=="2-004c", SUBSYSTEMS=="i2c", DRIVERS=="lm75", ENV{IS_HELIOS64_HWMON}="1" SUBSYSTEM!="hwmon", GOTO="helios64_hwmon_end" ENV{HWMON_PATH}="/sys%p" # ATTR{name}=="cpu", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" # ENV{IS_HELIOS64_HWMON}=="1", ATTR{name}=="lm75", ENV{HELIOS64_SYMLINK}="/dev/thermal-board" ENV{_IS_HELIOS64_FAN_}=="1", ENV{HELIOS64_SYMLINK}="/dev/fan-$env{_HELIOS64_FAN_}" # ENV{IS_HELIOS64_HWMON}=="1", RUN+="/bin/ln -sf $env{HWMON_PATH} $env{HELIOS64_SYMLINK}" LABEL="helios64_hwmon_end" ls -l /dev/thermal-cpu/ ls: cannot access '/dev/thermal-cpu/': No such file or directory /usr/sbin/pwmconfig: There are no fan-capable sensor modules installed

I just use the Usb-backup plugin. I tried the upgrade but had some errors which I couldn't solve ending up in installing the latest bullseye image from here https://armbian.hosthatch.com/archive/helios64/archive/ first to SD then to eMMC and then the system to a SSD while booting from eMMC - which works now really good again with having actual OMV6. The only trouble is that I won't get the fan quiet Thank you allen--smithee for your modification which doesn't work for me, sorry! I can only manual set it quiet with Daniel Helios64 commands echo 70 > /sys/class/hwmon/hwmon5/pwm1 echo 70 > /sys/class/hwmon/hwmon6/pwm1

Is there any way to lower the fans permanently also after a reboot maybe in /etc/fancontrol?

Thank you for your input! It would be really nice to collect some experience concerning the upgrade in this thread!

Dear Forum, I am using a Helios64 with armbian Debian 10 (Buster) Linux-Kernel 5.15.52 and OMV 5.6.26-1. If I want to have further Updates from OMV I need to upgrade to Debian 11, because OMV6 isn't compatible to Buster. Any recomendations how I should upgrade? The H64-System is on a SDD. Should I try a cli system upgrade or installing everything new with a bullseye image, if this is available (Where?)? Best wishes, Greg