kermit wrote:
> Nico Kadel-Garcia wrote:
>
>>
>> What *ELSE* did you change in the kernel? And did you do "make
>> install; make modules_install" to get the modules installed?
>
> This is usually other way round. 'make install' often creates initrd
> as part of kernel installation and initrd needs already installed
> modules.

Umm. If your kernel has loadable modules (and that is the de facto standard
for contemporary kernels), the old standard behavior for "make install" was
to install the kernel itself, not most of the modules may not be installed
by it. I'd really have to go take apart the strange Makefile structure to
get into details, but I found "make modules_install" to be a fairly
necessary followup step.

It's why I preferred "make rpm", which built up the images for me and would
also report if I forgot to rename the new kernel and tried to put it on top
of an old one with the same name (a source of endless trouble for new kernel
builders).

>> And why are you using
>> a 2.4 kernel?
>>
>
> Because it is apparently RHEL3 as indicated below
>
>>> Currently in "/lib/modules/2.4.21-27.ELsmp/kernel/drivers/net/"
>
> =arvi=