hmm.
I haven't used RH in years, so I'm not sure what the initrd lines are about. Also, what are you doing a "make install" on?
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.
My lilo.conf file is something like this (yours will be a bit diff. of course):
boot=/dev/hda
root=/dev/hda2
default=Linux-2.4.20
image=/boot/vmlinuz
label=Linux-2.4.20
read-only
image=/boot/vmlinuz.old
label=Linux-2.4.19
read-only
Then I run lilo and get a nice pat on the back...usually.
-Matt
On Fri, 10 Sep 2004 16:28:40 -0400 (EDT)
Tony Gogoi <tgogoi@xxxxxxxxxxxxxxx> wrote:
>
> Hi matt,
>
> Yes, I tried first without "nomodules", exactly the same thing happens.
>
> I don't have an "image=" line. I have "initrd" lines in lilo.conf created
> by "make install". Do you use"make install" ?
>
> The default option points to the working default modular kernel.
>
> > This is just my personal experience, but I build with no module support
> > all the time and I've never put the root="nomodules /dev/hda9" in the
> > lilo.conf file. Have you tried it without the "nomodules" statement?
> >
> > Also, are your boot= default= and image= options set right (especially
> > to the new kernel and not the previous one)?
> >
> > -Matt
> >
> > On Fri, 10 Sep 2004 16:01:28 -0400 (EDT)
> > Tony Gogoi <tgogoi@xxxxxxxxxxxxxxx> wrote:
> >
> > >
> > > Hello,
> > >
> > > This question is about the monolithic kernel again. Hope I'm not bugging
> > > the newsgroup. But I've tried many things and things still don't seem to
> > > work.
> > >
> > > My kernel is 2.4.20-8 from RedHat CD 9.0. I compiled the kernel without
> > > module support. My lilo line as a root="nomodules /dev/hda9". Booting
> > > seems to begin normally.
> > >
> > > Booting stops saying QM_MODULES: function not implemented. I have read on
> > > the net that that could be fixed with module-init-tools. But my question
> > > is rather generic: All the problems I get are related to module support. I
> > > have tried modifying the /etc/rc.d/rc.sysinit to avoid modprobes etc
> > > script etc but to no avail.
> > >
> > > I would be grateful for some suggestions on how to make a monolithic
> > > kernel completely independent of any module support.
> > >
> > > Regards,
> > > Tony
> > >
> > >
> > > -
> > > : 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
> > >
> > -
> > : 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
>
-
: 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
