All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@labri.fr>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Ben Skeggs <bskeggs@redhat.com>
Subject: Re: nouveau: temperature on nv40 is unavailable since ad40d73ef533ab0ad16b4a1ab2f7870c1f8ab954
Date: Tue, 13 Aug 2013 09:55:28 -0400	[thread overview]
Message-ID: <520A3AD0.5000304@labri.fr> (raw)
In-Reply-To: <3b367f03-0ab0-4b22-893e-3f03f16a496e@gmail.com>

On 13/08/2013 09:53, Pali Rohár wrote:
> On utorok, 13. augusta 2013 15:32:45 CEST, Martin Peres wrote:
>> On 13/08/2013 09:23, Pali Rohár wrote:
>>> On Tuesday 13 August 2013 09:01:19 Martin Peres wrote:
>>  ...
>> You can check the temperature by running nvidia-settings. If you can't
>> see the temperature in it, then nvidia doesn't support it on your 
>> card and
>> I'm not sure we should :s
>>
>> Thanks for the vbios you sent me in private. For the others, the reason
>> why he doesn't have temperature anymore is because his vbios lacks
>> sensor calibration values.
>>
>>
>
> In nvidia-settings tab "GPU 0 - (GeForce 6600 GT)" --> "Thermal 
> Settings" is:
>
> Thermal Sensor Information:
> ID: 0
> Target: GPU
> Provider: GPU Internal
> Temperature: 70 C (now)
>
> I looked in Windows program SpeedFan. It found Nvidia PCI card and 
> reported "GPU Temp" about 68-70 C. So it looks like both nvidia driver 
> and windows SpeedFan program reading same values.
>
Great, I'll cook you a patch in a bit and you'll see what the 
temperature is like. It won't be perfectly accurate but there is some 
kind of default for nvidia cards of this generation.

  reply	other threads:[~2013-08-13 13:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  9:56 nouveau: temperature on nv40 is unavailable since ad40d73ef533ab0ad16b4a1ab2f7870c1f8ab954 Pali Rohár
2013-08-13 13:01 ` Martin Peres
2013-08-13 13:23   ` Pali Rohár
2013-08-13 13:32     ` Martin Peres
2013-08-13 13:53       ` Pali Rohár
2013-08-13 13:53         ` Pali Rohár
2013-08-13 13:55         ` Martin Peres [this message]
2013-08-14  9:02           ` Pali Rohár
2013-08-15  2:07             ` Martin Peres
2013-08-15  7:24               ` Pali Rohár
2013-08-15 22:21                 ` Martin Peres
2013-08-16  7:14                   ` Pali Rohár
2013-08-21 10:18                     ` Martin Peres

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=520A3AD0.5000304@labri.fr \
    --to=martin.peres@labri.fr \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.