* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
@ 2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Mark D. Studebaker @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
try modprobing i2c-isa then it should work.
Charles Bailey wrote:
> Tried CVS i2c lk-24 and lm_sensors2 per your reply. Both build and
> install fine. ./prog/detect/sensors-detect again picks up the AMD768,
> but fails loading i2c-amd756, apparently because it's now in
> i2c/busses. It also fails to locate the 627HF, both before and after
> the amd756 module is loaded manually (not that that should matter,
> afaict). If I load modules manually, yielding
>
> Module Size Used by Not tainted
> w83627hf 13044 0 (unused)
> i2c-proc 8116 0 [w83627hf]
> i2c-amd756 3848 0
> i2c-dev 4992 0
> i2c-core 20164 0 [w83627hf i2c-proc i2c-amd756 i2c-dev]
>
> I still have no luck:
>
> [bailey@XXX ~]% /usr/local/bin/sensors
> No sensors found!
>
> If I add the eeprom chip driver, I get little more:
>
> [bailey@XXX ~]% /usr/local/bin/sensors
> eeprom-i2c-0-50
> Adapter: SMBus AMD75x adapter at 06e0
> Algorithm: Non-I2C SMBus adapter
> Memory type: DDR SDRAM DIMM SPD
> Memory size (MB): 512
>
> eeprom-i2c-0-51
> Adapter: SMBus AMD75x adapter at 06e0
> Algorithm: Non-I2C SMBus adapter
>
> [bailey@XXX ~]%
>
> I'm happy to test changes or provide additional data if that would help.
>
> --
> Regards,
> Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
> Fellow, Pediatric Hematology/Oncology
> Children's Hospital of Philadelphia/University of Pennsylvania
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
2005-05-19 6:24 ` Mark D. Studebaker
@ 2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Charles Bailey
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Jean Delvare @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
> OK, I've installed 2.8.0, which auto-detects the sensor, but still
> seems to have problems with the temp:
> (snip)
> eeprom-i2c-0-51
> Adapter: SMBus AMD75x adapter at 06e0
> Algorithm: Non-I2C SMBus adapter
> Machine name:
> H
> Serial number:
> H
Don't you care about these ones, it's a known bug (my fault) and fixed
in CVS.
> (snip)
> temp1: +25C (limit = +60C) sensor > thermistor temp2: +58.5C (limit = +60C, hysteresis = +50C)
> sensor = PII/Celeron diode ALARM
> temp3: +60.0C (limit = +60C, hysteresis = +50C) sensor > PII/Celeron diode ALARM
I can see in the configuration file that the sensor types can be
changed. Maybe the default configuration doesn't match your hardware.
Did you try changing these values in the config file (section
w83627hf-*, uncomment the lines), maybe it would give interesting
results?
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
@ 2005-05-19 6:24 ` Charles Bailey
2005-05-19 6:24 ` Charles Bailey
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Charles Bailey @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
--On Wednesday, August 13, 2003 01:20:30 AM +0200 Jean Delvare
<khali@linux-fr.org> wrote:
>
>> This does get a sensor running; it reports CPU temps of ~60 C. When
>> I finally had a chance to take the server down and check via the
>> BIOS, it reported temps in the mid-30s.
>>
>> The voltages and fan speeds reported via i2c seem to be reasonable
>> numbers.
>
> If you aren't using 2.8.0 yet, upgrading could help (and at least we'll
> make sure we aren't trying to fix a bug that was already corrected).
OK, I've installed 2.8.0, which auto-detects the sensor, but still seems to
have problems with the temp:
[root@xxx rc.d]# /usr/local/bin/sensors
eeprom-i2c-0-50
Adapter: SMBus AMD75x adapter at 06e0
Algorithm: Non-I2C SMBus adapter
eeprom-i2c-0-51
Adapter: SMBus AMD75x adapter at 06e0
Algorithm: Non-I2C SMBus adapter
Machine name:
H
Serial number:
H
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.71 V (min = +1.74 V, max = +1.93 V) ALARM
VCore 2: +2.49 V (min = +1.74 V, max = +1.93 V)
+3.3V: +3.28 V (min = +3.13 V, max = +3.45 V)
+5V: +4.94 V (min = +4.72 V, max = +5.24 V)
+12V: +12.27 V (min = +10.79 V, max = +13.19 V)
-12V: -12.70 V (min = -13.21 V, max = -10.90 V)
-5V: -5.01 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.39 V (min = +4.72 V, max = +5.24 V) ALARM
VBat: +3.48 V (min = +2.40 V, max = +3.60 V) ALARM
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 4500 RPM (min = 3000 RPM, div = 2)
fan3: 5400 RPM (min = 3000 RPM, div = 2)
temp1: +25C (limit = +60C) sensor = thermistor
temp2: +58.5C (limit = +60C, hysteresis = +50C) sensor = PII/Celeron
diode ALARM
temp3: +60.0C (limit = +60C, hysteresis = +50C) sensor = PII/Celeron
diode ALARM
vid: +1.850 V
alarms:
beep_enable:
Sound alarm disabled
[root@xxx rc.d]# uname -a
Linux xxx.med.upenn.edu 2.4.20-19.9smp #1 SMP Tue Jul 15 16:45:28 EDT 2003
i686 athlon i386 GNU/Linux
[root@xxx rc.d]#
The BIOS reported the CPU temps as 35 and 38 about twenty minutes previous
when I rebooted to install a new kernel.
I'm happy to do further testing if you have any suggestions.
--
Regards,
Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
Fellow, Pediatric Hematology/Oncology
Children's Hospital of Philadelphia/University of Pennsylvania
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
` (2 preceding siblings ...)
2005-05-19 6:24 ` Charles Bailey
@ 2005-05-19 6:24 ` Charles Bailey
2005-05-19 6:24 ` Jean Delvare
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Charles Bailey @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
--On Thursday, August 14, 2003 09:42:15 PM +0200 Jean Delvare
<khali@linux-fr.org> wrote:
>> (snip)
>> temp1: +25C (limit = +60C) sensor >> thermistor temp2: +58.5C (limit = +60C, hysteresis = +50C)
>> sensor = PII/Celeron diode ALARM
>> temp3: +60.0C (limit = +60C, hysteresis = +50C) sensor >> PII/Celeron diode ALARM
>
> I can see in the configuration file that the sensor types can be
> changed. Maybe the default configuration doesn't match your hardware.
> Did you try changing these values in the config file (section
> w83627hf-*, uncomment the lines), maybe it would give interesting
> results?
Thanks. Changing the settings seems to help:
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
[snip]
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 4530 RPM (min = 3000 RPM, div = 2)
fan3: 5443 RPM (min = 3000 RPM, div = 2)
temp1: +127C (limit = +60C) sensor =
PII/Celeron diode ALARM
temp2: +36.5C (limit = +60C, hysteresis = +50C) sensor = 3904
transistor
temp3: +42.0C (limit = +60C, hysteresis = +50C) sensor = 3904
transistor
temp2 and temp3 look like they're in the range of the values the BIOS
reported. (I can't shut the machine down again until tomorrow to check the
BIOS directly, but I'll let you know if there's a difference.)
Interestingly, when sensor2 and sensor3 are set, sensor1 reports the high
temperature above (+127) regardless of its setting.
--
Regards,
Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
Fellow, Pediatric Hematology/Oncology
Children's Hospital of Philadelphia/University of Pennsylvania
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
` (3 preceding siblings ...)
2005-05-19 6:24 ` Charles Bailey
@ 2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Charles Bailey
2005-05-19 6:24 ` Charles Bailey
6 siblings, 0 replies; 8+ messages in thread
From: Jean Delvare @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
> This does get a sensor running; it reports CPU temps of ~60 C. When
> I finally had a chance to take the server down and check via the
> BIOS, it reported temps in the mid-30s.
>
> The voltages and fan speeds reported via i2c seem to be reasonable
> numbers.
If you aren't using 2.8.0 yet, upgrading could help (and at least we'll
make sure we aren't trying to fix a bug that was already corrected).
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
` (4 preceding siblings ...)
2005-05-19 6:24 ` Jean Delvare
@ 2005-05-19 6:24 ` Charles Bailey
2005-05-19 6:24 ` Charles Bailey
6 siblings, 0 replies; 8+ messages in thread
From: Charles Bailey @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
--On Friday, June 27, 2003 20:34 -0400 "Mark D. Studebaker "
<mds@paradyne.com> wrote:
This does get a sensor running; it reports CPU temps of ~60 C. When I
finally had a chance to take the server down and check via the BIOS, it
reported temps in the mid-30s.
The voltages and fan speeds reported via i2c seem to be reasonable numbers.
> try modprobing i2c-isa then it should work.
>
> Charles Bailey wrote:
>> Tried CVS i2c lk-24 and lm_sensors2 per your reply. Both build and
>> install fine. ./prog/detect/sensors-detect again picks up the AMD768,
>> but fails loading i2c-amd756, apparently because it's now in
>> i2c/busses. It also fails to locate the 627HF, both before and after
>> the amd756 module is loaded manually (not that that should matter,
>> afaict). If I load modules manually, yielding
>>
>> Module Size Used by Not tainted
>> w83627hf 13044 0 (unused)
>> i2c-proc 8116 0 [w83627hf]
>> i2c-amd756 3848 0
>> i2c-dev 4992 0
>> i2c-core 20164 0 [w83627hf i2c-proc i2c-amd756 i2c-dev]
>>
>> I still have no luck:
>>
>> [bailey@XXX ~]% /usr/local/bin/sensors
>> No sensors found!
>>
>> If I add the eeprom chip driver, I get little more:
>>
>> [bailey@XXX ~]% /usr/local/bin/sensors
>> eeprom-i2c-0-50
>> Adapter: SMBus AMD75x adapter at 06e0
>> Algorithm: Non-I2C SMBus adapter
>> Memory type: DDR SDRAM DIMM SPD
>> Memory size (MB): 512
>>
>> eeprom-i2c-0-51
>> Adapter: SMBus AMD75x adapter at 06e0
>> Algorithm: Non-I2C SMBus adapter
>>
>> [bailey@XXX ~]%
>>
>> I'm happy to test changes or provide additional data if that would help.
>>
>> --
>> Regards,
>> Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
>> Fellow, Pediatric Hematology/Oncology
>> Children's Hospital of Philadelphia/University of Pennsylvania
>>
--
Regards,
Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
Fellow, Pediatric Hematology/Oncology
Children's Hospital of Philadelphia/University of Pennsylvania
^ permalink raw reply [flat|nested] 8+ messages in thread* Ticket 1288
2005-05-19 6:24 Ticket 1288 Charles Bailey
` (5 preceding siblings ...)
2005-05-19 6:24 ` Charles Bailey
@ 2005-05-19 6:24 ` Charles Bailey
6 siblings, 0 replies; 8+ messages in thread
From: Charles Bailey @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
> Thanks. Changing the settings seems to help:
>
> w83627hf-isa-0290
> Adapter: ISA adapter
> Algorithm: ISA algorithm
> [snip]
> fan1: 0 RPM (min = 3000 RPM, div = 2)
> fan2: 4530 RPM (min = 3000 RPM, div = 2)
> fan3: 5443 RPM (min = 3000 RPM, div = 2)
> temp1: +127C (limit = +60C) sensor > PII/Celeron diode ALARM temp2: +36.5C (limit = +60C, hysteresis > +50C) sensor = 3904 transistor temp3: +42.0C (limit = +60C,
> hysteresis = +50C) sensor = 3904 transistor
A bit of final followup: Setting the temperature sensor types to
temp1 = thermistor (3435 in sensors.conf)
temp2 = 3904 transistor (2 in sensors.conf)
temp3 = 3904 transistor (2 in sensors.conf)
yields temperature readings which appear to track, respectively, the BIOS's
values for "System Temp", "CPU1 temp", and "CPU2 temp". (I haven't seen
"System Temp" vary from 25, so I don't know whether it's real or a dud.
The values for fan1, fan2, and fan3 also seem to track the BIOS's values
for "SysFan speed" (always 0), "CPU1 fan speed", and "CPU2 fan speed". I
haven't looked carefully at the voltage sensors.
Once again, this is for a MicroStar K7D Master motherboard with dual
Athlons and the BIOS on the board.
I hope this helps.
--
Regards,
Charles Bailey < baileych _at_ mail _dot_ med _dot_ upenn _dot_ edu >
Fellow, Pediatric Hematology/Oncology
Children's Hospital of Philadelphia/University of Pennsylvania
^ permalink raw reply [flat|nested] 8+ messages in thread