[lm-sensors] CPU temperature(s) of Conroe

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Kessler]

Dear all,

I have an ASUS P5B-VM with an E6600 and would like to monitor the CPU
temperatures. Sensors-detect only finds an LM78 chip which has only one
temparature sensor. The temperature shown by sensors is obviously the
Mobo-temperature (same as in BIOS).
I have read that Conroes possess integrated temperature sensors which could be
read out directly from CPU registers.
a) Is this correct?
b) Is this implemented in lm-sensors?
c) If yes, what do I have to do to get sensors show the CPU temperatures of the
two cores?

Thank you for reply. If you need further info, please let me know.

Uli

[lm-sensors] CPU temperature(s) of Conroe

[Rudolf Marek]

Hello Ulrich,

> I have an ASUS P5B-VM with an E6600 and would like to monitor the CPU
> temperatures. Sensors-detect only finds an LM78 chip which has only one
> temparature sensor. The temperature shown by sensors is obviously the
> Mobo-temperature (same as in BIOS).

The LM-78 is a misdetection. Please try latest sensors-detect (check the devices 
page on our web)

I bet you have W83627DHG, you will need a patch for this chip. Here is 
preliminary patch:

http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj



> I have read that Conroes possess integrated
> read out directly from CPU registers.
> a) Is this correct?

Yes

> b) Is this implemented in lm-sensors?

Yes but not yet in kernel. You will need latest SVN snapshot of lm-sensors (make 
user_install) and also this set of patches:
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-October/018100.html

(some of the patch files are posted TWICE, please use the latest version - click 
on mail thread to check what is latest)

> c) If yes, what do I have to do to get sensors show the CPU temperatures of the
> two cores?

CHeck above. You will have more than one sensor ;)

> Thank you for reply. If you need further info, please let me know.

Please let me know if it works OK, and David too.

Regards
Rudolf

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Hi, Rudolf,

I have tried to follow your instructions but since I am quite a linux 
novice I have some problems as indicated below.

Rudolf Marek wrote:

> Hello Ulrich,
>
>> I have an ASUS P5B-VM with an E6600 and would like to monitor the CPU
>> temperatures. Sensors-detect only finds an LM78 chip which has only one
>> temparature sensor. The temperature shown by sensors is obviously the
>> Mobo-temperature (same as in BIOS).
>
>
> The LM-78 is a misdetection. Please try latest sensors-detect (check 
> the devices page on our web)
>
> I bet you have W83627DHG, you will need a patch for this chip. Here is 
> preliminary patch:
>
> http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj 
>
>
>
I have downloaded this patch. I understand that this is a C program. But 
I don't know where to put it and what to do with it. Could you please 
give me guidance?

>
>> I have read that Conroes possess integrated
>> read out directly from CPU registers.
>> a) Is this correct?
>
>
> Yes
>
>> b) Is this implemented in lm-sensors?
>
>
> Yes but not yet in kernel. You will need latest SVN snapshot of 
> lm-sensors (make user_install)

I downloaded the last SVN (2006/11/18), extracted, make user, make 
user_install. So far everything worked fine. Then I ran sensors-detect. 
It was revision 1.413 (2006/01/19) which I suspect not being the most 
recent one. It again only found the LM78 (because of the missing patches?).
Do I have to uninstall the previous version of lm-sensors before 
installing the new version?

> and also this set of patches:
> http://lists.lm-sensors.org/pipermail/lm-sensors/2006-October/018100.html
>
> (some of the patch files are posted TWICE, please use the latest 
> version - click on mail thread to check what is latest)
>
I think you mean this patch: 
http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20061017/759c6d1b/attachment-0001.bin

The same problem for me as before: I downloaded the file, recognized it 
as a C program, but don't know how to proceed.

>> c) If yes, what do I have to do to get sensors show the CPU 
>> temperatures of the
>> two cores?
>
>
> CHeck above. You will have more than one sensor ;)
>
>> Thank you for reply. If you need further info, please let me know.
>
>
> Please let me know if it works OK, and David too.
>
> Regards
> Rudolf
>
>
Some information on my system in case it meght help:
ASUS P5B-VM
E6600
2 GB DDR2-667 CL4
SUSE 10.1
Kernel 2.6.16.21-0.25-smp

I appreciate your help. Thank you.

Uli

[lm-sensors] CPU temperature(s) of Conroe

[Rudolf Marek]

Hi,

> I have downloaded this patch. I understand that this is a C program. But 
> I don't know where to put it and what to do with it. Could you please 
> give me guidance?

Yep I can. What distribution are you using? Debian? Fedora? Suse? ..?

>> Yes but not yet in kernel. You will need latest SVN snapshot of 
>> lm-sensors (make user_install)
> 
> I downloaded the last SVN (2006/11/18), extracted, make user, make 
> user_install. So far everything worked fine. Then I ran sensors-detect. 
> It was revision 1.413 (2006/01/19) which I suspect not being the most 
> recent one. It again only found the LM78 (because of the missing patches?).
> Do I have to uninstall the previous version of lm-sensors before 
> installing the new version?

Yes you will need to uninstall the package called "lm-sensors" or libsensors3 
the make user_install stuff is "outside" your packaging system. Ie it is same as 
you would just copy some software to your disk drive. And because you want that 
newer version without installer (no package) you  need to uninstall the package 
first. In short:

Because now you have installed two in the system. One sensors detect you have in 
/usr/sbin/sensors-detect and other you have in (the new one) /usr/local/sbin

Try to issue following command:

/usr/local/sbin/sensors-detect

>> and also this set of patches:
> The same problem for me as before: I downloaded the file, recognized it 
> as a C program, but don't know how to proceed.

Well this is a bit tricky to do. First I need to know what distribution you are 
using. Compiling new kernel image is certainly not task for beginners, but we 
may try.

Regards
Rudolf

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Hi, Rudolf,

>
> Yep I can. What distribution are you using? Debian? Fedora? Suse? ..?
>
It's SUSE 10.1, Kernel 2.6.16.21-0.25-smp
(ASUS P5B-VM, E6600, 2 x 1 GB DDR2-667 CL4)

>
> Yes you will need to uninstall the package called "lm-sensors" or 
> libsensors3 the make user_install stuff is "outside" your packaging 
> system. Ie it is same as you would just copy some software to your 
> disk drive. And because you want that newer version without installer 
> (no package) you  need to uninstall the package first. In short:
>
> Because now you have installed two in the system. One sensors detect 
> you have in /usr/sbin/sensors-detect and other you have in (the new 
> one) /usr/local/sbin
>
> Try to issue following command:
>
> /usr/local/sbin/sensors-detect
>
Okay, this one finds the Winbond W83627ehf and the Core2Duo processor 
(revision 4242 of sensors-detect, 2006-11-17) .
I tried to remove the old "SUSE version" with YAST but I get a lot of 
missing dependencies warnings. Is it safe to delete all those things 
(kdebase3-*, amarok-*,kdeaddons-*, susehelp* etc.)?

>
> Well this is a bit tricky to do. First I need to know what 
> distribution you are using. Compiling new kernel image is certainly 
> not task for beginners, but we may try.


SUSE 10.1, Kernel 2.6.16.21-0.25-smp, last kernel patches installed 
(SUSE Online Update).

I'm beginning to see the ligth at the end of the tunnel.

Best regards
Uli

[lm-sensors] CPU temperature(s) of Conroe

[Till Harbaum]

Hi,

Am Montag, 27. November 2006 10:14 schrieb Ulrich Ke?ler:
> I tried to remove the old "SUSE version" with YAST but I get a lot of
> missing dependencies warnings. Is it safe to delete all those things
> (kdebase3-*, amarok-*,kdeaddons-*, susehelp* etc.)?
Uhm, no, don't do that. I think you wouldn't even be able to 
delete them because there are tons of additional packets depending
on these and you'd have to remove them as well. You'd end up deleting nearly 
everything.

You might perhaps try to just overwrite the existing files by setting the 
install prefix to /usr. While this is ugly as well and may cause some problems 
it will likely allow your yast to be able to continue to work. The only real 
solution is of course to build a new package for your suse.

Ciao,
  Till

-- 
Dr. Till Harbaum <Till at Harbaum.org>

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Hi, Till, hi Rudolf,

>Hi,
>
>Am Montag, 27. November 2006 10:14 schrieb Ulrich Ke?ler:
>  
>
>>I tried to remove the old "SUSE version" with YAST but I get a lot of
>>missing dependencies warnings. Is it safe to delete all those things
>>(kdebase3-*, amarok-*,kdeaddons-*, susehelp* etc.)?
>>    
>>
>Uhm, no, don't do that. I think you wouldn't even be able to 
>delete them because there are tons of additional packets depending
>on these and you'd have to remove them as well. You'd end up deleting nearly 
>everything.
>
>  
>
I got the lm-sensors uninstalled wiht YAST by ignoring all the 
dependencies warnings.

>You might perhaps try to just overwrite the existing files by setting the 
>install prefix to /usr. While this is ugly as well and may cause some problems 
>it will likely allow your yast to be able to continue to work. The only real 
>solution is of course to build a new package for your suse.
>
>
>  
>
I'm sorry, I don't understand this part.

In the meantime I have tried to learn a bit about patching kernels etc.

This is what I understand I have to do to get the lm-sensors running 
with the W83627DHG chip and the Core2Duo temperature sensors:

1. I have to get a driver for the W83627DHG chip. This will be a 
loadable module w83627ehf.ko in the directory 
/lib/modules/2.6.16.21-0.25-smp/kernel/drivers/hwmon. SUSE 10.1 has such 
a driver but it seems too old (a. the documentation of the corresponding 
(?) w83627ehf.c file in /usr/src/linux/drivers/hwmon says nothing about 
w83627dhg support; b. I cannot do 'modprobe w83627ehf': no such device). 
The newer version of the w83627.c file is this:
http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj
So I should rename the old w83627ehf.c file and copy the new one to 
/usr/src/linux/drivers/hwmon.
Now I have to build the new kernel module. This is the step I don't 
understand yet.
After that I can do 'modprobe w83627ehf' and the W83627DHG works with 
lm-sensors.

2. Installing the coretemp driver is a bit more tricky because I have to 
patch msr.c first. I think this works in principle as above: rename 
/usr/src/linux/arch/i386/kernel/msr.c, copy the new msr.c to this 
directory and recompile. I think in this case I have to recompile the 
whole kernel because msr is no loadable module.
After that I can build the coretemp driver as a loadable module as 
above: copy coretemp.c to /usr/src/linux/drivers/hwmon, building the 
module, 'modprobe coretemp'.

In the end, I should add two lines to my file /etc/init.d/boot.local:
modprobe w83627ehf
modprobe coretemp

lm-sensors should work then. Eventually I have to correct the file 
sensors.conf.

Is this correct so far?
How does the patching thing work?
I think I should first save my old kernel in case something goes wrong. 
Is there a preferred way to do this?

Thank you for your help.

Best regards
Uli

[lm-sensors] CPU temperature(s) of Conroe

[* *]

> In the meantime I have tried to learn a bit about patching kernels etc.
>
> This is what I understand I have to do to get the lm-sensors running
> with the W83627DHG chip and the Core2Duo temperature sensors:
>
> 1. I have to get a driver for the W83627DHG chip. This will be a
> loadable module w83627ehf.ko in the directory
> /lib/modules/2.6.16.21-0.25-smp/kernel/drivers/hwmon. SUSE 10.1 has such
> a driver but it seems too old (a. the documentation of the corresponding
> (?) w83627ehf.c file in /usr/src/linux/drivers/hwmon says nothing about
> w83627dhg support; b. I cannot do 'modprobe w83627ehf': no such device).
> The newer version of the w83627.c file is this:
> http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj
> So I should rename the old w83627ehf.c file and copy the new one to
> /usr/src/linux/drivers/hwmon.
> Now I have to build the new kernel module. This is the step I don't
> understand yet.
> After that I can do 'modprobe w83627ehf' and the W83627DHG works with
> lm-sensors.
>
> 2. Installing the coretemp driver is a bit more tricky because I have to
> patch msr.c first. I think this works in principle as above: rename
> /usr/src/linux/arch/i386/kernel/msr.c, copy the new msr.c to this
> directory and recompile. I think in this case I have to recompile the
> whole kernel because msr is no loadable module.
> After that I can build the coretemp driver as a loadable module as
> above: copy coretemp.c to /usr/src/linux/drivers/hwmon, building the
> module, 'modprobe coretemp'.
>
> In the end, I should add two lines to my file /etc/init.d/boot.local:
> modprobe w83627ehf
> modprobe coretemp
>
> lm-sensors should work then. Eventually I have to correct the file
> sensors.conf.
>
> Is this correct so far?

I used a "add-coretemp-driver.patch" file I found on the internet,
don't remember which site.

Then from inside the /usr/src/linux directory, I ran

patch -p1 < /patch/to/add-coretemp-driver.patch

and ran make menuconfig, selected the Coretemp driver, and rebuilt the kernel.

> How does the patching thing work?
> I think I should first save my old kernel in case something goes wrong.
> Is there a preferred way to do this?

Basically, when you get to the stage of copying the new kernel from
arch/i386/boot/bzImage to /boot, make sure you don't use the same
filename as the existing kernel.... I actually like to rename my known
working kernel to bzImage_failsafe and the new one as bzImage, and
then have entries in grub's menu.lst for each.

>
> Thank you for your help.
>
> Best regards
> Uli
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

[lm-sensors] CPU temperature(s) of Conroe

[Rudolf Marek]

Hi,

*Is here some SuSE user around willing to help Ulrich with compilation please?*

Ulrich, kernel compilation is not what the beginners should face, if you wait
few months and then install new Suse (or update) then your system should have
the drivers and everything should be ok.

Your problem is in two places, you need to update the lm-sensors package first.
And then modify the kernel to replace the W83627EHF driver and patch the
coretemp driver.


As for the update:
We agreed with Khali that best is to do

make user_install

(so the libraries and utils will be 2x in fs)

So, please take the lm-sensors 2.10.1

unpack it, install libsysfs developement package, and issue following command:

cd directory_where_it_is
make user_install

Then make sure that new utils are linked with correct (new) library:

ldd /usr/local/bin/sensors

ldd /usr/local/bin/sensors
        libsensors.so.3 => /usr/local/lib/libsensors.so.3 (0x00002b55b27ef000)
        libc.so.6 => /lib/libc.so.6 (0x00002b55b2948000)
        libm.so.6 => /lib/libm.so.6 (0x00002b55b2b85000)
        libsysfs.so.2 => /lib/libsysfs.so.2 (0x00002b55b2d07000)
        /lib64/ld-linux-x86-64.so.2 (0x00002b55b26d7000)

You should check first line if it is same as mine.

This is *UNFINISHED* how to compile the kernel, you may try some steps,
hopefully someone SUSE skilled will help about this:

(here is some semi guide, dont follow it just read it
http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux)

Generally you need

0) install GNU make, gcc, ncurses devel,
1) get kernel source package (2.6.18?) and kernel-syms
2) it will be extracted to directory /usr/src/linux
3) Then get this file:
http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj

Rename it to w83627ehf.c and overwrite file in the /usr/src/linux/hwmon/

PI) get all patches for coretemp driver, use patch < ... to change the source.

You may skip this step, right now, lets try to compile the kernel with modified
EHF driver.

4) return to /usr/src/linux directory
5) issue make cloneconfig
6) issue make menuconfig

You should now see a menu, go to device drivers / hardware monitoring, find
W83627EHF and check if there is <M> symbol.

