From owner-freebsd-questions@FreeBSD.ORG Sat Oct 15 20:35:32 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 B15C516A41F for ; Sat, 15 Oct 2005 20:35:32 +0000 (GMT) (envelope-from jnevans@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2195C43D46 for ; Sat, 15 Oct 2005 20:35:32 +0000 (GMT) (envelope-from jnevans@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so500471qbd for ; Sat, 15 Oct 2005 13:35:32 -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=kQDC9aGNdu6LjuAHZVWqdbBWEX4JEhyBbhLpHwfyHGMuMLofbCl7av7Z4tRfzbuiWWbdMgygqtMolGn9POSwLj6C9xD5pylrr0dADhcQhEZiHEle769XyXfd3EndMWND0eVddUS7khwlKx/O+5pqMXCTepy99IW2IgRJUAhsjU8= Received: by 10.65.203.14 with SMTP id f14mr724335qbq; Sat, 15 Oct 2005 13:35:31 -0700 (PDT) Received: by 10.65.114.20 with HTTP; Sat, 15 Oct 2005 13:35:31 -0700 (PDT) Message-ID: <2cbc9d820510151335p55d69785oc876161f4d425ad4@mail.gmail.com> Date: Sat, 15 Oct 2005 13:35:31 -0700 From: Jared Evans To: Ask FreeBSD In-Reply-To: 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: Sat, 15 Oct 2005 20:35:32 -0000 Thanks for taking the time to reply. I shall try your patch and see if I ca= n get it to work. Jared On 10/14/05, Nikolas Britton wrote: > > On 10/14/05, Jared Evans wrote: > > I know that this isn't exactly a standard configuration (VMWare as > opposed > > 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 consol= e > 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 > display > > adapter in VMWare does. > > > > in src/sys/i386/isa/vesa.c, there is a check for the flag V_NONVGA in > line > > 655. If you comment it out, flag check will be bypassed. After all, if > Xorg > > 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 mor= e > 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? > > You computer (VMware) doesn't have a "proper" VESA BIOS and that is > why 800x600 raster text mode won't work etc. FreeBSD 6 has this all > worked just put 'allscreens_flags=3D"MODE_279"' in rc.conf for > 1024x768... you can get a list of other modes supported by typing in > vidcontrol -i MODE (I think, can never remember :-)). if you want this > for FreeBSD 5.x then your going to have to manually patch your system, > but I have a simple script that will do it for you. somewhere around > here...... check for patch errors after you run the script. > -------------------------------------------------- > cd /tmp > rm current-vesa_patch.tar.gz > fetch http://www.nbritton.org/uploads/current-vesa_patch.tar.gz > rm -r current-vesa_patch > tar -zxf current-vesa_patch.tar.gz > cd /usr/src/sys/dev/syscons > patch cd /usr/src/usr.sbin/vidcontrol > cp /tmp/current-vesa_patch/current-vidcontrol.1 ./vidcontrol.1 > cp /tmp/current-vesa_patch/current-vidcontrol.c ./vidcontrol.c > make && make install && make clean > ----------------------------------------------------- > You still need to put in your kernel (both FreeBSD 5 and 6): > options VESA > options SC_PIXEL_MODE > > and when you cvsup your src in FreeBSD 5 you will need to reapply the > patch, cvsup will overwrite the files becouse the cvs revision tags > don't match up. > > Anyways.... > > -- http://jarednevans.typepad.com