similar to: [Bug 105935] New: DRI3 suddenly stopped turning on at some point in the past 5 months

https://bugs.freedesktop.org/show_bug.cgi?id=101372 Bug ID: 101372 Summary: nouveau?/DRI3?: dual monitors unusable without running compton --paint-on-overlay (sometimes) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

https://bugs.freedesktop.org/show_bug.cgi?id=106662 Bug ID: 106662 Summary: nouveau DPMS poblem with DRI3 (GM107) Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=99464 Bug ID: 99464 Summary: openmw - Segfault with the nouveau ddx + DRI3 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee:

https://bugs.freedesktop.org/show_bug.cgi?id=98609 Bug ID: 98609 Summary: Firefox right click corrupted with DRI3 Product: Mesa Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

That would be great, as long as it does only that and does not go into the "drivername" territory. As the said driver ;-) "A driver name to use can be provided instead of simple boolean value, which will be passed to the GL implementation for it to load the appropriate backend." -Emil On 4 July 2015 at 18:17, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > IMO

X-Server versions older than 1.16.3 have bugs in their DRI3/Present implementation which impair nouveau, so it is better to stick to good old DRI2 by default on such servers. E.g., page flipping doesn't work at all under DRI3/Present with older servers, and use of extensions like OML_sync_control, SGI_video_sync or INTEL_swap_events also causes failure of Present. nouveau's glamor accel

On 04.11.2015 12:27, poma wrote: > On 04.11.2015 11:57, Martin Peres wrote: >> On 02/11/15 08:28, poma wrote: >>> An interesting results. >>> >>> DRI2: >>> >>> $ vblank_mode=0 glxgears >>> ATTENTION: default value of option vblank_mode overridden by environment. >>> 6321 frames in 5.0 seconds = 1264.103 FPS >>> 6380

On 02/11/15 08:28, poma wrote: > An interesting results. > > DRI2: > > $ vblank_mode=0 glxgears > ATTENTION: default value of option vblank_mode overridden by environment. > 6321 frames in 5.0 seconds = 1264.103 FPS > 6380 frames in 5.0 seconds = 1275.943 FPS > 6369 frames in 5.0 seconds = 1273.629 FPS > 6377 frames in 5.0 seconds = 1275.322 FPS > 6387 frames in

The DRI option with the intel ddx can be used to indicate the following - whether dri is disabled - the dri "version" - dri1, dri2, dri3 - the dri module name - doo_dri.so bar_dri.so I'm not sure how exactly it's supposed to work/works, and I believe most of that is due to legacy reasons. I'm just saying let's not do the whole thing - just the dri "version"

On 07/07/2015 09:51 PM, Ilia Mirkin wrote: > Lastly, from some discussions with ajax on IRC, it appears that DRI3 > is half-baked at best wrt sync between server and client. I think we > should just disable it by default for now, until issues are ironed > out. (Rather than what this patch has, which is default-on for Xorg > > some version.) What are the remaining known trouble

On Sun, Dec 31, 2017 at 2:23 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Not clear what the depth % 8 was trying to protect against, but it was > breaking 30bpp visuals with DRI3. Erm, actually switching to my test config which doesn't enable dri3 is what "fixed" things. DRI3 is still busted. Ignore this patch until that's properly figured out for 30bpp. >

An interesting results. DRI2: $ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 6321 frames in 5.0 seconds = 1264.103 FPS 6380 frames in 5.0 seconds = 1275.943 FPS 6369 frames in 5.0 seconds = 1273.629 FPS 6377 frames in 5.0 seconds = 1275.322 FPS 6387 frames in 5.0 seconds = 1277.330 FPS 6407 frames in 5.0 seconds = 1281.337 FPS 6381 frames in

On 07/14/2015 05:26 PM, Ilia Mirkin wrote: > On Mon, Jul 13, 2015 at 11:43 PM, Mario Kleiner > <mario.kleiner.de at gmail.com> wrote: >> On 07/07/2015 09:51 PM, Ilia Mirkin wrote: >>> >>> Lastly, from some discussions with ajax on IRC, it appears that DRI3 >>> is half-baked at best wrt sync between server and client. I think we >>> should just

The permission check fails if udev sets the render node to 0666 but leaves the card at 0660, as is done in at least udev-236. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/nouveau_dri2.c | 22 ++++++++-------------- 1 file changed, 8 insertions(+), 14 deletions(-) diff --git a/src/nouveau_dri2.c b/src/nouveau_dri2.c index ac0ca09..a726e86 100644 --- a/src/nouveau_dri2.c +++

On 07/18/2015 01:09 PM, Dave Airlie wrote: >>>> >>>> We can disable it by default on exa - intel and amd/radeon drivers also >>>> disable by default. However, on gpus >= maxwell only glamor accel is >>>> supported and glamor on nouveau is either dri3/present or no hw accel at >>>> all >>>> afaics. >>> >>>

I'm aware of this issue, and am experiencing it myself. The issue is that drmmode_event_handler takes up more and more CPU time. It seems like some events are being "left behind". I haven't had time to debug it further yet though. I also have DRI3 enabled, but only very rarely do I make use of my secondary GPUs, and I'm pretty sure I've seen the problem happen without

Hi, On 30-07-15 16:09, Ilia Mirkin wrote: > FWIW this is a fail on nv50+ as well. See for example > https://bugs.freedesktop.org/show_bug.cgi?id=91445 > > My suspicion is that this is due to the lack of PUSH_KICK in the *Done > exa handlers -- works fine with DRI2, but DRI3 has no synchronization > and so the commands never get flushed out. Easily verified by sticking >

On 04.11.2015 11:57, Martin Peres wrote: > On 02/11/15 08:28, poma wrote: >> An interesting results. >> >> DRI2: >> >> $ vblank_mode=0 glxgears >> ATTENTION: default value of option vblank_mode overridden by environment. >> 6321 frames in 5.0 seconds = 1264.103 FPS >> 6380 frames in 5.0 seconds = 1275.943 FPS >> 6369 frames in 5.0 seconds =

Not clear what the depth % 8 was trying to protect against, but it was breaking 30bpp visuals with DRI3. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/nouveau_dri2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/nouveau_dri2.c b/src/nouveau_dri2.c index cbb7b2a..07b6022 100644 --- a/src/nouveau_dri2.c +++ b/src/nouveau_dri2.c @@ -1076,7 +1076,7 @@

did the test result changed in any way? Maybe the DRI2 run was vsynced and the DRI3 not? Nouveau has a pretty high cpu usage in general, because it usually busy waits on fences (I think? not sure where it was exactly that nouveau is busy waiting) > poma <pomidorabelisima at gmail.com> hat am 7. April 2016 um 13:56 geschrieben: > > > > $ glmark2 >