Astropulse Error Message!

Message boards : Number crunching : Astropulse Error Message!
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Peter Cook Project Donor
Volunteer tester
Avatar

Send message
Joined: 3 Jul 99
Posts: 94
Credit: 23,643,722
RAC: 70
United Kingdom
Message 1696189 - Posted: 27 Jun 2015, 9:01:33 UTC

Hi all

Ever since the Astropulse database rebuild, I have had no downloads until this week and now I an getting a consistent error message "Task postponed: CL file build failure" - "Opencl_nvidia_100".

Can anyone shed any light on this one for me?

Thanks in advance.
Peter
ID: 1696189 · Report as offensive
Rasputin42
Volunteer tester

Send message
Joined: 25 Jul 08
Posts: 412
Credit: 5,834,661
RAC: 0
United States
Message 1696194 - Posted: 27 Jun 2015, 9:30:04 UTC

It is a driver issue.
Reverting nvidia driver back to 347.88 will fix it.
ID: 1696194 · Report as offensive
Profile Peter Cook Project Donor
Volunteer tester
Avatar

Send message
Joined: 3 Jul 99
Posts: 94
Credit: 23,643,722
RAC: 70
United Kingdom
Message 1696195 - Posted: 27 Jun 2015, 9:48:10 UTC - in response to Message 1696194.  

I just upgraded the driver to the newest version and so far looks ok! If there are any issue's I will go back to that one!

Thanks :)
ID: 1696195 · Report as offensive
Profile Zalster Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 5517
Credit: 528,817,460
RAC: 242
United States
Message 1696211 - Posted: 27 Jun 2015, 12:32:18 UTC - in response to Message 1696195.  

Peter it has to do with how things are named in the driver and the application. Nvidia drivers after 347.88 have what Nvidia calls OpenCL 1.2

This causes a problem when the Kernals are build.

Easiest fix is to revert to driver 347.88 which still had OpenCL 1.1

OpenCL 1.2 won't cause any problems with Multibeams but will error out your Astropulses.

Zalster
ID: 1696211 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1696217 - Posted: 27 Jun 2015, 13:03:13 UTC

Guys, please stop suggesting to revert to older drivers for this particular (bool2 vs bool_2) issue. Such reverse can do more bad than good.

Correct ways to deal with this issue:
1) simple edit of CL file
2) download and install updated app
3) revert with current stock NV AP.

Though time to time some driver restrictions occurs, it's not that case actually.
ID: 1696217 · Report as offensive
Profile Zalster Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 5517
Credit: 528,817,460
RAC: 242
United States
Message 1696226 - Posted: 27 Jun 2015, 19:18:43 UTC - in response to Message 1696217.  

Raistmer, The only reason I recommend reverting to older driver is the ease of usage. It allows them to continue to run Lunatics without having to revert to stock.

Steps 1 and 2 are only good for people with more than basic understanding of Boinc and willing to go hunting.

Problems for those without this knowledge are being able to find hidden folders , then editing the xml or CL files (and hoping they don't make a mistake)

Step 3 becomes the final solution when all the above fail.

Yes, I know you make new apps that work better with newer drivers but not everyone is comfortable with editing.

Best solution. Fix the CL file before it even downloads to end user. But that's someone else's department.

Ok, i'm off my soap box..
ID: 1696226 · Report as offensive

Message boards : Number crunching : Astropulse Error Message!


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.