From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 92386] New: Integrated sensor on nv43 doesn't work (wrong vbios parsing?)
Date: Sat, 10 Oct 2015 14:48:29 +0000 [thread overview]
Message-ID: <bug-92386-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92386
Bug ID: 92386
Summary: Integrated sensor on nv43 doesn't work (wrong vbios
parsing?)
Product: xorg
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: randrik-JGs/UdohzUI@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 118799
--> https://bugs.freedesktop.org/attachment.cgi?id=118799&action=edit
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/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3073 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-10-10 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 14:48 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-92386-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-10-10 14:49 ` [Bug 92386] Integrated sensor on nv43 doesn't work (wrong vbios parsing?) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-92386-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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.