 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
I'll try to have the source on GitHub this weekend.
|
|
|
|
The issue isn't with jansson, it's with libblkmaker. It seems you have the normal (i.e. non-primecoin) version. You have to download libblkmaker from https://dl.dropboxusercontent.com/u/55025350/bitcoin-libblkmaker.zip. It is the libblkmaker prime branch, with a couple of primecoin-specific things added. Those auxdata parameters are important, without them the miner won't work.  |
|
|
|
BTW, Maybe it's time to put the code on GitHub... mtrlt?
Yeah, the week is almost up. |
|
|
|
I then ran into another weird problem when compiling the kernels
For the record, here's the error: Write buffer vPrimes, 6302644 bytes. Status: 0
Compiling kernel... this could take up to 2 minutes.
ptxas error : Entry function 'CalculateMultipliers' uses too much shared data (0x5078 bytes + 0x10 bytes system, 0x4000 max)
What GPU? It seems it only has 16 kilobytes of local memory, whereas I've programmed the miner with the assumption of 32 kilobytes, which is what ~all AMD GPUs have. |
|
|
|
|
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)?
|
|
|
|
Please help me compile a file libblkmaker, so that I could use address different than mu1DxMiRUgzjNrVyVeHeRhqDm3XVK12SK2 in my config. I'm not a programmer.
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) You can also just redownload the library sources (from https://dl.dropboxusercontent.com/u/55025350/bitcoin-libblkmaker.zip). I have updated the source. |
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
|
1/9 seems about right. With use_gpu_fermat_test, it reports the amount of candidates left after doing Fermat tests on the GPU. Without it, it just reports whatever the GPU sieve returned.
|
|
|
|
|
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.
|
|
|
|
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: And it'll write the output to the file output.txt. |
|
|
|
DeaDTerra, could you try with: cpu_mining_threads 1
debug true
opencldebug true
and put the entire output to pastebin.com? |
|
|
|
Somebody, please, make a working 64 bit binary file.
Are you using Linux or Windows? |
|
|
|
I should have been more specific: I think there's a problem if you compile it yourself on 64-bit Linux. The supplied Windows binary is 32-bit.
Ubuntu 12.04 + x86_64, AMD GPUs -- works for me. No blocks yet, but it looks busy and the numbers are sane. I should have been more specific: I think there's a problem if you compile it yourself on 64-bit Linux. The supplied Windows binary is 32-bit.
DeaDTerra also uses win7 x64 Ok, so the problem isn't there.. I'm mining on win7 x64 just fine. |
|
|
|
|
I should have been more specific: I think there's a problem if you compile it yourself on 64-bit Linux. The supplied Windows binary is 32-bit.
|
|
|
|
I can't turn the fermat test off because then it crashes straight on start and I get fraction assserts error.
Same problem. Any suggestions about how can I fix it? OS? 32-bit or 64-bit? It might be that 64-bit is broken right now. |
|
|
|
|
