hi, i know this is an old thread but i do have
some input / experience to share here and I notice
a newer thread on the quick issue too.
1) i did boot 2.6.15-?? (?24 maybe) from ubuntu on
my powerbook3400/ etch testing last fall, around
September/October i was using it everyday. that
was because d
hi, i know this is an old thread but i do have
some input / experience to share here and I notice
a newer thread on the quick issue too.
1) i did boot 2.6.15-?? (?24 maybe) from ubuntu on
my powerbook3400/ etch testing last fall, around
September/October i was using it everyday. that
was because d
Hello, check this out:
https://launchpad.net/ubuntu/+source/quik/+bug/83346
apparently quik can't boot ubuntu's newer kernels. I also a kernel panic
with the newer 2.6 kernel under debian. I was however able to boot the
2.6.8 kernel, though, and Ubuntu warty has kernel-image-2.6.7-powerpc. So,
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
farthe
Anthony Henson writes:
> I run quik, I reboot, I set my real-base to F0, boot-device to
Why F0?
> ide0/[EMAIL PROTECTED]: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 637
I am about ready to take a chainsaw to this damn thing. I have tried all
kinds of different quik.conf settings, I ended up coping one straight from
some other guy that I googled,
timeout=10
default=linux
image=/boot/vmlinux
label=linux
root=/dev/hda9
partition=9
so that's my /etc/quik.c
6 matches
Mail list logo
