From owner-freebsd-current  Sat Nov  9 03:34:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA21263
          for current-outgoing; Sat, 9 Nov 1996 03:34:26 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA21256
          for <current@FreeBSD.ORG>; Sat, 9 Nov 1996 03:34:22 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id DAA29108; Sat, 9 Nov 1996 03:34:16 -0800 (PST)
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: current@FreeBSD.ORG
Subject: Re: syscons and mono VGA screens? 
In-reply-to: Your message of "Sat, 09 Nov 1996 20:57:17 +1030."
             <199611091027.UAA00239@genesis.atrad.adelaide.edu.au> 
Date: Sat, 09 Nov 1996 03:34:16 -0800
Message-ID: <29101.847539256@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> There's an annoying 'feature' now though; I have to leave the (mono VGA)
> monitor unplugged until after syscons has finished probing.  Otherwise,
> it gets as far as the autoconf line for syscons :
> 
> sc0 at 0x60-...

Heh.  I see that too on thud (running -current), FWIW.  Until now,
however, I just thought it was just some weird serial console hack in
Satoshi's kernel. :-)  We have an MGA monitor hooked to a port switch,
and thud's console is always the "dead" one now.

						Jordan