Re: QUIK READ ERROR ON BLOCK 63747 (KERNAL PANIC NOW!)
I thought that too... but I have it booting to the kernal now!!! Albiet with a panic, but I think that's my ramdisk not being set... 2.6 needs a ramdisk right? Anyone else that is interested in getting their machine to work without bootx, this is BY FAR the most detailed info and got me the farthest... it's even a debian kernal! Check it out! Debian needs to add this to their freaking install manualll FOR SHOOOO
http://fare.livejournal.com/93274.html
I think the bad blocks problem was my first.b file was bad, I downloaded one claiming to be redone for the beige g3's... maybe it was for scsi, I don't know, it could have been a few things, I've been going so fast forgetting stuff... Anyway
On 3/19/07, Paul Mackerras <paulus@samba.org> wrote:
Anthony Henson writes:
> I run quik, I reboot, I set my real-base to F00000, boot-device to
Why F00000?
> ide0/disk@0:9 bootfile to /vmlinux root=/dev/hda9 reset-all, when it comes
> back to OF, I type boot, I get the boot: prompt, I type linux, and I get
> "Read error on block 63747" twice, then cannot load image or find image or
> somesuch.
Maybe your disk has a bad block?
What sort of machine is this?
Paul.
Reply to: