Current packages Kernel 4.18.5, nvidia-drivers 396.54, cuda toolkit 9.2.88 driver and uvm successfully loads [ 3418.044800] nvidia-nvlink: Nvlink Core is being initialized, major device number 246 [ 3418.045321] nvidia 0000:07:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none [ 3418.045447] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 396.54 Tue Aug 14 19:02:34 PDT 2018 (using threaded interrupts) [ 3469.823513] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 245 correct libOpenCL is found (eselect opencl shows only nvidia and as enabled) # ldd /usr/bin/clinfo linux-vdso.so.1 (0x00007ffc98de6000) libOpenCL.so.1 => /usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1 (0x00007f368d0e5000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f368cee1000) libc.so.6 => /lib64/libc.so.6 (0x00007f368cb55000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f368c935000) /lib64/ld-linux-x86-64.so.2 (0x00007f368d505000) nvidia-smi works # nvidia-smi Sun Sep 2 20:26:18 2018 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 396.54 Driver Version: 396.54 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 105... Off | 00000000:07:00.0 Off | N/A | | 40% 38C P0 N/A / 75W | 0MiB / 4040MiB | 2% Default | .... (1050Ti) yet clinfo and all tested OpenCL applications fail to find the GPU # clinfo Number of platforms 0 Did work pre-update (Kernel 4.14.15, not sure about driver and cuda versions)
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. Write in the summary, which Gentoo package is broken, so that we can assign the ticket to the right team then. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
