You can still attempt to boot separate kernel and initrd; you
_have_ to use the 'netboot' image.
Well, two things. First, when I try that I get a similar error from yaboot.
That is, I netbooted yaboot and its .conf includes:
Those files are copied from development/ppc/os/ppc/ppc64/
method 'load' failed 000000300
Second, what I would like to be doing is testing the rawhide images.
So avoiding them because they don't work defeats part of the purpose.
OTOH, today's boot.iso gives me a python error in anaconda startup, so I
don't feel like I'm desperately missing out not having a smooth netboot
experience just now. ;-)
I suspect the problem is caused by the size of the newer images. A
smaller image would probably work.
Maybe there are some guaranteed-useless drivers enabled you can prune?
You can create the 'ppc64.img' from the kernel+initrd by
'mkzimage' script. If you edit /usr/share/ppc64-utils/zImage.lds to
change the address at which the resulting image is linked, does that
help? Try moving it to 16MiB?
I tried this and it helped in the sense that I don't get the ELF loading
error message any more. Instead, it slurps the file happily, then blinks
and restarts yaboot stage 1. So, not that much help.
I in no way trust the image I made. I used rawhide images, stubs, and
script to start with, but the rest of the tools are cobbled together on an
old install and maybe not good enough. If you would like to mkzimage one
for me with tools you trust, I would be glad to test it.
Oh, and maybe I don't have to bother filing a ppc64-utils bug and you can
just get this shoehorned in for the next schlub that thinks he can figure
out how to use that script on uninstalled input files.
--- ppc64-utils/devel/mkzimage.~1.5.~ 2005-11-18 17:15:15.000000000 -0800
+++ ppc64-utils/devel/mkzimage 2007-08-09 23:52:22.000000000 -0700
@@ -39,6 +39,7 @@ fi
for file in zImage.lds /usr/share/ppc64-utils/zImage.lds; do
if [ -f $file ]; then