7) recompile and install kernel, Any suse user tell what exactly needs to be
done here?

I'm sorry about my support, but to give you detailed instructions would take me
a lot of time (because I'm not a SUSE user), and unfortunately I dont have it
right now. I hope that other members of the list will help.

Rudolf

[lm-sensors] CPU temperature(s) of Conroe

[Christian Mahr]

Hi Rudolf & Ulrich

Maybe I do have a comparable set-up?

ASUS P5B deluxe WIFI main board with E6600 conroe
Suse 10.1
kernel 2.6.18.2 for SMP  compiled by myself, with coretemp-patch from Rudolf 
and w83627ehf(applied to the -dhg chip) from David. 
The fan control I set up "manually" by echo-ing into the registers (no clean 
solution yet) in some boot.fancontrol startup file.
the self-compiled kernel is not under yast/rpm control any more, but......

I adapted also ksensors to my needs to show 2 cpu speeds and 2 temperatures 
and the SATA disk. and 3 fans.

the whole kernel works well for sata, ide, network (sky2 patch), etc

Thinks that don?t work yet: 
	- WLAN in master-mode
	- suspend to disk for SMP kernel

what can I provide to you, ullrich?

	Christian

Am Samstag, 9. Dezember 2006 21:47 schrieb Rudolf Marek:
> Hi,
>
> *Is here some SuSE user around willing to help Ulrich with compilation
> please?*
>
> Ulrich, kernel compilation is not what the beginners should face, if you
> wait few months and then install new Suse (or update) then your system
> should have the drivers and everything should be ok.
>
> Your problem is in two places, you need to update the lm-sensors package
> first. And then modify the kernel to replace the W83627EHF driver and patch
> the coretemp driver.
>
>
> As for the update:
> We agreed with Khali that best is to do
>
> make user_install
>
> (so the libraries and utils will be 2x in fs)
>
> So, please take the lm-sensors 2.10.1
>
> unpack it, install libsysfs developement package, and issue following
> command:
>
> cd directory_where_it_is
> make user_install
>
> Then make sure that new utils are linked with correct (new) library:
>
> ldd /usr/local/bin/sensors
>
> ldd /usr/local/bin/sensors
>         libsensors.so.3 => /usr/local/lib/libsensors.so.3
> (0x00002b55b27ef000) libc.so.6 => /lib/libc.so.6 (0x00002b55b2948000)
>         libm.so.6 => /lib/libm.so.6 (0x00002b55b2b85000)
>         libsysfs.so.2 => /lib/libsysfs.so.2 (0x00002b55b2d07000)
>         /lib64/ld-linux-x86-64.so.2 (0x00002b55b26d7000)
>
> You should check first line if it is same as mine.
>
> This is *UNFINISHED* how to compile the kernel, you may try some steps,
> hopefully someone SUSE skilled will help about this:
>
> (here is some semi guide, dont follow it just read it
> http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux)
>
> Generally you need
>
> 0) install GNU make, gcc, ncurses devel,
> 1) get kernel source package (2.6.18?) and kernel-syms
> 2) it will be extracted to directory /usr/src/linux
> 3) Then get this file:
> http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139b
>c4d/attachment-0001.obj
>
> Rename it to w83627ehf.c and overwrite file in the /usr/src/linux/hwmon/
>
> PI) get all patches for coretemp driver, use patch < ... to change the
> source.
>
> You may skip this step, right now, lets try to compile the kernel with
> modified EHF driver.
>
> 4) return to /usr/src/linux directory
> 5) issue make cloneconfig
> 6) issue make menuconfig
>
> You should now see a menu, go to device drivers / hardware monitoring, find
> W83627EHF and check if there is <M> symbol.
>
> 7) recompile and install kernel, Any suse user tell what exactly needs to
> be done here?
>
> I'm sorry about my support, but to give you detailed instructions would
> take me a lot of time (because I'm not a SUSE user), and unfortunately I
> dont have it right now. I hope that other members of the list will help.
>
> Rudolf
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Rudolf Marek wrote:

>Hi,
>
>*Is here some SuSE user around willing to help Ulrich with compilation please?*
>
>Ulrich, kernel compilation is not what the beginners should face, if you wait
>few months and then install new Suse (or update) then your system should have
>the drivers and everything should be ok.
>
>Your problem is in two places, you need to update the lm-sensors package first.
>And then modify the kernel to replace the W83627EHF driver and patch the
>coretemp driver.
>
>
>As for the update:
>We agreed with Khali that best is to do
>
>make user_install
>
>(so the libraries and utils will be 2x in fs)
>
>So, please take the lm-sensors 2.10.1
>
>unpack it, install libsysfs developement package, and issue following command:
>
>cd directory_where_it_is
>make user_install
>
>Then make sure that new utils are linked with correct (new) library:
>
>ldd /usr/local/bin/sensors
>
>ldd /usr/local/bin/sensors
>        libsensors.so.3 => /usr/local/lib/libsensors.so.3 (0x00002b55b27ef000)
>        libc.so.6 => /lib/libc.so.6 (0x00002b55b2948000)
>        libm.so.6 => /lib/libm.so.6 (0x00002b55b2b85000)
>        libsysfs.so.2 => /lib/libsysfs.so.2 (0x00002b55b2d07000)
>  
>
In this line I have libsysfs.so.1. Is this a problem?

>        /lib64/ld-linux-x86-64.so.2 (0x00002b55b26d7000)
>
>You should check first line if it is same as mine.
>
>This is *UNFINISHED* how to compile the kernel, you may try some steps,
>hopefully someone SUSE skilled will help about this:
>
>(here is some semi guide, dont follow it just read it
>http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux)
>  
>
I have read that one, but I don't see how it can help me.

>Generally you need
>
>0) install GNU make, gcc, ncurses devel,
>1) get kernel source package (2.6.18?) and kernel-syms
>2) it will be extracted to directory /usr/src/linux
>3) Then get this file:
>http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/b139bc4d/attachment-0001.obj
>
>Rename it to w83627ehf.c and overwrite file in the /usr/src/linux/hwmon/
>  
>
So far I think I have it. By the way, the directory for the w83627ehf.c 
driver is /usr/src/linux/drivers/hwmon. Might be a special SUSE feature.

