Hi Gene,
> > Please keep this conversation on the LKML, where it started.
How many times must I tell you?
> Next adapter: SMBus nForce2 adapter at 5100
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x08
> Client found at address 0x4e
> Probing for `National Semiconductor LM75'... Failed!
> Probing for `Dallas Semiconductor DS1621'... Failed!
> Probing for `Analog Devices ADM1021'... Failed!
> Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
> Probing for `Maxim MAX1617'... Failed!
> Probing for `Maxim MAX1617A'... Failed!
> Probing for `TI THMC10'... Failed!
> Probing for `National Semiconductor LM84'... Failed!
> Probing for `Genesys Logic GL523SM'... Failed!
> Probing for `Onsemi MC1066'... Failed!
> Probing for `Maxim MAX1619'... Failed!
> Probing for `National Semiconductor LM82'... Failed!
> Probing for `National Semiconductor LM83'... Failed!
> Probing for `Maxim MAX6659'... Failed!
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Hmm, that could be a secondary temperature sensor. Please find out
which i2c bus number is "SMBus nForce2 adapter at 5100" (using
"i2cdetect -l") then dump the chips contents ("i2cdump N 0x4e b" where
N is the i2c bus number).
Please check "lsmod" and confirm that you are using the w83627hf driver
and not the older w83781d driver.
> > 2* The output of "sensors" in 2.6.15-rc5.
> [root@coyote root]# sensors
> (...)
> w83627hf-isa-0290
> Adapter: ISA adapter
> VCore 1: +1.66 V (min = +1.57 V, max = +1.73 V)
> VCore 2: +1.79 V (min = +1.57 V, max = +1.73 V) ALARM
> +3.3V: +3.26 V (min = +3.14 V, max = +3.47 V)
> +5V: +4.87 V (min = +4.76 V, max = +5.24 V)
> +12V: +11.80 V (min = +10.82 V, max = +13.19 V)
> -12V: -12.28 V (min = -13.18 V, max = -10.80 V)
> -5V: -5.05 V (min = -5.25 V, max = -4.75 V)
> V5SB: +5.59 V (min = +4.76 V, max = +5.24 V) ALARM
> VBat: +3.15 V (min = +2.40 V, max = +3.60 V)
> fan1: 1757 RPM (min = -1 RPM, div = 16) ALARM
> fan2: 2636 RPM (min = 659 RPM, div = 16)
> fan3: 0 RPM (min = 2636 RPM, div = 16) ALARM
> temp1: -48°C (high = +0°C, hyst = +11°C) sensor =
> thermistor
> temp2: +67.5°C (high = +120°C, hyst = +115°C) sensor =
> thermistor
> temp3: +127.5°C (high = +120°C, hyst = +115°C) sensor =
> PII/Celeron diode ALARM
> vid: +1.650 V
> alarms:
> beep_enable:
> Sound alarm enabled
>
> > 3* The output of "sensors" in 2.6.15-rc6.
> (...)
> w83627hf-isa-0290
> Adapter: ISA adapter
> VCore 1: +1.68 V (min = +1.57 V, max = +1.73 V)
> VCore 2: +1.79 V (min = +1.57 V, max = +1.73 V) ALARM
> +3.3V: +3.30 V (min = +3.14 V, max = +3.47 V)
> +5V: +4.87 V (min = +4.76 V, max = +5.24 V)
> +12V: +11.86 V (min = +10.82 V, max = +13.19 V)
> -12V: -12.28 V (min = -13.18 V, max = -10.80 V)
> -5V: -5.00 V (min = -5.25 V, max = -4.75 V)
> V5SB: +5.62 V (min = +4.76 V, max = +5.24 V) ALARM
> VBat: +3.14 V (min = +2.40 V, max = +3.60 V)
> fan1: 1721 RPM (min = -1 RPM, div = 16) ALARM
> fan2: 2636 RPM (min = 659 RPM, div = 16)
> fan3: 0 RPM (min = 2636 RPM, div = 16) ALARM
> temp1: -48°C (high = +0°C, hyst = +11°C) sensor =
> thermistor
> temp2: +63.0°C (high = +120°C, hyst = +115°C) sensor =
> thermistor
> temp3: +127.5°C (high = +120°C, hyst = +115°C) sensor =
> PII/Celeron diode ALARM
> vid: +1.650 V
> alarms:
> beep_enable:
> Sound alarm enabled
>
> Humm, not a heck of a lot of diff to the sensors output. temp1 is shut
> off in gkrellm anyway. Is temp3 the cpu? This is an Athon XP-2800
> stepping 00 cpu.
Obvsiouly not, else your computer would be on fire. The CPU temp would
be temp2, although it's quite high especially for a thermistor-based
measurement (which is usually taken from the socket rather than the CPU
itself). And it matches what gkrellm tells you in -rc5 (65 degrees C is
149 degrees F).
temp1 and temp3 are either nor wired, or use a different sensor type
than the one currently setup. You may try changing the sensor type and
see if it brings interesting readings (like built-in CPU diode or
motherboard sensor).
And actually there is very little difference between both outputs -
I expected this as the driver did not change between -rc5 and -rc6.
So the problem seems to be that gkrellm fails to pick the proper
temperature input in -rc6. Why, I have no idea. But as long as
"sensors" work, the bug has to be in gkrellm rather than the kernel
driver.
See if you have anything under /proc/acpi/thermal_zone. Maybe gkrellm
picks the temperature from ACPI in -rc6 for whatever reason.
--
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
