Topic: [XPM] Working on a GPU miner for Primecoin, new thread :) - page 15. (Read 166591 times)

I can confirm worksize of 64 was optimal for me too.

I had this same issue with the gandalfs dropping and I managed to keep it at a regular average number by playing around with the "worksize" parameter in the primecoin.conf , got the best result with 64

What GPU?

If this is of any help, looking at the console as all the data flies by, my setup (i7 chip, win8, 64bit) reels out all the data, starting with 0 fermats/sec and 786 gandalfs/s, then as time passes, the gandalfs/s progressively drops and if the app doesnt crash earlier each time the console reports the gandalfs/s it shows a smaller and smaller number, reducing to 60 gandalfs/s then it usually gives up and passes onto windows error reporting. It always only shows 0 fermats/s - ? what is this meant to be?

Great work! Might be fairer to fix the bug, I am one of the ones who hasnt been able to use the miner yet though.

I've made the primality tester 4-5x faster, but I haven't managed to fix the "fractional assert" problem. Should I just release the faster version (many people won't be able to use it) or try to fix the bug first (will take time)?

I got similar results enabling/disabling the fermat test on the GPU.

Any successful blocks?

Thanks! Now next problem is GPU is not used. How can I fix it?

You can also just redownload the library sources (from https://dl.dropboxusercontent.com/u/55025350/bitcoin-libblkmaker.zip). I have updated the source.

edit base58.c in the libblkmaker dir and add these middle lines:

      case   0:  // Bitcoin pubkey hash
      case  23:  // Primecoin pubkey hash
      case 111:  // Testnet pubkey hash

and

      case   5:  // Bitcoin script hash
      case  83:  // Primecoin script hash
      case 196:  // Testnet script hash

So, look up those bitcoin/testnet lines and add the primecoin one. Then compile (don't forget autogen.sh)

Please help me compile a file libblkmaker, so that I could use address different than mu1DxMiRUgzjNrVyVeHeRhqDm3XVK12SK2 in my config. I'm not a programmer.

I just finished to read all the thread, I'm so happy that I didn't "donate".

I'm better without a GPU miner since CPU it's what I'm most using right now, however XPM needs the GPU miner to gain popularity otherwise it will remain as the botnet coin.

cheers!

I don't think so.  Ypool uses XPT exclusively, IIRC.  I think primecoin-reaper uses getwork, so someone would need to port XPT to it.

Agreed.happens at stock clocks too and it's too much of a coincidence that all our cards are faulty.

I don't think this is a GPU error, but rather an error in the CPU code somewhere.

I have a hd7970 and hd7950.

1) How old is your GPU? - 3 months old
2) Have you ever OC'd or declocked it? - yes to recommended scrypt overclocks.
3) What intensity settings have you run it at on other coins and for how long? - i13 (cgminer) for most scrypt, i20 for copperlark (reaper miner). I dont mine full time, probably 3-4 days in one hit has been my longest non stop mine.
4) Have you ever over/under volted it? No.

Crashes with Prime Reaper on any sievesize setting after so long, sometime instant and sometime after a few mins depending on the setting. If I remove the sievesize setting and sievesize percentage entirely from the config file reaper sometimes runs, but always produces 0 fermats, and a value for gandalfs that declines over time. The longest it has run without crashing in this mode is around 2 hrs, eventually it crashed too. I have pretty much given up attempting to get it to work now.

1, About one to two months old.
2, yes slightly both ways, but it runs so hot that I most often let it run on default.
3, I usually use 10-15, I haven't been running any mining application 24/7, just a couple of hours to try the cards out.
4, Yes but not through any manual process, I have only used the built in +-20% voltage.
//DeaDTerra

This is a serious problem that may not have a fix.  I have a GPU that I still have running on SHA256 because it starts throwing massive errors if I try to use the same intensity on scrypt coins.  300MH vs 174KH running 16 vs 11 intensity.  Many of these GPUs have been running on hyperdrive for months on end, but until now they have not had to deal with the intensive memory load that your miner is throwing at them.  I'd bet your program hits GPU the same way P95 hits CPU... it stresses them to the point of failure not seen in normal/somewhat heavy operation.  With all the underclocking/overclocking/undervolting/overvolting I'd bet there are a lot of cards that appear to work fine yet are hiding a major problem. 

Memtest is a fairly intensive memory testing program, but it's not as intensive as P95.  I've seen many posts about people saying the P95 program was faulty cause it crashed their computer yet memtest said no problems.  Not once have those claims been proven out though, it's always ended up that P95 stressed something harder than memtest and found a problem that needed fixing.

I vaguely remember someone on the Mersenne forums having written a crude GPU program to simulate what memtest does... maybe you need to have people start looking into that.

Until then, I'd suggest you start having people answer a few basic questions to start the troubleshooting...

1) How old is your GPU?
2) Have you ever OC'd or declocked it?
3) What intensity settings have you run it at on other coins and for how long?
4) Have you ever over/under volted it?

I'd be willing to bet the answers to these 4 questions will start a pattern for those who have it working and those that don't.

I also have problems with reaper crashing,  win 7 x64,  played with the settings but no joy