dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20/5.0
Date: Fri, 06 Dec 2019 05:01:57 +0000	[thread overview]
Message-ID: <bug-201539-2300-HCicgltcFG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201539-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201539

--- Comment #42 from muncrief (rmuncrief@humanavance.com) ---
(In reply to MasterCATZ from comment #41)
> aio@aio:/usr/local/bin$ sudo systemctl status amdgpu-fancontrol
> ● amdgpu-fancontrol.service - amdgpu-fancontrol
>    Loaded: loaded (/etc/systemd/system/amdgpu-fancontrol.service; enabled;
> vendor preset: enabled)
>    Active: active (running) since Fri 2019-12-06 14:45:07 AEST; 3s ago
>  Main PID: 23922 (amdgpu-fancontr)
>     Tasks: 2 (limit: 4915)
>    Memory: 3.3M
>    CGroup: /system.slice/amdgpu-fancontrol.service
>            ├─23922 /bin/bash /usr/local/bin/amdgpu-fancontrol
>            └─23979 sleep 1
> 
> Dec 06 14:45:08 aio amdgpu-fancontrol[23922]: changing pwm to 175
> Dec 06 14:45:08 aio amdgpu-fancontrol[23922]:
> /usr/local/bin/amdgpu-fancontrol: line 65: echo: write error: Invalid
> argument
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: current temp: 62000
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: interpolated pwm value for
> temperature 62000 is: 175
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: current pwm: 104, requested to
> set pwm to 175
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: Fanmode not set to manual.
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: setting fan mode to 1
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: temp at last change was 62000
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]: changing pwm to 175
> Dec 06 14:45:09 aio amdgpu-fancontrol[23922]:
> /usr/local/bin/amdgpu-fancontrol: line 65: echo: write error: Invalid
> argument

I was about to call it a day when I got your email notifications. The line it's
talking about is:

echo "$NEW_PWM" > "$FILE_PWM"

So it looks like the "$FILE_PWM" variable is not valid. Remember, you have to
change the variables under the comment "hwmon paths, hardcoded for one amdgpu
card, adjust as needed" to whatever your system requires. To debug the
variables I would execute the 4 lines that set HWMON, FILE_PWM, FILE_FANMODE,
and FILE_TEMP from terminal and see where things are going wrong. I have to go
now but I'll try to help you more tomorrow if you're still having problems. But
once you have those variables set correctly the script should work. Here's what
the service status output looks like on my system:

   Loaded: loaded (/etc/systemd/system/amdgpu-fancontrol.service; enabled;
vendor preset: disabled)
   Active: active (running) since Thu 2019-12-05 18:16:27 PST; 2h 28min ago
 Main PID: 836 (amdgpu-fancontr)
    Tasks: 2 (limit: 4915)
   Memory: 7.7M
   CGroup: /system.slice/amdgpu-fancontrol.service
           ├─  836 /bin/bash /usr/local/bin/amdgpu-fancontrol
           └─14235 sleep 1

