From: decibel8@charter.net (David)
To: lm-sensors@vger.kernel.org
Subject: 1250
Date: Thu, 19 May 2005 06:24:02 +0000 [thread overview]
Message-ID: <200306270944.25036.decibel8@charter.net> (raw)
In-Reply-To: <200306021011.37032.decibel8@charter.net>
Well, no luck so far. Having a little trouble with the cvs and little short
on time till Sunday.
CVS i2c installed fine. CVS lm_sensors got an error during make right after:
lib/chips.c:2397: initializer element is not constant
lib/chips.c:2397: (near initialization for `adm1026_features[103]')
make: *** [lib/chips.ao] Error 1
Still seem to install fine during make install.
Ran sensors-detect, seemed normal. Couldn't use the init script cause diff
than gentoos.
bash-2.05b# lsmod
Module Size Used by Tainted: P
i2c-proc 6804 0
i2c-isa 748 0 (unused)
i2c-viapro 3604 0 (unused)
i2c-core 15396 0 [i2c-proc i2c-isa i2c-viapro]
module via686a not loading though. Can't 'modprobe' or 'insmod' to get it working
gives:
bash-2.05b# insmod via686a
Using /lib/modules/2.4.20-gentoo-r5/kernel/drivers/i2c/chips/via686a.o
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/i2c/chips/via686a.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
The only thing I did before installing was:
uninstall i2c and lm_sensors. rmmod all the modules, had to take some out of /etc/modules.autoload and
reboot to get them out. Normal. Rebooted. Then installed like said above.
Will see if can get working at least by Sunday.
Didn't change anything in the kernel and via686a worked before.
build is linked to the correct kernel source, yadda, yadda.
Might put the ebuild in for i2c and then just try lm_sensors from CVS.
HMMMM, sensors -s doesn't work. Then checked and there is no /usr/bin/sensors.
Must not have install do to the error during 'make'
Dave
On Friday 27 June 2003 02:53 am, you wrote:
> > I will try putting the CVS on tonight. For now though here is
> > the info you were interested on about the patch.
>
> OK, thanks. It turns out to be unrelated to our problems, but
> interesting though. They customized some of messages at the end of the
> script to reflect files locations and names on Gentoo. Part of what they
> did could even make it back into our version.
prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 1250 David
2005-05-19 6:23 ` 1250 Mark D. Studebaker
2005-05-19 6:23 ` 1250 Philip Pokorny
2005-05-19 6:23 ` 1250 Philip Pokorny
2005-05-19 6:23 ` 1250 Philip Pokorny
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 Philip Pokorny
2005-05-19 6:24 ` 1250 DAVID
2005-05-19 6:24 ` 1250 Philip Pokorny
2005-05-19 6:24 ` 1250 Philip Pokorny
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 David
2005-05-19 6:24 ` 1250 Jean Delvare
2005-05-19 6:24 ` David [this message]
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=200306270944.25036.decibel8@charter.net \
--to=decibel8@charter.net \
--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.