Date: Mon, 23 May 2016 19:34:32 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Jonathan Anderson" <jonathan@FreeBSD.org> Cc: "<freebsd-x11@freebsd.org>" <freebsd-x11@freebsd.org> Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported Message-ID: <154e09d170e.cf7aabdb205148.1446591210771811744@nextbsd.org> In-Reply-To: <40127652-dac5-38d2-041d-82cb6afa6a13@FreeBSD.org> References: <154d7562f75.116fac600120763.1508477402245154899@nextbsd.org> <47f48f29-3d52-8273-ab60-6e546ac02d03@FreeBSD.org> <154e07bdd60.c4c90bf9204116.1188840800130718382@nextbsd.org> <40127652-dac5-38d2-041d-82cb6afa6a13@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Mon, 23 May 2016 19:18:12 -0700 Jonathan Anderson <jonathan@FreeBSD.org> wrote ---- > On 05/23/16 23:28, Matthew Macy wrote: > > > > [...] > > > > > > > > Please send issue/success reports to the freebsd-x11 mailing list. > > > > I may be preoccupied with work matters for periods of time. Sending > > > > it to the list makes sure that the messages don't get lost. > > > > > > I'm using an Asus ZenBook UX305CA (Skylake m3-6Y30). With commit > > > 1e9ceda, after kldload'ing i915, the text console seems to work fine > > > (just a quick blink from the EFI framebuffer to i915). With no X > > > configuration files at all, I have success with glxgears and xrandr, and > > > I can run gtk-redshift (which didn't work with the scfb driver). > > > However, I think that various bits of rendering are happening in software: > > > > > > /var/log/Xorg.0.log (also attached): > > > ``` > > > [ 1124.648] (WW) intel(0): cannot enable DRI2 whilst forcing software > > > fallbacks > > > > > > Your permissions are wrong. You need to add yourself to the video group. > > You're right: I was not in the video group. After adding myself (and > logging out/in), however, I still get the same warning. I've attached my > new Xorg.0.log in case it's helpful. It's not, you'll have to re-enable logging before you start running glxgears. dev.drm.drm_debug=-1. It turns itself off 10s after load so that it doesn't interfere with usability because most problems occur at attach. Once you enable debugging you'll see copious output to /var/log/messages. Look for failures in there. Send me any info you can get. Also did you exit your shell, log back in and then restart X after adding yourself to the group? A simple test is to run glxgears as root and see what it says. Thanks. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154e09d170e.cf7aabdb205148.1446591210771811744>