From owner-freebsd-bugs Sun Mar 21 20:40:35 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 811F415211 for ; Sun, 21 Mar 1999 20:40:20 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id UAA54702; Sun, 21 Mar 1999 20:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 21 Mar 1999 20:40:02 -0800 (PST) Message-Id: <199903220440.UAA54702@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kazutaka YOKOTA Subject: Re: conf/10715: Console font loading problem at boot time Reply-To: Kazutaka YOKOTA Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/10715; it has been noted by GNATS. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message