similar to: [Bug 75761] weston-launch no output - black screen

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #32 from Pekka Paalanen <ppaalanen at gmail.com> --- (In reply to comment #31) > Created attachment 100199 [details] > weston log with pixman Something is seriously wrong here: [09:58:29.402] queueing pageflip failed: Permission denied But I see you have another weston session afterwards, which seems to run, but:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #27 from nerdopolis1 at verizon.net --- I pulled out my old Dell desktop with a Pentium 4 processor, and AGB Nvidia card (NV36), and it does the same thing. Mark45 on Phoronix said this issue affected all 3 of his Nvidia cards when he tried to use my Wayland Live CD. I added the "got pageflip event" lines as suggested, and

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #26 from Pekka Paalanen <ppaalanen at gmail.com> --- What did the -1 as crtc mean? I'm not sure how this is weston-specific, though. Weston programs a pageflip on a certain crtc, and then relies on that particular crtc to send back a pageflip event as requested. So if that's the culprit, is Nouveau on some particular

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #31 from nerdopolis1 at verizon.net --- Created attachment 100199 --> https://bugs.freedesktop.org/attachment.cgi?id=100199&action=edit weston log with pixman -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #39 from nerdopolis1 at verizon.net --- I would at least like to try to just try to apply them against the 3.13 nouveau module, instead of trying to rebuild the whole kernel first? So is that the only patch I would need? I'm still on 3.13 (which is also affected), as I have been doing all of my testing on the Weston side of

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #30 from nerdopolis1 at verizon.net --- The only interesting thing that I can find in the dmesg logs is this: [ 1.509268] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 1.509269] [drm] No driver support for vblank timestamp query. -- You are receiving this mail because: You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #36 from nerdopolis1 at verizon.net --- I'm trying to compile the module... it seems that it's gone from the log now??? How do I disable werror too? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #37 from nerdopolis1 at verizon.net --- I found out how to turn off werror, but I guess I need to know what patches I need to apply... Is that the only commit that I need to try the fix? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #41 from nerdopolis1 at verizon.net --- I found the second patch too, and I applied that as well. It works now, even after I applied them to 3.13, and built just the Nouveau module. I have an older Nvidia card, I think it's NV36. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #29 from Pekka Paalanen <ppaalanen at gmail.com> --- Hmm, a third remote possibility came to mind. If the timestamp delivered with the DRM pageflip event does not advance, I suppose Weston's fade-in animation might not advance either and therefore it never fades in. However this is hard for me to believe, as I think it would

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #33 from Pekka Paalanen <ppaalanen at gmail.com> --- I filed bug #79502 for adding the detection to Weston. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #35 from Ilia Mirkin <imirkin at alum.mit.edu> --- A few pageflip-related commits landed in the repo: http://cgit.freedesktop.org/~darktama/nouveau/ http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=ff527544b0048d41a56097a66ff954fb9b0a2c75 Seems related to what was going on here. Give it a shot... (you'll need to

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #28 from Pekka Paalanen <ppaalanen at gmail.com> --- I wonder if there are two different bugs in play here. If you do get the vblank events right, like it sounds that Nerdopolis does indeed get, then does reverting the blamed nouveau kernel patch make any difference? I would be surprised if it does make a difference. This

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #24 from Lubosz Sarnecki <lubosz at gmail.com> --- Since Weston and Wayland 1.5.0 were released today, I wanted to ask about the status of this bug. Does the patch which causes the regression have enough legitimacy to stay and break Weston? Does someone understand the problem on a large scale? -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #25 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #24) > Since Weston and Wayland 1.5.0 were released today, I wanted to ask about > the status of this bug. > > Does the patch which causes the regression have enough legitimacy to stay > and break Weston? It seems like a pretty correct fix,

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wayland-bugs at lists.freedesk |nouveau at lists.freedesktop.o |top.org |rg QA Contact|

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #12 from Pekka Paalanen <ppaalanen at gmail.com> --- Setting status to NEW, since this

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #18 from Lubosz Sarnecki <lubosz at gmail.com> --- I was able to boot all commits with following boot option: nouveau.config=NvMSI=0 Thanks to xexaxo on the IRC for pointing out this option. f074d733866628973eca0ddb0c534ef4561da9e0 is the first bad commit commit f074d733866628973eca0ddb0c534ef4561da9e0 Author: Maarten

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #19 from Lubosz Sarnecki <lubosz at gmail.com> --- Reverting the patch on current Linux master (4a4389abdd9822fdf3cc2ac6ed87eb811fd43acc) fixes the issue for me. Apperently s->crtc needs to be hardcoded to -1 for the screen not to stay black when launching weston. -- You are receiving this mail because: You are the

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #40 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #39) > I would at least like to try to just try to apply them against the 3.13 > nouveau module, instead of trying to rebuild the whole kernel first? So is > that the only patch I would need? > > I'm still on 3.13 (which is also