I did a little more investigation.
Intel drivers have been in wrong directories, most likely caused by automatic installation from windows.
So I thought Intel might be a good source for getting the correct drivers.
Edit: might be a little bit tricky because all GPU's have nr. 0 now ...
Drivers installed via Windows Update almost never have the extra parts required for OpenCL, CUDA or what not. It's always recommended to get the drivers from Intel, Nvidia or AMD directly.
No problem with the GPU nr. being 0. Both my 660Ti and the HD 4000 is nr. 0 and it still works.
The messages now show
25.06.2013 13:30:22 | | Local time is UTC +2 hours
25.06.2013 13:30:22 | | VirtualBox version: 4.2.12
25.06.2013 13:30:22 | | CAL: ATI GPU 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (CAL version 1.4.1741, 2048MB, 2008MB available, 7488 GFLOPS peak)
25.06.2013 13:30:22 | | CAL: ATI GPU 1: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (CAL version 1.4.1741, 1024MB, 991MB available, 4368 GFLOPS peak)
25.06.2013 13:30:22 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (driver version 1214.3 (VM), device version OpenCL 1.2 AMD-APP (1214.3), 2048MB, 2008MB available, 7488 GFLOPS peak)
25.06.2013 13:30:22 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (driver version 1214.3 (VM), device version OpenCL 1.2 AMD-APP (1214.3), 2048MB, 2008MB available, 7488 GFLOPS peak)
25.06.2013 13:30:22 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 2500 (driver version 9.18.10.3165, device version OpenCL 1.2, 1624MB, 1624MB available, 17 GFLOPS peak)
25.06.2013 13:30:22 | | No NVIDIA library found
Don't worry about different devices being Device 0, they will show up as CAL device 0, 1, 2, etc, or Cuda device 0, 1, 2, etc, or as OpenCL device 0, 1, 2 etc for a particular vendors platform, ie, AMD APP, Nvidia CUDA or Intel,
What you shouldn't have is two devices for the AMD APP platform with the same device number, What does CLinfo show? is that right, does Boinc run OpenCL apps on the right AMD GPU, or only on device 0?
I'd be very tempted to go down a few driver versions checking if the devices are displayed properly (fully cleaning out the drivers with the AMD Catalyst Un-install Utility each time) and recheck operation.
Don't worry about different devices being Device 0, they will show up as CAL device 0, 1, 2, etc, or Cuda device 0, 1, 2, etc, or as OpenCL device 0, 1, 2 etc for a particular vendors platform, ie, AMD APP, Nvidia CUDA or Intel,
What you shouldn't have is two devices for the AMD APP platform with the same device number, What does CLinfo show? is that right, does Boinc run OpenCL apps on the right AMD GPU, or only on device 0?
I'd be very tempted to go down a few driver versions checking if the devices are displayed properly (fully cleaning out the drivers with the AMD Catalyst Un-install Utility each time) and recheck operation.
Claggy
ATM I have some ati-wu's in queue, will wait until they are finished. Running on device 0 and device 1. Having gpu-z open twice, both gpu's show a usage of 75% or more. So it's possibly more a ui-problem than a device handling problem.
I rearranged my systems a bit because the gpu's are needed somwhere else, will get them back during the weekend. Is a non-amd system for the moment.
I followed the instructions given earlier and had the app running as 'Lokal'. Finished in a little bit more than 27 min. GPU usage ~98%, temp @ 38° (oversized cooler). Intel i3 3220 @ 3.3GHz Intel HD2500 BM 7.1.17 win7-64 GPU core clock 1050 MHz, GPU mem clock 666.7 MHz Mem usage dedicated 8MB, mem usage dynamic ~400MB GPU power reported as 2.9 W (GPU-Z 0.7.2)
It looks like reserving a thread helps a small bit. And that is odd, because according to task monitor, the task is using only about 5% of a thread (against a full thread reservation by BOINC). So that should mean it has 95% of a thread unused already, so why would manually reserving an additional thread improve anything?
Can't wait for the servers to be upgraded to have an intel check box!
FWIW, I have a couple boxes with both a nvidia discrete GPU + an intel HD 4000, crunching on both, with no monitors connected to either.
RE: I did a little more
Drivers installed via Windows Update almost never have the extra parts required for OpenCL, CUDA or what not. It's always recommended to get the drivers from Intel, Nvidia or AMD directly.
No problem with the GPU nr. being 0. Both my 660Ti and the HD 4000 is nr. 0 and it still works.
RE: The messages now
Don't worry about different devices being Device 0, they will show up as CAL device 0, 1, 2, etc, or Cuda device 0, 1, 2, etc, or as OpenCL device 0, 1, 2 etc for a particular vendors platform, ie, AMD APP, Nvidia CUDA or Intel,
What you shouldn't have is two devices for the AMD APP platform with the same device number, What does CLinfo show? is that right, does Boinc run OpenCL apps on the right AMD GPU, or only on device 0?
I'd be very tempted to go down a few driver versions checking if the devices are displayed properly (fully cleaning out the drivers with the AMD Catalyst Un-install Utility each time) and recheck operation.
Claggy
RE: Don't worry about
ATM I have some ati-wu's in queue, will wait until they are finished. Running on device 0 and device 1. Having gpu-z open twice, both gpu's show a usage of 75% or more. So it's possibly more a ui-problem than a device handling problem.
since clinfo is quite long I post a link.
https://dl.dropboxusercontent.com/u/50246791/clinfo1.txt
I'm using beta-drivers for amd (13.6 beta; 13.5 beta 2 was last clean install).
BTW: when googling for intel driver url's I found this: (sorry, german)
http://www.pcgameshardware.de/CPU-Hardware-154106/News/Open-CL-Intel-Treiber-AMD-Prozessor-1068152/
Maybe it's nonsense, but maybe it helps making some apps a little bit faster.
RE: since clinfo is quite
There is text missing from the beginning, if you do from cmd prompt: clinfo >Output.txt you will get all the text outputed into the Output.txt file.
Claggy
RE: There is text missing
https://dl.dropboxusercontent.com/u/50246791/clinfo2.txt
Is complete now. Windows Power Shell did it.
Alex
I've reported the Boinc
I've reported the Boinc 7.1.17 AMD device reporting problem to the Boinc Alpha list.
Claggy
I rearranged my systems a bit
I rearranged my systems a bit because the gpu's are needed somwhere else, will get them back during the weekend. Is a non-amd system for the moment.
I followed the instructions given earlier and had the app running as 'Lokal'. Finished in a little bit more than 27 min. GPU usage ~98%, temp @ 38° (oversized cooler). Intel i3 3220 @ 3.3GHz Intel HD2500 BM 7.1.17 win7-64 GPU core clock 1050 MHz, GPU mem clock 666.7 MHz Mem usage dedicated 8MB, mem usage dynamic ~400MB GPU power reported as 2.9 W (GPU-Z 0.7.2)
https://dl.dropboxusercontent.com/u/50246791/first%20albert-intel-opencl.PNG
one can follow the progress here: http://albertathome.org/host/6571/tasks
Will it help to keep that running? Requesting new wu's needs babysitting, stays dry for long periods.
RE: I've reported the Boinc
THX; I'm in contact with Charlie Fenton now.
One can follow here:
http://boinc.berkeley.edu/dev/forum_thread.php?id=8140&postid=49733#49733
RE: THX; I'm in contact
Problem solved.
Here are results from my
Here are results from my i7-3770S, no OC of the CPU or GPU. It has no additional discrete GPU. This is with BOINC showing 1CPU+1GPU.
With 1 additional thread reserved, 708 seconds, GPU load 96% flat:
https://albertathome.org/task/988045
With no additional thread reserved, 729 seconds, GPU load was a slightly wobbly ~93%:
https://albertathome.org/task/988042
It looks like reserving a thread helps a small bit. And that is odd, because according to task monitor, the task is using only about 5% of a thread (against a full thread reservation by BOINC). So that should mean it has 95% of a thread unused already, so why would manually reserving an additional thread improve anything?
Can't wait for the servers to be upgraded to have an intel check box!
FWIW, I have a couple boxes with both a nvidia discrete GPU + an intel HD 4000, crunching on both, with no monitors connected to either.
Dublin, California
Team: SETI.USA