I searched as much as I could, found alot of people asking
same question "How do I fix this?" , but no answers.
If anyone could shed some light that would be great.

After recompiling monolithic kernel with no module support
I still receive modprobe dependices errors when booting.

"modprobe can't open dependices file /lib/modules/2.4.9-12xxx/modules.dep
"No such file or directory"

Of coarse not, I compiled a monolithic kernel with no module support.
Even if you try to do a make/install modules from source dir, it won't
because there's no module support. There's nothing to link /boot/module-info to.
I've added append=nomodules to lilo.conf and it does show up in the 
/proc/cmdline as appended.
At first glance this does not seem to matter much, system boots and runs fine
but wait..... try to do a "mkbootdisk" it will fail with
"/lib/modules/2.4.9-12xxx is not a directory".
I've sniffed around in the rc.d/rc.sysinit file and as far as I can read it
should just pass over any module stuff.
Can not find any Redhat info in any of the reference material for 
upgrading/compliing kernels. Why don't they address this?
Can anyone help, this is got to be something everone runs into if building
a monolithic kernel? beside system running fine I still like my system to
boot clean with no errors.



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

Reply via email to