Hello, I tried what u guys suggested. Instead of using "make install" script to do all the new kernel installation, I copied ~mydir/arc/i386/boot/bzimage /boot/vmlinuz, copied ~mydir/System.map to /boot (or made a soft link to /boot/System.map). When I boot however, it goes upto "initalizing swap space [OK] and then then says: Can't open dependencies file /lib/modules/mykernel-version..... But why does a monolithic kernel try to "open" a "modules" related file? I guess I need to play around with the /etc/rc.d/rc.sysinit and remove the lines related to "probing"... I did try a bit of that too earlier but only made things worse. I never had these problems with compiling modular kernels. regards, tony n Fri, 10 Sep 2004, terry white wrote: > ... ciao: > > : on "9-10-2004" "Matt Hemingway" writ: > > : I build my 2.4.x kernel's via make mrproper (if it's new), make > : (menu)config, make dep && make bzImage all in the top level kernel > : source. Then cp arch/i386/boot/bzImage over my current kernel (for me > : it's /boot/vmlinuz). Well, first I backup the current one to > : /boot/vmlinuz.old, then overwrite. Then I update /etc/lilo.conf > : accordingly. > > in addition , "System.map" from the 'root' of the source, needs to > find its way to /boot ... > > > -- > ... i'm a man, but i can change, > if i have to , i guess ... > > - > : send the line "unsubscribe linux-admin" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Tony Gogoi - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
