toTOW wrote:MtM wrote:Sorry 11.7 = SDK 2.3, 11.9 was sdk 2.4
http://forums.amd.com/forum/messageview ... erthread=y seems SETI is also broken with 10.10 and upwards.
Great that it was reported by Raistmer. He's the developer of Lunatics optimized SETI applications for GPU (Astropulse and Multibeam which uses OpenCL on AMD GPUs).
I sent an email to Mike Houston to point him to our issues ...
Good, I would btw agree with a remark in that thread that a version which produced incorrect results ( which is even way worse then one which is bugged in that it fails to run something ) should be either removed as download or be accompanied with some warning about the broken compatibilities. Hope it gets fixed, people who use core_16 on amd might want to play the latest games as well, so for some downgrading or not upgrading isn't really a good option. Edit: removed concern about data validity concerning f@h.
Eagle wrote:I assume I can confirm it's the driver - the random blocks-iteration #38 failed with 995 (!) errors.
Should I downgrade or does FAH contact AMD to resolve the issue?
If that means I have to stay on "normal" GPU-WUs for a couple of weeks then that's fine with me..
I would downgrade simply because it getting fixed ( hopefully ) doesn't help you now, while those older drivers don't seem to have the issues reported. If you want to keep 11.11 due to some other reason, keep running core_11 work units.