[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Yuan Mu]

Hello Daan,

> I subscribed to the list because I am trying to configure lm-sensors for 
> my ASUS K8N-VM motherboard, which features a nvidia nforce410 chipset 
> (the one with geforce6100 integrated). So far I have good results with 
> the w83627ehf kernel module, yielding the following output:
> 
> -------
> d3vlin at arrakis ~ $ sensors
> w83627ehf-isa-0290
> Adapter: ISA adapter
> Chassis Fan:  1795 RPM  (min = 1205 RPM, div = 8)
> CPU Fan:      3245 RPM  (min = 1704 RPM, div = 8)
> System Temp:  +28?C  (high =   +60?C, hyst =   +40?C)
> CPU Temp:     +30.0?C  (high = +60.0?C, hyst = +40.0?C)
> Chipset Temp: +33.0?C  (high = +60.0?C, hyst = +40.0?C)
> d3vlin at arrakis ~ $
> -------
> 
> As one might notice, there is no information about VCore / 3.3V etc. 
> displayed. I have tried some modules, i2c_nforce2 in particular, but no 
> results. I wonder if there is support for this chipset or if anyone has 
> better results. I have included the relevant part of my 
> /etc/sensors.conf below.
I think the reason is voltage support not added to the driver in your kernel version.
The feature is added to the new kernel now.
And give us the kernel version would be useful.


-- 
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.

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Daan Willems]

Hello Yuan,

Thanks for your quick response. I am using latest vanilla kernels from 
kernel.org (so 2.6.17.1 now). Which version will support the voltage 
stuff in the w83627 driver?
Btw I also tried some patches for the 410 chip on the nforce2 driver 
that I found in the lmsensors archive, but those didn't bring me 
anything either.

Best, Daan

Yuan Mu wrote:
> Hello Daan,
> 
>> I subscribed to the list because I am trying to configure lm-sensors 
>> for my ASUS K8N-VM motherboard, which features a nvidia nforce410 
>> chipset (the one with geforce6100 integrated). So far I have good 
>> results with the w83627ehf kernel module, yielding the following output:
>>
>> -------
>> d3vlin at arrakis ~ $ sensors
>> w83627ehf-isa-0290
>> Adapter: ISA adapter
>> Chassis Fan:  1795 RPM  (min = 1205 RPM, div = 8)
>> CPU Fan:      3245 RPM  (min = 1704 RPM, div = 8)
>> System Temp:  +28?C  (high =   +60?C, hyst =   +40?C)
>> CPU Temp:     +30.0?C  (high = +60.0?C, hyst = +40.0?C)
>> Chipset Temp: +33.0?C  (high = +60.0?C, hyst = +40.0?C)
>> d3vlin at arrakis ~ $
>> -------
>>
>> As one might notice, there is no information about VCore / 3.3V etc. 
>> displayed. I have tried some modules, i2c_nforce2 in particular, but 
>> no results. I wonder if there is support for this chipset or if anyone 
>> has better results. I have included the relevant part of my 
>> /etc/sensors.conf below.
> I think the reason is voltage support not added to the driver in your 
> kernel version.
> The feature is added to the new kernel now.
> And give us the kernel version would be useful.

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Yuan Mu]

Hi Daan,
> 
> Thanks for your quick response. I am using latest vanilla kernels from 
> kernel.org (so 2.6.17.1 now). Which version will support the voltage 
> stuff in the w83627 driver?
> Btw I also tried some patches for the 410 chip on the nforce2 driver 
> that I found in the lmsensors archive, but those didn't bring me 
> anything either.
Sorry, It seems the voltage support has been added to the w83627ehf driver only 6 days ago ;)
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/hwmon/w83627ehf.c

You can also get the patch from the link.

-- 
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.

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Daan Willems]

Ok great! Will this patch apply to a vanilla 2.6.17.1 kernel?
Is it planned for a future update of the vanilla kernel?

Yuan Mu wrote:
> Hi Daan,
>>
>> Thanks for your quick response. I am using latest vanilla kernels from 
>> kernel.org (so 2.6.17.1 now). Which version will support the voltage 
>> stuff in the w83627 driver?
>> Btw I also tried some patches for the 410 chip on the nforce2 driver 
>> that I found in the lmsensors archive, but those didn't bring me 
>> anything either.
> Sorry, It seems the voltage support has been added to the w83627ehf 
> driver only 6 days ago ;)
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/hwmon/w83627ehf.c 
> 
> 
> You can also get the patch from the link.
> 

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Yuan Mu]

Daan Willems wrote:
> Ok great! Will this patch apply to a vanilla 2.6.17.1 kernel?
> Is it planned for a future update of the vanilla kernel?
> 
I think it can apply to your kernel.
Or you can waiting for 2.6.18-rc1 ;)

-- 
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.

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Daan Willems]

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'

Yuan Mu wrote:
> Daan Willems wrote:
>> Ok great! Will this patch apply to a vanilla 2.6.17.1 kernel?
>> Is it planned for a future update of the vanilla kernel?
>>
> I think it can apply to your kernel.
> Or you can waiting for 2.6.18-rc1 ;)
> 

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Yuan Mu]

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...

-- 
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.

[lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM

[Jean Delvare]

Hi Yuan, 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!

-- 
Jean Delvare