From: nettings@folkwang-hochschule.de (Jörn Nettingsmeier)
To: lm-sensors@vger.kernel.org
Subject: unresolved symbols...
Date: Thu, 19 May 2005 06:23:29 +0000 [thread overview]
Message-ID: <3C68287F.C9902B08@folkwang-hochschule.de> (raw)
In-Reply-To: <3C665DDE.39D2053C@folkwang-hochschule.de>
phil@netroedge.com wrote:
>
> Make sure that you are building sensors against the kernel source tree
> which you are running, and be sure you are using the same compiler to
> build the modules that was used to build the kernel. One of these is
> almost certainly the case.
i can definitely rule out the compiler issue, and i'm 98% sure the
kernel tree is the current one.
i will double-check when i upgrade again in a few days, and keep you
posted on the results.
meanwhile, thanks for responding, best regards,
j?rn
>
> On Sun, Feb 10, 2002 at 12:47:42PM +0100, J?rn Nettingsmeier wrote:
> > hello everyone !
> >
> > first of all, thanks for the great work you've done with lm_sensors
> > !
> > i've been happily using it for over 2 yrs now. like most users, i
> > only speak up when things go wrong :)
> >
> > since kernel 2.4.17, i've had some unresolved symbols on my system:
> >
> > depmod -ae
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.18-pre7/misc/i2c-hydra.o
> > depmod: i2c_bit_add_bus_Rsmp_d53ef5ba
> > depmod: i2c_bit_del_bus_Rsmp_2e7322be
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.18-pre7/misc/i2c-i810.o
> > depmod: i2c_bit_add_bus_Rsmp_d53ef5ba
> > depmod: i2c_bit_del_bus_Rsmp_2e7322be
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.18-pre7/misc/i2c-via.o
> > depmod: i2c_bit_add_bus_Rsmp_d53ef5ba
> > depmod: i2c_bit_del_bus_Rsmp_2e7322be
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.18-pre7/misc/i2c-voodoo3.o
> > depmod: i2c_bit_add_bus_Rsmp_d53ef5ba
> > depmod: i2c_bit_del_bus_Rsmp_2e7322be
> >
> > these are not modules i really need, and i don't really care about
> > them, but i thought you might want to know.
> > my current kernel is 2.4.18-pre9, patched with ingo's o(1) scheduler
> > and robert love's kpreempt.
> > modutils are 2.4.6.
> >
> > the system is a dual p3/600, 512 mb ram on an asus p2b-ds with an
> > intel bx chipset.
> >
> > oh, and lm_sensors is v2.6.2.
> >
> > let me know if you need more information or want me to check out a
> > new release.
> > in that case, please cc: me as i'm not on the list.
--
J?rn Nettingsmeier
home://Kurf?rstenstr.49.45138.Essen.Germany
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 unresolved symbols Jörn Nettingsmeier
2005-05-19 6:23 ` Jörn Nettingsmeier [this message]
2005-05-19 6:23 ` phil
-- strict thread matches above, loose matches on Subject: below --
2003-10-28 18:12 Unresolved symbols David Kesselring
2003-10-28 18:31 ` David Daney
2003-10-28 18:53 ` Jan-Benedict Glaw
2003-10-28 20:36 ` Geert Uytterhoeven
2003-10-28 21:18 ` Ralf Baechle
2003-04-09 19:32 unresolved symbols Sascha Hartmann
2003-04-09 20:14 ` Ken Moffat
2002-08-25 8:04 Madhavi
2002-06-28 17:28 Bo Forslund
2002-06-28 17:44 ` Takashi Iwai
2002-06-28 18:02 ` Stefan Gartner
2002-06-29 10:03 ` Patrick Shirkey
2002-05-30 20:48 Richard Dicaire
[not found] <5.0.2.1.2.20010126010507.00af5128@mail.reub.net>
2001-01-31 0:00 ` Unresolved symbols Rusty Russell
[not found] <5.0.2.1.2.20010105042217.0287d6f0@mail.reub.net>
2001-01-14 12:34 ` Rusty Russell
1999-07-22 15:53 Is the vger 2.2 kernel branch dead VALETTE Eric
1999-07-22 16:54 ` Unresolved symbols ian reinhart geiser (ADMIN)
1999-07-22 17:15 ` Daniel Jacobowitz
1999-07-22 17:23 ` ian reinhart geiser (ADMIN)
1999-07-24 8:46 ` Franz Sirl
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=3C68287F.C9902B08@folkwang-hochschule.de \
--to=nettings@folkwang-hochschule.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.