tsiv
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 04:55:40 PM |
|
Great work! marvelous first few posts!
building in windows right now......
Is that a burning house I smell..?
|
|
|
|
cryptomines
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 05:02:45 PM |
|
Great work! marvelous first few posts!
building in windows right now......
Is that a burning house I smell..? lol, no, still compiling. I shoulda used my other machine. I have fire extinguishers at the ready
|
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 05:08:26 PM |
|
Aaand it's out: https://github.com/tsiv/ccminerInsert the standard "if your house burns down, totally not my fault" disclaimer here. Windows build should be fine as well, at least I managed to compile it myself. I won't be releasing any binaries, feel free to do so yourselves though. Christ gonna release killer goretl version probably before or during weekend. The new version will upgrade x11 speed gtx 750 ti to 2.8 - 3. Maybe u should wait for the new release and implement your code which will increase x13 speed significantly. Or maybe both of u can combine code and do a combine release ? So the new version will have killer goretl + x13. That is pretty exciting.
Should be an easy modification, right now my X13 is using the same code for the first 11 algos as the original X11. At the simplest it just takes a recompile after throwing in the new groestl version. no reason to wait ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Actually I just curious to know what I did wrong I have a very good idea about that ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I did end up messing with the original echo hash, it seemed to have an extraneous xor that made the full 512 bit hash come out wrong. Then using that result for the additional hamsi+fugue hashes kinda ends badly. The funny thing is that it worked fine for X11 because it was the last hashing algo in the chain and the X11 algo only takes the first 256 bits of the hash, discarding the rest and the flipped bit ended up in the discarded part. Was a bitch to track down for sure. ok, it's working. Actually, I had a couple of other mistakes regarding bit swapping (I am rather bit illiterate...), which could have been solved by random trials ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) but for the echo, it was clearly outside my level of competence (however I was suspecting something funny, as it wasn't possible to add new algo on top of this one). In terms of speed I am getting between 1700khah/s and 1800khash/s with the 750ti. I found something else interesting, it is possible to run on X13 p2pool with X11 algo ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) and to get validated share (not sure if it works for the "big" share, but for the rest it works)
|
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 05:11:54 PM |
|
Great work! marvelous first few posts!
building in windows right now......
Is that a burning house I smell..? lol, no, still compiling. I shoulda used my other machine. I have fire extinguishers at the ready actually, it would be better to have only X13, if it compiles entirely both X11 and X13 it can take some times
|
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
tsiv
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 05:24:18 PM |
|
Great work! marvelous first few posts!
building in windows right now......
Is that a burning house I smell..? lol, no, still compiling. I shoulda used my other machine. I have fire extinguishers at the ready actually, it would be better to have only X13, if it compiles entirely both X11 and X13 it can take some times X13 just adds two more hashing algos to compile, it doesn't do the 11 X11 hashes twice or anything like that. That said, both the original shavite and my fugue seem to take forever to compile for some reason.
|
|
|
|
DemosMirak
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 05:34:39 PM |
|
Aaand it's out: https://github.com/tsiv/ccminerInsert the standard "if your house burns down, totally not my fault" disclaimer here. Windows build should be fine as well, at least I managed to compile it myself. I won't be releasing any binaries, feel free to do so yourselves though. Christ gonna release killer goretl version probably before or during weekend. The new version will upgrade x11 speed gtx 750 ti to 2.8 - 3. Maybe u should wait for the new release and implement your code which will increase x13 speed significantly. Or maybe both of u can combine code and do a combine release ? So the new version will have killer goretl + x13. That is pretty exciting.
Should be an easy modification, right now my X13 is using the same code for the first 11 algos as the original X11. At the simplest it just takes a recompile after throwing in the new groestl version. no reason to wait ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Actually I just curious to know what I did wrong I have a very good idea about that ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I did end up messing with the original echo hash, it seemed to have an extraneous xor that made the full 512 bit hash come out wrong. Then using that result for the additional hamsi+fugue hashes kinda ends badly. The funny thing is that it worked fine for X11 because it was the last hashing algo in the chain and the X11 algo only takes the first 256 bits of the hash, discarding the rest and the flipped bit ended up in the discarded part. Was a bitch to track down for sure. ok, it's working. Actually, I had a couple of other mistakes regarding bit swapping (I am rather bit illiterate...), which could have been solved by random trials ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) but for the echo, it was clearly outside my level of competence (however I was suspecting something funny, as it wasn't possible to add new algo on top of this one). In terms of speed I am getting between 1700khah/s and 1800khash/s with the 750ti. I found something else interesting, it is possible to run on X13 p2pool with X11 algo ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) and to get validated share (not sure if it works for the "big" share, but for the rest it works) You have a working version of CCminer, capable of mining X13? Would you care to share ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) (BTW, I use an GTX 770)?
|
BTC: 13enECLM3M3gjQDoBKouXuYFG4zXaDdDPx LTC: LRTbQNQcRjZV51PivQdhK7zpMtJYPouqR9
|
|
|
|
Equitum
Newbie
Offline
Activity: 29
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 06:03:13 PM |
|
What will be the next step for ccminer going forward ? It seems that there is no news regarding new release or development. Can we expect to see anything new this month ?
I think even before the weekend. Adding that killer groestl should be an easy exercise. Would be great !!! Groestl is very energy efficient, great algo. Not to mention that it would speed up X11 as well. And Jackpot and NIST5!
|
|
|
|
tarzanbigcity
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 06:46:38 PM |
|
Miner just closes. This is my bat file to launch. Tested on TMB
ccminer-x13.exe -o stratum+tcp://east01.us.trademybit.com:5550 -u user -p pass pause
|
|
|
|
cryptomines
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 06:52:02 PM |
|
Miner just closes. This is my bat file to launch. Tested on TMB
ccminer-x13.exe -o stratum+tcp://east01.us.trademybit.com:5550 -u user -p pass pause
ccminer-x13.exe -a x13 -o stratum+tcp://east01.us.trademybit.com:5550 -u user -p pass pause You need the algo argument. I'm getting a little over 1700 kh/s per card.
|
|
|
|
tarzanbigcity
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:04:15 PM |
|
Confirmed 1700 per card on EVGA 750 TI SC
|
|
|
|
|
gpuminer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:42:44 PM |
|
So here's my profitability list including X13 (using 1.75MH as hashrate per 750ti, as tsiv screenshotted ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ) http://pastebin.com/S5mUXWhvAgain prices aren't averages, so it could change in an instant ^^" But all formulas should be OK now. For some reason talk coin profit calculation seems to be different from other coin. I always calculate i will get more coins based on difficulties but in reality i am getting way less when i check pool per hour earning. Maybe u should check that out.
|
|
|
|
italeffect
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:43:10 PM |
|
Windows binary works for me too. 3 x 750ti rig is giving me about 5400 khash/s with a 100/300 overclock on x13
|
Dash: Xdopotr3eAHpsSCMkUyU2YWP3WQWb5X3t8
|
|
|
S_tring
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 252
Merit: 102
OPEN Platform - Powering Blockchain Acceptance
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:43:35 PM |
|
It's not a ccminer release.
|
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:47:14 PM |
|
doesn't seem to be the better way to ask... (if I was managing it, and had read your comment; you could wait a very long time to get an update...)
|
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
tarzanbigcity
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:47:28 PM |
|
Windows binary works for me too. 3 x 750ti rig is giving me about 5400 khash/s with a 100/300 overclock on x13
Are you using the EVGA cards? The ones without the pcie power port?
|
|
|
|
Bombadil
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:48:21 PM |
|
I'm trying to build it myself, but for some reason, Visual Studio decided to not let me have compute_50 anymore, only up to 35. I have cuda toolkit 5.5, any ideas? It worked before :sI'm a fool sometimes, ignore me ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) (it's compute_35 but with the constant at 1) It's not a ccminer release. Neither is the one with the SIMD hash boost? But, gpuminer, just wait a bit, first testing time ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
|
gpuminer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:48:57 PM |
|
doesn't seem to be the better way to ask... (if I was managing it, and had read your comment; you could wait a very long time to get an update...) i dont mind waiting. Just a reminder. I am used to waiting when it comes to ccminer.
|
|
|
|
S_tring
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 252
Merit: 102
OPEN Platform - Powering Blockchain Acceptance
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 12, 2014, 07:52:22 PM |
|
I'm trying to build it myself, but for some reason, Visual Studio decided to not let me have compute_50 anymore, only up to 35. I have cuda toolkit 5.5, any ideas? It worked before :s ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FAKI8YuZ.png%3F1&t=665&c=MEvwiOXg8HVRGQ) It's not a ccminer release. Neither is the one with the SIMD hash boost? But, gpuminer, just wait a bit, first testing time ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) All versions on cudamining.cc are Christians code, this X13 isn't. That's what I meant.
|
|
|
|
|