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: Mon, 10 Aug 2020 00:26:44 +0000	[thread overview]
Message-ID: <bug-201539-2300-PX4zkAy0on@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 #56 from Sean Birkholz (supasean@hotmail.com) ---
I was going to try and get a fancontrol script working, but I found the
following as I started to play around:

I got my results on Arch Linux's 5.7.12-arch1-1 kernel.  

On boot pwm1_enable is set to 1 (manual mode).  On 4.18.x it is normally set to
2 (automatic mode) iirc.  Changing this value to 2 does essentially nothing for
me and the fans do not spin up with increasing temp.  

However, I've found that running pwmconfig and not even answering the first
question (ie; I can just ctrl+c out) causes the automatic temp control to start
functioning.  So after you run pwmconfig, then change pwm1_enable to 2 and
everything works again.  So far it appears doing these two things gets me the
same functionality I had on 4.18.x and I can finally upgrade my kernel.  No fan
control script needed.

It is interesting to note, if you do these in the opposite order; set
pwm1_enable to 2 and then run pwmconfig, you must say yes to enabling manual
mode on the gpu's fan before they start functioning properly.  This also causes
the fan to run full speed (like pwm1_enable is set to 0) and you will need to
set 2 in pwm1_enable again.

I dont know what pwmconfig is modifying to cause pwm to work again... I wish i
knew so I could set that up with a script and not have to manually start it,
but this is good enough for now as I reboot rarely.  Maybe I can make a script
to use with systemctl when I'm not lazy.

-- 
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:[~2020-08-10  0:26 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
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 [this message]
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-PX4zkAy0on@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).