Re: sensor questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alexander Dalloz a écrit :
> Am Do, den 05.01.2006 schrieb François Patte um 22:51:
> 
> Starting to say: I am no sensors specialist.

Maybe, but better than me.... I think that I better understand what's
going on. thank you.

> 
>><----
>>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.

lm_sensors (2.9.1) doc gives only informations on w83627hf which seems
to be different from ...ehf

> 
>>>>"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 ;)

I got the sources of my kernel (2.6.14-1.1653_FC4) and there is a
/usr/src/linux-2.6.14/drivers/acpi/fan.c

I copied the kernel-2.6.14-x86_64-smp.config file as .config in
/usr/src/linux-2.6.14/
then ran "make oldconfig" without problems

then I went to /usr/src/linux-2.6.14/drivers/acpi/ and done what I told
you above.


> 
>>>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? 

This, I cannot know: there is only the default cpuspeed.conf and there
is no man for cpuspeed given with the tool...

> Did you check
> messages syslog file (i.e. dmesg after bootup)?

Yes. no mention at all of cpuspeed.

Best regards.

-- 
François Patte
UFR de mathématiques et informatique
Université René Descartes
http://www.math-info.univ-paris5.fr/~patte


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux