Hi Robert.

I just completed an install with the 20020209 snapshot.  No problem as you
reported.  The machine I installed to was identical in memory size and
CPU type (R5000) with the exception of it being a 150mhz processor.

I did see one bit of a problem when I installed, though... When selecting
the sets to be installed, the selection list does not match the "selected"
list.  I would recommend not toggling any selections and just using the
defaults (just press 'x' and then ENTER).

As for determining if you can complete the install, the following should
be verified:

1.	Is there a /netbsd kernel installed?  Check this as follows, if you
	can CTRL-C out of the install program:
	(If you can't CTRL-C out, the machine is hung.  Don't know why
	 this might happen)
	Get to a '#' prompt (exit install or CTRL-C)...
	# mount
	Check to see if the drive you installed to is mounted.  If it isn't,
	type:
	# mount /dev/sd?a /mnt    (sd? is the drive to which you installed)
	# ls -l /mnt/netbsd
	If it isn't there, then the install failed miserably, or you're
	mounting the wrong drive.
2.	Check for the boot program/block on the drive:
	# /usr/mdec/sgivol sd?
	You should see output similar to:

	# /usr/mdec/sgivol sd0
	disklabel shows 8888685 sectors
	checksum:  00000000
	root part: 0
	swap part: 1
	bootfile:  /netbsd

	Volume header files:
	boot     offset    2 blocks, length    53248 bytes (104 blocks)
	boot.elf offset  106 blocks, length    50304 bytes (99 blocks)

	SGI partitions:
 	0:a blocks   567296 first     2048 type  4 (BSD4.2)
 	1:b blocks   526336 first   569344 type  3 (Raw)
 	3:d blocks     2048 first        0 type  4 (BSD4.2)
 	4:e blocks  7790957 first  1095680 type  4 (BSD4.2)
 	8:i blocks     2064 first        0 type  0 (Volume Header)
	10:k blocks  8888685 first        0 type  6 (Volume)

	The "Volume header files:" should be identical.  If it isn't, then
	the installation of the boot programs in the Volume Header part of
	the disk failed.  This is also the case if you don't get proper
	sgivol output at all.

If the above two look proper, then the disk should boot.

I would be interested in finding out what steps you took for your
install... I.e. what actions you took when selecting the sets to install,
and what your disk layout selection was.

I would still recommend installing the 20011218 finally if all else fails.

-scott

> The machine is an Indy R5000,  hinv:
> CPU: MIPS R5000 Processor Chip Revision: 2.1
> FPU: MIPS R5000 Floating Point Coprocessor Revision: 1.0
> 1 180 MHZ IP22 Processor
> Main memory size: 128 Mbytes
> Secondary unified instruction/data cache size: 512 Kbytes on Processor 0
> Instruction cache size: 32 Kbytes
> Data cache size: 32 Kbytes
> Integral SCSI controller 0: Version WD33C93B, revision D
>   Disk drive: unit 1 on SCSI controller 0
>   Disk drive: unit 2 on SCSI controller 0
> On-board serial ports: 2
> On-board bi-directional parallel port
> Graphics board: GR3-XZ
> Integral Ethernet: ec0, version 1
> Integral ISDN: Basic Rate Interface unit 0, revision 1.0
> Iris Audio Processor: version A2 revision 4.1.0
> Vino video: unit 0, revision 0
> 
> I'm booting via bootp/tftp the install program from  .../binary/kernel/install.gz
> from an x86 NetBSD 1.5.2 machine.  I have done this over and over, changing
> the disk I'm installing to, and hoping it will go to completion magically, but it
> hasn't.
> Below is the text pasted from the serial console output at the point of no
> return (or ENTER either).  If anyone has a guess as to why this would/could
> happen I'd like to hear your speculation as well.  Alternatively, since the
> files seem to be unpacked to a newly created filesystem, is there another
> route I can go to complete the installation?
> 
> Thanks,
> 
> Robert
> 
>  All selected distribution sets unpacked successfully.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>                            +ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ+
>                            | Hit enter to continue |
>                            |                       |
>                            |>a: ok                 |
>                            +ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ+
> 
> 
> 
> sgimips NetBSD list wrote:
> 
> > > Hello,
> > >
> > > I'm getting through the install all the way until the program says (paraphrasing):
> > >
> > > "all distribution files have sucessfully been installed"
> > >   Press enter to continue...
> >
> > What installation method are you using?  Netboot?  CD? or an NFS type?
> >
> > > At this point, nothing happens, the machine is alive, minicom
> > > reports the serial console as being online, but the only way
> > > I could find to get out of this screen is to press the reset buttons
> > > on the indy.  After rebooting, I cannot boot the kernel, if it is
> > > even installed.
> >
> > Could you paste the actual messages reported?  This would help answer
> > your inquiry a bit more directly.  Perhaps for some reason the
> > wrong kernel is being selected, or no kernel is being selected at
> > installation time at all.
> >
> > > So my first question is, is this the expected behavior?
> > > Am I supposed to do somthing else at this point that I just haven't
> > > found the explanation for?
> >
> > Nope, it's not expected behaviour.  What type of machine are you
> > installing on?  INDY R4400?  R5000?  If this is an R5000 machine,
> > it might be hitting a known hang problem with that CPU.
> >
> > You might also try installing the previous snapshot dated 20011222.
> > The 20020209 snapshot was built during a particularly difficult
> > time with the source tree, and indeed could have some problems
> > with the sysinst program which performs the installation.
> >
> > -scott
>