280x hynix got 6.4-6.6mhs 14.xx drivers, clocks 1100 mem 1500
sgminer.exe -k darkcoin-mod --xintensity 128 --worksize 64 -g 4 --lookup-gap 2
Topic: X11 X13 X15 with 50% more hashrate 7Mh/s on 280x or 10 Mh/s on 290x - page 5. (Read 54262 times)
December 12, 2014, 05:18:45 PM
December 02, 2014, 04:49:57 AM
I am inserting the kernels in sgminer 5.0 (in the kernels folder) and I am also copying bin files in the main sgminer folder.
Then i run -k darkcoin-mod, no change in hash rate . What am I doing wrong?
@ wolf0 , dont say that i did not predict the leak.
If you make a kernel/miner with good hashrate and a reasonable donate option I will use yours.
Hope that others think the same as i do.
Then i run -k darkcoin-mod, no change in hash rate . What am I doing wrong?
@ wolf0 , dont say that i did not predict the leak.
If you make a kernel/miner with good hashrate and a reasonable donate option I will use yours.
Hope that others think the same as i do.
Use worksize 64, generate bins by yourself, then replace those bins with mine, using the same name as the ones you generated.
Yup and imagine that, a highly desirable product has now been leaked and is pretty much worthless to the author. Too bad you didn't release it with a modest dev fee attached. Instead people got pissed off you were trying to sell it for so much that they don't even consider it a option and there are people trying to resell it themselves for less or outright leaked it. But don't worry, I'm sure no one would've used your custom miner. -_-
Donations ARE NOT required. They are given of their free will. What you're talking about is a fee and someone not paying a fee. Don't confuse the two. Donations are not the same as a fee. You are happy if you get donations, if any. Fees are required to purchase a product.
Don't go on bitching about something like this when you could put a dev fee in. It's your own fault if you feel you deserve money for work for 'donating' it. NO ONE HAS TO DONATE. Donation expectations should be set at 0.
The problem may-be is that you forgot to donate for sgminer while you should have. Same applies to standard sgminer, someone wrap up the code
expecting from users they will donate... he was wrong, some moron thought they didn't have to make donations
expecting from users they will donate... he was wrong, some moron thought they didn't have to make donations
Donations ARE NOT required. They are given of their free will. What you're talking about is a fee and someone not paying a fee. Don't confuse the two. Donations are not the same as a fee. You are happy if you get donations, if any. Fees are required to purchase a product.
Don't go on bitching about something like this when you could put a dev fee in. It's your own fault if you feel you deserve money for work for 'donating' it. NO ONE HAS TO DONATE. Donation expectations should be set at 0.
Actually, it was my main source of income, and releasing it with a fee would have caused the same thing - someone taking it apart and ripping out the code. Dude, you don't even look at history before spouting your bullshit. Go look into the history of darkcoin-mod, and what this "community" will do to avoid paying even a 2% fee on a 50% increase.
EDIT: Oh, and by the way, you're correct that donations aren't required. But don't you dare bitch when people only sell to large farmers when you never donated a cent.
December 12, 2014, 06:25:44 AM
If you're going to use my shit, you may as well get it from me, not that bottom feeder. These are faster by a bit; I'll release Pitcairn in a little while to prove I'm the actual author, since Eliovp didn't have a bin for Pitcairn, nor up-to-date source to generate one.
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
https://ottrbutt.com/miner/wolf-x11Hawaiigw64l8ku0.bin
Same deal, use SGMiner 5 to generate a bin using worksize 64, then copy this bin over it with the same name.
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
https://ottrbutt.com/miner/wolf-x11Hawaiigw64l8ku0.bin
Same deal, use SGMiner 5 to generate a bin using worksize 64, then copy this bin over it with the same name.
I tried those briefly and I find them to be about 5% slower than lovestoshare's shit on Tahiti. What other params are you using besides xI=64 TC=8192, g=2?
Use xI 128 on Tahiti.
Edit: Hm strange it was related to the pool not to my settings or anything else. As long as this specific pool detects change of difficulty it throws HW errors on my side. On other pools it's working fine.
December 10, 2014, 09:25:01 PM
Nice work Wolf0!
How much u should get with 280x at 1100/1500 ?
Currently ~6.4MH/s.
How much u should get with 280x at 1100/1500 ?
Currently ~6.4MH/s.
December 07, 2014, 10:23:17 PM
If you're going to use my shit, you may as well get it from me, not that bottom feeder. These are faster by a bit; I'll release Pitcairn in a little while to prove I'm the actual author, since Eliovp didn't have a bin for Pitcairn, nor up-to-date source to generate one.
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
https://ottrbutt.com/miner/wolf-x11Hawaiigw64l8ku0.bin
Same deal, use SGMiner 5 to generate a bin using worksize 64, then copy this bin over it with the same name.
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
https://ottrbutt.com/miner/wolf-x11Hawaiigw64l8ku0.bin
Same deal, use SGMiner 5 to generate a bin using worksize 64, then copy this bin over it with the same name.
I tried those briefly and I find them to be about 5% slower than lovestoshare's shit on Tahiti. What other params are you using besides xI=64 TC=8192, g=2?
December 02, 2014, 12:43:41 AM
Аt least put Pitcairng and so the set will be full 
.
. The bastard who leaked it didn't have Pitcairn.
December 07, 2014, 10:21:01 PM
Nice.
R9 280x(tahiti): 6.450MHASH at standard clocks. with 4 threads
9970(tahiti): 5,9MHASH at standard clocks. with 4 threads
6990(Caymang): 4,1MHASH at standard clocks. with 2 threads
With 8 threads the rig is crashing.
Donation is comming tomorrow.
R9 280x(tahiti): 6.450MHASH at standard clocks. with 4 threads
9970(tahiti): 5,9MHASH at standard clocks. with 4 threads
6990(Caymang): 4,1MHASH at standard clocks. with 2 threads
With 8 threads the rig is crashing.
Donation is comming tomorrow.
is that 4.1 for both cayman cores or is it per core? I suspect it is the former.
Why 4 threads? I experimented with 4 threads and did not see any difference.
December 01, 2014, 10:59:38 PM
Oh yeah, this is my work. But now I also know who the source is.
They don't have it all, though - some old CL, but up to date bins for Tahiti and Hawaii on x11 - old bins for x15.
My current x13 should be safe: https://ottrbutt.com/miner/x13localrigwolf-12012014.png
Also just confirmed bins for x15 are old, so it's safe: https://ottrbutt.com/miner/x15localrigwolf-12012014.png
If you want to donate to the real author, here: 1Jp2R7dF9gYr872FkXiap2MaYaHNEfwWhZ
They don't have it all, though - some old CL, but up to date bins for Tahiti and Hawaii on x11 - old bins for x15.
My current x13 should be safe: https://ottrbutt.com/miner/x13localrigwolf-12012014.png
Also just confirmed bins for x15 are old, so it's safe: https://ottrbutt.com/miner/x15localrigwolf-12012014.png
If you want to donate to the real author, here: 1Jp2R7dF9gYr872FkXiap2MaYaHNEfwWhZ
December 07, 2014, 02:15:53 PM
@wolf Yep, when I created new bin file, I put "worksize" : "64", then I replace old bin file with your bin file, and keep worksize 64. I tried this on second rig and doesnt work too. Do I maybe need to change kernel folder or something? This is frustrating 
Do you happen to have blake compact or luffa parallel in your configs? Correct me if I'm wrong but I think you need to take those out as the Wolf0's bins don't have those activated, at least for x11. I'm not sure if that would prevent you from mining though, just a thought.
December 01, 2014, 08:40:38 PM
There's no way to tell 100% from the bin files, but you couldn't have known mine were far smaller than the shit code unless you had one - it's a little old, but your hashrates are also correct. Someone has stolen from me.
Well seems this has been in the wild for a while. File modification date is Nov 18th. Anyway you're also invited for a lunch. We can discuss X11 and "other things in littérature"
I haven't done a ton of updates on it since then, so it's close.
December 07, 2014, 01:20:48 PM
@wolf Yep, when I created new bin file, I put "worksize" : "64", then I replace old bin file with your bin file, and keep worksize 64. I tried this on second rig and doesnt work too. Do I maybe need to change kernel folder or something? This is frustrating
December 07, 2014, 11:21:17 AM
ok.. so i'll just mine X11 for now
thank you
thank you
December 01, 2014, 08:16:48 PM
This is something else indeed. LoveToShare, I would love if you shared some .cl files so that I could compare them with other darkcoin-mod.cl files. BTW did you compile those?
Anyway thanks for sharing...
Also I'm buying lunch if you stop by...
From his screenshot, all he has is some shitty cl and some slightly better bin files that Sabotage probably made himself by tweaking a few options in the stock darkcoin-mod and then tried to sell off as mine.
Looking at bin file size, I'd say they forced some parts of the code not to "unroll" as the whole bin is 1/2 size.
I'd love to look at their .cl to see what they've done.
In the performace side, 7950 is running at 4.9MH/s up from 3.0, 280X is about 6.4 up from 3.9
(on stock clocks. btw I have a problem with trixx and recent amd drivers, namely on 280x i seem to be able to set gpu clock and memclock, but gpu-z still shows stock clocks. Afterburner is even worse. Do you know what's with that?)
and 290X/X2 is at 8.7 per core up from 5.6 all on stock clocks.
Not bat at all I'd say. I will have to setup tomorrow to measure power usage...
Oh, goody. Now I might have to go kill someone. It could be an old version of mine - narrows the culprit down.
Are these yours? Have you looked at the .bin files?
p.s. what's with the Trixx and latest drivers? I cannot seem to be able to set gpu and mem clocks....
There's no way to tell 100% from the bin files, but you couldn't have known mine were far smaller than the shit code unless you had one - it's a little old, but your hashrates are also correct. Someone has stolen from me.
December 07, 2014, 11:13:33 AM
wolf
your .bin is working very good for me for X11
do you have the same for X13 ?
mining with 1 280x (which can't run f@h)
your .bin is working very good for me for X11
do you have the same for X13 ?
mining with 1 280x (which can't run f@h)
December 07, 2014, 09:29:53 AM
Like you said, I removed all bin files. After restarting rig, new .bin file was created, then I put new one in and rename it. After that I restarted mining but nothing happens, mining not starting....
December 07, 2014, 09:02:22 AM
What can be problem then? I notice, when I erase old .bin file and put new one, after restarting rig old .bin file shows up again on same place, and then I have 2 bin files in same folder, miner using old bin file ofc...
This is what I'd try: Remove all bins from folder. Start miner. Stop after first hash. Copy name of bin file just created. Rename new bin with that bin name you just created. Do not have del *.bin in .bat file. Try that.
December 07, 2014, 08:53:50 AM
What can be problem then? I notice, when I erase old .bin file and put new one, after restarting rig old .bin file shows up again on same place, and then I have 2 bin files in same folder, miner using old bin file ofc...
December 01, 2014, 07:46:11 PM
This is something else indeed. LoveToShare, I would love if you shared some .cl files so that I could compare them with other darkcoin-mod.cl files. BTW did you compile those?
Anyway thanks for sharing...
Also I'm buying lunch if you stop by...
From his screenshot, all he has is some shitty cl and some slightly better bin files that Sabotage probably made himself by tweaking a few options in the stock darkcoin-mod and then tried to sell off as mine.
Looking at bin file size, I'd say they forced some parts of the code not to "unroll" as the whole bin is 1/2 size.
I'd love to look at their .cl to see what they've done.
In the performace side, 7950 is running at 4.9MH/s up from 3.0, 280X is about 6.4 up from 3.9
(on stock clocks. btw I have a problem with trixx and recent amd drivers, namely on 280x i seem to be able to set gpu clock and memclock, but gpu-z still shows stock clocks. Afterburner is even worse. Do you know what's with that?)
and 290X/X2 is at 8.7 per core up from 5.6 all on stock clocks.
Not bat at all I'd say. I will have to setup tomorrow to measure power usage...
Oh, goody. Now I might have to go kill someone. It could be an old version of mine - narrows the culprit down.
December 07, 2014, 03:44:15 AM
Hi guys, I cant configure new wolf miner, I appreciate any help .
I using smos linux for mining, I put new wolf0 bin file and reneme it, but still getting same hashrate with Asus 7950 cards, around 3,2mhs.
Does somebody know what I am doing wrong?
This is my config file (Asus 7950 cards):
],
"kernel" : "x11mod",
"api-listen" : true,
"expiry" : "28",
"log" : "5",
"queue" : "1",
"scan-time" : "7",
"shares" : "0",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-engine" : "0",
"gpu-engine" : "1040",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "8",
"intensity" : "18",
"xintensity" : "0",
"auto-fan" : true,
"temp-target" : "65",
"temp-overheat" : "75",
"temp-cutoff" : "80",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "0",
"shaders" : "1792",
"thread-concurrency" : "8192"
}
Is this correct bin file for my cards?
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
.I using smos linux for mining, I put new wolf0 bin file and reneme it, but still getting same hashrate with Asus 7950 cards, around 3,2mhs.
Does somebody know what I am doing wrong?
This is my config file (Asus 7950 cards):
],
"kernel" : "x11mod",
"api-listen" : true,
"expiry" : "28",
"log" : "5",
"queue" : "1",
"scan-time" : "7",
"shares" : "0",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-engine" : "0",
"gpu-engine" : "1040",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "8",
"intensity" : "18",
"xintensity" : "0",
"auto-fan" : true,
"temp-target" : "65",
"temp-overheat" : "75",
"temp-cutoff" : "80",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "0",
"shaders" : "1792",
"thread-concurrency" : "8192"
}
Is this correct bin file for my cards?
https://ottrbutt.com/miner/wolf-x11Tahitigw64l8ku0.bin
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
December 02, 2014, 08:16:41 PM
Aren't the changes to these algorithms more or less like what was previously done for x11, several small kernels vs one big one.?
Jump to: