Message boards : BOINC client : 6.13: Exit BM not stopping milkyway but have other successes
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Jun 08 Posts: 641 |
I thought I would mention the following problems / successes. I upgraded 6.12.26 on two systems gpu's: hd5850+gtx570 and hd4890, to 6.13.0 and a day later to 6.13.1. (1) I got my first successful result on the hd4890 for milkyway. Previously, all the work units timeout out after about 80 seconds. The hd4890 was a warrantee replacement for my burned out gtx280 as xfxforce was out of gtx280s. (2) PrimeGrid tasks never start on the hd4890. I understand this is a problem with ATI 11.6 driver from what I read at PrimeGrid forum. Moo! wrapper runs fine on hd4890. The 5850 does not have any of these problem, it seems only the 4890 series. For both 13.0 and 13.1 closing BM stopped all CPU tasks and most gpu tasks for all projects but the CUDA version of milkyway failed to stop. Starting BM back up gave me two instances of milkyway cuda, but the one left running when BM exited quickly got into "waiting to run". This was easily repeatable. When the ATI version of milkyway terminates "ready to report" both monitors flicker noticibly and a second flicker about 1/2 sec later when the next milkyway work unit starts up. Hotfix 11.6b was supposed to fix flickering, but it had no effect on BOINC 6.13 (milkyway project). Anyway, I was very happy to be able to crunch milkyway using my ATI 4890. Only Moo! Wrapper worked when I first put the board into the system to replace the gtx280. [EDIT] Something in the ATI SDK was needed to make 11.6 work correctly with PrimeGrid. It iw working now on hd4890 |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.