From: ukessler@uni-bonn.de (Ulrich Keßler)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] CPU temperature(s) of Conroe
Date: Fri, 15 Dec 2006 15:58:30 +0000 [thread overview]
Message-ID: <4582C626.5010600@uni-bonn.de> (raw)
In-Reply-To: <loom.20061123T125301-366@post.gmane.org>
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
next prev parent reply other threads:[~2006-12-15 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 11:59 [lm-sensors] CPU temperature(s) of Conroe Ulrich Kessler
2006-11-24 12:57 ` Rudolf Marek
2006-11-24 15:04 ` Ulrich Keßler
2006-11-25 11:54 ` Rudolf Marek
2006-11-27 9:14 ` Ulrich Keßler
2006-11-27 17:02 ` Till Harbaum
2006-11-28 15:35 ` Ulrich Keßler
2006-12-06 3:44 ` * *
2006-12-09 20:47 ` Rudolf Marek
2006-12-09 21:30 ` Christian Mahr
2006-12-12 8:52 ` Ulrich Keßler
2006-12-12 23:13 ` Christian Mahr
2006-12-15 15:58 ` Ulrich Keßler [this message]
2006-12-15 17:13 ` Ulrich Keßler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4582C626.5010600@uni-bonn.de \
--to=ukessler@uni-bonn.de \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.