From owner-freebsd-current@FreeBSD.ORG Fri May 2 15:19:38 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 1A4EDDF9 for ; Fri, 2 May 2014 15:19:38 +0000 (UTC) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCE5A13B0 for ; Fri, 2 May 2014 15:19:37 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id l6so131686qcy.23 for ; Fri, 02 May 2014 08:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DlIQHAF9PZkk6ExiNi+GlNeGsVLWbQ7vUmFAOb3vFjE=; b=jItM0Zl0lXHZbCGc6cjMRxHa08Hu8mouB2lbjMgzHhTGBh0uC6m/FO/p1w7dh5GEJt 6GFvLxsy76FkJkS99XiyTO9UlNzT7qfr3JFU187JHC8WJrs78TXMAOVVqNp26MQzEhfz skk2LF5yXfTrJX7rTC+tgnusyUeEG4pwm71HpMg1t6MH3LemzGsdFEitPCC5BrMedfDa sxpANT0L9nMQv11OE91rt9m2zuxwA6Ete3Emki00JIqflVAWs8inbWL0xYRo4q49uqWO q3h6fDGsPwJe87uVsyyTsyui7f3/6GwMxcx7whkHVZxdnoZ+6ztdzgHTMszbHnPUny6+ giAQ== MIME-Version: 1.0 X-Received: by 10.224.115.3 with SMTP id g3mr23293842qaq.19.1399043976987; Fri, 02 May 2014 08:19:36 -0700 (PDT) Sender: carpeddiem@gmail.com Received: by 10.140.49.239 with HTTP; Fri, 2 May 2014 08:19:36 -0700 (PDT) In-Reply-To: <1398979896771-5908080.post@n5.nabble.com> References: <20140427143320.GA7138@over-yonder.net> <20140501083121.GU7138@over-yonder.net> <1398935140660-5907856.post@n5.nabble.com> <1398951899525-5907951.post@n5.nabble.com> <1398963647154-5908019.post@n5.nabble.com> <1398979023495-5908076.post@n5.nabble.com> <1398979896771-5908080.post@n5.nabble.com> Date: Fri, 2 May 2014 11:19:36 -0400 X-Google-Sender-Auth: WqOm_YJLGmSuZsSk7z9PQfc78KM Message-ID: Subject: Re: newcons and beeping X From: Ed Maste To: Jakub Lach Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current 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: Fri, 02 May 2014 15:19:38 -0000 On 1 May 2014 17:31, Jakub Lach wrote: > I'm aware of another problem though (and can > clarify it now). > > If I use any other character than a basic latin set, my > prompt is not preserved. Thanks for testing! With which shell do you observe this? I don't with csh from base and zsh from ports, and it appears sh doesn't accept the characters at all. (I am testing with -CURRENT, though.) > Apart form that, newcons works, albeit kind of choppy, > do I have any control of it's resolution? Right now it defaults to 80x25 characters in a 640x480 framebuffer, and the resolution won't change until the specific driver is loaded (e.g. i915kms), and it should then switch to the proper resolution for your display. This happens automatically when X starts, but you can also manually kldload the driver. There is unfortunately no way to choose a resolution yet. > Can I make it more seamless with both X and bootloader? > > (now I have bootloader for a splitsecond, abrupt video reset, > newcons spawned with the same resolution but with > different font, after starting X and going back to newcons > it preserves X resolution) For now if you have the driver load you'll have a seamless experience between console and X, but still a blip when switching from the loader to kernel. That will be addressed on UEFI systems, but we probably won't be able to do anything about it for the non-UEFI case. -Ed