My profile is set to no CPU, only NVidia and ATI. I have two ATI cards in this box, a 4850 and a 5870. Catalyst 9.12, Windows 7 64 Bit. All the client would do is download CPU WUs... something is still not right server side. I have BOINC 6.10.25 loaded. Went back to the optomized app.

---

this may be already said but have you guys looked in the

Boinc Manager Pref's???? in the pross usage tab do you guys

have "Use GPU while computer is in use" checked?????

if not you wont download any wu's let alone crunch any....

if this has already been said then dont pay attention

to my ramblings :) :)

---

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

Yes, that seems to be the case and i think that it is due to the scheduler version used.

if you take a look at the sched_reply*.xml in you boinc directory you'll see that MW uses <scheduler_version>610</scheduler_version>

Up to date projects like AQUA or Collatz use <scheduler_version>611</scheduler_version>

---

Join Support science! Joinc Team BOINC United now!

I still crunch with 64bit app 0.20b. Should I reset/reattach the project or do nothing to get the new app?

I crunch on a 3870 ATI card, 64bit Vista, BOINC 6.10.18

I would suggest you stick with the optimized app until they sort out the problems with the scheduler.

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

Yes, that seems to be the case and i think that it is due to the scheduler version used.

if you take a look at the sched_reply*.xml in you boinc directory you'll see that MW uses <scheduler_version>610</scheduler_version>

Up to date projects like AQUA or Collatz use <scheduler_version>611</scheduler_version>

We should be using the most up-to-date version of the BOINC server code... I'm wondering if our update script isn't working correctly, given the recent problems. I'm going to take a look at this.

--Travis

May be OT - I just noticed a couple of WUs with computation errors. Tried a manual update to clear the air.
'Message from server: Server error: recompile needed'.

---

Cheers,

PeterV

.

May be OT - I just noticed a couple of WUs with computation errors. Tried a manual update to clear the air.
'Message from server: Server error: recompile needed'.

Yeah I'm seeing the same issue. Part of the problem is I need to stop the web server to update the file upload handler and scheduler... and I don't yet have access privileges to do that. I've contacted our labstaff again (woo) and as we're kind of high priority on their to-do lists due to our previous issues, hopefully we'll be able to fix the problem soon.

May be OT - I just noticed a couple of WUs with computation errors. Tried a manual update to clear the air.
'Message from server: Server error: recompile needed'.

Yeah I'm seeing the same issue. Part of the problem is I need to stop the web server to update the file upload handler and scheduler... and I don't yet have access privileges to do that. I've contacted our labstaff again (woo) and as we're kind of high priority on their to-do lists due to our previous issues, hopefully we'll be able to fix the problem soon.

Things are looking up! The update has solved the ATI GPU detection and work for the new app is flowing and validating nicely. Good job!

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

Yes, that seems to be the case and i think that it is due to the scheduler version used.

if you take a look at the sched_reply*.xml in you boinc directory you'll see that MW uses <scheduler_version>610</scheduler_version>

Up to date projects like AQUA or Collatz use <scheduler_version>611</scheduler_version>

Is the scheduler version looking correct on your end now?

FINALLY!!!!!!! and a couple more !!!s
After Divide Overflow's comment #35311 I tried attaching my 5870 again [for the umpteenth time].
This time it worked and my 5870 is finally crunching MW.]
Thanks, Travis.

Unfortunately my CPU is also now crunching MW, when it should be crunching primegrid. is there a way to set this up so it only crunches mw on gpu?

---

Cheers,

PeterV

.

<scheduler_version>611</scheduler_version>

All good this end.

Thanks Travis.

---

Is the scheduler version looking correct on your end now?

Yes, <scheduler_version>611</scheduler_version> is shown in my sched_reply_milkyway.cs.rpi.edu_milkyway.xml file.

Computer now shows GPU and BOINC version, and tasks now show Run time.

All tasks completed of the last batch downloaded remain in pending so far.

Well, it is slowly picking up ATI and CPU work units, and it will be nice when it grabs a few for the green goblin. Thank you for promptly fixing the problem.

Unfortunately my CPU is also now crunching MW, when it should be crunching primegrid. is there a way to set this up so it only crunches mw on gpu?

Verstapp, go into your account > MilkyWay@home preferences and remove the check for "Use CPU".

All validating now.

I am still using the ATI app_info.xml. It is now recognised as an anonymous platform version. After the upgrade I had some trouble getting work and I needed to suspend my CPU projects before MilkyWay ATI work would download.

A quick question, why does the app report that it uses 41% of the CPU? If it not too much trouble, may you look into perhaps lowering the number? perhaps closer to the magic number of 27% ?

Thanks again.

A quick question, why does the app report that it uses 41% of the CPU? If it not too much trouble, may you look into perhaps lowering the number? perhaps closer to the magic number of 27% ?

Thanks again.

I'll ask Anthony about this.

--Travis

---