Advanced search

Message boards : Number crunching : Discussion of Ubuntu 16.04-x64 LTS installation and configuration

Author Message
Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 43504 - Posted: 23 May 2016 | 14:17:08 UTC
Last modified: 23 May 2016 | 14:18:09 UTC

This thread is to allow discussion of the following (locked) FAQ thread,

How to - install Ubuntu 16.04 x64 Linux & setup for GPUGrid

Post here about Ubuntu 16.04-x64 LTS installation and configuration.
Create a new thread for other distros, please.
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Profile Beyond
Avatar
Send message
Joined: 23 Nov 08
Posts: 1073
Credit: 4,497,101,754
RAC: 415,156
Level
Arg
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 43505 - Posted: 23 May 2016 | 14:20:33 UTC - in response to Message 43504.

This thread is to allow discussion of the following (locked) FAQ thread,

How to - install Ubuntu 16.04 x64 Linux & setup for GPUGrid

Post here about Ubuntu 16.04-x64 LTS installation and configuration.
Create a new thread for other distros, please.

Thank you VERY MUCH for doing this guide! It's greatly appreciated!

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 43506 - Posted: 23 May 2016 | 15:04:32 UTC - in response to Message 43505.

You are welcome and I hope you find it useful.

Feedback, experiences and discussion would be appreciated.
Will update the FAQ with any augmentations/corrections as needed.
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

klepel
Send message
Joined: 23 Dec 09
Posts: 137
Credit: 1,831,311,978
RAC: 1,398,012
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 43955 - Posted: 13 Jul 2016 | 22:39:45 UTC

I think, this is the more appropriate thread for the discussion I started over in COOLBITS as LUBUNTU and LINUX MINT are UBUNTU derivates.

My computer with the LUBUNTU 16.04 64-bit installation runs great for over 2 weeks now.

I installed LINUX MINT 18 64-bit on the computer with LINUX MINT 17.3 32-bit previously. Beside that the video card is too old to run GPUGRID, everything works very smooth.

So, I would like to say, that it is quite easy to use Linux for crunching with Nvidia GPUs since the UBUNTU 16.04 LTS release.

KSUMatt
Avatar
Send message
Joined: 11 Jan 13
Posts: 214
Credit: 831,004,493
RAC: 0
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44015 - Posted: 18 Jul 2016 | 21:47:05 UTC

THANK YOU so much for doing this.

Would you recommend a USB 3.0 drive, or is a 2.0 drive sufficient?

klepel
Send message
Joined: 23 Dec 09
Posts: 137
Credit: 1,831,311,978
RAC: 1,398,012
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 44017 - Posted: 19 Jul 2016 | 3:50:14 UTC

If you use the USB-stick for installation on a Hard Disk it is not so important if you use USB 2.0 or 3.0, although the latter is noticeable faster during installation or running LINUX from the USB-stick (The start-up process is much slower on the USB 2.0).

However I do recommend that you use an USB-stick of at least 16 GB for installation only and 32 GB if you like to run LINUX Mint from the stick itself. The best thing is to use a spare/cheap one, as I have burned several in the process, but I am not a computer or Linux specialist at all.

I always used Multiboot Yumi http://www.pendrivelinux.com/yumi-multiboot-usb-creator for the primary installation and then installed the LINUX Distro to second destination from there to either USB-stick or the Hard Disk.

KSUMatt
Avatar
Send message
Joined: 11 Jan 13
Posts: 214
Credit: 831,004,493
RAC: 0
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44028 - Posted: 21 Jul 2016 | 16:40:43 UTC - in response to Message 44017.
Last modified: 21 Jul 2016 | 17:25:49 UTC

If you use the USB-stick for installation on a Hard Disk it is not so important if you use USB 2.0 or 3.0, although the latter is noticeable faster during installation or running LINUX from the USB-stick (The start-up process is much slower on the USB 2.0).

However I do recommend that you use an USB-stick of at least 16 GB for installation only and 32 GB if you like to run LINUX Mint from the stick itself.


I have a 32GB USB 3.0 stick to which I was hoping to install Linux. Not run as a live distro (I'm assuming one cannot create, edit, and save persistent files within a live copy - is this incorrect?) or install from, but install Linux to the stick such that when the stick is plugged in, I will have a fully installed copy of Ubuntu, but when the stick is not plugged in, the PC will boot to Windows as normal from the internal drive.

After reading through skgiven's How To, I'm not sure whether this is the scenario in mind or not.

EDIT: I've tried twice to get Ubuntu up and running using UUI and also Rufus (as recommended on Ubuntu's site). Both times have resulted in absolutely nothing happening after the initial Install/Live selection screen. I would just get 20 minutes of black screen and the indicator light on the USB would not be flashing either. After 20 minutes I gave up - figured something should have loaded by then if it was working as it should. I hope I'm doing something wrong, but can't figure out what it would be.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 44030 - Posted: 22 Jul 2016 | 10:45:22 UTC - in response to Message 44028.

My intention was to cover a basic/standard installation to an internal drive, rather than an external USB stick to create a multi-boot environment.
Overall, I found the OS and NV driver installations very easy but that might not be the case if you need to multi-boot &/or boot to a USB stick.

In your case I don't know what's going wrong, but you may need to select the drive you are booting to when you restart or remove the other USB drive (assuming you are installing the OS from one USB stick onto the other)?
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

KSUMatt
Avatar
Send message
Joined: 11 Jan 13
Posts: 214
Credit: 831,004,493
RAC: 0
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44041 - Posted: 24 Jul 2016 | 22:38:49 UTC - in response to Message 44030.

My intention was to cover a basic/standard installation to an internal drive, rather than an external USB stick to create a multi-boot environment.
Overall, I found the OS and NV driver installations very easy but that might not be the case if you need to multi-boot &/or boot to a USB stick.

In your case I don't know what's going wrong, but you may need to select the drive you are booting to when you restart or remove the other USB drive (assuming you are installing the OS from one USB stick onto the other)?


I tried both the "Install" option and the Live session option, both just went to black screen immediately afterward.

When I saw your install instructions and you had us using USB sticks rather than optical discs I just assumed we were actually installing Linux TO the USB rather than just using it load the image for install to an internal drive.

I'd rather not set-up a dual boot situation due to bad past experiences, but I have an extra SSD I could swap in for the Linux install. Never tried it, but I'm assuming that unplugging the Windows drive and replacing it with a drive on which I would then install Linux would allow me to just switch which SATA cable I have plugged in to switch OS (and files, etc.).

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44103 - Posted: 8 Aug 2016 | 21:23:13 UTC

I've been slowly moving my DC machines to Ubuntu 16.04 LTS. There's been some trials along the way but I was able to search for answers. The only problem I have not been able to solve is getting the Boinc manager to connect to the boinc client again. It was working fine until I did a sudo service boinc-client restart command in a terminal. After that the manager is shown as disconnected and it will not reconnect even after a restart or a complete power down and restart. I think it may have something to do with the client_state.xml file. The is no ip addy listed but when I edit the file and add one it doesn't stick. When I restart boinc it's empty again. When I check that file on other Linux hosts it shows the ip 127.0.0.1. On my lone windows host it shows the assigned ip addy I gave it (192.168.1.xx). Have no idea what else to try and asking for help @ askubuntu.com has resulted in no responses.

KSUMatt
Avatar
Send message
Joined: 11 Jan 13
Posts: 214
Credit: 831,004,493
RAC: 0
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44104 - Posted: 8 Aug 2016 | 21:28:44 UTC - in response to Message 44103.

The only problem I have not been able to solve is getting the Boinc manager to connect to the boinc client again.


This is the issue I've always had with BOINC in Ubuntu. I've never been able to get it working because the Manager and the Client don't seem to want to talk to each other.

captainjack
Send message
Joined: 9 May 13
Posts: 112
Credit: 821,493,749
RAC: 1,143,915
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44105 - Posted: 9 Aug 2016 | 0:12:13 UTC

nanoprobe,

Never saw the issue that you have, but here are some ideas that might help.

Start up System Monitor and see if the boinc client is running. The Process Name will be "boinc" and the User will be "boinc".

Try restarting the boinc client with this command: "sudo /etc/init.d/boinc-client restart". Then restart the boinc manager and see if it connects.

If it is still not connected, from the boinc manager, from the menu bar at the top of the window, click on "File", then "Select computer...". A small window will open up asking for host name and password. In the host name box, try "localhost" (without the quotes) no password and see if that connects. If that doesn't work, try host name "127.0.0.1:31416" (without the quotes) and no password.

If none of that gets you going, how did you install BOINC?



Jim1348
Send message
Joined: 28 Jul 12
Posts: 460
Credit: 1,130,761,180
RAC: 18,722
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44107 - Posted: 9 Aug 2016 | 13:24:53 UTC - in response to Message 44104.

The only problem I have not been able to solve is getting the Boinc manager to connect to the boinc client again.


This is the issue I've always had with BOINC in Ubuntu. I've never been able to get it working because the Manager and the Client don't seem to want to talk to each other.

I have had this problem on every BOINC installation I have done in Ubuntu 16.04 on four machines.

The solution is:

Copy "gui_rpc_auth.cfg" from the /etc/boinc-client folder to the home directory and reboot to allow BM to connect.

Since you are only reading from the /etc/boinc-client it should work, but if you have a permission problem let me know. Why they did not get this right to begin with is beyond me, but I am new to Ubuntu myself and don't know what worked before.

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44112 - Posted: 9 Aug 2016 | 19:49:24 UTC - in response to Message 44105.
Last modified: 9 Aug 2016 | 20:33:56 UTC

nanoprobe,

Never saw the issue that you have, but here are some ideas that might help.

Start up System Monitor and see if the boinc client is running. The Process Name will be "boinc" and the User will be "boinc".

Try restarting the boinc client with this command: "sudo /etc/init.d/boinc-client restart". Then restart the boinc manager and see if it connects.

If it is still not connected, from the boinc manager, from the menu bar at the top of the window, click on "File", then "Select computer...". A small window will open up asking for host name and password. In the host name box, try "localhost" (without the quotes) no password and see if that connects. If that doesn't work, try host name "127.0.0.1:31416" (without the quotes) and no password.

If none of that gets you going, how did you install BOINC?




Thanks but none of your suggestions worked. The boinc client and manager were both installed from the repositories.

The system monitor did not show boinc, only boinc manager but I know the client is running because I can control it with BoincTasks and the sensors show temp and 100% core load. Maybe things are different in this version of ubuntu.

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44113 - Posted: 9 Aug 2016 | 19:54:00 UTC - in response to Message 44107.

The only problem I have not been able to solve is getting the Boinc manager to connect to the boinc client again.


This is the issue I've always had with BOINC in Ubuntu. I've never been able to get it working because the Manager and the Client don't seem to want to talk to each other.

I have had this problem on every BOINC installation I have done in Ubuntu 16.04 on four machines.

The solution is:

Copy "gui_rpc_auth.cfg" from the /etc/boinc-client folder to the home directory and reboot to allow BM to connect.

Since you are only reading from the /etc/boinc-client it should work, but if you have a permission problem let me know. Why they did not get this right to begin with is beyond me, but I am new to Ubuntu myself and don't know what worked before.


I copied the gui_rpc_auth.cfg from the /etc/boinc-client folder but I was not able to paste it into the home directory. The paste option was greyed out which means I have a permissions issue. Did a lot of searching and tried some terminal commands but have not found an answer yet.

Jim1348
Send message
Joined: 28 Jul 12
Posts: 460
Credit: 1,130,761,180
RAC: 18,722
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44114 - Posted: 9 Aug 2016 | 20:50:26 UTC - in response to Message 44113.
Last modified: 9 Aug 2016 | 21:49:54 UTC

I copied the gui_rpc_auth.cfg from the /etc/boinc-client folder but I was not able to paste it into the home directory. The paste option was greyed out which means I have a permissions issue. Did a lot of searching and tried some terminal commands but have not found an answer yet.


Here is a more complete list of what I do to allow access to /etc/boinc-client.

Note that I copy a modified "gui_rpc_auth.cfg" into that folder, but you may not need to modify it. Also, it allows for creating (or changing) a "cc_config.xml" file, if you need to do that. I also use a "remote_hosts.cfg" file to allow access over the LAN, but you may not need it.

I have also included the commands to allow access to /var/lib/boinc-client, where the project folders are located. You will need that to copy an "app_config.xml" file into the GPUGrid project folder, for example.

-> Just replace "user_name" with you actual user name.

Join the root group: sudo adduser user_name root
Join the BOINC group: sudo adduser user_name boinc

Allow group to read, write and execute in /etc/boinc-client folder: sudo chmod -R g+rwx /etc/boinc-client
Allow group to read, write and execute in /var/lib/boinc-client: sudo chmod -R g+rwx /var/lib/boinc-client
Reboot

Copy “gui_rpc_auth.cfg” to /etc/boinc-client folder
Copy “remote_hosts.cfg” to /etc/boinc-client folder
Copy “cc_config.xml” to /etc/boinc-client folder
Copy "gui_rpc_auth.cfg" to the home directory
Reboot

Copy the "app_config.xml" files to the project folders in /var/lib/boinc/

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44119 - Posted: 10 Aug 2016 | 0:51:09 UTC - in response to Message 44114.

I copied the gui_rpc_auth.cfg from the /etc/boinc-client folder but I was not able to paste it into the home directory. The paste option was greyed out which means I have a permissions issue. Did a lot of searching and tried some terminal commands but have not found an answer yet.


Here is a more complete list of what I do to allow access to /etc/boinc-client.

Note that I copy a modified "gui_rpc_auth.cfg" into that folder, but you may not need to modify it. Also, it allows for creating (or changing) a "cc_config.xml" file, if you need to do that. I also use a "remote_hosts.cfg" file to allow access over the LAN, but you may not need it.

I have also included the commands to allow access to /var/lib/boinc-client, where the project folders are located. You will need that to copy an "app_config.xml" file into the GPUGrid project folder, for example.

-> Just replace "user_name" with you actual user name.

Join the root group: sudo adduser user_name root
Join the BOINC group: sudo adduser user_name boinc

Allow group to read, write and execute in /etc/boinc-client folder: sudo chmod -R g+rwx /etc/boinc-client
Allow group to read, write and execute in /var/lib/boinc-client: sudo chmod -R g+rwx /var/lib/boinc-client
Reboot

Copy “gui_rpc_auth.cfg” to /etc/boinc-client folder
Copy “remote_hosts.cfg” to /etc/boinc-client folder
Copy “cc_config.xml” to /etc/boinc-client folder
Copy "gui_rpc_auth.cfg" to the home directory
Reboot

Copy the "app_config.xml" files to the project folders in /var/lib/boinc/

That fixed it. Can't thank you enough. For someone who claims to be new at Linux you fixed something I've searching for weeks. Where did you come up with the info?
Thanks again.
David

Jim1348
Send message
Joined: 28 Jul 12
Posts: 460
Credit: 1,130,761,180
RAC: 18,722
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44120 - Posted: 10 Aug 2016 | 2:07:56 UTC - in response to Message 44119.

For someone who claims to be new at Linux you fixed something I've searching for weeks. Where did you come up with the info?
Thanks again.
David

You are welcome. It is Googling and educated guessing. There is unfortunately no single source of information for BOINC on Linux. That seems to be true of other aspects of Linux too. You have to learn it yourself for each distro. But for my simple crunching needs, it is now actually faster to set up a machine on Ubuntu than for Windows. I did my fourth one today in under two hours from the point of wiping the SSD with a secure erase to crunching on BOINC, and shortly thereafter Folding too.

It is unfortunate that the learning curve is steep though. Linux is really designed to be a secure server operating system, not a desktop OS. The permissions and folder structure are quite different than Windows, as you know.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 44123 - Posted: 10 Aug 2016 | 10:33:08 UTC - in response to Message 44120.

Each distribution/version of Linux has different features, terminal commands and add ons which makes it almost as difficult moving from one distribution to another as it is to move from Windows to Linux. However, Ubuntu 6.04-x64 is a Long Term Support distro, so it's something you can stick with for longer. While the command lines might have changed somewhat, again, the GUI updates (via the Ubuntu Sortware icon and Sortware & Updates in System Settings) are encouraging.
At present 6.04-x64 LTS works for GPUGrid crunching due to the driver support for GTX900 series GPU's. The question at the back of my mind is will it support NV's GTX1000 series GPU's?

http://www.omgubuntu.co.uk/2016/06/top-5-terminal-commands

http://manpages.ubuntu.com/manpages/xenial/man8/
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44124 - Posted: 10 Aug 2016 | 12:29:10 UTC - in response to Message 44123.

Each distribution/version of Linux has different features, terminal commands and add ons which makes it almost as difficult moving from one distribution to another as it is to move from Windows to Linux. However, Ubuntu 6.04-x64 is a Long Term Support distro, so it's something you can stick with for longer. While the command lines might have changed somewhat, again, the GUI updates (via the Ubuntu Sortware icon and Sortware & Updates in System Settings) are encouraging.
At present 6.04-x64 LTS works for GPUGrid crunching due to the driver support for GTX900 series GPU's. The question at the back of my mind is will it support NV's GTX1000 series GPU's?

http://www.omgubuntu.co.uk/2016/06/top-5-terminal-commands

http://manpages.ubuntu.com/manpages/xenial/man8/


16.04 does support the 10xx series GPUs. It was a minor PITA(probably more so for me being the Linux noob) to get it working. I can post what I did later if that will help. Just waiting for GPUGrid to support them.
Thanks for the links.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 44137 - Posted: 11 Aug 2016 | 20:31:40 UTC - in response to Message 44124.

Please do, it's likely to be useful to many.
Thanks,
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

nanoprobe
Send message
Joined: 26 Feb 12
Posts: 181
Credit: 221,824,715
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 44142 - Posted: 12 Aug 2016 | 1:26:18 UTC
Last modified: 12 Aug 2016 | 1:28:13 UTC

When I first installed 16.04 I was using a 750Ti and I installed the 361 driver from the repository. When I tried to install my 1060 I couldn't get it to boot. I put the 750 back in and started searching. The 367.27 driver is needed for the 10xx cards. I also found it helped me to install synaptic package manager first.
I used the following commands to get started with the video drivers.

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-367 nvidia-settings


I then reinstalled the 1060 and it booted but there were still some issues. Installing the 367 driver did not install the needed OpenCl or CUDA libraries. I used synaptic package manager to install them. Now we're almost done.

Add the unprivileged boinc account to the video group

sudo usermod -a -G video boinc

Move BOINC start-up to the end of the start-up processing.

sudo update-rc.d -f boinc-client remove
sudo update-rc.d boinc-client defaults 99


Without nvidia-modprobe installed boinc will not find the GPU

sudo apt-get install nvidia-modprobe <-- when I did this I found that it was already installed YMMV

sudo modprobe nvidia_uvm

sudo service boinc-client restart

That's it but in some cases a reboot is needed. Hope this will help someone. My 1060 now happily runs POEM and Einstein. Patiently waiting for support here
You can find more driver info here.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,834,518,624
RAC: 292,156
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 45348 - Posted: 21 Nov 2016 | 12:12:20 UTC

Tried to use the 375.20 repo drivers on Ubuntu 16.04_x64 LTS but could not get Boinc to recognise the GPU. Tried lots of tricks (repeatedly) but none worked. Reverted to 370.28 and things are working again. X server said the 375.20 driver was there but maybe it didn't fully install.
For here there is no known reason to upgrade - I was just looking to see if there was anything in it (library updates that might make things faster), on the off-chance. There usually isn't BTW. If anyone tries to use 375.20 and can't get it to work, don't spend too much time on it.
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Rion Family
Send message
Joined: 13 Jan 14
Posts: 18
Credit: 6,123,676,315
RAC: 10,409,580
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwat
Message 45395 - Posted: 25 Nov 2016 | 16:53:42 UTC

I have a setup running


Boinc 7.6.31
GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3]
(8 processors) [2] NVIDIA GeForce GTX 780 (3052MB) driver: 375.20 Linux
4.4.0-21-generic 25 Nov 2016 | 16:44:32 UTC


I was doing an upgrade from Linux Mint 17.3 (ubuntu 14.04) to 18 (ubuntu 16.04) ,
I did test the 375.20 drivers with both versions. however to get the latest boinc client I had to get to mint 18.

Basic approach - your milage may vary :)

sudo apt-get purge nvidia*

Note - Once you reboot here you have to do the next steps from the Console as it will not boot into X
sudo reboot

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo
apt-get update

sudo apt-get install nvidia-375 nvidia-settings libcuda1-375

sudo apt-get install boinc 7.6


I found these sites usefull -
http://askubuntu.com/questions/757080/why-is-it-so-hard-to-install-nvidia-drivers-what-is-the-most-fool-proof-method
https://sites.google.com/site/easylinuxtipsproject/12

Here is what appears to be the relevent packages - there may be more - these are the ones I touched during the upgrades

paz@stealth-mint ~ $ sudo dpkg -l | grep -i nvidia
[sudo] password for paz:
rc libcuda1-331 331.113-0ubuntu0.0.4 amd64 NVIDIA CUDA runtime library
rc libcuda1-346 346.22-0ubuntu1~xedgers14.04.1 amd64 NVIDIA CUDA runtime library
rc libcuda1-349 349.16-0ubuntu0~xedgers14.04.1 amd64 NVIDIA CUDA runtime library
ii libcuda1-375 375.20-0ubuntu0~gpu16.04.1 amd64 NVIDIA CUDA runtime library
ii nvidia-375 375.20-0ubuntu0~gpu16.04.1 amd64 NVIDIA binary driver - version 375.20
ii nvidia-settings 375.20-0ubuntu0~gpu16.04.1 amd64 Tool for configuring the NVIDIA graphics driver

paz@stealth-mint ~ $ uname -a
Linux stealth-mint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

paz@stealth-mint ~ $ sudo dpkg -l | grep -i boinc
ii boinc 7.6.31+dfsg-6ubuntu1 all metapackage for the BOINC client and the manager
ii boinc-client 7.6.31+dfsg-6ubuntu1 amd64 core client for the BOINC distributed computing infrastructure
ii boinc-manager 7.6.31+dfsg-6ubuntu1 amd64 GUI to control and monitor the BOINC core client
ii libboinc7:amd64 7.6.31+dfsg-6ubuntu1 amd64 libraries of BOINC the client depends on

paz@stealth-mint ~ $

Profile MarkJ
Volunteer moderator
Project tester
Volunteer tester
Send message
Joined: 24 Dec 08
Posts: 730
Credit: 189,243,545
RAC: 0
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 47071 - Posted: 23 Apr 2017 | 11:06:09 UTC
Last modified: 23 Apr 2017 | 11:07:00 UTC

I've been converting all my Windows machines over to Linux of late. I have been running Win7 but given I don't want Microsoft deciding how to manage my machines for me I went with Linux.

I've written a blog post with the instructions HERE describing how to get Debian going.

Why Debian? Its more up to date than Ubuntu - Ubuntu is based upon Debian. Also everything needed is in their standard repositories. No fiddling with driver versions and the like.

Regarding the problems getting the manager to connect with the core client I found that simply adding the password that's in gui_rpc_auth.cfg to the properties of the BOINC Manager icon was enough for it to work. No need to have two copies of gui_rpc_auth. I use a windows laptop that runs BOINC Tasks to control the crunchers but also have the manager on the desktop of each cruncher.
____________
BOINC blog

Post to thread

Message boards : Number crunching : Discussion of Ubuntu 16.04-x64 LTS installation and configuration