From owner-freebsd-x11@FreeBSD.ORG Sat Jun 23 19:51:26 2012 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 80F801065676 for ; Sat, 23 Jun 2012 19:51:26 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep14.mx.upcmail.net (fep14.mx.upcmail.net [62.179.121.34]) by mx1.freebsd.org (Postfix) with ESMTP id 008778FC15 for ; Sat, 23 Jun 2012 19:51:25 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep14-int.chello.at (InterMail vM.8.01.05.04 201-2260-151-105-20111014) with ESMTP id <20120623195124.NBXE8105.viefep14-int.chello.at@edge01.upcmail.net> for ; Sat, 23 Jun 2012 21:51:24 +0200 Received: from [127.0.0.1] ([77.250.114.160]) by edge01.upcmail.net with edge id RvrN1j00f3TiT9101vrPCt; Sat, 23 Jun 2012 21:51:24 +0200 X-SourceIP: 77.250.114.160 Message-ID: <4FE61E39.4040202@rainbow-runner.nl> Date: Sat, 23 Jun 2012 21:51:21 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-x11@freebsd.org References: <20120622213442.GL2337@deviant.kiev.zoral.com.ua> <20120623085812.GN2337@deviant.kiev.zoral.com.ua> <20120623165145.GW2337@deviant.kiev.zoral.com.ua> <20120623184513.GZ2337@deviant.kiev.zoral.com.ua> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 120623-0, 23-06-2012), Outbound message X-Antivirus-Status: Clean Subject: Re: GPU_KMS still not working for me since merge X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Jun 2012 19:51:26 -0000 On 23-6-2012 21:15, Kevin Oberman wrote: > On Sat, Jun 23, 2012 at 11:45 AM, Konstantin Belousov > wrote: >> On Sat, Jun 23, 2012 at 11:39:23AM -0700, Kevin Oberman wrote: >>> On Sat, Jun 23, 2012 at 9:51 AM, Konstantin Belousov >>> wrote: >>>> On Sat, Jun 23, 2012 at 09:17:01AM -0700, Kevin Oberman wrote: >>>>> On Sat, Jun 23, 2012 at 1:58 AM, Konstantin Belousov >>>>> wrote: >>>>>> Verify that i915kms is loaded. If it is not, investigate why. >>>>> There is nothing of relevance in dmesg. But kldstat makes the problem >>>>> very clear.. After 'startx', I see i915.ko has been loaded along with drm.ko. >>>>> No i915kms.ko nor the i2c stuff that used to be pulled in. >>>>> >>>>> When I was running the pre-merge KMS code from back in late April, there >>>>> was no i915kms.ko...only i915.ko. >>>>> >>>>> Is there something I need to do to cause the correct module to load? >>>>> I don't have any Xorg.conf file and never have had for this laptop. >>>> Recent ddx Intel driver from ports loads right module automatically. >>> What is "recent ddx Intel driver"? I did re-build the xf86-video-intel >>> driver and, but I don't see any "ddx" reference. >>> >>> In any case, I deleted the i915.ko and linked (hard) i915kms.ko to >>> i915.ko and X now starts correctly. Not really >>> an ideal solution, but it does work for the moment. >> pooma% cvs -qR log -r 1.24 x11-drivers/xf86-video-intel/Makefile /usr/ports >> RCS file: /usr/local/arch/ncvs/ports/x11-drivers/xf86-video-intel/Makefile,v >> Working file: x11-drivers/xf86-video-intel/Makefile >> head: 1.24 >> [snip] >> revision 1.24 >> date: 2012/06/07 10:27:21; author: kwm; state: Exp; lines: +2 -1 >> Teach the KMS intel driver how the KMS i915 kernel module in head is named. >> >> Reviewed by: miwi@ >> > Mystery solved! The old xorg-devel with the kms patches produced > /usr/ports/c11-drivers/xf86-video-intel-kms and 'portmaster > xf86-video-intel was just re-building that driver. It was not building > the current one. > > I ran 'portmaster -o 11-drivers/xf86-video-intel > x11-drivers/xf86-video-intel-kms' which replaced the old, development > one with the correct one. I will delete the old one. I suspect others > who integrated xorg-devel and your earlier patches and are using > portmaster are hitting the same issue. > > Thanks again! Thats a really old port you had. I will see if I can find some time to make our mergescript smarter with regards to removed ports and such. -Koop