X11 X13 X15 with 50% more hashrate 7Mh/s on 280x or 10 Mh/s on 290x

[joe6pack]

To fix X13 kernel compilation:

Code:

Line 96: #include "aes_helper.cl"

should say...

#include "aes_helper-mod.cl"

or just download:

http://s000.tinyupload.com/index.php?file_id=21763187586152223354

[1714752614]

1714752614

[1714752614]

1714752614

[1714752614]

1714752614

[1714752614]

1714752614

[miningspree]

I was sad because I couldn't afford your mod, but understood you're position on giving away free. my 7950 does 5.1mh now. I will donate some btc as well, you deserve it. txid to follow

edit: https://blockchain.info/tx/08d8f2dee85b779d13bcc3ed7c9a4771fe8484cffc7eb9a7467700cf9db8a439

if you got a boost, atleast toss him a few bucks.

[qwep1]

To fix X13 kernel compilation:

Code:

Line 96: #include "aes_helper.cl"

should say...

#include "aes_helper-mod.cl"

or just download:

http://s000.tinyupload.com/index.php?file_id=21763187586152223354

I did not want to work, I'll sit on the old version

[qwep1]

Wolf0 thank you very much, you are a talented person

[jch9678]

why do my own .bin files have "bclp"  at the end ?

blake compact and luffa parallel in your config

Is there a reason not to use blake compact and luffa parallel or is it just that the bins that were leaked were not made with those settings turned on?

[joe6pack]

To fix X13 kernel compilation:

Code:

Line 96: #include "aes_helper.cl"

should say...

#include "aes_helper-mod.cl"

or just download:

http://s000.tinyupload.com/index.php?file_id=21763187586152223354

I did not want to work, I'll sit on the old version

Copy all of the .cl files from the zip posted earlier to your kernel directory, then modify marucoin-mod.cl, should work.

[Remember remember the 5th of November]

Aren't the changes to these algorithms more or less like what was previously done for x11, several small kernels vs one big one.?

[micairvas]

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

[micairvas]

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...

[JuanHungLo]

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.

[micairvas]

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....

[SalimNagamato]

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)

[SalimNagamato]

ok.. so i'll just mine X11 for now
thank you

[micairvas]

@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

[jch9678]

@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. 

[qbits]

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.

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.

[qbits]

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.

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?

[Bojcha]

Nice work Wolf0!
How much u should get with 280x at 1100/1500 ?
Currently ~6.4MH/s.

[majsta]

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.

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.

I don't know why but I m getting tons of HW errors no matter what I do.
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.

[cisahasa]

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