From owner-freebsd-current@FreeBSD.ORG Mon Feb 1 21:17:46 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id B94FA106566B; Mon, 1 Feb 2010 21:17:45 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Mon, 1 Feb 2010 16:17:30 -0500 User-Agent: KMail/1.6.2 References: <20100201184446.2325c04e.ubm.freebsd@gmail.com> In-Reply-To: <20100201184446.2325c04e.ubm.freebsd@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_rT0ZLsydPD114mT" Message-Id: <201002011617.31527.jkim@FreeBSD.org> Cc: Marc UBM Bocklet Subject: Re: vidcontrol / resolution problems with latest current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 01 Feb 2010 21:17:46 -0000 --Boundary-00=_rT0ZLsydPD114mT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Monday 01 February 2010 12:44 pm, Marc UBM Bocklet wrote: > Hiho! :-) > > Recently, I updated to the latest version of 9-current and found > out that I cannot set my console resolution to 800x600 anymore. If > I try, it just goes blank or shows a few coloured, garbled lines in > the upper third of my monitor. Starting X11 blindly works, as does > switching to X11. > > I'm suspecting the recent tty/xterm changes, but I am not sure. > > > uname -a: > > FreeBSD xxx.yyy 9.0-CURRENT FreeBSD 9.0-CURRENT #17: Sat > Jan 23 14:58:47 CET 2010 > sheep@ubm.mine.nu:/usr/obj/usr/src/sys/SUBMARINE_SMP i386 > > > Relevant part of my rc.conf that I used to set console to 800x600: > > allscreens_flags="-g 100x37 VESA_800x600" > > > Relevant kernel option that I use: > > # VESA support > > options VESA > > # raster display support for 800x600 resolution > > options SC_PIXEL_MODE > > > Can anyone point me to a solution / is more info required? Hmm... The attached patch should restore the previous behavior. Jung-uk Kim --Boundary-00=_rT0ZLsydPD114mT Content-Type: text/plain; charset="iso-8859-1"; name="vesa.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="vesa.diff" --- sys/dev/fb/vesa.c +++ sys/dev/fb/vesa.c @@ -1322,7 +1322,7 @@ vesa_set_mode(video_adapter_t *adp, int mode) vesa_adp->va_window_gran = info.vi_window_gran; } vesa_adp->va_window_orig = 0; - vesa_adp->va_line_width = vesa_get_line_width(&info); + vesa_adp->va_line_width = vesa_bios_get_line_length(); vesa_adp->va_disp_start.x = 0; vesa_adp->va_disp_start.y = 0; #if VESA_DEBUG > 0 --Boundary-00=_rT0ZLsydPD114mT--