Hi,

Are there any specific requirements for this app? I keep getting the following message:

28.11.2012 19:48:42 | SETI@home Beta Test | [error] App version uses non-existent NVIDIA GPU
28.11.2012 19:48:42 | SETI@home Beta Test | [error] Missing coprocessor for task ap_22my12ad_B0_P0_00137_20121029_05529.wu_3; aborting


I tried resetting the project, but that didn't help.

Looks like a boinc problem, not an app problem.
boinc isn't seeing the GPU properly.

you are running a boinc alpha client - do upgrade to the lastest one and try a reboot.

Initially, i was running 7.0.28, the latest official version. When this problem started appearing, i thought upgrading might help, but from what it looks like, didn't had much luck.

Can you post your Boinc startup messages from the Event Log, the first 20 to 30 lines will do,
Is there anything special about where you got you're GPU drivers from?, ie from DELL, from Microsoft Update, from Nvidia?
And are you doing any type of Remote Desktop onto that host?

Claggy

Hi,

Here are the first few lines:

02.12.2012 13:00:09 | | No config file found - using defaults
02.12.2012 13:00:09 | | Starting BOINC client version 7.0.28 for windows_x86_64
02.12.2012 13:00:09 | | log flags: file_xfer, sched_ops, task
02.12.2012 13:00:09 | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
02.12.2012 13:00:09 | | Data directory: xxxxxxxxxxxxx
02.12.2012 13:00:09 | | Running under account xxxxxxxxx
02.12.2012 13:00:09 | | Processor: 4 AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor [Family 21 Model 1 Stepping 2]
02.12.2012 13:00:09 | | Processor: 2.00 MB cache
02.12.2012 13:00:09 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm svm sse4a osvw ibs xop skinit wdt lwp fma4 page1gb rdtscp
02.12.2012 13:00:09 | | OS: Microsoft Windows 7: Enterprise x64 Edition, Service Pack 1, (06.01.7601.00)
02.12.2012 13:00:09 | | Memory: 7.95 GB physical, 15.95 GB virtual
02.12.2012 13:00:09 | | Disk: 100.01 GB total, 8.46 GB free
02.12.2012 13:00:09 | | Local time is UTC +1 hours
02.12.2012 13:00:09 | | VirtualBox version: 4.2.4
02.12.2012 13:00:09 | | NVIDIA GPU 0: GeForce 9600 GSO (driver version 306.97, CUDA version 5.0, compute capability 1.1, 384MB, 8380697MB available, 490 GFLOPS peak)
02.12.2012 13:00:09 | | OpenCL: NVIDIA GPU 0 (not used): GeForce 9600 GSO (driver version 306.97, device version OpenCL 1.0 CUDA, 384MB, 8380697MB available)
02.12.2012 13:00:09 | | App version needs OpenCL but GPU doesn't support it
02.12.2012 13:00:09 | SETI@home | Application uses missing NVIDIA GPU
02.12.2012 13:00:09 | | App version needs OpenCL but GPU doesn't support it
02.12.2012 13:00:09 | SETI@home | Application uses missing NVIDIA GPU
02.12.2012 13:00:09 | | App version needs OpenCL but GPU doesn't support it
02.12.2012 13:00:09 | SETI@home Beta Test | Application uses missing NVIDIA GPU
02.12.2012 13:00:09 | | App version needs OpenCL but GPU doesn't support it
02.12.2012 13:00:09 | World Community Grid | Application uses missing NVIDIA GPU

Drivers are straight from NVidia site. I don't use RDP as per se, but i have Logmein client installed, which i use occasionally.

Thanks

You don't happen to have the AMD APP SDK installed do you?

What does GPUCapsViewer say about how many OpenCL platforms and devices there are?

You could try a later Boinc, there were fixes for OpenCL detection, as well for the Wacky Nvidia GPU Memory reporting Bug, try Boinc 7.0.38 (7.0.40 is too new and has a few new features/Bugs)

Claggy

You don't happen to have the AMD APP SDK installed do you?

What does GPUCapsViewer say about how many OpenCL platforms and devices there are?

You could try a later Boinc, there were fixes for OpenCL detection, as well for the Wacky Nvidia GPU Memory reporting Bug, try Boinc 7.0.38 (7.0.40 is too new and has a few new features/Bugs)

Claggy

At least v7.0.40 is missing (has corrected) the show-stopper bug which meant that v7.0.38 never made it into official alpha testing.

I've been running v.40 for 24 hours now, with no sign of distress - but then, I didn't jump the gun and assume that Intel GPU support was finished already. It isn't.

You don't happen to have the AMD APP SDK installed do you?

What does GPUCapsViewer say about how many OpenCL platforms and devices there are?

You could try a later Boinc, there were fixes for OpenCL detection, as well for the Wacky Nvidia GPU Memory reporting Bug, try Boinc 7.0.38 (7.0.40 is too new and has a few new features/Bugs)

Claggy

At least v7.0.40 is missing (has corrected) the show-stopper bug which meant that v7.0.38 never made it into official alpha testing.

I've been running v.40 for 24 hours now, with no sign of distress - but then, I didn't jump the gun and assume that Intel GPU support was finished already. It isn't.

Yes, i remember now, Boinc 7.0.38 is missing the BOINC entry in the Start Menu, along with the Boinc Manager link,

Boinc is never fully finished, there's always something to fix, or add to, the Intel GPU changes will probably go on for months,

Claggy

Hi Claggy,

GPUCaps reports 2 platforms:

1: NVIDIA CUDA
2: AMD Accelerated Parallel Processing

And devices from what i could pick up, is 1 per platform. Both of them are listed as full platform: OpenCL 1.1 CUDA 4.2.1 FULL_PROFILE & OpenCL 1.2 AMD-APP (937.2) FULL_PROFILE

As per AMD APP SDK, i think i might have it, as it came bundled with chipset drivers from ASUS. Honestly, i don't know of any purpose for those SDK to be present, but if you think those are the source of the problem, i'm more than happy to remove them :)

Thanks

Hi Claggy,

GPUCaps reports 2 platforms:

1: NVIDIA CUDA
2: AMD Accelerated Parallel Processing

And devices from what i could pick up, is 1 per platform. Both of them are listed as full platform: OpenCL 1.1 CUDA 4.2.1 FULL_PROFILE & OpenCL 1.2 AMD-APP (937.2) FULL_PROFILE

As per AMD APP SDK, i think i might have it, as it came bundled with chipset drivers from ASUS. Honestly, i don't know of any purpose for those SDK to be present, but if you think those are the source of the problem, i'm more than happy to remove them :)

Thanks

I think having the AMD APP installed is part of the problem, you can eithier uninstall it, But you might find the Nvidia OpenCL support goes missing, in which case uninstall and reinstall the Nvidia drivers, (Both AMD & Nvidia drivers used to install & remove OpenCL.dll, later drivers install separate OpenCL.dll's for AMD or Nvidia)

Or upgrade to a later Boinc, eithier 7.0.36 or 7.0.40, Boinc 7.0.35 had the following fix which suggests that detection wasn't always working correctly:

client: If OpenCL detection gets an error for a platform or device, finish detection of the remaining platforms and / or devices.

Claggy

Fun never stops :)

I've upgraded my client to 7.0.40, and now, though missing coprocessor has disappeared from the logs, i have fresh one:

10.12.2012 22:46:42 | | Couldn't get Device IDs for platform #0: error -1

Also, i tried updating to latest beta NVidia drivers, which, unfortunately, didn't help that much.

At the end, i ended up installing 7.0.28, and, somehow, seems to be ok, at least for missing coprocessor. Now i just have error about missing OpenCL :)

10.12.2012 23:05:54 | | No config file found - using defaults
10.12.2012 23:05:54 | | Starting BOINC client version 7.0.28 for windows_x86_64
10.12.2012 23:05:54 | | log flags: file_xfer, sched_ops, task
10.12.2012 23:05:54 | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
10.12.2012 23:05:54 | | Data directory: E:\Programs\Boinc
10.12.2012 23:05:54 | | Running under account bigblue
10.12.2012 23:05:54 | | Processor: 4 AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor [Family 21 Model 1 Stepping 2]
10.12.2012 23:05:54 | | Processor: 2.00 MB cache
10.12.2012 23:05:54 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm svm sse4a osvw ibs xop skinit wdt lwp fma4 page1gb rdtscp
10.12.2012 23:05:54 | | OS: Microsoft Windows 7: Enterprise x64 Edition, Service Pack 1, (06.01.7601.00)
10.12.2012 23:05:54 | | Memory: 7.95 GB physical, 15.95 GB virtual
10.12.2012 23:05:54 | | Disk: 100.01 GB total, 10.91 GB free
10.12.2012 23:05:54 | | Local time is UTC +1 hours
10.12.2012 23:05:54 | | VirtualBox version: 4.2.4
10.12.2012 23:05:54 | | NVIDIA GPU 0: GeForce 9600 GSO (driver version 310.70, CUDA version 5.0, compute capability 1.1, 384MB, 8380644MB available, 490 GFLOPS peak)
10.12.2012 23:05:54 | | App version needs OpenCL but GPU doesn't support it
10.12.2012 23:05:54 | SETI@home | Application uses missing NVIDIA GPU
10.12.2012 23:05:54 | | App version needs OpenCL but GPU doesn't support it
10.12.2012 23:05:54 | SETI@home | Application uses missing NVIDIA GPU
10.12.2012 23:05:54 | | App version needs OpenCL but GPU doesn't support it
10.12.2012 23:05:54 | SETI@home Beta Test | Application uses missing NVIDIA GPU
10.12.2012 23:05:54 | | App version needs OpenCL but GPU doesn't support it
10.12.2012 23:05:54 | World Community Grid | Application uses missing NVIDIA GPU
10.12.2012 23:05:54 | | Version change (7.0.40 -> 7.0.28)

Beats me what it wants now. I'll probably have to take care after Xmas, as i will be away for 10 or so days.

Thanks for the support and time.

Regards,
Alex

Accordingly your BOINC log you doesn't have OpenCL support and OpenCK AP requires it. So, you need to fix your config still.

Well, it seems after various tweaks, it started to behave properly. I've updated Boinc client to 7.0.44, then installed latest AMD SDK kit, et voila - no more errors regarding coprocessor or any other 'funky' message.

Thank all for patience and assistance.