Subject: Re: How to boot RISC PC without harddisc?
To: None <bjh21@netbsd.org, l.smiers@chello.nl, port-arm32@netbsd.org>
From: Kjetil B. Thomassen <kjetil@thomassen.priv.no>
List: port-arm32
Date: 07/09/2001 00:16:46
In message <f8f109974a.kjetilbt@kbtrpc.thomassen.priv.no>
          "Kjetil B. Thomassen" <kjetil@thomassen.priv.no> wrote:

> In message <Pine.SOL.4.33.0107072012060.12766-100000@draco.cus.cam.ac.uk>
>           Ben Harris <bjh21@netbsd.org> wrote:
> 
> > On Fri, 6 Jul 2001, Leo Smiers wrote:
> > 
> > > In message <Pine.SOL.4.33.0107061741370.28972-100000@draco.cus.cam.ac.uk> you wrote:
> > > > If -current is OK, I can do it trivially.
> > > Please, would you be so kind.
> > 
> > <URL:ftp://ftp.netbsd.org/pub/NetBSD/misc/bjh21/cosc/netbsd.gz>
> > 
> > Since that was a GENERIC kernel anyway, I thought I may as well add the
> > NFS_BOOT options to it.
> 
> This kernel does not seem to support either of my monitors, so I'm a bit
> stuck here. The boot loader works fine, but when the kernel starts
> everything goes fuzzy, and the monitor looses sync.
> 
> I have set up my NetBSD/sparc 1.5 as a DHCP and boot server for the Risc
> PC, and modified the BtNetBSD application as outlined in one of the
> earlier mails in this thread, and the kernel boots, but then the screen
> just will not synchronize.
> 
> I have changed the config to:
> Run <BtNetBSD$Dir>.BtNetBSD <BtNetBSD$Dir>.^.kernels.netbsd maxproc=64 nofpa  
> 
> And, set the:
> *WimpMode X640 Y480 C256
> 
> Or:
> *WimpMode X1280 Y1024 C256
> 
> As my monitors support these, but to no avail.
> 
> I have attached my two special monitor files in case that can help you
> figure out why it doesn't work on my monitors.
> 
> CTRL-T seems to drop me into the debugger, and running reboot from there
> does indeed do a reboot.
> 
> I can, of course, hook up a third monitor, but that should not be
> necessary, if you ask me.
> 
> I have been trying to boot from the network, and it is able to get a
> lease from the DHCP server after I enter ne0 blindly and press enter
> three times, but something does not work correctly, and it dies.

That turned out to be a misconfiguration/understanding of DHCPD, and now
it mounts root, but gets no further. It does answer to ping, but that is
pretty much it.

My hardware configuration is:
http://www.thomassen.priv.no/MyRiscPC/

TIA!

Kjetil B.
mailto:kjetil@thomassen.priv.no
http://www.thomassen.priv.no/