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

[damm315er]

So I don't know if anyone has run across this yet, but it's definitely an issue that I ran into.  I'm trying to mine with SGminer, doing 2 different algo's at once.

I downloaded the latest compiled version and tried with that as well just to be sure.

My rig currently has 4 GPU's, and I'm trying to split them to run on different algo's.

The setup I use, is batch to tell pool, solo, or whatever, and the .conf has all the details specific to each GPU.

This works just fine, as long as all 4 GPU's run the same thing.

The problem starts at this command:    "device": "2,3", as SGminer will not operate correctly using that.  It will do "device": "0,1", just fine, but the 2,3 it will not even operate correctly if it is the first instance of SGminer.

I've tried it on the wolf0 build, tried it on this build - sgminer-5.1-dev-2014-11-10-win32.zip, and tried it on this build (the latest available here  - https://www.nicehash.com/index.jsp?p=software#sgminer)- sgminer_v5.1_2015-03-09-win32.zip

This screencap is using this build - sgminer_v5.1_2015-03-09-win32.zip, and it is the only instance of SGminer running.  It shows GPU 0 & 1 acting exactly as they should be.



This is the same version, also the only instance of SGminer running, but it's attempting to run GPU's 2 & 3.  (note the GPU id's at the left of the screen, yet the temps are correct for the GPU's it's supposed to be running)



I even broke it down to single GPU's, and while GPU 0 shows correcly, nothing else does.  And while the others (Anything started without "device" : "0" do actually mine at a greatly reduced rate, trying to run more than one will eventually crash the drivers.

Also notice the 2nd one building a bin, they are using the same settings that were used in the 4 GPU configuration, just pared down, there's no need to create a bin..

That's definitely a bug.

[1714766754]

1714766754

[1714766754]

1714766754

[1714766754]

1714766754

[1714766754]

1714766754

[1714766754]

1714766754

[1714766754]

1714766754

[tarrier]

So I don't know if anyone has run across this yet, but it's definitely an issue that I ran into.  I'm trying to mine with SGminer, doing 2 different algo's at once.

I downloaded the latest compiled version and tried with that as well just to be sure.

My rig currently has 4 GPU's, and I'm trying to split them to run on different algo's.

The setup I use, is batch to tell pool, solo, or whatever, and the .conf has all the details specific to each GPU.

This works just fine, as long as all 4 GPU's run the same thing.

The problem starts at this command:    "device": "2,3", as SGminer will not operate correctly using that.  It will do "device": "0,1", just fine, but the 2,3 it will not even operate correctly if it is the first instance of SGminer.

I've tried it on the wolf0 build, tried it on this build - sgminer-5.1-dev-2014-11-10-win32.zip, and tried it on this build (the latest available here  - https://www.nicehash.com/index.jsp?p=software#sgminer)- sgminer_v5.1_2015-03-09-win32.zip

This screencap is using this build - sgminer_v5.1_2015-03-09-win32.zip, and it is the only instance of SGminer running.  It shows GPU 0 & 1 acting exactly as they should be.

https://i.imgur.com/jviEo6K.jpg

This is the same version, also the only instance of SGminer running, but it's attempting to run GPU's 2 & 3.  (note the GPU id's at the left of the screen, yet the temps are correct for the GPU's it's supposed to be running)

https://i.imgur.com/gZUoafH.jpg

I even broke it down to single GPU's, and while GPU 0 shows correcly, nothing else does.  And while the others (Anything started without "device" : "0" do actually mine at a greatly reduced rate, trying to run more than one will eventually crash the drivers.

Also notice the 2nd one building a bin, they are using the same settings that were used in the 4 GPU configuration, just pared down, there's no need to create a bin..

That's definitely a bug.

i had this issue too. "device" command can not work properly.

[gaalx]

there is a kernel optimized for Blake 256. Thanks.

[damm315er]

So I don't know if anyone has run across this yet, but it's definitely an issue that I ran into.  I'm trying to mine with SGminer, doing 2 different algo's at once.

I downloaded the latest compiled version and tried with that as well just to be sure.

My rig currently has 4 GPU's, and I'm trying to split them to run on different algo's.

The setup I use, is batch to tell pool, solo, or whatever, and the .conf has all the details specific to each GPU.

This works just fine, as long as all 4 GPU's run the same thing.

The problem starts at this command:    "device": "2,3", as SGminer will not operate correctly using that.  It will do "device": "0,1", just fine, but the 2,3 it will not even operate correctly if it is the first instance of SGminer.

I've tried it on the wolf0 build, tried it on this build - sgminer-5.1-dev-2014-11-10-win32.zip, and tried it on this build (the latest available here  - https://www.nicehash.com/index.jsp?p=software#sgminer)- sgminer_v5.1_2015-03-09-win32.zip

This screencap is using this build - sgminer_v5.1_2015-03-09-win32.zip, and it is the only instance of SGminer running.  It shows GPU 0 & 1 acting exactly as they should be.



This is the same version, also the only instance of SGminer running, but it's attempting to run GPU's 2 & 3.  (note the GPU id's at the left of the screen, yet the temps are correct for the GPU's it's supposed to be running)



I even broke it down to single GPU's, and while GPU 0 shows correcly, nothing else does.  And while the others (Anything started without "device" : "0" do actually mine at a greatly reduced rate, trying to run more than one will eventually crash the drivers.

Also notice the 2nd one building a bin, they are using the same settings that were used in the 4 GPU configuration, just pared down, there's no need to create a bin..

That's definitely a bug.

Old news, I kept asking for it to be fixed, but no luck.

Is that only on this branch, or all branches?

[djm34]

Hi is there a way to turn off the queuing system so that sgminer solves a block before requesting a new one ? (without buffering)

[fenomenhaa]

Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? )

[fenomenhaa]

Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? )

Is there? Yes; dunno how profitable it is.

EDIT: Pulled my record for Quark: https://ottrbutt.com/miner/quarkwolf-04202015.png (NSFW)

@wolf0
İt depends on kernels efficiency )) .Ahh i see, so if you can share the power consumption ,we can be sure about profability,And i think that there is still too much potansial.İf it's sor sale send me pm about price.

