Message boards :
Number crunching :
V8 CUDA for Linux?
Message board moderation
Previous · 1 . . . 3 · 4 · 5 · 6 · 7 · 8 · 9 . . . 10 · Next
Author | Message |
---|---|
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Previously we found installing nVidia Toolkit 7.5 solved the problem when all else failed, and it really isn't that difficult to install...compared to other solutions. |
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Well I am glad someone jumped in before I got to the chase, cause I came across the same problem with MINT 17.3, but I didnt realize it straight away. See, I was crunching away on Seti Beta, but only getting CUDA tasks, but because of other responsibilities, I didn't get a chance to finally look at it earlier this week. Rebooted the MINT box and yep, no OPENCL recognised, read a few forums and tried a few things, but was going nowhere fast with the limited time I had. Here is what I tried - UBUNTU 15.10. Loaded the OS Updated the OS Added the PPA for NVIDIA Drivers (I have a GTX 960) Installed drivers 361.42 Rebooted Logged back in - Woohoo I have desktop Added the PPA for NVIDIA Modprobe Rebooted Logged back in - Woohoo I still have desktop Added the PPA for BOINC Installed BOINC software but as Juha has mentioned there are more libs to load. Using Synaptic, I installed the following boinc boinc-dev (I am not sure this is needed but just to make sure) boinc-client-opencl (oops installed this but its for the AMD Cards) boinc-client-nvidia boinc-manager boinc-client libboinc7 libboinc-app-dev All dependencies required will be loaded as well. Rebooted just for final measure (some windows habits are hard to quit) Okay, logged back in and yes we still have desktop (unity one, but I installed MATE and use that now) Started up BOINC with fingers crossed, woohoo card is recognised and you beauty both CUDA and OPENCL recognised. Also have just done my daughter PC and I loaded 15.10 then upgraded to 16.05 and then did all the above to that PC as well and now have two UBUNTU machines crunching, both at Seti and Seti Beta. I must admit I have had some headaches as well as triumphs, getting re-acquainted with the command line, what a powerful tool to use. This was my road back to crunching SETI under Linux (NVIDIA Cards) Hope you get to travel the same road soon. Regards Tazzduke (Mark) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
All I've had to do is follow two simple rules; 1) Do Not install BOINC from the Repository, use the Berkeley Installer instead. That covers the first part of Juha's essay. 2) Don't use the Repository driver, download the driver from nVidia instead. That covers the second half of Juha's essay. Using those 2 rules I've been able to run everything from Ubuntu 11.04 with Toolkit 4.2 to Ubuntu 15.10 with driver 361.42. I do have a copy of boincmgr 7.6.12 in my BOINC folder I use with Ubuntu 15.04 and above. I just switch from boincmgr 7.2.33 to 7.6.12 when needed by simply renaming it. Yes, I use the Same BOINC folder in Four different systems by just copying the folder from one partition to the other, you can do that when you use the Berkeley Installer. The trip down to Ubuntu 11.04 was very successful, producing the CUDA 4.2 App that still works very well in Ubuntu 15.10 with my 750Ti. BTW tazz, I ran across your Hackintosh in my Inconclusive list the other day. It would probably work if you used 10.11.3 instead of 10.11.4. Two Hacks I know of seemed to work fine with 11.3, one of them has the same problem as yours with 11.4, the other one I've only seen run CUDA with 11.4. They both work better with the Mac CUDA App verses the OpenCL App. |
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Greetings TBar Thanks for the info, that was not an easy thing to do, but it was case of seeing if I could do it. Turns out to a degree I did. I still have it loaded on the HDD (EL Capitan though) but it is no longer in my daughters PC as that now has Ubuntu 16.04 on it and will be there for awhile. I shall be sticking with 1 x WIN 7 and 2 x UBUNTU machines for the long run. There was one element that was missing with the OSX desktop, no GPU fan control, and around here during summer, to be able to manually adjust your GPU fans is essential, that is the only thing that keeps me from running it again. Regards Tazzduke |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
1) Do Not install BOINC from the Repository, use the Berkeley Installer instead. This has the problem that then you are stuck with 7.2.42 and it's bugs and issues. The two biggest issues that came to mind are the problematic OpenCL detection and not always accounting memory usage of VBox tasks correctly. The latter might not be a problem for you but it is for anyone wanting to run ATLAS@Home. You don't see (I think) the problem with OpenCL detection when you use drivers NVIDIA packaged. Their package includes the libOpenCL.so symlink. AMD's driver package however doesn't. While adding the symlink isn't that hard you need to add it in right directory. When helping people I find it tiring to always having to check which directory the driver package this time is using. The Berkeley package does make it easier to poke BOINC's files, I'll give you that. 2) Don't use the Repository driver, download the driver from nVidia instead. To me it seems that people want an easy way to install BOINC and drivers on their systems. And for a good reason. I mean, every time someone asks if Linux is any good he or she will be told Linux is just as easy as Windows and installing software is ever easier with a package manager. The way NVIDIA's driver package is installed is pretty awful compared to clicking a couple of buttons in a GUI tool. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Yes, I believe I mentioned the problem with OpenCL detection with the ATI drivers quite some time ago, Posted: 2 Apr 2014 Yes, it's been that way for that freaking long. That hasn't been a problem for me for almost as long as my ATI cards are stuck at Driver 14.6. I tried the newer drivers for a while and None were better, now they don't make drivers for those cards anymore. It really isn't that hard for the ATI cards as it's usually just that One link. The nVidia cards are a different matter. I have wasted Hours trying to get the Repository 352 driver to see OpenCL after Finally getting it to see CUDA. I don't have that problem with the recent drivers downloaded from nVidia. Of course, that's when using the Berkeley BOINC install, for those using the Repository BOINC it appears to be worse. Well, I don't use ATLAS@Home or VBox, so, not a problem...for me. My question is if there is Ever going to be an Updated Berkeley copy of BOINC. I've tried 7.4.25 and it doesn't work correctly. The Manager doesn't update without running the pointer across the screen. The other versions I've seen on the Web appear to have been compiled to be installed by the Repository verses placed in the Home folder. I suppose I could try compiling my own version, but it would be nice to just download a recent version from Berkeley. |
Al Send message Joined: 3 Apr 99 Posts: 1682 Credit: 477,343,364 RAC: 482 |
To me it seems that people want an easy way to install BOINC and drivers on their systems. And for a good reason. I mean, every time someone asks if Linux is any good he or she will be told Linux is just as easy as Windows and installing software is ever easier with a package manager. The way NVIDIA's driver package is installed is pretty awful compared to clicking a couple of buttons in a GUI tool. OMG, a truer statement has never been spoken! I have been trying to understand how to install the latest driver on Dostch's setup that I am playing with. I know that it is an older version, and I am trying to install the latest driver, but man, with windoze, it's double click to run it, and away you go. With this thing, you try that, it looks at you and says, "Umm, yeah? OK, what program do you want to use to do that with? What do you mean you DON'T KNOW?? COME ON!!" Obviously I don't know what I am doing, but I thought that it wasn't going to be _that_ hard. Turns out not so much. Is it the version, or is it Linux? Does it _have_ to be this hard? Or am I just that slow? If it hasn't gotten any better since I tried this the first time back in 2010, then no wonder that it is still a 1% OS. I really want to like it, but maybe I am just too brain locked into Windows to allow me to get my head around it, which is a bummer. I have the impression/assumption that it is a more efficient OS, lighter weight with less 'crap' going on the background, hence it would possibly be a better OS for crunching for that reason. Not sure that is necessarily true or not, it's just an assumption I am making. Am I missing something? |
Iztok s52d (and friends) Send message Joined: 12 Jan 01 Posts: 136 Credit: 393,469,375 RAC: 116 |
Am I missing something? Simple: in linux, you can do same thing in many different ways. Choice has a price: understanding options. like with telephones: years ago you just got one black model. Now you have to decide on brand, OS, technology (IS-95, LTE etc), cathegories (LTE-Advanced? Can it do MIMO 4 by 4?) etc etc.... Anyhow, for me seti is quite simple, on slackware. as root: sh NVIDIA-Linux-x86_64-361.28.run (also, disable nouveau driver for new installations) as user boinc: all boinc/seti stuff including app_info.xml in /etc/rc.d/rc.local: nvidia-smi sleep 1 echo "boinc/dobo >/dev/null 2>&1 &" |su - boinc and seti works even if X11 is not started on this PC. nvidia-smi loads proper modules. 73 Iztok |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
Wow :) :-) |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
[quote] I don't have any rc.d in /etc I have a list of rc0.d to rc6.d + rcS.d but no rc.local file |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
Previously we found installing nVidia Toolkit 7.5 solved the problem when all else failed, and it really isn't that difficult to install...compared to other solutions. Ok, I'm going to install it from here: https://developer.nvidia.com/cuda-downloads |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
Previously we found installing nVidia Toolkit 7.5 solved the problem when all else failed, and it really isn't that difficult to install...compared to other solutions. Here we go! cuda-repo-ubuntu1404-7-5-local_7.5-18_amd64.deb Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1404-7-5-local_7.5-18_amd64.deb` `sudo apt-get update` `sudo apt-get install cuda` 1) impossible to install cuda (some dependecies) so ... 2) I have changed repository driver, from 340 to 352.63 (recommended) and now "sudo apt-get install cuda" works. Reboot ...and now: ven 22 apr 2016 17:08:32 CEST | | CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version unknown, CUDA version 7.5, compute capability 5.0, 2047MB, 1839MB available, 2208 GFLOPS peak) So, summarizing ... 1) boinc from repository, 2) driver from repository but 3) nVidia Toolkit 7.5 from here: https://developer.nvidia.com/cuda-toolkit Edit: Now I have installed "SETIv8_Linux_CUDA42" and I get: ven 22 apr 2016 17:55:45 CEST | | App version needs OpenCL but GPU doesn't support it so ..."the never ending story" :-( |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
Now I have installed "SETIv8_Linux_CUDA42" and I get: Just for info: in my system if I look for nvidia-opencl* in synaptic I find nvidia-opencl-icd-352 (version 352.63-0ubuntu0.14.04.1) and nvidia-libopencl1-352 (version 352.63-0ubuntu0.14.04.1) In any case "SETI@home v8 Anonymous platform (NVIDIA GPU)" now are running. Host ID is 7978786, if someone wants to veryify results. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
It seems you are still caught up in all those items from the Repository that I DON'T USE. All that is necessary to install to get CUDA working in Ubuntu is to Install Ubuntu, Install the Berkeley version of BOINC and it's Dependencies, and install the nVidia driver from nVidia. You don't need that boinc-nvidia-cuda from the Repository that I'm looking at in the Package Manager right now. It's Not installed on My system and My system works. I have the Package Manager open with CUDA in the filter box and None of those Packages are installed on my system. When I want to Compile a CUDA App, I install the Toolkit FROM nVidia which I installed on this current system a little over a week ago. This system had been working for months before that with just the Berkeley BOINC 7.2.33 and the driver from nVidia, nothing from the Repository was installed except the Dependencies for the Apps in the Berkeley version of BOINC. I also use the .run versions of the nVidia installers, not the .deb versions. It seems as though you may have the Repository versions working Finally. That Error; "App version needs OpenCL but GPU doesn't support it", the "App version" they are talking about is referring to your app_info.xml. The "needs OpenCL but GPU doesn't support it" means you don't have OpenCL to work with the AP section, probably because you are using the Repository driver instead of the nVidia driver. You have been told the Repository driver doesn't work with OpenCL at least a couple of times. If you were to install the NVIDIA driver from nVidia then OpenCL would probably work. It seems your GTX 750Ti times are just as slow as your other CUDA cards. It should be MUCH faster than it is running. My only guess is it's related to all the items from the Repository you have installed. I only have the Berkeley BOINC and the nVidia driver installed on my normal systems. |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Ubuntu repository developed Windows style driver bloat ? lol. "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. |
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Greetings All I have found the following to work for my two machines with no hiccups, but then I have just upgraded two machines from 15.10 to 16.04 LTS. I have been getting the drivers from the following place https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa I have been getting the BOINC from the following place https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc But then again this maybe nought as the OP is trying to get his MINT 17 system crunching which is based off 14.04 LTS. Wishing you all the best. Tazzduke |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
It seems your GTX 750Ti times are just as slow as your other CUDA cards. It should be MUCH faster than it is running. My only guess is it's related to all the items from the Repository you have installed. I only have the Berkeley BOINC and the nVidia driver installed on my normal systems. I will investigate on GTX 750ti times. In this moment I see that CPU job is faster (roughly +76%). Here a pivot table. I remember that it is possible to run 2 (or more) tasks on GPU. I don't remember how. Something in some config file? Can someone refresh my mind? |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Checkout my new system, Sat 23 Apr 2016 04:27:30 AM EDT | | Starting BOINC client version 7.2.33 for x86_64-pc-linux-gnu After creating the Startup Disk, it took me about 45 minutes to install Mint and have it running CUDA tasks. Since Ubuntu 16.04 is out I just installed Mint over the Ubuntu 15.10 partition, I will install 16.04 over Mint later. This is what I mean by Slow, this is your 750Ti; https://setiathome.berkeley.edu/result.php?resultid=4877049628 WU true angle range is : .416908 Run time: 53 min 41 sec CPU time: 2 min 19 sec This is my 750Ti running the cuda42 App; https://setiweb.ssl.berkeley.edu/beta/result.php?resultid=23561035 WU true angle range is : 0.429288 Run time: 11 min 20 sec CPU time: 11 min 17 sec As you can see there is a Major problem with Your Host and simply having it run another task isn't going to fix it. All I did was Install Mint, Install nVidia driver 361.42, then drag the BOINC folder from the Ubuntu 14.04 partition to the Mint partition. I did have to install curl4 and libwx, and that was it. Nothing else was installed. I'm currently running the "Special" App and it's about twice as fast as the cuda42 App, but, look how well my brand new install is working compared to yours; https://setiathome.berkeley.edu/results.php?hostid=7258715&offset=120 As I said earlier, I don't know why your machines are running so slowly, but, you may want to consider trying to fix whatever is wrong before you go much further. |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
may be my 750ti is working slow |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
If you eliminate what it can't be, you will find what it must be. ALL of your GPUs are running at least Twice as slow as they should. Other people run the same OS and don't have the problem. Other people run the same GPU drivers and don't have the problem. That leaves what you are installing from the Repository, obviously something you're installing isn't working. It appears you are installing the same Repository files on All your Hosts. I would suggest trying what I did, install a new system on a spare drive/partition and then install just the nVidia driver, and the Berkeley BOINC. You can find BOINC here, http://boinc.berkeley.edu/dev/forum_thread.php?id=8378&postid=51551#51551 Install the new system with the same PC name as the existing system. Install BOINC in your Home folder then track down your existing BOINC files in the old system and move them to the New BOINC in the new system. Find the old setiathome.berkeley.edu folder and place it in the new BOINC/projects folder. You might want to run down the tasks first....just in case you don't get it right the first time. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.