Dec 05 20:44:46 Entropod amdgpu-fancontrol[836]: changing pwm to 80
Dec 05 20:44:47 Entropod amdgpu-fancontrol[836]: current temp: 49000
Dec 05 20:44:47 Entropod amdgpu-fancontrol[836]: interpolated pwm value for
temperature 49000 is: 90
Dec 05 20:44:47 Entropod amdgpu-fancontrol[836]: current pwm: 76, requested to
set pwm to 90
Dec 05 20:44:47 Entropod amdgpu-fancontrol[836]: temp at last change was 48000
Dec 05 20:44:47 Entropod amdgpu-fancontrol[836]: changing pwm to 90
Dec 05 20:44:48 Entropod amdgpu-fancontrol[836]: current temp: 48000
Dec 05 20:44:48 Entropod amdgpu-fancontrol[836]: interpolated pwm value for
temperature 48000 is: 80
Dec 05 20:44:48 Entropod amdgpu-fancontrol[836]: current pwm: 86, requested to
set pwm to 80
Dec 05 20:44:48 Entropod amdgpu-fancontrol[836]: not changing pwm, we just did
at 49000, next change when below 43000

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-12-06  5:02 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 12:32 [Bug 201539] New: AMDGPU R9 390 automatic fan speed control in Linux 4.19 bugzilla-daemon
2018-10-27 12:34 ` [Bug 201539] " bugzilla-daemon
2018-10-27 12:35 ` bugzilla-daemon
2018-10-27 12:45 ` bugzilla-daemon
2018-12-08  7:59 ` bugzilla-daemon
2018-12-21  1:30 ` bugzilla-daemon
2018-12-21  2:16 ` bugzilla-daemon
2018-12-21 15:06 ` bugzilla-daemon
2018-12-21 15:56 ` bugzilla-daemon
2018-12-24 11:55 ` [Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20 bugzilla-daemon
2018-12-24 11:55 ` bugzilla-daemon
2018-12-31  9:06 ` bugzilla-daemon
2019-01-05 13:41 ` bugzilla-daemon
2019-03-04  2:17 ` [Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20/5.0 bugzilla-daemon
2019-03-09  2:44 ` bugzilla-daemon
2019-04-17 10:37 ` bugzilla-daemon
2019-06-06 11:18 ` bugzilla-daemon
2019-06-06 11:44 ` bugzilla-daemon
2019-06-06 12:18 ` bugzilla-daemon
2019-06-07  1:41 ` bugzilla-daemon
2019-06-18 17:42 ` bugzilla-daemon
2019-06-24  2:18 ` bugzilla-daemon
2019-10-05 13:19 ` bugzilla-daemon
2019-11-03  4:08 ` bugzilla-daemon
2019-11-03  4:16 ` bugzilla-daemon
2019-11-03  4:29 ` bugzilla-daemon
2019-11-03  4:37 ` bugzilla-daemon
2019-11-05 23:47 ` bugzilla-daemon
2019-11-06  9:35 ` bugzilla-daemon
2019-11-16  0:42 ` bugzilla-daemon
2019-11-16  0:57 ` bugzilla-daemon
2019-11-16 12:07 ` bugzilla-daemon
2019-11-16 13:36 ` bugzilla-daemon
2019-11-16 14:15 ` bugzilla-daemon
2019-11-16 22:35 ` bugzilla-daemon
2019-11-17  0:43 ` bugzilla-daemon
2019-11-17  7:46 ` bugzilla-daemon
2019-12-05 17:00 ` bugzilla-daemon
2019-12-06  2:58 ` bugzilla-daemon
2019-12-06  3:04 ` bugzilla-daemon
2019-12-06  3:22 ` bugzilla-daemon
2019-12-06  4:30 ` bugzilla-daemon
2019-12-06  4:32 ` bugzilla-daemon
2019-12-06  4:45 ` bugzilla-daemon
2019-12-06  5:01 ` bugzilla-daemon [this message]
2019-12-06  5:52 ` bugzilla-daemon
2019-12-06  5:56 ` bugzilla-daemon
2019-12-07 19:48 ` bugzilla-daemon
2019-12-07 20:05 ` bugzilla-daemon
2019-12-07 20:20 ` bugzilla-daemon
2019-12-07 20:46 ` bugzilla-daemon
2019-12-07 21:04 ` bugzilla-daemon
2019-12-09  0:33 ` bugzilla-daemon
2019-12-09  0:55 ` bugzilla-daemon
2019-12-09 21:26 ` bugzilla-daemon
2019-12-10  1:03 ` bugzilla-daemon
2020-05-21 15:31 ` bugzilla-daemon
2020-06-03  8:26 ` bugzilla-daemon
2020-08-10  0:26 ` bugzilla-daemon
2020-12-01 21:54 ` bugzilla-daemon
2020-12-01 21:57 ` bugzilla-daemon
2020-12-01 22:47 ` bugzilla-daemon
2020-12-01 23:01 ` bugzilla-daemon
2020-12-02  1:33 ` bugzilla-daemon
2020-12-02  3:30 ` bugzilla-daemon
2020-12-02  3:34 ` bugzilla-daemon
2020-12-02  8:38 ` bugzilla-daemon
2020-12-02  9:57 ` bugzilla-daemon
2020-12-02 16:21 ` bugzilla-daemon
2020-12-02 19:31 ` bugzilla-daemon
2020-12-02 20:16 ` bugzilla-daemon
2020-12-02 21:11 ` bugzilla-daemon
2020-12-03  1:04 ` bugzilla-daemon
2020-12-13 23:56 ` bugzilla-daemon
2020-12-14 23:05 ` bugzilla-daemon
2020-12-14 23:26 ` bugzilla-daemon
2020-12-14 23:44 ` bugzilla-daemon
2021-02-06  5:34 ` bugzilla-daemon
2022-02-05 21:59 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-201539-2300-HCicgltcFG@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).