void-linux / void-linux/void-packages
Thermald tanks performance on ASUS UX3402Z. Need to use --adaptive
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.5.2_1 x86_64 GenuineIntel notuptodate FFF
Package(s) Affected
thermald-2.5.4_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
thermald is not supposed to affect performance this much.
Actual behaviour
Hello, I've encountered an issue with thermald, I don't know if we could really call this a bug but thermald needs some ACPI info about max temperatures on newer laptops/ultrabooks.
The ACPI info was not read, so on my laptop thermald would throttle heavily (cf. https://www.reddit.com/r/voidlinux/comments/16gtkl5/whole_system_slower_with_dbus_service/?utm_source=share&utm_medium=web2x&context=3)
Upstream people have added the "--adaptive" option to thermald. I simply added this option in the runit run file.
Up to you to decide if this should be distributed on void-packages.
The thermald help does say "adaptive mode: use adaptive performance tables if available", so it shouldn't affect users who miss it.
Should we add this option ?
Steps to reproduce
Hardware specific bug
enable dbus service
enable thermald service
lower performances.
enable dbus service
enable thermald service with --adaptive
no performance issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the thermald runit run file and compare the service command with the reported --adaptive invocation. Test thermald with and without that option on the affected setup; done means the service uses adaptive mode and no longer causes the reported performance loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100