All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] nvidia nforce410 chipset / ASUS
Date: Mon, 03 Jul 2006 12:05:07 +0000	[thread overview]
Message-ID: <20060703140507.ae573552.khali@linux-fr.org> (raw)
In-Reply-To: <44A87466.9020002@winbond.com>

Hi Yuan, Daan,

> > > > I've tried the patch on a plain 2.6.17.1 vanilla kernel, but using the 
> > > > newbuilt module still doesn't show me the voltages. However on building 
> > > > the module with the patch applied I get the following message:
> > > >
> > > > WARNING: drivers/acpi/processor.o - Section mismatch: reference to 
> > > > .init.data: from .text between 'acpi_processor_power_init' (at offset 
> > > > 0xf2f) and 'acpi_processor_cst_has_changed'
> > > One possible reason is you need to install new lm_sensors2 user space tools.
> > > If it is not this reason, i can not help you more :(
> > > I still have no chance to try 2.6.17.1 kernel...
> > 
> > No, this is a completely unrelated warning. There's something wrong in
> > the acpi code, the compiler warns about it since 2.6.17 (it was already
> > wrong before, but the compiler wasn't taught to detect the mistake
> > until recently.
> > 
> > So, Daan, you can ignore that warning safely. You would have the same
> > warning without the patch. I have the warning too for quite some times
> > now and nothing bad happened ;) Let's just hope the acpi people
> > eventually show up and fix it, so that people stop being frightened!
>
> Hmm, sorry, i think i made a mistake that i have not snipped the "WARNING ..." part.
> I know nothing about it at all ;)
> 
> And my reply is for "doesn't show the voltage after patch w83627ehf",

Ah, my mistake, I missed _that_ part of Daan's anwser ;)

> Jean, why it still can not show the voltages :(

For "sensors" to display the voltages, Daan will need the SVN version
of lm_sensors. 2.10.0 didn't have support for them.

The easiest way to verify if the patch itself worked, is to check
manually in /sys/class/hwmon/hwmon0/device/. If you have the in* files,
it's OK, and you simply need a newer version of user-space. You can get
snapshots here:
  http://dl.lm-sensors.org/lm-sensors/snapshots/

-- 
Jean Delvare


  reply	other threads:[~2006-07-03 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
2006-07-03 12:05 ` Jean Delvare [this message]
2006-07-03 12:20 ` Daan Willems
2006-07-07 13:59 ` Daan Willems
2006-08-13 16:37 ` 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=20060703140507.ae573552.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.