Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 208. (Read 877844 times)
July 03, 2014, 02:45:57 AM
I'm noticing another interesting issue. So, based on the conf I provided earlier, you can see I rent on betarigs. I am noticing that when I rent out my rigs, the only ones that click over to betarigs are the ones that did eventually connect to nicehash. All the other ones just stay on wafflepool and don't hash. This is completely unacceptable, because it means when I rent only 1/3 of the rigs have been kicking over, and the rest of them essentially go dead. I never had this problem with the old software. Anyone else?
July 02, 2014, 10:05:56 PM
my 7850 isn't working with any bitblock kernel
Commit from 7 hours ago: 27709ced8364b164c6342a8f38ffdedd9aa91d90
7850 with 1GB of GPU memory, xubuntu 13.10, catalyst driver 14.6
In debug, after if receives work from a pool, it keeps saying the number of staged work items is greater than the maximum (which is set at whatever queue is), and then discards the work item.
^^^ repeated again and again
If I change the queue number, the number of staged work items is still always one more than the "max" and the work get discarded. I've tried tons of different settings, and if I don't have it in text mode, the hashrates all stay at 0 and after a few minutes the cards are declared sick and hung.
advice?
Commit from 7 hours ago: 27709ced8364b164c6342a8f38ffdedd9aa91d90
7850 with 1GB of GPU memory, xubuntu 13.10, catalyst driver 14.6
In debug, after if receives work from a pool, it keeps saying the number of staged work items is greater than the maximum (which is set at whatever queue is), and then discards the work item.
Code:
Selecting BITBLOCKPOOL for work
Generated stratum merkle [.......]
Generated stratum header [........]
Work job_id [....] nonce2 [..] ntime [......]
Generated target [.......]
Generated stratum work
Pushing work from BITBLOCKPOOL to hash queue
35.0 C F: 20%(1203RPM) E: 860MHz M: 1200Mhz V: 1.138V A: 99% P: 0%
32.0 C F: 20%(1132RPM) E: 860MHz M: 1200Mhz V: 1.138V A: 99% P: 0%
34.0 C F: 20%(1047RPM) E: 860MHz M: 1200Mhz V: 1.138V A: 99% P: 0%
Staged work: total (2) > max (1), discarding
Discarded work
If I change the queue number, the number of staged work items is still always one more than the "max" and the work get discarded. I've tried tons of different settings, and if I don't have it in text mode, the hashrates all stay at 0 and after a few minutes the cards are declared sick and hung.
advice?
July 02, 2014, 09:21:49 PM
I agree Mannyg, once they connect they're fine, no issues, but if you restart... Also, I have my 280x hashing around 2.6Mh on 14.6 beta drivers in BAMT. I use the same settings for x11/x13/x15, the below conf is for my Sapphire Vapor-X 280x.
"intensity" : "16",
"worksize" : "256",
"thread-concurrency" : "8192",
"gpu-threads" : "2",
"gpu-engine" : "1080",
"gpu-memclock" : "1450",
"failover-only" : true,
"no-pool-disable" : true,
"api-network" : true,
"api-listen" : true,
"api-port" : "4028",
"gpu-powertune" : "0"
Sure wish Nicehash would chime in and let us know what is up with these connection issues!
"intensity" : "16",
"worksize" : "256",
"thread-concurrency" : "8192",
"gpu-threads" : "2",
"gpu-engine" : "1080",
"gpu-memclock" : "1450",
"failover-only" : true,
"no-pool-disable" : true,
"api-network" : true,
"api-listen" : true,
"api-port" : "4028",
"gpu-powertune" : "0"
Sure wish Nicehash would chime in and let us know what is up with these connection issues!
July 02, 2014, 09:19:48 PM
U can try my bitblock.bin I'm getting 2450kh/s with a 7950@1035/1500
https://mega.co.nz/#!zM8FXJwZ!E4u3wCEKR0y0BeXMwvEIDPGrYdgLcuVw5Zep13w4rNw
config
https://bitcointalksearch.org/topic/m.7646091
https://mega.co.nz/#!zM8FXJwZ!E4u3wCEKR0y0BeXMwvEIDPGrYdgLcuVw5Zep13w4rNw
config
https://bitcointalksearch.org/topic/m.7646091
July 02, 2014, 09:06:53 PM
I've been noticing lately that Nicehash, when connected, stays hashing fine.... that is until you restart the miner or something happens where your rig reboots, then it wont connect for a looooong while. I had to set my CGWatcher to keep trying indefinitely else it would just sit there after 3 failed attempts to start.
Has anyone managed to get their 280x's or 290's X15 speed to hash at 3.5x times their Scrypt hash rate? I cant get my 280x's barely at 2.3MH/s and my 290s at 2.4MH/s. I *should* be closer to 2.5MH/s and 3MH/s.
I'm using 13.12 drivers and Win8 x64, bitblock.cl kernel. Using the same engine, memclock and intensity as X11 & X13
Has anyone managed to get their 280x's or 290's X15 speed to hash at 3.5x times their Scrypt hash rate? I cant get my 280x's barely at 2.3MH/s and my 290s at 2.4MH/s. I *should* be closer to 2.5MH/s and 3MH/s.
I'm using 13.12 drivers and Win8 x64, bitblock.cl kernel. Using the same engine, memclock and intensity as X11 & X13
July 02, 2014, 08:09:31 PM
I'm still at 15 at Nicehash and 8 at Wafflepool. When did this start for you? For me the connection issues happened immediately after my miner upgrade, and interestingly enough, when I go back to the old miner, it still doesn't connect. For me this was when X15 became active on betarigs, I think Saturday the 28th. I guess I can't understand the issue because I'm using the nicehash build of sgminer which they sponsored to make work with their website. I will say there was one day one time when I restarted the miners and they connected instantly to nicehash, but that was only one time.
July 02, 2014, 08:00:54 PM
Quote
For all of you who are using NiceHash: today we had another DDoS (purely network related), I'm sorry for that. Nothing was lost, but as you've experienced there has been lots of disconnects both from providers rigs an buyers orders. Some miners might still having issues by not being able to connect due to several disconnects and invalid shares resulting into unwanted bans - this will be sorted by the end of the day by automatic un-ban (for valid miners). We'll improve our DDoS protection by moving to another, better DDoS protected location. Service is now working normally and all download links are alive. Thanks for understanding and thanks for using NiceHash.
I am thinking that they did not unban quite a few IP's that are legitimate but confused with aiding with the DDOS attack. ie, I have 3 rigs in my apt that can connect, but the 16 at my farm cannot do anything with NiceHash. I'm getting a little frustrated.
July 02, 2014, 07:41:18 PM
I don't see any issues and your connection issue is exactly the same as mine. It has to be on Nicehash's end. I have gotten 3 out of my 18 rigs to connect to nicehash through sheer luck, and the rest are hashing at LTCrabbit x11 port as the failover. I guess I just have to wait it out and hope they connect?
July 02, 2014, 07:31:24 PM
I find that it takes about a half-hour to connect to nicehash, and even then, only some rigs do it. Right now, 15 of my 23 rigs are at nicehash, the other 8 are at the wafflepool. The only reason I have wafflepool is because after the other day when I upgrade to sgminer 5 I haven't been able to connect to Nicehash on startup, even if I use the 3xxx ports. I am looking at the X15 order book and there are plenty of orders with no miners, so it isn't that there isn't any room. They will be on wafflepool, and then magically the most profitable 4xxxx port shows up as alive. I dont' want to use Scrypt/Scrypt-N/Keccak configs. Here is an example conf:
{
"pools" : [
{
"url" : "stratum+tcp://r7191.g28.rigs.eu.betarigs.com:10035",
"user" : "mrbobc-7191",
"pass" : "x",
"algorithm" : "bitblock"
},
{
"name" : "Nicehash_X13",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "marucoin-mod"
},
{
"name" : "Nicehash_X11",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "darkcoin-mod"
},
{
"name" : "Nicehash_X15",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "bitblock"
},
{
"name" : "Nicehash_Nist5",
"url" : "stratum+tcp://stratum.nicehash.com:4340",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f1=0;f2=0;f3=6;f4=4;f5=0;f6=3.5;f7=12",
"algorithm" : "talkcoin-mod"
},
{
"name" : "Wafflepool_X11",
"url" : "stratum+tcp://useast.wafflepool.com:3331",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "x",
"algorithm" : "darkcoin-mod"
}
],
"intensity" : "16",
"worksize" : "256",
"thread-concurrency" : "12239",
"gpu-threads" : "2",
"gpu-engine" : "1150",
"gpu-memclock" : "1425",
"failover-only" : true,
"no-pool-disable" : true,
"api-network" : true,
"api-listen" : true,
"api-port" : "4028",
"gpu-powertune" : "20"
}
Anything wrong with the conf? Anyone else having this issue?
{
"pools" : [
{
"url" : "stratum+tcp://r7191.g28.rigs.eu.betarigs.com:10035",
"user" : "mrbobc-7191",
"pass" : "x",
"algorithm" : "bitblock"
},
{
"name" : "Nicehash_X13",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "marucoin-mod"
},
{
"name" : "Nicehash_X11",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "darkcoin-mod"
},
{
"name" : "Nicehash_X15",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f2=0;f3=6;f4=5;f5=0;f6=3.9;f7=12",
"algorithm" : "bitblock"
},
{
"name" : "Nicehash_Nist5",
"url" : "stratum+tcp://stratum.nicehash.com:4340",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "f0=0;f1=0;f2=0;f3=6;f4=4;f5=0;f6=3.5;f7=12",
"algorithm" : "talkcoin-mod"
},
{
"name" : "Wafflepool_X11",
"url" : "stratum+tcp://useast.wafflepool.com:3331",
"user" : "1MmBUf6DKTQsNGBEyrsxrTFNCbCT1vtTEK",
"pass" : "x",
"algorithm" : "darkcoin-mod"
}
],
"intensity" : "16",
"worksize" : "256",
"thread-concurrency" : "12239",
"gpu-threads" : "2",
"gpu-engine" : "1150",
"gpu-memclock" : "1425",
"failover-only" : true,
"no-pool-disable" : true,
"api-network" : true,
"api-listen" : true,
"api-port" : "4028",
"gpu-powertune" : "20"
}
Anything wrong with the conf? Anyone else having this issue?
July 02, 2014, 07:25:31 PM
w00000t... switching finally working nicely for me on all my rigs, I just needed to adjust gpu-engine settings for each pool to avoid sick gpus.
How did you manage to do it? I use miner from nicehash v5 and example conf file from https://nicehash.com/multialgo/ but when run it I always go to backup pool 3333...
This is what I get:
Sorry I'm just seeing this now, I didnt realize you had quoted my post with a question
The example conf should work OK, but it might still need you to make some edits.
For example, if you are using windows, you have to remove gpu-threads from the pool profiles and use it only in the core config. Also, to really get this working right and stable, it helps to know your GPUs default clock speeds for engine and memory.
What OS are you using? What did you set for your worker password on your machine? I started using the f0=xxx;f2=xxx;f3=xxx etc where xxx represents the speed in MH/s for that algorithm. that helps the pool decide which one you would profit from the best automatically and set the other pools to dead. that *might* be going on with your config if you just are using pass=x
also, in your image, you have 'backupool' defined and that is just there as an example for you to use an alternate site as a backup pool.. its not a real site.
July 02, 2014, 07:10:06 PM
Take a look on the order book and Limited GH/s ~ Speed GH/s
If they're full, they can't connect more miner
Try without the p=xx in your password, you will see they're open
If they're full, they can't connect more miner
Try without the p=xx in your password, you will see they're open
July 02, 2014, 07:01:28 PM
I have the same problem with connecting.
few rigs are in and others cant make it. Its like server is limited for connections or there is a limit of connections from one IP.
This is too much annoying now. And it is going for 2 days !
few rigs are in and others cant make it. Its like server is limited for connections or there is a limit of connections from one IP.
This is too much annoying now. And it is going for 2 days !
July 02, 2014, 03:12:40 PM
Has Nicehash recovered from that DDOS attack yesterday? I am still seeing all 3xxx and 4xxx ports as dead on all but three of my rigs. I cannot figure out why. Posted Config. This is my first post here so let me know if I have posted something incorrectly. Thanks.
Code:
{
"pools" : [
{
"name" : "NiceHash_Scrypt_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4333",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=4;d=1024;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "zuikkis",
"gpu-engine" : "1125",
"xintensity" : "4",
"gpu-memclock" : "1500",
"thread-concurrency" : "8192"
},
{
"name" : "NiceHash_Scrypt-N_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4335",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=7;d=512;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "11",
"algorithm" : "zuikkis",
"xintensity" : "4",
"gpu-engine" : "1100",
"gpu-memclock" : "1500",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"gpu-powertune" : "20",
"gpu-threads" : "1"
},
{
"name" : "NiceHash_X11_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=0.5;d=0.08;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "darkcoin-mod",
"gpu-engine" : "1130",
"gpu-memclock" : "1500",
"intensity" : "17"
},
{
"name" : "NiceHash_X13_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=0.6;d=0.08;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "marucoin-mod",
"gpu-engine" : "1100",
"intensity" : "18",
"gpu-memclock" : "1500"
},
{
"name" : "NiceHash_Keccak_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4338",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=0.004;d=0.08;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "maxcoin",
"gpu-engine" : "1080",
"gpu-memclock" : "750",
"intensity" : "9",
"gpu-threads" : "1",
"gpu-powertune" : "-20",
"thread-concurrency" : "8193"
},
{
"name" : "NiceHash_X15_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=0.6;d=0.08;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "bitblock",
"gpu-engine" : "1100",
"intensity" : "18",
"gpu-memclock" : "1500"
},
{
"name" : "NiceHash_Nist5_multi!",
"url" : "stratum+tcp://stratum.nicehash.com:4340",
"user" : "1NjD5adrBEqJkkHkzWwhPRsdRLBbpC43NZ",
"pass" : "p=0.6;d=0.08;f0=2.4;f2=1.2;f3=12;f4=9;f5=1400.0;f6=11.5;f7=84;c0=4;c2=4;c3=2;c4=2;c5=3.2;c6=2;c7=2",
"nfactor" : "10",
"algorithm" : "talkcoin-mod",
"gpu-engine" : "1100",
"intensity" : "18",
"gpu-memclock" : "1500"
},
{
"name" : "LTCrabbit",
"url" : "x11.ltcrabbit.com:3332",
"user" : "lmaonade80.B3",
"pass" : "x",
"algorithm" : "darkcoin-mod",
"nfactor" : "10",
"intensity" : "17",
"gpu-engine" : "1130",
"gpu-memclock" : "1500"
},
{
"name" : "SimpleDrk",
"url" : "stratum+tcp://stratum.simpledrk.com:3353",
"user" : "XweHU29qvYn5tv71hw6KvTCPeYvS1F9dBu.emily",
"pass" : "x",
"algorithm" : "darkcoin-mod",
"intensity" : "17",
"gpu-engine" : "1130",
"gpu-memclock" : "1500"
},
{
"name" : "SimpleVert",
"url" : "stratum+tcp://ca.simplevert.com:3344",
"user" : "VkSvsHB8A1TtD3QzgSV7rkDC5XiWt5BFdx.emily",
"pass" : "x",
"nfactor" : "11",
"algorithm" : "zuikkis",
"gpu-engine" : "1140",
"thread-concurrency" : "6208",
"intensity" : "18",
"gpu-memclock" : "1500",
"lookup-gap" : "2",
"shaders" : "1280",
"gpu-powertune" : "20",
"rawintensity" : "5120"
}
]
,
"worksize" : "256",
"no-extranonce" : true,
"lookup-gap" : "2",
"shaders" : "2048",
"gpu-threads" : "2",
"gpu-engine" : "1070",
"gpu-fan" : "0-100",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "10",
"gpu-dyninterval" : "7",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "7",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"no-client-reconnect" : true,
"failover-only" : true,
"failover-switch-delay" : "30",
"api-allow" : "W:127.0.0.1/24",
"api-listen" : true
}
July 02, 2014, 11:33:53 AM
7950´s example (web) dont work
Some conf working? (yes, i use sgminerv5)
Some conf working? (yes, i use sgminerv5)
July 02, 2014, 07:43:52 AM
Does the "f=X" working in the 2014-06-30 Version?
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6=3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
Did you do your cooking by the book?
You gotta do your cooking by the book.
Sorry dont know what you mean. This was fixed ;f6=3.5
July 02, 2014, 07:36:13 AM
Does the "f=X" working in the 2014-06-30 Version?
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6?3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6?3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
Did you do your cooking by the book?
You gotta do your cooking by the book.
July 02, 2014, 07:18:51 AM
Does the "f=X" working in the 2014-06-30 Version?
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6?3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
"pass" : "d=XXX;f0=0;f2=0;f3=4;f4=3;f5=0;f6?3.5;f7=12",
i just want to let the rig jump between X11/X13/X15/nist5
But its still jump to "Scrypt"
July 02, 2014, 06:36:10 AM
Anyone knows how to activate auto-fan in this build? https://mega.co.nz/#!7RsD0AIa!SPh8WT2D7TGrV441i8o1IFSz4sVku6KQ48MPr5B2R48
"auto-fan": true doesn't work. I put only auto-fan / only gpu-fan xx / both / none and miner either starts at almost max fan speed or stays at lowest possbile (1300 rpm).
"auto-fan": true doesn't work. I put only auto-fan / only gpu-fan xx / both / none and miner either starts at almost max fan speed or stays at lowest possbile (1300 rpm).
July 02, 2014, 02:26:41 AM
I have a slow miner (-/+ 2 MHs) on X11, jumps between 2 diff 0.001 and 0.100
get only few accepted hashes, can you re-adjust diff.
get only few accepted hashes, can you re-adjust diff.
July 01, 2014, 05:18:24 PM
Can someone point out a link to download compiled v5 miner?
https://www.nicehash.com/software/#sgminerAnd no f*n readme, how should i know what to do, am I Obi-wan-kenobi?
Is someone going to walk me through or else i will just keep asking.
for windows "gurus"
, i can share my own windows build with a sample config file that i did recently during my tests with 14.6 drivers on Windows 7 (see my previous posts)- built with M$ Visual Studio from the latest sgminer v5_0 branch (v5_0 and v5_0-x15 have been merged recently)
- sgminer configuration file included with x11/x13/x15 profiles for nicehash x11/x13/x15 multi-algo switching and wafflepool x11/x13 as a failback (intesity, tc, etc. set for R9-280x)
- kernel binaries for x11/x13/x15 algos included as well (bin files only for tahiti), generated on win7 rig with 14.6 drivers for miners running win7 with amd 13.12 driver
1.) download the package from here:
https://www.dropbox.com/s/a3zutvnjp89c322/sgminer.dwmnr.20140701.zip
2.) unpack it to Your "Desktop" folder
3.) edit the sgminer.conf file - only enter Your BTC address
4.) simply run runme.bat
Jump to: