On Mon, Jul 15, 2002 at 04:00:13PM +0300, Rafi Cohen wrote:
> Hi, I tried to compile some modules with the kernel and system mentioned in
> the subject.
> After choosing the modules I needed in "make menuconfig", I issued the
> following steps:
> make dep, make clean, make bzimage, make install -- here I received the
> failure. The next steps should be make modules and make modules_install, but
> I did not continue from here, for the time being.
> I got an error in the install script. This script looks for a directory
> /lib/modules/2.4.18-3custom, but this directory does not exist. The only
> directories in /lib/modules are: 2.4.18-3 and 2.4.18-3debug.
> Compiling the same modules on Redhat 7.2 with kernel 2.4.7-10 was successful
> and /lib/modules/2.4.7-10custom did exist.
> 1. Is anybody aware of this problem and can you suggest a solution for it?
> 2. Generally, this problem is probably caused due a change from kernel
> 2.4.7-10 to 2.4.18-3, which I am not aware of.
> The Changes file in Documentation of kernel 2.4.18-3 mentions the cnages
> from 2.2 series to 2.4, but not changes within the 2.4 series. Where can I
> find those changes?
> If there is a mailing list more appropriate to this topic then let me know.
> Thank you in advance, Rafi Cohen.

The 'make install' step on the kernel is attempting to create the initrd image
. . . which is looking for the modules that you have created for the new
kernel.  So, you should probably throw the 'make modules' and 'make
modules_install' steps in before attempting to install the kernel.

That should take care of things for you.

- jkt

-- 
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
Jay Turner, QA Manager          [EMAIL PROTECTED]               Red Hat, Inc. 

      No amount of experimentation can ever prove me right;
      a single experiment can prove me wrong.   -- Albert Einstein 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to