With nvidia driver, you have to use nvidia-smi utility to get that
information. While the driver takes over the hardware, no other type of software can access same sensors. So when using nvidia-drivers, no
ssensors command.

On 6/19/2024 10:30 PM, Dale wrote:

Howdy,

I got the new Nvidia Quadro P1000 video card in the other day.  I got it installed.  I was using the nouveau drivers in the kernel.  They weren't
up to the task.  The display was slow and the mouse pointer was also
slow to respond and jerky like.  So, I downloaded and installed the
Nvidia drivers and the response is hugely better.  I expected those to include the drivers needed for the fan and temp sensors but it appears
not.  When I boot a kernel with the nouveau drivers, running sensors
prints the fan and temp data for the video card.  I know the card
supports this, haven't seen a video card in ages that doesn't tho.  So,
what drivers do I need in the kernel to support the temp and fan data?
I've enabled everything Nvidia I can find so it must be called something
else and searching isn't helping any.  Part of kernel config.

I2C Hardware Bus support

 <*> AMD 756/766/768/8111 and nVidia nForce
 < >   SMBus multiplexing on the Tyan S4882
 <*> AMD 8111
 <*> AMD MP2 PCIe
 <*> Intel 82801 (ICH/PCH)
 <*> Intel SCH SMBus 1.0
 <*> Intel iSMT SMBus Controller
 <*> Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)
 <*> Nvidia nForce2, nForce3 and nForce4
 < >   SMBus multiplexing on the Tyan S4985
 <*> NVIDIA GPU I2C controller
 <*> VIA VT82C586B
 <*> VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900
        *** ACPI drivers ***
 <*> SMBus Control Method Interface

I'm up to half a dozen attempts at building a kernel to find the right driver.  I've also searched the Nvidia website and searched but nothing
says the name of the drivers needed.  Maybe I'm missing something else.
Oh, I also tried a slightly older Nvidia driver just to see if it was
maybe a bug in the newer version.  No help.  Also, when I start the GUI
and open the Nvidia software, it doesn't show the temp and fan info
either.  It's just blank.

Any ideas?  Thanks.

Dale

:-)  :-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 7 July 2024 03:54:06 BST Dale wrote:

Alexandru N. Barloiu wrote:

With nvidia driver, you have to use nvidia-smi utility to get that information. While the driver takes over the hardware, no other type
of software can access same sensors. So when using nvidia-drivers, no ssensors command.

I been having . . . issues with the new rig. I wasn't able to dig into
this sensor issue so much. Now that I got it working pretty well, I
fired up gkrellm. It is my go to monitor app. The temp for the video
card show up there and gkrellm refers to it as GPU. So, they exist somewhere. I might add, it has been on my main rig for ages which also
uses Nvidia drivers. The AUXTIN4 matches the temp of the GPU temp on
gkrellm but a google search shows it is the power supply temp. I'm
digging around but have no idea where gkrellm is getting the temps
from. They somewhere, gkrellm found them but I have no idea where that
is, yet. As long as gkrellm works, and my screen works right, I can use gkrellm to monitor things.

Still kinda curious tho.

Dale

:-) :-)

AUXTIN is some reading off the MoBo. It could be what the PCIe picks up, potentially fed to it by the graphics card.

Not all AUXTIN readings are valid. The MoBo may have the provision, but no sensor or component is actually installed in this model.

I have 4 AUXTIN readings on a MoBo here, but I wouldn't be able to tell you something real is even connected to them:

AUXTIN0: +103.5°C sensor = thermistor
AUXTIN1: +104.0°C sensor = thermistor
AUXTIN2: +105.0°C sensor = thermistor
AUXTIN3: +105.0°C sensor = thermistor

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmaKcLIACgkQseqq9sKV ZxlYhg//dY3SR0PvOGfRSN2dpe4oKNCjSaND4DUraJRkWzjaDxO5IkW8bXuSeYtS +XayyZeJkrfKoMFMgscXC/GXnB0uTF+l3HH9YBaKrOvWS7wXtNgmum0L19RRcePB 9hzEs9uwiWMLAJMXpm8hhzhsUw9dltGRlCbaI9yJ0VyYVdItbJOPduKZAkHymzTj c1WvopT3Bbi6cQniPs0sJZaCsBBRpmrCEmfjWKZB8qpNY2ii0N3hjBlm+du6aV/n sVxAbkv/rVWZPNeDnce8XjI3LTSaPffrwAqB/IMc0U7C7eH+777mtdMvnrH2UdQ6 JYizHlPS/doNkaTOiL115d2OAq3nzenKIHoz1uSzAhZ7f9idf7bkmNk6eC5xAYMd pZ5kTqXrcpQstxPlAxZ75IeAW5pewxICLgHfzTpC78tnM5SLRgen+V7+JXo/Jtem +D4E6Dv9JEbNnJ2lVVUuEF3pdiKlZviYtHpO/Td3E609it8BXUK1LGGUi8b2yJXm 8xUEW03nqxTD9P8qHFv7Qa94VXEu2cKwqi0WzthCDLpmULSzPn5m733dXryQnU7G Cp53ucgEaiV77gNUEL4osCbDeGAlyfNrQMIgLIA6ijhbn6g3/THHa9rRflx0iWLN lqFhYilMafejFmnJgVZPAjSrtnasC0mtie8dwVIAeICuewREhjw=
=MZlU
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)