From nobody  Mon Mar  2 04:05:07 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA29426;
          Mon, 2 Mar 1998 04:05:07 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199803021205.EAA29426@hub.freebsd.org>
Date: Mon, 2 Mar 1998 04:05:07 -0800 (PST)
From: xcene@c2i.net
To: freebsd-gnats-submit@freebsd.org
Subject: VIDCONTROL VGA_80x50 sets 80x50 but uses wrong font (8x14 instead of 8x8?)
X-Send-Pr-Version: www-1.0

>Number:         5899
>Category:       bin
>Synopsis:       VIDCONTROL VGA_80x50 sets 80x50 but uses wrong font (8x14 instead of 8x8?)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar  2 04:10:01 PST 1998
>Closed-Date:    Tue May 19 02:31:09 PDT 1998
>Last-Modified:  Tue May 19 02:32:27 PDT 1998
>Originator:     Frode E. Moe
>Release:        FreeBSD 2.2.5-STABLE
>Organization:
-
>Environment:
whoa... i don't have access to my box right now, but it's 
a FreeBSD 2.2.5-STABLE compiled 26th of Feb '98 with all the CVSUpd's
available.
>Description:
The VIDCONTROL VGA_80x50 fails to set a 80x50 textmode properly.
Apparently it uses the 8x14 font instead of the 8x8 font, because
  1: the characters are 'cut in half'; only the upper half is shown
  2: changing the font with VIDCONTROL -F 8x14 [somefont] alters
     the display, while changing the 8x8 font does not.

I've tried loading every possible font for every possible mode,
but cannot get any proper 8x8 font displayed in VGA_80x50
(or VGA_80x60 either).

For the sake of completeness, i have a Matrox Millenium I PCI.
(80x50 textmode works great in DOS though). But if I don't 
load any 8x14 at all, the screen goes completely blank in VGA_80x50
(not even any half-cutted-to-pieces characters appear). I recall
reading somewhere that the MGA Millenium left out the 8x14 font in the
BIOS to make room for VBE 2.0 extensions, but the 8x14 font
shouldn't have anything to do with the 80x50 mode as far as I can see.

>How-To-Repeat:
'vidcontrol VGA_80x50'
 - there's nothing more to it!
>Fix:

>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: xcene@c2i.net
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: bin/5899: VIDCONTROL VGA_80x50 sets 80x50 but uses wrong font (8x14
	 instead of 8x8?) 
Date: Tue, 03 Mar 1998 01:18:34 +0900

 >>Number:         5899
 >>Category:       bin
 >>Synopsis:       VIDCONTROL VGA_80x50 sets 80x50 but uses wrong font (8x14 ins
 >tead of 8x8?)
 [snip]
 >>Release:        FreeBSD 2.2.5-STABLE
 >>Environment:
 >whoa... i don't have access to my box right now, but it's 
 >a FreeBSD 2.2.5-STABLE compiled 26th of Feb '98 with all the CVSUpd's
 >available.
 >>Description:
 >The VIDCONTROL VGA_80x50 fails to set a 80x50 textmode properly.
 >Apparently it uses the 8x14 font instead of the 8x8 font, because
 >  1: the characters are 'cut in half'; only the upper half is shown
 >  2: changing the font with VIDCONTROL -F 8x14 [somefont] alters
 >     the display, while changing the 8x8 font does not.
 >
 >I've tried loading every possible font for every possible mode,
 >but cannot get any proper 8x8 font displayed in VGA_80x50
 >(or VGA_80x60 either).
 
 Are you sure that you didn't load wrong font?  We should load a font
 file as shown below.
 
 	vidcontrol -f 8x8 iso-8x8.fnt
                       ~~~     ~~~
 Note that vidcontrol does NOT check if the given font file has the
 given size.  It is just possible to do, by accident,
 
 	vidcontrol -f 8x8 iso-8x14.fnt
                       ~~~     ~~~~
 Anyway, syscons.c in the 2.2-STABLE branch was updated on 28 Feb.  The
 update includes some fix for font handling.  Please try that version
 and see if you still have the same problem with it.
 
 Kazu
State-Changed-From-To: open->closed 
State-Changed-By: yokota 
State-Changed-When: Tue May 19 02:31:09 PDT 1998 
State-Changed-Why:  
Fix is now in 3.0-CURRENT (syscons.c 1.258) and in 2.2-STABLE (syscons.c 
1.182.2.33.) 
>Unformatted:
