From owner-freebsd-x11@freebsd.org Sun May 29 19:21:27 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 175FBB5357F for ; Sun, 29 May 2016 19:21:27 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07F53199E; Sun, 29 May 2016 19:21:26 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1464549679754973.9914145117731; Sun, 29 May 2016 12:21:19 -0700 (PDT) Date: Sun, 29 May 2016 12:21:19 -0700 From: Matthew Macy To: =?UTF-8?Q?=22Ren=C3=A9_Ladan=22?= Cc: "freebsd-x11" Message-ID: <154fdf6a252.ded3c290281065.8333167109007661706@nextbsd.org> In-Reply-To: References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> <5e9c72c8-eb73-eff6-9d20-03e5bc423ec0@freebsd.org> Subject: Re: CFT update day 2 MIME-Version: 1.0 User-Agent: Zoho Mail X-Mailer: Zoho Mail Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 19:21:27 -0000 =20 =20 It sounds like I just need to make the newer xf86-intel work. T= he old one probably simply isn't able to support newer chips. Thanks for th= e report.-M---- On Sun, 29 May 2016 12:15:47 -0700 Ren=C3=A9 Ladan wrote ----On 29-05-16 18:37, Matthias Haas wrote: > Am 29.05.201= 6 um 16:51 schrieb Ren=C3=A9 Ladan: >> On 23-05-16 10:12, Matthew Macy wrot= e: >>> The highlights for today are the following: >>> >>> Bug fixes: >>> -= Will Andrews fixed attach for some laptops (such as the Carbon X1). >>> = The Carbon X1 has a quirky BIOS that doesn't allow the OS to >>> enumer= ate the GPU's interrupt. >>> - Will Andrews identified a conditionally unin= itialized return in >>> idr_find that could lead to a panic in some case= s. >>> - Fixed a panic in mtrr_del frequently seen when attach failed. >>> = - Sleep/wakeups with interrupts are largely implemented correctly >>> no= w. Previously a polling 10ms sleep was used. I'm still >>> concerned tha= t the code really needs to be level-triggered. >>> >>> Cleanups: >>> - Logg= ing is now enabled for the first 10s after attach unless >>> dev.drm.drm= _debug_keep=3D1. >>> - Unimplemented warnings are off by default. >>> >> [.= ..snip USB instructions...] >>> If using the github repo, make sure you're = using the drm-next-4.6 >>> branch. >>> >> I tested the latest github versio= n on my laptop (an Acer Aspire >> E5-773G-78RN with an Intel HD 520 GPU, se= e [1]), some results: >> >> - xfce4 starts, no visual artifacts >> - XV is = disabled but present according to xdpyinfo, i.e. mplayer renders >> movies = with black borders in full screen mode >> - glxgears gets up to 30 fps full= screen (so something is not >> accelerated) >> - HDMI output works (when X= is started after initially plugging in the >> cable), the TV image keeps g= etting updated if I close the lid >> - switching back and forth between X a= nd the console works >> - stellarium works >> >> Maybe xf86-video-intel 2.2= 1.15 is missing an PCI id? > It is indeed missing a few PCI ids, I created = 2 patches that add those > missing ids, but that doesn't seem to be enough = in my case (Iris 550). > You may try them anyway and see if they change any= thing for you, but I > can't give any support as I'm only a web developer a= nd all this stuff is > not really my area of expertise. With a patched xf8= 6-video-intel the screen freezes and switching back to the console does not= work either. SSH login still works fine. Although Xorg looks frozen, Xorg.= log shows that acceleration should work now, as shown in the attached Xorg.= log diff (with timestamps removed). A kernel log from around the freeze is = attached too. This is with the drm-next-4.6 branch at commit 1e9ceda8a2a5b= 5eb45b3cd692987edc8b410817f >> [1] https://wiki.freebsd.org/Laptops/Acer_A= spire_E5_773G_78RN Cheers, Ren=C3=A9 =20 =20 =20 =20 =20