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

[badman74]

I would like to ask you if you have correct string in password?

"d=.01;f0=1;f2=.5;f3=9.5;f4=6.8;f5=750"

I think that you've mixed relative values with absolute
I don't know if I understand it correctly with this string you try to say to NiceHash server that you mining rig speed is: SCRYPT = 1 Mhs, ScryptN = 0.5 Mhs, X11 = 9.5Mhs, X13 = 6.8 Mhs and Keccak = 750 Mhs

well i suppose keccack probably should only be 700 but it would be 750 if the fan wasnt dieing on one of my cards

[platinum4]

Latest commit should take care of fan speed issues for you guys on auto-fan.

ok here is the windows build
https://mega.co.nz/#!jMBTURqL!7K1kotxbf3EiA5G61eBC0Y57c8fuyMxpph2LxYh4j0o

Bad ass, I'll try this out in a few hours after work.

EDIT:  Fan speed initialization fixed, profiles load correctly for fan speeds, even without default-profile not specified it doesn't spit out ckolivas, and it doesn't quit in 60 seconds from start.  Remains to be seen how it handles extended uptimes, and daily algo-flips.

Very fucking impressed right now with the all-hands-on-deck effort to get this Windows port up and as functional as the Linux builds.

Seems to be a winner so far.  For added fun, add "incognito" : true and try and guess what the fuck you're hashing and where!

kenshirothefist, I'd say this is a wrappable build to throw up as a pre-release for your https://www.nicehash.com/software/#sgminer

[B.T.Coin]

Latest commit should take care of fan speed issues for you guys on auto-fan.

ok here is the windows build
https://mega.co.nz/#!jMBTURqL!7K1kotxbf3EiA5G61eBC0Y57c8fuyMxpph2LxYh4j0o

This build looks pretty solid, good job.
The only problem I'm having is that I can not set the GPU engine clock on my Sapphire Dual-X cards when using Catalyst 14.6
With the Vapor-X cards it works fine.
It's probably an issue with the new beta drivers but just wanted to mention it in case it's something in SGminer.

EDIT: Just tested with afterburner and that can change the clocks on the Dual-X cards under 14.6 so maybe not a driver issue ?

[mannyg]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

[Slix]

Latest commit should take care of fan speed issues for you guys on auto-fan.

ok here is the windows build
https://mega.co.nz/#!jMBTURqL!7K1kotxbf3EiA5G61eBC0Y57c8fuyMxpph2LxYh4j0o

This build looks pretty solid, good job.
The only problem I'm having is that I can not set the GPU engine clock on my Sapphire Dual-X cards when using Catalyst 14.6
With the Vapor-X cards it works fine.
It's probably an issue with the new beta drivers but just wanted to mention it in case it's something in SGminer.

EDIT: Just tested with afterburner and that can change the clocks on the Dual-X cards under 14.6 so maybe not a driver issue ?

I've heard a few people mention something like that but it seems random or based on card models. It's not something that I've experienced myself with my Dual-X's. Try reverting back to 14.4 or 13.12 drivers.

Then, copy the following files from the 14.6 beta drivers into your sgminer folder: amd_opencl32.dll, amd_opencl64.dll, amdocl.dll and amdocl64.dll. You will be able to get 14.6beta speeds without actually installing the drivers and messing your system up.

[Slix]

Just a heads up, I fixed another thing last night involving nfactor. Sometimes the nfactor setting is read by the parser before algorithm, which would cause nfactor to revert to 10 (aka regular scrypt). If you experience any problems with nscrypt, try the latest commit.

[B.T.Coin]

Latest commit should take care of fan speed issues for you guys on auto-fan.

ok here is the windows build
https://mega.co.nz/#!jMBTURqL!7K1kotxbf3EiA5G61eBC0Y57c8fuyMxpph2LxYh4j0o

This build looks pretty solid, good job.
The only problem I'm having is that I can not set the GPU engine clock on my Sapphire Dual-X cards when using Catalyst 14.6
With the Vapor-X cards it works fine.
It's probably an issue with the new beta drivers but just wanted to mention it in case it's something in SGminer.

EDIT: Just tested with afterburner and that can change the clocks on the Dual-X cards under 14.6 so maybe not a driver issue ?

I've heard a few people mention something like that but it seems random or based on card models. It's not something that I've experienced myself with my Dual-X's. Try reverting back to 14.4 or 13.12 drivers.

