From owner-freebsd-current@FreeBSD.ORG Sat Jun 30 02:34:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3B7D106564A; Sat, 30 Jun 2012 02:34:55 +0000 (UTC) (envelope-from erich@alogreentechnologies.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.224.110]) by mx1.freebsd.org (Postfix) with ESMTP id B0DE98FC08; Sat, 30 Jun 2012 02:34:54 +0000 (UTC) Received: from x220.ovitrap.com ([122.129.201.29]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id q5U2YMi8013540; Fri, 29 Jun 2012 20:34:49 -0600 From: Erich Dollansky Organization: ALO Green Technologies To: freebsd-x11@freebsd.org Date: Sat, 30 Jun 2012 09:34:15 +0700 User-Agent: KMail/1.13.7 (FreeBSD/10.0-CURRENT; KDE/4.8.3; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201206300934.15441.erich@alogreentechnologies.com> X-Mailman-Approved-At: Sat, 30 Jun 2012 02:44:38 +0000 Cc: Andrey Fesenko , freebsd-current Subject: Re: GPU_KMS still not working CURRENT X220 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2012 02:34:56 -0000 Hi, On Thursday, June 28, 2012 11:15:54 PM Kevin Oberman wrote: > On Thu, Jun 28, 2012 at 8:45 AM, Andrey Fesenko wrote: > > I have lenovo thinkpad x220 > > > > # uname -a > > FreeBSD bsdx220 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r237683: Thu Jun > > 28 08:41:40 MSK 2012 root@bsdx220:/usr/obj/usr/src/sys/MY_INTEL > > amd64 it works for me with this: FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #7: Thu Jun 28 09:09:16 WIT 2012 > > > > # pciconf -lvb > > vgapci0@pci0:0:2:0: class=0x030000 card=0x21da17aa chip=0x01268086 > > rev=0x09 hdr=0x00 > > vendor = 'Intel Corporation' > > device = '2nd Generation Core Processor Family Integrated > > Graphics Controller' > > class = display > > subclass = VGA > > bar [10] = type Memory, range 64, base 0xf0000000, size 4194304, enabled > > bar [18] = type Prefetchable Memory, range 64, base 0xe0000000, > > size 268435456, enabled > > bar [20] = type I/O Port, range 32, base 0x6000, size 64, enabled > > > > After # kldload i915kms screen is black, if # kldunload i915kms panic > > Don't do this. It has been clearly stated that i915kms my not be > unloaded and that attempting to unload it WILL panic the system. > > Also, don't load i945kms. This WILL lock up the system with a blank screen. > it works for me. I use this kind of script to start X: sudo kldload i915kms sudo kldload acpi_call sudo chmod 666 /dev/acpi startx > The modules required are autoloaded during Xorg initialization. Just > make absolutely sure that you have the latest version of > xf-video-intel. (If you installed a rather early version of the KMS > code, it is possible that you have two xf-video.intel* ports in your > tree, thought I don't expect this is the case. This could be the real reason why it fails But I must say that it hangs on rare occasions. It might has to do with playing with the mouse or the keyboard during the start-up phase of X. At least, I did not notice a freeze when I did not play around with them during the start of X. Erich