[opensuse-factory] Why not installed w/caps and GL-enhanced-kernel config?
sudo wireshark QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 nl80211 not found.
sudo setcap cap_net_raw+ep /usr/bin/wireshark wireshark& [1] 31423 Ishtar:law/bin> nl80211 not found.
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast ...hmmmm.... 💡 (Ah!) (rpm -qf wireshark + -qi :) Name : wireshark-ui-qt Version : 2.6.2 Release : 2.1 Distribution: openSUSE Tumbleweed libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast So why isn't wireshark installed with cap_net_raw? At least it gets rid of 1 error message. This one: libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast seems pervasive -- even doing a "make xconfig" for kernel configuration. I keep wondering what the GL-enhanced kernel-config does? Anyone know or why libGL would be needed for an X-GUI ("make xconfig") of the kernel? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, comments and suggestions inline On 31.10.18 23:00, L A Walsh wrote:
sudo wireshark QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...hmmmm.... 💡 (Ah!)
(rpm -qf wireshark + -qi :) Name : wireshark-ui-qt Version : 2.6.2 Release : 2.1 Distribution: openSUSE Tumbleweed
sudo setcap cap_net_raw+ep /usr/bin/wireshark wireshark& [1] 31423 Ishtar:law/bin> nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
So why isn't wireshark installed with cap_net_raw? At least it gets rid of 1 error message. This one:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
Your XServer drivers and or Opengl/mesa seems to be broken (or not installed?!)
seems pervasive -- even doing a "make xconfig" for kernel configuration. I keep wondering what the GL-enhanced kernel-config does? Anyone know or why libGL would be needed for an X-GUI ("make xconfig") of the kernel?
I can't find a thread to this eMail at the ML archive, so it seems to be the first one,: Where is the connection you make between running wireshark (with the Qt frontend) to do with a kernel config? Anyway, wireshark-qt uses Opengl rendering if available (as i suspect xconfig is as well, it brings up make qconfig for me, so that one uses Qt as well). If you want to get rid of it, install the corresponding OpenGL driver for your hardware, or swrast if you run in a VM. Greetings, Tobias
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/31/2018 3:35 PM, Tobias Klausmann wrote:
Hi,
comments and suggestions inline
On 31.10.18 23:00, L A Walsh wrote:
sudo wireshark QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...hmmmm.... 💡 (Ah!)
(rpm -qf wireshark + -qi :) Name : wireshark-ui-qt Version : 2.6.2 Release : 2.1 Distribution: openSUSE Tumbleweed
sudo setcap cap_net_raw+ep /usr/bin/wireshark wireshark& [1] 31423 Ishtar:law/bin> nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
So why isn't wireshark installed with cap_net_raw? At least it gets rid of 1 error message. This one:
libGL error: No matching fbConfigs or visuals found
Your XServer drivers and or Opengl/mesa seems to be broken (or not installed?!)
I looked for swrast & found: /usr/lib64/dri/kms_swrast_dri.so /usr/lib64/dri/swrast_dri.so /usr/lib64/dri/updates/swrast_dri.so The first two come from the Mesa rpm. I didn't have the latest, but did have them installed. Now I think I have close to the latest (in TW): Mesa-18.1.6-205.1 Mesa-dri-18.1.6-205.1 Mesa-gallium-18.1.6-205.1 Mesa-libEGL1-18.1.6-205.1 Mesa-libGL1-18.1.6-205.1 Mesa-libGLESv1_CM1-18.1.6-205.1 Mesa-libGLESv2-2-18.1.6-205.1 Mesa-libglapi0-18.1.6-205.1 Mesa-devel-18.1.6-205.1 Mesa-dri-devel-18.1.6-205.1 Mesa-libEGL-devel-18.1.6-205.1 Mesa-libGL-devel-18.1.6-205.1 Mesa-libGLESv1_CM-devel-18.1.6-20 Mesa-libGLESv2-devel-18.1.6-205.1 Mesa-libglapi-devel-18.1.6-205.1 libLLVM6-6.0.1-1.1 libOSMesa8-18.1.6-205.1 libdrm2-2.4.93-1.1 libdrm_amdgpu1-2.4.93-1.1 libdrm_intel1-2.4.93-1.1 libdrm_nouveau2-2.4.93-1.1 libdrm_radeon1-2.4.93-1.1 libglvnd-1.0.0-1.2 libOSMesa-devel-18.1.6-205.1 libdrm-devel-2.4.93-1.1 libglvnd-devel-1.0.0-1.2 ---
seems pervasive -- even doing a "make xconfig" for kernel configuration. I keep wondering what the GL-enhanced kernel-config does? Anyone know or why libGL would be needed for an X-GUI ("make xconfig") of the kernel?
I can't find a thread to this eMail at the ML archive, so it seems to be the first one.
--- Search on swrast. For that matter, you can search on "libGL error: failed to load driver: swrast" in google and see tons of references. Reproducible in FreeBSD, Apple, Ubuntu. Someone posted about the problem related to Redhat, and got a answer telling him "you have a broken openGL install or broken driver." (seems to be a common reply on this problem, but so far, hasn't been the case). That user was lucky for their app as they could use and alternate output format that gave them their graph, however for openGL: "Apparently there are issues with the OpenGL/Mesa implementation." --- *sigh* - not too informative but a widely seen problem.
: Where is the connection you make between running wireshark (with the Qt frontend) to do with a kernel config?
I think you just made it (next paragraph). :-)
Anyway, wireshark-qt uses Opengl rendering if available (as i suspect xconfig is as well, it brings up make qconfig for me, so that one uses Qt as well).
If you want to get rid of it, install the corresponding OpenGL driver for your hardware, or swrast if you run in a VM.
AFAIK, they are installed on both server and client. On server (cygwin) they are in package dri-drivers:
locate swrast /lib/dri/swrast_dri.so /usr/src/debug/xorg-server-1.20.1-1/glx/glxdriswrast.c cygcheck -f /lib/dri/swrast_dri.so dri-drivers-18.0.5-1
I'm not sure why it searches on swrast at all, since openGL seems to be somewhat supported glewinfo shows 3188 extensions. 2723 extensions are supported while 744 extensions are not glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported). GLXspheres displays in 2560x1600 @ 73.2 frames/sec = 295.2 Mpixels/sec. Says that it was using indirect context. GLXgears never seems to synchronize and only shows the initial plot with a claim of 5015.046 FPS (think it is talking to itself). For whatever reason the swrast issue is common and not very helpful, however for programs that ignore the error and use feature-probing, it seems moderate functionality can be gained, but most see the the error and just stop trying w/GL. TBH, I was more amused about getting the swrast error when running an x-based (using qt) 'xconfig' as I was wondering how openGL would be used in a kernel-config tool. But then you had to go and be serious...so thought I'd take the time to recheck my crossing of 't''s and dotting of 'i''s and see if in doing so I could fix some other problem or someone else would see something. Thanks! -linda -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/11/2018 14:04, L A Walsh wrote:
On 10/31/2018 3:35 PM, Tobias Klausmann wrote:
Hi,
comments and suggestions inline
On 31.10.18 23:00, L A Walsh wrote:
sudo wireshark QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 QStandardPaths: wrong ownership on runtime directory /var/run/user/5013, 5013 instead of 0 nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...hmmmm.... 💡 (Ah!)
(rpm -qf wireshark + -qi :) Name : wireshark-ui-qt Version : 2.6.2 Release : 2.1 Distribution: openSUSE Tumbleweed
sudo setcap cap_net_raw+ep /usr/bin/wireshark wireshark& [1] 31423 Ishtar:law/bin> nl80211 not found. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
So why isn't wireshark installed with cap_net_raw? At least it gets rid of 1 error message. This one:
libGL error: No matching fbConfigs or visuals found
Your XServer drivers and or Opengl/mesa seems to be broken (or not installed?!)
I looked for swrast & found: /usr/lib64/dri/kms_swrast_dri.so /usr/lib64/dri/swrast_dri.so /usr/lib64/dri/updates/swrast_dri.so
The first two come from the Mesa rpm.
I didn't have the latest, but did have them installed. Now I think I have close to the latest (in TW):
Mesa-18.1.6-205.1 Mesa-dri-18.1.6-205.1 Mesa-gallium-18.1.6-205.1 Mesa-libEGL1-18.1.6-205.1 Mesa-libGL1-18.1.6-205.1 Mesa-libGLESv1_CM1-18.1.6-205.1 Mesa-libGLESv2-2-18.1.6-205.1 Mesa-libglapi0-18.1.6-205.1
Mesa-devel-18.1.6-205.1 Mesa-dri-devel-18.1.6-205.1 Mesa-libEGL-devel-18.1.6-205.1 Mesa-libGL-devel-18.1.6-205.1 Mesa-libGLESv1_CM-devel-18.1.6-20 Mesa-libGLESv2-devel-18.1.6-205.1 Mesa-libglapi-devel-18.1.6-205.1
libLLVM6-6.0.1-1.1 libOSMesa8-18.1.6-205.1 libdrm2-2.4.93-1.1 libdrm_amdgpu1-2.4.93-1.1 libdrm_intel1-2.4.93-1.1 libdrm_nouveau2-2.4.93-1.1 libdrm_radeon1-2.4.93-1.1 libglvnd-1.0.0-1.2
libOSMesa-devel-18.1.6-205.1 libdrm-devel-2.4.93-1.1 libglvnd-devel-1.0.0-1.2
---
seems pervasive -- even doing a "make xconfig" for kernel configuration. I keep wondering what the GL-enhanced kernel-config does? Anyone know or why libGL would be needed for an X-GUI ("make xconfig") of the kernel?
I can't find a thread to this eMail at the ML archive, so it seems to be the first one.
--- Search on swrast. For that matter, you can search on "libGL error: failed to load driver: swrast" in google and see tons of references. Reproducible in FreeBSD, Apple, Ubuntu. Someone posted about the problem related to Redhat, and got a answer telling him
"you have a broken openGL install or broken driver." (seems to be a common reply on this problem, but so far, hasn't been the case).
That user was lucky for their app as they could use and alternate output format that gave them their graph, however for openGL: "Apparently there are issues with the OpenGL/Mesa implementation." --- *sigh* - not too informative but a widely seen problem.
: Where is the connection you make between running wireshark (with the Qt frontend) to do with a kernel config?
I think you just made it (next paragraph). :-)
Anyway, wireshark-qt uses Opengl rendering if available (as i suspect xconfig is as well, it brings up make qconfig for me, so that one uses Qt as well).
If you want to get rid of it, install the corresponding OpenGL driver for your hardware, or swrast if you run in a VM.
AFAIK, they are installed on both server and client. On server (cygwin) they are in package dri-drivers:
locate swrast /lib/dri/swrast_dri.so /usr/src/debug/xorg-server-1.20.1-1/glx/glxdriswrast.c cygcheck -f /lib/dri/swrast_dri.so dri-drivers-18.0.5-1
I'm not sure why it searches on swrast at all, since openGL seems to be somewhat supported glewinfo shows 3188 extensions. 2723 extensions are supported while 744 extensions are not
glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported).
GLXspheres displays in 2560x1600 @ 73.2 frames/sec = 295.2 Mpixels/sec. Says that it was using indirect context.
GLXgears never seems to synchronize and only shows the initial plot with a claim of 5015.046 FPS (think it is talking to itself).
For whatever reason the swrast issue is common and not very helpful, however for programs that ignore the error and use feature-probing, it seems moderate functionality can be gained, but most see the the error and just stop trying w/GL.
TBH, I was more amused about getting the swrast error when running an x-based (using qt) 'xconfig' as I was wondering how openGL would be used in a kernel-config tool.
From memory, ever since Qt5 was released it has defaulted to using opengl to render all its UI's even basic ones that you wouldn't traditionally associate with opengl usage. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Il giorno Thu, 1 Nov 2018 14:18:54 +1030 Simon Lees <sflees@suse.de> ha scritto:
From memory, ever since Qt5 was released it has defaulted to using opengl to render all its UI's even basic ones that you wouldn't traditionally associate with opengl usage.
This IIRC only involves QML (and now has a fallback introduced in recent versions). Traditional QWidgets don't use this path. -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
On čtvrtek 1. listopadu 2018 4:34:16 CET L A Walsh wrote:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...
glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported).
It seems that you have the NVIDIA proprietary driver installed, but some applications are trying to use the libGL from Mesa. That does not see any supported devices, so it tries to use software rendering and that fails because it would have no way to present the results to the X server. Not sure why, maybe because of mismatched GLX extension... So it looks like broken driver installation. The Mesa and NVIDIA OpenGL implementation can live next to each other nowadays and the GLVND library is used to choose the right one. Apparently it does not work correctly in your case. The driver version is 416.34, which does not look like any version from the official NVIDIA openSUSE repositories. Did you install the driver using a *.run installation file from their web page? If yes, maybe it was not properly configured during the installation, or maybe it got messed up after some updates. I would recommend you to remove all parts of the NVIDIA driver and install one from the repository: https://en.opensuse.org/SDB:NVIDIA_drivers Michal Srb -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/1/2018 1:27 AM, Michal Srb wrote:
On čtvrtek 1. listopadu 2018 4:34:16 CET L A Walsh wrote:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...
glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported).
It seems that you have the NVIDIA proprietary driver installed,
On the Windows 'server'.
but some applications are trying to use the libGL from Mesa.
I'm not real clear about this, but those apps seem to be running on clients.
That does not see any supported devices, so it tries to use software rendering and that fails because it would have no way to present the results to the X server. Not sure why, maybe because of mismatched GLX extension...
?? how would it normally display results to the server? I mean isn't that the purpose of the swrast_dri -- to allow rendering in SW when there isn't a local 3D card? The 'client' where the programs run use remote windows located on the Xserver machine (the Win machine with the nvidia card). I don't have an nvidia card on my server,
So it looks like broken driver installation. So it looks like broken driver installation. The Mesa and NVIDIA OpenGL implementation can live next to each other nowadays and the GLVND library is used to choose the right one. Apparently it does not work correctly in your case.
I would recommend you to remove all parts of the NVIDIA driver and install one from the repository: https://en.opensuse.org/SDB:NVIDIA_drivers
---- I'm pretty sure it wouldn't work on the machine where the video card is located (win 7sp1). But you may be on to something....maybe the GLVND lib is not configured properly on install for the remote case? I'd think it would need to dynamically do config for remote vs. local, since someone could be running in either place if both machines had Nvidia cards. I think I've seen places where people had the nivida card installed on windows and were running linux in a VM and were trying to have something running in the VM, display on the host (a win machine) -- similar to my use case, but my 'remote' is really over remote bus, vs. a local one. How is GLVND configured to use remote / indirect rendering vs. local? It might also be confused by there being no local DRI-based graphics card (?). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On čtvrtek 1. listopadu 2018 16:40:26 CET L A Walsh wrote:
On 11/1/2018 1:27 AM, Michal Srb wrote:
On čtvrtek 1. listopadu 2018 4:34:16 CET L A Walsh wrote:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
...
glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported).
It seems that you have the NVIDIA proprietary driver installed,
--- On the Windows 'server'.
Oh, ok, I had no idea remote X or Windows was involved. I don't think I can give useful advice without knowing the setup. What kind of X server is running on the Windows machine? Which extension does it offer, what visuals? Outputs of `xdpyinfo` and `glxinfo` would help.
That does not see any supported devices, so it tries to use software rendering and that fails because it would have no way to present the results to the X server. Not sure why, maybe because of mismatched GLX extension...
---- ?? how would it normally display results to the server? I mean isn't that the purpose of the swrast_dri -- to allow rendering in SW when there isn't a local 3D card? The 'client' where the programs run use remote windows located on the Xserver machine (the Win machine with the nvidia card).
Sure, the rendering happens in software on the client side, but the final image still has to be sent over to the X server, which has to understand the format.
But you may be on to something....maybe the GLVND lib is not configured properly on install for the remote case? I'd think it would need to dynamically do config for remote vs. local, since someone could be running in either place if both machines had Nvidia cards.
I doubt that. If you don't have nvidia driver on your linux machine, GLVND is not the issue. We know that it is selecting the Mesa OpenGL implementation and that is correct. Michal Srb -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/1/2018 9:00 AM, Michal Srb wrote:
On čtvrtek 1. listopadu 2018 16:40:26 CET L A Walsh wrote:
On 11/1/2018 1:27 AM, Michal Srb wrote:
On čtvrtek 1. listopadu 2018 4:34:16 CET L A Walsh wrote:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast ...
glxinfo shows support up to openGL version 1.4 (4.6.0 NVIDIA 416.34) (and alot of lines for routines supported). It seems that you have the NVIDIA proprietary driver installed,
On the Windows 'server'.
Oh, ok, I had no idea remote X or Windows was involved. I don't think I can give useful advice without knowing the setup. What kind of X server is running on the Windows machine? Which extension does it offer, what visuals? Outputs of `xdpyinfo` and `glxinfo` would help.
Sure, the rendering happens in software on the client side, but the final image still has to be sent over to the X server, which has to understand the format.
It doesn't seem to be doing that, but does seem capable of running GLX over the wire in an indirect context. xdyinfo: name of display: athenae:0 version number: 11.0 vendor string: The Cygwin/X Project vendor release number: 12001000 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, LSBFirst, 32 image byte order: LSBFirst number of supported pixmap formats: 7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range: minimum 8, maximum 255 focus: PointerRoot number of extensions: 23 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM Present RANDR RECORD RENDER SHAPE SYNC Windows-DRI X-Resource XC-MISC XFIXES XFree86-Bigfont XINERAMA XInputExtension XKEYBOARD XTEST default screen number: 0 number of screens: 1 screen #0: dimensions: 2560x1600 pixels (542x339 millimeters) resolution: 120x120 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 root window id: 0x36f depth of root window: 24 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x20 default number of colormap cells: 256 preallocated pixels: black 0, white 16777215 options: backing-store WHEN MAPPED, save-unders NO largest cursor: 32x32 current input event mask: 0x4a0004 ButtonPressMask StructureNotifyMask SubstructureNotifyMask PropertyChangeMask number of visuals: 177 default visual id: 0x21 visual: visual id: 0x21 class: TrueColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff0000, 0xff00, 0xff significant bits in color specification: 8 bits .... and GLXinfo: n> LIBGL_DEBUG=verbose glxinfo|&more libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast name of display: athenae:0 display: athenae:0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2 OpenGL version string: 1.4 (4.6.0 NVIDIA 416.34) OpenGL extensions: GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_filter_anisotropic, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_program, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_mirror_once, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_s3tc, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_NV_blend_square, GL_NV_depth_clamp, GL_NV_fog_distance, GL_NV_fragment_program2, GL_NV_fragment_program_option, GL_NV_light_max_exponent, GL_NV_multisample_filter_hint, GL_NV_point_sprite, GL_NV_texgen_reflection, GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_NV_vertex_program2_option, GL_NV_vertex_program3, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_multi_draw_arrays, GL_SUN_slice_accum 176 GLX Visuals... glewinfo shows 3188 extensions. 2723 extensions are supported while 744 extensions are not GLXspheres @ 2560x1600 displays 73.2 frames/sec = 295.2 Mpixels/sec, using "indirect context". What indirect context would it be using to get that speed, or is that a normal speed for a non-accelerated X? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
L A Walsh
-
Luca Beltrame
-
Michal Srb
-
Simon Lees
-
Tobias Klausmann