| 1 |
On 08/15 10:33, Corentin “Nado” Pazdera wrote: |
| 2 |
> August 15, 2018 4:19 AM, tuxic@××××××.de wrote: |
| 3 |
> |
| 4 |
> > On 08/14 11:16, Nikos Chantziaras wrote: |
| 5 |
> > |
| 6 |
> >> On 14/08/18 13:35, tuxic@××××××.de wrote: |
| 7 |
> >> Hi, |
| 8 |
> >> |
| 9 |
> >> after upgrading to nvidia-drivers-396.51 no CUDA devices were found. |
| 10 |
> >> Last version, which works for me is nvidia-drivers-396.24-r1. |
| 11 |
> >> |
| 12 |
> >> Do you have the "uvm" USE flag set? It might be required for CUDA, but it's |
| 13 |
> >> disabled by default (perhaps wrongly, because USE flags should follow |
| 14 |
> >> upstream defaults unless there's a reason not to.) |
| 15 |
> > |
| 16 |
> > Yes it is: |
| 17 |
> > |
| 18 |
> > (this is the version, which is currentlu still working |
| 19 |
> > Installed versions: 396.24-r1(0/396)^md(08:31:04 PM 08/14/2018)(X driver kms static-libs tools uvm |
| 20 |
> > -acpi -compat -gtk3 -multilib -pax_kernel -wayland ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" |
| 21 |
> > ABI_S390="-32 -64" ABI_X86="64 -32 -x32" KERNEL="linux -FreeBSD") |
| 22 |
> > |
| 23 |
> > and set via /etc/portage/package.use |
| 24 |
> > |
| 25 |
> > # required by app-admin/conky-1.10.6-r1::gentoo[nvidia,X] |
| 26 |
> > # required by @selected |
| 27 |
> > # required by @world (argument) |
| 28 |
> >> =x11-drivers/nvidia-drivers-378.13 static-libs uvm |
| 29 |
> > |
| 30 |
> > What else could be the reason for the problem? |
| 31 |
> > How can I fix it? |
| 32 |
> |
| 33 |
> Can you also show content of modprobe.d file ? |
| 34 |
> Did you read the whole wiki page ? Did you check for MSI interrupts ? |
| 35 |
> https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers#Driver_fails_to_initialize_when_MSI_interrupts_are_enabled |
| 36 |
> |
| 37 |
> Regards, |
| 38 |
> -- |
| 39 |
> Corentin “Nado” Pazdera |
| 40 |
> |
| 41 |
|
| 42 |
The wiki-page is old...it speaks of nvidia-driver-174. |
| 43 |
|
| 44 |
|
| 45 |
modprobe.d/nvidia.conf: |
| 46 |
---------------------------- |
| 47 |
# Nvidia drivers support |
| 48 |
alias char-major-195 nvidia |
| 49 |
alias /dev/nvidiactl char-major-195 |
| 50 |
|
| 51 |
# To tweak the driver the following options can be used, note that |
| 52 |
# you should be careful, as it could cause instability!! For more |
| 53 |
# options see /usr/share/doc/nvidia-drivers-396.24-r1/README |
| 54 |
# |
| 55 |
# !!! SECURITY WARNING !!! |
| 56 |
# DO NOT MODIFY OR REMOVE THE DEVICE FILE RELATED OPTIONS UNLESS YOU KNOW |
| 57 |
# WHAT YOU ARE DOING. |
| 58 |
# ONLY ADD TRUSTED USERS TO THE VIDEO GROUP, THESE USERS MAY BE ABLE TO CRASH, |
| 59 |
# COMPROMISE, OR IRREPARABLY DAMAGE THE MACHINE. |
| 60 |
options nvidia NVreg_DeviceFileMode=432 NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=27 NVreg_ModifyDeviceFiles=1 |
| 61 |
|
| 62 |
|
| 63 |
modprobe.d/nvidia-rmmod.conf |
| 64 |
---------------------------- |
| 65 |
# Nvidia UVM support |
| 66 |
remove nvidia modprobe -r --ignore-remove nvidia-drm nvidia-modeset nvidia-uvm nvidia |
| 67 |
|
| 68 |
|
| 69 |
All the configurations are working all the years up to x11-drivers/nvidia-drivers-396.24-r1. |
| 70 |
After that, no CUDA device was found. |
| 71 |
Based on logical reasons, I would tend to think, that it is something |
| 72 |
version specific and no global setting which is valid since |
| 73 |
nvidia-driver-174. |
| 74 |
|
| 75 |
Regards, |
Archives