On 23 February 2014 11:48, Ilia Mirkin imirkin@alum.mit.edu wrote:
On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman daniel@quora.org wrote:
On 9 February 2014 02:57, Ilia Mirkin imirkin@alum.mit.edu wrote:
On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman daniel@quora.org 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:
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 :(
Interestingly, it turns out that the screen corruption occurs on every boot (booting with nouveau.noaccel=1 for now), and I can consistently work around it by one suspend-resume cycle.
Does booting with nouveau.config=NvForcePost=1 help?
Still no cigar with nouveau.config=NvForcePost=1.
I meant to add that restarting X or changing resolutions doesn't resolve the issue. The corruption is consistently 16-pixel wide by 1 high stippling on a consistent address range of the framebuffer.
Thanks, Daniel