From owner-freebsd-current Thu Dec 2 13: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id C130614F56 for ; Thu, 2 Dec 1999 13:02:26 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA27494 for current@freebsd.org; Thu, 2 Dec 1999 22:02:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C4CA58863; Thu, 2 Dec 1999 21:06:42 +0100 (CET) Date: Thu, 2 Dec 1999 21:06:42 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: Problem with syscons in VESA mode Message-ID: <19991202210642.A96274@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <3846A672.524B188A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <3846A672.524B188A@altavista.net> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Maxim Sobolev: > It is interesting. Seems like it is not only VESA modes bug. Strange that > nobody else observed this misbehaviour. I used to see that in 132 col. mode a year or so (maybe more) and it was fixed at that time... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message