On Sun, Sep 10, 2000 at 09:59:13PM +0400, Rino Mardo wrote:
> for me i'd rename it to /lib/modules/2.2.17-old in case i need 'em back ;-)
Actually, I do the same, until I get the new kernel tested and working.
Otherwise, in cases where I go from one version to another, like
2.2.15-2.2.17, I woul
twork Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my
- -Original Message-
From: Gutierrez Family [SMTP:[EMAIL PROTECTED]
Sent: Sunday, September 10, 2000 8:23 AM
To: debian-user@lists.debian.org
Subject:Weird messages after kernel compiling...
On Sun, Sep 10, 2000 at 10:50:34AM -0700 or thereabouts, John L . Fjellstad
wrote:
> On Sat, Sep 09, 2000 at 05:22:45PM -0700, Gutierrez Family wrote:
>
> > I saw a whole screen-full of "*** Unresolved symbols in
> > /lib/modules/2.2.17/misc/"
>
> I usually delete the /lib/modules/2.2.17 direct
On Sat, Sep 09, 2000 at 05:22:45PM -0700, Gutierrez Family wrote:
> I saw a whole screen-full of "*** Unresolved symbols in
> /lib/modules/2.2.17/misc/"
I usually delete the /lib/modules/2.2.17 directory, before I do
a 'make modules_install'. Try that.
--
John__
Hi again, everyone.I forgot to mention that after compiling my new
kernel, I now get manymodules-related error messages. If I remember
correctly, I did thefollowing:make mrproper (cleaned everything
right out)make xconfigmake depmake clean (don't know if this was
really necessary, since I'
5 matches
Mail list logo
