sp, and all other mining developers, I suggest you to watch development of this: https://bitcointalksearch.org/topic/m.12164065
There has to be a census reached about Lyra2REv2 diff multiplicator.
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 991. (Read 2347601 times)
edit: I get "illegal memory access" with the shared memory method
What architecture? The benchmark (-U -M) and difficulty (-U -S) tests run fine on the shared memory code.
I don't do real mining
.To switch between shared on shuffled , you need to modify SHUFFLE_MIN_VER (on top of the .cu file) from 350 to i.e. 600 (fictive Compute 6.0).
I have pull requested the fix for animecoin on util.cpp, let's hope it goes to the right fork this time ;-)
nice ...
so that would mean that we wouldnt need to edit and can compile direct from git? ...
if sp includes it that is - is that right? ...
#crysx
Yes, it compiles for me now; and SP_ has already merged the pull request, so you can go on git pulling ;-)
well - i can only do it remotely at the moment ...
not as satisfying as pulling at the office
...git that is - pulling git ... ahem ...
think ill just clone and start over ... hehehe ...
tanx ...
#crysx
if you modified some files yourself and it refuses to do "git pull", just run "git checkout [file]" to revert it to the original state ;-)
I have pull requested the fix for animecoin on util.cpp, let's hope it goes to the right fork this time ;-)
nice ...
so that would mean that we wouldnt need to edit and can compile direct from git? ...
if sp includes it that is - is that right? ...
#crysx
Yes, it compiles for me now; and SP_ has already merged the pull request, so you can go on git pulling ;-)
well - i can only do it remotely at the moment ...
not as satisfying as pulling at the office
...git that is - pulling git ... ahem ...
think ill just clone and start over ... hehehe ...
tanx ...
#crysx
I have pull requested the fix for animecoin on util.cpp, let's hope it goes to the right fork this time ;-)
nice ...
so that would mean that we wouldnt need to edit and can compile direct from git? ...
if sp includes it that is - is that right? ...
#crysx
Yes, it compiles for me now; and SP_ has already merged the pull request, so you can go on git pulling ;-)
I have pull requested the fix for animecoin on util.cpp, let's hope it goes to the right fork this time ;-)
nice ...
so that would mean that we wouldnt need to edit and can compile direct from git? ...
if sp includes it that is - is that right? ...
#crysx
GENOIL--
Genoil will be posting an SP_ modded Windows Ethminer binary sometime today. He announced this on his thread, page 7, linked a few posts back. --scryptr
EDIT: It is posted! The link is on the bottom of page 7. CPU usage is waaaaay down. --scryptr
Genoil will be posting an SP_ modded Windows Ethminer binary sometime today. He announced this on his thread, page 7, linked a few posts back. --scryptr
EDIT: It is posted! The link is on the bottom of page 7. CPU usage is waaaaay down. --scryptr
Ether trying to sync at leat 16hours.Is it normal or smthg wrong? 
)
) If you used the genesis_block.json in the geth then it should only take 10-15 minutes.
Once synced it always scrolls so you might be synced but not realizing it.
Keep an eye on the geth for the block number and check an explorer to see if they match.
EDIT: I see scryptr already mentioned most of this.
I have pull requested the fix for animecoin on util.cpp, let's hope it goes to the right fork this time ;-)
Yeah syncing for me took about 20-30m. Did it on two machines.
Ether trying to sync at leat 16hours.Is it normal or smthg wrong? )
) NORMAL BUT NOT TRUE--
Geth trys to sync constantly. If you check a page with blockchain history, and the blocks scrolling by are only one or two ahead of the latest posted blocks, you are synched. It takes only a short time, but it is not a GUI, so it isn't obvious. I don't have the link, but a search should find the ETH blockchain info. Geth is extremely verbose as default.
I was told it takes only 20-30 minutes. --scryptr
Ether trying to sync at leat 16hours.Is it normal or smthg wrong? )
) Quote
Somebody shared a pre-compiled CUDA Compute 50 Linux binary on Genoil's blog thread, and I toyed with it.
linky?
LINKY--
Here is a link to page 6 of Genoil's thread: "https://forum.ethereum.org/discussion/2227/cuda-miner/p6"
Look for poster SuchFakeAccount near the bottom of the page. He kindly said he would compile other binaries if asked. Pages 6 and 7 have a few binaries on them, just read the thread.
The file has some dependencies, and I don't have them. If I could place the dependencies in the directory like Windows *.dll files, I would. I just don't want to install Ethereum on my good rig and then have complications with CCminer compilation.
--scryptr
Looks like he/she noticed that and has now updated it with missing libraries.
What sort of luck are you guys having with mining Ethereum? I've been mining for about 24 hours and haven't found a block. Everything is so glitchy and buggy I can't tell if it's working right even though it should be.
Since there is no pool it seems as though this might be sorta pointless too. Pools are there because mining alone doesn't net the same results, even though it's supposed to be averaged over time it usually doesn't work that way. I may switch back to VTC till this ends up a bit more mature.
Since there is no pool it seems as though this might be sorta pointless too. Pools are there because mining alone doesn't net the same results, even though it's supposed to be averaged over time it usually doesn't work that way. I may switch back to VTC till this ends up a bit more mature.
I HIT ONE BLOCK--
I have 5 ETH coins after mining solo since sometime Friday. The prediction is about 10 coins a week for 25Mh/s, my current speed. Without a GUI wallet, I have to check my balance every few hours or so. Mining works. If optimized in CUDA code, I could earn a lot more. --scryptr
Try to see if 2>> ETHlog.txt flag will work with the miner software, if it does it will place a log file within the folder where the miner resides.
the 2>> name-can-be-what-ever-you-want-log.txt You can then open that log with notepad and use the search for yay! to find blocks you found
or boo! to find bad blocks within the log file. Asumming it uses yay and boo.
Quote
Somebody shared a pre-compiled CUDA Compute 50 Linux binary on Genoil's blog thread, and I toyed with it.
linky?
LINKY--
Here is a link to page 6 of Genoil's thread: "https://forum.ethereum.org/discussion/2227/cuda-miner/p6"
Look for poster SuchFakeAccount near the bottom of the page. He kindly said he would compile other binaries if asked. Pages 6 and 7 have a few binaries on them, just read the thread.
The file has some dependencies, and I don't have them. If I could place the dependencies in the directory like Windows *.dll files, I would. I just don't want to install Ethereum on my good rig and then have complications with CCminer compilation.
--scryptr
Quote
Somebody shared a pre-compiled CUDA Compute 50 Linux binary on Genoil's blog thread, and I toyed with it.
linky?
edit: I get "illegal memory access" with the shared memory method
hm that probably got borked in all the mess...it used to be fine.
i'll see if i can fix that tomorrow.
ETHMINER and LINUX--
Somebody shared a pre-compiled CUDA Compute 50 Linux binary on Genoil's blog thread, and I toyed with it. Just as in CCminer, there are shared library files. The file will not run unless you have the Ethereum system installed properly. I don't think I will install it on my 750ti rig.
If I rebuild my AMD 280x rig, I will install it, and run ethminer instead of sgminer. It all depends on ETH and its value on the coin market. I do suspect that Ethminer would run smoothly, and with less energy usage and the headaches associated with sgminer. --scryptr
Somebody shared a pre-compiled CUDA Compute 50 Linux binary on Genoil's blog thread, and I toyed with it. Just as in CCminer, there are shared library files. The file will not run unless you have the Ethereum system installed properly. I don't think I will install it on my 750ti rig.
If I rebuild my AMD 280x rig, I will install it, and run ethminer instead of sgminer. It all depends on ETH and its value on the coin market. I do suspect that Ethminer would run smoothly, and with less energy usage and the headaches associated with sgminer. --scryptr
There is no projectfile for visual studio 2013. and the cuda 7.0 compiler is slow. Perhaps 30% faster with cuda 6.5.
You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
doesn't make much of a difference actually, everything is slowed down my mem load/store. (moving to 32bit would probably help a little as well but get some problem with some dll)You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
actually can't get my 780ti/750ti to work properly because of the high mem allocation (which actually isn't so high... but it doesn't like that)
I've spent a lot of time already trying to figure out why the algo doesn't perform well on some windows/nvidia combo's. this gtx750ti i have at home gets only 500KH, but when i pull it out and place it along a gtx780 i run at work, it pulls 8MH/s (as it should, and most linux people report).
The 1GB RAM allocation (both on RAM and per GPU) is for the "dagger" file. This is used in the "middle" part of the ethash algo, where a random 64 node path is walked through that file. This takes up most of the time, about 85% compared to the keccak stuff. The dagger file updates each 30,000 blocks. This all with the goal of fighting off ASIC development.
The code as I have in git now is a bit of a mess, with two approaches of running the dagger loop dumped into a single file. One approach uses shared memory (compute_hash), whereas the other one warp shuffles instead (compute_hash_shuffle). Turned out to hardly make a difference. By default shuffle is now used.
Currently looking into splitting the whole thing back up into 3 parts (keccak/dagger/keccak) and see if i can run these kernels concurrently. there's a branch for that, cudaminer-staged.
actually I have 2 980 which runs ok, but the 2 other card 780ti + 750ti are doing about 1.5MH/s together... (can be due to the fact they are on riser...)
edit: I get "illegal memory access" with the shared memory method
There is no projectfile for visual studio 2013. and the cuda 7.0 compiler is slow. Perhaps 30% faster with cuda 6.5.
You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
doesn't make much of a difference actually, everything is slowed down my mem load/store. (moving to 32bit would probably help a little as well but get some problem with some dll)You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
actually can't get my 780ti/750ti to work properly because of the high mem allocation (which actually isn't so high... but it doesn't like that)
I've spent a lot of time already trying to figure out why the algo doesn't perform well on some windows/nvidia combo's. this gtx750ti i have at home gets only 500KH, but when i pull it out and place it along a gtx780 i run at work, it pulls 8MH/s (as it should, and most linux people report).
The 1GB RAM allocation (both on RAM and per GPU) is for the "dagger" file. This is used in the "middle" part of the ethash algo, where a random 64 node path is walked through that file. This takes up most of the time, about 85% compared to the keccak stuff. The dagger file updates each 30,000 blocks. This all with the goal of fighting off ASIC development.
The code as I have in git now is a bit of a mess, with two approaches of running the dagger loop dumped into a single file. One approach uses shared memory (compute_hash), whereas the other one warp shuffles instead (compute_hash_shuffle). Turned out to hardly make a difference. By default shuffle is now used.
Currently looking into splitting the whole thing back up into 3 parts (keccak/dagger/keccak) and see if i can run these kernels concurrently. there's a branch for that, cudaminer-staged.
Jump to: