Am Do, den 05.01.2006 schrieb François Patte um 22:51: Starting to say: I am no sensors specialist. > OK. But informations are not clear at all: for instance (after following > a lot of symlink) I read files: temp1_input 39000 (39000 what?), > temp1_max 45000 (what?), temp1_max_hyst 40000 (what?) Same for temp2 and 3 > > I got more info using "sensors" command: > > Sys Temp: +38°C (high = +45°C, hyst = +40°C) You see above values correspond with the degrees in °C (*1000). > CPU Temp: +55.0°C (high = +45.0°C, hyst = +40.0°C) > temp3: +67.5°C (high = +80.0°C, hyst = +75.0°C) > > It seems that CPU is "overheated" but where all this can be configured? I can't tell you whether 55°C is too much for your Pentium D as I have no values to compare with. Too be aware that those sensors on motherboards aren't exact and temperature values they output often differ from reality. This is just because this sensor interface stuff is a cheap add-on. > And what is the meaning of "hyst"? And what is this 3rd temperature (one > more time!) "hyst" is the value starting with it when reached there is an alarm signaled. I don't know your motherboard and thus can't tell you whether "temp3" is a real value (most probably not). Not all signals a sensors chip can handle are connected by the motherboard manufacturer. So blind sensors signals then show phantom values. I face this myself with an ASUS motherboard running an AMD64. > there are also files for fans (x=1, 2, 3, 4) fanx_div fanx_input > fanx_min seem to be related to the fan speed.... Correct. `sensors' command should print out fan speed values too. How much and how much with correct values depends both from the sensors chip and how the motherboard manufacturer uses it on the specific motherboard. > >>I used gkrellm > >> > >>this gives me 3 temperatures: I cannot know which is which... average of > >>temp1 is 40°C, temp2 is 55°C and temp3 125°C > >> > >>How can I know what is measured by these temperatures? > > > Those are ACPI thermal zones. Was meant to be about your sentence "there is nothing in /proc/acpi/thermal_zone .../fan" > Yes, but which ones? I have only 2 thermal reports in the bios: CPU and > MB what is the 3rd one? The values gkrellm shows you are the lm_sensors values. About the 3rd value see my comment above (phantom, going crazy sometimes). > >>gkrellm gives me also 4 fans: only one is working, CPU fan I think. How > >>can I get the others working: I have 3 more fans installed on my tower > >>(Antec P180) and is it possible (and how?) to controll all fans speed > >>according to the remperatures in the tower. > > Do all fans provide sensors data? Not all fans do so. Are all fan > > connectors on the motherboard have sensor chip connections or do they > > just provide power? What do you mean by "control": speed regulation or > > just getting the fan speed value? > Speed regulation (and value) but this seems to be available with some > fans only. I openned the tower and the tower fans have only 2 wires, the > sockets on the MB are for 3. Fan cables with only 2 wires have no speed signal, those fans are just powered. 3 wires means the fan supports reporting his rotation speed. Does not imply there is a sensor data, because that depends on the motherboard whether it has a sensors connector for it. The other point, whether you can control of the fan speed by software is even more depending on what the motherboard manufacturer realized. And it depends too on the capability of the lm_sensors module. Please read in the driver matrix about your chipset and whether the documentation lists "PWM" capability. If it does, there is the chance you can adjust the fan speed with software commands. That should be explained in the lm_sensors documentation about your sensors chip module. > >>I run 2.6.14-1.1653_FC4smp kernel and there are no fan, processor, > >>thermal.... modules available; are these modules necessary to control > >>all these hardwares and, if yes, how can I compile them for my kernel? I > >>read http://fedora.redhat.com/docs/release-notes/fc4/errata/#sn-kernel > > > > > > I am sure the kernel has the required I2C modules. Did you run > > sensors-detect? > > Yes. I can't understand this: > > <---- > Next adapter: SMBus I801 adapter at 0400 > Do you want to scan it? (YES/no/selectively): > Client found at address 0x08 > Client found at address 0x44 > Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed! > Client at address 0x50 can not be probed - unload all client drivers first! > Client at address 0x52 can not be probed - unload all client drivers first! > -----> If you read through the lm_sensors documentation carefully you will find that SMBus isn't that reliable and accessing it even can lookup the whole system. There is an explicit warning by the lm_sensors authors about that. In your case it seems there is a race condition between some components of lm_sensors detection activity regarding this specific sensors. > I tried to unload all related i2c modules but, after that, result is the > same. > > scan of the ISA bus failed everywhere Then the sensors chip is not ISA connected. > scan for Super I/O sensors failed everywhere except: So there you see the sensors chip detected which is used on your motherboard. > <---- > Probing for `Winbond W83627EHF Super IO Sensors' > Success... found at address 0x0290 > -----> Well, you should find that widely spreaded sensors chip mentioned in the motherboard manual. And the lm_sensors documentation tells you about it and its support in specific. > scan for secondary Super I/O sensors failed Typically on the non server boards you have only 1 sensors chip. > > Did you compare the motherboard manual information about > > the sensors chip with the information about the lm_sensors software? > > i did not find any info about this (except BIOS settings) n the mobo > booklet. Then see whether the ASUS website contains more information. I bet this information is published as all ASUS boards I know are shipped with that kind of info. And it is pretty easy to get this data by a google search within minutes http://www.google.com/search?hl=en&lr=&c2coff=1&q=asus+p5wd2+premium+sensor+I%2FO&btnG=Search Or identify the chip on the board itself by opening the PC case. > >>"7.2.2.4. Building Only Kernel Modules" > >> > >>but did not understand how to build the correct Makefile to compile, > >>say, the thermal module: changing what is to be changed in the given > >>example, I get a "nothing to do for default" as a result.... > > > > > > What do you try to compile? And what did you change from the default? > > Here is infos given on redhat site: > > <---------- > > For example, to build the foo.ko module, create the following Makefile > in the directory containing the foo.c file: > > obj-m := foo.o > > KDIR := /lib/modules/$(shell uname -r)/build > PWD := $(shell pwd) > > default: > $(MAKE) -C $(KDIR) M=$(PWD) modules > > Issue the make command to build the foo.ko module. > ----------> > > I tried to compile "fan" module: I replaced "foo" by "fan". this didn't Hu? There is no "fan" module. Which source code did you use when trying to compile whatever using that Makefile skeleton? > work.... I changed $(shell uname -r) by `uname -r` and same for "$(shell No, just leave it as it is. > pwd)" for I did not understand what was the exact meaning of this (so > did gcc which complained about "unknown command "shell"!) > > In that case I did not get error message, only: nothing to do for default. I don't see what you try to do. Do you try to compile lm_sensors yourself from upstream sources? Smells like you do not know yourself what you try ;) > this is a pentium D and according to the "sensors" command, CPU is > always overheated.... Told you already that you shall not take the values too serious. They are more or less estimations. They are worth for long run comparisons to see when something bad happens, like a dieing CPU fan. Maybe you have to adjust the lm_sensors value calculation. See /etc/sensors.conf. > >>Last question: I cannot start cpuspeed service, how can I do that and > >>how to configure this service. > > Why can't you start that service? > > I run "service cpuspeed start" (no OK displayed), then I check with > "service cpuspeed status". Answer is: "cpuspeed is stopped" Does the /etc/cpuspeed.conf contains matching settings? Did you check messages syslog file (i.e. dmesg after bootup)? > François Patte Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 01:20:03 up 32 days, 5:57, load average: 0.20, 0.27, 0.21
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
