gmane.linux.drivers.sensors

Check out my Facebook profile

Prakash J Kokkattu — 2008-12-01T03:20:56

_______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: hwmon: add support for w83667hg

David Hubbard — 2008-12-01T06:53:00

Hi Gong Jun, On Sun, Nov 30, 2008 at 11:31 PM, nuvoton.com> wrote: Looks good. Signed-off-by: David Hubbard gmail.com> _______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: hwmon: add support for w83667hg

2008-12-01T06:31:50

Dear David, Thanks I've fixed it. Here is the updated one. Best regards, Gong Jun Signed-off-by: Gong Jun nuvoton.com> --- w83627ehf.c | 122 +++++++++++++++++++++++++++++++++----------------- 1 file changed, 82 insertions(+), 40 deletions(-) --- --- w83627ehf.c.orig2008-11-26 11:13:12.000000000 +0800 +++ w83627ehf.c2008-11-27 11:26:01.000000000 +0800 < at >< at > -36,6 +36,7 < at >< at > w83627ehf 10 5 4 3 0x8850 0x88 0x5ca3 0x8860 0xa1 w83627dhg 9 5 4 3 0xa020 0xc1 0x5ca3 + w83667hg 9 5 3 3 0xa510 0xc1 0x5ca3 */ #include < at >< at > -51,12 +52,13 < at >< at > #include #include "lm75.h" -enum kinds { w83627ehf, w83627dhg }; +enum kinds { w83627ehf, w83627dhg, w83667hg}; /* used to set data->name = w83627ehf_device_names[data->sio_kind] */ static const char * w83627ehf_device_names[] = { "w83627ehf", "w83627dhg", +"w83667hg", }; static unsig

Re: Special handling of SiS south bridges insensors-detect

Jean Delvare — 2008-11-30T20:17:34

I just check and apparently the quirk went into kernel 2.6.0-test10, and was fixed in 2.6.5. It happens that kernel 2.6.5 is the first one we claim to support in lm-sensors 3.x. So indeed the sensors-detect quirk can go away. Thanks,

Re: Special handling of SiS south bridges insensors-detect

Mark M. Hoffman — 2008-11-30T15:56:52

Hi Jean: * Jean Delvare linux-fr.org> [2008-11-30 13:47:40 +0100]: Very early 2.6.x did not yet have the SiS quirks code... so this was at one time still necessary. But yes, IMO this can go away now. Regards,

Special handling of SiS south bridges in sensors-detect

Jean Delvare — 2008-11-30T12:47:40

