Graphics Support

[Alex Merritt]

Thanks, Matt, I'll pursue the X path.

The module loads, but the prompt strangely does not change, despite the
edits to loader.conf. The dmesg log doesn't show any information that the
intel driver found a device; it only says it loaded.

When I configure xorg.conf with the driver to be "intel", X is unable to
complete, claiming no device is found. The log shows the shared object
loads for Intel, but it does not find any graphics device. The CPU is
i7-4800MQ which is Haswell.

With no xorg.conf configured, X loads fine into XFCE4 but I am not
convinced the resolution is 1920x1080 (the maximum).

Any suggestions for debugging this?

-Alex

On Thu, Jul 9, 2015 at 10:28 PM, Matthew Dillon <dillon at backplane.com>
wrote:

> 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
> decoding, etc.
>
> 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
> /boot/loader.conf:
>
> kern.kms_console=1
> drm.video.dvid1="1680x1050"
>
> 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.
>
> -Matt
>
>
> 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
>> recommend?
>>
>> Thanks,
>> Alex
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20150713/a8c0253a/attachment.html>