View previous topic :: View next topic |
Author |
Message |
Myu Apprentice
Joined: 22 Oct 2014 Posts: 164 Location: Belgium
|
Posted: Tue Mar 22, 2016 7:26 am Post subject: nvidia-364.12 ( Wayland + DRM/KMS-ready driver ! ) |
|
|
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 ! _________________ Gentoo stable with bits of ~amd64 // Xfce 4.13 + Compiz Reloaded.
Last edited by Myu on Tue Mar 22, 2016 8:06 pm; edited 2 times in total |
|
Back to top |
|
|
Juippisi Developer
Joined: 30 Sep 2005 Posts: 722 Location: /home
|
Posted: Tue Mar 22, 2016 9:44 am Post subject: Re: nvidia-364.12 ( Wayland + DRM/KMS-ready driver ! ) |
|
|
Myu wrote: | 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! |
|
Back to top |
|
|
gordonp Tux's lil' helper
Joined: 23 May 2005 Posts: 100
|
Posted: Tue Mar 22, 2016 1:34 pm Post subject: How to use? |
|
|
OK - I emerge'd 364.12, and I've read nVidia's notes and README for KMS info:
http://www.nvidia.com/download/driverResults.aspx/100577/en-us
http://us.download.nvidia.com/XFree86/Linux-x86_64/364.12/README/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: | [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! |
|
Back to top |
|
|
chrisyu Apprentice
Joined: 10 Apr 2003 Posts: 207 Location: China
|
Posted: Tue Mar 22, 2016 4:03 pm Post subject: |
|
|
Change file nvidia-drivers-364.12.ebuild, line #127
to
Code: |
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: |
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. |
|
Back to top |
|
|
Myu Apprentice
Joined: 22 Oct 2014 Posts: 164 Location: Belgium
|
Posted: Tue Mar 22, 2016 4:45 pm Post subject: |
|
|
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: |
[ 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: | options nvidia_drm modeset=1 |
I'll keep investigating regarting the TTY resolution
edit : The arch wiki mention on the KMS page
Quote: | The proprietary NVIDIA driver supports KMS (since 364.12). However, it lacks an fbdev driver for the high-resolution console. |
_________________ Gentoo stable with bits of ~amd64 // Xfce 4.13 + Compiz Reloaded. |
|
Back to top |
|
|
Josef.95 Advocate
Joined: 03 Sep 2007 Posts: 4520 Location: Germany
|
|
Back to top |
|
|
xtx Tux's lil' helper
Joined: 27 Dec 2011 Posts: 129
|
Posted: Wed Mar 23, 2016 3:36 am Post subject: |
|
|
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: | #!/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. |
|
Back to top |
|
|
Saundersx Apprentice
Joined: 11 Apr 2005 Posts: 290
|
Posted: Wed Mar 23, 2016 6:50 am Post subject: |
|
|
xtx wrote: | 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: | #!/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 |
|
Back to top |
|
|
xtx Tux's lil' helper
Joined: 27 Dec 2011 Posts: 129
|
Posted: Wed Mar 23, 2016 3:31 pm Post subject: |
|
|
Saundersx wrote: | xtx wrote: | 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: | #!/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 |
|
Back to top |
|
|
mouacyk n00b
Joined: 23 Mar 2009 Posts: 23
|
Posted: Wed Mar 23, 2016 7:48 pm Post subject: |
|
|
After modifying the driver ebuild and patching weston, I still end up with an error when running weston-launch:
Code: | 
[ 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: | weston -B drm-backend.so --tty=1 --use-egldevice --current-mode |
Screenshot: http://i63.tinypic.com/dmuyz7.png |
|
Back to top |
|
|
Myu Apprentice
Joined: 22 Oct 2014 Posts: 164 Location: Belgium
|
Posted: Thu Mar 24, 2016 4:27 pm Post subject: |
|
|
@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. _________________ Gentoo stable with bits of ~amd64 // Xfce 4.13 + Compiz Reloaded. |
|
Back to top |
|
|
mouacyk n00b
Joined: 23 Mar 2009 Posts: 23
|
Posted: Thu Mar 24, 2016 5:23 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
Celes_Eternal n00b
Joined: 23 Dec 2014 Posts: 46
|
Posted: Sat Apr 02, 2016 11:58 pm Post subject: |
|
|
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 |
|
Back to top |
|
|
dweezil-n0xad Apprentice
Joined: 30 Oct 2006 Posts: 156 Location: Ostend, Belgium
|
Posted: Sun Apr 03, 2016 10:29 am Post subject: |
|
|
what is the emerge output when you try the new version?
Code: | emerge =x11-drivers/nvidia-drivers-364.12-r1 -1av |
_________________ i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
Back to top |
|
|
Celes_Eternal n00b
Joined: 23 Dec 2014 Posts: 46
|
Posted: Tue Apr 05, 2016 3:17 pm Post subject: |
|
|
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... |
|
Back to top |
|
|
|