BOINC not using CUDA after upgrade to Ubuntu 14.04


log in

Advanced search

Questions and Answers : GPU applications : BOINC not using CUDA after upgrade to Ubuntu 14.04

Author Message
Genesius
Send message
Joined: 29 Nov 00
Posts: 2
Credit: 857,724
RAC: 472
United States
Message 1505872 - Posted: 19 Apr 2014, 0:33:33 UTC

HP machine running Ubuntu Gnome 14.04 with a Nvidia GeForce GT-610, driver 337.12. CUDA worked fine when I was still on Ubuntu Gnome 13.10, but after a clean install of 14.04 I only get the CPU version of BOINC. I have BOINC 7.2.47 installed from the Ubuntu repositories. Tried installing the boinc-nvidia-cuda package, but that didn't help. Tried a few different Nvidia drivers(all installed from Ubuntu repos) with no change.

First 20-odd lines of the event log:

    Wed 16 Apr 2014 11:28:34 PM EDT | | Starting BOINC client version 7.2.47 for x86_64-pc-linux-gnu
    Wed 16 Apr 2014 11:28:34 PM EDT | | log flags: file_xfer, sched_ops, task
    Wed 16 Apr 2014 11:28:34 PM EDT | | Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
    Wed 16 Apr 2014 11:28:34 PM EDT | | Data directory: /var/lib/boinc-client
    Wed 16 Apr 2014 11:28:34 PM EDT | | No usable GPUs found
    Wed 16 Apr 2014 11:28:34 PM EDT | | Host name: andy-desktop
    Wed 16 Apr 2014 11:28:34 PM EDT | | Processor: 2 GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz [Family 6 Model 15 Stepping 13]
    Wed 16 Apr 2014 11:28:34 PM EDT | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm
    Wed 16 Apr 2014 11:28:34 PM EDT | | OS: Linux: 3.13.0-24-generic
    Wed 16 Apr 2014 11:28:34 PM EDT | | Memory: 3.86 GB physical, 3.72 GB virtual
    Wed 16 Apr 2014 11:28:34 PM EDT | | Disk: 18.21 GB total, 10.99 GB free
    Wed 16 Apr 2014 11:28:34 PM EDT | | Local time is UTC -4 hours
    Wed 16 Apr 2014 11:28:34 PM EDT | | Config: GUI RPCs allowed from:
    Wed 16 Apr 2014 11:28:34 PM EDT | rosetta@home | URL http://boinc.bakerlab.org/rosetta/; Computer ID 1731518; resource share 100
    Wed 16 Apr 2014 11:28:34 PM EDT | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7240280; resource share 100
    Wed 16 Apr 2014 11:28:34 PM EDT | SETI@home | General prefs: from SETI@home (last modified 16-Apr-2014 19:10:43)
    Wed 16 Apr 2014 11:28:34 PM EDT | SETI@home | Computer location: home
    Wed 16 Apr 2014 11:28:34 PM EDT | SETI@home | General prefs: no separate prefs for home; using your defaults
    Wed 16 Apr 2014 11:28:34 PM EDT | | Reading preferences override file
    Wed 16 Apr 2014 11:28:34 PM EDT | | Preferences:
    Wed 16 Apr 2014 11:28:34 PM EDT | | max memory usage when active: 1975.91MB
    Wed 16 Apr 2014 11:28:34 PM EDT | | max memory usage when idle: 3556.64MB
    Wed 16 Apr 2014 11:28:34 PM EDT | | max disk usage: 1.00GB
    Wed 16 Apr 2014 11:28:34 PM EDT | | (to change preferences, visit a project web site or select Preferences in the Manager)
    Wed 16 Apr 2014 11:28:34 PM EDT | | gui_rpc_auth.cfg is empty - no GUI RPC password protection
    Wed 16 Apr 2014 11:28:34 PM EDT | | Not using a proxy

Profile arkayn
Volunteer tester
Avatar
Send message
Joined: 14 May 99
Posts: 3594
Credit: 47,338,244
RAC: 328
United States
Message 1505884 - Posted: 19 Apr 2014, 2:35:04 UTC

If you shut down BOINC and then restart it, does it detect the GPU's?
____________

Genesius
Send message
Joined: 29 Nov 00
Posts: 2
Credit: 857,724
RAC: 472
United States
Message 1506035 - Posted: 19 Apr 2014, 14:27:10 UTC - in response to Message 1505884.

Nope. Did "sudo /etc/init.d/boinc-client stop", confirmed it stopped, then "sudo /etc/init.d/boinc-client start".

Checked the event log in Boinc Manager to make sure I was looking at the right time & date, still says no usable GPU.
____________

Jason McGuffin
Send message
Joined: 12 Aug 13
Posts: 1
Credit: 55,359
RAC: 635
United States
Message 1513037 - Posted: 7 May 2014, 3:06:36 UTC - in response to Message 1506035.

Nope. Did "sudo /etc/init.d/boinc-client stop", confirmed it stopped, then "sudo /etc/init.d/boinc-client start".

Checked the event log in Boinc Manager to make sure I was looking at the right time & date, still says no usable GPU.


I still cannot use my Quadro either after 14.04. Used all above steps.

Rostislav Stříbrný
Send message
Joined: 28 Feb 13
Posts: 1
Credit: 22,754
RAC: 1
Czech Republic
Message 1517825 - Posted: 18 May 2014, 15:07:43 UTC - in response to Message 1513037.

Hi,
I'm also using Ubuntu 14.04 LTS and CUDA and OpenCL works successfully for other BOINC projects. Unfortunately, not for SETI@home. :-(

BOINC normally detects my GPU:


Sun 18 May 2014 04:37:06 PM CEST | | CUDA: NVIDIA GPU 0: NVS 5400M (driver version unknown, CUDA version 6.0, compute capability 2.1, 1024MB, 896MB available, 182 GFLOPS peak)
Sun 18 May 2014 04:37:06 PM CEST | | OpenCL: NVIDIA GPU 0: NVS 5400M (driver version 331.38, device version OpenCL 1.1 CUDA, 1024MB, 896MB available, 182 GFLOPS peak)



My advice: Try installing at least the nvidia-cuda-toolkit package and maybe also ocl-icd-libopencl1.


My list of (relevant) installed packages:

dpkg --list | grep -E "ocl|opencl|nvidia|cuda" | cut -c5-40,70-110 | sort

boinc-nvidia-cuda 7.2.42+dfsg-1
libcuda1-331-updates 331.38-0ubuntu7
libcudart5.5:amd64 5.5.22-3ubuntu1
nvidia-331-updates 331.38-0ubuntu7
nvidia-cuda-dev 5.5.22-3ubuntu1
nvidia-cuda-doc 5.5.22-3ubuntu1
nvidia-cuda-gdb 5.5.22-3ubuntu1
nvidia-cuda-toolkit 5.5.22-3ubuntu1
nvidia-opencl-icd-331-updates 331.38-0ubuntu7
nvidia-prime 0.6.2
nvidia-profiler 5.5.22-3ubuntu1
nvidia-settings 337.12-0ubuntu1~xedgers13.10.1
nvidia-visual-profiler 5.5.22-3ubuntu1
ocl-icd-dev 2.1.3-4
ocl-icd-libopencl1:amd64 2.1.3-4
ocl-icd-libopencl1:i386 2.1.3-4
ocl-icd-opencl-dev:amd64 2.1.3-4
opencl-headers 1.2-2013.10.23-1

Porcelain Mouse
Send message
Joined: 17 May 99
Posts: 21
Credit: 18,092,357
RAC: 25,104
United States
Message 1518058 - Posted: 19 May 2014, 6:36:48 UTC
Last modified: 19 May 2014, 7:07:36 UTC

I have the same symptom as OP, nVidia GPU not used after upgrade to Ubuntu 14.04. But, my system detects CUDA and still cannot run CUDA Seti. I'm pretty sure my GTX 280 was running CUDA apps before upgrade, now it will not run them. It just says:

App version needs OpenCL but GPU doesn't support it
Application uses missing NVIDIA GPU

Both these lines are new to me. The first one makes some sense, as no OpenCL GPU is detected. But, SETI has CUDA apps, AFAIK. And the second statement makes no sense at all.

Even more confusing is that I see BOINC requesting new tasks for "NVIDIA", though I haven't received any. The previous errors could be completely normal *if* I got some tasks; seems like it wants to work despite them.

I tried changing to the latest driver, which supports my GTX 280, so that's a nice improvement, but that didn't help SETI at all. I did try installing ocl-icd first, which did NOT help and did NOT allow BOINC to detect an OpenCL-capable GPU. I cannot install ocl-icd now, however, as that conflicts with the nvidia-ocl-icd. clinfo gives error -30, which explains why BOINC can't find an OpenCL GPU, although the icd library is installed with the nvidia-ocl-icd pkg, which is all I can do.

Last Poster, Rostislav, can you tell why SETI will not run even when you have OpenCL GPU detected?
____________

Porcelain Mouse
Send message
Joined: 17 May 99
Posts: 21
Credit: 18,092,357
RAC: 25,104
United States
Message 1519437 - Posted: 21 May 2014, 21:55:57 UTC

Bump. Does anyone have any ideas? I'm at an impasse.

My system is requesting CUDA work, but doesn't get any. That correlates with the upgrade to 14.04 XUbuntu. I checked the news page and the CUDA FAQ (which is very out-of-date, right?) and I don't see anything about CUDA wu stopping. I have no idea why I'm not getting GPU work for the detected GPU.

Also, I still don't know why OpenCL device isn't detected. I suppose that's not just a problem for SETI, though. I'll check with Ubuntu, but OP had this symptom also, and that hasn't been addressed yet. Only suggestion to install ocl-icd-libopencl1 package is confusing as this pkg conflicts with nvidia-opencl-icd.
____________

Profile Zalster
Volunteer tester
Send message
Joined: 27 May 99
Posts: 415
Credit: 22,987,787
RAC: 151,928
United States
Message 1519443 - Posted: 21 May 2014, 22:07:38 UTC - in response to Message 1519437.

Procelain,

Try posting over in Number crunching in the message boards. That gets more traffic than this area does. I know there has been a lot of talk about the different drivers and updates. Might give them a try over there.


Zalster

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2568
Credit: 5,872,954
RAC: 2,656
Bulgaria
Message 1519585 - Posted: 22 May 2014, 2:58:01 UTC - in response to Message 1519437.
Last modified: 22 May 2014, 3:15:40 UTC


When you ask questions it is better to post your startup log (as OP) - this gives the tech people more info than rephrasing with own words


You can't expect to get CUDA work from SETI on Linux as there is no such stock app:
http://setiathome.berkeley.edu/apps.php

(there are Linux apps:
- for AstroPulse OpenCL on ATI and NVIDIA GPUs
- for SETI@home v7 OpenCL on ATI
)


BOINC keeps asking for (non-existent) CUDA work/app ~once a day because the project may some day supply CUDA stock app


Note:
If BOINC detects CUDA there is a way to run SETI@home v7 CUDA app/tasks on Linux by manually installing third-party apps:
http://setiathome.berkeley.edu/forum_thread.php?id=74031&postid=1475186#1475186
http://setiathome.berkeley.edu/forum_thread.php?id=74153&postid=1487416#1487416
(and continue reading a few of my next posts in the above link)


BOINC GPU Detection in Linux:
http://setiathome.berkeley.edu/forum_thread.php?id=74746

(I'm not a Linux guy, read for yourself if the above is relevant (only if you have problem with BOINC GPU Detection))


In the past you used third-party apps / anonymous platform / app_info.xml
http://boinc.berkeley.edu/wiki/anonymous_platform
http://setiathome.berkeley.edu/host_app_versions.php?hostid=5167888

Visible as:
'SETI@home Enhanced (anonymous platform, NVIDIA GPU)' == CUDA app
'AstroPulse v6 (anonymous platform, NVIDIA GPU)' == OpenCL app


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Porcelain Mouse
Send message
Joined: 17 May 99
Posts: 21
Credit: 18,092,357
RAC: 25,104
United States
Message 1519633 - Posted: 22 May 2014, 5:35:33 UTC

Thanks all.

It was helpful to be reminded that CUDA Linux apps do not exist, officially.
As BilBg noted, I have used thrid-party apps, but I stopped well before this current problem. It became difficult to manage. It has it's advantages, though, and I guess this is another case where it would help me. Obviously, it's a lot more work to switch back, so I'd rather not. But, that's probably why I didn't realize CUDA shouldn't work for me now.

Best I can tell, the nVidia drivers have experienced the same problem as the ATi drivers did, recently, which was/still is a nightmare on my ATi machine.

This says that drivers before 331.49 should work:
https://boinc.berkeley.edu/dev/forum_thread.php?id=9162

But I'm using 331.38.

This says all the nVidia drivers are fine, but opencl is messed up:
https://devtalk.nvidia.com/default/topic/734098/linux/-boinc-ubuntu-nvidia-no-usable-gpus-found-/

That sounds right to me, but, AFAICT, my ICD vendor file exists and specifies the nvidia opencl library. However, clinfo finds a different library and doesn't like it. So, I'm still in the same predicament.

I'll try number crunching or maybe my distro. It's clear the drivers aren't working right before BOINC starts.

Thanks.
____________

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2568
Credit: 5,872,954
RAC: 2,656
Bulgaria
Message 1519844 - Posted: 22 May 2014, 17:05:59 UTC - in response to Message 1519633.

You can test the functionality of OpenCL by LuxMark
http://setiathome.berkeley.edu/forum_thread.php?id=74710&postid=1513143#1513143
____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Porcelain Mouse
Send message
Joined: 17 May 99
Posts: 21
Credit: 18,092,357
RAC: 25,104
United States
Message 1522600 - Posted: 30 May 2014, 5:13:03 UTC

I think this is the relevant upstream bug:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362

LuxMark sounds neat and cool and it would be fun to play with on my CrossFire system, but I don't see how it will help here. clinfo gives an error, which is all I need to know, I think. If LuxMark has diagnostic capabilities, that would be different.
____________

Porcelain Mouse
Send message
Joined: 17 May 99
Posts: 21
Credit: 18,092,357
RAC: 25,104
United States
Message 1524372 - Posted: 4 Jun 2014, 10:16:15 UTC

Turns out driver version 304 does work, at least it does now.

I was using 304 before upgrade to Ubuntu 14.04. After the upgrade, I checked and it was still set to use the proprietary nVidia driver v304. So, I figured it would hurt to try a different version. But, I never got v331 to work.

I just tried v304 (updates) again and now it works. It's possible they fixed it, it's possible the -updates version would have worked the whole time. Not sure.

hope this helps others.


Post to thread

Questions and Answers : GPU applications : BOINC not using CUDA after upgrade to Ubuntu 14.04

Copyright © 2014 University of California