Upgrading nvidia-drm-kmod-550.120 puts glmark2 to 30-50% perfo

J

jb82

After today's pkg upgrade on 14.1-RELEASE of the nvidia-drm-kmod package, precisely to this version:

Code: 
nvidia-drm-kmod-550.120        NVIDIA DRM Kernel Module

routine glmark2 shows something like 2-3x drop in FPS. Anybody else seeing this performance drop?
 
i have just upgraded to 550.120

my build of dwl ( wayland version of dwm ) isnt starting now
so ill have to try and see what the issue is

dont know if its related to the nvidia update or something else

only just updated so havent noticed any other issues yet
 
NapoleonWils0n said:
i have just upgraded to 550.120

my build of dwl ( wayland version of dwm ) isnt starting now
so ill have to try and see what the issue is

dont know if its related to the nvidia update or something else

only just updated so havent noticed any other issues yet
Click to expand...
On a funny note, I've been trying Wayland on my Quadro T2000 for 15 minutes after quite some time and I'm typing this from dwl. But glmark2 numbers are suspicious at least.
 
Never encounterd (not with glmark2, but glxgears included in graphics/mesa-demos on xorg) such a drop. Quadro P1000 (Pascal generation) GPU.
550.120, 550.54.14, 555.58.02, 560.28.03, 560.31.02 and 560.35.03 showed almost equivalent results. Older versions, too.

Are you sure you have /dev/dri/* appear? If not, fallback to installed generic framebuffer could happen.

Or does Sync to VBlank enabled on Nvidia Settings (x11/nvidia-settings)?
 
im not using the dwl package

i was using the dwl 0.6 release with wlroots 0.17
wlroots has been updated to 0.18

so i need to download dwl 0.7 which works with wlroots 0.18

codeberg.org

dwl

dwm for Wayland
codeberg.org codeberg.org

so a wlroots issue and not related to nvidia
 
T-Aoki said:
Are you sure you have /dev/dri/* appear? If not, fallback to installed generic framebuffer could happen.
Click to expand...
Yes, driver per se works just fine so far.
Exactly the same setup, tested in a different bootenv, the only difference was the nvidia-drm-kmod chain/package version.
Xorg, dwm, no standalone compositor, vsync enabled.
And because we all do love numbers:

NVIDIA 550.54.14
Code: 
=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      NVIDIA Corporation
    GL_RENDERER:    Quadro T2000/PCIe/SSE2
    GL_VERSION:     4.6.0 NVIDIA 550.54.14
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 10718 FrameTime: 0.093 ms
[build] use-vbo=true: FPS: 16718 FrameTime: 0.060 ms
[texture] texture-filter=nearest: FPS: 14716 FrameTime: 0.068 ms
[texture] texture-filter=linear: FPS: 14683 FrameTime: 0.068 ms
[texture] texture-filter=mipmap: FPS: 14867 FrameTime: 0.067 ms

NVIDIA 550.120
Code: 
=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      NVIDIA Corporation
    GL_RENDERER:    Quadro T2000/PCIe/SSE2
    GL_VERSION:     4.6.0 NVIDIA 550.120
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 5680 FrameTime: 0.176 ms
[build] use-vbo=true: FPS: 6131 FrameTime: 0.163 ms
[texture] texture-filter=nearest: FPS: 6003 FrameTime: 0.167 ms
[texture] texture-filter=linear: FPS: 5974 FrameTime: 0.167 ms
[texture] texture-filter=mipmap: FPS: 6024 FrameTime: 0.166 ms
 
No idea why but "Allow flipping" has with 550.120 huge impact (negative) on performance which was not the case for the previous driver.
 
NapoleonWils0n said:
i have just upgraded to 550.120

my build of dwl ( wayland version of dwm ) isnt starting now
so ill have to try and see what the issue is

dont know if its related to the nvidia update or something else

only just updated so havent noticed any other issues yet
Click to expand...
I can confirm that dwl/seatd work smoothly for the first time on my old P1's Quadro T2000. I disabled Allow flipping in x11/nvidia-settings. Closing the issue.
 
Just a possibility, but possibly some fix related with multiple buffering (it shoule relate with flipping) caused some specific configurations (GPU, X/Wayland, applications,...) becoming slow.

Below are the list of skipped (on ports) veesions of 550 (production branch) drivers between 550.54.14 and 550.120 picked from FreeBSD x64 Graphics Driver Archive and their release highlights. Some of them contains fixes related with buffering.

FreeBSD Display Driver – x64 550.107.02 | FreeBSD x64
Fixed a race condition involving modeset ownership which could lead to flip event timeout errors when enabling the 'fbdev' kernel module parameter in nvidia-drm.

FreeBSD Display Driver – x64 550.100 | FreeBSD x64
Fixed a bug that caused OpenGL triple buffering to behave like double buffering.

FreeBSD Display Driver – x64 550.90.07 | FreeBSD x64
Fixed a bug that caused OpenGL triple buffering to behave like double buffering.

FreeBSD Display Driver – x64 550.90.07 | FreeBSD x64
Fixed a bug that caused driver installation to fail when the manual page installation directory did not already exist.
Improved the ability of nvidia-modprobe to detect whether kernel modules are already loaded. This corrects an issue that prevented nvidia-persistenced from setting persistence mode on some systems.
Fixed a bug that could cause additional X screens to claim displays that should have been assigned to a prior X screen based on the given X configuration.
Fixed a bug that could cause the X server to crash when graphics applications requested single-buffered drawables while certain features (such as Vulkan sharpening) are enabled.
Fixed a bug that could lead to a kernel panic, due to a failure to release a spinlock under some conditions.
Fixed a race condition which could lead to crashes when Xid errors occur concurrently on multiple GPUs

FreeBSD Display Driver – x64 550.78 | FreeBSD x64
Fixed a regression that led to Xid errors when loading the NVIDIA driver on some notebook systems with RTX 4xxx series GPUs.

FreeBSD Display Driver – x64 550.76 | FreeBSD x64
Minor bug fixes and improvements

FreeBSD Display Driver – x64 550.67 | FreeBSD x64
Fixed a bug that could cause the GPU driver to hang when running some Vkd3d games, such as F1 2021.
Fixed a bug that caused eglExportDMABUFImageQueryMESA() to return invalid DRM formats for the images that use the sRGB color space.
Updated the nvidia-settings control panel to ensure that the entire Display Configuration page can be used when the Layout window is shown.
Updated the nvidia-settings control panel to allow the primary display to be set on any GPU in a multi-GPU system.
 
scottro said:
Just for what it's worth, updating to Nvidia 550.120 (and its kmod) is what enabled my dwl (0.7, NapoleonWils0n dwl 0.17, was a typo, right?) to work. Prior to 550.120, dwl (and labwc) wouldn't start for me. (NVidia GeForce GT1030).
Click to expand...
Exactly! Exactly the same situation. Wayland for the first time working on my machine.
 
if you have just got wayland working
i would recommend wlr-which-key

wlr-which-key lets you create global keyboard shortcuts for wlroots based wayland compositors
with a heads up display like which-key on emacs or nvim showing you the keys you can press and the command that will be run

forums.freebsd.org

wlr-which-key - keymap manager for wlroots inspired by which-key

wlr-which-key lets you create global keyboard shortcuts for wlroots based wayland compositors with a heads up display like which-key on emacs or nvim showing you the keys you can press and the command that will be run the advantage of wlr-which-key is you only have to remember one keyboard...
forums.freebsd.org forums.freebsd.org

my wlr-which-key config

github.com

freebsd-dotfiles-xps/.config/wlr-which-key/config.yaml at master · NapoleonWils0n/freebsd-dotfiles-xps

freebsd dotfiles dell xps 15 2019. Contribute to NapoleonWils0n/freebsd-dotfiles-xps development by creating an account on GitHub.
github.com github.com
 
I'm on dwl. Quite stable, but a few minutes ago just the very first crash. Suddenly, no new Wayland app couldn't be run complaining that it cannot find Wayland display, though dwl was still running. Sometimes I envy all those guys with amdgpu kernel module :)

Code: 
jb@p1 ~> foot
 err: wayland.c:1541: failed to connect to wayland; no compositor running?
but dwl up & running. E.g. Firefox and Chromium (both on Wayland).
 
You must log in or register to reply here.
Back
Top