Plus you might need to edit /etc/modules. First time I compiled certain
drivers into my kernel, which had been modules, that file will then cause
the kernel to load modules that no longer exist.
It was pretty funny. I thought I had really screwed things up!
From: "s. keeling" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Debian User <debian-user@lists.debian.org>
Subject: Re: Wierd messages during bootup...
Date: Fri, 8 Sep 2000 22:49:17 -0600
On Fri, Sep 08, 2000 at 12:51:52PM -0700, Daly Gutierrez wrote:
> Hi again, everyone.
>
> I forgot to mention that after compiling my new kernel, I now get many
> modules-related error messages. If I remember correctly, I did the
> following:
>
> make mrproper (cleaned everything right out)
> make xconfig
> make dep
> make clean (don't know if this was really necessary, since I'd done
> 'make mrproper')
> make bzImage (didn't notice any errors, I don't think)
> make modules
> make modules_install
> copied bzImage to the boot directory (renamed) and ran 'lilo'
> rebooted
Look into kernel-package.
> I saw a whole screen-full of "*** Unresolved symbols in
> /lib/modules/2.2.17/misc/<module name.o>"
I believe this has to do with not mv'ing your /lib/modules.xxxx to
/lib/modules.xxxx.old before make modules (make modules_install?).
--
[EMAIL PROTECTED] (Stephen) TopQuark Software & Serv. Enquire
within.
[sed 's/[EMAIL PROTECTED]/@/g'] Contract programmer, server
bum.
Any technology distinguishable from magic is insufficiently advanced.
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
/dev/null
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
