Vesa,
I was under the impression that an initrd was not required. I had
tried previously to use mkinitrd but it did not make a difference. Is
there anything special about using the mkinitrd, do I need to mount the
image and copy stuff to it? Or can I just run the command?
Thanks
justin
Vesa J��skel�inen wrote:
>
> 30.10.2001 19:20:22, Justin Gaither <[EMAIL PROTECTED]> wrote:
>
> >I installed redhat 7.2, I then downloaded a generic 2.4.13 kernel from
> >kernel.org
> >
> >I applied some patches for ext3 and win4lin. I then added the new
> >kernel to the grub.conf file as below. However when I select the kernel
> >from the grub menu, it just reboots, and gives me the menu again. I can
> >still boot the other kernel. How do I get debug info, so that I can
> >tell if it is a grub problem or a kernel problem?
> >
> >grub.conf:
> >
> >default=0
> >timeout=10
> >splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >title Red Hat Linux (2.4.9-7)
> > root (hd0,0)
> > kernel /boot/vmlinuz-2.4.9-7 ro root=/dev/hda1
> > initrd /boot/initrd-2.4.9-7.img
> >
> >title Win4Lin Kernel (2.4.13)
> > root (hd0,0)
> > kernel /boot/vmlinuz-2.4.13 root=/dev/hda1
>
> Just a guess, you need to make new initrd image for new kernel, '/sbin/mkinitrd'
>command
> with older redhats if I remeber correcly.
--
Justin Gaither Phone: 512-306-7292 x529
Xilinx, Communications Technology Div. Fax: 512-306-7293
500 N. Capital of TX Hwy.
Bldg 3 email: [EMAIL PROTECTED]
Austin, TX 78746 WWW: www.rocketchips.com
www.xilinx.com
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
