If you need help with BOINC it's always a good idea to post those startup messages that Gary mentioned.
Quote:
I typed in # find /usr -name libOpenCL* -a -print
and nothing came up (doing something wrong there)
You did not really type "#", did you? That would indeed be wrong. "#" indicates a shell prompt, precisely a root shell prompt. If you actually type it, it makes the whole line a comment.
Try it again without the hash sign. If you find /usr/lib/libOpenCL.so.1 but not /usr/lib/libOpenCL.so, run "sudo apt-get install fglrx-dev" and look again.
Explanation: Linux Lite seems to be based on Ubuntu trusty which as far as I can see contains everything needed in the fglrx package, except the infamous libOpenCL.so link. That is installed by fglrx-dev.
I am running Ubuntu 14 and here is what I installed to get it to recognize the AMD GPU:
1. ATI binary X.Org driver - install it.
2. fglrx-dev - install it (other prerequisites will install)
3. reboot
There was no need for me to generate soft links for any libraries or do anything else.
... There was no need for me to generate soft links for any libraries or do anything else.
The OP's recent message shows the symbolic link needed by BOINC already exists!!
The bit I'm wondering about is that the the permissions on the actual library don't show the execute bit as being set. Could you please check if your working system has -rw-r--r-- permissions for the library as the OP shows for his system? I could easily be wrong but my understanding was that .so (shared object) files should be -rwxr-xr-x and maybe this is the OP's problem.
... There was no need for me to generate soft links for any libraries or do anything else.
The OP's recent message shows the symbolic link needed by BOINC already exists!!
The bit I'm wondering about is that the the permissions on the actual library don't show the execute bit as being set. Could you please check if your working system has -rw-r--r-- permissions for the library as the OP shows for his system? I could easily be wrong but my understanding was that .so (shared object) files should be -rwxr-xr-x and maybe this is the OP's problem.
user@hostname:/usr/lib$ ls -l libOpen* lrwxrwxrwx 1 root root 14 Aug 18 06:18 libOpenCL.so -> libOpenCL.so.1 -rw-r--r-- 1 root root 27328 Aug 18 06:19 libOpenCL.so.1
[EDIT] I have used "sudo service boinc-client restart" after making changes and "sometimes" this has had a positive effect. But not always. I find that there are times when a reboot does the job. Why? Not sure but if dkms is involved in a software update/install then it seems that a reboot is absolutely necessary. If installing software from the command line using "apt-get" you will notice that dkms gets called on certain updates where the kernel gets involved.
Hmm ok - I am assuming you
)
Hmm ok - I am assuming you are running a monitor on the graphics card.
This thread may be relevant and i've just noticed (another) typo in it (mea culpa)! where it says /etc/defaults/... it should be /etc/default/
i would look very closely at
ls -lart /usr/lib/libOpenCL.so*
should show
[pre]
-rw-r--r-- 1 root root 26184 Jun 2 17:52 /usr/lib/libOpenCL.so.1
lrwxrwxrwx 1 root root 23 Jun 4 23:03 /usr/lib/libOpenCL.so -> /usr/lib/libOpenCL.so.1
[/pre]
then
grep LD_LIB /etc/init.d/boinc_client
grep LD_LIB /etc/default/boinc-client
one or both should show the setting for LD_LIBRARY_PATH
[pre]
LD_LIBRARY_PATH=/lib64:/usr/lib:/lib:/usr/local/lib
export LD_LIBRARY_PATH
[/pre]
if you do make changes - make certain you make a backup.
Yes running monitor from
)
Yes running monitor from graphics card
chase1902@Storm:~$ ls -lart /usr/lib/libOpenCL.so*
lrwxrwxrwx 1 root root 14 Aug 18 11:18 /usr/lib/libOpenCL.so -> libOpenCL.so.1
-rw-r--r-- 1 root root 27328 Aug 18 11:19 /usr/lib/libOpenCL.so.1
Will have a read of the
)
Will have a read of the thread you linked to later tonight, as not seeing the setting for LD_LIBRARY_PATH.
Thanks again for your help.
John
RE: If you need help with
)
I am running Ubuntu 14 and here is what I installed to get it to recognize the AMD GPU:
1. ATI binary X.Org driver - install it.
2. fglrx-dev - install it (other prerequisites will install)
3. reboot
There was no need for me to generate soft links for any libraries or do anything else.
RE: ... There was no need
)
The OP's recent message shows the symbolic link needed by BOINC already exists!!
The bit I'm wondering about is that the the permissions on the actual library don't show the execute bit as being set. Could you please check if your working system has -rw-r--r-- permissions for the library as the OP shows for his system? I could easily be wrong but my understanding was that .so (shared object) files should be -rwxr-xr-x and maybe this is the OP's problem.
Cheers,
Gary.
I'm now quite confident that
)
I'm now quite confident that this issue is one I ran into when I switched from NVIDIA to AMD. Took me a while to work it out.
xhost may not be installed by default, you'd need to install x11-xserver-utils for that.
RE: RE: ... There was no
)
here is what I am showing:
user@hostname:/usr/lib$ ls -ld
drwxr-xr-x 159 root root 20480 Sep 5 13:34
user@hostname:/usr/lib$ ls -l libOpen*
lrwxrwxrwx 1 root root 14 Aug 18 06:18 libOpenCL.so -> libOpenCL.so.1
-rw-r--r-- 1 root root 27328 Aug 18 06:19 libOpenCL.so.1
[EDIT] I have used "sudo service boinc-client restart" after making changes and "sometimes" this has had a positive effect. But not always. I find that there are times when a reboot does the job. Why? Not sure but if dkms is involved in a software update/install then it seems that a reboot is absolutely necessary. If installing software from the command line using "apt-get" you will notice that dkms gets called on certain updates where the kernel gets involved.
RE: I'm now quite confident
)
Success, thank you for your help. hopefully all will run smooth now.
John
RE: Success, thank you for
)
The xhost setting is not permanent, you'll want to look for a way to automate it.
RE: I could easily be
)
This is no longer needed, (certainly not set for most "so" libraries on Ubuntu for some time) although a good (a bit old) answer is here
There are a couple of notable so files which are executable - the ldd linker is one such.
Edit: To be a little clearer - in *nix, symbolic links do not have settable permissions, their permissions always show as "lrwxrwxrwx".