Pages:
Author

Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 73. (Read 877846 times)

newbie
Activity: 21
Merit: 0
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 Smiley
full member
Activity: 169
Merit: 100

 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
sr. member
Activity: 406
Merit: 250

 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?
jr. member
Activity: 101
Merit: 1
Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? Smiley)

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
newbie
Activity: 21
Merit: 0
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.
sr. member
Activity: 434
Merit: 250
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?
legendary
Activity: 1510
Merit: 1003
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 ...
sr. member
Activity: 248
Merit: 250
Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? Smiley)

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 Smiley)) .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.
sr. member
Activity: 248
Merit: 250
Nowadays i focused in nvidia, is there any optimised quark,qubit kernel for 280x? Smiley)
legendary
Activity: 1400
Merit: 1050
Hi is there a way to turn off the queuing system so that sgminer solves a block before requesting a new one ? (without buffering)

sr. member
Activity: 539
Merit: 255
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?
sr. member
Activity: 411
Merit: 250
there is a kernel optimized for Blake 256. Thanks.
newbie
Activity: 35
Merit: 0
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.
sr. member
Activity: 539
Merit: 255
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.
hero member
Activity: 528
Merit: 500
What is with the quark mining so profitable all of sudden? Also anybody can share wolf0's program please Sad.

as far as I know Wolf0 has not released any bin's for Quark and has not released a miner
legendary
Activity: 1750
Merit: 1024
Why do you think only wolf can create optimized binaries?
I think kachur can create it as kminer for monero. Isn't it possible?

Just want to point out Kachur made a very competitive Cryptonote miner with Claymore. He eventually stopped updating it and got banned for some reason. There was also some schenanagins about duplicated shares for a bit too.
sr. member
Activity: 481
Merit: 250
What is with the quark mining so profitable all of sudden? Also anybody can share wolf0's program please Sad.
sr. member
Activity: 406
Merit: 250
I noticed in this thread some links to optimized miner by author of "kachur" CryptoNight miner. This kachur shit was a malware/scamware miner exploiting plain stupid duplicate share vulnerability in node-cryptonote-pool. You warned, stay away from all blobs by this "dev".

https://bitcointalksearch.org/topic/m.9262887


Do you also have a proof that this new miner submits duplicate shares?

of course it does, besides it switches off the rig power supply
to use preinstalled liquid antimatter source, no heat at all, just extreme radiation

Too much radiation is bad. But if it can use radiation to transmit coins, then energy is saved. Grin
sr. member
Activity: 434
Merit: 250
I noticed in this thread some links to optimized miner by author of "kachur" CryptoNight miner. This kachur shit was a malware/scamware miner exploiting plain stupid duplicate share vulnerability in node-cryptonote-pool. You warned, stay away from all blobs by this "dev".

https://bitcointalksearch.org/topic/m.9262887


Do you also have a proof that this new miner submits duplicate shares?
legendary
Activity: 1904
Merit: 1003
I noticed in this thread some links to optimized miner by author of "kachur" CryptoNight miner. This kachur shit was a malware/scamware miner exploiting plain stupid duplicate share vulnerability in node-cryptonote-pool. You warned, stay away from all blobs by this "dev".

https://bitcointalksearch.org/topic/m.9262887
Pages:
Jump to: