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

Re: Switching from BootX to quik

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: 
> > I am also interesting boot with quick, but I thought that required 
> > an 
> > non-initrd kernel. 
> Modern quik supports initrd.  I have an old-world 7200 which, after a 
> dist-upgrade, is happily running sarge/testing (3.1?) with a stock 2.6 
> kernel.  Here's the relevant info: 

Ok I have the same software installad as you listed and copied the
values for /etc/quick.conf.

pc236:~# ls -l /boot/vmlinux-2.6.8-powerpc
-rw-r--r--  1 root root 3966115 Jan  9 00:54 /boot/vmlinux-2.6.8-powerpc
pc236:~# ls -l /boot/initrd.img-2.6.8-powerpc
-rw-r--r--  1 root root 4825088 Jan 20 15:47 /boot/initrd.img-2.6.8-powerpc

pc236:~# more /etc/quik.conf

# Generated by quikconfig
# (C) 1998 Matt McLean <keys@yikes.com>
# partition=3
# map=/boot/map

Do I have to manually use nvsetnv to make it work. I am suspicious of
the line 

"boot-device /AAPL,ROM"


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
little-endian?  false
real-mode?      false
auto-boot?      true
diag-switch?    false
fcode-debug?    false
oem-banner?     false
oem-logo?       false
use-nvramrc?    false
real-base       0xffffffff
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     /AAPL,ROM
diag-device     fd:diags
input-device    ttya
output-device   ttya
boot-command    boot

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: