Bug 92386

Summary:

Integrated sensor on nv43 doesn't work (wrong vbios parsing?)

Product:

xorg

Reporter:

Andrew Randrianasulu <randrik>

Component:

Driver/nouveau

Assignee:

Nouveau Project <nouveau>

Status:

RESOLVED MOVED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

git

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
hack for recognizing sensor on nv43	none
vbios	none

Description Andrew Randrianasulu 2015-10-10 14:48:29 UTC

Created attachment 118799 [details]
hack for recognizing sensor on nv43

Hello, this is me again with my useful nv43.

As far as I can see nvidia binary driver can use integrated sensor on my card, while nouveau can't. After some digging I found problem - nouveau can't find some calibration coefficients in vbios. May be they missed completely, or bios slightly misparsed. I'll attach again my vbios, and patch I made after looking at nvclock sources [1]. Patch allow sensor to work, and reported temperature roughly correspond to what I saw with binary driver (looking at raw output I see nouveau still hotter than nvidia, but I can ignore this for now).

Not sure if such hack (?) should go into nouveau, or I (someone) better to find if values really missed from vbios first.

Command for getting raw sensor value:
envytools/nva/nvapeek 0x15b4

[1] - http://www.linuxhardware.org/nvclock/

Comment 1 Andrew Randrianasulu 2015-10-10 14:49:28 UTC

Created attachment 118800 [details]
vbios

Comment 2 Martin Peres 2019-12-04 09:05:02 UTC

-- 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/224.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.