On 8/15/24 3:45 AM, Masaru Nomiya wrote:

Felix would say;

Please show the results of;

$ inxi -Ga

Thanks Masaru, How about: $ inxi -Ga Graphics: Device-1: NVIDIA GF104GLM [Quadro 3000M] vendor: Hewlett-Packard driver: nvidia v: 390.157 alternate: nouveau,nvidia_drm non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last: release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx process: 40/28nm built: 2010-2016 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0e3a class-ID: 0300 Device-2: Sunplus Innovation HP HD Webcam [Fixed] driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.4:3 chip-ID: 1bcf:2805 class-ID: 0e02 Display: x11 server: X.Org v: 21.1.12 compositor: kwin driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa alternate: nouveau,nv gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 1600x900 s-dpi: 106 s-size: 383x222mm (15.08x8.74") s-diag: 443mm (17.43") Monitor-1: LVDS-0 res: 1600x900 hz: 60 dpi: 106 size: 382x215mm (15.04x8.46") diag: 438mm (17.26") modes: N/A API: OpenGL v: 4.6.0 vendor: nvidia v: 390.157 glx-v: 1.4 direct-render: yes renderer: Quadro 3000M/PCIe/SSE2 memory: 1.95 GiB API: Vulkan Message: No Vulkan data available. $ cat /etc/vulkan/icd.d/nvidia_icd.json { "file_format_version" : "1.0.0", "ICD": { "library_path": "libGLX_nvidia.so.0", "api_version" : "1.0.65" } } $ LIBGL_DEBUG=1 glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 2048 MB Currently available dedicated video memory: 1848 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro 3000M/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 390.157 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6.0 NVIDIA 390.157 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.157 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 $ nvidia-smi Thu Aug 15 01:59:44 2024 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 390.157 Driver Version: 390.157 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 Quadro 3000M Off | 00000000:01:00.0 N/A | N/A | | N/A 63C P12 N/A / N/A | 133MiB / 1984MiB | N/A Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 Not Supported | +-----------------------------------------------------------------------------+ $ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 300 frames in 5.0 seconds = 59.875 FPS 301 frames in 5.0 seconds = 60.009 FPS 301 frames in 5.0 seconds = 60.009 FPS 301 frames in 5.0 seconds = 60.010 FPS $ glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_NV_video_capture, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, <snip> I run gnome-sudoku from the command line to specify a dark theme, so I notice when it generates errors. For example, I run it with: $ GTK_THEME=Nordic-darker-standard-buttons-v40 gnome-sudoku & These errors are new. Rather strange since everything works fine, it's like vulkan lost its mind with the last updates. Any ideas? -- David C. Rankin, J.D.,P.E.

On 8/15/24 9:44 PM, Masaru Nomiya wrote:

DCR> On 8/15/24 3:45 AM, Masaru Nomiya wrote: DCR> > Felix would say; DCR> > DCR> > Please show the results of; DCR> > DCR> > $ inxi -Ga

DCR> Thanks Masaru,

DCR> How about:

DCR> $ inxi -Ga DCR> Graphics: DCR> Device-1: NVIDIA GF104GLM [Quadro 3000M] vendor: Hewlett-Packard DCR> driver: nvidia v: 390.157 alternate: nouveau,nvidia_drm non-free: DCR> series: 390.xx+ status: legacy (EOL~2022-11-22) last: release: 390.157 DCR> kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx process: 40/28nm DCR> built: 2010-2016 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: lanes: 16 [...] DCR> I run gnome-sudoku from the command line to specify a dark DCR> theme, so I notice when it generates errors. For example, I run DCR> it with:

DCR> $ GTK_THEME=Nordic-darker-standard-buttons-v40 gnome-sudoku &

DCR> These errors are new. Rather strange since everything works DCR> fine, it's like vulkan lost its mind with the last updates.

DCR> Any ideas?

Thanks.

Your nvidia Architecture is Fermi.

Then please have a look;

https://bbs.archlinux.org/viewtopic.php?id=273935

Best Regards.

Thanks Masaru! I saw that, but thought openSUSE did something to mask the errors since I had not seen any of that output before the last dup. Anyway, this is a laptop, so not much I can do about the card. Maybe I just need to remove all vulkan stuff. I'm not sure when it was installed or why. I certainly don't need it. Likely a dependency for something. Until then, it will just be: $ cat bin/gsudoku.sh #!/bin/sh theme="${1:-Nordic-darker-standard-buttons-v40}" export GTK_THEME="$theme" exec gnome-sudoku &>/dev/null & Problem solved! -- David C. Rankin, J.D.,P.E.

Hello, In the Message; Subject : Re: Tumbleweed Gnome-sudoku: error Vulkan: Loader Message: setup_loader_term_phys_devs Message-ID : <249b5407-a5a4-43ef-aa6d-5a8f1bb80851@gmail.com> Date & Time: Fri, 16 Aug 2024 00:09:20 -0500 [DCR] == "David C. Rankin" <drankinatty@gmail.com> has written: DCR> On 8/15/24 9:44 PM, Masaru Nomiya wrote: MN> > Your nvidia Architecture is Fermi. MN> > Then please have a look; MN> > https://bbs.archlinux.org/viewtopic.php?id=273935 DCR> Found the culprit - packman: DCR> gstreamer-plugin-openh264 gstreamer-plugins-bad gstreamer-plugins-bad-codecs Not libgstvulkan? I don't use the pacman repository because I struggle to maintain the integrity of the whole system. That's why I didn't know about gstreamer-plugins-bad-codecs. Well, I'm going to bed soon. ♪〜　Rock a bye David. Best Regards & Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --

On 8/15/24 3:45 AM, Masaru Nomiya wrote:

Isn't it already 1 a.m.? You'd better go to bed.

Hehe, yep, I'm getting old... I need my rest, but many times I go to sleep at 10, but wake at 1 or so and can't go back to sleep until 3 or 4... Getting old does have its challenges :)

DCR> After the latest TW dup, there is an error written to stderr DCR> from gnome-sudoku:

DCR> (gnome-sudoku:38804): Gdk-CRITICAL **: 01:19:21.227: Vulkan: Loader Message: DCR> setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current DCR> config

DCR> Anybody have a clue what Vulkan is looking for that it isn't DCR> finding -- and how do I fix it?

DCR> Is this mesa related?

Felix would say;

Please show the results of;

$ inxi -Ga

(sent with more in prior reply) Until we find a solution, a quick hack to keep the terminal clean is: $ GTK_THEME=Nordic-darker-standard-buttons-v40 gnome-sudoku 2>/dev/null & Of course this just tosses the errors in the bit-bucket, but everything else keeps working. Big issue is why isn't vulkan seeing the NVidia cores... -- David C. Rankin, J.D.,P.E.