V8 CUDA for Linux?

Message boards : Number crunching : V8 CUDA for Linux?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 . . . 10 · Next

AuthorMessage
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779558 - Posted: 16 Apr 2016, 7:26:02 UTC - in response to Message 1779366.  

Ok, thanks for the instructions.
Just to be sure, this driver works without the installation of nvidia-modprobe?
Is this utility installed on your host?

Becosuse of course my goal today is to install nvidia-modprobe just to have my GPU seen by Boinc with my actual driver. if I can, then I install the V8 application to CUDA.

But if I install driver 361 and I don't have my GPU seen by Boinc I am still at the foot of the ladder :-)

So if someonne can tell me why with the same operating system (linux mint 17.3 cinnamon 64 bit) I have machine in which I see nvidia-modprobe in repository and I can install it and some other not.
Difference is only GPU type, but are all Geforce.
ID: 1779558 · Report as offensive
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 251
Credit: 3,696,783,867
RAC: 12,606
France
Message 1779566 - Posted: 16 Apr 2016, 8:33:23 UTC - in response to Message 1779558.  
Last modified: 16 Apr 2016, 8:33:42 UTC



So if someonne can tell me why with the same operating system (linux mint 17.3 cinnamon 64 bit) I have machine in which I see nvidia-modprobe in repository and I can install it and some other not.
Difference is only GPU type, but are all Geforce.


Check your repository file in /etc/apt/sources.list
ID: 1779566 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779630 - Posted: 16 Apr 2016, 15:43:40 UTC - in response to Message 1779566.  
Last modified: 16 Apr 2016, 15:44:21 UTC



So if someonne can tell me why with the same operating system (linux mint 17.3 cinnamon 64 bit) I have machine in which I see nvidia-modprobe in repository and I can install it and some other not.
Difference is only GPU type, but are all Geforce.


Check your repository file in /etc/apt/sources.list

Thanks for suggestion.
Same in both computer (with nvidia-modprobe found or not found)

#deb cdrom:[Linux Mint 17.3 _Rosa_ - Release amd64 20151128]/ trusty contrib main non-free

By the way, mint 17.3 give me the possiblility to optimize software sources. And I have done it.
I have reverted to default choice .. bot nothing changed.
Nvididia-modprobe non found
ID: 1779630 · Report as offensive
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 251
Credit: 3,696,783,867
RAC: 12,606
France
Message 1779642 - Posted: 16 Apr 2016, 16:01:09 UTC - in response to Message 1779630.  


By the way, mint 17.3 give me the possiblility to optimize software sources. And I have done it.
I have reverted to default choice .. bot nothing changed.
Nvididia-modprobe non found


Could you try :

apt-add-repository ppa:xorg-edgers/ppa -y
apt-get update
ID: 1779642 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1779648 - Posted: 16 Apr 2016, 16:13:47 UTC - in response to Message 1779558.  

Ok, thanks for the instructions.
Just to be sure, this driver works without the installation of nvidia-modprobe?
Is this utility installed on your host?

Becosuse of course my goal today is to install nvidia-modprobe just to have my GPU seen by Boinc with my actual driver. if I can, then I install the V8 application to CUDA.

But if I install driver 361 and I don't have my GPU seen by Boinc I am still at the foot of the ladder :-)

So if someonne can tell me why with the same operating system (linux mint 17.3 cinnamon 64 bit) I have machine in which I see nvidia-modprobe in repository and I can install it and some other not.
Difference is only GPU type, but are all Geforce.

I Don't use Modprobe, I've found if you Don't use the drivers from the Repository you Don't Need Modprobe. As stated before, I don't use the repository to install BOINC either, I use the Berkeley method https://boinc.berkeley.edu/wiki/Installing_BOINC#The_Berkeley_Installer which also means I don't have to worry about File Permissions as all the BOINC files are in the BOINC folder in my Home folder.

If you swapped out the 750Ti with the 560 you will probably be offered Modprobe again, Yes, it depends on the card you have installed as to which files you are offered by the Repository. Here's another example, I have the 361 driver installed and everything works fine Without Modprobe. However, if I remove the nVidia 361 and install 352 from the Repository BOINC, the SAME BOINC, will say it can't find the GPU. Remove the Repository 352 and Install 361, just as I've posted, and BOINC will find the GPU.
I'd suggest you forget about Modprobe and install the nVidia 361 driver as per my previous post. I'd also suggest Not using the Repository to Install BOINC, your life would be much simpler.
The only thing you have to do extra with the Berkeley_Installer is use ldd in the Terminal with the Package Manager to install the dependencies. You install the dependencies Once, then you're done. No more Permissions problems when using the Berkeley_Installer.
ID: 1779648 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779659 - Posted: 16 Apr 2016, 16:46:02 UTC - in response to Message 1779642.  


By the way, mint 17.3 give me the possiblility to optimize software sources. And I have done it.
I have reverted to default choice .. bot nothing changed.
Nvididia-modprobe non found


Could you try :

apt-add-repository ppa:xorg-edgers/ppa -y
apt-get update

Done.
Still impossible to find nvidia-modprobe package
ID: 1779659 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779661 - Posted: 16 Apr 2016, 16:51:46 UTC - in response to Message 1779648.  

... I have the 361 driver installed and everything works fine Without Modprobe. However, if I remove the nVidia 361 and install 352 from the Repository BOINC, the SAME BOINC, will say it can't find the GPU. Remove the Repository 352 and Install 361, just as I've posted, and BOINC will find the GPU.
I'd suggest you forget about Modprobe and install the nVidia 361 driver as per my previous post. I'd also suggest Not using the Repository to Install BOINC, your life would be much simpler.
The only thing you have to do extra with the Berkeley_Installer is use ldd in the Terminal with the Package Manager to install the dependencies. You install the dependencies Once, then you're done. No more Permissions problems when using the Berkeley_Installer.

Ok, understood but "ldd" what is this?
ID: 1779661 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1779666 - Posted: 16 Apr 2016, 17:37:23 UTC - in response to Message 1779661.  

Ok, understood but "ldd" what is this?

ldd will list the dependencies for the App entered. After installing BOINC in the Home folder you would open the BOINC folder and drag the Apps one by one into the terminal and check for missing dependencies. One of the common missing dependencies is libwx_gtk2u_xxx-2.8. Type in ldd then drag boincmgr into the terminal window, you will see;
tbar@TBar-iSETI:~$ ldd '/home/tbar/BOINC/boincmgr'
linux-vdso.so.1 => (0x00007ffdc008f000)
libwx_gtk2u_html-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-2.8.so.0 (0x00007ff0a764a000)
libwx_gtk2u_adv-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-2.8.so.0 (0x00007ff0a736f000)
libwx_gtk2u_core-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 (0x00007ff0a6d8e000)
libwx_baseu_net-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0 (0x00007ff0a6b60000)
libwx_baseu-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 (0x00007ff0a6814000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007ff0a655b000)
etc...

Only some dependencies will be missing. Then copy libwx and paste it into the Package Manager Filter box. It will list the packages available, usually installing libwxgtk2.8-0 will satisfy the requirement. Keep checking the App and installing dependencies until none are missing, it will look similar to the above when finished. You have to check the four Apps;
boinc
boinccmd
boincmgr
boincscr
Usually only boinc & boincmgr are missing dependencies. After all the dependencies are satisfied, you're finished and BOINC should work by double clicking boincmgr. You can pin boincmgr to the launchbar once running to make starting BONIC easier.
ID: 1779666 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779853 - Posted: 17 Apr 2016, 7:32:13 UTC - in response to Message 1779366.  
Last modified: 17 Apr 2016, 7:32:28 UTC

Download the driver, http://www.nvidia.com/Download/driverResults.aspx/101423/en-us,
then move it to your Home folder and make sure the Execute Permission is set.
Close all programs then hit control+ALT+F1 to move into the console and Login.

Stop the XServer;
sudo service lightdm stop


sorry: lightdm unrecognized service

My system is Linux Mint 17.3 "Rosa" - Cinnamon (64-bit)

Looking on forum I have found this
https://forums.linuxmint.com/viewtopic.php?t=105443

Maybe mint 13 and before uses mdm not lightdm.

Sure that all your instructions are valid for mint 17?
ID: 1779853 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1779856 - Posted: 17 Apr 2016, 7:56:41 UTC - in response to Message 1779853.  

Download the driver, http://www.nvidia.com/Download/driverResults.aspx/101423/en-us,
then move it to your Home folder and make sure the Execute Permission is set.
Close all programs then hit control+ALT+F1 to move into the console and Login.

Stop the XServer;
sudo service lightdm stop


sorry: lightdm unrecognized service

My system is Linux Mint 17.3 "Rosa" - Cinnamon (64-bit)

Looking on forum I have found this
https://forums.linuxmint.com/viewtopic.php?t=105443

Maybe mint 13 and before uses mdm not lightdm.

Sure that all your instructions are valid for mint 17?

Hey, different versions call it different names as you have discovered. Some call it GDM. If you're afraid to install the nVidia driver then don't. I'm certainly not going to force you. Stay with what you have.
I'd be Real afraid of installing that CUDA App if I were you, I actually DID make that.
ID: 1779856 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1779918 - Posted: 17 Apr 2016, 17:15:39 UTC - in response to Message 1779856.  

If you're afraid to install the nVidia driver then don't. I'm certainly not going to force you. Stay with what you have.
I'd be Real afraid of installing that CUDA App if I were you, I actually DID make that.

It's not a problem of "afraid " but of full correct instructions.
One of the problems in the Net is that we can find a lot "do in such way" but as you know not all of them are sane.
I'm in IT since 1978 so I know that it's better to be very cautious.
If I see that first line is an error, something in my few neurons :-) tells me to be careful about other lines.
My goal is to run seti@ V8 on GPU in linux mint environment with GTX 750ti
Of course is not a medical prescription :-)
I know that you don't want to force me but I need to be sure of every step I do.
ID: 1779918 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1780060 - Posted: 18 Apr 2016, 8:43:11 UTC

Host is new and without any important data, so I get the risk.

Installation done. Non errors.

But as Mint starts, Cinnamon crashes.
I have only a low resolution screen; hard to work.
I cannot revert to old nvidia dirvers so I need to reinstall Linux.
Boinc starts but "No usable GPU found".

Format and reinstall.
ID: 1780060 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1780068 - Posted: 18 Apr 2016, 10:37:24 UTC - in response to Message 1780060.  
Last modified: 18 Apr 2016, 10:40:36 UTC

That sounds similar to what I've experienced when the Repository driver wasn't removed before installing the nVidia driver. In that case the nVidia driver will "backup" the Repository driver and install it's own files. I've never seen anything good from that scenario. One way to check if that's what happened would be to look in /usr/lib/x86-linux-gnu and find libcuda.so.XXX.xx. If you installed 361.42 you should find libcuda.so.361.42 there, if you also find another file such as libcuda.so.352.63 there, it's not good. It's even worse if you find a third file, such as libcuda.so.304.xx with the other two. It tends to create confusion.

There are different ways to remove the Repository drivers and the nVidia drivers, One of the commands to remove the Repository driver is the one I listed; sudo apt-get remove --purge nvidia*. The way to remove the nVidia driver was also listed, for driver 361.42 you would run sudo ./NVIDIA-Linux-x86_64-361.42.run --uninstall. The nVidia command will Not remove the Repository driver, as the Repository command will Not remove the nVidia driver.

