Hi
Could anyone possible help me with the following problem :)
Problem: I can't boot the kernel (2.6.15-1) with modules enabled (using
DEBIAN)
Reason: My ram disk boot image is not being recognised (not attached to
an existing device).
title Debian GNU/Linux, kernel 2.6.15-1-Modules-enabled
root (hd0,4)
kernel /boot/vmlinuz-2.6.15-1 root=/dev/hda5 ro
initrd /boot/initrd.img
savedefault
boot
The initrd image is not attached to a legitimate device (ie) As
I understand it the initrd.img should be attached to /dev/hda5
I have never conciously attached the ram disk image to a device,
be it hda5 or what ever. HOW DO I DO THIS???
Where I am at:
INITIAL CONDITIONS: I downloaded Debian from the web. It installed
a kernel on my behalf. I got the config from which this kernel was built
from /boot to build my kernel.
1) I have compiled 2.6.15-1 with modules enabled. COMPILES FINE.
Copied bzImage to /boot as vmlinuz-2.6.15-1.
2) I have done make modules. MODULES COMPILES FINE.
3) I have done make modules_install. NO PROBLEMS
4) I ran a script mkinitrdramfs to create the image for the ram disk
(WORKED)
and copied it to /boot.
When I try to boot the kernel, the kernel insists that hda5 does not exist.
No reason why it should either. I simply copied the original grub entry
(theoretically
an identical kernel) and hoped for the best.
How do associate my initrd.img with hda5 or whatever...
Cheers
Rashid Latif
_________________________________________________________________
Meet Sexy Singles today @ Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D22740&_t=751140432&_r=emailtagline_meetsexy_june&_m=EXT
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
