Posts by Tex1954

1) Message boards : Number crunching : 7970s Dont Run (Message 5521) Posted 10 Oct 2013 by Tex1954 Post: Have you tried BOINC Client 7.2.16? Iam running with Catalyst 13.9 too but only one card. Dont know if this helps. I have tried drivers from 12.10 up to (now) 13.9 and nothing works. All the WU compute error after 26 seconds or so. The GPU never gets turned on... System is an AMD 1100T or now a 1045T (testing) and HD 7970... 8-)
2) Message boards : Number crunching : Forcing work on one GPU only (Message 2816) Posted 4 Mar 2012 by Tex1954 Post: I can report the same problem running Moo! Wrapper on the ATI HD6990 card. If I use the above app_info.xml file and say one GPU per task, it will load and run two tasks... displays showing 1ATI per WU. But often during crunching, the GPU usage will drop or oscillate between 90-99% as if it is unstable. Also, the Dnet application looks to use ALL GPU's in real time, so if you suspend one task, the other starts using both GPU's even though app_info doesn't prescribe that. That causes more problems as eventually it's trying to run two tasks on two GPU's at the same time. This tells me both applications are polling both GPU's at the same time trying to compete for GPU resources... and explains the large differences I see in task completion times. One would expect a simple doubling of times, but that doesn't seem to be the case... it can be a lot worse than that... This behavior also seen when starting a collatz task on one GPU and Moo on the another. If the collatz task is suspended, the Moo! task starts using both GPU's! So, one can see this isn't nice behavior and contrary to BOINC methodology in general. :)
3) Questions and Answers : Windows : Distributed.net has stopped working .. (Message 2800) Posted 1 Mar 2012 by Tex1954 Post: Ohh. Nope... talking about the Win7-955 machine... Used to have a 955 CPU... upgraded to 1100T a while back... :)
4) Questions and Answers : Windows : Distributed.net has stopped working .. (Message 2794) Posted 1 Mar 2012 by Tex1954 Post: Well, I discovered something interesting... I have an HD6990 and when I use the linked app_info file, it says it is running one task per GPU, but seems to be using both of them anyway! I suspended the pending tasks, then suspended ONE task and suddenly the GPU's go to 99% again... both of them. Try detaching, reinstall clean drivers, rebooting and all the tricks... it insisits on using BOTH GPU's even when the app_info and the status line say it is using only one... LOL! I was wondering why it was taking so long... :) Since Moo is not designed to be Nvidia friendly, you might be better off just excluding the Nvidias here and using them on GpuGrid or PrimeGrid instead. Most projects work better with one platform or the other, Moo is better with AMD. That does NOT mean it won't work with Nvidia cards, they just won't be at their best. Since they are competitors, Nvidia and AMD I mean, they do things differently, they get the same answer in the end though. Umm, an HD6990 is an AMD/ATI card... like two 6970's on one card... and it happens to be in a box driven by a 3.75GHz 1100T CPU... Soo, not sure how your comment applies to my problem... :D
5) Questions and Answers : Windows : Distributed.net has stopped working .. (Message 2791) Posted 1 Mar 2012 by Tex1954 Post: Well, I discovered something interesting... I have an HD6990 and when I use the linked app_info file, it says it is running one task per GPU, but seems to be using both of them anyway! I suspended the pending tasks, then suspended ONE task and suddenly the GPU's go to 99% again... both of them. Try detaching, reinstall clean drivers, rebooting and all the tricks... it insisits on using BOTH GPU's even when the app_info and the status line say it is using only one... LOL! I was wondering why it was taking so long... :)