Are the Weston patches supposed to work with the latest nvidia packages? I keep getting "failed to initialize egl" and "fatal: failed to create compositor backend" errors whenever I try to launch Weston. Am I running into the same kernel issue?

Thanks for the info. I did do that, but at least I know it's not a driver issue. I'll look more into it when I get back home.

I'm trying to use the modesetting interface through the libdrm API (drmModeGetResources() etc) to query the video device configuration. The application works with the nouveau, radeon, amdgpu, and i915 drivers, but not with the nvidia proprietary driver. drmAvailable() returns false, and most other calls return an error value of EINVAL (invalid argument). I have tested using driver 375.26 on Fedora 25, kernel 4.9.8 and driver 367.27 on Ubuntu 14.04, kernel 4.4.0. I see 3 possibilities: 1) I've misunderstood this post. Support for KMS in the Nvidia driver does not refer to these facilities. 2) The Nvidia driver is not properly configured. Parameter nvida-drm.modeset=1 is passed on the command line, as well as being set in modprobe.d. modprobe -n -vv nvidia-drm reports: [code] insmod /lib/modules/4.4.0-62-generic/updates/dkms/nvidia_367_drm.ko modeset=0 modeset=1 modeset=1 [/code] And dmeg contains the following lines: [code] 2.113245] [drm] Initialized drm 1.1.0 20060810 [ 2.135747] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [ 2.964251] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.964253] [drm] No driver support for vblank timestamp query. [/code] From other posts, I believe this indicates that modesetting is configured. But perhaps there's something else that needs to be done. 3) There's some secret sauce that needs to be added to the code. As I said, the application works with the common open source drivers. Guidance appreciated

insmod /lib/modules/4.4.0-62-generic/updates/dkms/nvidia_367_drm.ko modeset=0 modeset=1 modeset=1

2.113245] [drm] Initialized drm 1.1.0 20060810

[    2.135747] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver

[    2.964251] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

[    2.964253] [drm] No driver support for vblank timestamp query.

Hello. Is there a plans to support Xwayland on Nvidia driver? I can't run any GLX application on GNOME Wayland with Nvidia drivers, it give's me "Could not initialize GLX"

Hello, I'm having problems on running any kind of vulkan example. I wrote a small triangle snippet that was working once and now it gives me: VkResult is "ERROR_OUT_OF_HOST_MEMORY" Moreover, this dmesg is displayed whenever I try to run a vulkan program or a wayland session (running a wayland session usually leads to a freeze) [code] [ 46.575238] nvidia-modeset: Allocated GPU:0 (GPU-11f5c854-549f-e316-402b-12d0ed756f2a) @ PCI:0000:01:00.0 [ 46.575364] nvidia-modeset: Freed GPU:0 (GPU-11f5c854-549f-e316-402b-12d0ed756f2a) @ PCI:0000:01:00.0 [/code] Opengl runs smoothly, it may be a misconfiguration but I don't understand where it could be. Could you help me? Just tell me what kind of info you need. Thank you, -l

[   46.575238] nvidia-modeset: Allocated GPU:0 (GPU-11f5c854-549f-e316-402b-12d0ed756f2a) @ PCI:0000:01:00.0

[   46.575364] nvidia-modeset: Freed GPU:0 (GPU-11f5c854-549f-e316-402b-12d0ed756f2a) @ PCI:0000:01:00.0