From owner-freebsd-x11@FreeBSD.ORG Sat Jul 20 04:52:43 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 475FB20A for ; Sat, 20 Jul 2013 04:52:43 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by mx1.freebsd.org (Postfix) with ESMTP id 25A74238 for ; Sat, 20 Jul 2013 04:52:42 +0000 (UTC) Received: from fed1rmimpo210 ([68.230.241.161]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130720045236.EJUH3892.fed1rmfepo101.cox.net@fed1rmimpo210> for ; Sat, 20 Jul 2013 00:52:36 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo210 with cox id 2Usc1m0052oShb201UscRM; Sat, 20 Jul 2013 00:52:36 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.51EA1794.008C,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=drIF/Sc4 c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=-sc1xts7OiMA:10 a=ktNfuVtv0skA:10 a=IkcTkHD0fZMA:10 a=05pWP5ZVAAAA:8 a=hKplxj3TifQA:10 a=N0hn25qrDHYSdf4V7qQA:9 a=QEXdDO2ut3YA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6JLftOO001874; Fri, 19 Jul 2013 21:41:56 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51EA1884.5030608@reynoldsnet.org> Date: Fri, 19 Jul 2013 21:56:36 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 04:52:43 -0000 On 7/19/2013 9:15 PM, Kevin Oberman wrote: > > Did you define WITH_KMS in /etc/make.conf? Did you build libdrm with > the KMS option? yes, i did have that in there. I should have reported that. I'm pretty sure that libdrm was built with this option because at one point I just said screw it and blew away all packages and just started over to make sure I had ALL good components of Xorg 7.7. But I will double check. > > There have been reports of issues with Haswell GPUs, so it still may > not work with the current KMS code, but it is worth a try. (And it > would be appreciated if you could report the results.) With my little "tester" account (as I don't want to inadvertently hose my own .kde4 setup or anything else) I was able to launch into KDE earlier this afternoon. But ... apparently it was not using the intel driver, but fell back to VESA. > > If all else fails, you can use VESA, but it will be very slow and may > have other issues. Yes, upon further inspection, what I thought was "success" I think was a fall-back to using VESA. In my Xorg.0.log: [ 17861.411] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, .... Haswell CRW Server (GT1), Haswell CRW Server (GT2), Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2), Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2), Iris(TM) Pro Graphics 5200, ValleyView PO board So it did load the driver and at least print this out, but later on in the file after a bunch of: [ 17861.959] drmOpenDevice: node name is /dev/dri/card0 [ 17861.959] Failed to change owner or group for file /dev/dri! 2: No such file or directory [ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: No such file or directory [ 17861.959] drmOpenDevice: open result is -1, (No such file or directory) [ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: No such file or directory [ 17861.959] drmOpenDevice: open result is -1, (No such file or directory) [ 17861.959] drmOpenDevice: Open failed [ 17861.959] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 17861.959] drmOpenDevice: node name is /dev/dri/card0 I see [ 17861.961] (II) VESA(0): initializing int10 [ 17861.962] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [ 17861.964] (II) VESA(0): VESA BIOS detected [ 17861.964] (II) VESA(0): VESA VBE Version 3.0 [ 17861.964] (II) VESA(0): VESA VBE Total Mem: 262080 kB [ 17861.964] (II) VESA(0): VESA VBE OEM: Intel(R) HSW Mobile/Desktop Graphics Chipset Accelerated VGA BIOS [ 17861.964] (II) VESA(0): VESA VBE OEM Software Rev: 0.0 [ 17862.017] (==) VESA(0): Depth 24, (--) framebuffer bpp 32 [ 17862.017] (==) VESA(0): RGB weight 888 [ 17862.017] (==) VESA(0): Default visual is TrueColor [ 17862.017] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0) [ 17862.017] (II) Loading sub module "ddc" [ 17862.017] (II) LoadModule: "ddc" [ 17862.017] (II) Module "ddc" already built-in [ 17862.017] (II) VESA(0): VESA VBE DDC supported [ 17862.017] (II) VESA(0): VESA VBE DDC Level 2 [ 17862.017] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec. [ 17862.029] (II) VESA(0): VESA VBE DDC read successfully .... I don't know if this was simply a fall-back or if my xorg.conf file is telling it to use vesa. As I was saying, I used the file generated by Xorg -configure and it set things up for two monitors and it has two "Device" sections, one that uses the "intel" driver and one that uses "vesa." I have not tried using no configuration file just yet. So, are there developers with the Haswell boards and it's just a matter of time before kinks get worked out? Do you suggest using no xorg.conf file? Also, as reported once I go into X via 'startx' on a console there's no coming back out. If I try it is a hard wedge. I know that's being currently worked on. If there's any kernel module or kernel config option or something that I need to have in order to even remotely have a chance at making this GPU work, please let me know. As of this moment I'm just running GENERIC/amd64, but I plan on recompiling things going forward. -jr