From: Steven Smith <sos22@cam.ac.uk>
To: Shaun Bryant <sbryant@ThePit.org>
Cc: "'linux-newbie@vger.kernel.org'" <linux-newbie@vger.kernel.org>
Subject: Re: Kernel error
Date: Mon, 27 May 2002 17:50:31 +0100 [thread overview]
Message-ID: <20020527165031.GA2875@cam.ac.uk> (raw)
In-Reply-To: <A1F41DE771DCD5119FE30060089343500A58C6@NET-ARCH>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
<snip>
The only explanation which immediately comes to mind is that you've
recompiled a kernel without setting EXTRAVERSION in the Makefile.
Normally, when you make modules_install for a new kernel, it obliterates
the old contents of /lib/modules/<version>, to avoid odd crashes
from using modules compiled for the wrong kernel. If you then reverted
to an old kernel which had the same version, you'd have the new modules
and an old kernel, which can sometimes give this sort of error.
My suggestion would be to compile a new kernel, and set EXTRAVERSION.
If the new kernel is version 2.4.5<extra>, then put the System.map
in /boot/System.map-2.4.5<extra>.
This doesn't explain why all of your modules are gzipped, though.
Is this a distribution-specific kernel, or one compiled from the sources at
www.kernel.org?
Steven Smith,
sos22@cam.ac.uk.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-05-27 16:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 14:57 Kernel error Shaun Bryant
2002-05-26 18:40 ` Richard Adams
2002-05-27 4:35 ` G Anna
2002-05-27 15:18 ` Richard Adams
2002-05-27 15:45 ` Ray Olszewski
2002-05-27 19:15 ` Richard Adams
2002-05-27 16:50 ` Steven Smith [this message]
2002-05-28 15:44 ` Setting EXTRAVERSION (was Re: Kernel error) G Anna
2002-05-28 16:54 ` Ray Olszewski
2002-05-28 17:08 ` Steven Smith
2002-05-28 18:32 ` Richard Adams
2002-05-28 20:24 ` Chuck Gelm
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 22:49 kernel error w.landgraf
2007-06-02 9:24 kernel Error umesh
2007-06-02 16:04 ` Michal Piotrowski
2006-04-16 6:43 Kernel error Saurabh Jain
2006-04-17 16:12 ` Stephen Hemminger
2005-12-09 21:18 Kernel Error Thiago Moraes
2005-01-10 11:05 kernel error Russell Coker
2005-01-12 16:49 ` Stephen Smalley
2005-01-12 17:34 ` Stephen Smalley
2005-01-17 11:53 ` Russell Coker
2004-06-20 13:13 Kernel error Michael Egberts
2002-09-30 21:34 Kernel Error Brian Marr
2002-10-01 6:18 ` Oleg Drokin
2002-05-25 19:54 Kernel error Shaun Bryant
2002-05-26 11:45 ` Richard Adams
2002-05-25 17:47 Shaun Bryant
2002-05-25 18:48 ` Richard Adams
2001-03-04 15:15 Romain Chantereau
2001-03-04 16:57 ` Arthur Pedyczak
2000-12-12 11:53 kernel error jordi
2000-12-12 13:32 ` Erik Mouw
2000-06-02 20:35 Ryan Boder
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=20020527165031.GA2875@cam.ac.uk \
--to=sos22@cam.ac.uk \
--cc=linux-newbie@vger.kernel.org \
--cc=sbryant@ThePit.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.