Then, copy the following files from the 14.6 beta drivers into your sgminer folder: amd_opencl32.dll, amd_opencl64.dll, amdocl.dll and amdocl64.dll. You will be able to get 14.6beta speeds without actually installing the drivers and messing your system up.

I did some more testing and found that I can change the clocks with 14.6 but I just can not change them below the stock clock speed.
Since I undervolted my cards, they were running just below stock clocks.

Thanks for the tip on copying the opencl files, this worked pefectly and I can change the clocks below stock again now I use 13.12

[amacar]

Thank you for your work nicehash team 

[platinum4]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

I get SICK -> DEAD on x13 usually after having done x11 for an extended time, then flipping.   It doesn't require a hard boot, just a restart of the mining instance.

[mannyg]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

I get SICK -> DEAD on x13 usually after having done x11 for an extended time, then flipping.   It doesn't require a hard boot, just a restart of the mining instance.

Flipping from X13 to X11 just made one GPU go SICK -> DEAD , and if i restart only the mining instance, the hashrate does not build up to its normal speed, it only goes to about 50-60% speed.  I have to reboot the OS and restart mining for it to work at full speed.   Sometimes just mining X11 does this too without any switching.

[morfey911]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

I get SICK -> DEAD on x13 usually after having done x11 for an extended time, then flipping.   It doesn't require a hard boot, just a restart of the mining instance.

Flipping from X13 to X11 just made one GPU go SICK -> DEAD , and if i restart only the mining instance, the hashrate does not build up to its normal speed, it only goes to about 50-60% speed.  I have to reboot the OS and restart mining for it to work at full speed.   Sometimes just mining X11 does this too without any switching.

Try lower xi, i had the same with my 290x, but after i reduced xi from 144 to 32 (hashrate not hurt) - i have not seen any SEEK or DEAD.
sry for my bad english.

[platinum4]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

I get SICK -> DEAD on x13 usually after having done x11 for an extended time, then flipping.   It doesn't require a hard boot, just a restart of the mining instance.

Flipping from X13 to X11 just made one GPU go SICK -> DEAD , and if i restart only the mining instance, the hashrate does not build up to its normal speed, it only goes to about 50-60% speed.  I have to reboot the OS and restart mining for it to work at full speed.   Sometimes just mining X11 does this too without any switching.

Try lower xi, i had the same with my 290x, but after i reduced xi from 144 to 32 (hashrate not hurt) - i have not seen any SEEK or DEAD.
sry for my bad english.

xI: 32 is WAY below I:19 how do you have good hashrates with that?

[morfey911]

I've mined Scrypt, Scrypt-N, and X13 for extended periods of time without errors. (2days or more)... so far the only algorithm that has given me SICK > DEAD cards is X11.  Keccak im not even sure if I have configured right, i get a pretty good hash rate but an unusually high amount of rejects.

I get SICK -> DEAD on x13 usually after having done x11 for an extended time, then flipping.   It doesn't require a hard boot, just a restart of the mining instance.

Flipping from X13 to X11 just made one GPU go SICK -> DEAD , and if i restart only the mining instance, the hashrate does not build up to its normal speed, it only goes to about 50-60% speed.  I have to reboot the OS and restart mining for it to work at full speed.   Sometimes just mining X11 does this too without any switching.

Try lower xi, i had the same with my 290x, but after i reduced xi from 144 to 32 (hashrate not hurt) - i have not seen any SEEK or DEAD.
sry for my bad english.

xI: 32 is WAY below I:19 how do you have good hashrates with that?

i dont know, but after i found that, i changed xi on my other rigs and this works perfect. Look at screenshot below:
http://cdn.joxi.ru/uploads/prod/2014/06/25/f59/3f5/cb2999442afe029945797c02a0e3ceb00be59ede.jpg
GPU 0,1,2 - R9 290x at 1040 gpu mhz
GPU 3 - r9 290 at 950 gpu mhz

[coda]

ok this miner goes 30% faster ... well done guys !!  
but it also draws 30% more watts @ the wall   (and the cards are hotter also)

[platinum4]

Try lower xi, i had the same with my 290x, but after i reduced xi from 144 to 32 (hashrate not hurt) - i have not seen any SEEK or DEAD.
sry for my bad english.

xI: 32 is WAY below I:19 how do you have good hashrates with that?
[/quote]

i dont know, but after i found that, i changed xi on my other rigs and this works perfect. Look at screenshot below:

GPU 0,1,2 - R9 290x at 1040 gpu mhz
GPU 3 - r9 290 at 950 gpu mhz
[/quote]

I just tried this and it hard crashed my rig after 2 minutes 20 seconds.  I'll pass for now.  xI: of 320 works a bit better for tweaking.  Do you have shaders : 2816 specified?

[kenshirothefist]

We have published new sgminer_v5 binaries (linux, windows), build today (60 sec quit fix, high speed fan fix, etc.): https://www.nicehash.com/software/#sgminer

[morfey911]

ok this miner goes 30% faster ... but it also draws 30% more watts @ the wall  

Yeah, a little more and x11/x13 will draw like script.

[morfey911]

Try lower xi, i had the same with my 290x, but after i reduced xi from 144 to 32 (hashrate not hurt) - i have not seen any SEEK or DEAD.
sry for my bad english.

xI: 32 is WAY below I:19 how do you have good hashrates with that?

i dont know, but after i found that, i changed xi on my other rigs and this works perfect. Look at screenshot below:
http://cdn.joxi.ru/uploads/prod/2014/06/25/f59/3f5/cb2999442afe029945797c02a0e3ceb00be59ede.jpg
GPU 0,1,2 - R9 290x at 1040 gpu mhz
GPU 3 - r9 290 at 950 gpu mhz
[/quote]

I just tried this and it hard crashed my rig after 2 minutes 20 seconds.  I'll pass for now.  xI: of 320 works a bit better for tweaking.  Do you have shaders : 2816 specified?
[/quote]

screenshot from my other rig.
3 x 290 reference at 1010mhz.
http://cdn.joxi.ru/uploads/prod/2014/06/25/925/431/5bfffa37c4373505a7f8ec80f9a441cca4432cdc.jpg

config:

Code:

{
"pools" : [
        {
                "name" : "NiceHash_X11",
                "url" : "stratum+tcp://stratum.nicehash.com:4336",
                "user" : "",
                "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0",
                "pool-algorithm" : "darkcoin-mod",
                "pool-nfactor" : "10",
                "pool-gpu-engine" : "1010",
                "pool-gpu-memclock" : "1500",
		"pool-xintensity" : "32"
        },
        {
                "name" : "NiceHash_X13",
                "url" : "stratum+tcp://stratum.nicehash.com:4337",
                "user" : "",
                "pass" : "f0=0;f2=0;f3=4;f4=3;f5=0",
                "pool-algorithm" : "marucoin-mod",
                "pool-nfactor" : "10",
                "pool-gpu-engine" : "1010",
		"pool-xintensity" : "144"
        },
        {
                "name" : "Trademybit_X11",
                "url" : "stratum+tcp://am01.eu.trademybit.com:4440",
                "user" : "",
                "pass" : "",
                "pool-algorithm" : "darkcoin-mod",
                "pool-nfactor" : "10",
                "pool-gpu-engine" : "1010",
                "pool-gpu-memclock" : "1500",
		"pool-xintensity" : "32"
        },
        {
                "name" : "Trademybit_X13",
                "url" : "stratum+tcp://am01.eu.trademybit.com:5550",
                "user" : "",
                "pass" : "",
                "pool-algorithm" : "marucoin-mod",
                "pool-nfactor" : "10",
                "pool-gpu-engine" : "1010",
		"pool-xintensity" : "144"
        }
],
"hamsi-expand-big" : "7",
"gpu-threads" : "2",
"worksize" : "256",
"vectors" : "1",
"lookup-gap" : "2",
"gpu-fan" : "50-100",
"gpu-powertune" : "20",
"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "80",
"auto-fan" : true,
"auto-gpu" : true,
"log" : "1",
"failover-only" : true,
"failover-switch-delay" : "30",
"no-pool-disable" : true,
"scrypt" : true,
"queue" : "0",
"scan-time" : "10",
"expiry" : "28",
"api-listen" : true,
"api-port" : "4028"
}

[platinum4]

No "shaders" specified; interesting.  I'll check this out.

EDIT:  Also, it should be explained right here that you aren't using the newest "form" of config files, with profiles and pools.  Shouldn't matter though.

xI:320 just blew my card into SICK in about 15 minutes.

[bullus]

No "shaders" specified; interesting.  I'll check this out.

EDIT:  Also, it should be explained right here that you aren't using the newest "form" of config files, with profiles and pools.  Shouldn't matter though.

xI:320 just blew my card into SICK in about 15 minutes.

maybe u should try hamsi expand big 7, like his config.