Problem with jminer
-
I have:
1 x 1TB
4 X 2TB
1 x 5TBSo 6 plots over that size
-
so you used another miner before? you may contain using that one or replot the not supported files.
first maybe try removing the drives with that not supported plotfiles, and look if jminer works than.
-
I know jminer works without those plots. It's just a lot of work and time replotting all those plots, I don't have that good GPUs so I use CPU plotting.
I really would like to use GPU mining cause it is faster...
-
yes, sorry for that ... i see the pain ... but there is no chance to fix the plotfiles for jminer.
maybe try running 2 miners, one for not supported plots on CPU and rest on jminer?!
-
And no way to fix jminer using biginteger?
-
@Focus did you try to mine those plots with cpu miner to see what happens
-
No problem using cpuminer but extremely slow, sometimes my plots are not fully checked and a new block arrives
-
@Focus thats strange cause I never had an issue where cpu worked and gpu not.
-
@Focus sure there is a chance^^ but i have to find time for that, a lot other stuff on todo list. I do not know how long you can wait ... therefore i suggested the mixed mode.
-
OK keeping fingers crossed
-
@Focus why the hell did you choose such huge startnonces?!
-
@luxe I didn't chose them, it did it automatically with the GUI (write plots)
-
ok, i see ...
-
@Focus i do not promise anything, but i will look into it ... to see how much code is effected.
-
@luxe ok hopefully it's an easy fix
-
@Focus Well, i made jminer running with BigInteger, but i'm not sure if burst-wallet can even handle that ... in every case.
If you look at:
https://github.com/burst-team/burstcoin/blob/master/src/java/nxt/http/SubmitNonce.java#L29The submitted nonce for mining gets converted (back) to a Long.
That would fail if nonce is bigger than 18446744073709551616 (2 x Long.MAX_VALUE)public static long parseUnsignedLong(String number) { if (number == null) { return 0; } BigInteger bigInt = new BigInteger(number.trim()); if (bigInt.signum() < 0 || bigInt.compareTo(two64) != -1) { throw new IllegalArgumentException("overflow: " + number); } return bigInt.longValue(); }I guess it would throw a IllegalArgumentException !
Conclusion:
This will work for your problem, but does not mean nonce numbers can be unlimited high. Just up to 18446744071922212865.
-
Quickly ran it and it's not throwing an error. Will do more thourough testing tonight. Thank you !!!!!
-
Thank you for pointing out this issue, feedback makes software better :-)
