From owner-freebsd-current@FreeBSD.ORG Thu Oct 31 21:01:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 947C75CE for ; Thu, 31 Oct 2013 21:01:40 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [70.91.206.90]) by mx1.freebsd.org (Postfix) with ESMTP id 77F9A227D for ; Thu, 31 Oct 2013 21:01:40 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 31 Oct 2013 14:05:29 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.4/8.14.4) with ESMTP id r9VL1d5D090449; Thu, 31 Oct 2013 14:01:39 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.4/8.14.4/Submit) id r9VL1cAC090447; Thu, 31 Oct 2013 14:01:38 -0700 (PDT) (envelope-from ambrisko) Date: Thu, 31 Oct 2013 14:01:38 -0700 From: Doug Ambrisko To: Aleksandr Rybalko Subject: Re: newcons comming Message-ID: <20131031210138.GC30328@ambrisko.com> References: <20131025151847.2a1b83de93335040797ceaf1@ddteam.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131025151847.2a1b83de93335040797ceaf1@ddteam.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 31 Oct 2013 21:01:40 -0000 On Fri, Oct 25, 2013 at 03:18:47PM +0300, Aleksandr Rybalko wrote: | Hello fellow hackers! | | I finally reach the point when I can work with newcons instead of | syscons on my laptop. Yes, I know it still buggy and have a lot of | style(9) problems. But we really have to get it into HEAD and 10.0 to | enable shiny new Xorg features, drivers, etc. I built the kernel from: base/user/ed/newcons/ and installed it on my new ThinkPad T530 with Intel graphics chip. In general it works better since now syspend and resume works with and without X. However, as with my prior ThinkPads I need to switch out of X to suspend and resume. So I have vidcontrol -s 1 in my /etc/rc.suspend and vidcontrol -s 9 in /etc/rc.resume. If I don't the display ends up corrupted but somewhat working. I had to kldload i915kms in /etc/rc.local since having it there at boot via /boot/loader.conf resulted in the system not booting. I need i915kms for X so I don't need to use vesa mode. The FreeBSD logo on boot is interesting but I'd prefer seeing FreeBSD boot messages to see what is happening. I'm not sure if there is a flag to disable that since I have played with it much. However, on a whole it is much improved since with i915kms and newcons when in X via vesa I couldn't switch to a non-X display since it was blank. Thanks, Doug A.