Re: Weird messages after kernel compiling...

2000-09-11 Thread John L . Fjellstad
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

RE: Weird messages after kernel compiling...

2000-09-10 Thread CHEONG, Shu Yang \[Patrick\]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK...what you need is to cp from /usr/src/linux "System.map" to /boot and replace the file "System.map-". Also, what I normally do is mv /lib/modules/ to /lib/modules/.original (Just in case the "backward compatibility" setting was not enabled during t

Re: Weird messages after kernel compiling...

2000-09-10 Thread Rino Mardo
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

Re: Weird messages after kernel compiling...

2000-09-10 Thread John L . Fjellstad
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__