aticalrt64.dll string is not in the exe

Relevant strings in gpu_detect_v2.exe are:

aticalrt.dll
amdcalrt.dll

No ATI library found.

calInit
calGetVersion
calDeviceGetCount
calDeviceGetAttribs
calShutdown
calDeviceGetInfo
calDeviceGetStatus
calDeviceOpen
calDeviceClose

calInit() missing from CAL library
calDeviceGetCount() missing from CAL library
calDeviceGetAttribs() missing from CAL library

calInit() returned %d
calDeviceGetCount() returned %d
calDeviceGetAttribs() returned %d

No usable CAL devices found

Since the message in your post is 'No usable CAL devices found' and not 'No ATI library found.'
obviously one of aticalrt.dll or amdcalrt.dll is found but the functions used (calDeviceGetCount() ...) do not report CAL devices


Unfortunately BOINC do not report the driver version ('Coprocessors CAL Oland (2048MB)')
http://wuprop.boinc-af.org/show_host_detail.php?hostid=56273

What is the driver version?

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

I've used pretty much every driver version made in the last 3 years, but I'm currently on 12.102.0.0

I added OpenCL detection: http://wuprop.boinc-af.org/download/gpu_detect_v3.exe
Can you test it?

---

Searching for NVIDIA GPU
Found 2 GPUs
NVIDIA Device 0: GeForce GTX 660 Ti (7 multiprocessors @ 1111 MHz)
NVIDIA Device 1: GeForce GTX 660 (5 multiprocessors @ 1033 MHz)
Searching for ATI/AMD GPU
Found 1 GPU
ATI/AMD Device 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (target: 8) (18 multiprocessors @ 725 MHz)

Got an appcrash when running it:
Faulting application name: gpu_detect_v3.exe, version: 0.0.0.0, time stamp: 0x51f7fca0
Faulting module name: gpu_detect_v3.exe, version: 0.0.0.0, time stamp: 0x51f7fca0
Exception code: 0xc0000005
Fault offset: 0x00009cc8
Faulting process id: 0x148c

Still get the same result:

Searching for NVIDIA GPU
Failed to seach NVIDIA GPU. See below for more informations
No NVIDIA library found
Searching for ATI/AMD GPU
Failed to seach ATI/AMD GPU. See below for more informations
No usable CAL devices found

I fixed the bug: http://wuprop.boinc-af.org/download/gpu_detect_v3.1.exe
Thanks.

---

Searching for NVIDIA GPU
Failed to seach NVIDIA GPU. See below for more informations
No NVIDIA library found
Searching for ATI/AMD GPU
Found 3 GPUs
ATI/AMD Device 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (target: 20) (32 multiprocessors @ 925 MHz)
ATI/AMD Device 1: AMD Radeon HD 7870/7950/7970 series (Tahiti) (target: 20) (32 multiprocessors @ 925 MHz)
ATI/AMD Device 2: AMD Radeon HD 7870/7950/7970 series (Tahiti) (target: 20) (32 multiprocessors @ 925 MHz)
Searching for OpenCL GPU
Found 3 GPUs
Advanced Micro Devices, Inc. Device 2: Tahiti (target: 20) (32 multiprocessors @ 925 MHz) already found as ATI/AMD device 2
Advanced Micro Devices, Inc. Device 2: Tahiti (target: 20) (32 multiprocessors @ 925 MHz) already found as ATI/AMD device 2
Advanced Micro Devices, Inc. Device 2: Tahiti (target: 20) (32 multiprocessors @ 925 MHz) already found as ATI/AMD device 2


Searching for NVIDIA GPU
Found 3 GPUs
NVIDIA Device 0: GeForce GTX 580 (16 multiprocessors @ 1645 MHz)
NVIDIA Device 1: GeForce GTX 590 (16 multiprocessors @ 1260 MHz)
NVIDIA Device 2: GeForce GTX 590 (16 multiprocessors @ 1260 MHz)
Searching for ATI/AMD GPU
Failed to seach ATI/AMD GPU. See below for more informations
No ATI library found.
Searching for OpenCL GPU
Found 3 GPUs
NVIDIA Corporation Device 5177680: GeForce GTX 580 (16 multiprocessors @ 1645 MHz) already found as NVIDIA device 0
NVIDIA Corporation Device 5177680: GeForce GTX 590 (16 multiprocessors @ 1260 MHz) already found as NVIDIA device 2
NVIDIA Corporation Device 5177680: GeForce GTX 590 (16 multiprocessors @ 1260 MHz) already found as NVIDIA device 2

---

Reno, NV
Team: SETI.USA

Searching for NVIDIA GPU
Failed to seach NVIDIA GPU. See below for more informations
NVIDIA drivers present but no GPUs found

Searching for ATI/AMD GPU
Found 1 GPU
ATI/AMD Device 0: AMD Radeon HD 6570/6670/7570/7670 series (Turks) (target: 18) (6 multiprocessors @ 800 MHz)

Searching for OpenCL GPU
Found 1 GPU
Advanced Micro Devices, Inc. Device 0: Turks (target: 18) (6 multiprocessors @ 800 MHz) already found as ATI/AMD device 0

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Success!

Searching for NVIDIA GPU
Failed to seach NVIDIA GPU. See below for more informations
No NVIDIA library found
Searching for ATI/AMD GPU
Failed to seach ATI/AMD GPU. See below for more informations
No usable CAL devices found
Searching for OpenCL GPU
Found 1 GPU
Advanced Micro Devices, Inc. Device 4718592: Oland (target: 25) (6 multiprocessors @ 700 MHz)

Searching for NVIDIA GPU
Found 2 GPUs
NVIDIA Device 0: GeForce GTX 660 Ti (7 multiprocessors @ 1111 MHz)
NVIDIA Device 1: GeForce GTX 660 (5 multiprocessors @ 1033 MHz)
Searching for ATI/AMD GPU
Found 1 GPU
ATI/AMD Device 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (target: 8) (18 multiprocessors @ 725 MHz)
Searching for OpenCL GPU
Found 3 GPUs
Advanced Micro Devices, Inc. Device 0: Cypress (target: 8) (18 multiprocessors @ 725 MHz) already found as ATI/AMD device 0
NVIDIA Corporation Device 0: GeForce GTX 660 Ti (7 multiprocessors @ 1110 MHz) already found as NVIDIA device 0
NVIDIA Corporation Device 0: GeForce GTX 660 (5 multiprocessors @ 1032 MHz) already found as NVIDIA device 1

Is it an issue that for OpenCL they are all Device 0, albeit 'already found'?

Z's 'Device 2' triplet and Device 5177680 looks bit odd. Crossfire and Sli?
Ditto for Sellyme's Device 4718592

(My apologies if the following is something you already know.)

I think your task may be more complicated than just accurately determining which GPUs are present in a computer.

Presumably, you ultimately want to know which GPU an application is running on. That's where things get really convoluted in a multi-gpu system, especially when there's different GPUs from the same manufacturer.

One of PrimeGrid's GPU applications (Genefer) prints copious amounts of information to stderr.txt. From this information comes the following nugget of BOINC behavior: when a GPU task is paused and restarted, it won't necessarily restart on the same GPU it was originally running on.

So you can have an app start to run on a GTX TITAN, then switch to a GT 510, switch back to the GTX TITAN, then finish on a GTX 280, if that's what the computer has installed.

That makes it very difficult to get decent timing numbers from computers with multiple heterogeneous GPUs.

Since the purpose of detecting all the GPUs is likely to gather accurate data for each app on individual GPUs, you'll also have to keep separate statistics when the app switches from one GPU to another.