Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752132AbaBHS57 (ORCPT ); Sat, 8 Feb 2014 13:57:59 -0500 Received: from mail-ob0-f171.google.com ([209.85.214.171]:43606 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752025AbaBHS56 (ORCPT ); Sat, 8 Feb 2014 13:57:58 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 8 Feb 2014 13:57:57 -0500 X-Google-Sender-Auth: RY6JlxeqGwJS9koWkzuq6HTbprw Message-ID: Subject: Re: nouveau graphical corruption in 3.13.2 From: Ilia Mirkin To: Daniel J Blueman Cc: "nouveau@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , Linux Kernel , Dave Airlie , Ben Skeggs Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman wrote: > Interestingly, there was graphical failure booting 3.6.11, even > nvidia-current fails to initialise, but these two issues could be due > to running the Xorg stack in Ubuntu 14.04 pre-release. Using > nouveau.noaccel=1 works great for the first X session, but after > logging out, lightdm and the next session experiences this consistent > screen corruption: > > http://quora.org/nouveau-corruption.jpg Does that just happen in 3.6.11 or even in 3.13? If the latter, that points to some key lack of understanding of... something. With noaccel, we're not using pgraph or anything fancy -- it's just a framebuffer, basically. So if we can't even render _that_ right... Hopefully someone else will pipe up re your other issues -- my knowledge base on this is exhausted :( -ilia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/