Jump to content
XPEnology Community

Trauma

Member
  • Posts

    46
  • Joined

  • Last visited

  • Days Won

    6

Trauma last won the day on August 31 2022

Trauma had the most liked content!

1 Follower

Recent Profile Visitors

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

Trauma's Achievements

Junior Member

Junior Member (2/7)

26

Reputation

  1. Nice work, though it could have been cool to open a PR on my repo
  2. Most of the time hard drives are way more power hungry than one CPU on this type of setup. You're PSU efficiency is also important, a 500w 80+ Power Supply can drain around 50w without any load. So in this case scaling down the CPU is more a matter of temperature management IMHO.
  3. What the load of your cpu looks like ? And did you used custom midload/maxload ?
  4. Since i can not explain why your sensor id do not start @ 1 and since you seems to be the only one with this issue. I'll recommend you to mod the script before installation. Just change : currtemp=$(cat /sys/bus/platform/devices/coretemp.0/hwmon/hwmon0/temp1_input) maxtemp=$(cat /sys/bus/platform/devices/coretemp.0/hwmon/hwmon0/temp1_max) to currtemp=$(cat /sys/bus/platform/devices/coretemp.0/hwmon/hwmon0/temp2_input) maxtemp=$(cat /sys/bus/platform/devices/coretemp.0/hwmon/hwmon0/temp2_max) And launch the install.sh
  5. This is your problem, to help you out i'll need to know what are your syno model, DSM version and CPU model.
  6. Bug fixed, please try to update and reinstall, should work.
  7. The script think you're cpu is at 430°, so it enter in the cooling mode and set the cpu frequency at 1800 Hz. Its a bug related with the max temp, I'll fix this.
  8. Download the archive : https://github.com/Trauma/cpufreq-userspace-scaler/archive/refs/heads/master.zip Extract the archive copy the files to your nas ssh to your nas cd path/to/cpufreq-userspace-scaler-master sudo ./install.sh
  9. Seems to work fine so ? Maybe you did not install it correctly..
  10. Ok, thanks. So the new cpucorecount method works for you too, since it return 7 and you can see that you have /sys/devices/system/cpu/cpu0 to /sys/devices/system/cpu/cpu7 which is fine. FYI `awk '{ print $1 - 1 }'` means `print the first field of the previous command minus 1` Since nproc return 8 for you, and since /sys/devices/system/cpu/cpu0 start at 0 we need to remove one core form the count to obtain the right value (7 for you). This to said that you first experiments were totally hazardous, and I can not explain why it worked for you. If you want me to help further, please run the latest version of the script with `bash -x ./scaler.sh` and paste the output here (no screenshots please). Cheers.
  11. @burtal it seems like cpucorecount is not set properly for you. can you give me the output of those commands please : nproc | awk '{ print $1 - 1 }' and grep cores /proc/cpuinfo | sort -u | awk '{ print $4 - 1 }' and grep cores /proc/cpuinfo | sort -u | awk '{ print $7 - 1 }' and ls -l /sys/devices/system/cpu/
  12. @use-nas and @burtal this version should fix your respective issues : https://github.com/Trauma/cpufreq-userspace-scaler/tree/fix/celeron_temp Let me know.
  13. The complete and correct cpucorecount command should be : cpucorecount=$(nproc | awk '{ print $1 - 1 }') If it return the right value, the same method can be used for lowload etc..
  14. Try to use this please : cpucorecount=$(nproc) I've tested this successfully on my config, i think it should work for hyperthreaded and standard threaded CPU's
  15. Please provide me the output of this command please : sudo dmidecode --type processor
×
×
  • Create New...