Re: Install problem, no boot after all
if you have a working macos install cd, and about 50mb of free disk space---
i would reccomend the setup that has worked for me on machines such as
yours.
1. make a 20-50mb macos hfs partition, and install macos onto it.
2. install the program 'bootx' on the macos side
3. get the install kernel and ramdisk image from the debian ftp site here:
ftp://ftp.debian.org//debian/dists/woody/main/disks-powerpc/current/powermac
/
4. setup bootx to use the install kernel, and ramdisk, reboot and install
the base system.
5. get a better kernel, that is optimised for that machine here:
http://www.ppckernel.org/kernel.php?id=24
6. re-configure bootx with the new kernel, and reboot.
7. install the rest of your packages and enjoy!
dylan
on 03.4.6 4:39 AM, Boris Bezlaj at boris@gajba.net wrote:
> On Sun, Apr 06, 2003 at 12:44:01PM +0200, Tamas Nagy wrote:
>>
>> It seems that the 'quik' bootloader doesn't work from Debian installer
>> with PowerMac 4400/200. The other boot possibility would be a 'boot
>> floppy' which after selection informs me that 'boot floppy' is not valid
>> option...
>
> You can (probably) boot from hfs formatted floppy. Just copy
> vmlinux.coff to floppy and when booting enter into OpenFirmware:
> 0> boot fd:vmlinux.coff kernel_arguments...
>
> Note that with recent 2.4 kernels there are some problems with COFF
> images..
>
>> Is there any way to boot the installed system from MacOS or from a
>> custom made boot-floppy?
>
> I use quik with great success..although i must admit it didn't work out
> of the box after install. I have a PowerComputing box which is a bit
> different than yours i guess..but not much.
>
> My boot config:
> Mac partition type.
> /boot is on /dev/sda2(ext2 fs, 12MB). All files necessarry for boot
> are placed inside:
> System.map-2.2.22
> System.map-2.4.21-pre7
> boot
> first.b
> quik.conf
> tt
> System.map-2.4.19
> blast
> lost+found
> second.b
> zorg
>
> /boot/quik.conf:
> # quik -f -v -r /boot -C /quik.conf
> # ^^^^^^ this is how i run quik..only need to run it once
> # after adding new kernel image to /boot you anly need to modify
> # quik.conf for the changes to take effect
> #
> timeout = 50
> default = zorg
> partition = 2
> append = "video=imsttfb:vmode:12 devfs=nomount"
>
> # 2.2.22
> image = /tt
> root = /dev/sda3
> label = tt
> read-only
> # 2.4.19
> image = /blast
> root = /dev/sda3
> label = blast
> read-only
> # 2.4.21-pre7 - testing swim3
> image = /zorg
> root = /dev/sda3
> label = zorg
> read-only
>
> NVRAM parameters:
> little-endian? false
> real-mode? false
> auto-boot? true
> diag-switch? false
> fcode-debug? false
> oem-banner? false
> oem-logo? false
> use-nvramrc? true
> real-base 0x7f00000
> real-size 0x100000
> virt-base 0xffffffff
> virt-size 0x100000
> load-base 0x4000
> pci-probe-list 0xffffffff
> screen-#columns 0x64
> screen-#rows 0x28
> selftest-#megs 0x0
> boot-device scsi-int/sd@0:0
> boot-file
> diag-device fd:diags
> diag-file
> input-device kbd
> output-device /bandit@F4000000/IMS,tt128mb8
> oem-banner
> oem-logo
> nvramrc : slowboot begin
> ." Waiting for boot device.." cr d# 1000 ms
> boot-device ['] $boot catch drop
> key? until ;
>
> boot-command slowboot
>
> Note that your settings _will_ be different since u have different hardware.
Reply to: