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

Re: Switching from BootX to quik

On Wed, Feb 16, 2005 at 12:10:51PM +0100, Simon Vallet wrote:
> On Wed, 16 Feb 2005 11:29:57 +0100
> Hans Ekbrand <hans@sociologi.cjb.net> wrote:
> > I changed to the boot-device and boot-file to
> > 
> > boot-device ata/ATA-disk@0:6
> > boot-file ata/ATA-disk@0:6/boot/vmlinux-2.6.8-powerpc
> > 
> >  and guess what happened, linux booted!!!
> Always a pleasing moment. You are almost there :-)
> > It didn't get its initrd and therefore failed to mount root,
> > 
> > VFS: Cannot open root device "<NULL>" or unkown-block(0,1)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on uknown-block(0,1)
> >  (0)Rebooting
> This was a common problem with previous, non-initrd enabled quik
> versions-- are you sure you've got the latest quik from sarge ?


pc236:~# apt-cache policy quik
  Installed: 2.1-3
  Candidate: 2.1-3
  Version Table:
 *** 2.1-3 0
        500 http://ftp.sunet.se testing/main Packages
        100 /var/lib/dpkg/status
     2.0e-0.6 0
        500 http://ftp.sunet.se stable/main Packages
pc236:~# quik -V
QUIK version 2.1

> > but that should be a minor problem.
> You may also try with a non-initrd kernel.

Yes, but I would rather stick to the debian stock-kernels, for

> > The boot-file argument, should that point to the virtual image name
> > given in /etc/quik.conf or a real file containing the linux kernel? 
> Actually, it may be both, or sometimes empty, in which case quik should
> boot the 'default' image you defined in quik.conf. AFAIK, this is quite
> machine-dependent : some models do seem to require the full path to the
> image in 'boot-file', others are quite happy with a quik label.

When I did put the full path to the kernel in the boot-file argument,
quik didn't seem to use the definitions in /etc/quik.conf, it didn't
give the kernel the initrd. I guess I could give the
initrd=/boot/initrd.img-2.6.8-powerpc in boot-file as

boot-device     ata/ATA-disk@0:6
boot-file       ata/ATA-disk@0:6/boot/vmlinux-2.6.8-powerpc initrd=/boot/initrd.img-2.6.8-powerpc root=/dev/ram

But that didn't work either (Black screen).

(For the moment, I cannot even reproduce the successful boot, might be
related to 'boot-command    begin ['] boot catch 1000 ms cr again' or
'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: