CCminer(SP-MOD) Modded GPU kernels.

[djm34]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

[1714677954]

1714677954

[1714677954]

1714677954

[1714677954]

1714677954

[scryptr]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

PRECISE--

OK, you have a point, DJ.  I was posting in sp_'s thread, however.  I DO try to be clear about OS, version, hash rates, clock rates, spelling and punctuation, etc.  I've groaned about the bleeding edge speed before, myself, but sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Maybe a few releases should focus on code clean-up and standardization rather than speed.  Future improvements would then be on a stronger base.       --scryptr

[sp_]

djm34, why do you care about the broken solomining? Release 68 is more stable than ever, and everybody is using my mod because it is the fastest opensource in the world. Optimizing for the Maxwell is not straight forward because there are so many different cards with different properties. There are different operating systems with different adressmodes and drivers. But my modded kernals are the fastest on all the cards and operating systems.

The solomining bug can be fixed. T Nelson is looking at it. If you think solomining is important for you should donate some mBTC to him to motivate.


Some time ago when quark was paying 0.7BTC/GHASH:

[impulse2000]

Fired my poor gtx750 1gb again, 1500/1600 = 6300kh/s (release 68, quark)

GTX750TI-OC-2GD5 - 7250kh/s - Clocks +180Mhz/+180Mhz (release 68, quark)

Pretty good, but how much is the consumption? Hash/watt

The 1gb 750 has a TDP of just 35W in the bios.
And on standard clocks it uses around 40Watts to produce 5 MHASH of quark. (125KHASH per watt).
A 970 gigabyte windforce gaming will do around 17MHASH in 180 watts. (94.444444444444KHASH per watt)


So the junior card is 32% bether is hash/watt, but you need alot more cards/motherboards/ram/cpu's/psu's So I guess none of you are mining with the gtx 750 ?

I dont know. This my home comp, not rig. Son watches YouTube + ccminer with -i 16-17. If not -i 22.9.
Q8300 / P5K-SE-EPU / 2GB / Win7x86 / GTX750Ti-2GB

[zTheWolfz]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

Phoenixcoin has low diff and the blockchain should download fairly quick for the wallet.

I find blocks in a matter of mins. after starting r54, r55 & r56 gives more boooo's than r54 that I get none in.
-i value needs to be low -i 10 is a good starting point for solo mining phoenixcoin.
at 300+ kh/s I find a block in about every 15 mins most of the time on a single GTX960.

r68 dump log

Code:

[2015-09-23 02:44:50] NVAPI GPU monitoring enabled.
[2015-09-23 02:44:50] 1 miner thread started, using 'neoscrypt' algorithm.
[2015-09-23 02:44:50] Binding thread 0 to cpu 0 (mask 1)
[2015-09-23 02:44:50] JSON protocol request:
{"method": "getwork", "params": [], "id":0}


* Rebuilt URL to: http://127.0.0.1:3333/
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 3333 (#0)
* Server auth using Basic with user 'phoenixcoinpc'
> POST / HTTP/1.1

Authorization: Basic cGhvZW5peGNvaW5wYzp4

Host: 127.0.0.1:3333

Accept-Encoding: identity

Content-Type: application/json

Content-Length: 45

User-Agent: ccminer/1.5.67-git(SP-MOD)

X-Mining-Extensions: longpoll noncerange reject-reason

X-Mining-Hashrate: 0



< HTTP/1.1 200 OK

< Date: Wed, 23 Sep 2015 07:44:50 +0000

< Connection: keep-alive

< Content-Length: 311

< Content-Type: application/json

< Server: phoenixcoin-json-rpc/v0.6.6.0

< 

* Connection #0 to host 127.0.0.1 left intact
[2015-09-23 02:44:50] JSON protocol response:
{
   "error": null,
   "result": {
      "algorithm": "neoscrypt",
      "data": "02000000e2f3ceab75f7db954acf51383b48743fea1faa9f0216239bcc864ff0f1c66a0a221a2f1c9f713cd60c3d9cc41aa5fc9c5e52c37405c96a017a19442d5158802f6c580256549e071d000000003d010000",
      "target": "0000000000000000000000000000000000000000000000000000549e07000000"
   },
   "id": 0
}

[2015-09-23 02:44:50] JSON inval data
[2015-09-23 02:44:50] json_rpc_call failed, retry after 30 seconds

r54 dump log:

Code:

[2015-09-23 02:50:43] NVAPI GPU monitoring enabled.
[2015-09-23 02:50:43] 1 miner thread started, using 'neoscrypt' algorithm.
[2015-09-23 02:50:43] Binding thread 0 to cpu 0 (mask 1)
[2015-09-23 02:50:43] JSON protocol request:
{"method": "getwork", "params": [], "id":0}


* Rebuilt URL to: http://127.0.0.1:3333/
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 3333 (#0)
* Server auth using Basic with user 'phoenixcoinpc'
> POST / HTTP/1.1

Authorization: Basic cGhvZW5peGNvaW5wYzp4

Host: 127.0.0.1:3333

Accept-Encoding: identity

Content-Type: application/json

Content-Length: 45

User-Agent: ccminer/1.5.54-git(SP-MOD)

X-Mining-Extensions: longpoll noncerange reject-reason

X-Mining-Hashrate: 0



< HTTP/1.1 200 OK

< Date: Wed, 23 Sep 2015 07:50:43 +0000

< Connection: keep-alive

< Content-Length: 311

< Content-Type: application/json

< Server: phoenixcoin-json-rpc/v0.6.6.0

< 

* Connection #0 to host 127.0.0.1 left intact
[2015-09-23 02:50:43] JSON protocol response:
{
   "error": null,
   "result": {
      "algorithm": "neoscrypt",
      "data": "020000009e9408c3bdb43e00e98c4a7be4f7a3bc916192166a99c3b6bac9446c7a89d3530066c080ddfeaba4403860b0ecdc1717783955c2403c9eac01b01a6dab94f81fcd590256549e071d000000003d010000",
      "target": "0000000000000000000000000000000000000000000000000000549e07000000"
   },
   "id": 0
}

[2015-09-23 02:50:43] got new work in 3.00 ms
[2015-09-23 02:50:43] JSON protocol request:
{"method": "getblocktemplate", "params": [], "id":0}


* Rebuilt URL to: http://127.0.0.1:3333/
* Found bundle for host 127.0.0.1: 0x729f590
* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 3333 (#0)
* Server auth using Basic with user 'phoenixcoinpc'
> POST / HTTP/1.1

Authorization: Basic cGhvZW5peGNvaW5wYzp4

Host: 127.0.0.1:3333

Accept-Encoding: identity

Content-Type: application/json

Content-Length: 54

User-Agent: ccminer/1.5.54-git(SP-MOD)

X-Mining-Extensions: longpoll noncerange reject-reason

X-Mining-Hashrate: 0



< HTTP/1.1 500 Internal Server Error

< Date: Wed, 23 Sep 2015 07:50:43 +0000

< Connection: close

< Content-Length: 1155

< Content-Type: application/json

< Server: phoenixcoin-json-rpc/v0.6.6.0

< 

* Closing connection 0
[2015-09-23 02:50:43] JSON protocol response:
{
   "error": {
      "code": -1,
      "message": "getblocktemplate [params]\nIf [params] does not contain a \"data\" key, returns data needed to construct a block to work on:\n  \"version\" : block version\n  \"previousblockhash\" : hash of current highest block\n  \"transactions\" : contents of non-coinbase transactions that should be included in the next block\n  \"coinbaseaux\" : data that should be included in coinbase\n  \"coinbasevalue\" : maximum allowable input to coinbase transaction, including the generation award and transaction fees\n  \"target\" : hash target\n  \"mintime\" : minimum timestamp appropriate for next block\n  \"curtime\" : current timestamp\n  \"mutable\" : list of ways the block template may be changed\n  \"noncerange\" : range of valid nonces\n  \"sigoplimit\" : limit of sigops in blocks\n  \"sizelimit\" : limit of block size\n  \"bits\" : compressed target of next block\n  \"height\" : height of the next block\nIf [params] does contain a \"data\" key, tries to solve the block and returns null if it was successful (and \"rejected\" if not)\nSee https://en.bitcoin.it/wiki/BIP_0022 for full specification."
   },
   "result": null,
   "id": 0
}

[2015-09-23 02:50:43] JSON-RPC call failed: getblocktemplate [params]
If [params] does not contain a "data" key, returns data needed to construct a block to work on:
  "version" : block version
  "previousblockhash" : hash of current highest block
  "transactions" : contents of non-coinbase transactions that should be included in the next block
  "coinbaseaux" : data that should be included in coinbase
  "coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees
  "target" : hash target
  "mintime" : minimum timestamp appropriate for next block
  "curtime" : current timestamp
  "mutable" : list of ways the block template may be changed
  "noncerange" : range of valid nonces
  "sigoplimit" : limit of sigops in blocks
  "sizelimit" : limit of block size
  "bits" : compressed target of next block
  "height" : height of the next block
If [params] does contain a "data" key, tries to solve the block and returns null if it was successful (and "rejected" if not)
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
[2015-09-23 02:50:54] CTRL_C_EVENT received, exiting

[qqqq]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SRC - https://securechain.info/wiki/Download

Days to generate one block mining solo: 0.32 Day(s) on 6300 Kh\s

Soloing is broken. I tried it via several release 56, 61, 66 etc

[theotherme]

djm34, why do you care about the broken solomining? Release 68 is more stable than ever, and everybody is using my mod because it is the fastest opensource in the world. Optimizing for the Maxwell is not straight forward because there are so many different cards with different properties. There are different operating systems with different adressmodes and drivers. But my modded kernals are the fastest on all the cards and operating systems.

The solomining bug can be fixed. T Nelson is looking at it. If you think solomining is important for you should donate some mBTC to him to motivate.

Actually, I care because when you spend some time to develop code and you see it butchered elsewhere, it kind of hurt.
I don't deny what you did for quark or x11, however the gain of speed of other algos is at most marginal.
People use your release because it is hyped, not necessarily because it is the fastest.
And because your release is in that position, it would be good if it was a cleaned one rather the half broken it is half of the time.
(you could create a development fork like Epsylon3 )

And I think you over-read  a little what T Nelson wrote...  

[pallas]

This version is not marginally faster.
If you ever compared quark, neoscrypt and x11 with the other forks you'll know it's between 10 and 30 percent faster.

[sp_]

Actually, I care because when you spend some time to develop code and you see it butchered elsewhere, it kind of hurt.
I don't deny what you did for quark or x11, however the gain of speed of other algos is at most marginal.
People use your release because it is hyped, not necessarily because it is the fastest.
And because your release is in that position, it would be good if it was a cleaned one rather the half broken it is half of the time.
(you could create a development fork like Epsylon3 )
And I think you over-read  a little what T Nelson wrote...  

Epsylons fork 1.6.6 is mining quark at 12MHASH mine is mining at 17,3MHASH (gtx 970). The small commit's I have done over time, does pay off in the end. I sometimes merge pullrequests from other developers. Klaus_t,pallas,t nelson and flipclip.
It's open source, It's free, and it's the fastest out there..

[sp_]

sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Before I started 1 year ago quark was doing 4.5 on the 750ti, you can compile djm34's version here and test for your self:

https://github.com/djm34/ccminer-standard

Solomining works, but my release 68 is 45% faster.

[bathrobehero]

Fired my poor gtx750 1gb again, 1500/1600 = 6300kh/s (release 68, quark)

GTX750TI-OC-2GD5 - 7250kh/s - Clocks +180Mhz/+180Mhz (release 68, quark)

Pretty good, but how much is the consumption? Hash/watt

The 1gb 750 has a TDP of just 35W in the bios.
And on standard clocks it uses around 40Watts to produce 5 MHASH of quark. (125KHASH per watt).
A 970 gigabyte windforce gaming will do around 17MHASH in 180 watts. (94.444444444444KHASH per watt)


So the junior card is 32% bether is hash/watt, but you need alot more cards/motherboards/ram/cpu's/psu's So I guess none of you are mining with the gtx 750 ?

Please sp_, I can't beg you enough to get a watt meter. There are no magic cards, the 1GB 750 cards have the exact same power consumption profiles as the 2GB 750 Ti's in their BIOS, feel free to see for yourself:

https://www.techpowerup.com/vgabios/index.php?architecture=&manufacturer=&model=GTX+750&interface=&memType=&memSize=

Benchmarks with clear power consumption figures:
https://www.techpowerup.com/reviews/ASUS/GTX_750_OC/23.html
http://us.hardware.info/reviews/5221/13/nvidia-geforce-gtx-750--750-ti-review-the-first-maxwell-generation-gpus-power-consumption
http://www.guru3d.com/articles_pages/msi_geforce_gtx_750_and_750_ti_gaming_review,5.html

[sp_]

I have checked power consumption on my gigabyte card and at 1420core/3300 mem it get 44-45watt.
Also i checked with -X1 ... -X17 and found that power consumption differs only 1-2 watt.

Did you use a watt meter?

[zTheWolfz]

@t-nelson

See my last "edited" post above for more data, if there is something else I can add to the command line that would be of more help please post and I'll do my best to get you the info you need. Something seems to be missing or broken after this line "id": 0

[bensam1231]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

PRECISE--

OK, you have a point, DJ.  I was posting in sp_'s thread, however.  I DO try to be clear about OS, version, hash rates, clock rates, spelling and punctuation, etc.  I've groaned about the bleeding edge speed before, myself, but sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Maybe a few releases should focus on code clean-up and standardization rather than speed.  Future improvements would then be on a stronger base.       --scryptr

Considering DJM doesn't release anything, he doesn't really offer an alternative. I'd rather take a buggy and sometimes glitchy version with speed over one that's getting steamrolled by the private miners (usually released by the same person).

Also, everyone is getting their panties in a knot about solo mining. Who even solo mines now days? Only people who do have to have a relatively large farm for that to actually work (on the profitable coins). Perhaps consider charging them for a solo mining version. The amount of shits I have for this issue are about 0 as it is I'm sure for the majority of miners as we're all on pools... because, you know, we can't magic 5% of the network hashrate out of our asses.

Seems as though people are on SP's balls because profits are tight and he's offering a open source-public miner, which hurts the private miner business. For instance, DJM's toted L2V2 rewrite isn't even worthwhile anymore compared to Quark or other alternatives.

[ol92]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

PRECISE--

OK, you have a point, DJ.  I was posting in sp_'s thread, however.  I DO try to be clear about OS, version, hash rates, clock rates, spelling and punctuation, etc.  I've groaned about the bleeding edge speed before, myself, but sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Maybe a few releases should focus on code clean-up and standardization rather than speed.  Future improvements would then be on a stronger base.       --scryptr

Considering DJM doesn't release anything, he doesn't really offer an alternative. I'd rather take a buggy and sometimes glitchy version with speed over one that's getting steamrolled by the private miners (usually released by the same person).

Also, everyone is getting their panties in a knot about solo mining. Who even solo mines now days? Only people who do have to have a relatively large farm for that to actually work (on the profitable coins). Perhaps consider charging them for a solo mining version. The amount of shits I have for this issue are about 0 as it is I'm sure for the majority of miners as we're all on pools... because, you know, we can't magic 5% of the network hashrate out of our asses.

Seems as though people are on SP's balls because profits are tight and he's offering a open source-public miner, which hurts the private miner business. For instance, DJM's toted L2V2 rewrite isn't even worthwhile anymore compared to Quark or other alternatives.

Without downplaying what sp_ has bring to us, the nvidia maxwell "small" miners communauty, he has built on top of what others like djm, truvot, tsiv,and before KlausT cbuchner had already built. Without them ccminer wouldn't be what it is.
On the other hand solomining is important for small miners : this allow us to benefit from recently launched coins or low profiles ones, often more profitable. Moreover, ethereum (rather shift, exp which have lower difficulties) mining is more profitable in solo, due to very fast blocks which penalized pools mining if you have not low latency network between your rig and the pool.
 

[serg_25]

I have checked power consumption on my gigabyte card and at 1420core/3300 mem it get 44-45watt.
Also i checked with -X1 ... -X17 and found that power consumption differs only 1-2 watt.

Did you use a watt meter?

of course. don't have any other ways to check power consumption of my card

[qqqq]

To bensam1231, yeah that's right, solo miners is a small percent but if software has a bug it must be fixed i guess.

[theotherme]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

PRECISE--

OK, you have a point, DJ.  I was posting in sp_'s thread, however.  I DO try to be clear about OS, version, hash rates, clock rates, spelling and punctuation, etc.  I've groaned about the bleeding edge speed before, myself, but sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Maybe a few releases should focus on code clean-up and standardization rather than speed.  Future improvements would then be on a stronger base.       --scryptr

Considering DJM doesn't release anything, he doesn't really offer an alternative. I'd rather take a buggy and sometimes glitchy version with speed over one that's getting steamrolled by the private miners (usually released by the same person).

Also, everyone is getting their panties in a knot about solo mining. Who even solo mines now days? Only people who do have to have a relatively large farm for that to actually work (on the profitable coins). Perhaps consider charging them for a solo mining version. The amount of shits I have for this issue are about 0 as it is I'm sure for the majority of miners as we're all on pools... because, you know, we can't magic 5% of the network hashrate out of our asses.

Seems as though people are on SP's balls because profits are tight and he's offering a open source-public miner, which hurts the private miner business. For instance, DJM's toted L2V2 rewrite isn't even worthwhile anymore compared to Quark or other alternatives.

first: I don't release anything ? seriously ?  
I have released most of the algo which were released this year:  lyra (both versions, several optimizations and rewrite and for both nvidia and amd) neoscrypt and several others algos.  

second: stop accusing other devs. to release private miners all the time, which is your excuse for everything
(you know very well it isn't true at least for me since you contacted me to have my private neoscrypt and I told you no.
I release only very rarely private miners and mostly on a trust basis (if the fee is large enough, I could trust you more... yeah well...  ))

Have you considered that releasing something so that donation go to someone else or worst, as you just showed, that people like you don't even know I did release it, is at best irritating ?
It isn't a question of profit, donation never represented a lot, it is just a question of fairness and having his work acknowledged...  and again, I am usually paid for what I develop and open-source...

and sorry for being a bit direct... but I am saying out loud what many have been thinking for quite a while...
and seriously the only thing we ask is that the release process gets a little more serious than what happened over the past few months... where broken releases alternate with roll-back fixing in part the change which causes the release for being broken in the first place...

last: solo mining is important for many and there is no reason for it to get ignored.

[pallas]

I think this discussion is worthless.

There is tpruvot fork from which most of the others were forked from.

It's the best one in terms of features but it doesn't have all the optimisations.
You can use it.

OR

Use sp fork if you want the speed.
Or Klaust's fork. Or Djm34's. Or make your own (tip: take tpruvot and apply the optimisations). Or help fixing the bugs.

Whatever you want to do, stop whining and go ahead :-D

BTW there will never be fair rewards for the miners because you can't measure the value of each one's work. And anyway it's a handful of dollars worth.

[sp_]

I am usually paid for what I develop and open-source...

And after you open source it, somebody works for free and optimize your work and get a few beers in donations. I don't understand your problem.. Miners needs the software to be up do date to earn money. Old kernals are not profitable any more.