search for: glxinfo

Dear Centos Users We are running centos on our HPC. Indeed, we have a problem with running some software using X11 server such as pymol. For your information, we are using cygwin to access to the hpc (using ssh -X -Y username at xxx.xxx.xxx.xxx) When we are testing glxinfo on my desktop, it gives us the following error: [username at hpc ~]# glxinfo name of display: localhost:10.0 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 149 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext)...

https://bugs.freedesktop.org/show_bug.cgi?id=71172 Priority: medium Bug ID: 71172 Assignee: nouveau at lists.freedesktop.org Summary: Segfault when running glxinfo. NV25GL [Quadro4 900 XGL] Severity: normal Classification: Unclassified OS: All Reporter: simon at mungewell.org Hardware: Other Status: NEW Version: unspecified Component: Drivers/DRI/nouveau...

...will get it for you ASAP. When I check the X.org log file, it says direct rendering: enabled on my graphics device (it attaches its i810 driver to the kernel's i915 DRM device). This would appear to me to suggest that atleast the X server is running with full DRM capabilities. But when I use glxinfo, it says direct rendering: No. I am just wodnering, is there anything special I need to do for GL to work with the DRM stuff? I haven't installed (atleast knowingly) any other MESA library, so following the advice I have found that should be all I need to check, but apparently something else is...

http://bugs.freedesktop.org/show_bug.cgi?id=11038 Summary: nouveau and NV17: glxinfo, glxgears and other gl-apps crash Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:...

https://bugs.freedesktop.org/show_bug.cgi?id=70212 Priority: medium Bug ID: 70212 Assignee: nouveau at lists.freedesktop.org Summary: glxinfo triggers assert in cso_release_all after 3f0627c2ad6 Severity: normal Classification: Unclassified OS: All Reporter: awatry at gmail.com Hardware: All Status: NEW Version: git Component: Drivers/DR...

https://bugs.freedesktop.org/show_bug.cgi?id=69488 Priority: medium Bug ID: 69488 Assignee: nouveau at lists.freedesktop.org Summary: GF108 (NVC1) GPU lockup QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: vekinn at gmail.com Hardware: Other

https://bugs.freedesktop.org/show_bug.cgi?id=28570 Francisco Jerez <currojerez at riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Component|Server/general

...ibGL warning: 3D driver claims to not support visual 0x4b libGL error: Can't open configuration file /home/ioannis/.drirc: No such file or directory. compiz: GLX_EXT_texture_from_pixmap is missing compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0 but running glxinfo says: $ glxinfo | grep GLX_EXT_texture_from_pixmap libGL warning: 3D driver claims to not support visual 0x4b GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap and the follwoing might be useful to know as we...

https://bugs.freedesktop.org/show_bug.cgi?id=99968 Bug ID: 99968 Summary: [NV4C] System crashes reliably with glxinfo Product: Mesa Version: 12.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org Re...

Hi! I have managed to get games like Team Fortress 2 and Mirror's Edge to finally run. But only with really bad performance. If I run glxinfo | grep direct in the terminal, I get: Code: direct rendering: No (LIBGL_ALWAYS_INDIRECT set) However, if I run sudo glxinfo | grep direct, it outputs this: Code: direct rendering: Yes I'm not sure if that is relevant, but it seems a bit odd. Here is my xorg.conf file: Code: Section "...

...months now and up until about a month ago, Warcraft III ran fine. Now it keeps giving me an error about msvcr80.dll. I have that dll in the warcraft directory. Also, I have compiz start up at logon, but even if I replace it with kwin, the same error still comes up so it's not compiz. I checked glxinfo and the correct driver is installed working. My video card is a built-in Nvidia GeForce 7050. Here's the error that comes up: err:module:attach_process_dlls "MSVCR80.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"Z:\\media\\stuff\...

...ked beautifully. Yesterday, after a reboot, FC offered to update my packages, including wine, and I agreed. Now, pretty much any wine command I run results in this: > winecfg drmUnmap back failed! ERROR! mapping regions Segmentation fault In the previous thread, Skippyboy suggested running glxinfo as a diagnostic. Unfortunately, that turns out to produce the same result: > glxinfo name of display: :0.0 drmUnmap back failed! ERROR! mapping regions Segmentation fault Any help would be appreciated. My current (post-upgrade) wine version is 0.9.35-1 Thanks, julian -------------- next...

Hi I found a way to reliably reproduce PFIFO CACHE_ERRORS, but I don't see why. How to reproduce them: 1) Run a couple of glxinfo loops - 3 is usually enough. while [ true ]; do nvgl glxinfo >/dev/null 2>/dev/null; done 2) Run glxgears. 3) If you can't see it now, resize glxgears window or add more glxinfos. Note: you need at least 2 CPUs. Usually the error looks like this (with a bit improved logging): nouveau...

...e: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 and for AIGLX this: (**) Option "AIGLX" "True" (**) AIGLX enabled (II) AIGLX: Loaded and initialized /usr/lib/dri/nouveau_dri.so which looks promising to me. glxinfo reports $ glxinfo | grep Mesa OpenGL renderer string: Mesa DRI GeForce4 Ti 4200 Go AGP 8x 20060219 x86/MMX/SSE2 OpenGL version string: 1.2 Mesa 7.1 unfortunately direct rendering doesn't get enabled $ glxinfo | grep direct direct rendering: No Of course I know nouveau is in its infancy. Just...

...tp://go-compiz.org/index.php?title=Compiling 2) try to run by launching compiz...but the only results was to not view the windows' borders.. so i searched in the forum and found a guide... that told me how to look if everything was going well..and here i found(??) a problem...the command is glxinfo | grep texture_from_pixmap and the result shoud be.. GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer, instead that is mine qwerty@homeLESS:~...

...rmation. 3) Corrupted colors! Especially black - i see a set of random sized huge gray pixels instead of solid black area. Other colors are suffering too, see http://imagebin.ca/view/ay3nrec.html. $uname -a Linux lynn 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux $glxinfo $ glxinfo name of display: :0.0 Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display &quot...

