On Mon, 01 May 2000, Bill Shirley wrote:
| I'm not sure what is going wrong here, but my modules are in
| /lib/modules/2.2.14-15mdk
| there are other directories under /lib/modules also. (I made an error in my
| original response.) I think there is some option in the kernel build that
| specifies where the modules should be found.
|
| However, the kernel is STILL trying to load your SCSI low-level driver as a
| module. This makes me think you are not executing the kernel you created
| ("I am told that linux is Loading the module"). Check the date on
| /boot/vmlinuz to verify it is the one you built. Then check that lilo.conf
| is pointing to your kernel build. If you didn't change Makefile to
| INSTALL_PATH=/boot then your new kernel will be in /, which you should copy
| to /boot.
This is my number one argument for incrementing the release number on kernels
you build (example 2.2.14-15.1mdk). When you build the kernel with the same
version and release number, the modules get installed in the same (old)
directory. So when the modules list is generated, it still finds those modules
which have been integrated into the new kernel. This *can* cause errors like
loading modules that are already integrated into the kernel.
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
