Message boards : Server and website : Question on server msg "Fermi Class GPU not supported by cuda2.2"
Author | Message |
---|---|
Getting a interesting message from the server: "Fermi Class GPU not supported by cuda2.2" | |
ID: 19211 | Rating: 0 | rate:
![]() ![]() ![]() | |
But you still receive the workunits? | |
ID: 19212 | Rating: 0 | rate:
![]() ![]() ![]() | |
yes, I do. Which begs the question, what is the intention of the server message? | |
ID: 19217 | Rating: 0 | rate:
![]() ![]() ![]() | |
Is anyone else having the same problem? | |
ID: 19227 | Rating: 0 | rate:
![]() ![]() ![]() | |
Is anyone else having the same problem? Only if the BOINC work request includes a request for CPU work. 04/11/2010 09:25:18 | GPUGRID | Sending scheduler request: To fetch work. 04/11/2010 09:25:18 | GPUGRID | Requesting new tasks for NVIDIA GPU 04/11/2010 09:25:18 | GPUGRID | [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs 04/11/2010 09:25:18 | GPUGRID | [sched_op] NVIDIA GPU work request: 345.48 seconds; 0.00 GPUs 04/11/2010 09:25:20 | GPUGRID | Scheduler request completed: got 1 new tasks 04/11/2010 09:25:20 | GPUGRID | [sched_op] Server version 611 04/11/2010 09:25:20 | GPUGRID | Project requested delay of 31 seconds 04/11/2010 09:25:20 | GPUGRID | [sched_op] estimated total CPU task duration: 0 seconds 04/11/2010 09:25:20 | GPUGRID | [sched_op] estimated total NVIDIA GPU task duration: 25146 seconds 04/11/2010 09:25:20 | GPUGRID | [sched_op] Deferring communication for 31 sec 04/11/2010 09:25:20 | GPUGRID | [sched_op] Reason: requested by project 04/11/2010 09:25:22 | GPUGRID | Started download of 138-KASHIF_HIVPR_n1_bound_cl_ba2-50-LICENSE ... 04/11/2010 09:37:53 | GPUGRID | Sending scheduler request: To fetch work. 04/11/2010 09:37:53 | GPUGRID | Requesting new tasks for CPU 04/11/2010 09:37:53 | GPUGRID | [sched_op] CPU work request: 1.00 seconds; 0.23 CPUs 04/11/2010 09:37:53 | GPUGRID | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 GPUs 04/11/2010 09:37:55 | GPUGRID | Scheduler request completed: got 0 new tasks 04/11/2010 09:37:55 | GPUGRID | [sched_op] Server version 611 04/11/2010 09:37:55 | GPUGRID | Message from GPUGRID: No work sent 04/11/2010 09:37:55 | GPUGRID | Message from GPUGRID: Fermi-class GPU not supported by cuda2.2 04/11/2010 09:37:55 | GPUGRID | Message from GPUGRID: (reached limit of 2 GPU tasks in progress) 04/11/2010 09:37:55 | GPUGRID | Project requested delay of 31 seconds (BOINC test version 6.12.4, host 43404, GTX 470) | |
ID: 19230 | Rating: 0 | rate:
![]() ![]() ![]() | |
Have you deselected "Use Central Processing Unit (CPU)" in GPUGrid Preferences? | |
ID: 19232 | Rating: 0 | rate:
![]() ![]() ![]() | |
Have you deselected "Use Central Processing Unit (CPU)" in GPUGrid Preferences? Oh dear. Sorry, but that remark calls for a history lesson. You'll be aware that there are three entries on the preferences page (there should be four, but that's a BOINC problem we'll come to later). They are: Use NVIDIA GPU if present (enforced by 6.10+ clients) Use Graphics Processing Unit (GPU) if available Use Central Processing Unit (CPU) The lower pair (believe me, I know about this stuff) control whether or not the GPU/CPU are actually used by work already present on your computer. But they do not control work fetch requests. The client would still request CPU work, even if the result would be a refusal, as now. They are old code, and shouldn't really be necessary any more. The upper one - which should be paired with a matching "Use CPU (Enforced by version 6.10+)" - actually appeared because of this email, which I sent to the boinc_dev mailing list on 26 September 2009: Following on from my previous thought, it seems that we aren't paying enough These two do control work fetch requests. If I were able to select "Use CPU (Enforced by version 6.10+)", then the client wouldn't issue CPU work requests, and the fact that BOINC has a rogue error message would be conveniently hidden from view. In fact, GPUGrid already has that control, but it's hidden from view. If GPUGrid were to install a dummy app defined as a CPU app, the control would appear (defaulted, unfortunately, to 'yes'): we'd be able to flip it to 'no': and the error messages would go away, along with a small number of completely unnecessary CPU work requests. That's what AQUA have done with their dummy CUDA app. But I don't recommend it. BOINC would automatically pick up the presence of the CPU app (not knowing that it was a dummy), and start advertising the project as CPU-capable. That would cause even more confusion than this misleading error message has already done. Everything I've just said applies equally to the "Use ATI GPU (Enforced by version 6.10+)" control, likewise already present in this project's code, but hidden because no ATI application has been installed (yet). To my mind, it would be better if these hidden controls could send the 'no' signal, so the work requests could be inhibited for non-existent plan_classes. As and when an ATI or CPU application is installed for real, the controls would become visible (presumably still defaulted to yes) and active under user control - and the automatic updating of the 'supported platforms' list at BOINC projects would work - truthfully - as designed. Please join me in calling for this (belated) change. | |
ID: 19234 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thanks Richard, I forgot the lower config was no longer applicable. I'm rather more vaguely aware of long running problems in this area; I seem to have read more speculative posts than factual posts about this issue. You seem to have fuller grasp of the picture than most, if not all, as you point out a method to remedy this. From the end user point of view, it's not fun trying to run Betas and getting unrelated error messages that could have been systemically removed a year ago, one of many such annoyances with GPU crunching. I get the general impression that GPU’s are a pain in the side of Berkeley, and GPU related problems tend to be ignored rather than dealt with. For what it's worth I would belatedly support your motion. Do you think they want to push for Boinc server updates? | |
ID: 19275 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi GDF, | |
ID: 19998 | Rating: 0 | rate:
![]() ![]() ![]() | |
I'm getting the same error message from the server, have been for a while, but now no new work units. GTX460 WIN7-64bit. | |
ID: 20044 | Rating: 0 | rate:
![]() ![]() ![]() | |
Same situation with the error message. It's been going on for quite awhile now. Looking at my tasks here on the site, it seems I completed two about a week ago...but nothing much else. Is there just not much of a demand for Fermi class GPUs right now...? I would find that surprising. | |
ID: 20243 | Rating: 0 | rate:
![]() ![]() ![]() | |
I fixed it shortly after this post by checking the "Join" tab above. First I downgraded BOINC to the recommended version, then I installed the CUDA3.1 (developer) drivers. | |
ID: 20246 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Server and website : Question on server msg "Fermi Class GPU not supported by cuda2.2"