nvidia-364.12 ( Wayland + DRM/KMS-ready driver ! )

[Myu]

Hello everyone,

So our blazing fast package maintainers have already put an ebuild for x11-drivers/nvidia-drivers-364.12 which is the very first nvidia driver which supports all at once :

Wayland ( Weston needs changes to support the driver so it's still too early : ref )
DRM + KMS ( nvidia own implementation without an fbdev driver for high-res tty ? see ref )
Vulkan
GLNVD by default


It installs fine with kernel 4.4.6 and openGL still works so let's investigate together the other features !

I had limited time to play with it so far but I'll report with any findings and update the wiki along the way.

Have a nice day !

[Juippisi]

It installs fine with kernel 4.4.6 and openGL still works

All I wanted to hear. Thanks for putting this out, time to sync and update!

[gordonp]

OK - I emerge'd 364.12, and I've read nVidia's notes and README for KMS info:

http://www.nvidia.com/download/driverRe ... 0577/en-us
http://us.download.nvidia.com/XFree86/L ... index.html

But I'm kinda lost
My real goal in all this is to use X11 (not Wayland), but to get a nicer console on my large monitor - right now, the console has really-huge fonts, and is pretty much unusable. It ~used~ to work, some time ago, with uvesafb, but no longer.

Here are my USE-flags:

Code: Select all

[ebuild   R   ~] x11-drivers/nvidia-drivers-364.12:0/364::gentoo  USE="X acpi driver gtk3 kms multilib tools -compat -pax_kernel -static-libs -uvm -wayland" 0 KiB
[ebuild   R    ] sys-kernel/gentoo-sources-4.1.15-r1:4.1.15-r1::gentoo  USE="-build -experimental -kdbus -symlink" 0 KiB

But my first problem is that I cannot find nvidia-drm.ko Is there a specific USE-flag needed?

Thanks!

[chrisyu]

Change file nvidia-drivers-364.12.ebuild, line #127

to

Code: Select all

use kms && MODULE_NAMES+=" nvidia-modeset(video:${S}/kernel) nvidia-drm(video:${S}/kernel)"

Re-emerge, reboot, lsmod, then we get nvidia-drm .
But still don't know what to do.

But it's a step forward, right?

I tried

Code: Select all

modprobe -r nvidia-drm ; modprobe nvidia-drm modeset=1

But it printed some kernel panic messages.
Since it's late, I have to test later.

[Myu]

Hi everyone

(edited after findings)

So I've a X11 system booted with nvidia-drm running it seems, TTY resolution is still enormous as before.

Code: Select all

[    2.156724] nvidia: module license 'NVIDIA' taints kernel.
[    2.164752] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
[    2.172984] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  364.12  Wed Mar 16 20:44:12 PDT 2016
[    2.177420] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    2.858437] nvidia-modeset: Allocated GPU:0 (GPU-cb14a0f5-e4d3-2dfd-930b-16c2c145622e) @ PCI:0000:01:00.0

Steps :

0. Make a BACKUP of /usr/portage/x11-drivers/nvidia-drivers-364.12, you never know.
1. Apply @chrisyu modification ( thanks! )
2. ebuild nvidia-drivers-364.12 manifest
3. emerge =nvidia-drivers-364.12 ( nvidia-drm.ko is now at /lib64/modules/$(uname -r)/video/nvidia-drm.ko )
4. add this to /etc/modprobe.d/nvidia.conf :

Code: Select all

options nvidia_drm modeset=1

I'll keep investigating regarting the TTY resolution

edit : The arch wiki mention on the KMS page

The proprietary NVIDIA driver supports KMS (since 364.12). However, it lacks an fbdev driver for the high-resolution console.

[Josef.95]

Just a good info-link from nvidia-forum
NVIDIA 364.12 release: Vulkan, GLVND, DRM KMS, and EGLStreams

[xtx]

anybody figure out how to use vulkan yet? i installed the new nvidia-beta driver and i have talos on steam. i enabled the public beta for talos and launched it as 64 bit, but when i switch to the vulkan api in game i get "Cannot set display mode" and I see the line "Vulkan error: Cannot find a compatible vulkan ICD!"

my first guess is that my launch options for steam are the issue, i launch steam with the script:

Code: Select all

#!/bin/bash 
export DISPLAY=:0
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/nvidia/lib:/usr/lib/opengl/nvidia/lib" 
exec ~/.local/share/Steam/steam.sh "$@"

I did a search for vulkan to see if there was a folder somewhere that I need to include in this launch script but I didn't see anything.

[Saundersx]

anybody figure out how to use vulkan yet? i installed the new nvidia-beta driver and i have talos on steam. i enabled the public beta for talos and launched it as 64 bit, but when i switch to the vulkan api in game i get "Cannot set display mode" and I see the line "Vulkan error: Cannot find a compatible vulkan ICD!"

my first guess is that my launch options for steam are the issue, i launch steam with the script:

Code: Select all

#!/bin/bash 
export DISPLAY=:0
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/nvidia/lib:/usr/lib/opengl/nvidia/lib" 
exec ~/.local/share/Steam/steam.sh "$@"

I did a search for vulkan to see if there was a folder somewhere that I need to include in this launch script but I didn't see anything.

I'm betting this is related https://bugs.gentoo.org/show_bug.cgi?id=578040

[xtx]

anybody figure out how to use vulkan yet? i installed the new nvidia-beta driver and i have talos on steam. i enabled the public beta for talos and launched it as 64 bit, but when i switch to the vulkan api in game i get "Cannot set display mode" and I see the line "Vulkan error: Cannot find a compatible vulkan ICD!"

my first guess is that my launch options for steam are the issue, i launch steam with the script:

Code: Select all

#!/bin/bash 
export DISPLAY=:0
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib32/opengl/nvidia/lib:/usr/lib/opengl/nvidia/lib" 
exec ~/.local/share/Steam/steam.sh "$@"

I did a search for vulkan to see if there was a folder somewhere that I need to include in this launch script but I didn't see anything.

I'm betting this is related https://bugs.gentoo.org/show_bug.cgi?id=578040

Good catch, almost definitely the issue. Thanks, I'll keep my eyes on the bug report

[mouacyk]

After modifying the driver ebuild and patching weston, I still end up with an error when running weston-launch:

Code: Select all


[ 5338.262318] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=none,decodes=none:owns=io+mem
[ 5338.262416] nvidia-nvlink: Nvlink Core is being initialized, major device number 250
[ 5338.262437] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  364.12  Wed Mar 16 21:11:26 PDT 2016
[ 5338.263459] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  364.12  Wed Mar 16 20:44:12 PDT 2016
[ 5338.263950] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
[ 5338.824705] nvidia-modeset: Allocated GPU:0 (GPU-595b3d36-aaea-d916-d4ce-4efa80c7c223) @ PCI:0000:02:00.0
[ 5338.886475] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 5338.886476] [drm] No driver support for vblank timestamp query.
[ 5350.257392] [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000200] Failed to import NVKMS memory to GEM object

Edit: Had to run the good old fashion way with full parameters.

Code: Select all

weston -B drm-backend.so --tty=1 --use-egldevice --current-mode

Screenshot: http://i63.tinypic.com/dmuyz7.png

[Myu]

@mouacyk : Nicely done ! Could you describe how exactly you've patched weston ? With version 1.9 or 1.10 ?


x11-drivers/nvidia-drivers-364.12-r1 now includes the -drm.ko needed fixes + another fix for Vulkan.

[mouacyk]

Version 1.10 - I cloned the latest weston git sources and applied each of the 7 patches that NVidia posted. 2 or 3 of the patches didn't apply completely, so had to edit manually. After all patch is done, build and install the patched weston locally.

Haven't bothered with xwayland yet, because there are use flag conflicts with egl and opengl on my system. However, a quick build of qtwayland without egl and wayland-compositor allowed running some qt apps from within weston, such as kate and kcalc.

[Celes_Eternal]

Hello guys,

Anybody know why i can't upgrade more than 361.28-r2, even with keyword and mask?
I didn't found any informations, but i have the ebuild in /usr/portage/...
I know i have some change to do, like upgrading my kernel. But why emerge say nothing about 364?

Thanks

[dweezil-n0xad]

what is the emerge output when you try the new version?

Code: Select all

emerge =x11-drivers/nvidia-drivers-364.12-r1 -1av

[Celes_Eternal]

Sorry to be so late
Thanks, it seem that i had to create a package.unmask, just mask other versions was not enough...
First time i do that. Anyway, my question has nothing to do here, sorry...