[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Switching from BootX to quik



On Mon, Feb 14, 2005 at 10:09:38AM +0100, Hans Ekbrand wrote:
> On Fri, Feb 11, 2005 at 11:16:52AM -0500, Rich Johnson wrote:
> > On Friday, February 11, 2005, at 03:15 AM, Hans Ekbrand wrote: 

[...]

> Do I have to manually use nvsetnv to make it work. I am suspicious of
> the line 
> 
> "boot-device /AAPL,ROM"
> 
> below?
> 
> pc236:~# quik -v
> Second-stage loader is on /dev/hda6
> Config file is on partition 6
> Writing first-stage QUIK boot block to /dev/hda6
> Making /dev/hda6 bootable (map entry 6)
> Writing block table to boot block on /dev/hda6
> pc236:~# nvsetenv
[...]
> boot-device     /AAPL,ROM
> boot-file
[...]
> pc236:~# 

http://penguinppc.org/bootloaders/quik/quirks.php lists Performa 6400
which ought to be similar to my Performa 5400 and says the following:

    * output-device defaults to ttya
    * output-device screen ONLY works with floppy booting, must use output-device ttya to boot off of SCSI/IDE.
    * load-base may need to be changed to 100000.
    * Internal IDE Drive: boot-device ata/ATA-disk@0:0
    * Note that if linux isn't the first bootable partition on your
    drive, you'll have to specify the partition number in boot-file:
    boot-file ata/ATA-Disk@0:X/vmlinux root=/dev/hdaX (X is partition
    no. of root)

Does quick know of the model-specific quirks mentioned on
http://penguinppc.org/bootloaders/quik/quirks.ph? Is it up to me as an
user to configure OF?

-- 
Note that I use Debian version 3.1
Linux emac140 2.6.9-1-686 #1 Thu Nov 25 03:48:29 EST 2004 i686 GNU/Linux

Hans Ekbrand (http://sociologi.cjb.net) <hans@sociologi.cjb.net>

Never trust a message that appears to come from me but is not signed
with GPG! It is most likely SPAM or a VIRUS sent by someone who has my
adress and got infected.

My public key, ID 7050614E, is available from the HKP key servers and
here: http://sociologi.cjb.net/~hans/key.txt

Attachment: signature.asc
Description: Digital signature


Reply to: