I upgraded from CUDALucas-2.04 Beta-4.1-sm_21-x64.exe to CUDALucas-2.04 Beta-4.2-sm_30-x64.exe and now I am getting the following error:

CUDALucas.cu(163) : cufftSafeCall() CUFFT error 6: CUFFT_EXEC_FAILED

I thought I had bad CUDA DLLs, but I downloaded fresh ones from the recommended site, and I still get the error.

Please advise.

Thank you.

What card are you using it on? If you're using sm_30 then you need at least a Kepler. Use the architecture which your card belongs to. [45][78]0s are 2.0, [45][1-6]0 are 2.1, and everything <= GTX 2** are 1.x.

I use a GTX 580, but I am upgrading to 4.2 because the latest version of mfaktc uses 4.2.

I run CudaLukas and mfaktc side-by-side and I had a [url=http://www.mersenneforum.org/showthread.php?t=16993]problem[/url] with mismatched CUDA versions.

Thank you.

[QUOTE=TObject;308850]I use a GTX 580, but I am upgrading to 4.2 because the latest version of mfaktc uses 4.2.
Thank you.[/QUOTE]

Okay, but you'll still need a CUDA_4.2-sm_20 executable. flash doesn't compile those AFAIK. You have to choose one with sm <= 20. If you want CUDA_4.2-sm_20, you'll have to compile it yourself or ask flash to do it.

Note that there probably won't be a performance increase from switching CUDA versions.

I see. Thank you.

I can compile just about any combination, but the problem is what Dubslow already pointed out: you won't see much of an improvement.

The version that fastest on all of my 580s is CUDA_3.2 | sm_1.3. You should try that one and let us know how it works for you.

New versions of 2.04 beta are uploaded [URL="https://sourceforge.net/projects/cudalucas/files/2.04%20Beta/"]here[/URL]. They are based on r32 from SourceForge which is the baseline update discussed that included the filelocking. I had to make some minor adjustments to CUDALucas.cu and Parse.c to get it to compile, but I did not make any changes to the functions.

Without having to figure out what went wrong right now, as I was reviewing the changes between r32 and r37 to make it compile, I found that the modified [SIZE=2]open_s function that I added for MSVS, which used _sopen_s, was probably wrong and caused the problem... hopefully.[/SIZE]
[SIZE=2][/SIZE]
[SIZE=2]I have committed the changes to r38.[/SIZE]
[SIZE=2][/SIZE]
[SIZE=2]Everyone please test this build for the filelocking error. Thanks!
[/SIZE]

[QUOTE=Dubslow;308853]Okay, but you'll still need a CUDA_4.2-sm_20 executable. flash doesn't compile those AFAIK.[/QUOTE]

I compiled a 4.2 | sm_20 version, in case you need it.

Hi,

[QUOTE=TObject;308850]I use a GTX 580, but I am upgrading to 4.2 because the latest version of mfaktc uses 4.2.

I run CudaLukas and mfaktc side-by-side and I had a [url=http://www.mersenneforum.org/showthread.php?t=16993]problem[/url] with mismatched CUDA versions.

Thank you.[/QUOTE]

[QUOTE=flashjh;308855]I can compile just about any combination, but the problem is what Dubslow already pointed out: you won't see much of an improvement.

The version that fastest on all of my 580s is CUDA_3.2 | sm_1.3. You should try that one and let us know how it works for you.[/QUOTE]

[B]In theory[/B] all you need is a driver which is capable of CUDA 4.2 or newer. Than you download and unpack mfaktc 0.19 in one directory, mfaktc has the correct runtime libs included in the download. Than download CUDALucas and put the right runtime libs into the CUDALucas directory. You don't need to install the CUDA toolkit.
There is only one point where I'm unsure: I don't know whether you can run both apps (with different CUDA versions) concurrently or not.

Oliver

[QUOTE=flashjh;309485]New versions of 2.04 beta are uploaded [URL="https://sourceforge.net/projects/cudalucas/files/2.04%20Beta/"]here[/URL]. They are based on r32 from SourceForge which is the baseline update discussed that included the filelocking. I had to make some minor adjustments to CUDALucas.cu and Parse.c to get it to compile, but I did not make any changes to the functions.

Without having to figure out what went wrong right now, as I was reviewing the changes between r32 and r37 to make it compile, I found that the modified [SIZE=2]open_s function that I added for MSVS, which used _sopen_s, was probably wrong and caused the problem... hopefully.[/SIZE]
[SIZE=2][/SIZE]
[SIZE=2]I have committed the changes to r38.[/SIZE]
[SIZE=2][/SIZE]
[SIZE=2]Everyone please test this build for the filelocking error. Thanks!
[/SIZE][/QUOTE]
:tu:

Edit: r33 and r37 had some changes, including updated FFT lengths. Those need to be reincorporated. I'll try and make those into an r39.

Okay, slight change of plans: I recall LaurV somewhere saying that a larger FFT length was faster than some smaller ones in CUDALucas' table, but I wasn't able to relocate that post. In addition, I will also add the signal-handling fix discussed before to r39.

In the meantime, all Windows users should test flash's latest compile for the filelocking bug; note, however, that compared to earlier beta releases, some FFT lengths might not appear. If the bug is confirmed killed, then the final release (non-beta) of 2.04 will reincorporate the changes from the old binary lost in the new ones (i.e., it will be r39). r39 will be committed when LaurV responds.

[QUOTE=Dubslow;309543]Edit: r33 and r37 had some changes, including updated FFT lengths. Those need to be reincorporated. I'll try and make those into an r39.[/QUOTE]

[QUOTE=Dubslow;309566]Okay, slight change of plans...[/QUOTE]
It had been so long, I couldn't remember what was done/not done. I remember making the FFT table changes now. I can help reincorporate, if you want, or just let me know when R39 is ready and I'll compile it.