Hi togehter.

I have an initramfs problem with the 2.6.16-linux-kernel. I created a cpio-archive with /dev/console and a static init and put this file into the kernel-option for the initramfs. It looks like the make process is putting the automatically compressed file into the kernel-image. But when I now boot it, I always got a kernel panic: Any idea where I should look for an mistake? This would be my first non-x86-initramfs, so it's likely I'm making some stupid error.

I was messing around for some time until I gave up. I now created the exactly same setup (using the same cpio-file) using a 2.6.15 kernel. Now I can read my "hello world" (I know, not very useful this init, but that was only to test ).

So, there are more problems than just a few renaming-problems with 2.6.16. Just in case anybody else gets this problem.

Of course it would still be nice if someone could give me a hint howto get this to work with 2.6.16. Thanks

Hi!
Did you already try to use an initrd instead of the
initramfs?
I use the initramfs in linux/usr/initramfs_data.cpio.gz only for fb-splash & the initrd (in 2.6.16-kernels in linux/arch/powerpc/boot/ramdisk.image.gz) for ramdisk-boot stuff).
Sorry if I completely missunderstood you!

I didn't - or to be precise, an initrd is my current way to do it with the older kernels. But since initrds are deprecated and initramfs really has some nice improvements, I wanted to try it out since I had to update my kernel nonetheless (hal & co want >=2.6.15). I'm updating to 2.6.15 for now - new enough for updating, old enough for initramfs to work