Message boards : Questions and problems : BOINC WU on LinuxMint with NVIDIA GPU
Message board moderation
Previous · 1 · 2 · 3 · 4 · Next
Author | Message |
---|---|
Send message Joined: 5 Oct 06 Posts: 5125 |
I doubt you'll ever get any GPU tasks from Milkyway. Their applications page indicates that their applications require support for the OpenCL programming language, and your message log implies that BOINC hasn't detected OpenCL support in your NVidia drivers. Roland might have some ideas on that, but if you are satisfied by running GPU projects with CUDA applications, I'd suggest you rest on your laurels before embarking on another round of driver updates. |
Send message Joined: 28 Apr 13 Posts: 42 |
Richard - Sorry to bust your bubble, but Milkyway and Collatz are both downloading WUs now. I have them both set to 0.25C + 0.5NV. The GPUs can't handle .25NV, but that is ok. They are working fine at .5NV. With Collatz crashing perodically, I've set both Projects to download. I won't need to mess with this PC again unless it stops crunching. |
Send message Joined: 5 Oct 06 Posts: 5125 |
Richard - Sorry to bust your bubble, but Milkyway and Collatz are both downloading WUs now. I have them both set to 0.25C + 0.5NV. Don't worry about bursting my bubble - I have grave doubts about MilkyWay's ability to comprehend and manage the plan_class facility, so it doesn't really surprise me that their 'opencl_nvidia' or 'opencl_nvidia_101' plan classes don't do what they say on the tin. I had a long discussion with them while they were trying to develop their multi-threaded CPU application (nbody), culminating in the revelation When I started releasing the format was to use gpu classes and I kept the convention. Since the idea is to get a gpu version of nbody out I thought it was a place holder for turning on that option. My comment was more of a warning not to be too concerned if your machine continued to suck on empty from that project - but if it works, that's great. Given the level of project support, it might have been a long slog tracking down any remaining problems. |
Send message Joined: 29 Aug 05 Posts: 15558 |
I think that the lucky deduction that projects can make is: when the GPU is Nvidia and it has CUDA detected, it can automatically do OpenCL 1.0 at the minimum. All CUDA capable GPUs can do OpenCL 1.0, a few can do OpenCL 1.1, none can do any better because Nvidia stopped developing OpenCL. As opposed to AMD and Intel GPUs, where you're required to have had some detection of capabilities. |
Send message Joined: 7 Mar 12 Posts: 67 |
Glad it is all working for you. Sometimes they just have to chew on things a while before they decide to let you have work. |
Send message Joined: 28 Apr 13 Posts: 42 |
Roland - on my other Linux PC that still is running LM 64-bit, I tried your sudo apt-get install nvidia-modprobe The result was... gandalf@MiddleEarth ~ $ sudo apt-get install nvidia-modprobe [sudo] password for gandalf: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package nvidia-modprobe What am I missing? |
Send message Joined: 7 Mar 12 Posts: 67 |
You CANNOT SKIP STEPS. Every step from the beginning. ++++ Want to know the only steps different to make your current 64-bit system work? After rebooting so nvidia-331 takes full effect. Click on the little blue start button in the lower left corner. In the little search bar at the top type "sour" and you should see an option for "Software Sources" appear. Click it. Click the "Additional repositories" button on left. Click the "Add a new repository" button at bottom. paste in the following: deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse Click "Ok" Click the "update" or "refresh" button on upper right side of screen. (This will be greyed out with "No action required" until you actually add something and I don't remember what the text chagnes to.) Exit out of all windows. Click on the little blue start button in the lower left corner. Applications->System->Synaptic Package Manager Enter password when prompted. After the index finishes updating type "modpro" in the "Quick filter" field Mark nvidia-modprobe for installation, then click "Apply changes" Exit everything and reboot Open your BOINC manager. Click Advanced->Event Log Scroll to top of log (it always shows last entry when it opens) You should see something like: Tue 10 Mar 2015 06:35:09 AM CDT | | CUDA: NVIDIA GPU 0: GeForce GT 630 (driver version unknown, CUDA version 6.0, compute capability 3.5, 2047MB, 1973MB available, 692 GFLOPS peak) near the beginning. ------------------- You skipped past the very beginning of this and did not add the repository. |
Send message Joined: 7 Mar 12 Posts: 67 |
First NVidia crash some time during wee hours of morning on 64-bit machine. In all fairness though, I had streamed 2 episodes of "Person of Interest" AND watched 2 DVDs without shutting down BOINC. Came out this morning and saw the tell-tale signs with a flashing caps lock and scroll lock on keyboard. Reset button time. With regular use it appears the 331 driver with the modprobe manages to run about a week before it gives up the ghost. |
Send message Joined: 28 Apr 13 Posts: 42 |
Roland - Could not find a ... Click on the little blue start button in the lower left corner. Was able to work around this instruction. I suspect this guide was written for other than LinuxMint. Knock on wood, it will still work. Will keep you advised. |
Send message Joined: 28 Apr 13 Posts: 42 |
Sat 14 Mar 2015 08:15:41 AM PDT | | log flags: file_xfer, sched_ops, task, sched_op_debug Sat 14 Mar 2015 08:15:41 AM PDT | | Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3 Sat 14 Mar 2015 08:15:41 AM PDT | | Data directory: /var/lib/boinc-client Sat 14 Mar 2015 08:15:41 AM PDT | | CUDA: NVIDIA GPU 0: GeForce GTX 650 (driver version unknown, CUDA version 6.0, compute capability 3.0, 1023MB, 887MB available, 813 GFLOPS peak) Sat 14 Mar 2015 08:15:41 AM PDT | | CUDA: NVIDIA GPU 1: GeForce GTX 650 (driver version unknown, CUDA version 6.0, compute capability 3.0, 1024MB, 1004MB available, 813 GFLOPS peak)
|
Send message Joined: 28 Apr 13 Posts: 42 |
FYI - Upon running Boinc Manager, Collatz is running. Milkyway downloaded WUs, then aborted them. I have since deactivated the Milkyway Project. |
Send message Joined: 20 Nov 12 Posts: 801 |
Milkyway downloaded WUs, then aborted them. Exit status 201 (0xc9) EXIT_MISSING_COPROC You need to get BOINC to detect OpenCL support. Run the command that matches your OS: 64-bit: cd /usr/lib/x86_64-linux-gnu/ && sudo ln -s libOpenCL.so.1 libOpenCL.so 32-bit: cd /usr/lib/i386-linux-gnu/ && sudo ln -s libOpenCL.so.1 libOpenCL.so And then restart BOINC. |
Send message Joined: 5 Oct 06 Posts: 5125 |
The mystery, then, is why the tasks were allocated and downloaded in the first place. I've always thought that there's something strange about Milkyway's scheduler. |
Send message Joined: 28 Apr 13 Posts: 42 |
This one is a 64-bit... gandalf@MiddleEarth ~ $ cd /usr/lib/x86_64-linux-gnu/ && sudo ln -s libOpenCL.so.1 libOpenCL.so [sudo] password for gandalf: ln: failed to create symbolic link ‘libOpenCL.so’: File exists |
Send message Joined: 20 Nov 12 Posts: 801 |
Your previous post did have a very plausible sounding explanation. Milkyway's opencl_nvidia* plan classes could be set to only check for CUDA but the app_version may still require OpenCL coproc. Too bad we can't see how they, or any other project, have set up the plan classes. |
Send message Joined: 20 Nov 12 Posts: 801 |
This one is a 64-bit... And BOINC still doesn't detect OpenCL? That's new. Enable <coproc_debug> log flag in cc_config.xml (in /var/lib/boinc-client), restart BOINC and then post the start-up messages. |
Send message Joined: 7 Mar 12 Posts: 67 |
You may actually have to install that Boinc_app_milkyway package you had before. I don't subscribe to this project so I don't know. I do humbly suggest you open a question on the forum/support board for the milkyway project asking them about getting things working with NVidia under 64-bit Mint. You have other projects pulling down WUs and completing so not the issue is specific to that project. Btw, my instructions were all for Mint 17 KDE. I make it a point not to run any of the Gicky-Gnasty-Gnome desktops unless I'm forced at gunpoint <Grin> |
Send message Joined: 7 Mar 12 Posts: 67 |
Gandalf, If you want to be able to go away for a long weekend and believe your systems are happily processing WU, you probably need to drop them all back to 32-bit. I just had yet another NVidia crash this morning on my 64-bit machine. |
Send message Joined: 7 Mar 12 Posts: 67 |
@Gandalf, Have you solved the problem? I have been having a rash of Nvidia crashes. In a few days when the disks show up I'm going to experiment with different distros. The YAU stuff doesn't seem to be testing 64-bit again. Will be looking at: Chakra http://chakraos.org/forum/ RoboLinux http://www.robolinux.org/about/ Linux Lite https://www.linuxliteos.com/ I really don't want to give up my RAM and drop back to 32-bit on this machine. |
Send message Joined: 28 Apr 13 Posts: 42 |
I've decided to stay with Collatz and increase the Minimum work buffer to 10.0 days and the Max additional work buffer to 4.00 days. I'm hoping that when the Collatz crashes again that this setting will provide enough work until the Callatz comes back on line. Time will tell. My 32-bit PC froze and T/S showed a fan on the heat sink had dies. Have left the PC powered down until I can replace the fan. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.