No Usable GPU found - ATI
10 Jul 2014 2:08:08 UTC
Topic 197634
(moderation:
I have looked thru other threads and can't seem to fix this.
New Linux Mint 17 install after removing Nvidia card. Replaced with AMD R9 270X. I've installed every thing I know of and BM won't pick up the new card.
Wed 09 Jul 2014 10:01:46 PM EDT | | Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu
Wed 09 Jul 2014 10:01:46 PM EDT | | log flags: file_xfer, sched_ops, task
Wed 09 Jul 2014 10:01:46 PM EDT | | Libraries: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Wed 09 Jul 2014 10:01:46 PM EDT | | Data directory: /var/lib/boinc-client
Wed 09 Jul 2014 10:01:46 PM EDT | | OpenCL CPU: Pentium(R) Dual-Core CPU E5400 @ 2.70GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1411.4 (sse2), device version OpenCL 1.2 AMD-APP (1411.4))
Wed 09 Jul 2014 10:01:46 PM EDT | | No usable GPUs found
Wed 09 Jul 2014 10:01:46 PM EDT | | Host name: BOINC1
Wed 09 Jul 2014 10:01:46 PM EDT | | Processor: 2 GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz [Family 6 Model 23 Stepping 10]
Wed 09 Jul 2014 10:01:46 PM EDT | | 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 lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm
Wed 09 Jul 2014 10:01:46 PM EDT | | OS: Linux: 3.13.0-24-generic
Wed 09 Jul 2014 10:01:46 PM EDT | | Memory: 1.95 GB physical, 2.00 GB virtual
Wed 09 Jul 2014 10:01:46 PM EDT | | Disk: 227.14 GB total, 210.96 GB free
Wed 09 Jul 2014 10:01:46 PM EDT | | Local time is UTC -4 hours
Wed 09 Jul 2014 10:01:46 PM EDT | | Config: GUI RPCs allowed from:
Wed 09 Jul 2014 10:01:46 PM EDT | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 11454103; resource share 100
Wed 09 Jul 2014 10:01:46 PM EDT | Einstein@Home | General prefs: from Einstein@Home (last modified 09-Jul-2014 03:06:17)
Wed 09 Jul 2014 10:01:46 PM EDT | Einstein@Home | Computer location: home
Wed 09 Jul 2014 10:01:46 PM EDT | | General prefs: using separate prefs for home
Wed 09 Jul 2014 10:01:46 PM EDT | | Reading preferences override file
Wed 09 Jul 2014 10:01:46 PM EDT | | Preferences:
Wed 09 Jul 2014 10:01:46 PM EDT | | max memory usage when active: 2000.65MB
Wed 09 Jul 2014 10:01:46 PM EDT | | max memory usage when idle: 2000.65MB
Wed 09 Jul 2014 10:01:46 PM EDT | | max disk usage: 100.00GB
Wed 09 Jul 2014 10:01:46 PM EDT | | (to change preferences, visit a project web site or select Preferences in the Manager)
Wed 09 Jul 2014 10:01:46 PM EDT | | gui_rpc_auth.cfg is empty - no GUI RPC password protection
Wed 09 Jul 2014 10:01:46 PM EDT | | Not using a proxy
I don't know what else to put on here to help you help me, so thanks in advance for anything you can do.
Phil
No Usable GPU found - ATI
)
I am NOT a Linux guy, but from my many tries I think you have to install the 'alternate' video card drivers.
Disclaimer: the following
)
Disclaimer: the following procedure has worked for me but use it at your own risk.
Linux Mint 17 is based on Ubuntu 14.04 (Trusty) so I have used the procedure contained in the Unofficial AMD Linux Community (referenced in AMD website).
link: http://wiki.cchtml.com/index.php/Ubuntu_Trusty_Installation_Guide
Notice: this procedure is applicable for kernel releases up to 3.11
To see your kernel level issue the command cat /proc/version_signature
Kernel up to 3.11
Begin the procedure by going to Installing Proprietary Drivers a.k.a. Catalyst/fglrx and read carefully all the steps and install the prerequisite packages.
The installation begins at Installing Catalyst Manually (from AMD/ATI's site) STABLE and last command is "sudo dpkg -i fglrx*.deb"
If your kernel is 3.14 follow the instructions in
Installing Catalyst on kernel >=3.14.0 (3.14.2 including)
(All kernels)
If, after the installation & reboot, the GPU card is not detected by BOINC client issue the following command (term): sudo /etc/init.d/boinc-client restart
Free-DC statistics
BAM! Thank you so much.
)
BAM! Thank you so much. Worked first time thru, just had to use the restart command.
I recommend a moderator make this a sticky. Very nice.
Thanks again.
Phil
Additional question: The
)
Additional question:
The new card is happily crunching away, but the catalyst drive does not seem to have the overclocking and monitoring that the driver did when I was using windows.
Is this normal for the Linux driver? And if so, what are some recommendations for GPU monitoring and clocking?
Thanks
There is a CLI utility called
)
There is a CLI utility called aticonfig (could also be called amdconfig) that gets installed when you install the Catalyst drivers. It has zillions of options for all sorts of things, including setting and monitoring clock speeds and temperatures. It needs to be run as root.
if you run
aticonfig --helpyou will get a listing and explanation of all the options. Be warned that the list extends over a *lot* of pages so you should pipe the output through a scrolling utility (like less) so that you can comfortably browse all the information at leisure. If you scroll down in the output about 300 lines, you'll see a heading about AMD Overdrive (TM) Options. These are probably the ones you want.A couple of useful examples.
aticonfig --od-enableYou need to run this first up to enable AMD Overdrive. This will then allow you to change clock speeds.aticonfig --odgc (or --od-getclocks)This tells you what the clock values currently are.aticonfig --odgt (or --od-gettemperature)Outputs the current temperature.aticonfig --odsc (or --od-setclocks=x,y)Set new values for core and memory clocks. You need to read up on the details about this.aticonfig --odcc (or --od-commitclocks)Make the current clock values 'permanent' - ie survive a reboot.Hope this helps.
Cheers,
Gary.
Geez I love the command
)
Geez I love the command line...not. Lol.
I changed the clocks and the screen went blank and wouldn't come back. Forced a reboot and now the driver appears to be missing. I can't issue any ati commands. Returns a command not found error.
And BM says GPU missing...grr.
Guess I'll reinstall the driver and see what happens.
Don't despair, there is still
)
Don't despair, there is still a chance to fix the problem.
This problem (not recognizing GPU after reboot) is a well-known problem
when you install Boinc Manager/Boinc Client from Software Sources of any
Ubuntu-based Linux distribution.
Just issue the following CLI command after starting Boinc Manager:
sudo /etc/init.d/boinc-client restart
Reason: Boinc client is started before the appropriate GPU driver is loaded
so when you start Boinc Manager there is no driver.
In case you are still having problems, please just post a feedback on this Message Board.
Best regards.
Free-DC statistics
RE: ... I changed the
)
I've seen the problem mentioned where Ubuntu can allow BOINC to start too quickly before the driver is loaded But I really know nothing about that. However, that wouldn't be why your screen went blank when you changed clocks. I guess that would be your card not being able to run with the increased frequencies.
How big an increase did you try to make? I hope you didn't 'commit' the new values before testing that they would still work properly when the card had a crunching load. You need to make small increments and test thoroughly. If you haven't 'committed', a reboot should restore default values and immediately get you out of trouble if an increment is too much for the card to handle. There's no reason to suppose you would need to reinstall the driver.
Cheers,
Gary.
Hi Gary, I really have no
)
Hi Gary,
I really have no idea what happened. I made a small increase in clock speed and it just fritzed out, blank screen.
As I explained in Best Linux Distro for crunching I really stink at command line use. I haven't been around Linux for about 10 years.
So to ease the pain I just returned the card and brought home an Nvidia which is easier for me to use right now.
Many thanks to Sergioclr for the very clear instructions on installing an AMD driver. The install went very well. Just as it turns out AMD is not for me, for now, for Linux. AMD needs to support Linux the way they support Windows and give us a proper driver so that I don't have to feel like it's 1983 and use a command line. Other than this whole GUI thing I like AMD products. There's a reason the top crunchers use them. Just not my cup of tea until they fix that.
Phil