From owner-freebsd-current@FreeBSD.ORG Fri May 22 07:31:56 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FDA827A; Fri, 22 May 2015 07:31:56 +0000 (UTC) Received: from mail.kronometrix.org (mail.kronometrix.org [54.72.43.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "kronometrix.org", Issuer "kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D6B561A3A; Fri, 22 May 2015 07:31:55 +0000 (UTC) Received: from [192.168.1.171] (188-127-209-196.cust.suomicom.net [188.127.209.196]) (authenticated bits=0) by mail.kronometrix.org (8.14.9/8.14.9) with ESMTP id t4M7Zfuj087709 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 22 May 2015 07:35:41 GMT (envelope-from sparvu@kronometrix.org) Message-ID: <555EDB63.7040700@kronometrix.org> Date: Fri, 22 May 2015 10:31:47 +0300 From: Stefan Parvu Reply-To: sparvu@kronometrix.org Organization: kronometrix.org User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Adrian Chadd CC: Johannes Jost Meixner , "current@freebsd.org" , Lutz Bichler , Michael Reifenberger Subject: Re: i915kms.ko regression? References: <555EA666.405@FreeBSD.org> <555ED40A.9080405@kronometrix.org> In-Reply-To: OpenPGP: id=CED4DF6EB415AB03087F1B5C1CB2B549DE465D09 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Fri, 22 May 2015 07:31:56 -0000 > ok. i really do bet it's a backlight config problem, and unfortunately > I don't have the laptop to be able to debug it. Sorry :( no worries. But what does this mean in practice for future: do we need to wait for a new drm2 update or this problem will stay this way until somebody really does fix it ? -- Stefan Parvu