dillon at backplane.com
Thu Jul 9 22:28:39 PDT 2015
It really is best to use X, it should be well supported on Haswell cpus.
You get all sorts of goodies like nice acceleration, hardware video
We do have some primitive kms console frame buffer support but it's really
just designed for simple console stuff and not designed to be a work
environment. Example use case would be to put this in your
And then 'kldload i915kms' manually after booting to test it out and if it
works you can put the kldload i915kms into your /etc/rc.local. Video
resolution will default to the highest-supported monitor resolution. The
output id in the resolution hint depends on the system setup (I'm not sure
how to list available outputs).
The vga stuff is fast becoming obsolete.
And, really, this console stuff isn't designed for work environments
either. You want to use X with the intel driver. The GPU support
significantly improves performance over VESA or anything else.
On Thu, Jul 9, 2015 at 7:32 PM, Alex Merritt <merritt.alex at gmail.com> wrote:
> Hello DF users,
> I am trying to enable console support for larger resolutions without using
> X. I read that enabling "options VESA" makes more options available to
> "vidcontrol" to switch into, but when I build, it tells me that option is
> unrecognized. I have a Haswell CPU (i7-4800MQ) and am using 4.0.6 currently.
> # vidcontrol -i mode
> shows only modes 24, 27, 30, 32, 34.
> # pciconf -l | grep vga
> vgapci0 at pci0:1:0:0 class=0x030000 card=0x197b103c chip=0x11fc10de
> rev=0xa1 hdr=0x00
> Should I just be using X instead of trying this route? What do you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users