Re: Making sense of temperatures and CPU fan
Rio <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Message-ID | <[email protected]> |
On Sunday 29 March 2009, Grant wrote: > > ahh. you neglected to say you are using AMD processors. you have a dual > > processor machine filled with 2 dual core processors. each listing for our > > dual core opterons shows 2 of each 'core' designation, so i chose the one > > that matched what the 'sensors' command listed for temps for each. i am not > > sure why there are 2 of each for each processor. it seems to not be > > in 'sensors' but in gkrellm. > > I'm actually using a single (dual core) AMD 6000+ CPU. > > > again just choose the core0 and 1 for each processor that match what sensors > > reports for temps. > > I do get 4 readings from sensors though: > > # sensors > k8temp-pci-00c3 > Adapter: PCI adapter > Core0 Temp: > +14 C > Core0 Temp: > +16 C > Core1 Temp: > +20 C > Core1 Temp: > +18 C > until someone in the know can tell us why i would choose the 2 highest readings for core0 and core1. safer and probably a bit more accurate. > > hmm sensors doesnt return something like this in the listing? > > > > fan1: 2163 RPM (min = 0 RPM) > > fan2: 1785 RPM (min = 0 RPM) > > fan3: 1439 RPM (min = 0 RPM) > > fan4: 1461 RPM (min = 0 RPM) > > temp1: +43°C (low = +127°C, high = +127°C) sensor = thermistor > > temp2: +41°C (low = +127°C, high = +127°C) sensor = diode > > > > the above was taken from my intel system... but now that i believe you have > > amd processors, probably opterons, here is a sample listing from one of our > > servers. it uses a tyan motherboard which is using via chipset rather than > > nvidia. i suggest checking for forums about nvidia chipset sensors, there may > > be one that you don't have installed. possibly it needs a 3rd party sensor > > module or nvidia may have a chipset module or solution to this. i noticed > > your sensors report was too short indicating that the proper modules do not > > appear to be installed. > > I've built every I2C and ACPI option into the kernel with the same results. > based on what i see from the program listing below, you might want to check with either the mobo mfgr or nvidia for possible sensor modules for the specific chipset. i dont believe nvidia would make a chipset without a full complement of sensors available. it may be possible this chipset is too new to have someone provide 3rd party open source sensor modules. most likely nvidia support would be the best guidance in this. they or the mobo mfgr might be able to explain the 4 temp readings on 2 cores as well. > > did you run sensors-detect when you installed lm-sensors? > > Yes, I get pretty strange output from that too. If I answer "yes" to > ISA I/O or Super I/O scanning I get: > > /dev/port: Operation not permitted > > and the script terminates. Since I'm building I2C into the kernel, > generating /etc/conf.d/lm_sensors and starting /etc/init.d/lm_sensors > did not seem to make any difference. I was getting temperatures > anyway. But here is the output of sensors-detect: > > # sensors-detect > # sensors-detect revision 5291 (2008-06-23 23:40:46 -0700) > > This program will help you determine which kernel modules you need > to load to use lm_sensors most effectively. It is generally safe > and recommended to accept the default answers to all questions, > unless you know what you're doing. > > We can start with probing for (PCI) I2C or SMBus adapters. > Do you want to probe now? (YES/no): > Probing for PCI bus adapters... > Found unknown SMBus adapter 10de:0752 at 0000:00:01.1. > Sorry, no supported PCI bus adapters found. > > If you have undetectable or unsupported I2C/SMBus adapters, you can have > them scanned by manually loading the modules before running this script. > > We are now going to do the I2C/SMBus adapter probings. Some chips may > be double detected; we choose the one with the highest confidence > value in that case. > If you found that the adapter hung after probing a certain address, > you can specify that address to remain unprobed. > > Next adapter: NVIDIA i2c adapter (i2c-0) > Do you want to scan it? (YES/no/selectively): > Client found at address 0x50 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... Yes > (confidence 8, not a hardware monitoring chip) > Client found at address 0x51 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... No > > Next adapter: NVIDIA i2c adapter (i2c-1) > Do you want to scan it? (YES/no/selectively): > > Next adapter: NVIDIA i2c adapter (i2c-2) > Do you want to scan it? (YES/no/selectively): > > Next adapter: NVIDIA i2c adapter (i2c-3) > Do you want to scan it? (YES/no/selectively): > > Next adapter: NVIDIA i2c adapter (i2c-4) > Do you want to scan it? (YES/no/selectively): > > Next adapter: NVIDIA i2c adapter (i2c-5) > Do you want to scan it? (YES/no/selectively): > Client found at address 0x50 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... No > Client found at address 0x51 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... No > Client found at address 0x52 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... No > Client found at address 0x53 > Probing for `Analog Devices ADM1033'... No > Probing for `Analog Devices ADM1034'... No > Probing for `SPD EEPROM'... No > Probing for `EDID EEPROM'... No > > Some chips are also accessible through the ISA I/O ports. We have to > write to arbitrary I/O ports to probe them. This is usually safe though. > Yes, you do have ISA I/O ports even if you do not have any ISA slots! > Do you want to scan the ISA I/O ports? (YES/no): no > > Some Super I/O chips may also contain sensors. We have to write to > standard I/O ports to probe them. This is usually safe. > Do you want to scan for Super I/O sensors? (YES/no): no > > Some south bridges, CPUs or memory controllers may also contain > embedded sensors. Do you want to scan for them? (YES/no): > Silicon Integrated Systems SIS5595... No > VIA VT82C686 Integrated Sensors... No > VIA VT8231 Integrated Sensors... No > AMD K8 thermal sensors... Success! > (driver `k8temp') > AMD K10 thermal sensors... No > Intel Core family thermal sensor... No > Intel AMB FB-DIMM thermal sensor... No > VIA C7 thermal and voltage sensors... No > > Now follows a summary of the probes I have just done. > Just press ENTER to continue: > > Driver `k8temp' (should be inserted): > Detects correctly: > * Chip `AMD K8 thermal sensors' (confidence: 9) > > To load everything that is needed, execute the commands below... > > #----cut here---- > # Chip drivers > # Warning: the required module k8temp is not currently installed > # on your system. For status of 2.6 kernel ports check > # http://www.lm-sensors.org/wiki/Devices. If driver is built > # into the kernel, or unavailable, comment out the following line. > modprobe k8temp > # sleep 2 # optional > /usr/bin/sensors -s # recommended > #----end cut here---- > Do you want to overwrite /etc/conf.d/lm_sensors? Enter s for other > filename (YES/no/s): > Done. > You should now start the lm_sensors service to load the required > kernel modules. > > - Grant > > ______________________________________________ > Gkrellm mailing list > [email protected] > Read archives-join-leave-set RSS feed: > http://archive.lists.netservicesgroup.com > This service is provided by The Network Services Group: > http://www.netservicesgroup.com > > -- Rio ______________________________________________ Gkrellm mailing list [email protected] Read archives-join-leave-set RSS feed: http://archive.lists.netservicesgroup.com This service is provided by The Network Services Group: http://www.netservicesgroup.com