[ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner

[KiloWatts]

Grumble...  well, I just got this when it switched to Scrypt:

Code:

[02:34:21] Accepted 01d0895f Diff 141/64 GPU 1 at NiceHash_Scrypt-N 
[02:34:21] Stratum connection to NiceHash_Scrypt-N interrupted
[02:34:31] Waiting for work to be available from pools.
[02:34:34] NiceHash_Scrypt-N not responding!
[02:34:34] Switching to NiceHash_Scrypt
[02:34:34] NiceHash_Scrypt difficulty changed to 256
[02:34:41] Work available from pools, resuming.
[02:34:41] Building binary zuikkisHawaiigw256l4lg2tc32765nf10.bin
[02:34:57] Initialising kernel zuikkis.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[02:34:57] Initialising kernel zuikkis.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[02:34:57] Error -4: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[02:34:57] Error -4: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[02:34:57] GPU 0 failure, disabling!
[02:34:57] GPU 1 failure, disabling!
[02:35:37] Shutdown signal received.

Turned both GPUs off immediately.  I agree, I think a 60-second buffer would be a good idea.

[1715636614]

1715636614

[1715636614]

1715636614

[1715636614]

1715636614

[DarkAGeS]

Again ... about 6 Hours ago. N-Scrypt running well the last 15 Hours, then in the Night it switched to X13 and again back to N-Scrypt. 5 of my GPUs go off and 1 got the turn and was running well in the right speed

Any solution for this? Missing 6 Hours every Day hurts.

I use sgminer-5.0-pre-release-2014-06-11
That looks like my situation, but my 270x not stoped but started mine with very slow speed (20k instead of 230k). In the same time other rig with 280x switched without problems.
Distinctions in configs are:
270x config:

Code:

"pool-gpu-threads" : "2",
"pool-rawintensity": "5120",
"pool-thread-concurrency" : "6336"

280x config just define:

Code:

"pool-intensity" : "13"

this options defined in general part of 280x config (not pool part):

Code:

"gpu-threads" : "2",
"thread-concurrency" : "8192",

I think there is a problem with pool-gpu-threads and pool-thread-concurrency options - they dont work right according to my observations. On windows miner just crash if I even define same pool-gpu-threads for all pools. On linux (bamt) it works but with bugs

[Adz]

Again ... about 6 Hours ago. N-Scrypt running well the last 15 Hours, then in the Night it switched to X13 and again back to N-Scrypt. 5 of my GPUs go off and 1 got the turn and was running well in the right speed

Any solution for this? Missing 6 Hours every Day hurts.

I use sgminer-5.0-pre-release-2014-06-11
That looks like my situation, but my 270x not stoped but started mine with very slow speed (20k instead of 230k). In the same time other rig with 280x switched without problems.
Distinctions in configs are:
270x config:

Code:

"pool-gpu-threads" : "2",
"pool-rawintensity": "5120",
"pool-thread-concurrency" : "6336"

280x config just define:

Code:

"pool-intensity" : "13"

this options defined in general part of 280x config (not pool part):

Code:

"gpu-threads" : "2",
"thread-concurrency" : "8192",

I think there is a problem with pool-gpu-threads and pool-thread-concurrency options - they dont work right according to my observations. On windows miner just crash if I even define same pool-gpu-threads for all pools. On linux (bamt) it works but with bugs

I had the same problem with 2x of my rigs dropping out when autoswitching,. On one of the rigs the GPU reported dead and the other rig wasn't hashing. Only thing is I don't have either pool-gpu-threads or pool-thread-concurrency in my pool section.
I have since changed the "failover-switch-delay"  from 30 to 60 to see if that makes a difference during the autoswitch

[guzzzi]

Again ... about 6 Hours ago. N-Scrypt running well the last 15 Hours, then in the Night it switched to X13 and again back to N-Scrypt. 5 of my GPUs go off and 1 got the turn and was running well in the right speed

Any solution for this? Missing 6 Hours every Day hurts.

I use sgminer-5.0-pre-release-2014-06-11
That looks like my situation, but my 270x not stoped but started mine with very slow speed (20k instead of 230k). In the same time other rig with 280x switched without problems.
Distinctions in configs are:
270x config:

Code:

"pool-gpu-threads" : "2",
"pool-rawintensity": "5120",
"pool-thread-concurrency" : "6336"

280x config just define:

Code:

"pool-intensity" : "13"

this options defined in general part of 280x config (not pool part):

Code:

"gpu-threads" : "2",
"thread-concurrency" : "8192",

I think there is a problem with pool-gpu-threads and pool-thread-concurrency options - they dont work right according to my observations. On windows miner just crash if I even define same pool-gpu-threads for all pools. On linux (bamt) it works but with bugs

I had the same problem with 2x of my rigs dropping out when autoswitching,. On one of the rigs the GPU reported dead and the other rig wasn't hashing. Only thing is I don't have either pool-gpu-threads or pool-thread-concurrency in my pool section.
I have since changed the "failover-switch-delay"  from 30 to 60 to see if that makes a difference during the autoswitch

i tryed the "failover-switch-delay" with the same result. As soon he switch to nscrypt all my gpus go off. terrible so many times today. think i will go back to mine one algo till this is fixed or solution is ready. cant babysit all the day.

[CounterStrike]

Is this miner as stable as the other miner for r9 280x and r9 290?

[mannyg]

Is this miner as stable as the other miner for r9 280x and r9 290?

Stable for both my 280x and 290's, but the switching kills my 290s,.. not my 280x's.  I have my 290's mining with auto-switching disabled and switching to the profitable algo when ever i get around to seeing it change

[DiCE1904]

Has anyone got this working with PiMP? If so howd you do it please

[KiloWatts]

Again ... about 6 Hours ago. N-Scrypt running well the last 15 Hours, then in the Night it switched to X13 and again back to N-Scrypt. 5 of my GPUs go off and 1 got the turn and was running well in the right speed

Any solution for this? Missing 6 Hours every Day hurts.

I use sgminer-5.0-pre-release-2014-06-11
That looks like my situation, but my 270x not stoped but started mine with very slow speed (20k instead of 230k). In the same time other rig with 280x switched without problems.
Distinctions in configs are:
270x config:

Code:

"pool-gpu-threads" : "2",
"pool-rawintensity": "5120",
"pool-thread-concurrency" : "6336"

280x config just define:

Code:

"pool-intensity" : "13"

this options defined in general part of 280x config (not pool part):

Code:

"gpu-threads" : "2",
"thread-concurrency" : "8192",

I think there is a problem with pool-gpu-threads and pool-thread-concurrency options - they dont work right according to my observations. On windows miner just crash if I even define same pool-gpu-threads for all pools. On linux (bamt) it works but with bugs

I had the same problem with 2x of my rigs dropping out when autoswitching,. On one of the rigs the GPU reported dead and the other rig wasn't hashing. Only thing is I don't have either pool-gpu-threads or pool-thread-concurrency in my pool section.
I have since changed the "failover-switch-delay"  from 30 to 60 to see if that makes a difference during the autoswitch

i tryed the "failover-switch-delay" with the same result. As soon he switch to nscrypt all my gpus go off. terrible so many times today. think i will go back to mine one algo till this is fixed or solution is ready. cant babysit all the day.

Failover-switch-delay doesn't appear to do anything here.  (there is no delay)

[mannyg]

Scratch that, just switched from scrypt-n to scrypt and my 280x rig took a dive.   

[KiloWatts]

Yep, it's undoubtedly broke.  I'm going to stick to 1 algorithm since it seems Scrypt and N-Scrypt are neck-to-neck right now.

[platinum4]

Scratch that, just switched from scrypt-n to scrypt and my 280x rig took a dive.   

Should be safe to say this miner can't effectively handle scrypt.  And that's ok!

[KiloWatts]

I'm starting to wonder about what determines whether or not an algo is more profitable.  Nicehash says 'volume' has to be big enough to warrant a switch, yet I'm looking at Scrypt-N, and it's going for twice as much as Scrypt very clearly.  Would it be better to switch to Scrypt with a higher volume, or remain on N-Scrypt and wait for slower sales at higher prices?

Edit:  Nevermind, I see.

[platinum4]

I'm starting to wonder about what determines whether or not an algo is more profitable.  Nicehash says 'volume' has to be big enough to warrant a switch, yet I'm looking at Scrypt-N, and it's going for twice as much as Scrypt very clearly.  Would it be better to switch to Scrypt with a higher volume, or remain on N-Scrypt and wait for slower sales at higher prices?

Edit:  Nevermind, I see.

I'd be interested to see how they account for difference in power usage as well.

[Adz]

Yep, it's undoubtedly broke.  I'm going to stick to 1 algorithm since it seems Scrypt and N-Scrypt are neck-to-neck right now.

Yup i'm with you. Ill go back to standard mining until NiceHash Guys start posting what they are doing to address these issues

[rudarSRB]

Still no fix for CGWatcher?

[katak]

When you see cuda miner... don't we have to sell our AMD boards if miner doesn't improve significantly ? :p

[oktay50000]

Still no fix for CGWatcher?

+1000 on that

[cgladue]

Still no fix for CGWatcher?

+1000 on that

im using CGWatcher perfectly fine, i did have a problem when i wasnt using the "Arguments" textbox, so i had to fill that in as well and now its 100% running fine ...


Under Settings Tab, this is what i have configured ...

Miner:   C:\Coin mining\sgminer-win32\sgminer.exe

Config File:    C:\Coin mining\sgminer-win32\scrypt.conf

Arguments:     "--config=C:\Coin mining\sgminer-win32\scrypt.conf" 2>log.txt

[cgladue]

To the dev: what is being done to fix the crashing/hanging of the computer when switching from X11/x13 back to scrypt-n ?

this is a huge issue

[platinum4]

To the dev: what is being done to fix the crashing/hanging of the computer when switching from X11/x13 back to scrypt-n ?

this is a huge issue

Pretty much just don't use it for that, right now.  If you are living in an area where you can mine scrypt-n without it being unbearably hot, then I would just do so for a few hours a day with another mining program right now, since it's been the dominant profitable algorithm on nicehash now for 3 days straight.  You're not missing anything with these shitty rental rates and profitability right now amongst x11/x13.