On Sun, 11 Feb 1996 22:04:48 -0800 
 Jeff Woolsey <woolsey@jlw.com> wrote:

 > I have a 4/260 I don't use very often, and I noticed that NetBSD 1.1
 > supported (sort of) the sun4 kernel architecture (4/100, 4/200, etc.)

Cool!  :-)

 > Well, I set it all up and the kernel double panics while booting.
 > And while attempting to get a script of what happened, it double panics
 > in a different way.  Observe:

Hmm .. let's see if we can deal with this...

 > Auto-boot in progress...
 > 
 > EEPROM boot device...Boot: ie(0,0,0) 
 > ie: No Carrier
 > -ie: No Carrier
 > \

I assume it's doing this because you have the eeprom in diag mode...?

 > Copyright (c) 1982, 1986, 1989, 1991, 1993
 > 	The Regents of the University of California.  All rights reserved.
 > 
 > NetBSD 1.1 (GENERIC) #7: Tue Nov 21 20:16:32 MET 1995
 >     pk@neon:/usr/src1/sys/arch/sparc/compile/GENERIC
 > real mem = 33529856
 > avail mem = 30236672
 > using 204 buffers containing 1671168 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 f3000000
 > eeprom0 at obio0 addr f2000000
 > memreg0 at obio0 addr f4000000
 > zs0 at obio0 addr f1000000 pri 12, softpri 6
 > zs0a: console i/o
 > zs1 at obio0 addr f0000000 pri 12, softpri 6
 > bwtwo0 at obio0 addr fd000000: bwtwo, 1600 x 1280
 > ie0 at obio0 addr f6000000 pri 6 address 08:00:20:00:87:1b, type onboard
 > vmel0 at mainbus0
 > vmes0 at mainbus0
 > cgtwo0 at vmes0 addr ff400000 vec 0xa8: cgtwo, 1152 x 900
 > panic: multiple /dev/fb declarers

I can help you with this one...Basically, NetBSD 1.1 didn't handle 
multiple framebuffers on the sun4 properly.  I wrote some code that did 
framebuffer configuration a little "better".  It's now included in 
NetBSD-current.  By default, it will attach the "console" framebuffer to 
/dev/fb, or, if the console is not on a framebuffer, attach the "last" 
framebuffer to /dev/fb.  If you wish, I can build you a kernel with the 
new framebuffer code.

 > syncing disks... trap type 0x7: pc=f8039dd0 npc=f8039d50 psr=1010c0<EF,S,PS>
 > panic: alignment fault

 > Here is the description of the machine when it runs SunOS:
 > 
 > Feb 11 15:37:27 bombast vmunix: Copyright (c) 1983-1993, Sun Microsystems, Inc.
 > Feb 11 15:37:27 bombast vmunix: cpu = Sun 4/200 Series
 > Feb 11 15:37:27 bombast vmunix: mem = 32768K (0x2000000)
 > Feb 11 15:37:27 bombast vmunix: avail mem = 30965760
 > Feb 11 15:37:27 bombast vmunix: Ethernet address = 8:0:20:0:87:1b
 > Feb 11 15:37:27 bombast vmunix: xyc0 at vme16d16 0xee40 vec 0x48 
 > Feb 11 15:37:27 bombast vmunix: sc0 at vme24d16 0x200000 vec 0x40 
 > Feb 11 15:37:27 bombast vmunix: st0 at sc0 slave 32
 > Feb 11 15:37:27 bombast vmunix: st1 at sc0 slave 40
 > Feb 11 15:37:27 bombast vmunix: sr0 at sc0 slave 48
 > Feb 11 15:37:27 bombast vmunix: sd0 at sc0 slave 0
 > Feb 11 15:37:27 bombast vmunix: sd0:  <Quantum ProDrive 105S cyl 974 alt 2 hd 
 > 6 sec 35>

Ah ... you have an "sc" board ... There's no driver for the "sc" yet.

--------------------------------------------------------------------------
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