[XPM] Working on a GPU miner for Primecoin, new thread :)

[bitwarrior]

64 bit Windows Binary Please.

Any shared info on how to fix the appcrash due to integer overflow thingy?

I have observed that only 2 chains in utmost high value are being counter, in what way those 3 chains and above can be obtain?

Thanks

[wyldfire]

On my win7 laptop I intalled intel 2013 OpenCL1.2 SDK which is supposed to work with the integrated HD graphic card. I got this with beta 2

Code:

Warning: unknown property "#mine" in configuration file.
Warning: unknown property "opencldebug" in configuration file.
Warning: unknown property "use_gpu" in configuration file.
Warning: unknown property "use_gpu_fermat_test" in configuration file.
I'm now mining primecoin!
GeneratePrimeTable() : setting nSievePercentage = 15, nSieveSize = 25165824
Share thread started
GeneratePrimeTable() : prime table [1, 25165824] generated with 1575661 primes
Available CPU mining algorithms: hp7
Using default: hp7
Creating 2 CPU threads.
1...2...done
List of platforms:
        0       Intel(R) OpenCL
Using platform number 0
2013-09-05 11:43:54 Error: Error getting OpenCL device IDs

configs are the default with user pws, port, threads, address changed according to %appdata% config.

I can't explain the failure you're seeing, but trust me when I say your Intel HD graphics device will be a total dog on primecoin.  When primecoin-reaper hits its stride it might be worth your time, but not yet.

Does Intel's OCL kit come with a "clInfo" executable?  That might list the devices and you could see if there's actually one presented that matches the qualities being searched for.

[mhps]

On my win7 laptop I intalled intel 2013 OpenCL1.2 SDK which is supposed to work with the integrated HD graphic card. I got this with beta 2
...

I can't explain the failure you're seeing, but trust me when I say your Intel HD graphics device will be a total dog on primecoin.  When primecoin-reaper hits its stride it might be worth your time, but not yet.

That is OK. New thingies are sort of fun to play with. This same laptop found a block on the day primecoin was released.

Does Intel's OCL kit come with a "clInfo" executable?  That might list the devices and you could see if there's actually one presented that matches the qualities being searched for.

I had searched and didn't find clinfo (32bit win7).

[FiiNALiZE]

On my win7 laptop I intalled intel 2013 OpenCL1.2 SDK which is supposed to work with the integrated HD graphic card. I got this with beta 2
...

I can't explain the failure you're seeing, but trust me when I say your Intel HD graphics device will be a total dog on primecoin.  When primecoin-reaper hits its stride it might be worth your time, but not yet.

That is OK. New thingies are sort of fun to play with. This same laptop found a block on the day primecoin was released.

The difficulty now is light years away from the difficulty at release.

If your laptop only mined 1 block on day 1, then it'll probably take anywhere from 3-4 weeks for you to find a block (CPU-wise)

[mhps]

That is OK. New thingies are sort of fun to play with. This same laptop found a block on the day primecoin was released.

The difficulty now is light years away from the difficulty at release.

If your laptop only mined 1 block on day 1, then it'll probably take anywhere from 3-4 weeks for you to find a block (CPU-wise)

What I meant was that the laptop has been a fun toy to play with when the timing is right.  My better machines are all running hp10 or RdB. Currently I only want to see the GPU miner working to get a hang of it.

By the way XPM network difficulty appears to be stalling http://192.241.170.170/  Maybe those who desperately tried to mine some coins (probably at a loss) before the GPU miner comes out find there is no need to rush after all. ;P

[mtrlt]

64 bit Windows Binary Please.

Any shared info on how to fix the appcrash due to integer overflow thingy?

I have observed that only 2 chains in utmost high value are being counter, in what way those 3 chains and above can be obtain?

Thanks

The 32 bit binary works fine on 64-bit Windows.

[JoeMattie]

I donated a bitcoin and I don't want it back.

Programming is hard work.  I sent a guy $130 to help defray the costs of real life while he worked on writing a program that I wanted to be written.

He wrote the program.

Expectations met.

[paulthetafy]

The TOTAL counts aren't comparable between use_gpu_fermat_test true/false, should look at 2-chains. I'll remove the TOTAL count in the next version.

