On Sat, 09 Mar 96 23:05:00 EST 
 "Chris Austin-Lane" <cal@nas.edu> wrote:

 >   Sun 4/260 with CGTwo and BWTwo (and a TAAC), NetBSD 1.1 binaries (two
 >   disks, one SunOS, one now NetBSD), when I boot b sd(0,0,0)netbsd -s, the
 >   following error appears:
 > 
 >   zs0a: console i/o
 >   bw0 at obio0 addr fd000000: bwtwo, 1600 x 1280
 >   ie0 at obio0 addr f6000000 pri 6 address 08:00:20:06:12:12, type onboard
 >   el0 at mainbus0
 >   es0 at mainbus0
 >   cgtwo0 at vmes0 addr ff400000 vec 0xa8: cgtwo, 1152 x 900
 >   panic: multiple /dev/fb declarers

This was a bug in 1.1, and I fixed it shortly after 1.1.  I've pulled the 
required fixes into the 1.1 branch, and they should be in patch2, 
whenever it's released...

I'll try and build you a kernel from that branch tonight...

(Yes, to the other folks in the audience, I have build a GENERIC kernel 
from -current sources like I promised ... I'll try and put both the 
-current GENERIC and the 1.1-almost-p2 GENERIC up for ftp tomorrow.)

 >   The only workaround I have found is to pull the cgtwo out of the machine.
 >   I can't pull the bwtwo out because it has the serial ports, ethernet, and
 >   keyboard attachment.  Am I missing something? (Hopefully a switch on the
 >   bwtwo to disable it?) If I can get -current compiled, I plan to config
 >   out the bw0 driver; failing that, I will try to find and comment out the
 >   driver code itself (at least that part which declares it as a /dev/fb).

The "bwtwo card" is actually the CPU board...

Like I said, it's fixed in -current ... and the "console framebuffer" 
(i.e. looks at the eeprom console property) gets attached to /dev/fb.

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