Bug 98852

Created attachment 128183 [details]
Output of the dmesg command

Created attachment 128184 [details]
installed nouveau drivers

Created attachment 128185 [details]
Output of the lspci command

Created attachment 128186 [details]
content of the yast-hwscreen tool

How can I set the speed of the graphic card fan to full speed or
an certain value greater 0 rpms ?

can you attach your vbios.rom file from /sys/kernel/debug/dri/0/vbios.rom

Created attachment 128188 [details]
Content of vbios.rom

The documentation on how to set the fan speed is located here: https://www.kernel.org/doc/Documentation/thermal/nouveau_thermal

However, it is quite likely that we do not configure the PWM controler properly. Looking at your vbios, I see that the expected frequency is 42kHz which is quite high and may be the reason why your fan would not rotate properly (unless it is set to 100%).

What would be really useful, would be for you to try to force the fan to 100%, by following the guide I sent you.

(In reply to Martin Peres from comment #8)
> The documentation on how to set the fan speed is located here:
> https://www.kernel.org/doc/Documentation/thermal/nouveau_thermal
> 
> However, it is quite likely that we do not configure the PWM controler
> properly. Looking at your vbios, I see that the expected frequency is 42kHz
> which is quite high and may be the reason why your fan would not rotate
> properly (unless it is set to 100%).
> 
> What would be really useful, would be for you to try to force the fan to
> 100%, by following the guide I sent you.

I guess you should also try other fan speeds too, report back when you have tried.
The expected result would be for the fan to barely spin at 10% and gradually spin up until reaching 100%. At 100%, the noise should be quite loud.

If this is the behaviour you see, then I would like you to set the fan mode to automatic (mode 2) and monitor the fan speed set by Nouveau by reading pwm1.

If the fan speed does not change with temperature, it would be useful to paste here kernel logs with nouveau.debug="ptherm=debug" set in your kernel command line (you can edit this from grub directly, when booting up).

I list here the commands I have given as root.

But the fan did not start.

Have I used wrong values ?
 
I'am a little bit confused by the description where is written, that
some parameter are in milli-degree, but I can't recognize what of the parameters this are.

So I played around with values from 1 to 1000 to hit as blind user
a value, where the fan could start.

In the appendix hwmon-handling  is the protocol of my session.

Created attachment 128205 [details]
Session in a Terminal Window with the attempt to start the graphic card fan

I did some further tests with setting of the boot time parameter
in the yast kernel parameter line.

Also with 
 
nouveau.runpm=0  or
nouveau.runpm=1  
the fan on the graphic card does not start.

Beside this I use for PC tests also the systemrescue-Distribution
where DVD images can be found on 
http://www.system-rescue-cd.org/Download

I observed that until version 4.6.1 the fan on the graphic card was running.
Starting with version 4.7.1 the fan stops after loading of the rescue system.

(In reply to Egon Niessner from comment #12)
> I did some further tests with setting of the boot time parameter
> in the yast kernel parameter line.
> 
> Also with 
>  
> nouveau.runpm=0  or
> nouveau.runpm=1  
> the fan on the graphic card does not start.
> 
> Beside this I use for PC tests also the systemrescue-Distribution
> where DVD images can be found on 
> http://www.system-rescue-cd.org/Download
> 
> I observed that until version 4.6.1 the fan on the graphic card was running.
> Starting with version 4.7.1 the fan stops after loading of the rescue system.

This is really weird as there are no changes related to the fan between 4.6 and 4.7 :s

I guess, at this point, we need to check out what nouveau is doing versus what the blob is doing.

Please download and compile envytools[0] and run the following command when running Nouveau, then when using the proprietary driver:
 - nvapeek e114 10

Please report back.

[0] https://github.com/envytools/envytools/commits/master

I downloaded the envytools Software from your link and tried an installation.
I got following error messages:

inux-234d:/home/nie1/envytools/envytools-master # cmake . -G Ninja
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!




linux-234d:/home/nie1/envytools/envytools-master # cmake .
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!


On the system the whole linux kernel development environment is installed
and all packages mentioned in the envytools description.
What have I to do, that the compilation is possible ?

(In reply to Egon Niessner from comment #14)
> I downloaded the envytools Software from your link and tried an installation.
> I got following error messages:
> 
> inux-234d:/home/nie1/envytools/envytools-master # cmake . -G Ninja
> CMake Error: CMake was unable to find a build program corresponding to
> "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a
> different build tool.
> CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
> CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
> -- Configuring incomplete, errors occurred!
> 
> 
> 
> 
> linux-234d:/home/nie1/envytools/envytools-master # cmake .
> CMake Error: CMake was unable to find a build program corresponding to
> "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a
> different build tool.
> CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
> CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
> -- Configuring incomplete, errors occurred!
> 
> 
> On the system the whole linux kernel development environment is installed
> and all packages mentioned in the envytools description.
> What have I to do, that the compilation is possible ?

drop the "-G Ninja"

There is a ninja package on Arch Linux, I would guess that something similar exists on openSUSE.

Try with `cmake -G"Unix Makefile" .` instead, or clear the CMake cache (delete CMakeCache.txt and CMakeFiles should be enough I think), and try again to run `cmake .`.

Thanks for your help!
With `cmake -G"Unix Makefiles" .
I could translate the envytools Package.

Here the Output with the nouveau driver and not runnung fan:
nvapeek e114 10
0000e114: 00000001 00000000 00000000 80000000


Here the Output with the original nvidia driver
(Installed is the original NVIDIA Package
NVIDIA-Linux-x86_64-340.96.run)

nvapeek e114 120
0000e114: 00000001 00000000 00000020 00000003
0000e124: 10000000 00000000 0001010e 00000000
0000e134: 000f4240 00000007 10000000 00000000
0000e144: 0001010e 00000000 000f4240 00000007
0000e154: 10000000 00000000 0001010e 00000000
0000e164: 000f4240 00000007 10000000 00000000
0000e174: 0001010e 00000000 000f4240 00000007
0000e184: 00000012 00000000 00010000 00000000
0000e194: 00000000 00000000 00000000 0000000d
0000e1a4: 00000001 0000000c 0022ffff 00000000
0000e1b4: 00000001 fe7fffff 00003047 00000002
...
0000e1d4: 00000000 0000001f 00000001 00000000
0000e1e4: 00000000 00000001 00000003 00000003
0000e1f4: 0000000c 00000002 00000002 0003103c
0000e204: 00000002 00000000 00000000 00000000

(In reply to Egon Niessner from comment #17)
> Thanks for your help!
> With `cmake -G"Unix Makefiles" .
> I could translate the envytools Package.
> 
> Here the Output with the nouveau driver and not runnung fan:
> nvapeek e114 10
> 0000e114: 00000001 00000000 00000000 80000000
> 
> 
> Here the Output with the original nvidia driver
> (Installed is the original NVIDIA Package
> NVIDIA-Linux-x86_64-340.96.run)
> 
> nvapeek e114 120
> 0000e114: 00000001 00000000 00000020 00000003

Exactly what I did not want to see :s

Could you attach here your vbios? You can get it by running: nvagetbios -s prom > vbios.rom

Please also add the output of: nvapeek 101000

Thanks in advance, you uncovered a deeper bug!

Here the output of the nvapeek command:

nvapeek e114 10
0000e114: 00000001 00000000 00000000 80000000

I added the vbios.com as attachment.

Created attachment 128379 [details]
Content of the vbios

(In reply to Egon Niessner from comment #19)
> Here the output of the nvapeek command:
> 
> nvapeek e114 10
> 0000e114: 00000001 00000000 00000000 80000000
> 
> I added the vbios.com as attachment.

no, you should run: nvapeek 101000 :)

Sorry, the last output was not the wished one.
Now the correct output:

nvapeek 101000
00101000: 80408c8e

Thanks for being super helpful and responsive! We compute the clock tree correctly so now, the problem is that we do not detect which PWM controller we need to write to.

So, let's have a look at nouveau's code now and see what could go wrong :)

(In reply to Martin Peres from comment #23)
> Thanks for being super helpful and responsive! We compute the clock tree
> correctly so now, the problem is that we do not detect which PWM controller
> we need to write to.
> 
> So, let's have a look at nouveau's code now and see what could go wrong :)

Nothing obvious comes to mind. Especially not something related to the fan. If it is a regression between 4.6 and 4.7, is it too much to ask for a bisect? :s

Hello,
what have I to do, to produce a bisect?

Have I to install a special version of a kernel?

I can make an installation on a other harddisk.

I have got a second Geforce GT240 card, which shows the same Fan-symptoms.
Would it help you, if I send the pcie-card to you for tests in your own
test-equipment ?

If you will do own tests, you have not to send the card back to me.
Regards
Egon

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/307.