To remove the nVidia driver and install the Repository driver you would reverse the previous procedure. It helps if you know which driver is offered by the Repository, in this case we will use 352.xx. You also need to still have the installed nVidia driver in your Home folder.

1) Close all programs and hold control+ALT+F1 to drop into the console, then Login.
2) Use which ever command is Appropriate to Stop the XServer
3) Remove the nVidia driver, sudo ./NVIDIA-Linux-x86_64-361.42.run --uninstall
4) Install the Repository driver, sudo apt-get install nvidia-352
If you still have the Repository driver installed, you should Probably run the Uninstall command first, sudo apt-get remove --purge nvidia* then install, sudo apt-get install nvidia-352
5) Reboot, sudo reboot.

You shouldn't need to format or reinstall.
So far, I've managed to install and try about half of the recent drivers in the nVidia Linux Repository, all but a couple worked just fine in the systems I've tried them on.

Good Luck.
ID: 1780068 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1780087 - Posted: 18 Apr 2016, 13:55:18 UTC - in response to Message 1780068.  
Last modified: 18 Apr 2016, 13:57:20 UTC

System now reverted to Repository driver.

I'm looking for nvidia_modprobe (missing in my repository) and I have found sources, done the make and make install but nothing changed.
Of course of the same version of the driver (now I'm using 340.96)

I'm still with "No usable GPUs found".
ID: 1780087 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1780190 - Posted: 18 Apr 2016, 21:46:01 UTC - in response to Message 1780087.  

Your experience is similar to a number of others from late last year. My theory is it's related to how you installed BOINC. People installing BOINC from the Repository seem to have the problem more than those who installed BOINC using the Berkeley Installer. From those old threads Most of the people I'm aware of solved the problem by installing the nVidia CUDA Toolkit, most used Toolkit 7.5 which installs nVidia driver 352.xx. I use Ubuntu because both Berkeley and nVidia list compatible versions of Ubuntu. Some say Mint is basically Ubuntu, however the version numbers are different. nVidia lists Ubuntu 14.04 & 15.04 as supported by Toolkit 7.5 https://developer.nvidia.com/cuda-downloads, rather or not that translates to your OS is up to you to decide, I use Ubuntu.

If you do choose to install the Toolkit I suggest the same method used to install a driver. Download the Toolkit and place it in your Home folder.
1) Move into the Console, Login, then Stop the XServer
2) Remove any existing driver be it from the Repository or nVidia
3) Install the Toolkit and choose to install the Driver and the Toolkit, you don't need Samples
4) If it complains about a non-compatible Compiler choose the Override. You are looking for a working BOINC not a working Toolkit even though the Toolkit will probably work after using the Override anyway

After you get BOINC working you can install a newer nVidia driver if you wish. My current Ubuntu 14.04 has Toolkit 6.5 and nVidia driver 361.42 working well together. So far, I've used it to Compile 4 different CUDA Apps including the "Special" CUDA 6.5 App I'm using now.
ID: 1780190 · Report as offensive
Profile Francesco Forti
Avatar

Send message
Joined: 24 May 00
Posts: 334
Credit: 204,421,005
RAC: 15
Switzerland
Message 1780770 - Posted: 20 Apr 2016, 17:44:29 UTC - in response to Message 1780190.  

nVidia CUDA Toolkit is in Mint 17.3 repository as "5.5.22-3ubuntu1"

Installed with all dependencies.

Nothing
ID: 1780770 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1780814 - Posted: 20 Apr 2016, 21:20:59 UTC - in response to Message 1780770.  

I don't think Toolkit 5.5 is going to help any.
Here is the 5.5 page, https://developer.nvidia.com/cuda-toolkit-55-archive
Relevant points on 5.5;
Release date: July 2013
Highest OS Supported: Ubuntu 12.10
Installed Driver: 319.xx
Your OS is closer to Ubuntu 15.04
Your 750 Requires driver 337.xx or higher.

AFAIK, the Lowest Toolkit to support the 750 is 6.5, and the Highest OS for Toolkit 6.5 is Ubuntu 14.04.

Have you noticed there are quite a few other people running your OS that don't seem to have your problem? http://setiathome.berkeley.edu/top_hosts.php
I see a few there listed as "Linux 3.19.0-32-generic" and they seem to be running driver 352.79.
ID: 1780814 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1780838 - Posted: 20 Apr 2016, 22:38:12 UTC
Last modified: 20 Apr 2016, 22:45:55 UTC

To use CUDA or OpenCL you need to have NVIDIA drivers loaded and some device nodes created.

Normally X server takes care of loading drivers and all that.

BOINC installed from repository package usually starts before X has loaded drivers.

BOINC installed from Berkeley package is usually started after logging in to X.

One way to get repository BOINC to detect GPUs is to restart it after logging in to X.

NVIDIA's usermode parts of CUDA and OpenCL know how to load the drivers with the help of nvidia-modprobe.

Unlikely normal programs nvidia-modprobe has permissions to load drivers as it is installed setuid root.

nvidia-modprobe is included in the driver package NVIDIA makes.

nvidia-modprobe is not included in Ubuntu 14.04=Trusty repositories.

nvidia-modprobe is included in Trusty backports repository as well as in repositories of later Ubuntu versions.

Starting with Ubuntu 16.04 nvidia-modprobe is no longer needed as Ubuntu's driver package is tweaked so that udev does all the necessary work.

Ubuntu's Software Sources tool can enable backports repository by ticking a checkbox.

Mint's Software Sources tool can't enable Ubuntu backports repository.

On Mint trusty-backports can be enabled by editing /etc/apt/sources.list.d/additional-repositories.list and uncommenting (removing # sign) the following line (and changing the URL to that of a nearby mirror) or adding the line in a new .list file in the same directory:

deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse


After enabling repositories package cache must be refreshed in the usual manner with package manager.

For OpenCL support an OpenCL ICD (Installable Client Driver) loader and OpenCL ICD are required where the loader provides a driver independent way of accessing OpenCL implementations.

NVIDIA's own package provides both, Ubuntu's version is split into multiple packages.

On Ubuntu, NVIDIA OpenCL ICD is provided by nvidia-opencl-icd-* package.

On Ubuntu, different implementations of OpenCL ICD are available in packages nvidia-libopencl1-* and ocl-icd-libopencl1 .

For completeness, on Ubuntu CUDA component is in package libcuda1-* .

All the required packages are normally installed by installing the main driver package nvidia-* which is what the Driver Manager GUI tool installs.

Older versions of BOINC try to get access to the OpenCL ICD loader by opening libOpenCL.so .

libOpenCL.so as a file or a symlink has not been present in Ubuntu's OpenCL ICD loader packages for a good while.

To get the OpenCL detection working the symlink can be created manually or BOINC can be upgraded to a version that can detect OpenCL even without the symlink.

Since about version 7.6.23 BOINC has been enhanced try libOpenCL.so.1 also.

For Ubuntu and derivatives a newer version of BOINC can be installed from LocutusOfBorg's ppa.

When all else fails, enable coproc_debug and post startup logs.
ID: 1780838 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6324
Credit: 106,370,077
RAC: 121
Russia
Message 1780841 - Posted: 20 Apr 2016, 22:44:05 UTC - in response to Message 1780838.  

Wow :)
That's Linux...
ID: 1780841 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1780842 - Posted: 20 Apr 2016, 22:54:17 UTC - in response to Message 1780841.  

That's what happens when you watch a problem solving going nowhere and decide to clear up a few misunderstandings at the same time and crank up the level of detail all the way to ridiculous.
ID: 1780842 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 . . . 10 · Next

Message boards : Number crunching : V8 CUDA for Linux?


 
©2023 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.