From nobody@FreeBSD.ORG Sun Mar 21 15:19:30 1999 Return-Path: Received: by hub.freebsd.org (Postfix, from userid 32767) id EC32714BE2; Sun, 21 Mar 1999 15:19:29 -0800 (PST) Message-Id: <19990321231929.EC32714BE2@hub.freebsd.org> Date: Sun, 21 Mar 1999 15:19:29 -0800 (PST) From: adam@whizkidtech.net Sender: nobody@FreeBSD.ORG To: freebsd-gnats-submit@freebsd.org Subject: Console font loading problem at boot time X-Send-Pr-Version: www-1.0 >Number: 10715 >Category: conf >Synopsis: Console font loading problem at boot time >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: Sun Mar 21 15:20:00 PST 1999 >Closed-Date: Tue Mar 23 11:52:12 PST 1999 >Last-Modified: Tue Mar 23 11:58:14 PST 1999 >Originator: G. Adam Stanislav >Release: 3.1-RELEASE #0 >Organization: Whiz Kid Technomagic >Environment: FreeBSD dunaj.whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE #0: Mon Feb 15 11:08:08 GMT 1999 jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC i386 >Description: When rc.conf contains screen fonts to be loaded, it loads them improperly. I noticed it when I developed a Central-European key map, and type characters number 208, 209, and 211 (0-based). The screen font is loaded, and everything shows up properly, except those three characters. I have to manually reload the font with vidcontrol -f 8x16 iso02-8x16.fnt . After that, I can see all characters properly. >How-To-Repeat: Place iso02-8x16 in your rc.conf as your default 8x16 console font. Reboot. Type Alt-208, Alt-209, Alt-211 using your numeric keypad. You will either get a blank space, a wrong character or complete junk. Run vidcontrol -f 8x16 iso02-8x16.fnt, then type those characters again. This time, they will appear on your screen properly. (This is using a local console, I have not tried it remotely -- I am not equiped for that). >Fix: As an internim fix, I use vidcontrol to load the font manually after booting. Incidentally, I tried to use vidcontrol from a start-up script, and it did not work... I have to do it manually after booting and logging on. >Release-Note: >Audit-Trail: From: Kazutaka YOKOTA To: adam@whizkidtech.net Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: conf/10715: Console font loading problem at boot time Date: Mon, 22 Mar 1999 13:39:32 +0900 >>Number: 10715 >>Category: conf >>Synopsis: Console font loading problem at boot time >>Confidential: no >>Severity: non-critical >>Priority: low >>Responsible: freebsd-bugs [...] >>Description: >When rc.conf contains screen fonts to be loaded, it loads them improperly. I n >oticed it when I developed a Central-European key map, and type characters num >ber 208, 209, and 211 (0-based). The screen font is loaded, and everything sho >ws up properly, except those three characters. I have to manually reload the f >ont with vidcontrol -f 8x16 iso02-8x16.fnt . After that, I can see all charact >ers properly. >>How-To-Repeat: >Place iso02-8x16 in your rc.conf as your default 8x16 console font. Reboot. Ty >pe Alt-208, Alt-209, Alt-211 using your numeric keypad. You will either get a >blank space, a wrong character or complete junk. Run vidcontrol -f 8x16 iso02- >8x16.fnt, then type those characters again. This time, they will appear on you >r screen properly. (This is using a local console, I have not tried it remotel >y -- I am not equiped for that). You are using the mouse cursor in the text console, right? This is a known problem when you enable the mouse cursor. The console driver uses font for the character codes 208 though 211 to display the mouse cursor. To avoid this problem, you can use the following option in your kernel configuration file. options "SC_MOUSE_CHAR=3" Add the above line to your kernel configuration file and rebuild the kernel, then the console driver will use font for the character codes 3 thourgh 6 to display the mouse cursor. The characters 208 through 211 should be shown properly. Kazu From: "Daniel C. Sobral" To: adam@whizkidtech.net Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: conf/10715: Console font loading problem at boot time Date: Mon, 22 Mar 1999 21:48:40 +0900 This sounds suspiciously like the characters being used by the mouse code. Do you have mouse enabled? adam@whizkidtech.net wrote: > > >Number: 10715 > >Category: conf > >Synopsis: Console font loading problem at boot time > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun Mar 21 15:20:00 PST 1999 > >Closed-Date: > >Last-Modified: > >Originator: G. Adam Stanislav > >Release: 3.1-RELEASE #0 > >Organization: > Whiz Kid Technomagic > >Environment: > FreeBSD dunaj.whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE #0: Mon Feb 15 11:08:08 GMT 1999 jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC i386 > > >Description: > When rc.conf contains screen fonts to be loaded, it loads them improperly. I noticed it when I developed a Central-European key map, and type characters number 208, 209, and 211 (0-based). The screen font is loaded, and everything shows up properly, except those three characters. I have to manually reload the font with vidcontrol -f 8x16 iso02-8x16.fnt . After that, I can see all characters properly. > >How-To-Repeat: > Place iso02-8x16 in your rc.conf as your default 8x16 console font. Reboot. Type Alt-208, Alt-209, Alt-211 using your numeric keypad. You will either get a blank space, a wrong character or complete junk. Run vidcontrol -f 8x16 iso02-8x16.fnt, then type those characters again. This time, they will appear on your screen properly. (This is using a local console, I have not tried it remotely -- I am not equiped for that). > >Fix: > As an internim fix, I use vidcontrol to load the font manually after booting. Incidentally, I tried to use vidcontrol from a start-up script, and it did not work... I have to do it manually after booting and logging on. > > >Release-Note: > >Audit-Trail: > >Unformatted: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" From: "G. Adam Stanislav" To: Kazutaka YOKOTA Cc: freebsd-gnats-submit@freebsd.org, "Daniel C. Sobral" Subject: Re: conf/10715: Console font loading problem at boot time Date: Mon, 22 Mar 1999 09:57:24 -0600 At 13:39 22-03-1999 +0900, Kazutaka YOKOTA wrote: >You are using the mouse cursor in the text console, right? > >This is a known problem when you enable the mouse cursor. The console >driver uses font for the character codes 208 though 211 to display the >mouse cursor. Ouch! Those codes are used for real characters not only by ISO-8859-2, which is what I happen to require, but, as far as I know, by all varieties of the ISO-8859 group of standards. On the other hand (again AFAIK), the ISO 8859 standard group reserves character codes 128 - 159 for system use. I would strongly urge whomever is in charge of text console development to change the mouse cursor into character codes within that area. I mean by default, without the need to rebuild the kernel. After all, outside of the English and perhaps German speaking countries, most of the world needs either one of the ISO-8859 standards, or a similar standard not yet covered by ISO. I have now disabled the mouse (since I have not figured out how to take advantage of it anyway), and the problem has disappeared. But that is not an ideal solution. Thanks to everyone who replied, Adam From: "Daniel C. Sobral" To: "G. Adam Stanislav" Cc: Kazutaka YOKOTA , freebsd-gnats-submit@freebsd.org Subject: Re: conf/10715: Console font loading problem at boot time Date: Tue, 23 Mar 1999 01:34:28 +0900 "G. Adam Stanislav" wrote: > > At 13:39 22-03-1999 +0900, Kazutaka YOKOTA wrote: > >You are using the mouse cursor in the text console, right? > > > >This is a known problem when you enable the mouse cursor. The console > >driver uses font for the character codes 208 though 211 to display the > >mouse cursor. > > Ouch! Those codes are used for real characters not only by ISO-8859-2, > which is what I happen to require, but, as far as I know, by all varieties > of the ISO-8859 group of standards. > > On the other hand (again AFAIK), the ISO 8859 standard group reserves > character codes 128 - 159 for system use. I would strongly urge whomever is Yeah, sure. But PC architecture only has extra scan lines for characters 208 through 211 (or similar range, I don't quite recall). Using any others for the mouse pointer results in an ugly mouse pointer. This is actually an available option, as Yokota-san has mentioned, and is probably mentioned in the LINT. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Tue Mar 23 11:52:12 PST 1999 State-Changed-Why: Asked and answered. [Would make a great FAQ] >Unformatted: