I suspect part of the problem then is that my system is an Optimus
system, and so I use Bumblebee. The command prints as follows:

$ update-alternatives --display x86_64-linux-gnu_gl_conf 
x86_64-linux-gnu_gl_conf - manual mode
  link currently points to /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
/usr/lib/nvidia-319-updates/ld.so.conf - priority 8602
  slave x86_64-linux-gnu_grub_fb_blacklist: 
/usr/share/nvidia-319-updates/nvidia-319-updates.grub-gfxpayload
  slave x86_64-linux-gnu_libOpenCL.so: /usr/lib/nvidia-319-updates/libOpenCL.so
  slave x86_64-linux-gnu_libOpenCL.so_lib32: 
/usr/lib32/nvidia-319-updates/libOpenCL.so
  slave x86_64-linux-gnu_libvdpau_nvidia.so: 
/usr/lib/nvidia-319-updates/vdpau/libvdpau_nvidia.so
  slave x86_64-linux-gnu_libvdpau_nvidia.so.1: 
/usr/lib/nvidia-319-updates/vdpau/libvdpau_nvidia.so.1
  slave x86_64-linux-gnu_libvdpau_nvidia.so.1_lib32: 
/usr/lib32/nvidia-319-updates/vdpau/libvdpau_nvidia.so.1
  slave x86_64-linux-gnu_libvdpau_nvidia.so_lib32: 
/usr/lib32/nvidia-319-updates/vdpau/libvdpau_nvidia.so
  slave x86_64-linux-gnu_man_nvidiaxconfig.gz: 
/usr/share/man/man1/alt-nvidia-319-updates-xconfig.1.gz
  slave x86_64-linux-gnu_nvidia-autostart.desktop: 
/usr/share/nvidia-319-updates/nvidia-autostart.desktop
  slave x86_64-linux-gnu_nvidia-cuda-mps-control: 
/usr/lib/nvidia-319-updates/bin/nvidia-cuda-mps-control
  slave x86_64-linux-gnu_nvidia-cuda-mps-control.1.gz: 
/usr/share/man/man1/alt-nvidia-319-updates-cuda-mps-control.1.gz
  slave x86_64-linux-gnu_nvidia-cuda-mps-server: 
/usr/lib/nvidia-319-updates/bin/nvidia-cuda-mps-server
  slave x86_64-linux-gnu_nvidia-debugdump: 
/usr/lib/nvidia-319-updates/bin/nvidia-debugdump
  slave x86_64-linux-gnu_nvidia-smi.1.gz: 
/usr/share/man/man1/alt-nvidia-319-updates-smi.1.gz
  slave x86_64-linux-gnu_nvidia.icd: /usr/share/nvidia-319-updates/nvidia.icd
  slave x86_64-linux-gnu_nvidia_app_profile: 
/usr/share/nvidia-319-updates/nvidia-application-profiles-319.49-rc
  slave x86_64-linux-gnu_nvidia_bug_report: 
/usr/lib/nvidia-319-updates/bin/nvidia-bug-report.sh
  slave x86_64-linux-gnu_nvidia_desktop: 
/usr/share/nvidia-319-updates/ubuntu-nvidia-settings.desktop
  slave x86_64-linux-gnu_nvidia_drv: 
/usr/lib/nvidia-319-updates/xorg/nvidia_drv.so
  slave x86_64-linux-gnu_nvidia_modconf: /lib/nvidia-319-updates/modprobe.conf
  slave x86_64-linux-gnu_nvidia_smi: /usr/lib/nvidia-319-updates/bin/nvidia-smi
  slave x86_64-linux-gnu_nvidia_xconfig: 
/usr/lib/nvidia-319-updates/bin/nvidia-xconfig
  slave x86_64-linux-gnu_xorg_extra_modules: /usr/lib/nvidia-319-updates/xorg
  slave x86_64-linux-gnu_xvmcconfig: /usr/lib/nvidia-319-updates/XvMCConfig
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf - priority 500
  slave x86_64-linux-gnu_xorg_extra_modules: 
/usr/lib/x86_64-linux-gnu/xorg/x11-extra-modules
Current 'best' version is '/usr/lib/nvidia-319-updates/ld.so.conf'.

I can't set the GL alternative to the nvidia one, because then GL won't
work on my system: I use mesa, because my primary card is Intel. It
seems odd to me that the OpenCL configuration is tied to the OpenGL one.
I don't use my nvidia card for GL, but only for OpenCL. I use bumblebee
to turn the card on and run computational code on it, not for display
purposes. Would it be possible to separate the two configurations?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231581

Title:
  nVidia opencl symlink incorrect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1231581/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to