On 08/15 11:39, Corentin “Nado” Pazdera wrote: > August 15, 2018 1:16 PM, tu...@posteo.de wrote: > > > The wiki-page is old...it speaks of nvidia-driver-174. > > Yeah, for legacy cards... If you check the history its also been updated > quite frequently. > > > modprobe.d/nvidia.conf: > > ---------------------------- > > # Nvidia drivers support > > alias char-major-195 nvidia > > alias /dev/nvidiactl char-major-195 > > > > # To tweak the driver the following options can be used, note that > > # you should be careful, as it could cause instability!! For more > > # options see /usr/share/doc/nvidia-drivers-396.24-r1/README > > # > > # !!! SECURITY WARNING !!! > > # DO NOT MODIFY OR REMOVE THE DEVICE FILE RELATED OPTIONS UNLESS YOU KNOW > > # WHAT YOU ARE DOING. > > # ONLY ADD TRUSTED USERS TO THE VIDEO GROUP, THESE USERS MAY BE ABLE TO > > CRASH, > > # COMPROMISE, OR IRREPARABLY DAMAGE THE MACHINE. > > options nvidia NVreg_DeviceFileMode=432 NVreg_DeviceFileUID=0 > > NVreg_DeviceFileGID=27 > > NVreg_ModifyDeviceFiles=1 > > > > modprobe.d/nvidia-rmmod.conf > > ---------------------------- > > # Nvidia UVM support > > remove nvidia modprobe -r --ignore-remove nvidia-drm nvidia-modeset > > nvidia-uvm nvidia > > > > All the configurations are working all the years up to > > x11-drivers/nvidia-drivers-396.24-r1. > > After that, no CUDA device was found. > > Based on logical reasons, I would tend to think, that it is something > > version specific and no global setting which is valid since > > nvidia-driver-174. > > Updates may need to change a config file after bringing breaking changes, it > might not be the cause > I agree. But its possible. > > Is CUDA disabled on both cards? I have a 970Ti, although my MB is different, > we might try to > compare the big differences in our systems? > > -- > Corentin “Nado” Pazdera >
...sorry, I am no native speaker...I dont understand. I did not know how to disable CUDA on both cards. So...since it works perfectly with the old driver I would think: No, CUDA is enabled (or at least the old driver does this for me). Then I do an "emerge <new nvidia-driver-version>" and CUDA stops working. I do not change anything else nor do I know, who/what could disable CUDA on both cards ... except for the driver itsself. This is weird. Again, for logical reasons I think, that the culprit is either the driver itsself or a missing (and therefor undocumented) configuration step needed for the new drivers. The cards are not "old" in any sense.
