similar to: NOUVEAU(0): DRI3 on EXA enabled

Displaying 20 results from an estimated 400 matches similar to: "NOUVEAU(0): DRI3 on EXA enabled"

2015 Nov 04
3
NOUVEAU(0): DRI3 on EXA enabled
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 =
2015 Nov 05
0
NOUVEAU(0): DRI3 on EXA enabled
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
2015 Nov 04
0
NOUVEAU(0): DRI3 on EXA enabled
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
2016 Apr 07
2
glmark2: high CPU usage - DRI3 & modeset
$ glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: nouveau GL_RENDERER: Gallium 0.4 on NV98 GL_VERSION: 3.0 Mesa 11.2.0 ======================================================= /etc/X11/xorg.conf.d/nouveau.conf Section "Device" Identifier
2006 Nov 17
1
the notorious "GLX_EXT_texture_from_pixmap is missing" error
I'm not reporting a bug (I know it's not the right place to do that anyway), but a little help would be appreciated. Once again I run into the famous "compiz: GLX_EXT_texture_from_pixmap is missing" error. The problem is I can't figure out what's wrong. I use fedora core 6 on an athlon XP with an ati RV250 and the radeon open-source drivers running compiz reports: $
2016 May 19
0
ati fglrx vs amdgpu absolutely mad on R5 m255 vs IRIS P520
Hello guys, native drivers are mad for my laptop: Downgrade to native centos kernel vmlinuz-3.10.0-327.18.2.el7.x86_64. fglrx glxgears around ~800 in 5 seconds my test with amdgpu kernel 4.6 (intel vs amdgpu): [andy at localhost ~]$ cat /proc/version Linux version 4.6.0-1.el7.centos.x86_64 (andy at localhost.localdomain) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Thu May 19
2015 Aug 14
15
[Bug 91632] New: Crash in nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=91632 Bug ID: 91632 Summary: Crash in nouveau Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org
2018 Apr 06
9
[Bug 105935] New: DRI3 suddenly stopped turning on at some point in the past 5 months
https://bugs.freedesktop.org/show_bug.cgi?id=105935 Bug ID: 105935 Summary: DRI3 suddenly stopped turning on at some point in the past 5 months Product: Mesa Version: 17.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium
2015 Jun 30
3
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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
2015 Jul 04
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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
2017 Dec 31
2
[PATCH] dri3: remove bogus condition for creating pixmap
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 @@
2015 Jul 04
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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"
2008 Jan 08
0
[fdo] Intel G35 / X3500 video tearing
I've recently set up a system built on an ASUS P5E-VM HDMI motherboard running Ubuntu 7.10 and I'm experiencing some very noticeable tearing during video playback with mplayer. I have read some discussion about video tearing with other Intel chipsets in the mailing list a while back but hadn't heard much about it lately. I've experimented with both xv and gl video output as well
2015 Jul 30
2
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
Hi Maarten, xf86-video-nouveau causes a garbled display when running gnome-shell on nv4x (tested with nv43 and nv46) since this commit: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99 I've seen some discussion about issues caused by enabling dri, but AFAIK no solution let. I have time to help with debugging / fixing this, but I
2015 Jul 14
3
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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
2015 Aug 03
3
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
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 >
2015 Jul 14
4
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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
2015 Jul 19
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
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. >>> >>>
2015 Aug 03
2
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
Hi, On 03-08-15 17:36, Ilia Mirkin wrote: > On Mon, Aug 3, 2015 at 9:02 AM, Hans de Goede <hdegoede at redhat.com> wrote: >> 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
2020 Aug 13
2
Accumulating CPU load from Xorg process with DRI3
I observed this bug for quite some time, but so far I workarounded it with just setting DRI2 (default) in xorg.conf.d/20-nouveau.conf Now with two GPU i iwsh to use DRI3, so right now it set up like this: cat /etc/X11/xorg.conf.d/20-nouveau.conf Section "Device" Identifier "Card0" Driver "nouveau" Option "PageFlip" "1" #Option