pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[borisnet]

@pastrychef
I investigated a bit and I got the following GPU temperature vs fan behaviour - not entirely wrong but would like the fan to run maybe at lower speed to avoid the bump of speed which becomes very audible.

Fan not running:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=49

Temperature increases - Fan still not running:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=57

Temperature reached 58 and triggered the fan:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=56
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=1834
"Temperature(C)"=58

Fan does it job - temperature comes back down:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=56
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=2256
"Temperature(C)"=51

Temperature reaches 50 and fan stops:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=50

I am just wondering whether there is a way to force the GPU fan to run at lower speed like 30% speed constantly to avoid the on/off under this short amplitude of temperature.

 

[pastrychef]

@pastrychef
I investigated a bit and I got the following GPU temperature vs fan behaviour - not entirely wrong but would like the fan to run maybe at lower speed to avoid the bump of speed which becomes very audible.

Fan not running:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=49

Temperature increases - Fan still not running:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=57

Temperature reached 58 and triggered the fan:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=56
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=1834
"Temperature(C)"=58

Fan does it job - temperature comes back down:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=56
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=2256
"Temperature(C)"=51

Temperature reaches 50 and fan stops:

ioreg -l | grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock';
"Fan Speed(%)"=0
"Core Clock(MHz)"=1340
"Memory Clock(MHz)"=2000
"Fan Speed(RPM)"=0
"Temperature(C)"=50

I am just wondering whether there is a way to force the GPU fan to run at lower speed like 30% speed constantly to avoid the on/off under this short amplitude of temperature.

I don't know of a way to manipulate the fan on any video cards other than the Vega cards.

 

[borisnet]

I don't know of a way to manipulate the fan on any video cards other than the Vega cards.

How do you do that on the Vega cards? That might give me some inspiration ;-)

 

[pastrychef]

How do you do that on the Vega cards? That might give me some inspiration ;-)

On Vega cards, we use an app called VGTab. It generates a kext that contains the power tables for the Vegas. You can find a copy of VGTab attached to post #1.

 

[pentaflex]

Try changing audio-id to 1 to see if it makes a difference.

Thanks for the suggestion, but unfortunately it had no effect. Any other ideas?

 

[pastrychef]

Thanks for the suggestion, but unfortunately it had no effect. Any other ideas?

Are you using the latest Lilu/AppleALC/WhateverGreen? You can also try audio-id 7.

 

[pentaflex]

No joy with audio-id 7 either. The issue does not seem to be related to this, as all values work fine until after sleep. (Curious, where are you getting these numbers?)

I'm also curious why the issue started after the 10.14.4 update. I may research that more. Fortunately this is an annoyance, not a show stopper.

I've never done anything special with Lilu/AppleALC/WhateverGreen. My config simply uses your EFI from post #1, unaltered, other than serial # etc. (I use iMac18,3.)

 

[pastrychef]

No joy with audio-id 7 either. The issue does not seem to be related to this, as all values work fine until after sleep. (Curious, where are you getting these numbers?)

I'm also curious why the issue started after the 10.14.4 update. I may research that more. Fortunately this is an annoyance, not a show stopper.

I've never done anything special with Lilu/AppleALC/WhateverGreen. My config simply uses your EFI from post #1, unaltered, other than serial # etc. (I use iMac18,3.)

These are the values listed in the AppleALC supported codecs page.

I have not had any issues with audio and/or sleep with 10.14.4.

Please try to update to the latest Lilu/AppleALC/WhateverGreen. They are located in /EFI/CLOVER/kexts/Other/. The latest AppleALC does have a fix for some sleep situations.

 

[pastrychef]

I've been using the iMac19,1 system definition with the latest EFI folder since yesterday and everything seems solid. Please keep in mind that I am using the special 18E2034 build of macOS that ships with the latest iMacs.

 

[corint1]

@pastrychef
the new clover ... what do you say about that?