From owner-freebsd-questions@FreeBSD.ORG Fri Oct 14 18:12:40 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BA7116A424 for ; Fri, 14 Oct 2005 18:12:40 +0000 (GMT) (envelope-from jnevans@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB83743D4C for ; Fri, 14 Oct 2005 18:12:36 +0000 (GMT) (envelope-from jnevans@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so338025qbd for ; Fri, 14 Oct 2005 11:12:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=t/P8THiE/9NkiYDmFQkJMsxB7ANmOsgNUXGi8r2gjZ5cNXwAx/pSU1kIl+mXBwslhm92yneCpYIe/GhwVo1GWKfL/Ndearuwv2YtION3Xcyn8uhVnGgQ5g5HGFhNNqqkUWh2tsYwE/rl3aobmLnTWJ9IkMqKrkCBMVfKFc1gjt0= Received: by 10.65.52.9 with SMTP id e9mr974899qbk; Fri, 14 Oct 2005 11:12:36 -0700 (PDT) Received: by 10.65.114.20 with HTTP; Fri, 14 Oct 2005 11:12:36 -0700 (PDT) Message-ID: <2cbc9d820510141112q69db8bd1j3dfd12b265ec6b18@mail.gmail.com> Date: Fri, 14 Oct 2005 11:12:36 -0700 From: Jared Evans To: Ask FreeBSD In-Reply-To: <2cbc9d820510141024i80098bdpee425dd4d0eb19b6@mail.gmail.com> MIME-Version: 1.0 References: <2cbc9d820510141024i80098bdpee425dd4d0eb19b6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: How to get a high resolution console for FreeBSD inside a VMWare image? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 18:12:40 -0000 I looked over the link but I don't think it's related to the solution I'm looking for. I don't have any problems with high resolution X console. I'm talking about the regular text console when you first boot the machine. Jared >yeah...you'll need to install the vmware tools for FreeBSD. >Here's the link: > >http://www.vmware.com/support/ws45/doc/new_guest_tools_ws.html#1008244 > >I was in the same situation and it worked for me. > >Teo On 10/14/05, Jared Evans wrote: > > I know that this isn't exactly a standard configuration (VMWare as oppose= d > to native installation) for FreeBSD so most of the answers I found online > weren't really applicable for me. > > I simply wanted a high resolution FreeBSD console PTYs running under > VMWare. It was surprisingly more complex than I expected: > > When attempting to change screen resolution for a console in FreeBSD > running under VMWare, I ran across this error message: > > > vidcontrol -g 100x37 VESA_800x600 > > vidcontrol: cannot set videomode inappropriate ioctl for device > > It seemed to me that VMWare was unable to init VESA correctly in console > but strangely enough Xorg is capable of changing to a higher resolution > without any problems. > > After some googling: > > VESA driver in current source tree checks the NONVGA flag of VESA > information block when loading. If this flag is set it will refuse to > initialize. Most VESA adapters do not set this flag, but the virtual disp= lay > adapter in VMWare does. > > in src/sys/i386/isa/vesa.c, there is a check for the flag V_NONVGA in lin= e > 655. If you comment it out, flag check will be bypassed. After all, if Xo= rg > can use higher resolution, there shouldn't be a problem using VESA on the > console! > > Re-compiling my kernel to include the below as suggested by several more > web searches: > > options VESA > options SC_PIXEL_MODE > options VGA_WIDTH90 > > rebooting then: > > > vidcontrol -g 100x37 VESA_800x600 > > vidcontrol: operation not supported by device > > Any more tips for me? > -- http://jarednevans.typepad.com