similar to: [Bug 93670] Reverse PRIME using two external screens on Nvidia card leads to "Configure crtc 5 failed" since xorg-server 1.18.0

https://bugs.freedesktop.org/show_bug.cgi?id=93670 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Ilia Mirkin <imirkin at

A port of commit ff9a6b6f from xf86-video-ati. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93670 Reported-by: Thomas D. <thfrdue at gmx.de> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/drmmode_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 1dc48c5..b950f42 100644 ---

Hi Ilia, Ben, et al. Can I please get a review of this patch, and assuming the review is favorable, can someone please push this ? Regards, Hans p.s. Is it ok if I request push rights to the nouveau repos / group at freedesktop.org ? On 03-06-16 14:46, Hans De Goede wrote: > drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call > to drmmode_xf86crtc_resize(), but on a

drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call to drmmode_xf86crtc_resize(), but on a subsequent drmmode_set_scanout_pixmap(NULL) it would not remove the fb. This keeps the crtc marked as busy, which causes the dgpu to not being able to runtime suspend, after an output attached to the dgpu has been used once. Which causes burning through an additional 10W of power and the

https://bugs.freedesktop.org/show_bug.cgi?id=103202 Bug ID: 103202 Summary: Tearing with reverse prime (intel primary, nouveau secondary) Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

A few polish fixes here over RC2.  I'll start the 1.18 stable branch and update master for 1.19pre in a moment.  Thanks to everyone who helped make 1.18 our best release yet! Adam Jackson (3):       build: Remove stale miext/cw include paths       vidmode: Drop the unused event code       xserver 1.18.0 Alan Coopersmith (3):       Xorg.man: move XLOCAL details to X(7) man page instead

(same message as before, except this one I remembered to gpg-sign) A few polish fixes here over RC2.  I'll start the 1.18 stable branch and update master for 1.19pre in a moment.  Thanks to everyone who helped make 1.18 our best release yet! Adam Jackson (3):       build: Remove stale miext/cw include paths       vidmode: Drop the unused event code       xserver 1.18.0 Alan Coopersmith (3):

https://bugs.freedesktop.org/show_bug.cgi?id=99501 Bug ID: 99501 Summary: xrandr rotation does not work with reverse prime Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=69876 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Revers prime sometime |[NVC3] Reverse prime |freezes the machine |sometimes freezes the |

https://bugs.freedesktop.org/show_bug.cgi?id=103896 Bug ID: 103896 Summary: [optimus, reverse PRIME] no HDMI audio Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #3 from Mike <michele.cane at gmail.com> --- With 3.10 is working fine. Have not tried with 3.11. I recompiled 3.12-rc1 without vgaswitcheroo and the problem persists. -- 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=69876 --- Comment #4 from Kevin N. <vekinn at gmail.com> --- I experience the same thing with my Thinkpad t530 and NVS 5400m in Optimus mode with 3.12-rc2 on Fedora 19. Locks up if I use xrandr or try to do anything with the displayport unless I have it plugged in at boot. Works fine if I change in bios to discrete nvidia. -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #5 from Emil Velikov <emil.l.velikov at gmail.com> --- There has been quite a few changes in the window you've mentioned. Thus to narrow it down further you can try - boot with "nouveau.config=MSI=0" to disable MSI interrupts(introduced in 3.12) If that does not help git bisect might be in order :) -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #6 from Emil Velikov <emil.l.velikov at gmail.com> --- Had a typo previously, the correct argument is nouveau.config=NvMSI=0 -- 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=69876 --- Comment #7 from Mike <michele.cane at gmail.com> --- Created attachment 87285 --> https://bugs.freedesktop.org/attachment.cgi?id=87285&action=edit dmesg output from nouveau.debug=trace -- 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=69876 --- Comment #8 from Mike <michele.cane at gmail.com> --- (In reply to comment #6) > Had a typo previously, the correct argument is > nouveau.config=NvMSI=0 The behaviour remain the same with nouveau.config=NvMSI=0 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #9 from Mike <michele.cane at gmail.com> --- When nouveau.runpm=0 no freeze occurs. -- 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=69876 --- Comment #10 from Mike <michele.cane at gmail.com> --- If after xrandr --setprovideroffloadsink nouveau Intel i turn on the card with, for example, DRI_PRIME glxgers and then I xrandr --setprovideroutputsource nouveau Intel there is no freeze -- You are receiving this mail because: You are the assignee for the bug. --------------

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #11 from Ilia Mirkin <imirkin at alum.mit.edu> --- Is this still an issue with 3.13.x or later? Some runpm issues were fixed there. -- 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=69876 --- Comment #12 from Mike <michele.cane at gmail.com> --- I dropped Gnome and I now use Compton as compositor and the problem is no more present. I do not know if is due to newer kernel 3.16 or is a compositor related issue. Cheers Michele Cane, PhD. Sent from my Android device. On Aug 21, 2014 11:25 PM, <bugzilla-daemon at