On Fri, 14 Dec 2007 15:33:45 +0100, Udo van den Heuvel wrote: > Jean Delvare wrote: > > On Wed, 12 Dec 2007 16:32:51 +0100, Udo van den Heuvel wrote: > >> I am running Fedora 8 on a Gigabyte m56s-s3 board with an AMD X2 BE-2350. > >> Running sensors gives me: > >> > >> # sensors > >> k8temp-pci-00c3 > >> Adapter: PCI adapter > >> temp1: -9?C > >> temp2: -20?C > >> temp3: -18?C > >> temp4: -14?C > >> > >> it8716-isa-0290 > (.....) > >> in5: +3.18 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.07 V > >> fan1: 805 RPM (min = 0 RPM) > >> fan2: 0 RPM (min = 0 RPM) > >> temp1: +38?C (low = +127?C, high = +127?C) sensor = thermistor > >> temp2: +35?C (low = +127?C, high = +127?C) sensor = thermistor > >> temp3: +25?C (low = +127?C, high = +127?C) sensor = diode > >> vid: +1.000 V (yes, throttled down) > >> > >> As you can see the k8temp info is slightly off-target. > >> Is this a known issue? How could it be corrected? > > > > The rumor says that most recent K8 CPUs have broken thermal sensors and > > there's nothing you can do about that. My hope is that we can blacklist > > them in the k8temp driver directly, but I don't know which models are > > affected exactly. > > No software compensation possible? Not that I know of. You can always apply arbitrary offsets via compute statements in sensors.conf, but 1* you'll have to guess the offset and 2* there is no guarantee that a simple offset will do the trick. So all in all I doubt it's worth the effort. > (...) > > Gigabyte are famous for their thermal sensors > > that read 25 degrees C all the time (even though there are typically > > thermistors, not thermal diodes.) These are unconnected thermal inputs > > which you can just ignore. > > When temp3 is changed to thermistor it reads 89 degrees versis 24 as > diode. (temp1/2 are 34 now) In general you can hope that the sensor types set by the BIOS are correct. -- Jean Delvare
