Hi,

I was using "load ne0:" as per the instructions on the Chalice Technologies
linux page. I did get "boot ne0:" working though - thanks for your help,
Mark. I now also have a kernel configured to mount NFS as root. It works
great.

-Edwin

ps: Does anyone out there have updated CATS firmware? I've been bugging
ChalTech for the images, and they were promised to me last weekend, but I
haven't heard a peep. I'd really like to try booting off a Zip drive and
floppy like all those other people are doing. Serves me right for being an
early adopter. :-)

-----Original Message-----
From: Mark Brinicombe [mailto:mark@causality.com]
Sent: Saturday, June 26, 1999 5:00 AM
To: Edwin Foo
Cc: 'port-arm32@netbsd.org'
Subject: Re: netbooting a CATS board


On Tue, 22 Jun 1999, Edwin Foo wrote:

> Hi all,
> 
> Has anyone had success netbooting a CATS board? If so, I'd like to hear
from
> you. I've gotten to the point that the CATS firmware will successfully
send
> out a bootp request and use tftp to load the kernel, but I'm at a loss as
to
> how to (a) configure the kernel and (b) give the right paramters to the
> "call" command in the firmware.
Hi,
  I do this quite a lot. Ok sounds like you have the dhcp/tftp side of
things sorted.
What command are you using to load/boot the kernel ?

You should just be able to do somehting like

boot ne0:

which should load and then run the kernel so you should not have to worry
about using the call command.

As to the kernel config. If you just want a kernel that will mount nfs as
the root filesystem them you just need to make sure that NFS is configured
and the config line the config file reads something like

config netbsd root on ne0 type nfs

Cheers,
				Mark