4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

[Matthew Macy]

 ---- On Mon, 23 May 2016 19:18:12 -0700 Jonathan Anderson <jonathan at 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