From owner-freebsd-stable Sat Jun 15 7:31:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from Tor.farlep.net (tor.farlep.net [213.130.1.225]) by hub.freebsd.org (Postfix) with ESMTP id C582F37B410 for ; Sat, 15 Jun 2002 07:31:48 -0700 (PDT) Organization: Farlep-Internet Received: from cyanide.cat5 (cat5.farlep.net [213.130.5.107]) by Tor.farlep.net with ESMTP id g5FEUU828120; Sat, 15 Jun 2002 17:30:30 +0300 Date: Sat, 15 Jun 2002 17:31:28 +0300 (EEST) From: FreeBSD technical account To: jeremie le-hen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: problem changing to VESA mode with vidcontrol under 4.6-RC In-Reply-To: <20020615145943.A5513@arlette.epita.fr> Message-ID: <20020615172918.B9377-100000@cyanide.pro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You must have VESA support in kernel to switch between VESA modes: options VESA options VGA_WIDTH90 On Sat, 15 Jun 2002, jeremie le-hen wrote: > Date: Sat, 15 Jun 2002 14:59:43 +0200 > From: jeremie le-hen > To: freebsd-stable@FreeBSD.ORG > Subject: problem changing to VESA mode with vidcontrol under 4.6-RC > > Hi, > > this problem might surely be easy to solve, but i'm not a VESA master and i didn't succeed in resolving it: > > With 4.5 release, "vidcontrol VESA_132x60" was working perfectly, but i upgraded to 4.6-RC and i upgraded my bios in the same time... :/ I know it's not a very good idea, but now it's done, and i cannot come back. But now, I cannot use any VESA mode any longer. In my opinion, FreeBSD is not culprit, but i wonder if someone have any idea to help me, maybe a diagnostic tool i don't know, ... > > Thanks in advance. > -- > Jeremie aka TataZ > le-hen_j@epita.fr > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message