Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Oct 2005 10:24:46 -0700
From:      Jared Evans <jnevans@gmail.com>
To:        Ask FreeBSD <freebsd-questions@freebsd.org>
Subject:   How to get a high resolution console for FreeBSD inside a VMWare image?
Message-ID:  <2cbc9d820510141024i80098bdpee425dd4d0eb19b6@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
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 runnin=
g
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 bu=
t
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 displa=
y
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 more we=
b
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?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2cbc9d820510141024i80098bdpee425dd4d0eb19b6>