please fix your MUA to wrap lines at ~72 characters. On Sun, Nov 12, 2000 at 07:45:04PM +0000, [EMAIL PROTECTED] wrote: > Hello > > I have successfully install Debian Power PC GNU/Linux 2.2 rev 0 non > US on to a Power Mac 2700/75 (system outline below) using BootX to > boot Linux from a second hard disk with a Linux fs on it. But BootX > is of course working from within the Mac OS and my end goal is to > run the 2700/75 as a Debian only system. >
you will want to use quik then
> All my attempt to make the 2700/75 a Debian stand alone system fails
> at the �The Moment of Truth� reboot of the system. I have
> tried rebooting both from the hard disk and from a miBoot v1.0a3
> description as follows:
> Hard disk boot:
> Screen goes blank and the 2700/75 seems to hang.
miboot is a really fickle bootloader for general purposes.
for quik you need to set the OpenFirmware boot-device variable
yourself in order to boot with quik, to do this:
upgrade to potato r1, simply run apt-get update && apt-get dist-upgrade
check your /etc/quik.conf make sure the image= line points to a real
kernel. pointing at a symlink might not work.
example:
root=/dev/sda2
partition=2
image=/boot/vmlinux-2.2.17
label=linux
read-only
run /sbin/quik
now run:
nvsetenv boot-device "$(ofpath /dev/sda)0"
that should make your system quik bootable, you might be able to see
the quik prompt if you change two other OF variables:
nvsetenv output-device screen
nvsetenv input-device kbd # or maybe keyboard
>
> miBoot v1.0a3 floppy boot:
> This method stops at a �Rebooting in 180 seconds.. � with the following error
> message
kernel panic.
> Warning: unable to open init console.
> Kernel Panic: No init found. Try passing init= option to kernel.
probably not pointing the kernel at the right root filesystem, i don't
know how you do that with miboot, as i said its a really annoying
bootloader for general purposes.
> I have had this problem before with BootX when I did not install the
> ramdisk.image.gz. I have assumed that with a Debian only
> installation this problem is caused by something new.
no you need to add root=/dev/sda2 or whatever your root partititon is
to boot properly.
> The Debian install documentation indicates that I may have to
> troubleshoot boot problems by adding special boot arguments to the
> system but it seems unclear as to how this is to be done.
with miboot i don't think you can, with bootX you add arguments to the
kernel arguments feild. for quik you add them to the boot: prompt
(which you may be able to see if you change the output-device
variable, see above)
quik
boot: linux root=/dev/sda2
> I would be very grateful if any one could give me a suggestion as to what to
> do next.
>
> Look forward to receiving any helpful pointers.
> Partition scheme - 20MB BOOT (unused at reboot), 64MB SWAP, 436MB HOME
> (unused at reboot)
i hope you didn't mount that boot partition on /boot that will break
quik.
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpsxPFFvYyUO.pgp
Description: PGP signature
