Thread 'Problem install Nvidia and Ubuntu 16.04.1 + Boinc 7.6.31 (x64 )'

Author	Message
Agentb Send message Joined: 30 May 15 Posts: 265	Message 73868 - Posted: 7 Nov 2016, 20:22:43 UTC Ritchie wrote: I'm seeing same kind of problems with my fresh installation (Ubuntu 16.04.1 + Boinc 7.6.31 (x64 ) ). My purpose was to try and learn if I could make a Nvidia GPU work with Boinc + Linux. I also wanted to try the Boinc Manager for the first time with Ubuntu. I don't know if I was at right track at all, but this way I installed BOINC (after installing Nvidia drivers thru somewhere the Ubuntu Update tabs): "sudo apt-get install boinc-client-nvidia-cuda" and then also "sudo apt-get install boinc-client-opencl" and "sudo apt-get install boinc-client-fglrx" and "sudo apt-get install boinc-manager". Now this Boinc GUI keeps acting like a joke. No matter how I set the three different activity settings they keep living their own life. Another thing is the whole GUI is able to contact the BOINC core only the first time after a reboot. If I exit Manager and start it again, Manager fails to contact Boinc core anymore. Nvidia card was recognized and working okay whatsoever. In response to floyd's message... permissions here look like this: $ ls -al /etc/boinc-client/ total 36 drwxr-xr-x 2 root root 4096 ** . drwxr-xr-x 134 root root 12288 .. -rw-rw-r-- 1 boinc boinc 4672 cc_config.xml -rw-rw-r-- 1 root boinc 1450 global_prefs_override.xml -rw-r----- 1 root boinc 1 gui_rpc_auth.cfg -rw-r--r-- 1 root boinc 296 remote_hosts.cfg (I've just replaced the dates with **). I don't know if those permissions look good. I don't know how to make them look better, if they are wrong at the moment. I'm pretty much a newbie with linux, but have had at least some success with Mint 18 and Ubuntu _without Boinc Manager_. It's just sooo frustraiting to find out how this basic usage with Manager seems right away like a nightmare. Clearly this combination isn't for anybody seeking a friendly experience. Even after BOINC + Ubuntu have been copulating already for years... outcome from that seems to be cursed with whatever syndromes. Luckily I have Windows as a parallel option for this machine. Whoah, now it's easier to breathe again. ID: 73868 ·

Agentb Send message Joined: 30 May 15 Posts: 265	Message 73869 - Posted: 7 Nov 2016, 21:35:00 UTC - in response to Message 73868. Last modified: 7 Nov 2016, 21:58:43 UTC Ritchie wrote: I'm seeing same kind of problems with my fresh installation (Ubuntu 16.04.1 + Boinc 7.6.31 (x64 ) ). My purpose was to try and learn if I could make a Nvidia GPU work with Boinc + Linux. I also wanted to try the Boinc Manager for the first time with Ubuntu. Firstly to be clear the names on Linux the GUI is a boinc manager called boincmgr (there are other options for managing boinc, boinccmd and an app boinctui) and boinc-client is a script for starting and stopping boinc (and reading status and the like) - there is also the more correct systemctl approach to stopping and starting boinc sudo systemctl --no-pager status boinc-client.service sudo systemctl --no-pager stop boinc-client.service sudo systemctl --no-pager start boinc-client.service I don't know if I was at right track at all, but this way I installed BOINC (after installing Nvidia drivers thru somewhere the Ubuntu Update tabs): "sudo apt-get install boinc-client-nvidia-cuda" and then also "sudo apt-get install boinc-client-opencl" and "sudo apt-get install boinc-client-fglrx" and "sudo apt-get install boinc-manager". Some wrong turns here. You have installed a (old) AMD driver fgrlx and I'm not certain of the need to install boinc-client-nvidia-cuda and boinc-client-opencl, kind of depends what gets installed when the graphics are installed. My normal approach is install if not working. I usallyy start with getting card working and with graphics drivers, it's not clear what state the graphics are at now as you have installed from two sources. I'll have to look at how up to date the repos are. The documentation Installing_BOINC_on_Ubuntu shows the correct install process. I'd suggest stopping boinc, remove all the apt-get (documentation describes how) and reinstalling. You might lose some gpu tasks though. Now this Boinc GUI keeps acting like a joke. No matter how I set the three different activity settings they keep living their own life. Another thing is the whole GUI is able to contact the BOINC core only the first time after a reboot. If I exit Manager and start it again, Manager fails to contact Boinc core anymore. In the other post i have mentioned how to use boinccmd to see the true status. When you "exit manager" i think the default action may be to shutdown boinc unless you clear a tick-box. The systemctl status (see above) after exit will show that. example agentb@gluon:~/boinc$ sudo systemctl --no-pager status boinc-client ● boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2016-11-06 11:03:18 GMT; 1 day 10h ago Main PID: 942 (sh) CGroup: /system.slice/boinc-client.service ├─ 942 /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log ├─ 946 /usr/bin/boinc --dir /var/lib/boinc-client ├─26855 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... ├─26946 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... ├─27157 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... └─28928 ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4G_1.52_x86_64-pc-linux-gnu__BRP4G-Beta-opencl-ati -i p20... Nov 06 11:03:18 gluon systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client... Nov 06 11:03:18 gluon systemd[1]: Started Berkeley Open Infrastructure Network Computing Client. this shows boinc and several science tasks running. Nvidia card was recognized and working okay whatsoever. In response to floyd's message... permissions here look like this: $ ls -al /etc/boinc-client/ total 36 drwxr-xr-x 2 root root 4096 ** . drwxr-xr-x 134 root root 12288 .. -rw-rw-r-- 1 boinc boinc 4672 cc_config.xml -rw-rw-r-- 1 root boinc 1450 global_prefs_override.xml -rw-r----- 1 root boinc 1 gui_rpc_auth.cfg -rw-r--r-- 1 root boinc 296 remote_hosts.cfg (I've just replaced the dates with ). I don't know if those permissions look good. I don't know how to make them look better, if they are wrong at the moment. They are fine. i've use the code formatting to make it a bit easier to read, permissions are changed with chmod** and linux forums are better than i at explaining. I'm pretty much a newbie with linux, but have had at least some success with Mint 18 and Ubuntu _without Boinc Manager_. It's just sooo frustraiting to find out how this basic usage with Manager seems right away like a nightmare. Clearly this combination isn't for anybody seeking a friendly experience. Even after BOINC + Ubuntu have been copulating already for years... outcome from that seems to be cursed with whatever syndromes. Luckily I have Windows as a parallel option for this machine. Whoah, now it's easier to breathe again. If you are new to linux, and have never used a command line before it will bite - it's like learning a new language, you will find it frustrating. If you know English, intuitive it is (to English speakers). I can not stress enough for beginners do not start typing commands without understanding what they mean. "man <command>" before "<command>" and spend some time to work through some command line tutorials to learns some basics. hth ID: 73869 ·

Richie Send message Joined: 2 Jul 14 Posts: 186	Message 73872 - Posted: 8 Nov 2016, 3:12:42 UTC - in response to Message 73869. AgentB wrote: Firstly to be clear the names on Linux the GUI is a boinc manager called boincmgr (there are other options for managing boinc, boinccmd and an app boinctui) and boinc-client is a script for starting and stopping boinc (and reading status and the like) - there is also the more correct systemctl approach to stopping and starting boinc sudo systemctl --no-pager status boinc-client.service sudo systemctl --no-pager stop boinc-client.service sudo systemctl --no-pager start boinc-client.service Thank you very much. I hadn't heard of those "systemctl" things at all. I'll try them. I had some couple of years old notes for myself that included lines ./run_client –daemon and sudo /etc/init.d/boinc-client restart but I think those are for situation if Boinc was running as a daemon. I don't remember. AgentB wrote: Some wrong turns here. You have installed a (old) AMD driver fgrlx and I'm not certain of the need to install boinc-client-nvidia-cuda and boinc-client-opencl, kind of depends what gets installed when the graphics are installed. My normal approach is install if not working. Okay. I didn't know that fglrx was for AMD. That one at least I could skip in the future. AgentB wrote: The documentation Installing_BOINC_on_Ubuntu shows the correct install process. I had read that guide and also the separate CUDA section there... https://help.ubuntu.com/community/Cuda ... but I saw there was such an old Nvidia driver mentioned and page edited last time for almost three years ago... so I wasn't sure if that CUDA guide would hold true anymore. I felt lazy and thought "oh my, do I have to go through all those commands". Googled more... and came up with something shorter: https://www.devmanuals.net/install/ubuntu/ubuntu-16-04-LTS-Xenial-Xerus/how-to-install-boinc-client-nvidia-cuda.html "Nice. Much easier to try out" ... so I went with that. Actually when I entered sudo apt-get install boinc-client-nvidia-cuda it said something like "suggested additional packages" and listed boinc-client-fglrx and also boinc-client-opencl if I remember right. Then I installed them also (without understanding the first one was for AMD). AgentB wrote: I'd suggest stopping boinc, remove all the apt-get (documentation describes how) and reinstalling. You might lose some gpu tasks though. I'll do that next time I log in to Linux (later this week). AgentB wrote: In the other post i have mentioned how to use boinccmd to see the true status. When you "exit manager" i think the default action may be to shutdown boinc unless you clear a tick-box. The systemctl status (see above) after exit will show that. example agentb@gluon:~/boinc$ sudo systemctl --no-pager status boinc-client ● boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2016-11-06 11:03:18 GMT; 1 day 10h ago Main PID: 942 (sh) CGroup: /system.slice/boinc-client.service ├─ 942 /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log ├─ 946 /usr/bin/boinc --dir /var/lib/boinc-client ├─26855 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... ├─26946 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... ├─27157 ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1_1.05_x86_64-pc-linux-gnu__FGRPSSE-Beta --inputfile LATeah000... └─28928 ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4G_1.52_x86_64-pc-linux-gnu__BRP4G-Beta-opencl-ati -i p20... Nov 06 11:03:18 gluon systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client... Nov 06 11:03:18 gluon systemd[1]: Started Berkeley Open Infrastructure Network Computing Client. this shows boinc and several science tasks running. --------- If you are new to linux, and have never used a command line before it will bite - it's like learning a new language, you will find it frustrating. If you know English, intuitive it is (to English speakers). I can not stress enough for beginners do not start typing commands without understanding what they mean. "man <command>" before "<command>" and spend some time to work through some command line tutorials to learns some basics. hth Thanks again for all that information you gave. I appreciate really. I haven't gave up with linux for sure, but I'm still learning the basics (only knew a few commands what comes to command line). Originally I was considering to install Ubuntu 16.10, but I wasn't sure at all if that would'd introduced even additional challenges on getting Boinc to see the GPU. I'll practise usage with this LTS version first. ID: 73872 ·

Agentb Send message Joined: 30 May 15 Posts: 265	Message 73887 - Posted: 8 Nov 2016, 20:58:31 UTC - in response to Message 73872. Last modified: 8 Nov 2016, 20:59:28 UTC Thank you very much. I hadn't heard of those "systemctl" things at all. I'll try them. Ei ongelmaa. When ubuntu moved to "systemd" (16.04) systemctl is the command to control the systemd service manager (aka daemons), and boinc as installed by the debian based repos (includes ubuntu) runs under its control. I had some couple of years old notes for myself that included lines ./run_client –daemon and This how the non-repo (install ancient version from boinc website) is started and is not recommended. sudo /etc/init.d/boinc-client restart but I think those are for situation if Boinc was running as a daemon. I don't remember. The systemctl equivalent is sudo systemctl --no-pager restart boinc-client.service They are interchangeable although the systemctl is the future. AgentB wrote: Some wrong turns here. You have installed a (old) AMD driver fgrlx and I'm not certain of the need to install boinc-client-nvidia-cuda and boinc-client-opencl, kind of depends what gets installed when the graphics are installed. My normal approach is install if not working. Okay. I didn't know that fglrx was for AMD. That one at least I could skip in the future. Removing unwanted packages means you don't get useless or damaging updates. https://www.devmanuals.net/install/ubuntu/ubuntu-16-04-LTS-Xenial-Xerus/how-to-install-boinc-client-nvidia-cuda.html "Nice. Much easier to try out" ... so I went with that. Good link up to date. Actually when I entered sudo apt-get install boinc-client-nvidia-cuda it said something like "suggested additional packages" and listed boinc-client-fglrx and also boinc-client-opencl if I remember right. I don't quite believe fglrx but i will test later. Thanks again for all that information you gave. I appreciate really. I haven't gave up with linux for sure, but I'm still learning the basics (only knew a few commands what comes to command line). Originally I was considering to install Ubuntu 16.10, but I wasn't sure at all if that would'd introduced even additional challenges on getting Boinc to see the GPU. I'll practise usage with this LTS version first. Good choice, stick with the LTS releases until you are confident. The .10 releases are less stable, more buggy, and have a very short support life. Kind of crash-test-dummy releases. ID: 73887 ·

Bob Harder Send message Joined: 11 Oct 10 Posts: 13	Message 73969 - Posted: 11 Nov 2016, 11:14:24 UTC I am running BOINC 7.2.42 using UBUNTU 16.04 with a NVIDIA card. Here is what I do starting with a "clean" UBUNTU installation. 1) G0 to the BOINC website and download the BOINC software (boinc_7.2.42_x86_64-pc-linux-gnu.sh) 2) Copy or move it to your home directory 3) Mark it for execution (Permissions) 4) Install BOINC (run the .sh file) 5) Copy run_manager to your Desktop (for convenience) 6) Open the Terminal, navigate to the Desktop, and run (start) BOINC (run_manager) 7) Check for errors (missing libraries) and correct any missing 8) Using apt-get or Synaptic install nvidia-361 9) When you start BOINC, check the Event Log to make sure there are two lines that indicate CUDA and Opencl were recognized. You should be good to go. Maybe this is the answer to a different question than is being addressed in this thread. ID: 73969 ·

ChristianB Volunteer developer Volunteer tester Send message Joined: 4 Jul 12 Posts: 321	Message 73973 - Posted: 11 Nov 2016, 12:47:33 UTC Bob: Your way might work but it has the serious flaw that BOINC is only running when you are logged in and also have started the BOINC Manager until then your computer is idle. You would also need to update this by hand where in contrast a package install would be automatically started at boot time and automatically be up to date (when using the correct repository). The Problem with GPUs is that you need to install extra packages (which are taken care of by boinc-client-nvidia-cuda). Also installing nvidia-361 might not be the best choice for everyone as nvidia dropped support of older cars in newer Linux drivers. ID: 73973 ·

Bob Harder Send message Joined: 11 Oct 10 Posts: 13	Message 73976 - Posted: 11 Nov 2016, 16:02:16 UTC - in response to Message 73973. Last modified: 11 Nov 2016, 16:03:33 UTC ChristianB - If my computer is turned on, I am always logged-in so that was never an issue for me. I have the run_manager in my UBUNTU Startup Application list. The BOINC Manager starts when I turn on my computer and automatically login. The boinc-client-nvidia-cuda that I never used is probably why I have that step about the missing libraries. That would make the installation process easier than trying to figure out what packages are missing. I will try that next time. I should have written "nvidia-361 or whatever driver version you want to use". Thanks for the comments. ID: 73976 ·

Agentb Send message Joined: 30 May 15 Posts: 265	Message 73985 - Posted: 11 Nov 2016, 20:20:00 UTC - in response to Message 73969. I am running BOINC 7.2.42 using UBUNTU 16.04 with a NVIDIA card. Maybe this is the answer to a different question than is being addressed in this thread. Doing it this way - Use an old (more bugs) version. - Especially inherit a number of GPU detection bugs resolved around 7.6.32 - Never receive updates in the normal manner, keeping you system up to date. - Share your personal files with boinc and all the science applications. The correct install separates boinc and all the science applications to run as a user=boinc. There is a risk a bad application could delete files, and if user=boinc it should not be able to access user=you. - Unable to autostart on power up. A lot of work goes into getting repository installs correct and in the Debian family of Linux always look to the repos for software. ID: 73985 ·

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.