From owner-freebsd-current Fri Dec 3 1: 1:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C5FA14C57 for ; Fri, 3 Dec 1999 01:01:44 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-25.iptelecom.net.ua [212.9.227.25]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA15945; Fri, 3 Dec 1999 11:04:46 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA10599; Fri, 3 Dec 1999 10:59:31 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38478671.F57E2780@altavista.net> Date: Fri, 03 Dec 1999 10:59:29 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: Problem with syscons in VESA mode References: <38465D07.8A25A0D@altavista.net> <199912030018.JAA29566@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > >I'm using non-standard 100x37 console mode on my notebook, because in 80x25 > >text mode letters seems too big for my 12' panel, while other modes doesn't > >cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 > >100x37 mode (instead of default 80x25) with 8x16 font, and in most cases all > >works just fine (including ncurses and dialog bases apps), but sometimes when > >I'm building world or some other app text suddenly shifts from the edge of the > >screen by several spaces and all text passed to the console after that also > >being printed with that offset. For example: > [...] > > This strange behavior was reported several times in the past. It must > be related to screen update logic in syscons. But, I don't think we > have successfully fixed it at that time :-( > > It's time to analyze the problem again... Obviously... If any help with debugging/testing would be necessary please do not hesitate to contact me. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message