[SOLVED] GPU fans not spinning, and how to run GPU stress test

Arct1c_f0x · 07-26-2020, 08:03 PM

Nothing is wrong with my AMD Gigabyte GPU but I noticed that it's fans are not spinning (three fan GPU) although they do start spinning when I power on my tower. I pretty certain that this is because the GPU is in a special mode where the fans don't start spinning until the GPU reaches a certain temp.

Is there any way to make the fans run automatically when the desktop is on? Or would I not want to do that?

2nd question.
What's the best way in your opinion to run a diagnostic GPU stress test? I just want to know how for my own personal edification (There's nothing wrong with my brand new GPU)

Thanks in advance!

scasey · 07-26-2020, 08:26 PM

It sounds like you’re saying the fans don’t spin when the power is off...???

I would expect the fans to only run when they’re needed.
Gotta say: “If it ain’t broke, don’t fix it.”

EdGr · 07-26-2020, 08:56 PM

Since you have a new GPU, check the kernel messages to make sure that the kernel recognizes it and loads the firmware. Then, check Xorg.0.log to make sure that X recognizes the GPU and enables acceleration.

For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:

for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done

Three glblurs can max out my six-year-old GPU at 4K.
Ed

Arct1c_f0x · 07-27-2020, 06:32 AM

Quote:

Originally Posted by scasey

It sounds like you’re saying the fans don’t spin when the power is off...???

I would expect the fans to only run when they’re needed.
Gotta say: “If it ain’t broke, don’t fix it.”

Sorry for the confusion. At first when I turn my tower on the fans power on, but then immediately after that anything I do and they don't spin.

ondoho · 07-27-2020, 06:43 AM

Stress test the GPU - play some games?
IF they use the GPU at all. 'glxinfo' can tell you if that's possible.

Possibly also 'sensors'detect' and 'sensors'.
Read all these commands' man pages before asking about their usage.

verndog · 07-27-2020, 10:32 AM

There's a tool called 'stress'. From debian based, just

Code:

sudo apt install stress

. Then run something like this

Quote:

stress -c 1 -t 10

from command line.

obobskivich · 07-27-2020, 02:06 PM

Quote:

Originally Posted by Arct1c_f0x

Sorry for the confusion. At first when I turn my tower on the fans power on, but then immediately after that anything I do and they don't spin.

This is normal/designed behavior on newer GPUs (going back at least a few years now - for example my GeForce 1080 does this, and is 2-3 years old, but my Radeon 290X does not, and is a year or two older than that) - you are exactly right, the fan is set to be 'off' unless the GPU hits a pre-defined temperature (usually 40-50* C). Nothing is wrong with operating this way, and this behavior is provided by the card's firmware. It is possible to override this either by A) connecting the fans directly to the computer's power supply (and they will just run all the time, at maximum speed) or B) software. On linux I'm not sure exactly what that software package is, but on Windows you would use something like Afterburner (which is based on Rivatuner) to set a manual fan-curve - this would only apply AFTER the system had booted up and the software was running (in other words, the software is over-riding the card's firmware behavior, not changing it). In general, I would just accept the default behavior, because it is set with sane values - the GPU is not in danger at lower temperatures, and the fans should be spinning up at higher temperatures (and with 3 separate fans, the odds that something is just 'blocking' the fan from spinning are low - if this was a single fan card I would tell you to check and make sure something isn't sticking the fan in place (e.g. like it sucked up a ziptie or something)).

A quick web search found this thread on another forum about 'Afterburner alternatives on linux' that you might find interesting/helpful: https://linustechtips.com/main/topic...tive-on-linux/

Finally, if you want to see the GPU's temperature and fan RPM, psensor (which is basically a nice GUI application to get the same info 'sensors' will provide, as ondoho suggests) should be able to do that for you. This way you can confirm the GPU is indeed under some temperature threshold (for example my newer GeForce card does this, and the fan stays off under 50* C, and only comes on to about 900 RPM under 60* C), and not actually overheating (on a modern GPU that would generally be >90* C).

For loading the GPU up, I agree with the other suggestions - run a 3D game or some other 3D application (like the screensaver suggestion from EdGr is a good one). A lot of 'GPU stress test' applications (like Furmark) are strongly counterindicated by nVidia/AMD as they can create a significant amount of heat for the GPU, which can lead to thermal stress on the board, and/or premature failure (not to mention how much power it wastes).

Arct1c_f0x · 07-27-2020, 03:22 PM

Quote:

Originally Posted by EdGr

Since you have a new GPU, check the kernel messages to make sure that the kernel recognizes it and loads the firmware. Then, check Xorg.0.log to make sure that X recognizes the GPU and enables acceleration.

For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:

for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done

Three glblurs can max out my six-year-old GPU at 4K.
Ed

I'm still pretty new to this. Do you mean check the Kernel messages when the system first boots up? And what is the Xorg.0.log and how do I check it?

when I type the sensors command this is what shows up:

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +28.0°C

On my other system when I type 'sensors' into a terminal is says amdgpu and then describes all this information about the GPU

Thanks Ed

Arct1c_f0x · 07-27-2020, 03:25 PM

Quote:

Originally Posted by obobskivich

This is normal/designed behavior on newer GPUs (going back at least a few years now - for example my GeForce 1080 does this, and is 2-3 years old, but my Radeon 290X does not, and is a year or two older than that) - you are exactly right, the fan is set to be 'off' unless the GPU hits a pre-defined temperature (usually 40-50* C). Nothing is wrong with operating this way, and this behavior is provided by the card's firmware. It is possible to override this either by A) connecting the fans directly to the computer's power supply (and they will just run all the time, at maximum speed) or B) software. On linux I'm not sure exactly what that software package is, but on Windows you would use something like Afterburner (which is based on Rivatuner) to set a manual fan-curve - this would only apply AFTER the system had booted up and the software was running (in other words, the software is over-riding the card's firmware behavior, not changing it). In general, I would just accept the default behavior, because it is set with sane values - the GPU is not in danger at lower temperatures, and the fans should be spinning up at higher temperatures (and with 3 separate fans, the odds that something is just 'blocking' the fan from spinning are low - if this was a single fan card I would tell you to check and make sure something isn't sticking the fan in place (e.g. like it sucked up a ziptie or something)).

A quick web search found this thread on another forum about 'Afterburner alternatives on linux' that you might find interesting/helpful: https://linustechtips.com/main/topic...tive-on-linux/

Finally, if you want to see the GPU's temperature and fan RPM, psensor (which is basically a nice GUI application to get the same info 'sensors' will provide, as ondoho suggests) should be able to do that for you. This way you can confirm the GPU is indeed under some temperature threshold (for example my newer GeForce card does this, and the fan stays off under 50* C, and only comes on to about 900 RPM under 60* C), and not actually overheating (on a modern GPU that would generally be >90* C).

For loading the GPU up, I agree with the other suggestions - run a 3D game or some other 3D application (like the screensaver suggestion from EdGr is a good one). A lot of 'GPU stress test' applications (like Furmark) are strongly counterindicated by nVidia/AMD as they can create a significant amount of heat for the GPU, which can lead to thermal stress on the board, and/or premature failure (not to mention how much power it wastes).

Thanks a lot obobskivich! You made a lot of useful information plain and concise! I appreciate it and I gave you some rep

ondoho · 07-27-2020, 04:25 PM

Quote:

Originally Posted by verndog

There's a tool called 'stress'. From debian based, just

Code:

sudo apt install stress

. Then run something like this from command line.

If OP's concern is really about the GPU and its fan only, then stressing the CPU is pointless.
Although it could indirectly help troubleshoot the issue.

Quote:

Originally Posted by EdGr

For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:

for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done

Nice idea, haven't noticed it before!

EdGr · 07-27-2020, 06:09 PM

Quote:

Originally Posted by Arct1c_f0x

I'm still pretty new to this. Do you mean check the Kernel messages when the system first boots up? And what is the Xorg.0.log and how do I check it?

As root, do:

Code:

dmesg | less

You should see lines like:

Code:

[   11.739473] [drm] radeon kernel modesetting enabled.
...
[   11.743892] [drm] radeon: 2048M of VRAM memory ready
[   11.743894] [drm] radeon: 2048M of GTT memory ready.
[   11.743902] [drm] Loading pitcairn Microcode
[   11.921961] [drm] Internal thermal controller with fan control

In /var/log/Xorg.0.log, you should see lines like:

Code:

[    51.092] (--) RADEON(0): Chipset: "PITCAIRN" (ChipID = 0x6819)
...
[    52.547] (II) RADEON(0): glamor X acceleration enabled on AMD PITCAIRN (DRM 2.50.0, 5.4.51, LLVM 10.0.0)

Quote:

Originally Posted by ondoho

Nice idea, haven't noticed it before!

Thanks! I find that glblur is good for testing GPUs and inducing vertigo.

Ed

Arct1c_f0x · 07-27-2020, 06:32 PM

Quote:

Originally Posted by EdGr

As root, do:

Code:

dmesg | less

You should see lines like:

Code:

[   11.739473] [drm] radeon kernel modesetting enabled.
...
[   11.743892] [drm] radeon: 2048M of VRAM memory ready
[   11.743894] [drm] radeon: 2048M of GTT memory ready.
[   11.743902] [drm] Loading pitcairn Microcode
[   11.921961] [drm] Internal thermal controller with fan control

In /var/log/Xorg.0.log, you should see lines like:

Code:

[    51.092] (--) RADEON(0): Chipset: "PITCAIRN" (ChipID = 0x6819)
...
[    52.547] (II) RADEON(0): glamor X acceleration enabled on AMD PITCAIRN (DRM 2.50.0, 5.4.51, LLVM 10.0.0)

Thanks! I find that glblur is good for testing GPUs and inducing vertigo.

Ed

Yeah I want to say that it's definitely not recognizing my GPU for what it is

When i do

Quote:

sudo dmesg | grep -i vga or I type dmesg | grep -i GPU or AMDGPU

Nothing shows up and i've gone through almost every line now and nothing seems to ackowledge my graphics card.

I started up a pc game 'Warband mount and Blade' on steam on this desktop and it ran really really poorly (and warband is not a super graphics intensive game.) I mean obviously my graphics card is working because I have my monitor plugged into it (display port at 1080p) but I think it's running at a stunted level of performance.

Further more when I type sensors in the terminal this is what I get

Quote:

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +47.0°C

I'm downloading AOEII now on steam to try and play that so we'll see. Any deal what the problem is?

EdGr · 07-27-2020, 06:53 PM

Quote:

Originally Posted by Arct1c_f0x

Yeah I want to say that it's definitely not recognizing my GPU for what it is

When i do

Nothing shows up and i've gone through almost every line now and nothing seems to ackowledge my graphics card.

I started up a pc game 'Warband mount and Blade' on steam on this desktop and it ran really really poorly (and warband is not a super graphics intensive game.) I mean obviously my graphics card is working because I have my monitor plugged into it (display port at 1080p) but I think it's running at a stunted level of performance.

You are in for an OS upgrade. You want a very recent OS to support your GPU.

Alternatively, you can install AMD's proprietary driver as a stopgap measure until the open-source drivers have caught up.
Ed

Arct1c_f0x · 07-27-2020, 08:56 PM

Quote:

Originally Posted by EdGr

You are in for an OS upgrade. You want a very recent OS to support your GPU.

Alternatively, you can install AMD's proprietary driver as a stopgap measure until the open-source drivers have caught up.
Ed

That's awesome thanks, Ed! I have pretty much the newest Debian buster version - Debian Buster AMD 64 10.4

This is my graphics card:
https://www.newegg.com/gigabyte-rade...82E16814932236

GIGABYTE Radeon RX 5500 XT DirectX 12 GV-R55XTGAMING OC-8GD 8GB 128-Bit GDDR6 PCI Express 4.0 x16 ATX Video Card

I just bought it, think it need proprietary drivers to function at its full potential?

It's this one the RX 5500 series

Quote:

AMD Radeon™ Product Family Compatibility

Radeon™ Software for Linux® is compatible with the following AMD products.
AMD Product Family Compatibility

AMD Radeon™ RX 5700/5600/5500 Series Graphics

Can't seem to find where the download for the proprietary drivers for my card are but I'll continue looking. Is it right in front of my face and I don't see it?

Thanks again, Ed. I think you're right that I need the proprietary drivers for it to function correctly.

EdGr · 07-27-2020, 09:45 PM

Quote:

Originally Posted by Arct1c_f0x

That's awesome thanks, Ed! I have pretty much the newest Debian buster version - Debian Buster AMD 64 10.4

...

Thanks again, Ed. I think you're right that I need the proprietary drivers for it to function correctly.

Yes, use the proprietary driver for now. Debian takes an especially long time to get new software into a release.
Ed