* [lm-sensors] nvidia nforce410 chipset / ASUS
@ 2006-07-03 1:35 Yuan Mu
2006-07-03 12:05 ` Jean Delvare
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Yuan Mu @ 2006-07-03 1:35 UTC (permalink / raw)
To: lm-sensors
Hi Jean, Daan,
>> Daan Willems wrote:
>>> 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",
Jean, why it still can not show the voltages :(
--
Best Regards
Yuan Mu
=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] nvidia nforce410 chipset / ASUS
2006-07-03 1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
@ 2006-07-03 12:05 ` Jean Delvare
2006-07-03 12:20 ` Daan Willems
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2006-07-03 12:05 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] nvidia nforce410 chipset / ASUS
2006-07-03 1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
2006-07-03 12:05 ` Jean Delvare
@ 2006-07-03 12:20 ` Daan Willems
2006-07-07 13:59 ` Daan Willems
2006-08-13 16:37 ` Jean Delvare
3 siblings, 0 replies; 5+ messages in thread
From: Daan Willems @ 2006-07-03 12:20 UTC (permalink / raw)
To: lm-sensors
Hi Jean, Juan,
> 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.
Thanks for the remark! That indeed seems the case, as I do have the in*
files there ;) I am using 2.10.0-7 lm-sensors, as currently provided in
Debian etch/testing. Thanks a lot for the support!
Daan
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] nvidia nforce410 chipset / ASUS
2006-07-03 1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
2006-07-03 12:05 ` Jean Delvare
2006-07-03 12:20 ` Daan Willems
@ 2006-07-07 13:59 ` Daan Willems
2006-08-13 16:37 ` Jean Delvare
3 siblings, 0 replies; 5+ messages in thread
From: Daan Willems @ 2006-07-07 13:59 UTC (permalink / raw)
To: lm-sensors
> 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/
>
Right, so the patch appears to work just fine... when will it be
submitted for inclusion in the vanilla kernel series?
I guess more people are waiting for this support..
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] nvidia nforce410 chipset / ASUS
2006-07-03 1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
` (2 preceding siblings ...)
2006-07-07 13:59 ` Daan Willems
@ 2006-08-13 16:37 ` Jean Delvare
3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2006-08-13 16:37 UTC (permalink / raw)
To: lm-sensors
Hi Daan,
> > 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/
>
> Right, so the patch appears to work just fine... when will it be
> submitted for inclusion in the vanilla kernel series?
> I guess more people are waiting for this support..
It's already in, 2.6.18 will be the first released kernel have it.
--
Jean Delvare
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-08-13 16:37 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-03 1:35 [lm-sensors] nvidia nforce410 chipset / ASUS Yuan Mu
2006-07-03 12:05 ` Jean Delvare
2006-07-03 12:20 ` Daan Willems
2006-07-07 13:59 ` Daan Willems
2006-08-13 16:37 ` Jean Delvare
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.