Quote from: mumus on October 27, 2014, 11:22:43 AM

Quote from: djm34 on October 26, 2014, 07:57:22 PM

Quote from: skunk on October 26, 2014, 05:49:15 PM

Quote from: mumus on October 26, 2014, 05:07:26 PM

Quote from: skunk on October 26, 2014, 04:09:14 PM

Quote from: mumus on October 26, 2014, 02:37:30 PM

Quote from: skunk on October 26, 2014, 01:56:15 PM

Quote from: djm34 on October 26, 2014, 12:50:15 PM

Quote from: skunk on October 26, 2014, 10:50:13 AM

Quote from: Supercomputing on October 26, 2014, 05:37:57 AM

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working.

thank you mumus, there are no submission attempts thus confirming the mining code is actually not working...
i've blindly tried to enable SKEIN_ERR_CHECK into hash/skein.h but nothing changed, do you know if there's something that could eventually be tuned in the code that could help fixing it?

Try to lower the const int throughput = 512*8 * 512 * 4; in sk1024.cu, for example to 512* 8 * 512 * 1 or just 512 * 512. Let me know if it worked or not. I'm trying to understand the code and now I'm playing now with another parameter that can be related and it may help. I'm a beginner in cuda coding and I definitely don't understand the code crypto algorithm yet.

unfortunately still no submission attempts, even not with just 512...

It isn't related to the throughput.
I need to rewrite the kernel for skein for compute_30 and I don't have time at the moment to work on that task...

Yes, slowly but I realized that isn't related to any parameter. I've also found one of my old compute_20 card and it doesn't works on it either.

don't hold your breath for a compute_20 cards version of the algorithm