* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
@ 2007-10-19 18:33 ` Hans de Goede
2007-10-19 18:34 ` David Hubbard
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2007-10-19 18:33 UTC (permalink / raw)
To: lm-sensors
James Scott Jr wrote:
> Folks,
>
> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro
> mainboard, using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output
> from sensors is wrong. Is there a preformatted config file for these
> mainboard somewhere that I can find? Or can you give me a hit on what I
> need to know in order to create/adjust one?
>
Abit usually does not use the sensors of the super io chip (which the w83627dhg
is), instead they use their own solution called uguru. There is a driver for
this, but the uguru isn't detected by sensors-detect.
Try modprobe abituguru3, and then try running sensors again.
The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
this kernel for F-7 do:
yum update --enable-repo=updates-testing kernel
After rebooting into the new kernel do
modprobe abituguru3
sensors
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
2007-10-19 18:33 ` Hans de Goede
@ 2007-10-19 18:34 ` David Hubbard
2007-10-19 18:50 ` JAMES SCOTT
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: David Hubbard @ 2007-10-19 18:34 UTC (permalink / raw)
To: lm-sensors
Hi James,
> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output from sensors is
> wrong. Is there a preformatted config file for these mainboard somewhere
> that I can find? Or can you give me a hit on what I need to know in order
> to create/adjust one?
I think you'll need to create one. I haven't seen any emails on the
lm-sensors list about your motherboard.
Creating a new config file isn't too hard. Look at the man page for
sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf
You should also have one already (maybe in /etc/sensors.conf) and
reading it is very helpful.
> The cpu cores are really in the high 30's, cpu & case fans are not
> present, ....
I'm looking at the IP32 pro manual, page 11, and I see six fans
(CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
fans, which makes me wonder if your southbridge (possibly an Intel
ICH9) is controlling one fan. Do you have zero fans connected? Or just
one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
Guru Panel." Do you have a uguru on the motherboard? (I'm not really
familiar with abit's uguru, but there are some other people here on
lm-sensors who know a lot more about it.)
The sensors.conf file we figure out here, for the sake of all IP32 pro
users, should probably not disable the fan input readings and alarms.
But if you want, you can set "ignore" statements for all the fans, so
they don't show up in the sensors output, since you don't have fans
connected to the motherboard.
> [jscott@vserv ~]$ sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
OK, the above lines are fine.
> VCore: +1.46 V (min = +1.03 V, max = +1.74 V)
> in1: +8.76 V (min = +11.30 V, max = +2.80 V) ALARM
> AVCC: +3.20 V (min = +2.06 V, max = +0.88 V) ALARM
> 3VCC: +3.20 V (min = +1.87 V, max = +0.58 V) ALARM
> in4: +1.48 V (min = +0.34 V, max = +1.20 V) ALARM
> in5: +1.34 V (min = +1.03 V, max = +1.03 V) ALARM
> in6: +4.28 V (min = +5.99 V, max = +3.30 V) ALARM
> VSB: +3.10 V (min = +3.47 V, max = +2.02 V) ALARM
> VBAT: +0.51 V (min = +0.99 V, max = +2.06 V) ALARM
It would be really helpful to match these voltages against voltages in
your BIOS. Also, try to find information on what the min and max for
each should be. The most important ones, of course, are VCore, 3VCC,
VBAT, and 12V (which I don't see there).
This means that the voltages are not being calculated correctly. This
isn't a surprise. The w83627dhg chip reads voltages, but each
motherboard is wired differently, so the voltage arriving at the 'dhg
pins is never the same.
> Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> CPU Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> fan4: 0 RPM (min = 439 RPM, div = 128) ALARM
> fan5: 0 RPM (min = 81 RPM, div = 128) ALARM
So it looks like nothing's connected to your fans. We'll just leave
them there for now.
> Sys Temp: +21°C (high = +58°C, hyst = +78°C)
> CPU Temp: +30.0°C (high = -126.0°C, hyst = +75.5°C)
> AUX Temp: -23.0°C (high = +80.0°C, hyst = +75.0°C)
The temps don't look right. I think coretemp is reporting the right
temperature, and sensors.conf will need to scale the temps it gets
(which are just voltages) to match coretemp.
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0: +54°C (high = +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1: +51°C (high = +100°C)
>
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2: +49°C (high = +100°C)
>
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3: +52°C (high = +100°C)
>
> [jscott@vserv ~]$
>
>
>
> [jscott@vserv ~]$ cat /etc/sysconfig/lm_sensors
> ...
> #
> # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
> MODULE_0=w83627ehf
> MODULE_1=coretemp
> [jscott@vserv ~]$
Well, that's a start. Please reply with information about what chips
you have (you can run 'lspci -n' for that) and look at your BIOS setup
screen for voltages and temperatures. The numbers reported by BIOS
will be the most accurate. We'll try to match those numbers in
sensors.
HTH,
David
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
2007-10-19 18:33 ` Hans de Goede
2007-10-19 18:34 ` David Hubbard
@ 2007-10-19 18:50 ` JAMES SCOTT
2007-10-19 18:54 ` Hans de Goede
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: JAMES SCOTT @ 2007-10-19 18:50 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 5708 bytes --]
See inline comments
----- Original Message ----
From: David Hubbard <david.c.hubbard@gmail.com>
To: James Scott Jr <skoona@verizon.net>; lm-sensors@lm-sensors.org
Sent: Friday, October 19, 2007 2:34:54 PM
Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
Hi James,
> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output from sensors is
> wrong. Is there a preformatted config file for these mainboard somewhere
> that I can find? Or can you give me a hit on what I need to know in order
> to create/adjust one?
I think you'll need to create one. I haven't seen any emails on the
lm-sensors list about your motherboard.
Creating a new config file isn't too hard. Look at the man page for
sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf
You should also have one already (maybe in /etc/sensors.conf) and
reading it is very helpful.
yes, I have a /etc/sensors.conf with an entry for w83627dhg-isa-*, but not coretemp-isa-*
> The cpu cores are really in the high 30's, cpu & case fans are not
> present, ....
I'm looking at the IP32 pro manual, page 11, and I see six fans
(CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
fans, which makes me wonder if your southbridge (possibly an Intel
ICH9) is controlling one fan. Do you have zero fans connected? Or just
one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
Guru Panel." Do you have a uguru on the motherboard? (I'm not really
familiar with abit's uguru, but there are some other people here on
lm-sensors who know a lot more about it.)
I have a cpu fan, and case fan in their labeled position. I will be adding a memory cooler fan later in the aux1 fan position. all other positions are empty. No uguru as uguru is a windows app.
The sensors.conf file we figure out here, for the sake of all IP32 pro
users, should probably not disable the fan input readings and alarms.
But if you want, you can set "ignore" statements for all the fans, so
they don't show up in the sensors output, since you don't have fans
connected to the motherboard.
> [jscott@vserv ~]$ sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
OK, the above lines are fine.
> VCore: +1.46 V (min = +1.03 V, max = +1.74 V)
> in1: +8.76 V (min = +11.30 V, max = +2.80 V) ALARM
> AVCC: +3.20 V (min = +2.06 V, max = +0.88 V) ALARM
> 3VCC: +3.20 V (min = +1.87 V, max = +0.58 V) ALARM
> in4: +1.48 V (min = +0.34 V, max = +1.20 V) ALARM
> in5: +1.34 V (min = +1.03 V, max = +1.03 V) ALARM
> in6: +4.28 V (min = +5.99 V, max = +3.30 V) ALARM
> VSB: +3.10 V (min = +3.47 V, max = +2.02 V) ALARM
> VBAT: +0.51 V (min = +0.99 V, max = +2.06 V) ALARM
It would be really helpful to match these voltages against voltages in
your BIOS. Also, try to find information on what the min and max for
each should be. The most important ones, of course, are VCore, 3VCC,
VBAT, and 12V (which I don't see there).
I will get those data points later tonight when I get home. I remember VCore being 1.33V though.
This means that the voltages are not being calculated correctly. This
isn't a surprise. The w83627dhg chip reads voltages, but each
motherboard is wired differently, so the voltage arriving at the 'dhg
pins is never the same.
> Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> CPU Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> fan4: 0 RPM (min = 439 RPM, div = 128) ALARM
> fan5: 0 RPM (min = 81 RPM, div = 128) ALARM
So it looks like nothing's connected to your fans. We'll just leave
them there for now.
CPU fan is a 100mm and case fan is a 80mm fan.
> Sys Temp: +21°C (high = +58°C, hyst = +78°C)
> CPU Temp: +30.0°C (high = -126.0°C, hyst = +75.5°C)
> AUX Temp: -23.0°C (high = +80.0°C, hyst = +75.0°C)
The temps don't look right. I think coretemp is reporting the right
temperature, and sensors.conf will need to scale the temps it gets
(which are just voltages) to match coretemp.
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0: +54°C (high = +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1: +51°C (high = +100°C)
>
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2: +49°C (high = +100°C)
>
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3: +52°C (high = +100°C)
>
> [jscott@vserv ~]$
>
>
>
> [jscott@vserv ~]$ cat /etc/sysconfig/lm_sensors
> ...
> #
> # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
> MODULE_0=w83627ehf
> MODULE_1=coretemp
> [jscott@vserv ~]$
Well, that's a start. Please reply with information about what chips
you have (you can run 'lspci -n' for that) and look at your BIOS setup
screen for voltages and temperatures. The numbers reported by BIOS
will be the most accurate. We'll try to match those numbers in
sensors.
HTH,
David
Ok, thanks.
I will post the bios temps, speeds, and voltage values, along with my sensors.conf file. I should mention I am planning to use gkrellm; but I need sensors to read right before adjusting it. Question: As I think about the list of ports 'in1, in2, etc' that are contained in the sensors.conf file. How do I determine all the ports available as a starting template - is their a tool that can enum what's available from the chip? before I verify that the correct labels and computes are applied?
James,
[-- Attachment #1.2: Type: text/html, Size: 8305 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (2 preceding siblings ...)
2007-10-19 18:50 ` JAMES SCOTT
@ 2007-10-19 18:54 ` Hans de Goede
2007-10-19 19:00 ` David Hubbard
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2007-10-19 18:54 UTC (permalink / raw)
To: lm-sensors
James,
Didn't you get my mail? I really believe you are on a dead trail here and that
your efforts will be in vane. Repeating myself:
Abit usually does not use the sensors of the super io chip (which the w83627dhg
is), instead they use their own solution called uguru. There is a driver for
this, but the uguru isn't detected by sensors-detect.
Try modprobe abituguru3, and then try running sensors again.
The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
this kernel for F-7 do:
yum update --enable-repo=updates-testing kernel
After rebooting into the new kernel do
modprobe abituguru3
sensors
Regards,
Hans (the author of the abituguru and abituguru3 drivers)
JAMES SCOTT wrote:
> See inline comments
>
> ----- Original Message ----
> From: David Hubbard <david.c.hubbard@gmail.com>
> To: James Scott Jr <skoona@verizon.net>; lm-sensors@lm-sensors.org
> Sent: Friday, October 19, 2007 2:34:54 PM
> Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
>
> Hi James,
>
>> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
>> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output from sensors is
>> wrong. Is there a preformatted config file for these mainboard somewhere
>> that I can find? Or can you give me a hit on what I need to know in order
>> to create/adjust one?
>
> I think you'll need to create one. I haven't seen any emails on the
> lm-sensors list about your motherboard.
>
> Creating a new config file isn't too hard. Look at the man page for
> sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf
>
> You should also have one already (maybe in /etc/sensors.conf) and
> reading it is very helpful.
>
> yes, I have a /etc/sensors.conf with an entry for w83627dhg-isa-*, but not coretemp-isa-*
>
>> The cpu cores are really in the high 30's, cpu & case fans are not
>> present, ....
>
> I'm looking at the IP32 pro manual, page 11, and I see six fans
> (CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
> fans, which makes me wonder if your southbridge (possibly an Intel
> ICH9) is controlling one fan. Do you have zero fans connected? Or just
> one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
> Guru Panel." Do you have a uguru on the motherboard? (I'm not really
> familiar with abit's uguru, but there are some other people here on
> lm-sensors who know a lot more about it.)
>
> I have a cpu fan, and case fan in their labeled position. I will be adding a memory cooler fan later in the aux1 fan position. all other positions are empty. No uguru as uguru is a windows app.
>
> The sensors.conf file we figure out here, for the sake of all IP32 pro
> users, should probably not disable the fan input readings and alarms.
> But if you want, you can set "ignore" statements for all the fans, so
> they don't show up in the sensors output, since you don't have fans
> connected to the motherboard.
>
>> [jscott@vserv ~]$ sensors
>> w83627dhg-isa-0290
>> Adapter: ISA adapter
>
> OK, the above lines are fine.
>
>> VCore: +1.46 V (min = +1.03 V, max = +1.74 V)
>> in1: +8.76 V (min = +11.30 V, max = +2.80 V) ALARM
>> AVCC: +3.20 V (min = +2.06 V, max = +0.88 V) ALARM
>> 3VCC: +3.20 V (min = +1.87 V, max = +0.58 V) ALARM
>> in4: +1.48 V (min = +0.34 V, max = +1.20 V) ALARM
>> in5: +1.34 V (min = +1.03 V, max = +1.03 V) ALARM
>> in6: +4.28 V (min = +5.99 V, max = +3.30 V) ALARM
>> VSB: +3.10 V (min = +3.47 V, max = +2.02 V) ALARM
>> VBAT: +0.51 V (min = +0.99 V, max = +2.06 V) ALARM
>
> It would be really helpful to match these voltages against voltages in
> your BIOS. Also, try to find information on what the min and max for
> each should be. The most important ones, of course, are VCore, 3VCC,
> VBAT, and 12V (which I don't see there).
>
> I will get those data points later tonight when I get home. I remember VCore being 1.33V though.
>
> This means that the voltages are not being calculated correctly. This
> isn't a surprise. The w83627dhg chip reads voltages, but each
> motherboard is wired differently, so the voltage arriving at the 'dhg
> pins is never the same.
>
>> Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> CPU Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> fan4: 0 RPM (min = 439 RPM, div = 128) ALARM
>> fan5: 0 RPM (min = 81 RPM, div = 128) ALARM
>
> So it looks like nothing's connected to your fans. We'll just leave
> them there for now.
>
> CPU fan is a 100mm and case fan is a 80mm fan.
>
>> Sys Temp: +21°C (high = +58°C, hyst = +78°C)
>> CPU Temp: +30.0°C (high = -126.0°C, hyst = +75.5°C)
>> AUX Temp: -23.0°C (high = +80.0°C, hyst = +75.0°C)
>
> The temps don't look right. I think coretemp is reporting the right
> temperature, and sensors.conf will need to scale the temps it gets
> (which are just voltages) to match coretemp.
>
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0: +54°C (high = +100°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1: +51°C (high = +100°C)
>>
>> coretemp-isa-0002
>> Adapter: ISA adapter
>> Core 2: +49°C (high = +100°C)
>>
>> coretemp-isa-0003
>> Adapter: ISA adapter
>> Core 3: +52°C (high = +100°C)
>>
>> [jscott@vserv ~]$
>>
>>
>>
>> [jscott@vserv ~]$ cat /etc/sysconfig/lm_sensors
>> ...
>> #
>> # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
>> MODULE_0=w83627ehf
>> MODULE_1=coretemp
>> [jscott@vserv ~]$
>
> Well, that's a start. Please reply with information about what chips
> you have (you can run 'lspci -n' for that) and look at your BIOS setup
> screen for voltages and temperatures. The numbers reported by BIOS
> will be the most accurate. We'll try to match those numbers in
> sensors.
>
> HTH,
> David
>
> Ok, thanks.
>
> I will post the bios temps, speeds, and voltage values, along with my sensors.conf file. I should mention I am planning to use gkrellm; but I need sensors to read right before adjusting it. Question: As I think about the list of ports 'in1, in2, etc' that are contained in the sensors.conf file. How do I determine all the ports available as a starting template - is their a tool that can enum what's available from the chip? before I verify that the correct labels and computes are applied?
>
> James,
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (3 preceding siblings ...)
2007-10-19 18:54 ` Hans de Goede
@ 2007-10-19 19:00 ` David Hubbard
2007-10-19 19:00 ` JAMES SCOTT
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: David Hubbard @ 2007-10-19 19:00 UTC (permalink / raw)
To: lm-sensors
Hi James,
Hans is right. And he's the one I was thinking knew about the uguru.
There *is* linux support. It's pretty good. So I'd guess that the
w83627dhg is being used for its other LPC features (floppy controller,
RTC, I can't remember then all). The sensor part of that chip is not
wired at all, or may be wired up only a little. The uguru will have
most (probably all) of the sensors stuff you're looking for.
Unfortunately, I'm only experienced with the w83627dhg. Hans can help
you though.
David
On 10/19/07, Hans de Goede <j.w.r.degoede@hhs.nl> wrote:
> James,
>
> Didn't you get my mail? I really believe you are on a dead trail here and that
> your efforts will be in vane. Repeating myself:
>
> Abit usually does not use the sensors of the super io chip (which the w83627dhg
> is), instead they use their own solution called uguru. There is a driver for
> this, but the uguru isn't detected by sensors-detect.
>
> Try modprobe abituguru3, and then try running sensors again.
>
> The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
> this kernel for F-7 do:
> yum update --enable-repo=updates-testing kernel
>
> After rebooting into the new kernel do
> modprobe abituguru3
> sensors
>
>
> Regards,
>
> Hans (the author of the abituguru and abituguru3 drivers)
>
>
>
>
> JAMES SCOTT wrote:
> > See inline comments
> >
> > ----- Original Message ----
> > From: David Hubbard <david.c.hubbard@gmail.com>
> > To: James Scott Jr <skoona@verizon.net>; lm-sensors@lm-sensors.org
> > Sent: Friday, October 19, 2007 2:34:54 PM
> > Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
> >
> > Hi James,
> >
> >> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
> >> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output from sensors is
> >> wrong. Is there a preformatted config file for these mainboard somewhere
> >> that I can find? Or can you give me a hit on what I need to know in order
> >> to create/adjust one?
> >
> > I think you'll need to create one. I haven't seen any emails on the
> > lm-sensors list about your motherboard.
> >
> > Creating a new config file isn't too hard. Look at the man page for
> > sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf
> >
> > You should also have one already (maybe in /etc/sensors.conf) and
> > reading it is very helpful.
> >
> > yes, I have a /etc/sensors.conf with an entry for w83627dhg-isa-*, but not coretemp-isa-*
> >
> >> The cpu cores are really in the high 30's, cpu & case fans are not
> >> present, ....
> >
> > I'm looking at the IP32 pro manual, page 11, and I see six fans
> > (CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
> > fans, which makes me wonder if your southbridge (possibly an Intel
> > ICH9) is controlling one fan. Do you have zero fans connected? Or just
> > one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
> > Guru Panel." Do you have a uguru on the motherboard? (I'm not really
> > familiar with abit's uguru, but there are some other people here on
> > lm-sensors who know a lot more about it.)
> >
> > I have a cpu fan, and case fan in their labeled position. I will be adding a memory cooler fan later in the aux1 fan position. all other positions are empty. No uguru as uguru is a windows app.
> >
> > The sensors.conf file we figure out here, for the sake of all IP32 pro
> > users, should probably not disable the fan input readings and alarms.
> > But if you want, you can set "ignore" statements for all the fans, so
> > they don't show up in the sensors output, since you don't have fans
> > connected to the motherboard.
> >
> >> [jscott@vserv ~]$ sensors
> >> w83627dhg-isa-0290
> >> Adapter: ISA adapter
> >
> > OK, the above lines are fine.
> >
> >> VCore: +1.46 V (min = +1.03 V, max = +1.74 V)
> >> in1: +8.76 V (min = +11.30 V, max = +2.80 V) ALARM
> >> AVCC: +3.20 V (min = +2.06 V, max = +0.88 V) ALARM
> >> 3VCC: +3.20 V (min = +1.87 V, max = +0.58 V) ALARM
> >> in4: +1.48 V (min = +0.34 V, max = +1.20 V) ALARM
> >> in5: +1.34 V (min = +1.03 V, max = +1.03 V) ALARM
> >> in6: +4.28 V (min = +5.99 V, max = +3.30 V) ALARM
> >> VSB: +3.10 V (min = +3.47 V, max = +2.02 V) ALARM
> >> VBAT: +0.51 V (min = +0.99 V, max = +2.06 V) ALARM
> >
> > It would be really helpful to match these voltages against voltages in
> > your BIOS. Also, try to find information on what the min and max for
> > each should be. The most important ones, of course, are VCore, 3VCC,
> > VBAT, and 12V (which I don't see there).
> >
> > I will get those data points later tonight when I get home. I remember VCore being 1.33V though.
> >
> > This means that the voltages are not being calculated correctly. This
> > isn't a surprise. The w83627dhg chip reads voltages, but each
> > motherboard is wired differently, so the voltage arriving at the 'dhg
> > pins is never the same.
> >
> >> Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> >> CPU Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> >> Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
> >> fan4: 0 RPM (min = 439 RPM, div = 128) ALARM
> >> fan5: 0 RPM (min = 81 RPM, div = 128) ALARM
> >
> > So it looks like nothing's connected to your fans. We'll just leave
> > them there for now.
> >
> > CPU fan is a 100mm and case fan is a 80mm fan.
> >
> >> Sys Temp: +21°C (high = +58°C, hyst = +78°C)
> >> CPU Temp: +30.0°C (high = -126.0°C, hyst = +75.5°C)
> >> AUX Temp: -23.0°C (high = +80.0°C, hyst = +75.0°C)
> >
> > The temps don't look right. I think coretemp is reporting the right
> > temperature, and sensors.conf will need to scale the temps it gets
> > (which are just voltages) to match coretemp.
> >
> >> coretemp-isa-0000
> >> Adapter: ISA adapter
> >> Core 0: +54°C (high = +100°C)
> >>
> >> coretemp-isa-0001
> >> Adapter: ISA adapter
> >> Core 1: +51°C (high = +100°C)
> >>
> >> coretemp-isa-0002
> >> Adapter: ISA adapter
> >> Core 2: +49°C (high = +100°C)
> >>
> >> coretemp-isa-0003
> >> Adapter: ISA adapter
> >> Core 3: +52°C (high = +100°C)
> >>
> >> [jscott@vserv ~]$
> >>
> >>
> >>
> >> [jscott@vserv ~]$ cat /etc/sysconfig/lm_sensors
> >> ...
> >> #
> >> # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
> >> MODULE_0=w83627ehf
> >> MODULE_1=coretemp
> >> [jscott@vserv ~]$
> >
> > Well, that's a start. Please reply with information about what chips
> > you have (you can run 'lspci -n' for that) and look at your BIOS setup
> > screen for voltages and temperatures. The numbers reported by BIOS
> > will be the most accurate. We'll try to match those numbers in
> > sensors.
> >
> > HTH,
> > David
> >
> > Ok, thanks.
> >
> > I will post the bios temps, speeds, and voltage values, along with my sensors.conf file. I should mention I am planning to use gkrellm; but I need sensors to read right before adjusting it. Question: As I think about the list of ports 'in1, in2, etc' that are contained in the sensors.conf file. How do I determine all the ports available as a starting template - is their a tool that can enum what's available from the chip? before I verify that the correct labels and computes are applied?
> >
> > James,
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > lm-sensors mailing list
> > lm-sensors@lm-sensors.org
> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (4 preceding siblings ...)
2007-10-19 19:00 ` David Hubbard
@ 2007-10-19 19:00 ` JAMES SCOTT
2007-10-19 19:25 ` JAMES SCOTT
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: JAMES SCOTT @ 2007-10-19 19:00 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1273 bytes --]
Hans,
That makes sense to me, I will try it tonight. thanks.
James,
----- Original Message ----
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: James Scott Jr <skoona@verizon.net>
Cc: lm-sensors@lm-sensors.org
Sent: Friday, October 19, 2007 2:33:46 PM
Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
James Scott Jr wrote:
> Folks,
>
> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro
> mainboard, using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output
> from sensors is wrong. Is there a preformatted config file for these
> mainboard somewhere that I can find? Or can you give me a hit on what I
> need to know in order to create/adjust one?
>
Abit usually does not use the sensors of the super io chip (which the w83627dhg
is), instead they use their own solution called uguru. There is a driver for
this, but the uguru isn't detected by sensors-detect.
Try modprobe abituguru3, and then try running sensors again.
The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
this kernel for F-7 do:
yum update --enable-repo=updates-testing kernel
After rebooting into the new kernel do
modprobe abituguru3
sensors
Regards,
Hans
[-- Attachment #1.2: Type: text/html, Size: 1811 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (5 preceding siblings ...)
2007-10-19 19:00 ` JAMES SCOTT
@ 2007-10-19 19:25 ` JAMES SCOTT
2007-10-19 19:26 ` Hans de Goede
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: JAMES SCOTT @ 2007-10-19 19:25 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 7614 bytes --]
Hans,
I got your mail - we were a little out of sync. Around 7:00pm EDT I should have completed your suggestions - with great expectations I might add.
Thanks,
James,
Note: I saw the patch messages too. I may try both if needed. I don't have DDR3 memory, so I'm thinking I may not benefit from the patch - but I have it if needed.
----- Original Message ----
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: JAMES SCOTT <skoona@verizon.net>
Cc: David Hubbard <david.c.hubbard@gmail.com>; lm-sensors@lm-sensors.org
Sent: Friday, October 19, 2007 2:54:16 PM
Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
James,
Didn't you get my mail? I really believe you are on a dead trail here and that
your efforts will be in vane. Repeating myself:
Abit usually does not use the sensors of the super io chip (which the w83627dhg
is), instead they use their own solution called uguru. There is a driver for
this, but the uguru isn't detected by sensors-detect.
Try modprobe abituguru3, and then try running sensors again.
The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
this kernel for F-7 do:
yum update --enable-repo=updates-testing kernel
After rebooting into the new kernel do
modprobe abituguru3
sensors
Regards,
Hans (the author of the abituguru and abituguru3 drivers)
JAMES SCOTT wrote:
> See inline comments
>
> ----- Original Message ----
> From: David Hubbard <david.c.hubbard@gmail.com>
> To: James Scott Jr <skoona@verizon.net>; lm-sensors@lm-sensors.org
> Sent: Friday, October 19, 2007 2:34:54 PM
> Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
>
> Hi James,
>
>> I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
>> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output from sensors is
>> wrong. Is there a preformatted config file for these mainboard somewhere
>> that I can find? Or can you give me a hit on what I need to know in order
>> to create/adjust one?
>
> I think you'll need to create one. I haven't seen any emails on the
> lm-sensors list about your motherboard.
>
> Creating a new config file isn't too hard. Look at the man page for
> sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf
>
> You should also have one already (maybe in /etc/sensors.conf) and
> reading it is very helpful.
>
> yes, I have a /etc/sensors.conf with an entry for w83627dhg-isa-*, but not coretemp-isa-*
>
>> The cpu cores are really in the high 30's, cpu & case fans are not
>> present, ....
>
> I'm looking at the IP32 pro manual, page 11, and I see six fans
> (CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
> fans, which makes me wonder if your southbridge (possibly an Intel
> ICH9) is controlling one fan. Do you have zero fans connected? Or just
> one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
> Guru Panel." Do you have a uguru on the motherboard? (I'm not really
> familiar with abit's uguru, but there are some other people here on
> lm-sensors who know a lot more about it.)
>
> I have a cpu fan, and case fan in their labeled position. I will be adding a memory cooler fan later in the aux1 fan position. all other positions are empty. No uguru as uguru is a windows app.
>
> The sensors.conf file we figure out here, for the sake of all IP32 pro
> users, should probably not disable the fan input readings and alarms.
> But if you want, you can set "ignore" statements for all the fans, so
> they don't show up in the sensors output, since you don't have fans
> connected to the motherboard.
>
>> [jscott@vserv ~]$ sensors
>> w83627dhg-isa-0290
>> Adapter: ISA adapter
>
> OK, the above lines are fine.
>
>> VCore: +1.46 V (min = +1.03 V, max = +1.74 V)
>> in1: +8.76 V (min = +11.30 V, max = +2.80 V) ALARM
>> AVCC: +3.20 V (min = +2.06 V, max = +0.88 V) ALARM
>> 3VCC: +3.20 V (min = +1.87 V, max = +0.58 V) ALARM
>> in4: +1.48 V (min = +0.34 V, max = +1.20 V) ALARM
>> in5: +1.34 V (min = +1.03 V, max = +1.03 V) ALARM
>> in6: +4.28 V (min = +5.99 V, max = +3.30 V) ALARM
>> VSB: +3.10 V (min = +3.47 V, max = +2.02 V) ALARM
>> VBAT: +0.51 V (min = +0.99 V, max = +2.06 V) ALARM
>
> It would be really helpful to match these voltages against voltages in
> your BIOS. Also, try to find information on what the min and max for
> each should be. The most important ones, of course, are VCore, 3VCC,
> VBAT, and 12V (which I don't see there).
>
> I will get those data points later tonight when I get home. I remember VCore being 1.33V though.
>
> This means that the voltages are not being calculated correctly. This
> isn't a surprise. The w83627dhg chip reads voltages, but each
> motherboard is wired differently, so the voltage arriving at the 'dhg
> pins is never the same.
>
>> Case Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> CPU Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> Aux Fan: 0 RPM (min = 10546 RPM, div = 128) ALARM
>> fan4: 0 RPM (min = 439 RPM, div = 128) ALARM
>> fan5: 0 RPM (min = 81 RPM, div = 128) ALARM
>
> So it looks like nothing's connected to your fans. We'll just leave
> them there for now.
>
> CPU fan is a 100mm and case fan is a 80mm fan.
>
>> Sys Temp: +21°C (high = +58°C, hyst = +78°C)
>> CPU Temp: +30.0°C (high = -126.0°C, hyst = +75.5°C)
>> AUX Temp: -23.0°C (high = +80.0°C, hyst = +75.0°C)
>
> The temps don't look right. I think coretemp is reporting the right
> temperature, and sensors.conf will need to scale the temps it gets
> (which are just voltages) to match coretemp.
>
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0: +54°C (high = +100°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1: +51°C (high = +100°C)
>>
>> coretemp-isa-0002
>> Adapter: ISA adapter
>> Core 2: +49°C (high = +100°C)
>>
>> coretemp-isa-0003
>> Adapter: ISA adapter
>> Core 3: +52°C (high = +100°C)
>>
>> [jscott@vserv ~]$
>>
>>
>>
>> [jscott@vserv ~]$ cat /etc/sysconfig/lm_sensors
>> ...
>> #
>> # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
>> MODULE_0=w83627ehf
>> MODULE_1=coretemp
>> [jscott@vserv ~]$
>
> Well, that's a start. Please reply with information about what chips
> you have (you can run 'lspci -n' for that) and look at your BIOS setup
> screen for voltages and temperatures. The numbers reported by BIOS
> will be the most accurate. We'll try to match those numbers in
> sensors.
>
> HTH,
> David
>
> Ok, thanks.
>
> I will post the bios temps, speeds, and voltage values, along with my sensors.conf file. I should mention I am planning to use gkrellm; but I need sensors to read right before adjusting it. Question: As I think about the list of ports 'in1, in2, etc' that are contained in the sensors.conf file. How do I determine all the ports available as a starting template - is their a tool that can enum what's available from the chip? before I verify that the correct labels and computes are applied?
>
> James,
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
[-- Attachment #1.2: Type: text/html, Size: 10784 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (6 preceding siblings ...)
2007-10-19 19:25 ` JAMES SCOTT
@ 2007-10-19 19:26 ` Hans de Goede
2007-10-20 2:53 ` James Scott Jr
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2007-10-19 19:26 UTC (permalink / raw)
To: lm-sensors
JAMES SCOTT wrote:
> Hans,
>
> I got your mail - we were a little out of sync. Around 7:00pm EDT I should have completed your suggestions - with great expectations I might add.
>
> Thanks,
>
> James,
> Note: I saw the patch messages too. I may try both if needed. I don't have DDR3 memory, so I'm thinking I may not benefit from the patch - but I have it if needed.
>
I don't think you will need it, as the utility download link for you
motherboard links to a version of the windows uguru utility which does not know
about these 2 new boards.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (7 preceding siblings ...)
2007-10-19 19:26 ` Hans de Goede
@ 2007-10-20 2:53 ` James Scott Jr
2007-10-20 20:49 ` Jean Delvare
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: James Scott Jr @ 2007-10-20 2:53 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3777 bytes --]
Hans,
Took me longer to get home than I thought, but I did get it done. Here
is the sensor output.
Thank you, sensor's output is now correct - coretemp's is wacked. I
will look into whats happening with coretemp, later.
[jscott@vserv ~]$ sensors
abituguru3-isa-00e0
Adapter: ISA adapter
CPU Core: +1.23 V (min +0.00 V, max +1.55 V)
DDR2: +1.88 V (min +1.50 V, max +2.30 V)
DDR2 VTT: +0.94 V (min +0.75 V, max +1.15 V)
CPU VTT 1.2V: +1.20 V (min +1.00 V, max +1.50 V)
MCH 1.25V: +1.33 V (min +1.05 V, max +1.55 V)
ICHIO 1.5V: +1.52 V (min +1.20 V, max +1.80 V)
ICH 1.05V: +1.06 V (min +0.85 V, max +1.25 V)
ATX +12V (24-Pin): +12.18 V (min +9.60 V, max +14.40 V)
ATX +12V (8-pin): +12.18 V (min +9.60 V, max +14.40 V)
ATX +5V: +4.98 V (min +3.99 V, max +6.00 V)
+3.3V: +3.26 V (min +2.64 V, max +3.94 V)
5VSB: +5.04 V (min +3.99 V, max +6.00 V)
CPU: +40°C (high = +65°C, crit = +75°C)
System : +33°C (high = +55°C, crit = +65°C)
PWM : +55°C (high = +80°C, crit = +90°C)
PWM Phase2: +0°C (high = +0°C, crit = +255°C)
PWM Phase3: +0°C (high = +0°C, crit = +255°C)
PWM Phase4: +0°C (high = +0°C, crit = +255°C)
PWM Phase5: +0°C (high = +0°C, crit = +255°C)
CPU Fan: 1200 RPM (min 300 RPM)
SYS Fan: 2940 RPM (min 300 RPM)
AUX1 Fan: 0 RPM (min 300 RPM)
AUX2 Fan: 0 RPM (min 300 RPM)
AUX3 Fan: 0 RPM (min 300 RPM)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +54°C (high = +100°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +51°C (high = +100°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +52°C (high = +100°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +50°C (high = +100°C)
[jscott@vserv ~]$ uname -a
Linux vserv 2.6.23.1-4.fc7 #1 SMP Fri Oct 12 21:07:27 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
On Fri, 2007-10-19 at 20:33 +0200, Hans de Goede wrote:
> James Scott Jr wrote:
> > Folks,
> >
> > I have a system with an Intel Q6600 quad core on a ABit IP35 Pro
> > mainboard, using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7. The output
> > from sensors is wrong. Is there a preformatted config file for these
> > mainboard somewhere that I can find? Or can you give me a hit on what I
> > need to know in order to create/adjust one?
> >
>
> Abit usually does not use the sensors of the super io chip (which the w83627dhg
> is), instead they use their own solution called uguru. There is a driver for
> this, but the uguru isn't detected by sensors-detect.
>
> Try modprobe abituguru3, and then try running sensors again.
>
> The abituguru3 driver is only available in kernel 2.6.23 and higher, to install
> this kernel for F-7 do:
> yum update --enable-repo=updates-testing kernel
>
> After rebooting into the new kernel do
> modprobe abituguru3
> sensors
>
>
> Regards,
>
> Hans
James,
a.k.a Skoona
Registered Linux User #270764
FC6 on Dual AMD 2400+ MPs, with ATI-9600SE and LG 1680x1050 20inch
FC7 on Intel Q6600, with GeForce 7200GS and Acer 1680x1050 20inch
Folding@home Team: 37988 FedoraFolders
Author: Gkrellfah2 Folding@Home Linux Monitor
Author: GFHCM GTK Folding@Home Linux Monitor
Author: GapcMon - Linux UPS Status Monitor
Contributor: GIW - Gtk Instrumentation Library
[-- Attachment #1.2: Type: text/html, Size: 8768 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (8 preceding siblings ...)
2007-10-20 2:53 ` James Scott Jr
@ 2007-10-20 20:49 ` Jean Delvare
2007-10-21 13:35 ` JAMES SCOTT
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2007-10-20 20:49 UTC (permalink / raw)
To: lm-sensors
On Fri, 19 Oct 2007 22:53:09 -0400, James Scott Jr wrote:
> Thank you, sensor's output is now correct - coretemp's is wacked. I
> will look into whats happening with coretemp, later.
>
> [jscott@vserv ~]$ sensors
> (...)
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0: +54°C (high = +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1: +51°C (high = +100°C)
>
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2: +52°C (high = +100°C)
>
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3: +50°C (high = +100°C)
>
The coretemp values actually look alright to me.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (9 preceding siblings ...)
2007-10-20 20:49 ` Jean Delvare
@ 2007-10-21 13:35 ` JAMES SCOTT
2007-10-21 13:37 ` Hans de Goede
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: JAMES SCOTT @ 2007-10-21 13:35 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1562 bytes --]
----- Original Message ----
From: Jean Delvare <khali@linux-fr.org>
To: James Scott Jr <skoona@verizon.net>
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>; lm-sensors@lm-sensors.org
Sent: Saturday, October 20, 2007 4:49:01 PM
Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
On Fri, 19 Oct 2007 22:53:09 -0400, James Scott Jr wrote:
> Thank you, sensor's output is now correct - coretemp's is wacked. I
> will look into whats happening with coretemp, later.
>
> [jscott@vserv ~]$ sensors
> (...)
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0: +54°C (high = +100°C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1: +51°C (high = +100°C)
>
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2: +52°C (high = +100°C)
>
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3: +50°C (high = +100°C)
>
The coretemp values actually look alright to me.
Jean; The abituguru3... sensors output showed 'CPU 40c' and coretemp... details the same CPU around '50c'. So, I have output, it is formatted correctly. However, I believe the reported value is wrong. 10c is a huge difference in values - which is correct? All Cores are running Folding@Home at 100%, so this is a load temp and would not be available if I rebooted to bios to verify.
I did not find the coretemp-isa-* in the sensors.conf file. Do you know where the computes for this module are setup?
--
Jean Delvare
[-- Attachment #1.2: Type: text/html, Size: 2683 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (10 preceding siblings ...)
2007-10-21 13:35 ` JAMES SCOTT
@ 2007-10-21 13:37 ` Hans de Goede
2007-10-21 18:43 ` Jean Delvare
2007-10-22 2:11 ` James Scott Jr
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2007-10-21 13:37 UTC (permalink / raw)
To: lm-sensors
JAMES SCOTT wrote:
>
> ----- Original Message ----
> From: Jean Delvare <khali@linux-fr.org>
> To: James Scott Jr <skoona@verizon.net>
> Cc: Hans de Goede <j.w.r.degoede@hhs.nl>; lm-sensors@lm-sensors.org
> Sent: Saturday, October 20, 2007 4:49:01 PM
> Subject: Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
>
> On Fri, 19 Oct 2007 22:53:09 -0400, James Scott Jr wrote:
>> Thank you, sensor's output is now correct - coretemp's is wacked. I
>> will look into whats happening with coretemp, later.
>>
>> [jscott@vserv ~]$ sensors
>> (...)
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0: +54°C (high = +100°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1: +51°C (high = +100°C)
>>
>> coretemp-isa-0002
>> Adapter: ISA adapter
>> Core 2: +52°C (high = +100°C)
>>
>> coretemp-isa-0003
>> Adapter: ISA adapter
>> Core 3: +50°C (high = +100°C)
>>
>
> The coretemp values actually look alright to me.
>
> Jean; The abituguru3... sensors output showed 'CPU 40c' and coretemp... details the same CPU around '50c'. So, I have output, it is formatted correctly. However, I believe the reported value is wrong. 10c is a huge difference in values - which is correct? All Cores are running Folding@Home at 100%, so this is a load temp and would not be available if I rebooted to bios to verify.
>
> I did not find the coretemp-isa-* in the sensors.conf file. Do you know where the computes for this module are setup?
James,
For some reason later versions of the uguru (and earlier versions too after a
BIOS update) seem to report much too low CPU temp values. I guess they are
reporting the actual sensor value and adding some offset to compensate for the
distance between the sensor on the motherboard and the actual CPU.
So I think the core temp readings are correct, esp. for a loaded system.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (11 preceding siblings ...)
2007-10-21 13:37 ` Hans de Goede
@ 2007-10-21 18:43 ` Jean Delvare
2007-10-22 2:11 ` James Scott Jr
13 siblings, 0 replies; 15+ messages in thread
From: Jean Delvare @ 2007-10-21 18:43 UTC (permalink / raw)
To: lm-sensors
On Sun, 21 Oct 2007 06:35:05 -0700 (PDT), JAMES SCOTT wrote:
> Jean; The abituguru3... sensors output showed 'CPU 40c' and coretemp...
> details the same CPU around '50c'. So, I have output, it is formatted
> correctly. However, I believe the reported value is wrong. 10c is a
> huge difference in values - which is correct?
10°C isn't that big, it really depends what the different sensors
measure exactly. It is possible that all temperatures are correct and
just not measuring the same thing. The coretemp driver reports the CPU
core temperature, which is presumably the hottest point of the CPU. The
abituguru driver, OTOH, may be reporting the temperature in the CPU
socket, or the temperature of a thermal diode close to the CPU or
inside the CPU but not in the core. It is expected that the reported
temperature is lower.
> I did not find the coretemp-isa-* in the sensors.conf file. Do you
> know where the computes for this module are setup?
No computes are needed for the coretemp, the temperatures are reported
directly by the driver.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors'
2007-10-19 18:01 [lm-sensors] ABIT IP35 Pro mainboard wrong values from 'sensors' James Scott Jr
` (12 preceding siblings ...)
2007-10-21 18:43 ` Jean Delvare
@ 2007-10-22 2:11 ` James Scott Jr
13 siblings, 0 replies; 15+ messages in thread
From: James Scott Jr @ 2007-10-22 2:11 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
Jean,
Thanks for the update on how and where the coretemp-* module gets its
values. Understanding this makes the 10°C not seems too great a
difference.
James,
On Sun, 2007-10-21 at 20:43 +0200, Jean Delvare wrote:
> On Sun, 21 Oct 2007 06:35:05 -0700 (PDT), JAMES SCOTT wrote:
> > Jean; The abituguru3... sensors output showed 'CPU 40c' and coretemp...
> > details the same CPU around '50c'. So, I have output, it is formatted
> > correctly. However, I believe the reported value is wrong. 10c is a
> > huge difference in values - which is correct?
>
> 10°C isn't that big, it really depends what the different sensors
> measure exactly. It is possible that all temperatures are correct and
> just not measuring the same thing. The coretemp driver reports the CPU
> core temperature, which is presumably the hottest point of the CPU. The
> abituguru driver, OTOH, may be reporting the temperature in the CPU
> socket, or the temperature of a thermal diode close to the CPU or
> inside the CPU but not in the core. It is expected that the reported
> temperature is lower.
>
> > I did not find the coretemp-isa-* in the sensors.conf file. Do you
> > know where the computes for this module are setup?
>
> No computes are needed for the coretemp, the temperatures are reported
> directly by the driver.
>
[-- Attachment #1.2: Type: text/html, Size: 2130 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread