Ok, it turns out this only happens when I have Samsung magicbright dynamic contrast enabled.
But this was not a problem under the 361.42 driver so it is still a regression in the nvidia xorg driver.
But now at least we know how to reproduce it. Can nvidia now take a look?
Thank you.
I wonder if these support will be added in the future. In the meantime Valve adding support for these tech these week sometime for Dota 2 and probably whole source 2 engine. So if Ubuntu current (tested) driver is not supporting Vulkan officially I can’t run Dota 2 Vulkan DLC on my old machine? It probably give me a message that my system is not officially supported these features in the driver as well as these was being like when nvidia present their lib gl vnd firt release driver.
Do I have to held any hopes that these support will be added in future or should forget about it?
I’m developing a real time graphics application on an embedded linux platform using DRM and EGL.
The platform uses a special linux based operating system without X-server support and no GUI.
I can build and run applications just fine, however, I’m facing the issue that VSYNC is always enabled and the framerate can not exceed 60fps (This is the refresh rate of the connected monitor in fullHD resolution).
Usually, with x-Server, one would open the nvidia-settings app and force VSYNC off, or, alternatively, directly edit the config file. I can not do that on my embedded platform because I do not have X-Server support.
I have tried to disable VSYNC using EGL in my egl setup source code by setting “eglSwapInterval” to 0, as well as passing EGL_MIN_SWAP_INTERVAL as 0 in the eglconfig array. Even though the swap intervall function call returns no error, VSYNC remains active and fps are locked. I have also tried to edit several environment variables that are supposed to disable vsync, but again those only seem to work with X.
So my question is, how can I force VSYNC off without having access to the nvidia-settings app and the X-Server?
Am I missing something in my EGL setup routine, or do I need to configure the driver somehow?
I have enable kms for nvidia with the latest stable driver. I get these error message in dmesg.
[ 47.233586] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
[ 47.312051] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
[ 47.326385] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
[ 47.327470] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
[ 47.354485] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
[ 47.355577] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object
‘VSYNC off’ mode is not yet supported by nvidia-drm driver, work is in progress to get it supported.
For error messages “Failed to import NVKMS memory to GEM object”, can I get to know how can I reproduce them? With which application you are seeing these error? From configuration information, you are using gnome-shell, but as far as know gnome don’t have support for eglstreams yet.
I get the same “Failed to import NVKMS memory to GEM object” error. I’m booting via UEFI and trying to get early KMS working for a boot screen / virtual console at native resolution. I don’t think Gnome-Shell is the culprit here as we’re all having problems before the display server even starts (whether it be X or Wayland… doesn’t matter).
As per the ArchWiki article (https://wiki.archlinux.org/index.php/NVIDIA#DRM_kernel_mode_setting), I have the necessary modules loaded into my initramfs: nvidia, nvidia_modeset, nvidia_uvm and nvidia_drm. I also have nvidia-drm.modeset=1 as a kernel command line option. The initramfs has been rebuilt after adding all of the above.
Hi All,
For issue " [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GEM object"
Please start the separate forum thread to avoid confusion. Also provide details reproduction steps and nvidia bug report so that we can internally reproduce this issue and investigate.
Yes, 32-bit vulkan should work with the x86_64 NVIDIA driver package: the nvidia_icd.json file lists “libGLX_nvidia.so.0” as the library, and the run-time loader should pick up the correct 32-bit or 64-bit libGLX_nvidia.so.0. If that doesn’t work for you, please let me know.
I’ve been trying this intermittently since the first release, when it worked. I figured someone broke something and it would be fixed, but seemingly not. Anyway, for a long time, launching weston just goes to a completely black screen, but is seemingly reactive to input. I get the following kernel messages at that time:
Are you doing development work? Your kernel version is new. What kernel level was it last working on? I have been using a 4.6.5 and 4.8.5 for a while and recently upgraded to 4.8.6. I plan to upgrade to 4.8.8 or 4.8.12 by next week.
What is in: /proc/driver/nvidia/version? It looks like 375.20
What is on your kernel boot line: Remove nomodeset if present. It is not present in the logs.
What other kernels do you have on this system?
Can someone PLEASE help me. I have a laptop with an Intel GPU and an Nvidia GTX 970m. I’m trying to turn off the power to the Nvidia GPU when using the Intel GPU in order to save power. To do this, I need to unload the Nvidia modules, but I’m stuck on nvidia_drm - it just doesn’t unload:
$ sudo rmmod nvidia_drm
rmmod: ERROR: Module nvidia_drm is in use
I’m sing the 375.20 driver, and am running kernel 4.9.