It sounds like to me that you don't have the proper filesystem drivers built into your kernel.

What filesystem for linux are you using?  It needs to be built as <*>, not <M>.

You should be using Linux naming for your hardrive in your yaboot.conf.

Please post the output from "mac-fdisk -l /dev/hda" (minus the quotes please).

Also post your /etc/yaboot.conf so we can see if that is setup correctly.

Regards,
Draeven

On Tue, 2005-09-20 at 22:43 -0400, Nicholas S-A wrote:

Thank you so much! That worked to get over the prom_init. unfortunately, I still cannot boot. It gets a kernel panic wand outputs: VFS: unable to open root "/dev/hda11" or unknown-block(0,0) add root= with correct root device to boot line kernel panic - cannot open root filesystem reboot in 180 seconds... I used "/dev/hda9" (my boot partition), "/dev/ram0", "hd:11", etc in various combinations as kernel options for root= and real_root= . with root=/dev/ram0 and real_root=/dev/hda11, it said unknown-block(1,0) instead. Is there an easy fix for this? should I be using OF or Linux HD naming? any other ideas? thank you so much again, Nick On Sep 20, 2005, at 9:40 PM, Joseph Jezak wrote: > Nicholas S-A wrote: >> hello, >> I have installed Gentoo PPC (2005.1) on my 800 Mhz Titanium PowerBook >> G4 successfully (it boots). I have some problems, however, and I was >> wondering if anyone could help me. As it stands, I can not do the >> following which I would like: >> 2) I have a problem with my kernel. When I try to boot off of a >> kernel that I complied myself, it always gives " returning* >> 0x01400000 from prom_init"* as an error in the Open Firmware white >> background, then NO MORE TEXT is outputted, and it freezes. >> Apparently, this error is common with powermac G5's (except with more >> text and a return to the OF prompt), but why my old powerbook has it >> I do not know. to compile the kernel, I ran >> make clean dep modules modules_install vmlinux >> dep was not needed. My system says making the vmlinux image worked >> fine. however, it does not boot, instead giving the above error. Any >> ideas on how I could get it to work? > > You haven't compiled in a framebuffer device. On that machine you > need to have RadeonFB compiled into your kernel.