From nobody  Wed Feb 19 13:22:55 1997
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA19895;
          Wed, 19 Feb 1997 13:22:55 -0800 (PST)
Message-Id: <199702192122.NAA19895@freefall.freebsd.org>
Date: Wed, 19 Feb 1997 13:22:55 -0800 (PST)
From: chris@bb.cc.wa.us
To: freebsd-gnats-submit@freebsd.org
Subject: Syscons in 2.2 wont work with Diamond Speedstar pro se
X-Send-Pr-Version: www-1.0

>Number:         2775
>Category:       conf
>Synopsis:       Syscons in 2.2 wont work with Diamond Speedstar pro se
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    sos
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 19 13:30:04 PST 1997
>Closed-Date:    Mon May 12 03:13:14 PDT 1997
>Last-Modified:  Mon May 12 03:42:07 PDT 1997
>Originator:     Chris Coleman
>Release:        2.2-GAMMA and 3.0-Current
>Organization:
Big Bend Community College
>Environment:
>Description:
I can't install FreeBSD 2.2-Gamma or 3.0-Current on my machine.  It
is a pentium 100, 64 Meg of ram, 6G disk space, Adaptech 2940 controller
SCSI 2 Fast/Wide Barracuda drives. (4G,2G) , Diamond Stealth Speedstar Pro
SE Video Card with 1 Meg of Ram.  At boot-up it just starts flashing colors
where the letters should be.  I think this is a syscons problem.

Then I changed out the Video Card to a Trident card. (both are pci)  It didnt
have the same problem. The flashing stuff went away.  But I still couldn't
install 2.2-GAMMA.  It got all the way through the probe stuff, then
it just didn;t do any thing.  The last line was APM powermanagment disabled, 
not probed.  It just sat there.
>How-To-Repeat:
It happened once before when I tried to go to 2.2-Current from 2.1.5 I ended
up going to 2.1.6 instead. I never could get to 2.2 anything.
>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: jkh 
Responsible-Changed-When: Wed Feb 19 16:42:08 PST 1997 
Responsible-Changed-Why:  
syscons is Soren's baby. 

From: Mike McGaughey <mmcg@heraclitus.cs.monash.edu.au>
To: chris@bb.cc.wa.us
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: conf/2775: Syscons in 2.2 wont work with Diamond Speedstar pro se
Date: Thu, 20 Feb 1997 15:26:27 +1100 (EST)

 > I can't install FreeBSD 2.2-Gamma or 3.0-Current on my machine.  It
 >  Diamond Stealth Speedstar Pro
 > SE Video Card with 1 Meg of Ram.  At boot-up it just starts flashing colors
 > where the letters should be.  I think this is a syscons problem.
 
 This matches the behaviour on my system.  In my case, I put in a working
 video card long enough to install the system and recompile the kernel
 with the PCVT driver.
 
 PCVT works fine.  I don't know what it does differently to syscons.
 
 Cheers,
 
     Mike.

From: Chris Coleman <chris@bb.cc.wa.us>
To: Mike McGaughey <mmcg@heraclitus.cs.monash.edu.au>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: conf/2775: Syscons in 2.2 wont work with Diamond Speedstar pro se
Date: Wed, 19 Feb 1997 20:23:25 -0800 (PST)

 I tried that, I put in a working trident card, the problem went away, but
 it still would not install.  I guess I have two problems here.
 
 Christopher J. Coleman (chris@aries.bb.cc.wa.us)
 Computer Support Technician I  (509)-766-8873
 Big Bend Community College  Internet Instructor
 FreeBSD Book Project:  http://www.bb.cc.wa.us/~chris/book.html
 I may Be inaffective, but atleast I am good at it.
 
 On Thu, 20 Feb 1997, Mike McGaughey wrote:
 
 > 
 > > I can't install FreeBSD 2.2-Gamma or 3.0-Current on my machine.  It
 > >  Diamond Stealth Speedstar Pro
 > > SE Video Card with 1 Meg of Ram.  At boot-up it just starts flashing colors
 > > where the letters should be.  I think this is a syscons problem.
 > 
 > This matches the behaviour on my system.  In my case, I put in a working
 > video card long enough to install the system and recompile the kernel
 > with the PCVT driver.
 > 
 > PCVT works fine.  I don't know what it does differently to syscons.
 > 
 > Cheers,
 > 
 >     Mike.
 > 
 

From: "Paul A. Scott" <pscott@netcom.com>
To: <freebsd-gnats-submit@freebsd.org>
Cc:  Subject: Re: conf/2775: Syscons in 2.2 wont work with Diamond Speedstar pro se
Date: Sat, 19 Apr 1997 15:34:37 -0700

 Attempting to install FreeBSD 2.2.1 (from Walnut Creek CD-ROM or floppy) I
 have the exact same TWO problems as reported in conf/2775:
 
 1) On system 1, after kernel uncompresses, the screen goes completely
 garbled. Look like running in graphics mode with completely messed up
 character maps. Almost looks like static it's so garbled. This occurs with
 Diamond Speedstar64 video card. Impossible to continue installation.
 
 2) On system 2, using a Trident 9000 video card, the screen looks fine, but
 after kernel probes all devices, the screen goes blank, beeps once, the
 cursor goes to the lower left hand corner of the screen, and the system
 sits idle. Switching to the alternate console, Alt-F2, I see a single line
 that says "DEBUG: ioctl(3, TIOCCONS, NULL) = 0 (success)".  Key strokes on
 the first console are ignored. Key strokes on the alternate console are
 processed, but no shell is available.
 
 Both these systems run every release of FreeBSD from 1.0 through 2.1.6
 without any problems. Haven't tried 2.1.7 or 2.2.0. My first  experience
 with the problem is with 2.2.1 although it makes sense that 2.2.0 is where
 it originated.
 
 I hope someone gets this fixed soon and puts out 2.2.2 asap. I'm asking for
 a refund on from Walnut Creek for 2.2.1. Although I always recompile the
 kernel in every release for many (good) reasons, I'm not going to use the
 alternate console driver; syscons should work. I'll wait; hopefully not too
 long.
 
State-Changed-From-To: open->closed 
State-Changed-By: yokota 
State-Changed-When: Mon May 12 03:13:14 PDT 1997 
State-Changed-Why:  
The PR originator reported that 3.0-970502-SNAP worked. The same 
kludge/fix is now in RELENG_2_2 too (syscons.c 1.182.2.18). 
>Unformatted:
