Unable to get ATi GPU's to Crunch in Ubuntu

Message boards : Number crunching : Unable to get ATi GPU's to Crunch in Ubuntu
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839473 - Posted: 1 Jan 2017, 20:59:37 UTC

I could use some help. I have tried everything I can think of to get these two ATI cards to crunch ANY project. First I had Ubuntu 16.04 installed and realized it was a driver issue (or so I thought) so I tried different drivers, no go. Then I moved them to another PC and installed Ununtu 14.04, which is supposed to have support for the cards, but still no go on getting them to work. BOINC says No GPU Detected.

Does ANYONE have any ideas on what I might be missing? Just let me know what I can supply system information wise to help figure this out, getting a bit frustrated. Now I know why I dislike ATI cards...

1: 31-Dec-2016 22:38:41 (low) [] Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu
2: 31-Dec-2016 22:38:41 (low) [] log flags: file_xfer, sched_ops, task
3: 31-Dec-2016 22:38:41 (low) [] Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2 .3
4: 31-Dec-2016 22:38:41 (low) [] Data directory: /var/lib/boinc-client
5: 31-Dec-2016 22:38:41 (low) [] No usable GPUs found
6: 31-Dec-2016 22:38:41 (low) [] Host name: cruncher
7: 31-Dec-2016 22:38:41 (low) [] Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz [Famil y 6 Model 58 Stepping 9]
8: 31-Dec-2016 22:38:41 (low) [] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_ perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_c pl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts
9: 31-Dec-2016 22:38:41 (low) [] OS: Linux: 4.4.0-57-generic
10: 31-Dec-2016 22:38:41 (low) [] Memory: 15.56 GB physical, 15.89 GB virtual
11: 31-Dec-2016 22:38:41 (low) [] Disk: 213.41 GB total, 198.52 GB free
12: 31-Dec-2016 22:38:41 (low) [] Local time is UTC -7 hours
13: 31-Dec-2016 22:38:41 (low) [] VirtualBox version: 5.1.12r112440

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]

Thanks!
ID: 1839473 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839478 - Posted: 1 Jan 2017, 21:24:07 UTC - in response to Message 1839473.  
Last modified: 1 Jan 2017, 21:36:54 UTC

Let's see, since you don't have the CPU OpenCL listed I'd guess you're using the repository driver. I'd suggest the same as in the other thread, try making a link to the OpenCL library in /usr/lib. The easiest way is to open a file browser with root privileges. Open a terminal and enter gksu nautilus. It you need to, install gksu and nautilus. Enter the password and then navigate to where usr/lib/libOpenCL.so should be. If you have libOpenCL.so.1 there, make a link to it and name the link libOpenCL.so. If you have libOpenCL.so there, make a link and name it libOpenCL.so.1. One of those should result in BOINC seeing ONE GPU. To get BOINC to see Both GPUs, you'll have to do the gpu_manager.conf hack explained in other posts.

See if the link works first.

...only one of the GPUs is recognized by BOINC
ID: 1839478 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839486 - Posted: 1 Jan 2017, 22:03:39 UTC - in response to Message 1839478.  
Last modified: 1 Jan 2017, 22:05:40 UTC

Maybe the issue is this is a headless server? I don't use X or anything. I SSH into the system. The more I read the more it seems the GPU's are tied into a graphical desktop.

I pulled all the drivers I installed from fglrx*.

I am not seeing any of the OpenCL stuff. I did download fglrx-core_15.302-0ubuntu1_amd64_ub_14.01.deb I am thinking I should install this.

la /usr/lib
total 11340
drwxr-xr-x 64 root root 4096 Jan 1 14:35 .
drwxr-xr-x 11 root root 4096 Dec 31 21:04 ..
drwxr-xr-x 2 root root 4096 Dec 31 20:23 accountsservice
drwxr-xr-x 4 root root 4096 Dec 31 20:22 apt
drwxr-xr-x 2 root root 4096 Dec 31 20:45 at-spi2-core
drwxr-xr-x 2 root root 4096 Dec 31 20:27 boinc-client
drwxr-xr-x 3 root root 4096 Dec 31 20:10 byobu
drwxr-xr-x 2 root root 4096 Dec 31 20:45 colord
-rwxr-xr-x 1 root root 3274 Apr 3 2014 command-not-found
drwxr-xr-x 2 root root 4096 Dec 31 20:45 compat-ld
drwxr-xr-x 2 root root 4096 Dec 31 20:03 coreutils
drwxr-xr-x 2 root root 4096 Dec 31 20:22 dbus-1.0
drwxr-xr-x 2 root root 4096 Dec 31 20:45 dconf
drwxr-xr-x 2 root root 4096 Dec 31 21:04 dkms
drwxr-xr-x 3 root root 4096 Dec 31 20:03 dpkg
drwxr-xr-x 2 root root 4096 Dec 31 20:03 eject
drwxr-xr-x 3 root root 4096 Dec 31 20:03 gcc
drwxr-xr-x 2 root root 4096 Dec 31 20:09 girepository-1.0
drwxr-xr-x 2 root root 4096 Dec 31 20:22 gnupg
drwxr-xr-x 2 root root 4096 Dec 31 20:45 gold-ld
drwxr-xr-x 3 root root 4096 Dec 31 20:13 grub
drwxr-xr-x 2 root root 4096 Dec 31 20:13 grub-legacy
drwxr-xr-x 3 root root 4096 Dec 31 20:03 initramfs-tools
drwxr-xr-x 2 root root 4096 Dec 31 20:03 insserv
drwxr-xr-x 3 root root 4096 Dec 31 20:03 klibc
drwxr-xr-x 2 root root 4096 Dec 31 20:08 language-selector
drwxr-xr-x 2 root root 4096 Dec 31 20:45 ldscripts
-rw-r--r-- 1 root root 1174416 May 2 2016 libbfd-2.24-system.so
lrwxrwxrwx 1 root root 18 Oct 31 07:40 libbind9.so.90 -> libbind9.so.90.0.9
-rw-r--r-- 1 root root 55080 Oct 31 07:40 libbind9.so.90.0.9
lrwxrwxrwx 1 root root 24 Mar 7 2014 libboinc_crypt.so.7 -> libboinc_crypt.so.7.2.42
-rw-r--r-- 1 root root 26464 Mar 7 2014 libboinc_crypt.so.7.2.42
lrwxrwxrwx 1 root root 18 Mar 7 2014 libboinc.so.7 -> libboinc.so.7.2.42
-rw-r--r-- 1 root root 444464 Mar 7 2014 libboinc.so.7.2.42
lrwxrwxrwx 1 root root 22 Mar 7 2014 libboinc_zip.so.7 -> libboinc_zip.so.7.2.42
-rw-r--r-- 1 root root 455104 Mar 7 2014 libboinc_zip.so.7.2.42
lrwxrwxrwx 1 root root 19 Dec 18 2013 libcwidget.so.3 -> libcwidget.so.3.0.0
-rw-r--r-- 1 root root 1052352 Dec 18 2013 libcwidget.so.3.0.0
lrwxrwxrwx 1 root root 17 Oct 31 07:40 libdns.so.100 -> libdns.so.100.2.2
-rw-r--r-- 1 root root 1912304 Oct 31 07:40 libdns.so.100.2.2
lrwxrwxrwx 1 root root 28 Aug 8 2014 libgirepository-1.0.so.1 -> libgirepository-1.0.so.1.0.0
-rw-r--r-- 1 root root 208352 Aug 8 2014 libgirepository-1.0.so.1.0.0
lrwxrwxrwx 1 root root 18 Oct 31 07:40 libisccc.so.90 -> libisccc.so.90.0.6
-rw-r--r-- 1 root root 34776 Oct 31 07:40 libisccc.so.90.0.6
lrwxrwxrwx 1 root root 19 Oct 31 07:40 libisccfg.so.90 -> libisccfg.so.90.1.0
-rw-r--r-- 1 root root 140416 Oct 31 07:40 libisccfg.so.90.1.0
lrwxrwxrwx 1 root root 16 Oct 31 07:40 libisc.so.95 -> libisc.so.95.5.0
-rw-r--r-- 1 root root 400824 Oct 31 07:40 libisc.so.95.5.0
lrwxrwxrwx 1 root root 18 Oct 31 07:40 liblwres.so.90 -> liblwres.so.90.0.7
-rw-r--r-- 1 root root 75688 Oct 31 07:40 liblwres.so.90.0.7
-rw-r--r-- 1 root root 1369432 May 2 2016 libopcodes-2.24-system.so
lrwxrwxrwx 1 root root 17 Dec 31 20:03 libperl.so.5.18 -> libperl.so.5.18.2
-rw-r--r-- 1 root root 1608280 Mar 1 2016 libperl.so.5.18.2
lrwxrwxrwx 1 root root 18 Mar 7 2014 libsched.so.7 -> libsched.so.7.2.42
-rw-r--r-- 1 root root 256136 Mar 7 2014 libsched.so.7.2.42
lrwxrwxrwx 1 root root 19 Dec 18 2013 libxapian.so.22 -> libxapian.so.22.6.3
-rw-r--r-- 1 root root 2051544 Dec 18 2013 libxapian.so.22.6.3
drwxr-xr-x 3 root root 4096 Dec 31 20:13 linux-boot-probes
drwxr-xr-x 3 root root 4096 Dec 31 20:03 locale
drwxr-xr-x 2 root root 4096 Dec 31 22:30 locate
drwxr-xr-x 2 root root 4096 Dec 31 20:09 man-db
drwxr-xr-x 2 root root 4096 Dec 31 20:09 memtest86+
drwxr-xr-x 3 root root 4096 Dec 31 20:03 mime
drwxr-xr-x 2 root root 4096 Dec 31 20:23 openssh
drwxr-xr-x 2 root root 4096 Dec 31 20:13 os-prober
drwxr-xr-x 4 root root 4096 Dec 31 20:13 os-probes
drwxr-xr-x 3 root root 4096 Dec 31 20:03 perl
drwxr-xr-x 6 root root 4096 Dec 31 20:09 perl5
drwxr-xr-x 2 root root 4096 Dec 31 21:13 pkgconfig
drwxr-xr-x 4 root root 4096 Dec 31 20:09 pm-utils
drwxr-xr-x 2 root root 4096 Dec 31 20:10 policykit-1
drwxr-xr-x 3 root root 4096 Dec 31 20:09 pppd
drwxr-xr-x 26 root root 20480 Dec 31 20:24 python2.7
drwxr-xr-x 3 root root 4096 Dec 31 20:03 python3
drwxr-xr-x 32 root root 20480 Dec 31 20:22 python3.4
drwxr-xr-x 2 root root 4096 Dec 31 20:03 rsyslog
drwxr-xr-x 2 root root 4096 Nov 2 2013 sasl2
lrwxrwxrwx 1 root root 19 Aug 11 10:15 sftp-server -> openssh/sftp-server
drwxr-xr-x 2 root root 4096 Dec 31 20:10 software-properties
drwxr-xr-x 3 root root 4096 Dec 31 20:23 ssl
drwxr-xr-x 2 root root 4096 Dec 31 20:22 sudo
drwxr-xr-x 3 root root 4096 Dec 31 20:09 systemd
drwxr-xr-x 2 root root 4096 Feb 4 2014 tar
drwxr-xr-x 5 root root 4096 Dec 31 20:06 tasksel
drwxr-xr-x 2 root root 4096 Dec 31 20:03 tc
drwxr-xr-x 2 root root 4096 Dec 31 20:23 tmpfiles.d
drwxr-xr-x 2 root root 4096 Dec 31 20:22 ubuntu-release-upgrader
drwxr-xr-x 2 root root 4096 Dec 31 20:22 update-notifier
drwxr-xr-x 2 root root 4096 Dec 31 20:03 upstart
drwxr-xr-x 2 root root 4096 Dec 31 20:06 valgrind
drwxr-xr-x 8 root root 4096 Dec 31 20:49 virtualbox
drwxr-xr-x 3 root root 4096 Dec 31 20:10 w3m
drwxr-xr-x 2 root root 4096 Dec 9 2014 X11
drwxr-xr-x 33 root root 20480 Jan 1 14:35 x86_64-linux-gnu
drwxr-xr-x 3 root root 4096 Dec 31 21:13 xorg
drwxr-xr-x 2 root root 4096 Dec 31 20:46 zathura
cruncher:~$
ID: 1839486 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839488 - Posted: 1 Jan 2017, 22:24:49 UTC - in response to Message 1839486.  

Maybe the issue is this is a headless server?

Yes, that does make things more difficult. It should work though.
That version of BOINC looks for the OpenCL library in usr/lib and upon Not finding it there will report No usable GPUs.
Different systems and different drivers will place the library and links in different locations. You just need to find the OpenCL library and place a valid link to it in usr/lib named libOpenCL.so
One popular location for the library is usr/lib/x86_64-linux-gnu. Another is usr/lib/fglrx.
ID: 1839488 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839490 - Posted: 1 Jan 2017, 22:52:08 UTC - in response to Message 1839488.  

Maybe the issue is this is a headless server?

Yes, that does make things more difficult. It should work though.
That version of BOINC looks for the OpenCL library in usr/lib and upon Not finding it there will report No usable GPUs.
Different systems and different drivers will place the library and links in different locations. You just need to find the OpenCL library and place a valid link to it in usr/lib named libOpenCL.so
One popular location for the library is usr/lib/x86_64-linux-gnu. Another is usr/lib/fglrx.


OK, I installed the AMD drivers and now I have the OpenCL.so.1 so I made the link and rebooted and still have:

lrwxrwxrwx 1 root root 23 Jan 1 15:42 libOpenCL.so -> /usr/lib/libOpenCL.so.1
-rw-r--r-- 1 root root 27336 Dec 18 2015 libOpenCL.so.1


boinccmd --get_messages
1: 01-Jan-2017 15:46:07 (low) [] Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu
2: 01-Jan-2017 15:46:07 (low) [] log flags: file_xfer, sched_ops, task
3: 01-Jan-2017 15:46:07 (low) [] Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
4: 01-Jan-2017 15:46:07 (low) [] Data directory: /var/lib/boinc-client
5: 01-Jan-2017 15:46:07 (low) [] OpenCL CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))
6: 01-Jan-2017 15:46:07 (low) [] No usable GPUs found
7: 01-Jan-2017 15:46:07 (low) [] Host name: cruncher
8: 01-Jan-2017 15:46:07 (low) [] Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz [Family 6 Model 58 Stepping 9]


@cruncher:~$ locate OpenCL
/etc/OpenCL
/etc/OpenCL/vendors
/etc/OpenCL/vendors/amdocl32.icd
/etc/OpenCL/vendors/amdocl64.icd
/usr/lib/libOpenCL.so.1
/usr/lib32/libOpenCL.so.1
ID: 1839490 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839493 - Posted: 1 Jan 2017, 23:01:34 UTC - in response to Message 1839490.  

@cruncher:~$ locate OpenCL
/etc/OpenCL
/etc/OpenCL/vendors
/etc/OpenCL/vendors/amdocl32.icd
/etc/OpenCL/vendors/amdocl64.icd
/usr/lib/libOpenCL.so.1
/usr/lib32/libOpenCL.so.1

I still don't see /usr/lib/libOpenCL.so
ID: 1839493 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839501 - Posted: 1 Jan 2017, 23:43:37 UTC - in response to Message 1839493.  

@cruncher:~$ locate OpenCL
/etc/OpenCL
/etc/OpenCL/vendors
/etc/OpenCL/vendors/amdocl32.icd
/etc/OpenCL/vendors/amdocl64.icd
/usr/lib/libOpenCL.so.1
/usr/lib32/libOpenCL.so.1

I still don't see /usr/lib/libOpenCL.so



It was shown in the directory listing above, but I updated the locate database and :

locate OpenCL
/usr/lib/libOpenCL.so
/usr/lib32/libOpenCL.so
ID: 1839501 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839508 - Posted: 2 Jan 2017, 0:02:31 UTC - in response to Message 1839501.  

Data directory: /var/lib/boinc-client

Must be another problem associated with the Repository version of BOINC. I don't use the Repository version for various reasons.
Both my dual ATI Ubuntu 14.04 machines have the Berkeley BOINC installed in the Home folder, I don't have these problems.
I think there is another step that works with the repository version of BOINC posted somewhere on this board, or maybe someone else can post it.
ID: 1839508 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839629 - Posted: 2 Jan 2017, 16:53:24 UTC - in response to Message 1839508.  

Hmm, well thanks for trying. I have pretty much given up. I guess these cards are just not usable at least in any version of Linux I know how to get around in. Maybe I'll just axe the Ubuntu and put a copy of Windows on.
ID: 1839629 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1839636 - Posted: 2 Jan 2017, 17:24:08 UTC - in response to Message 1839629.  

The first thing you should do is connect monitor to the cards. There's no point in trying to get an advanced configuration working before you have verified that basics work.

You can also try running clinfo if it reports any GPUs. If it doesn't BOINC won't either.
ID: 1839636 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839639 - Posted: 2 Jan 2017, 17:44:39 UTC - in response to Message 1839629.  
Last modified: 2 Jan 2017, 18:15:24 UTC

I'm pretty sure it's some obscure Permissions issue. A number of people have had the same trouble, some were able to solve it. Like I said, I found out a couple of years ago the easiest way to run BOINC was to use the Berkeley Installer and place it in the Home folder. You don't have any of those issues if you run BOINC from your Home folder. All I've had to do to get dozens of different installs to work is to install the System, place the Berkeley BOINC in the Home folder and install the One dependency, Install a driver and make sure the OpenCL link is in usr/lib. That's it, all of them worked. Earlier it was easier to install the Vendors Driver, but lately the Repository drivers have been working well.

Try this, it was suggested a few days ago, ...ensuring boinc was added to the "video" group
There are a few other things you can try, but, you'll have to search for them.
Juha may be able to help. If you can't get it to work, I'd suggest trying the Berkeley BOINC in the Home folder while suspending the System Networking. If it works you might be able to transfer your existing files to the Home folder BOINC and then re-enable networking. No Harm No Foul as long as the Ubuntu Networking is off when you first try the Berkeley BOINC.

This is for an nVidia card, it's the same for an ATI cards, just use the ATI driver.
https://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1836494#1836494
ID: 1839639 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839688 - Posted: 2 Jan 2017, 20:52:30 UTC - in response to Message 1839639.  

Do you have instructions on how to install the BOINC client in the home folder? I have downloaded the Ubuntu .sh file from the BOINC page, but I haven't a clue to how to get this installed. I seem to get it to run, but no projects and the like.
ID: 1839688 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839691 - Posted: 2 Jan 2017, 21:13:39 UTC - in response to Message 1839688.  
Last modified: 2 Jan 2017, 21:22:59 UTC

The instructions are at the link at the bottom of my last post, and here, https://boinc.berkeley.edu/wiki/Installing_BOINC#The_Berkeley_Installer
That's for a machine with a monitor, it might be best to attach at least one monitor as Juha suggested. I have one card attached and the other using a dummy plug. When the .sh file runs it will create a folder named BOINC. The BOINC folder should be in your Home folder, I believe the execute bits are set, you might check that. You can probably install the needed dependency by installing libwxgtk2.8-dev. sudo apt-get install libwxgtk2.8-dev
That should be all boincmgr needs, you might check dependencies with ldd in the terminal. After that, all you have to do is run the boincmgr that's in the BOINC folder. I just double click boincmgr and then lock it to the launcher, it works best if you don't restart BOINC very often ;-)
ID: 1839691 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839711 - Posted: 2 Jan 2017, 23:17:01 UTC
Last modified: 2 Jan 2017, 23:48:10 UTC

Hmmmm, I see a New Linux Host that still isn't showing any GPUs. So, that eliminates any Permissions problems, you don't need any special Permissions to run BOINC from the Home folder. It acts as though it's Not finding OpenCL even though the CPU was showing OpenCL. If you haven't run clinfo yet, run clinfo in the terminal and see if it's listing 2 GPUs and a CPU. Also, look in the old boinc-client/projects/setiathome.berkeley.edu folder, find the ATI OpenCL App and run ldd on it to see if it's finding libOpenCL.so.1.

Since you are running Ubuntu 14.04.x there is a Known Ubuntu Verified Bug that causes the xorg.conf to be overwritten on each boot. This will prevent initializing one of the GPUs, I can verify this Bug affects my ATI systems, https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489 ...I'm on that list. You might as well apply the simple fix just in case that makes a difference. All you have to do is add some comments Exactly where this post indicates they should go. I can verify this also fixes the problem on my Ubuntu 14.04.x systems, http://askubuntu.com/questions/453902/problem-in-setting-up-amd-dual-graphics-trinity-radeon-hd-7660g-and-thames-ra/477006#477006 There is an Option B in that post, but I've never tried it. I applied Option A.
ID: 1839711 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1839718 - Posted: 3 Jan 2017, 0:50:16 UTC - in response to Message 1839691.  
Last modified: 3 Jan 2017, 0:53:25 UTC

No go, still not detecting the GPU's.

I am beginning to think it is an OpenCL issue or something. I tried to install OpenCL 2.0 but I cannot get it to install as it keep telling me that I am missing the Kernel Headers.

But as far as I can tell they are there.

sudo ./amd-driver-installer-14.41-x86.x86_64.run
Created directory fglrx-install.fdpJvu
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-14.41.................
====================================================================
AMD Catalyst(TM) Proprietary Driver Installer/Packager
=====================================================================
ERROR: Please install the required pre-requisites before proceeding with AMD Catalyst installation. Please check file usr/share/ati/fglrx-install.log for more details.

cat fglrx-install.log
NOTE: If your system has logged the missing packages required for installation, install them in the order as per the log file to resolve package-dependency issues.
fglrx installation requires that the system has kernel headers. /lib/modules/4.4.0-57-generic/build/include/linux/version.h cannot be found on this system.
Install kernel headers using the command apt-get install linux-headers-4.4.0-57-generic.

sudo apt-get install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-4.4.0-57-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

clinfo
I: ICD loader reports no usable platforms
ID: 1839718 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1839721 - Posted: 3 Jan 2017, 1:22:35 UTC - in response to Message 1839718.  
Last modified: 3 Jan 2017, 1:35:58 UTC

try:
sudo apt-get update
sudo apt-get install build-essential

and try again [if it installs something]. Probably already installed, and not mentioned in the dependencies, but can't see any installer building kernel modules without it. There is probably other stuff missing if that package is missing, but at least would probably point to needing to setup for kernel module building in more detail. [The display mentions a log file with the probably correct order for installation... odd that it seems to just stop on Linux Headers...]
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1839721 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1839725 - Posted: 3 Jan 2017, 1:36:48 UTC - in response to Message 1839718.  
Last modified: 3 Jan 2017, 1:51:59 UTC

ERROR: Please install the required pre-requisites before proceeding with AMD Catalyst installation. Please check file usr/share/ati/fglrx-install.log for more details.
cat fglrx-install.log
NOTE: If your system has logged the missing packages required for installation, install them in the order as per the log file to resolve package-dependency issues.
fglrx installation requires that the system has kernel headers. /lib/modules/4.4.0-57-generic/build/include/linux/version.h cannot be found on this system.
Install kernel headers using the command apt-get install linux-headers-4.4.0-57-generic.
clinfo
I: ICD loader reports no usable platforms

Yep, No OpenCL and Other problems as well. To install the drivers from AMD you must install a list of pre-requisites. Go to usr/share/ati/fglrx-install.log and it will show a list of the Files you need to Install.
Somehow you have corrupted kernel headers to boot.
Are you still working Headless or do you have a monitor? It would be easier with a monitor...maybe.
You need to remove the fglrx drivers that are somehow showing OpenCL on the CPU but says no usable platforms. If it were me I'd switch to the console, login, then stop lightdm with sudo stop lightdm
and then remove the fglrx drivers with sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
Then I'd install the Repository drivers that don't require pre-requisites, sudo apt-get install fglrx
Reboot, and work from the monitor. You are probably going to have to boot to an earlier kernel, then go to /boot and remove all the files that have 4.4.0-57 in the name. Then you can reinstall the 4.4.0-57 headers.
Maybe Juha has a better method. If it were me, since it's a New install, I'd copy my /home/BOINC folder to another partition/USB drive and do a clean install. Then I'd copy my BOINC folder back to the New Home folder, set the execute bits, and BOINC wouldn't miss a beat once everything else was added back. I hate to start with a new system having such problems, there are probably more problems as yet undiscovered.
ID: 1839725 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1840229 - Posted: 5 Jan 2017, 22:09:44 UTC - in response to Message 1839718.  

ERROR: Please install the required pre-requisites before proceeding with AMD Catalyst installation.


And before installing the required pre-requisites read the release notes to see what they are. Your kernel is too new. Even the last fglrx supports kernels only up to 3.19. fglrx is very picky on what it supports. You need to match Xorg (if you use X) and kernel versions both. You may have better luck backing to an earlier point release of Ubuntu 14.04.

fglrx used to use X to load kernel modules, set up device nodes and all that. Since 14.12 Omega it's supposed to no longer require X but you may need to run the first OpenCL program as root so that the OpenCL runtime can do whatever it needs. Read the discussion in Guide to run OpenCL headless, without X server and as normal user.
ID: 1840229 · Report as offensive
Profile Mitchell Tuckness
Volunteer tester
Avatar

Send message
Joined: 16 Apr 99
Posts: 46
Credit: 21,421,544
RAC: 5
United States
Message 1840533 - Posted: 7 Jan 2017, 4:40:25 UTC - in response to Message 1840229.  
Last modified: 7 Jan 2017, 4:41:37 UTC

ERROR: Please install the required pre-requisites before proceeding with AMD Catalyst installation.


And before installing the required pre-requisites read the release notes to see what they are. Your kernel is too new. Even the last fglrx supports kernels only up to 3.19. fglrx is very picky on what it supports. You need to match Xorg (if you use X) and kernel versions both. You may have better luck backing to an earlier point release of Ubuntu 14.04.

fglrx used to use X to load kernel modules, set up device nodes and all that. Since 14.12 Omega it's supposed to no longer require X but you may need to run the first OpenCL program as root so that the OpenCL runtime can do whatever it needs. Read the discussion in Guide to run OpenCL headless, without X server and as normal user.


Yeah, I even tried 14.0.4.4 and 14.0.4.1 and still only seeing one card. I am beginning to think it might be the motherboard. I have two more identical ones, I am going to swap it out and give it a go. I also purchased an 8 Core AMD CPU and a Gigabyte Motherboard so when they arrive I am going to give them a try.

If anyone know places that sell used video cards in bulk let me know :) Looking to get 6 RX 470's. Those should work with the new drivers, kernel and give me a nice crunch base. Thinking of using it for the Seti@home Bitcoin donation campaign @ http://www.bitcoinutopia.net/bitcoinutopia/ if I can get them working.
ID: 1840533 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 34744
Credit: 261,360,520
RAC: 489
Australia
Message 1840540 - Posted: 7 Jan 2017, 5:14:42 UTC

Can you show us the 1st 30-40 lines of your BOINC messages?

Cheers.
ID: 1840540 · Report as offensive
1 · 2 · Next

Message boards : Number crunching : Unable to get ATi GPU's to Crunch in Ubuntu


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