Floating Point Exception caused by configure script creating a makefile with an erroneous arch specification (workaround included) about cudaminer HOT 10 CLOSED

Seems related with: #7

from cudaminer.

Seems like the same problem. Have you tried compiling without the -arch=compute_10 argument? (Sorry for the delay, was traveling.)

from cudaminer.

Well, what helped for me - reinstalling drivers.... It works now.

from cudaminer.

Awesome! You should update the bug you have open with that info. :)

from cudaminer.

I am pretty sure the compute_10 is needed, as it forces the creation of PTX 1.0 code, which is what I want.
The driver will usually translate the PTX 1.0 code to whatever compute architecture you happen to run.

Christian

from cudaminer.

In the case of my GTX 250, however, it appears this option is causing nvidia CUDA calls to fail.

I'm away from my computer at the moment, but how would you feel about a pull request that added a "no-compute" option to the config file that allows compilation without "compute_10," and added a CudaError value check after line 878 that printed a warning suggesting using the "no-compute" option to compile and exited if cudaerror returned the "Invalid Device Function" value, suggesting the use had the same issue as myself? After all, once this option is removed, the code functions properly for me.

from cudaminer.

Note: Current code does not compile without arch (ptxas error : Entry function … uses too much shared data)
and crashes during autotuning with a floating point exception

from cudaminer.

I tried compiling with a fresh repository on Linux with the Nvidia 319.60 drivers with a Quadro 3000M card, and I'm also getting this error. I tried removing the -arch=compute_10 from the nvcc call but I still got the same problem. The machine I tested on is at my work so I will have to try some more tomorrow.

from cudaminer.

On a GT 540M, having this problem with 319.60 drivers on Ubuntu 13.10. I'm launching via optriun. Like @jra89 I also tried removing --arch=compute_10 but also got the same problem.

from cudaminer.

Sorta-Workarround: Disable autotune and specify a configuration on the command line...

from cudaminer.