In the boinc event log, I do have line items such as "Requesting new tasks for CPU and AMD/ATI GPU". So seti@home is aware of my graphics cards and trying to use them.

However, using MSI Afterburner, I don't see any usage of either of my two graphics cards (gpu's), although all eight CPUs listed show full utilization. I've checked my preferences and they do say to use the graphics cards, and the project is set to use gpu's based on preferences.

The graphics cards are AMD Radeon FirePro D700 cards circa 2015, and there are two of them (I am running a Mac Pro under Bootcamp, Windows 10 all up-to-date).

Currently I am only running seti@home under boinc (meaning, no other boinc projects).

When using this machine for triple-a gaming, such as Battlefront, I do see full utilization of both graphics cards.

Is the issue that not all seti@home (and AstroPulse - I see those in the log too) tasks will use the GPU(s)? Or is there something else that could be wrong? If so, how can that be troubleshooted?

---

Easiest thing is to post the first 30 lines of the start log after a restart so people can look at it

Easiest thing is to post the first 30 lines of the start log after a restart so people can look at it

That will answer what version of drivers are installed and if the right "thingys" (a well known technical term) to allow gpu processing are available.

I remember something about ATI cards being cranky if the "wrong" (sometimes that appears to be "current") drivers are installed.

Tom

---

A proud member of the OFA (Old Farts Association).

Great thanks - here's the error:

6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it

How can I go about fixing this?

Here's the log, pasted below, from last restart - and indeed, it does show an issue that OpenCL is not supported.
Note: While currently I am only running seti@home, usually I run 20% climateprediction.net, so the log below may show some of those messages.

6/9/2017 11:05:56 PM | | cc_config.xml not found - using defaults
6/9/2017 11:05:56 PM | | Starting BOINC client version 7.6.33 for windows_x86_64
6/9/2017 11:05:56 PM | | log flags: file_xfer, sched_ops, task
6/9/2017 11:05:56 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
6/9/2017 11:05:56 PM | | Data directory: C:\ProgramData\BOINC
6/9/2017 11:05:56 PM | | Running under account chris
6/9/2017 11:05:57 PM | | CAL: ATI GPU 0: AMD Radeon HD 7870/7950/7970/R9 280/R9 280X series (Tahiti) (CAL version 1.4.1848, 6144MB, 6104MB available, 8704 GFLOPS peak)
6/9/2017 11:05:57 PM | | CAL: ATI GPU 1: AMD Radeon HD 7870/7950/7970/R9 280/R9 280X series (Tahiti) (CAL version 1.4.1848, 6144MB, 6104MB available, 8704 GFLOPS peak)
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | | App version needs OpenCL but GPU doesn't support it
6/9/2017 11:05:57 PM | SETI@home | Application uses missing ATI GPU
6/9/2017 11:05:57 PM | SETI@home | Missing coprocessor for task 21fe09ab.6701.7843.8.35.104_1
6/9/2017 11:05:57 PM | SETI@home | Missing coprocessor for task 21fe09ab.6701.7843.8.35.48_1
6/9/2017 11:05:57 PM | | Host name: DESKTOP-5O0I0D4
6/9/2017 11:05:57 PM | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz [Family 6 Model 62 Stepping 4]
6/9/2017 11:05:57 PM | | 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 htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes f16c rdrandsyscall nx lm avx vmx smx tm2 dca pbe fsgsbase smep
6/9/2017 11:05:57 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.14393.00)
6/9/2017 11:05:57 PM | | Memory: 31.97 GB physical, 36.72 GB virtual
6/9/2017 11:05:57 PM | | Disk: 465.87 GB total, 49.71 GB free
6/9/2017 11:05:57 PM | | Local time is UTC -7 hours
6/9/2017 11:05:57 PM | climateprediction.net | URL http://climateprediction.net/; Computer ID 1372977; resource share 20
6/9/2017 11:05:57 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7735257; resource share 80
6/9/2017 11:05:57 PM | climateprediction.net | General prefs: from climateprediction.net (last modified 11-Mar-2017 12:26:48)
6/9/2017 11:05:57 PM | climateprediction.net | Computer location: home
6/9/2017 11:05:57 PM | climateprediction.net | General prefs: no separate prefs for home; using your defaults
6/9/2017 11:05:57 PM | | Reading preferences override file
6/9/2017 11:05:57 PM | | Preferences:
6/9/2017 11:05:57 PM | | max memory usage when active: 3273.91MB
6/9/2017 11:05:57 PM | | max memory usage when idle: 29465.16MB
6/9/2017 11:05:57 PM | | max disk usage: 15.00GB
6/9/2017 11:05:57 PM | | don't compute while active
6/9/2017 11:05:57 PM | | don't use GPU while active
6/9/2017 11:05:57 PM | | suspend work if non-BOINC CPU load exceeds 40%
6/9/2017 11:05:57 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
6/9/2017 11:05:57 PM | SETI@home | Task 21fe09ab.6701.7843.8.35.104_1 is 150.28 days overdue; you may not get credit for it. Consider aborting it.
6/9/2017 11:05:57 PM | SETI@home | Task 21fe09ab.6701.7843.8.35.48_1 is 150.28 days overdue; you may not get credit for it. Consider aborting it.
6/9/2017 11:05:57 PM | | Running CPU benchmarks
6/9/2017 11:05:57 PM | | Suspending computation - CPU benchmarks in progress
6/9/2017 11:05:57 PM | | Suspending network activity - computer is in use
6/9/2017 11:06:28 PM | | Benchmark results:
6/9/2017 11:06:28 PM | | Number of CPUs: 8
6/9/2017 11:06:28 PM | | 4002 floating point MIPS (Whetstone) per CPU
6/9/2017 11:06:28 PM | | 10006 integer MIPS (Dhrystone) per CPU
6/9/2017 11:11:24 PM | | Resuming network activity
6/9/2017 11:11:24 PM | SETI@home | Starting task 20oc08aa.25787.259728.10.37.83_1
6/9/2017 11:11:24 PM | SETI@home | Starting task blc04_2bit_guppi_57835_04054_HIP39896_0020.15693.818.23.46.118.vlar_1
6/9/2017 11:11:24 PM | SETI@home | Starting task 28au08af.21850.6616.6.33.39.vlar_1
6/9/2017 11:11:24 PM | SETI@home | Starting task blc04_2bit_guppi_57835_04842_HIP39896_0022.6402.818.24.47.223.vlar_2

---

Not sure who is the best with AMD cards, I think it's TBar.

Let's see what he says

Here is some additional detail I got from the built-in ATI manager program:

Graphics Chipset
AMD Radeon FirePro D700 (Bootcamp edition by bootcampdrivers.com). It works.

It does have OpenCL: OpenCLâ„¢ Version 21.19.164.1

Here is all the detail:

Radeon Pro and AMD FirePro Settings Version - 2016.1115.1552.28539
Driver Packaging Version - 16.40.3211-161115a-308829E
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1571
Direct3D® Version - 9.14.10.01221
OpenGL® Version - 6.14.10.13456
OpenCLâ„¢ Version - 21.19.164.1
AMD Mantle Version - Not Available
AMD Mantle API Version - Not Available
AMD Audio Driver Version - 10.0.1.0
Vulkanâ„¢ Driver Version - 1.3.0
Vulkanâ„¢ API Version - 1.0.26

---

It appears you're using the Apple Bootcamp driver. Try downloading the AMD drivers for Windows 10. Those will probably work.
Why you're using a Mac to run BOINC in Widows is a mystery, as far as I know there isn't any problems running that machine with BOINC in OSX.

Thanks; yes, I am on Windows to run some games that don't run on macOS, that guests and myself want to play.

Because of that, currently I have this machine almost always booted to Windows. I do for sure have Boinc installed also on the macOS partition for this machine.

I think that if running bootcamp, it is required to run the bootcamp drivers, as the stock drivers for Windows will not work with the Mac hardware.

I've also cross-posted this issue at the driver source I use: http://bootcampdrivers.freeforums.net/thread/96/get-opencl-support

---

I think that if running bootcamp, it is required to run the bootcamp drivers, as the stock drivers for Windows will not work with the Mac hardware...

That must be something new. I've run older versions of Windows on my Mac Pro since 2008 and never had any problems using the Windows drivers in Windows. I stopped that shortly after I was able to compile and run SETI Apps on my Mac. That was a couple years ago.

Are you referring to the cylindrical-style Mac Pro?

---

As with any GPU manufacturer, never use Windows supplied drivers as they are always lacking something.

Only get your drivers from the manufacturers' website if you want all the functions of your GPU working. ;-)

Cheers.

Are you referring to the cylindrical-style Mac Pro?

Nope, I refused to spend money on a trashcan that can't be upgraded. I did look around and it appears they've turned running Windows on a Mac in Bootcamp into a real nightmare. Unless you're willing to jump thru some nasty hoops you're stuck with the Bootcamp drivers which apparently don't work for SETI. It's hard to decide if its Windows 10 or Apples fault, probably both. You use to be able to just install Windows on a Mac using a dfferent HD/SSD without using the Bootcamp drivers, I suspect you still can but it would take a while to track down all the drivers. I would recommend that when you want to run SETI, you boot into OSX and run it there. It's probably the easiest thing to do.
Good Luck.

Thanks, and that sounds like some good research that you did on this specific issue. Luckily, more and more games are working on macOS, and support for the Xbox Elite Controller is in the works.

---

E.g., support such as https://github.com/360Controller/360Controller#wireless-xbox-one-controllers

---