From: Dieter Nützel <Dieter.Nuetzel@hamburg.de>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>
Cc: Rik Faith <faith@valinux.com>,
"Dri-devel" <Dri-devel@lists.sourceforge.net>,
"Alan Cox" <alan@redhat.com>
Subject: Re: test13-pre3
Date: Tue, 19 Dec 2000 01:58:17 +0100 [thread overview]
Message-ID: <00121901581700.00433@SunWave1> (raw)
> List: linux-kernel
> Subject: Re: test13-pre3 woes
> From: Peter Samuelson <peter@cadcamlab.org>
> Date: 2000-12-18 9:19:13
> [Download message RAW]
>
>
> [J Sloan]
> > The module now compiles and gets installed -
> > Unfortunately, attempting to load it does not go well:
> >
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol remap_page_range
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol __wake_up
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol mtrr_add
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol __generic_copy_from_user
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol schedule
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol kmalloc
> > kernel/drivers/char/drm/tdfx.o: unresolved symbol si_meminfo
>
> Those symbols are rather generic and rather important. Sounds like a
> generic module problem. Do other modules load? Does your kernel use
> MODVERSIONS? (This module apparently doesn't.) Are you using a recent
> version of modutils?
>
> Puzzled. Maybe Keith Owens knows something.
>
> Peter
I got this, too. The one liner send here on lkm seems to be not enough. Even
Alan's ac1/2 did not do the trick. The 'new' Linux makefile changes brake
this stuff. It works before these changes.
So Rik any comments?
Thanks,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany
email: nuetzel@kogs.informatik.uni-hamburg.de
@home: Dieter.Nuetzel@hamburg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-19 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 0:58 Dieter Nützel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-18 17:35 test13-pre3 Petr Vandrovec
2000-12-18 17:18 ` test13-pre3 Maciej W. Rozycki
2000-12-17 21:55 test13-pre3 Linus Torvalds
2000-12-17 23:43 ` test13-pre3 Albert Cranford
2000-12-18 6:00 ` test13-pre3 Peter Samuelson
2000-12-18 12:58 ` test13-pre3 Maciej W. Rozycki
2000-12-18 14:34 ` test13-pre3 Christoph Rohland
2000-12-18 19:24 ` test13-pre3 Christoph Rohland
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=00121901581700.00433@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=Dri-devel@lists.sourceforge.net \
--cc=alan@redhat.com \
--cc=faith@valinux.com \
--cc=linux-kernel@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.