Can we have the AMD APP OpenCL runtime driver version displayed on the Computer details page please, as well as the Cal driver version, (which has stayed the same over the last couple of Catalysts)
as that can't be used to determine the APP OpenCL runtime version: http://www.hal6000.com/seti/boinc_ati_gpu_cheat_sheet.htm During Alpha testing at Lunatics and Beta testing at Seti Beta on the AMD OpenCL Multibeam app we came across an AMD APP runtime Bug, when the app is initially run it produces a kernel file, a fft wisdom file and some fft plan files, On Catalyst 12.8 the AMD OpenCL Multibeam apps produce strongly similar results, when initialy run on Cat 12.10 the apps produce inconclusive results finding the wrong pulses, on Catalyst 12.11 Beta and Cat 13.1 the apps when initialy run produce driver restarts, the kernel file being the culprit in each case, on Catalyst 13.2 Beta the compilations fail with an error, If a user does compilations under Cat 12.8, then upgrades drivers, the app will opperate correctly on Cat 12.10, 12.11 Beta, 13.1 and 13.2 Beta, If he did compilations under Cat 12.10 he'll produce inconclusives, and continue to produce inconclusives on Cat 12.11 Beta, and Cat 13.1, Cat 13.2 Beta, and even Cat 12.8 (unless he deletes the kernel file for his GPU, or detaches and reattaches) (There are further complications getting the driver and APP runtime downgraded) Eric will likely want to limit the AMD OpenCL Multibeam app to hosts running the right AMD APP OpenCL runtime, and not a more recent Buggy runtime, so he'll need to restrict the app to an APP runtime of not later than 938.2, I'm not sure that is possible at the moment, Claggy _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
