In the latest version, the developer has introduced features to measure recently released hardware component performance. Having said that, it's a good tool to keep your PC running at peak performance. Since you don’t need to pay a penny for SpeedFan download, the program offers basic functionality. SpeedFan is a useful utility tool, which lets you assess the computer’s health and performance without much effort. # in config/sources/families/include/rockchip64_common.incģ96 # copy hwmon rules to fix device mappingģ98 install -m 644 $SRC/packages/bsp/helios64/les $destination/etc/udev/rules.d/Ĥ00 install -m 644 $SRC/packages/bsp/helios64/les $destination/etc/udev/rules.Controls fan speed and monitors performance I tried reversing the build system to find why the old file was used instead of the other, but the best I could find is The content of the les is indeed correct and match the 5.10.x kernel device tree: Run: '/bin/ln -sf /sys/devices/virtual/thermal/thermal_zone0/temp /dev/thermal-cpu/temp1_input'Īpparently for some reason the device-tree changed upstream and the thermal type changed from soc-thermal to cpu?įor anybody passing by, the issue is due to the fact that for some reason the armbian-bsp-cli-helios64 package for 21.05.2 (EDIT: clarify, 21.05.1 is fine as seen below) was build with the old udev rule (for 4.4 kernels): HELIOS64_SYMLINK=/dev/thermal-cpu/temp1_input HWMON_PATH=/sys/devices/virtual/thermal/thermal_zone0/temp Run: '/bin/ln -sf /sys/devices/virtual/thermal/thermal_zone0 ' <- something is wrong here, there is no targetĪfter spending a bit more time reading the udev rule, I realized that the second argument was empty because we don't match the ATTR="/dev/thermal-cpu/temp1_input", RUN+="/usr/bin/mkdir # udevadm control # udevadm test /sys/devices/virtual/thermal/thermal_zone0 HWMON_PATH=/sys/devices/virtual/thermal/thermal_zone0 Reading rules file: /etc/udev/rules.d/lesĭEVPATH=/devices/virtual/thermal/thermal_zone0 Reading rules file: /etc/udev/rules.d/les After reading the rule in /etc/udev/rules.d/les and a bit of udev documentation, I managed to find how to test # udevadm test /sys/devices/virtual/thermal/thermal_zone0 Now digging more this issue happen because udev is not creating the symlink like it should for some reason. Ln -s /sys/devices/virtual/thermal/thermal_zone0/temp /dev/thermal-cpu/temp1_input After a bit of poking around and learning about udev, I managed to manually solve the issue by recreating the device symlink manually: May 28 00:08:13 helios64 systemd: rvice: Failed with result 'exit-code'.īasically fancontrol expect a device in /dev to read the sensors value from, and that device seems to be missing. May 28 00:08:13 helios64 systemd: rvice: Main process exited, code=exited, status=1/FAILURE May 28 00:08:13 helios64 fancontrol: In the latter case, you should run pwmconfig again. May 28 00:08:13 helios64 fancontrol: modules haven't been loaded, or your configuration file is outdated. May 28 00:08:13 helios64 fancontrol: At least one referenced file is missing. May 28 00:08:13 helios64 fancontrol: Error: file /dev/thermal-cpu/temp1_input doesn't exist Main PID: 2876 (code=exited, status=1/FAILURE) Process: 2876 ExecStart=/usr/sbin/fancontrol (code=exited, status=1/FAILURE) Process: 2495 ExecStartPre=/usr/sbin/fancontrol -check (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)ĭrop-In: /etc/systemd/system/Īctive: failed (Result: exit-code) since Fri 00:08:13 CEST 1min 42s ago Posting here following what was recommended on twitter.Īfter updating my helios64 earlier this week and rebooting to get the new kernel, I realized it was suspiciously silent.Ī quick check to sensor temps readings and physical check made me realize the fan were not spinning.Īfter a quick read on the wiki, I checked fancontrol which was indeed # systemctl status rvice
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |