All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@shikadi.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value
Date: Tue, 20 Oct 2009 11:03:50 +0000	[thread overview]
Message-ID: <4ADD9916.3080301@shikadi.net> (raw)
In-Reply-To: <20091019164516.701032uxlen5ai2k@mail.simonandkate.net>

> Thanks for clarifying that. Still new at all this stuff really... :)

That makes two of us ;-)

> Well, based on the git version of hwmon-vid.c the fact that
> /sys/class/hwmon/hwmon0/device/vrm is originally 110 on my system would
> seem to indicate then that the hwmon-vid driver is correctly setting the
> VRM version based on my Conroe CPU to 110. Is there any way to
> interrogate the hwmon-vid driver to see whether it is working at a lower
> level before the it87 driver reads it in?

All the hwmon-vid driver seems to do is ask the driver for the raw vid value
and run it through a formula.  It doesn't actually have anything to do with
hardware at all (other than detecting the CPU brand and model.)

> Perhaps the elrepo.org kmod-it87 driver that I am using needs to be
> updated with more recent code to support the different VID configuration
> of the 8718 and 8720 chips...

Quite possibly, but if you download the latest Linux kernel, compile and boot
that, and try again you'll know for sure whether code exists to handle it or
not.  Given the number of quirks motherboard sensors seem to have, I suspect
this issue is just another quirk that needs to be added to the it87 driver.

The next step is to probably get some raw vid values off the it87 chip to see
what they look like - if those are all zero then we know the lines aren't
connected, but if there are some values there it should in theory be possible
to map them to vid voltages.  I guess this is where that isadump output you
posted comes in...

It's a shame there's no "passthrough" vrm version that disables the formula
and shows the raw vid value, as that would probably be quite helpful.  Maybe
it's worth adding a patch to do just that?

Cheers,
Adam.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-10-20 11:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  6:45 [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value Simon Wilson
2009-10-19 10:51 ` Justin Piszcz
2009-10-19 11:07 ` Adam Nielsen
2009-10-19 23:35 ` Simon Wilson
2009-10-19 23:59 ` Adam Nielsen
2009-10-20  1:12 ` Simon Wilson
2009-10-20  1:43 ` Adam Nielsen
2009-10-20  2:05 ` Simon Wilson
2009-10-20 11:03 ` Adam Nielsen [this message]
2009-10-20 11:23 ` Simon Wilson
2009-10-20 11:38 ` Jean Delvare
2009-10-20 11:48 ` Jean Delvare
2009-10-20 11:50 ` Adam Nielsen
2009-10-20 11:57 ` Jean Delvare
2009-10-20 12:02 ` Jean Delvare
2009-10-20 12:15 ` Adam Nielsen
2009-10-20 14:15 ` Jean Delvare
2009-10-21 12:15 ` Simon Wilson
2009-10-21 12:30 ` Simon Wilson
2009-10-21 12:51 ` Jean Delvare
2009-10-21 12:53 ` Jean Delvare
2009-10-21 12:57 ` Simon Wilson
2009-10-21 13:06 ` Jean Delvare
2009-10-21 13:28 ` Adam Nielsen
2009-10-21 13:41 ` Jean Delvare
2009-10-22 12:28 ` Jean Delvare
2009-10-22 23:20 ` Adam Nielsen
2009-10-23  7:13 ` Jean Delvare

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=4ADD9916.3080301@shikadi.net \
    --to=a.nielsen@shikadi.net \
    --cc=lm-sensors@vger.kernel.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.