From owner-freebsd-current@FreeBSD.ORG Thu May 1 13:45:01 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB2F18C0 for ; Thu, 1 May 2014 13:45:01 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C5771CD0 for ; Thu, 1 May 2014 13:45:00 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WfrIJ-0000eg-He for freebsd-current@freebsd.org; Thu, 01 May 2014 06:44:59 -0700 Date: Thu, 1 May 2014 06:44:59 -0700 (PDT) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1398951899525-5907951.post@n5.nabble.com> In-Reply-To: References: <20140427143320.GA7138@over-yonder.net> <20140501083121.GU7138@over-yonder.net> <1398935140660-5907856.post@n5.nabble.com> Subject: Re: newcons and beeping X MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 13:45:01 -0000 I think that newcons used somehow my terminus font from X (?) and there were no polish characters. I had/have in rc.conf font8x14=iso02-8x14 font8x16=iso02-8x16 font8x8=iso02-8x8 but it made no difference. It was on 10-STABLE, somewhat early after merge. I may try it again later today. -- View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907951.html Sent from the freebsd-current mailing list archive at Nabble.com.