Hi Mark, Now that support for Linux 2.4 has been dropped from sensors-detect, I am looking at possible clean-ups. One thing I am curious about is the handling of SiS south bridges. I remember that these required special handling for Linux 2.4 because they were all showing up with the same PCI ID. However I am surprised that we still have the following code even for Linux 2.6, where I seem to understand that PCI quirks in the kernel are taking care of revealing the actual device: sub adapter_pci_detection_sis_96x { # Add the appropriate entries to < at >pci_adapters if (exists $pci_list{'1039:0016'}) { push < at >pci_adapters, < at >pci_adapters_sis96x; } elsif (exists $pci_list{'1039:0008'}) { push < at >pci_adapters, < at >pci_adapters_sis5595; } } Can this go away now? Thanks,

Re: pwmconfig failure under Ubuntu Intrepid with Intel 945GM chipset

Jean Delvare — 2008-11-29T17:51:48

Hi Dan, On Sun, 23 Nov 2008 20:38:30 -0500, Dan Davison wrote: On most recent laptops, thermal management is handled by ACPI. No hardware monitoring chips are exposed to the OS and thus software-based fan speed control is not possible (and most often not desirable either - the ACPI-based control should work just fine.) The coretemp driver lets you read the CPU temperature value of Intel Core and later CPU models. It is not a hardware monitoring chip driver, so, no fan speed readings nor control. FWIW, the smartbatt driver is a legacy thing for Linux 2.4. I seem to remember that ACPI is taking care of this now (at least on some laptop models). The ACPI driver is named sbs. We should no longer recommend the smartbatt driver. No, it doesn't. It is a simple temperature-only driver. These are the ACPI temperatures, if they never change, this suggests that the ACPI implementation of your laptop is broken. Upgrading the BIOS might help. As a side note, the value 26.8 itself is pretty suspicious, consideri

Re: ITE 8710 support

Jean-Marc Spaggiari — 2008-11-29T16:29:22

Hi Daniel, Can you please send me the details? I will takea look and I might be able to provide you a patch that you can test. Thanks, JM 2008/11/29 daniel. perzynski aster.pl>: _______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

ITE 8710 support

daniel.perzynski — 2008-11-29T14:08:10

Hi, Please add support for ITE 8710F chipset. I can provide data sheet and programming guide. If you are interested in those documents please let me know where to send them. Regards, _______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

GET BACK TO ME

Muhammed Karal — 2008-11-28T13:46:02

_______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

PATCH: hwmon-fschmd-watchdog-v4.patch

Hans de Goede — 2008-11-28T15:01:54

Hi Jean, Today I had access to my FSC test machine for the first time in a while. So here is the latest version of my watchdog support for Siemens hwmon IC's patch. This fixes the last 2 issues you spotted during review. Can you please queue this for 2.6.29 ? If Wim comes up with anything during his review I'll fix that with a follow up patch, Regards, Hans This patch adds support for the watchdog part found in _all_ supported FSC sensor chips. Signed-off-by: Hans de Goede redhat.com> diff -up linux-2.6.28-rc4/drivers/hwmon/Kconfig.wtd linux-2.6.28-rc4/drivers/hwmon/Kconfig --- linux-2.6.28-rc4/drivers/hwmon/Kconfig.wtd2008-11-10 11:13:01.000000000 +0100 +++ linux-2.6.28-rc4/drivers/hwmon/Kconfig2008-11-10 11:27:10.000000000 +0100 < at >< at > -318,10 +318,11 < at >< at > config SENSORS_FSCHMD depends on X86 && I2C && EXPERIMENTAL help If you say yes here you get support for various Fujitsu Siemens - Computers sensor chips. + Computers sensor chips, including support for the integrated + watchd

Re: PATCH: hwmon-fschmd-watchdog-v4.patch

Jean Delvare — 2008-11-28T16:17:27

Hi Hans, On Fri, 28 Nov 2008 16:01:54 +0100, Hans de Goede wrote: Applied, thanks. Now I'm waiting for the patch which deprecates fscher and fscpos :)

Re: New Asus board and multiplesensorschips(W83667HG/W83791D/ADT7475)

Marco Chiappero — 2008-11-27T14:41:31

> Hum, anything in dmesg? > Anyway I'm attacching the new version (plus patch for ACPI - diffed > against git-current, but it's easily adapted to older kernels). Hi Luca, sorry for my late reply but I've been busy these days. I compiled and loaded the new atk driver and compiled again lm-sensors with the old patch (that was laying around in my /usr/src) and this time I managed to see the atk driver readings from the "sensors" output (don't know why it didn't work the first time, sorry). However I noticed that the code you posted recently it's a little bit different, isn't? Should I try that one too? About the atk, it seems to work fine, but I haven't got the time to verify the presence of strange issues, regarding for example suspend and/or hibernate, stuff like that (does it matter?). Any suggestion about what to check is welcome. The only thing to say is that in the new code now shows all the readings in the /sys/class/hwmon/hwmonX/ dir instead of the /sys/class/hwmon/hwmonX/device/ I used to

Re: hwmon: add support for w83667hg

David Hubbard — 2008-11-26T18:26:39

Hi Gong Jun, On Wed, Nov 26, 2008 at 12:39 AM, nuvoton.com> wrote: It looks good, but I do have one question. The last two reads are identical to the ones in the for loop. Can this code be moved to the for loop instead of skipping it there and then reading it after? Thanks, David _______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

hwmon: add support for w83667hg

2008-11-26T07:39:19

Dear all, This patch adds support for the Nuvoton w83667hg chip to the w83627ehf driver. It has been tested on ASUS P5QL PRO by Gong Jun. Best regards, Gong Jun Signed-off-by: Gong Jun nuvoton.com> --- w83627ehf.c | 122 ++++++++++++++++++++++++++++++++++---------------- 1 file changed, 84 insertions(+), 38 deletions(-) --- --- w83627ehf.c.orig2008-11-26 11:13:12.000000000 +0800 +++ w83627ehf.c2008-11-26 15:37:15.000000000 +0800 < at >< at > -36,6 +36,7 < at >< at > w83627ehf 10 5 4 3 0x8850 0x88 0x5ca3 0x8860 0xa1 w83627dhg 9 5 4 3 0xa020 0xc1 0x5ca3 + w83667hg 9 5 3 3 0xa510 0xc1 0x5ca3 */ #include < at >< at > -51,12 +52,13 < at >< at > #include #include "lm75.h" -enum kinds { w83627ehf, w83627dhg }; +enum kinds { w83627ehf, w83627dhg, w83667hg}; /* used to set data->name = w83627ehf_device_names[data->sio_kind] */ static const char * w83627ehf_dev

Re: DDR2 SODIMM temperature sensor driver

Darrick J. Wong — 2008-11-24T20:18:07

The FB-DIMM temperature sensors are inside the AMB buffer chip on the memory module. Not sure how many non-FB DDR2 DIMMs have temperature sensors that you can read; none of my machines (even the laptops) have any. --D _______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Help with configuration on k7s41

Noel David Torres Taño — 2008-11-24T19:27:12

_______________________________________________ lm-sensors mailing list lm-sensors< at >lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: Gigabyte GA-MA69G-S3H it8716 temperatures?

Jean Delvare — 2008-11-24T12:15:00

Hi Jon, On Mon, 24 Nov 2008 10:15:12 +0000, Jon Hewer wrote: Indeed. And temp2 isn't fake as I first thought, which is good news. Thanks, I've added this data point to my collection.

Re: Gigabyte GA-MA69G-S3H it8716 temperatures?

Jon Hewer — 2008-11-24T10:15:12

Hi Jean, Thanks very much for your reply. I've just tried running two "md5sum /dev/zero" commands in parallel. After about 30 seconds or so temp2 increased from 25 to 31 and temp3 from 19 to 28. I suppose this along with your comment about thermal diode measurement type suggests temp3 is my CPU temp. My CPU isn't water cooled, however it is an Athlon X2 4450e which is meant to run pretty cool, and I've also upgraded to a better heatsink than the retail one. After building my server I did check the temperatures in the BIOS, which returned a temperature of about 26 degrees or so for the CPU. I don't have a monitor hooked up to my server at the moment, but might do so to check the BIOS again now that I have the lm-sensors output for comparison. As requested, here is the contents of /proc/cpuinfo $ cat /proc/cpuinfo processor: 0 vendor_id: AuthenticAMD cpu family: 15 model: 107 model name: AMD Processor model unknown stepping: 2 cpu MHz: 2305.229 cache size: 512 KB physical id: 0 siblings: 2

Re: Gigabyte GA-MA69G-S3H it8716 temperatures?

Jean Delvare — 2008-11-24T09:52:46

Hi Jon, On Mon, 24 Nov 2008 09:27:08 +0000, Jon Hewer wrote: Preliminary note: the "transistor" above should read "thermistor", that's a bug in the it87 driver which has been fixed already. As a rule of thumb, CPU temperature is most often measured by a thermal diode and motherboard temperature by a thermistor. That would be temp1=system and temp3=cpu. That being said, I have to admit that 19 degrees C is very low for CPU temperature, unless it is water-cooled. A quick test you can do to find out who is who is to put significant load on the CPU (for example, "md5sum /dev/zero" running twice in parallel for a dual-core CPU) and see which temperature is rising faster. That will be the CPU temperature. You can also compare the readings in the BIOS with those returned by "sensors" under Linux. The readings in the BIOS should be equivalent to those of "sensors" under moderate load. Also note that Gigabyte has a long record of doing nasty things with temperature sensors. For example, temp2 reads 25 degrees

Gigabyte GA-MA69G-S3H it8716 temperatures?

Jon Hewer — 2008-11-24T09:27:08

Hello, The output of sensors for my Gigabyte GA-MA69G-S3H motherboard is as follows: k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: -6.0°C Core0 Temp: +1.0°C Core1 Temp: -8.0°C Core1 Temp: -5.0°C it8716-isa-0228 Adapter: ISA adapter VCore: +1.18 V (min = +0.00 V, max = +4.08 V) VDDR: +1.94 V (min = +0.00 V, max = +4.08 V) +3.3V: +3.25 V (min = +0.00 V, max = +4.08 V) +5V: +4.92 V (min = +0.00 V, max = +6.85 V) +12V: +12.10 V (min = +0.00 V, max = +16.32 V) in5: +3.14 V (min = +0.00 V, max = +4.08 V) in6: +0.10 V (min = +0.00 V, max = +4.08 V) 5VSB: +4.92 V (min = +0.00 V, max = +6.85 V) VBat: +3.10 V fan1: 1341 RPM (min = 0 RPM) fan2: 1002 RPM (min = 0 RPM) temp1: +33.0°C (low = +127.0°C, high = +60.0°C) sensor = transistor temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor temp3: +19.0°C (low = +127.0°C, high = +60.0°C) sensor = ther