Bug 40894

Summary:	nv30-/temperature: Reverse engineer the temperature coefficients
Product:	xorg	Reporter:	Martin Peres <martin.peres>
Component:	Driver/nouveau	Assignee:	Nouveau Project <nouveau>
Status:	RESOLVED INVALID	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	40892

Description Martin Peres 2011-09-14 15:30:02 UTC

We currently have some bits of knowledge about temperature management on cards up to nv40, but it doesn't seem to work on every card.

The work that needs to be done is understand how the temperature table entries in the vbios influence the proprietary driver's temperature readings.

What is needed is to install the envytools (https://github.com/pathscale/envytools/tree/), get your vbios using nvagetbios, parse it with nvbios, get the address of the temperature table, edit this table with an hex editor, upload it using nvafakebios, load the nvidia module and then launch the blob and check how your changes affected the temperature reading.

Then, exit X, rmmod nvidia and start again at the hex editor step ;)

Comment 1 Ilia Mirkin 2013-08-18 18:09:41 UTC

It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team

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.