Re: didn't do it quite right...
To quote Rino Mardo <helixfish@gmx.net>,
# On Sun, Jan 07, 2001 at 07:03:26PM +0100 or thereabouts, tom wrote:
# > Howdy Guys,
# >
# > I just ugraded from 2.0.36 to 2.2.18 (hey, I'm slow...) on a
# > potato system. I did not do it the "debian way", however, and
# > I still appear to have 2.0.36 installed, and running top give
# > me ye olde "warning: /boot/System.map has an incorrect kernel
# > version"
# >
# > I looked at lilo.conf, made one change. Here are all the steps I
# > took:
# >
# > 1. unpack source to /usr/src/linux/*
# > 2. cd /usr/src/linux/
# > 3. make menuconfig
# > 4. make dep
# > 5. make clean
# > 6. make bzImage
# > 7. make modules
# > 8. make modules_install
# > 9. mv System.map /boot/System.map
# > 10. cd /usr/src/linux/arch/i386/boot/
# > 11. mv bzImage /boot/
# > 12. cd /boot
# > 13. cp vmlinuz vmlinuz.safe
# > 14. cp bzImage vmlinuz
# > 15. lilo
# >
#
# what i always do is rename /lib/modules/2.2.x to /lib/modules/2.2.x-n
# whenever i have modules
And that works? From what I understand, 'modprobe' and the kernel rely
on /lib/modules/<kernel version> to be the same as the kernel
version(ie: 'uname -r').
Dave
Reply to: