Re: Trouble getting Quik working...
On Thu, Jan 23, 2003 at 02:50:18PM -0800, Dylan Barrie wrote:
>
> On Thursday, January 23, 2003, at 06:40 AM, Chris Tillman wrote:
> >How about posting the results of nvsetenv and cat /target/etc/quik.conf
> >from the installer shell, so we can catch up with where you're
> >at now?
>
> The output of nvsetenv:
>
> 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 0xffffffff
> real-size 0x100000
> virt-base 0xffffffff
> virt-size 0x100000
> load-base 0x4000
My load-base is also 100000 (not probably related though, I have a
PowerBase 180
> pci-probe-list 0xffffffff
> screen-#columns 0x64
> screen-#rows 0x28
> selftest-#megs 0x0
> boot-device scsi-int/sd@0:0
> boot-file linux
> diag-device fd:diags
> diag-file
> input-device kbd
> output-device pci1/@E
> oem-banner
> oem-logo
> boot-command boot
My boot-command is
begin ['] boot catch 1000 ms cr again boot
This is supposed to allow the drive to spin up before trying
to boot.
>
> The output of quik.conf:
>
> # Example of how can be quik.conf set up
> timeout = 100
> default = linux
> image = /boot/vmlinux-2.2.20-pmac
> label = linux
> #partition = 2
> root = /dev/sda2
> #image = /boot/vmlinux.old
> # label = old
Try
chroot /target quik -v
(Maybe there's something going wrong with the quik installation).
--
"The way the Romans made sure their bridges worked is what
we should do with software engineers. They put the designer
under the bridge, and then they marched over it."
-- Lawrence Bernstein, Discover, Feb 2003
Reply to: