Subject: Re: problems installing on a SUN4/260 ...
To: Charles J. Williams <chas@volt.nrl.navy.mil>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-sparc
Date: 04/08/1996 11:07:59
On Mon, 8 Apr 1996 11:20:22 -0400 
 "Charles J. Williams" <chas@volt.nrl.navy.mil> wrote:


[ . . . ]
 > 	si0 targ 0 lun 0: <CDC, 94191-15, 0136> SCSI1 0/direct fixed
 > 	sd1 at scsibus0: 633MB, 1632 cyl, 15 head, 52 sec, 512 bytes/sec
 > 	si0 targ 1 lun 0: <CDC, 94191-15, 0136> SCSI1 0/direct fixed
 > 	sd2 at scsibus0: 640MB, 1632 cyl, 15 head, 53 sec, 512 bytes/sec
 > 	root on sd2a
 > 
 > (yes, while both drives are 94191-15's they are actually different block sizes)
 > 
 > after this i dont see anything, a friend (namely ken) noticed that it
 > still was watching the serial (since we could force "overflows") and
 > the memory activity lights were blinking randomly.

Oh, I bet I know what it is ... Make sure your NetBSD /dev is 
populated.  I guess you untarr'd the distribution with SunOS tar(1)?  GNU 
tar(1) understands how to deal with device nodes.

What you can do is run the NetBSD MAKEDEV under SunOS, but then make sure 
to run it under NetBSD once you can boot into single-user.

Your boot sequence looks normal and healthy.  This is what mine looks like:

Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.

NetBSD 1.1B (BIGSBY) #127: Sat Apr  6 21:52:22 PST 1996
  thorpej@bigsby:/tmp_mnt/basalt/work/netbsd/src/sys/arch/sparc/compile/BIGSBY
real mem = 25141248
avail mem = 22355968
using 153 buffers containing 1253376 bytes of memory
bootpath: /vmes0/si0/sd@0,0
mainbus0 (root)
cpu0 at mainbus0: SUN-4/200 series (MB86910 or WTL1164/5 FPU)
cpu0: 131072 byte write-back, 16 bytes/line, sw flush cache enabled
obio0 at mainbus0
oclock0 at obio0 addr 0xf3000000
eeprom0 at obio0 addr 0xf2000000
memreg0 at obio0 addr 0xf4000000
zs0 at obio0 addr 0xf1000000 pri 12, softpri 6
zs1 at obio0 addr 0xf0000000 pri 12, softpri 6
bwtwo0 at obio0 addr 0xfd000000: bwtwo, 1600 x 1280 (console)
bwtwo0: attached to /dev/fb
ie0 at obio0 addr 0xf6000000 pri 6 address 08:00:20:40:31:17, type onboard
vmel0 at mainbus0
vmes0 at mainbus0
si0 at vmes0 addr 0xff200000 vec 0x40 pri 3
si0: options=7<RESELECT,DMA_INTR,DMA>
scsibus0 at si0
sd0 at scsibus0 targ 0 lun 0: <HITACHI, DK516C, NO34> SCSI2 0/direct fixed
sd0: 1272MB, 2179 cyl, 15 head, 79 sec, 512 bytes/sec
root on sd0a
ie0: TDR detected an open 13056 clocks away

[ running -current, so it should look slightly different from yours ]

 > 	b) swap my scsi id's, does (0,8,0) == ID 2 give netbsd
 > 	   a headache? (i get one everytime i see this)

No, NetBSD can cope with this ... It found your boot device properly, it 
appears...

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939