Sageev George wrote:

> Using the serial port console did allow me to see
> the kernel booting, but I now get a different error
> towards the end of this process. I'll just put the
> error here, but I'll put the complete console output
> at the end of this message.
> 
>     le0 at dio0 scode 21 ipl 5: address 08:00:09:15:ae:95
>     le0: 8 receive buffers, 2 transmit buffers
>     topcat0 at dio0 scode 133: 1280 x 1024 256 color hi-res catseye display
>     grf0 at topcat0
>     ite0 at grf0
>     interrupt levels: bio = 4, net = 5, tty = 5
>     hil0 device 1: US ASCII keyboard
>     boot device: le0
>     root on le0
>     no file system for le0
>     cannot mount root, error = 79
>     root device (default le0):le0a
>     dump device: sd1b
>     file system (default generic): nfs
>     root on le0 dumps on sd1b
>     cannot mount root, error = 49
>     root device (default le0):
> 
> I was trying to netboot, which works for the 1.5.3 system,
> (meaning I am confident that rbootd, rarp, bootparams, and
> nfs are set up correctly)

These days the kernel and the bootblocks use bootp/dhcp.  I can
see that the bootblocks already used bootp to load the kernel.

I can see that the INSTALL kernel doesn't have support for
mounting root on nfs (options NFS_BOOT_BOOTP).  Try the GENERIC
kernel instead.

While you're doing this, it would be useful to see if you
can install using sysinst in the RAMDISK kernel.  You'd be
trail-blazing here too, since it hasn't been tested.

	-- Gregory McGarry <g.mcgarry@ieee.org>