Good to know, thanks! Looking at 2/3 chains then the gpu_fermat_test is faster by ~ 1.4x (I do have a weak CPU in there).  Is the candidate difference a red herring (1/9 as many) or just the way it is reported?

I'm just not seeing stats anything like this.

With the fermat test done on the GPU I get...
0 fermats/s, 6.73269 gandalfs/s.
70.2502k TOTAL     1.79828k 2-chains     39.093 3-chains     39.093 4-chains

With the fermat done on the CPU I get ...
60338.8 fermats/s, 3523.21 gandalfs/s.
350.383M TOTAL     1.01852M 2-chains     64.7127k 3-chains     3.58685k 4-chains     298.904 5-chains

Ignoring the total, the fermat test on the GPU gives 1000x fewer 2-chains,  and 100x fewer 4-chains.  This is with 2 x 7950, a AMD FX(tm)-4130 Quad-Core Processor, and ubunutu 13.

Am I missing something somewhere?

[pyromaniac]

64 bit Windows Binary Please.

Any shared info on how to fix the appcrash due to integer overflow thingy?

I have observed that only 2 chains in utmost high value are being counter, in what way those 3 chains and above can be obtain?

Thanks

The 32 bit binary works fine on 64-bit Windows.

Not for most people.

[DeaDTerra]

It is hard to get the entire output as once the program froze enough text has gone by that the original details are gone.
Is there anyway to capture the whole output in an easy way?
(I have little knowledge within coding and such, so please be patient )
//DeaDTerra

Yeah just run it from the command line / terminal like this:

Code:

reaper > output.txt

And it'll write the output to the file output.txt.

Okay thank you.
Output and settings with ferm test enabled:
http://pastebin.com/t9w3P8uk
Without ferm test:
http://pastebin.com/u8xkqXww

If you need any additional info just ask
//DeaDTerra

[paulthetafy]

It is hard to get the entire output as once the program froze enough text has gone by that the original details are gone.
Is there anyway to capture the whole output in an easy way?
(I have little knowledge within coding and such, so please be patient )
//DeaDTerra

Yeah just run it from the command line / terminal like this:

Code:

reaper > output.txt

And it'll write the output to the file output.txt.

Okay thank you.
Output and settings with ferm test enabled:
http://pastebin.com/t9w3P8uk
Without ferm test:
http://pastebin.com/u8xkqXww

If you need any additional info just ask
//DeaDTerra

Start my reducing your sievesize to 1000000 and only enabling 1 GPU and see if that helps. 

[DeaDTerra]

It is hard to get the entire output as once the program froze enough text has gone by that the original details are gone.
Is there anyway to capture the whole output in an easy way?
(I have little knowledge within coding and such, so please be patient )
//DeaDTerra

Yeah just run it from the command line / terminal like this:

Code:

reaper > output.txt

And it'll write the output to the file output.txt.

Okay thank you.
Output and settings with ferm test enabled:
http://pastebin.com/t9w3P8uk
Without ferm test:
http://pastebin.com/u8xkqXww

If you need any additional info just ask
//DeaDTerra

Start my reducing your sievesize to 1000000 and only enabling 1 GPU and see if that helps. 

I tried it
It helped a bit, I got it running stable for about a minute but then it crashed.
//DeaDTerra

[mtrlt]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

[balanghai]

Can this be used to mine in ypool?

[pgbit]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

I get the same bug as DeaDTerra. Let me know if I can help test, or if you need a pastebin dump to figure it out. I am trying all sorts of settings but still get the same issue, running on Win8, 64bit. I get the same issue on three other PCs. The most it runs for is a minute or so.

[jammertr]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

I get the same bug as DeaDTerra. Let me know if I can help test, or if you need a pastebin dump to figure it out. I am trying all sorts of settings but still get the same issue, running on Win8, 64bit. I get the same issue on three other PCs. The most it runs for is a minute or so.

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

[bcp19]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

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.

[DeaDTerra]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

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.

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

[yager]

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.

[mtrlt]

It seems like memory corruption, the most annoying kind of bug. Might take some time to fix, I haven't been able to reproduce it on my computer.

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.

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