From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stefan G. Weichinger" Subject: Re: I915 regression : black screen at boot / Sandybridge Mobile (GT2) Date: Mon, 30 Jan 2012 22:19:42 +0100 Message-ID: <4F27096E.20007@xunil.at> References: <20120112103636.4299097a@jbarnes-desktop> <20120112112531.0daa6129@jbarnes-desktop> <20120112115715.23b6f8e1@jbarnes-desktop> <20120112121737.793d85bc@jbarnes-desktop> <20120112124949.03f14e96@jbarnes-desktop> <20120112142424.470eddd0@jbarnes-desktop> <20120112144526.29dc235c@jbarnes-desktop> Reply-To: lists@xunil.at Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from postler.lichtfels.com (postler.lichtfels.com [78.46.92.195]) by gabe.freedesktop.org (Postfix) with ESMTP id 3E3B79E961 for ; Mon, 30 Jan 2012 13:19:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by postler.lichtfels.com (Postfix) with ESMTP id 590B820DA4 for ; Mon, 30 Jan 2012 22:19:22 +0100 (CET) Received: from postler.lichtfels.com ([127.0.0.1]) by localhost (postler.lichtfels.com [127.0.0.1]) (amavisd-maia, port 10024) with LMTP id 20113-08 for ; Mon, 30 Jan 2012 22:19:21 +0100 (CET) Received: from [172.32.99.26] (mail.oops.co.at [213.129.238.225]) by postler.lichtfels.com (Postfix) with ESMTPA id CCE4720DA2 for ; Mon, 30 Jan 2012 22:19:21 +0100 (CET) In-Reply-To: <20120112144526.29dc235c@jbarnes-desktop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Am 2012-01-12 23:45, schrieb Jesse Barnes: >> Tested with the (attached, hopefully correct) patch and it still works. :-) > > Yay, thanks a lot! I'll send it upstream now. The gentoo-devs still haven't fixed that yet ... in their gentoo-sources-3.2.1-r2, my reported bug is still unreplied .... The patch doesn't match anymore (not even somehow ...), is there a patch already against the newer kernel? Without patching the misbehavior is still there. Thanks, Stefan