[rednoW]

Is there? Yes; dunno how profitable it is.

EDIT: Pulled my record for Quark: https://ottrbutt.com/miner/quarkwolf-04202015.png (NSFW)

Users report more then 16mhs on 290x with alt free but non-public miner ...

[Oscilson]

Is there? Yes; dunno how profitable it is.

EDIT: Pulled my record for Quark: https://ottrbutt.com/miner/quarkwolf-04202015.png (NSFW)

Users report more then 16mhs on 290x with alt free but non-public miner ...

What is the non-public miner?

[scaggy]

Is there? Yes; dunno how profitable it is.

EDIT: Pulled my record for Quark: https://ottrbutt.com/miner/quarkwolf-04202015.png (NSFW)

Users report more then 16mhs on 290x with alt free but non-public miner ...

I know, mine's not polished yet - it was hacked together in an afternoon.

When its polished you gonna sell it here? same as fenomenhaa said i am also interested to pay for it pm me also what its gonna cost.

[xelbyb]

Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? )

Is there? Yes; dunno how profitable it is.

EDIT: Pulled my record for Quark: https://ottrbutt.com/miner/quarkwolf-04202015.png (NSFW)

GPU0 7950  Asus        1050/950  Hunix
GPU1 7950  Gigabyte  1050/950  Elpida

[BitmoreCoin]

 What's their speed?

Odd that less than a week after someone gets my version, this happens...

280x
qubit - 12.5 Mh / S
Quark - 12.3 Mh / S

Doesn't work with standard sgminer however

What is the core/memory frequency?

[jch9678]

 What's their speed?

Odd that less than a week after someone gets my version, this happens...

280x
qubit - 12.5 Mh / S
Quark - 12.3 Mh / S

Doesn't work with standard sgminer however

What is the core/memory frequency?

1100/1500

[scaggy]

Over 17.60MH/s on 290X @ 1100/1500. I haven't finished fixing it up the rest of the chips yet; I just made some mods to the host code and OpenCL so I could raise the intensity - now less resources are wasted, so I can up it and actually gain hashrate.

Here (NSFW): https://ottrbutt.com/miner/quarkwolf-05122015.png

Back to the other miner dev.

damm thats some nice hashrate allready

[sp_]

You are getting closer to my gtx 980 OC numbers using the latest ccminer(sp-mod). Good job.

[sp_]

Haven't tested in a while but I think it is around 20MHASH on max stable clock.

[BitmoreCoin]

You are getting closer to my gtx 980 OC numbers using the latest ccminer(sp-mod). Good job.

My 290X is doing 18.33MH/s right now, did a little more tuning. What's your number on the 980?

What is the estimated power consumption?, GTX980 can do 20MH/s at 180W.

A GTX 980OC pulls around 180W for quark and does 20MHASH.
A 7 card rig does 140MHASH and use 1350W. (The payout per day is the same as a 409MHASH ASIC scrypt miner)
A 7card 750TI rig does 45,5MHASH an use 430W. (The payout per day is the same as a 143MHASH ASIC scrypt miner)

[BitmoreCoin]

You are getting closer to my gtx 980 OC numbers using the latest ccminer(sp-mod). Good job.

My 290X is doing 18.33MH/s right now, did a little more tuning. What's your number on the 980?

What is the estimated power consumption?, GTX980 can do 20MH/s at 180W.

A GTX 980OC pulls around 180W for quark and does 20MHASH.
A 7 card rig does 140MHASH and use 1350W. (The payout per day is the same as a 409MHASH ASIC scrypt miner)
A 7card 750TI rig does 45,5MHASH an use 430W. (The payout per day is the same as a 143MHASH ASIC scrypt miner)

I don't have a meter since I melted my last one. Happened to me twice now; I need another.

If yours can do 18MH around 180W, then you save the life of many AMD cards.

[iju76]

Quark - 280X is doing 15.33MH/s

[hk47]

Quark - 280X is doing 15.33MH/s

Which version of the driver? What a miner? Operating frequencies of video card? Your message here is not very informative ..