..., (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Apr 23 20:36:28 2003 (==) Using config file: "/etc/X11/XF86Config" But I get this in /var/log/messages: Apr 23 20:36:29 noname /kernel: error: [drm:radeon_unlock] *ERROR* Process 338 using kernel context 0 And glxinfo reports that I have no direct rendering (output: http://anders.fix.no/test/glxinfo.txt). :( My XF86Config: http://anders.fix.no/test/XF86Config. Excerpt from pciconf -l -v output: drm0@pci1:0:0: class=0x030000 card=0x7112174b chip=0x51591002 rev=0x00 hdr=0x00 vendor = 'ATI Technologie...

...hine under Windows XP. So I think it's wine's fault. I checked for performance issues on the www, but I found no help. I also noticed the claim that NO performance fall-off should be expected and this is encouraging. Where's the point? Direct rendering works OK for LINUX. Anyway: ?? glxinfo|grep rendering gives: ? get fences failed: -1 ? param: 6, val: 0 ? direct rendering: Yes Graphic card is Intel GMA915 Thanks for any help, Nicola -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachme...

...s: libdrm x86_64 2.4.67-1.20160218gitadd8936.el7.centos local-drivers - OK mesa-libGL-devel x86_64 11.1.2-1.20160210.el7.centos local-mesa - OK installed packaged: xorg-x11-drv-ati.x86_64 7.6.1-1.el7.centos @local-drivers OK libdrm.x86_64 2.4.67-1.20160218gitadd8936.el7.centos OK glxinfo says: OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.6.2) OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.2 OpenGL core profile shading language version string: 3.30 OpenGL version string: 3.0 Mesa 11.1.2 OpenGL shading language version string: 1.30 OpenGL...

https://bugs.freedesktop.org/show_bug.cgi?id=98629 Bug ID: 98629 Summary: OpenGL applications warns "MESA-LOADER: failed to retrieve device information" Product: Mesa Version: 13.0 Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium