Same here. i.e. 0.33 count and cpu 0.05.

Well wile it lasted. Reverted back to 6.10.0 which was good for 48 hours. Now I find a similar not requesting work probs. So now back to 6.5.0 I guess.

snip..
Of course, only time will tell if this works long term which has been the ban of many a "fix" that works for a short while but fails after some time...

LTD and STD are completely broken for ATIs, they don't work at all...CPU and CUDA are not affected.(that's one of the bugs i found)

I'm guessing that there will be a new client released on monday.

---

Join Support science! Joinc Team BOINC United now!

Same here. i.e. 0.33 count and cpu 0.05.

Well wile it lasted. Reverted back to 6.10.0 which was good for 48 hours. Now I find a similar not requesting work probs. So now back to 6.5.0 I guess.

No work at all... so no need to change the client.

LTD and STD are completely broken for ATIs, they don't work at all...CPU and CUDA are not affected.(that's one of the bugs i found)

Ugh...

well, hopefully this will be corrected.

I'm guessing that there will be a new client released on monday.

We can but hope. More likely it will be several days to a couple weeks if the past is any guide.

Any chance you can convert the ATI code to do OpenCL detection and configuration? This is the next, and for awhile, the last big GPU issue aside from getting it to work well ...

Those scheduler bugs are certainly frustrating. After looking like everything was running smoothly I found my machine completely dry for more than eight hours. It refuses to ask for more work from any of my active projects and seems perfectly happy to sit idle. :(

I ended up going back to 6.6.20 this morning as BOINC was not requesting any work from MW even with SETI disabled. It kept saying 0 idle CPU's when there was in fact 4 idle CPU's.

Now we just have to wait for someone to kick the servers here.

---

Any chance you can convert the ATI code to do OpenCL detection and configuration? This is the next, and for awhile, the last big GPU issue aside from getting it to work well ...

OpenCL support can be figured out by looking at the CALVersion numbers.
However, i see no real reason for looking at openCL at all atm.

AFAIK, openCL doesn't even support double precision at it's current state. At least that's what i read in the release docs.

---

Join Support science! Joinc Team BOINC United now!

I have tried 6.6.36 and 6.10.0 (and .1) couldn't geyt any of them to download any MW (won't finish on time) [rubbish] . I'm currently running 6.6.31 as it seems to be the latest version where the scheduler has any idea about what it is doing.

Rob.B

---

I have tried 6.6.36 and 6.10.0 (and .1) couldn't geyt any of them to download any MW (won't finish on time) [rubbish] . I'm currently running 6.6.31 as it seems to be the latest version where the scheduler has any idea about what it is doing.

Hating to rain on your parade ... but, none of the 6.x.y versions have a "good" scheduler.

I only moved on to make it easier to run my GPUs... I would not have "upgraded" otherwise ...

I am only playing with 6.10.1 because it is one of the first that "recognizes" the ATI card I have and as been noted even that is problematical with issues ...

Any chance you can convert the ATI code to do OpenCL detection and configuration? This is the next, and for awhile, the last big GPU issue aside from getting it to work well ...

OpenCL support can be figured out by looking at the CALVersion numbers.
However, i see no real reason for looking at openCL at all atm.

AFAIK, openCL doesn't even support double precision at it's current state. At least that's what i read in the release docs.

Because it is there? :)

So that we can be ahead of the power curve for once?

Even if it does not support DP at this time, there are quite a few projects that are single precision and if we could add OpenCL maybe they would be encouraged to migrate there so that the people with ATI cards would have a choice as to which projects to join.

For now, unless there is another project I missed in my last spate with illness, only two projects with ATI support. (Did The Lattice Project add ATI support?)

Any chance you can convert the ATI code to do OpenCL detection and configuration? This is the next, and for awhile, the last big GPU issue aside from getting it to work well ...

OpenCL support can be figured out by looking at the CALVersion numbers.
However, i see no real reason for looking at openCL at all atm.

AFAIK, openCL doesn't even support double precision at it's current state. At least that's what i read in the release docs.

Because it is there? :)

So that we can be ahead of the power curve for once?

Even if it does not support DP at this time, there are quite a few projects that are single precision and if we could add OpenCL maybe they would be encouraged to migrate there so that the people with ATI cards would have a choice as to which projects to join.

For now, unless there is another project I missed in my last spate with illness, only two projects with ATI support. (Did The Lattice Project add ATI support?)

I don't see how openCL would give ati users a choice since it is only a programming interface. It's not that you can run the code on any GPU or CPU. AFAIK, one still needs to write special apps for NV,ATI and CPU.

---

Join Support science! Joinc Team BOINC United now!

And back to 6.10.1 since 6.6.20 does not understand <coproc>.

At least work is flowing again.

---

I don't see how openCL would give ati users a choice since it is only a programming interface. It's not that you can run the code on any GPU or CPU. AFAIK, one still needs to write special apps for NV,ATI and CPU.

If BOINC supported OpenCL then perhaps more projects than EaH would be looking at OpenCL ... if more projects support GPUs that would give the uses more projects to chose from ... especially if they use ATI cards.

The advantage of OpenCL is that each project would only have to develop one GPU application that would be executable on both GPU types

If BOINC supported OpenCL then perhaps more projects than EaH would be looking at OpenCL ... if more projects support GPUs that would give the uses more projects to chose from ... especially if they use ATI cards.

The advantage of OpenCL is that each project would only have to develop one GPU application that would be executable on both GPU types

Boinc doesn't have to support openCL.

All that boinc needs todo is detect the hardware and driver versions.
The version tag will tell the scheduler if the GPU driver has openCL support and therefor can handle an openCL app.

It's completely up to the projects to rewrite their apps using openCL.

---

Join Support science! Joinc Team BOINC United now!

By the way 6.10.3 has been posted for Windows now.
http://boinc.berkeley.edu/dl/?C=M;O=D

Should be the top option.

---

By the way 6.10.3 has been posted for Windows now.

Will it fetch me MW CPU WUs even though I have set GPU=no and CPU=yes,

I know I have a NVIDIA CUDA which isn't up to MW minimum requirements, but I'm not sure how much longer I can face MW telling me that there is no work available for me :( ;P

---

By the way 6.10.3 has been posted for Windows now.
http://boinc.berkeley.edu/dl/?C=M;O=D

Should be the top option.

I tried it yesterday on my cpu only machine and it didn't recognise my previous install, didn't start boinc.exe and had no projects listed. Downgraded to 6.6.38 and luckily it picked up from where it left off.

Heading away on vacation tomorrow for a week so there's no chance of trialling it on my GPU machines until after I get back - hopefully further bugs will be worked out by then.

By the way 6.10.3 has been posted for Windows now.

Will it fetch me MW CPU WUs even though I have set GPU=no and CPU=yes,

I know I have a NVIDIA CUDA which isn't up to MW minimum requirements, but I'm not sure how much longer I can face MW telling me that there is no work available for me :( ;P

Hi Ice
I have the opposite problem, I'm set to GPU only, but all I'm getting is CPU using 6.10.3. It also downloaded about 200 collatz WUs. So I will run out all my Collatz and see if I get any MW Cuda. I got my new machine up n' running (i7 920 with a gtx 275 in it)Wow its very fast!!
;-p

---

By the way 6.10.3 has been posted for Windows now.

Will it fetch me MW CPU WUs even though I have set GPU=no and CPU=yes,

I know I have a NVIDIA CUDA which isn't up to MW minimum requirements, but I'm not sure how much longer I can face MW telling me that there is no work available for me :( ;P

Hi Ice
I have the opposite problem, I'm set to GPU only, but all I'm getting is CPU using 6.10.3.

I tried that, but with 6.10.2/1 and got a similar result, ie, you get the opposite of what you want ;)

Congrats on the new machine :)

---

Guys...and gals....

It all boils down to ONE THING.....

If you have a setup that's working,
DON'T CHANGE IT!

Let someone else be the guinea pig and when you finally see positive results, then MAYBE try it out. Of course, this is just personal opinion.

[Insert maniacal grin here]

Yo-