>PI) get all patches for coretemp driver, use patch < ... to change the source.
>
>You may skip this step, right now, lets try to compile the kernel with modified
>EHF driver.
>  
>
Okay, I skip this and try the rest first.

>4) return to /usr/src/linux directory
>5) issue make cloneconfig
>6) issue make menuconfig
>
>You should now see a menu, go to device drivers / hardware monitoring, find
>W83627EHF and check if there is <M> symbol.
>
>  
>
This seems all okay.

>7) recompile and install kernel, Any suse user tell what exactly needs to be
>done here?
>
>  
>
After menuconfig I was prompted to build the new kernel by issuing make. 
When I do this everything works fine until make comes to the new 
w83627ehf.c file. From then I only get errors and make stops proceeding 
(takes about 15 seconds).
I then copied the old w83627ehf.c file back and tried make again. It 
took about 10 minutes and complained a few times but the driver 
apparently was built correctly.
I changed again to the new w83627ehf.c file in order to have a closer 
look at the error messages. I issued make cloneconfig, make menuconfig, 
make. It all worked. I don't know what was different this second time. 
It took about 30 seconds and the only thing that was recompiled was the 
w83627ehf driver.
I got these messages:
...
Building modules, stage 2.
MODPOST
CC                 drivers/hwmon/w83627ehf.mod.o
LD [M]           drivers/hwmon/w83627ehf.ko

What do I have to do now to load the new module? (modprobe -r w83627ehf 
and then modprobe w83627ehf does not work: no such device)
I think I have  recompiled only a module so I do not need to change the 
whole kernel. Is this correct?

