OpenCL apps are available for download on Lunatics

Further about doing the transition to r1760, the issue is the clFFTplan file ending with _32768_r1761.bin so that should be deleted unless you're sure it was created by the Astropulse application. The other _r1761.bin files won't be needed so if you like things neat they can also be deleted.

All right here's my updated test report for MB r1760 only (since there haven't been any significant changes for AP between r1363 and r1761 and they're all working just fine, ATI and NV both).


HD 6970

WinXP, Catalyst 11.2/11.7 kludge (only known stable configuration for my Cayman cards).

I never got to try this one with r1761. In fact, I had to pinch a WU from CPU to test r1760. But it seems to be working okay, CPU/GPU usage looks good. Time taken to complete is a little longer than usual (even considering the extra time used for binary compilation), but I've seen some MB WUs take this long even with r426. So I can't comment on relative performance till I get more WUs processed with MB r1760.

I picked this particular WU because it already has a result awaiting validation on the server, but unfortunately uploads (and downloads) seem to be dead for me at time of writing, so I'll have to wait till the server recovers before I can see if my result is valid. At least the spike/pulse/triplet/gaussian counts are consistent.

Edit: Oops, no, strike that. Uploads working again, albeit at a crawl. But the result was marked as valid!


HD 6950

WinXP, Catalyst 11.2/11.7 kludge (only known stable configuration for my Cayman cards).

I kept getting -9 result overflows with MB r1761 previously. I'm quite sure that I had AP r1761 running previously, and given that MB WUs are working again with r1760, I'd say reusing the AP r1761 bin was the problem. Looks like problem solved! The work-unit was marked as valid, in any case.


AMD C-50

Win7 32-bit, Catalyst 12.8.

Unfortunately, the good news doesn't carry over to the APUs. Result appears to be the same as before - after only a few seconds of GPU use, the driver crashed at about 0.792% progress.


AMD E-450

Win7 64-bit, Catalyst 13.1.

Given that the C-50 failed again and that the underlying GPU is very similar, I didn't feel it was worth the effort of rolling back to Catalyst 12.8 to try this one again.
____________
Soli Deo Gloria

All right here's my updated test report for MB r1760 only

Observation: 1761 produced "WARNING: suboptimal workgroup size for PC_find_pulse_kernel_cl pass x" in stderr. From a quick look at the source I think that's just about wasteful memory alignment, shouldn't have much to do with speed.

And what period_iterations_num value did you try already with C-60 ?

Observation: 1761 produced "WARNING: suboptimal workgroup size for PC_find_pulse_kernel_cl pass x" in stderr.

Mine is a C-50, but essentially the same as your C-60 except for the turbo clock boost. Anyway, I normally use 24, but at 32 I still get a driver crash. Do you suggest going even higher?

I know very well that it's not very powerful. But I tried values of 64, 128, 256, 512 (I know there's no real reason to use powers of 2, I just did), but all of them resulted in driver crashes within seconds of the GPU being used. If there are any other suggestions, I'll give them a try.

Rolling back to r426 yet again.
____________
Soli Deo Gloria

I know very well that it's not very powerful. But I tried values of 64, 128, 256, 512 (I know there's no real reason to use powers of 2, I just did), but all of them resulted in driver crashes within seconds of the GPU being used. If there are any other suggestions, I'll give them a try.

Rolling back to r426 yet again.

That's crazy. Do you know how to open it and try cleaning out the heat-sink and fan? It's a bit fiddly, but I learned how to open the case to replace the memory - the pre-installed 1 GiB was paltry.

Hopefully, it's not like what happened to my most powerful laptop - pipe between GPU and heat-sink seems to be no longer effective. I can feel the heat being transferred on the pipe between the heat-sink and CPU, but the GPU one is relatively cold, which tells me something is broken. >.< Well, it's only a Mobility Radeon 2600, so the best it could do was the old CAL-based hybrid AP, anyway.
____________
Soli Deo Gloria

That's crazy. Do you know how to open it and try cleaning out the heat-sink and fan?

So sounds like the fan itself is broken or not spinning very well, at best.

Well, never mind, then. Looks like I'll have to be your low-end Fusion tester for the time being. (:
____________
Soli Deo Gloria

So sounds like the fan itself is broken or not spinning very well, at best.

So sounds like the fan itself is broken or not spinning very well, at best.

YEs, fan is broken. Sometimes it spins fast and noisless but soon after it begins strong vibration accompanying laud noise and rotation speed drops (and APU temp rises up to point of emergency shutdown near 90C )

Observation: 1761 produced "WARNING: suboptimal workgroup size for PC_find_pulse_kernel_cl pass x" in stderr. From a quick look at the source I think that's just about wasteful memory alignment, shouldn't have much to do with speed.

Actually it can affect performace. Suboptibal workgroup size meand underloading GPU. Could you give link on result with that warning ?

One more report from me.

HD 4670

WinXP, Catalyst 11.12.

I did this one earlier, but didn't bother reporting it. I didn't expect MB to work since maximum work-group size is only 128, and I was right: r1760 seemed to get stuck on compiling the FFT plans. The bin_V6 file was compiled okay.

This is the same AGP card that had been plagued with several invalid AP results in the past (you might remember helping me with this one, Raistmer). Interesting that in recent months, it seems to have stabilised enough on r1363 and r1761 is also working okay so far. I noticed that Catalyst 12.1 produces a lot more invalid results than Catalyst 11.12.


HD 4850

WinXP, Catalyst 11.12.

This one I have set-up on the computer I made for my brother. No work has been done on the Radeon card for a long, long time, but so far the stability issues I remembered from previously seem to be no longer present. At least from what we've seen so far. AP works great, MB r1760/r1761 also running without apparent issue. But the work-units will take a while to complete, so can't comment on their correctness just yet.
____________
Soli Deo Gloria