Displaying 20 results from an estimated 200 matches similar to: "[Bug 75761] weston-launch no output - black screen"
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #14 from Lubosz Sarnecki <lubosz at gmail.com> ---
I am only bisecting the nouveau directory, like so:
git bisect start v3.14 v3.10 -- drivers/gpu/drm/nouveau
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #16 from Lubosz Sarnecki <lubosz at gmail.com> ---
Chipset: GF110 (NVC8)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140410/3e3ea7e7/attachment.html>
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
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
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
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
2014 May 28
0
[Bug 75761] weston-launch no output - black screen
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
2012 Sep 24
8
[Bug 55294] New: Running EGL demos on DRM from mesa-demos causes a corrupted output on NV50
https://bugs.freedesktop.org/show_bug.cgi?id=55294
Priority: medium
Bug ID: 55294
Assignee: nouveau at lists.freedesktop.org
Summary: Running EGL demos on DRM from mesa-demos causes a
corrupted output on NV50
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS:
2012 Sep 28
5
[Bug 55412] New: Screen turns black during boot after driver tries to set mode on NV50
https://bugs.freedesktop.org/show_bug.cgi?id=55412
Priority: medium
Bug ID: 55412
Assignee: nouveau at lists.freedesktop.org
Summary: Screen turns black during boot after driver tries to
set mode on NV50
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux
2014 Mar 04
18
[Bug 75776] New: Hearthstone displays corrupted buffers on NVA5
https://bugs.freedesktop.org/show_bug.cgi?id=75776
Priority: medium
Bug ID: 75776
Assignee: nouveau at lists.freedesktop.org
Summary: Hearthstone displays corrupted buffers on NVA5
Severity: normal
Classification: Unclassified
OS: All
Reporter: lubosz at gmail.com
Hardware: Other
Status: NEW
2014 Apr 09
0
[Bug 75761] weston-launch no output - black screen
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|
2014 Apr 09
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
Pekka Paalanen <ppaalanen at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NOTOURBUG |---
--- Comment #11 from Pekka Paalanen
2014 Apr 09
0
[Bug 75761] weston-launch no output - black screen
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
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #15 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #13)
> My bisection process so far is pretty frustrating,
> since the majority of the commits between 3.12 and 3.13 do not boot.
> I get corrupted output before being able to login.
What HW are you using?
--
You are receiving this mail
2014 Apr 10
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #17 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #16)
> Chipset: GF110 (NVC8)
There are known issues with NVC8 that go away with blob pgraph fw, perhaps
worth trying with that. (See bug #54437.)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part
2014 Apr 17
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
soundx94 at hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #20 from soundx94 at hotmail.com ---
Thanks for
2014 Apr 17
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #21 from Pekka Paalanen <ppaalanen at gmail.com> ---
(In reply to comment #20)
> Thanks for bisecting the kernel. Reverting that patch on the latest kernel
> also fixes the issue for me.
> (Using NVE6: GTX 660)
Hey, wait! Why did you close this bug?
Has upstream merged a fix, or did this problem never occur on
2014 Apr 17
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
--- Comment #22 from soundx94 at hotmail.com ---
I thought WORKSFORME is the proper status because it works for me at the moment
with this modification and it can get merged into upstream. Sorry if i
misunderstood the status label, do you want me to reopen it ?
--
You are receiving this mail because:
You are the assignee for the bug.
2014 Apr 17
0
[Bug 75761] weston-launch no output - black screen
https://bugs.freedesktop.org/show_bug.cgi?id=75761
Pekka Paalanen <ppaalanen at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |---
--- Comment #23 from Pekka Paalanen
2014 May 28
0
[Bug 75761] weston-launch no output - black screen
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,
2014 May 30
0
[Bug 75761] weston-launch no output - black screen
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
2014 May 31
0
[Bug 75761] weston-launch no output - black screen
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