>I'm sorry about my support, but to give you detailed instructions would take me
>a lot of time (because I'm not a SUSE user), and unfortunately I dont have it
>right now. I hope that other members of the list will help.
>
>Rudolf
>
>  
>
Thank you for your support. I'm optimistic that we will be getting 
sensors to work.

Uli

[lm-sensors] CPU temperature(s) of Conroe

[Christian Mahr]

Am Dienstag, 12. Dezember 2006 09:52 schrieb Ulrich Ke?ler:
> What do I have to do now to load the new module? (modprobe -r w83627ehf
> and then modprobe w83627ehf does not work: no such device)
> I think I have ?recompiled only a module so I do not need to change the
> whole

the redy made "w83627ehf.ko" needs to be copied to 
to /lib/modules/<kernel-version>/kernel/drivers/hwmon/w83627ehf.ko   (of 
course replace <kernel version> by your kernel version)
you can say "depmod -a" afterwards to sort out module linkages but this might 
not even necessary (doesn?t hurt either).

Afterwards, "modprobe w83627ehf"  should work, start "tail 
-f /var/log/messages" in another window first to observe whats happening. 
use lsmod to confirm presence among modules.
confirm appearance of a bunch of devices in /sys (in my system 
its /sys/devices/platform/i2c-9191/9191-0290/ ): lots of fan*, in* and pwm* 
etc

BR
Christian

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Hi, Christian, hi, Rudolf,

>>What do I have to do now to load the new module? (modprobe -r w83627ehf
>>and then modprobe w83627ehf does not work: no such device)
>>I think I have  recompiled only a module so I do not need to change the
>>whole
>>    
>>
>
>the redy made "w83627ehf.ko" needs to be copied to 
>to /lib/modules/<kernel-version>/kernel/drivers/hwmon/w83627ehf.ko   (of 
>course replace <kernel version> by your kernel version)
>you can say "depmod -a" afterwards to sort out module linkages but this might 
>not even necessary (doesn?t hurt either).
>
>Afterwards, "modprobe w83627ehf"  should work, start "tail 
>-f /var/log/messages" in another window first to observe whats happening. 
>use lsmod to confirm presence among modules.
>confirm appearance of a bunch of devices in /sys (in my system 
>its /sys/devices/platform/i2c-9191/9191-0290/ ): lots of fan*, in* and pwm* 
>etc
>
>BR
>Christian
>
>
>  
>
I did this and I got the same error (no such device again).

I checked if I really had compiled the new w83627ehf.c by compiling it 
again (make clean, make cloneconfig, make menuconfig, make). 
Unfortunately, I got the error messages again when compiling the new 
w83627ehf.c. So I obviously compiled the old version in the run that had 
no problems.

So now I need help to figure out where the compile problems come from. 
The error messages are things like "initializer element is not constant" 
or "... undeclared her (not in a function)" or "missing braces around 
initializer" (this is only a warning).
I took a look at the include list at the beginning of w83627ehf.c. In 
the new version there are two additional files to be included: 
hwmon-sysfs.h and mutex.h. They can be found in the directory 
/usr/src/linux/include/linux. Do I have to tell the compiler something 
about that e. g. in a Makefile?

Sorry that I answer only today but the last days our mail server was down.

Thanks for your help.

Uli

[lm-sensors] CPU temperature(s) of Conroe

[Ulrich Keßler]

Hi, Rudolf and Christian

>
> So now I need help to figure out where the compile problems come from. 
> The error messages are things like "initializer element is not 
> constant" or "... undeclared her (not in a function)" or "missing 
> braces around initializer" (this is only a warning).
> I took a look at the include list at the beginning of w83627ehf.c. In 
> the new version there are two additional files to be included: 
> hwmon-sysfs.h and mutex.h. They can be found in the directory 
> /usr/src/linux/include/linux. Do I have to tell the compiler something 
> about that e. g. in a Makefile?
>
I think I found a way to check if this is a problem. I inserted two 
lines in the old w83627ehf.c file:
#include <linux/mutex.h>
#include <linux/hwmon-sysfs.h>
and recompiled. It worked without problems. So there must be something else.

Uli