1) Message boards : Number crunching : Computational Error? (Message 58676) Posted 11 Jun 2013 by Barblovesroses Post: Thanks for posting this thread. I can't believe how many different projects this AMD Catalyst driver series is a problem for. I have had to download and reload it several times for different projects myself now in the hopes that it would resolve issues that I was having at different projects. Some of the projects had me go back to the older version 12.8 (volpex) and you seem to want 13.1 for Milky Way to work properly while I believe that T4T wants the latest version 13.4. I'm not sure what version keeps Poem happy but its running smoothly at present for me so I'm not complaining!(and to think I didn't even know about Catalyst when I first was running Poem and got this new computer and got introduced to the world of GPU's almost a year ago...hahaha) I just switched back down to 13.1 Catalyst and I hope my other projects will run ok too for now...I should know within a few days. It gets confusing not knowing why you are getting all of these computation errors every time there is an upgrade of a system and you don't know if its something you need to change or if its a programming issue. Do you post something on the board yourself or do you wait to see if someone else does...then sometimes you get busy and forget and the problem is still there a month later repeating itself and noone else has complained about it either. Anyway, thanks everyone for talking about this issue and figuring it out before I looked into it myself!!! Hugs and cyberblessings to all of you!

2) Message boards : Number crunching : GPU lacks necessary double precision extension (Message 57064) Posted 28 Jan 2013 by Barblovesroses Post: Did it used to work here? It looks like one of those built into the cpu gpu's and Boinc just isn't seeing it. Have you tried upgrading to the latest Alpha version of Boinc, ver 7.0.45 available here: http://boinc.berkeley.edu/dl/?C=M;O=D as the newest versions tend to add more support for more cpu/gpu combinations then the older versions. It also says it only has 512mb of ram, I haven't checked the specs, I don't know where they are, but could it be too little? It must be physical ram too, not added on ram like the old laptops could do.[/quote] Thankyou for the info on the updated versions - I've found that it pays to use them and I wasn't aware that they had been updated recently so am grateful for the info. As to the ram, will have to find out if it can be expanded on this computer...just had a problem with another program desireing more ram than I had available too and it puzzled me too so I need to see why this less than a year old computer is running low on RAM memory for projects all of a sudden. again, thanks for the suggestion.

3) Message boards : Number crunching : GPU lacks necessary double precision extension (Message 57056) Posted 28 Jan 2013 by Barblovesroses Post: I appear to be having this issue with my computer too and have had for some time but didn't check into it until just now. Some jobs will run just fine for the project, but at other times, I get the error message that GPU lacks necceary double precision extension just like others were having back about a year ago. Decided to research it tonight and found this thread. Here is my most recent event log from the project 1/27/2013 11:46:36 PM | Milkyway@Home | Sending scheduler request: To fetch work. 1/27/2013 11:46:36 PM | Milkyway@Home | Requesting new tasks for ATI 1/27/2013 11:46:37 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks 1/27/2013 11:46:37 PM | Milkyway@Home | No tasks sent 1/27/2013 11:46:37 PM | Milkyway@Home | Message from server: GPU lacks necessary double precision extension my computer's id with the project is 453339. NO NVIDIA here...and I just recently updated my amd catalyst graphics as was having some problems with Poem@home and it was pointed out that I had old graphics so now those are updated and that fixed my problems there, but it hasn't fixed this issue(thought worth a mention in case it might be something to consider as part of the problem). Any suggestions? Barb

©2024 Astroinformatics Group