Yes, this works. So why the install kernel doesn't boot (since it doesn't come with a separate initrd)?<br><br>- Naveen<br><br><div><span class="gmail_quote">On 4/21/06, <b class="gmail_sendername">Paul Nasrat</b> <<a href="mailto:pnasrat@redhat.com">
pnasrat@redhat.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, 2006-04-21 at 19:47 +0530, Naveen wrote:<br>
><br>> Getting the same result for the RHEL4 and FC5 one. The netboot image<br>> (ppc32.img) from FC5 doesn't work since it's 7.3 MB (larger than 6).<br>><br>> It is the netboot.img file under the images directory on the CD#1 of
<br>> RHEL. A "file" on this shows that this is a 32-bit executable ... any<br>> other way to check ?<br><br>Boot the seperate "vmlinuz" (it's vmlinux - don't ask) and<br>ramdisk.image.gz eg from:
<br><br><br><a href="http://download.fedora.redhat.com/pub/fedora/linux/core/5/ppc/os/ppc/ppc64/">http://download.fedora.redhat.com/pub/fedora/linux/core/5/ppc/os/ppc/ppc64/</a><br><br>with a yaboot.conf like:<br><br>init-message = "\nWelcome to the installer ppc testing environment!\nHit
<br><TAB> for boot options.\n\n"<br><br>image=/ppc64/vmlinuz<br> label=fc5<br> initrd=/ppc64/ramdisk.image.gz<br> read-only<br><br>This should work. There are some patches I have to review and test to
<br>improve our malloc which should allow larger images, and zImage support<br>too.<br><br>Paul<br><br><br></blockquote></div><br><br clear="all"><br>-- <br><br>- Naveen