Author

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

member
Activity: 81
Merit: 1002
It was only the wind.
Yes but honestly the mining revenue for X11 right now is a joke.

6 months ago we were using an old miners but making 0.006/BTC/MHASH and now we are making what ? Barealy 0.00015/BTC/MHASH

Not profitable anyway

Yeah, even with my bins, it's a waste of time.
sr. member
Activity: 539
Merit: 255
It is a free service mostly (as most people don't even donate), so the "unhappy customer" behavior, won't help you a lot....
 and again the info has been posted on vertcoin thread (you should visit if you intend to mine it....)
Do you have time to make your rigs running ? (may-be you want people to send you btc directly too ?)

by the way there is a windows-build.txt file in directory doc with everything needed to build a compilation environnement under windows.
(with even the link to the packages...)

LOL, yeah, I'm so lazy that I tried that build it yourself from the text file...  It is outdated, and absolutely meaningless with the updated compiler packages nowadays.  Have you looked at it?  

How would you know ?  Grin
It is may-be outdated but it works. and this is with that I compile the stuff you will download to get some money out of your investment...
once you have found the vertcoin thread

How would I know?  Because I tried it.  It says to do things that there are not options to do after the updated packages were released.
legendary
Activity: 1400
Merit: 1050
It is a free service mostly (as most people don't even donate), so the "unhappy customer" behavior, won't help you a lot....
 and again the info has been posted on vertcoin thread (you should visit if you intend to mine it....)
Do you have time to make your rigs running ? (may-be you want people to send you btc directly too ?)

by the way there is a windows-build.txt file in directory doc with everything needed to build a compilation environnement under windows.
(with even the link to the packages...)

LOL, yeah, I'm so lazy that I tried that build it yourself from the text file...  It is outdated, and absolutely meaningless with the updated compiler packages nowadays.  Have you looked at it?  

How would you know ?  Grin
It is may-be outdated but it works. and this is with that I compile the stuff you will download to get some money out of your investment...
once you have found the vertcoin thread
sr. member
Activity: 539
Merit: 255
It is a free service mostly (as most people don't even donate), so the "unhappy customer" behavior, won't help you a lot....
 and again the info has been posted on vertcoin thread (you should visit if you intend to mine it....)
Do you have time to make your rigs running ? (may-be you want people to send you btc directly too ?)

by the way there is a windows-build.txt file in directory doc with everything needed to build a compilation environnement under windows.
(with even the link to the packages...)

LOL, yeah, I'm so lazy that I tried that build it yourself from the text file...  It is outdated, and absolutely meaningless with the updated compiler packages nowadays.  Have you looked at it?  

If you'd like to donate some BTC, pick somewhere else.  I like to mine, that's why I have invested thousands in hardware to do it with.  But working a lot don't have time to invest into something with a steep learning curve.  Last time I compiled anything was for Apple in the 80's.

Vertcoin thread?  I'll have to take a look, hopefully it's not another dead end that I don't really have time to waste following.
member
Activity: 81
Merit: 1002
It was only the wind.
7970 just 38khs on Neoscrypt  Tongue first time, whats the setting for NEO and which is the best miner?

There's only one miner...
legendary
Activity: 1512
Merit: 1000
quarkchain.io
I've  lost in the thread. Would you help me with the reached speed of neoscrypt with 280X ?

Reach what speed?

I cant rice above 320-322 kh/s with your kernel from nicehash with 14.7 rc3 driver , with these settings:
Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

localpath\sgminer.exe --algorithm neoscrypt -o url -u user -p pass --intensity 13 --rawintensity 6144 -g 2 -w 256 --gpu-platform 0 --gpu-memclock 1500 --gpu-engine 1030 --thread-concurrency 8192 --shaders 2048 --api-listen --api-port 4028 --api-allow W:127.0.0.1

pause
legendary
Activity: 1400
Merit: 1050
By the way the latest version of lyra2RE (which should be slightly faster than the one in metalicjames, better groestl256 and one round blake256) can be found here:
https://github.com/djm34/sgminer

Where does one find compiled win32 or 64 binaries of this? Or is there too much sadistic pleasure in making software illiterate GPU rig operators have to figure out how to compile it themselves?  Shocked
learn to compile or ditch winblows

Yeah, great....  Work 60+ hour weeks, and then learn linux or learn how to compile in all the spare time I don't have because I'm so lazy and stupid.
It is a free service mostly (as most people don't even donate), so the "unhappy customer" behavior, won't help you a lot....
 and again the info has been posted on vertcoin thread (you should visit if you intend to mine it....)
Do you have time to make your rigs running ? (may-be you want people to send you btc directly too ?)

by the way there is a windows-build.txt file in directory doc with everything needed to build a compilation environnement under windows.
(with even the link to the packages...)
sr. member
Activity: 539
Merit: 255
By the way the latest version of lyra2RE (which should be slightly faster than the one in metalicjames, better groestl256 and one round blake256) can be found here:
https://github.com/djm34/sgminer

Where does one find compiled win32 or 64 binaries of this? Or is there too much sadistic pleasure in making software illiterate GPU rig operators have to figure out how to compile it themselves?  Shocked
learn to compile or ditch winblows

Yeah, great....  Work 60+ hour weeks, and then learn linux or learn how to compile in all the spare time I don't have because I'm so lazy and stupid.
member
Activity: 81
Merit: 1002
It was only the wind.


Humm. I'm not sure why I'm showing you this, maybe because I have something to brag and I like bragging. Smiley

I made some small optimizations on the Wolf's neoscrypt kernel. Now it does 430khs on 280x, 450khs on r9 290, and 260khs on r9 270.

I'm thinking what I should do with this. There's no point to release this to public as this would just make net hashrate rocket and everyone would still get the same profit.



 Shocked you should keep this config for yourself. If sharing, the net hash rate increases so high.

I've got it too, and that's my plan Tongue
member
Activity: 158
Merit: 10
Hello, can you help me with neoscript for r9 290x what miner and what configs need to use. I cant get above 260 kh.
hero member
Activity: 935
Merit: 1001
I don't always drink...
it is Catalyst 14.6

finally got mine up over 1 Mh/s with xI 256, 815/1500, w 64, g 2, tc 8192
legendary
Activity: 1792
Merit: 1008
/dev/null
By the way the latest version of lyra2RE (which should be slightly faster than the one in metalicjames, better groestl256 and one round blake256) can be found here:
https://github.com/djm34/sgminer

Where does one find compiled win32 or 64 binaries of this? Or is there too much sadistic pleasure in making software illiterate GPU rig operators have to figure out how to compile it themselves?  Shocked
learn to compile or ditch winblows
legendary
Activity: 1400
Merit: 1050
By the way the latest version of lyra2RE (which should be slightly faster than the one in metalicjames, better groestl256 and one round blake256) can be found here:
https://github.com/djm34/sgminer

Where does one find compiled win32 or 64 binaries of this? Or is there too much sadistic pleasure in making software illiterate GPU rig operators have to figure out how to compile it themselves?  Shocked
that would be a good start for making you less software illiterate...
The binaries were posted vertcoin thread
full member
Activity: 198
Merit: 100
By the way the latest version of lyra2RE (which should be slightly faster than the one in metalicjames, better groestl256 and one round blake256) can be found here:
https://github.com/djm34/sgminer

Where does one find compiled win32 or 64 binaries of this? Or is there too much sadistic pleasure in making software illiterate GPU rig operators have to figure out how to compile it themselves?  Shocked
member
Activity: 81
Merit: 1002
It was only the wind.
You know the funny thing about your whole BS campaign against miners Wolf is after your kernel leaked, x11 difficulty has barely moved. Which means one of three things. Everyone is operating on Maxwell (I find this hard to believe), people didn't find it... OR more then likely it was already well distributed before it leaked.

Remember my threads where I was asking what was happening in the last two months that made difficulty jump so much? Then I surmised that it was because people were using GPUs as space heaters. I'm pretty sure your kernel has been in circulation for quite some time already either through your own hands or from back room trading behind the scenes. Either way I'm earning now what I did before people turned their GPUs on 'for heat' with x11, which just happened to coincide with when you started distributing your kernel.

So you basically shot yourself in your feet by trying to keep everything low key, which just made more people try and sell it behind your back... And apparently all the big miners got it because it hasn't changed a darn thing now that it's public. I suppose they could have their own super secret kernel maker too? -_-

Too bad you didn't just go public with it (besides bragging) and make a miner for it... but I suppose people would just cheat that as well (and apparently also resell it for cheaper to other people). There are also people that would be willing to NOT pay 3 BTC, but donate hashing power as well... But you know, keep thinking what you want.

Oh and people still pay Claymores fee.

Well, you can lower your voltages and clocks, to get same hashrate with less watts. Less clock necessarily doesn't mean less watts, but less voltage almost definetily does..

But yes, running higher hashrate means higher watts also. I haven't measured it because power consumption is not an issue for me, but the GPUs seem to run a bit hotter.

Aye, not talking about higher hashrate then what we're getting right now. Same hashrate as publicly available miner, with the optimizations he put in place in this one.

I know it got distributed before it was public. People pay Claymore's fee for one reason: no one has publicly reverse engineered his code yet. Many people use a proxy to strip out his fee, as well.
full member
Activity: 198
Merit: 100
Wolf0,

Did you stop compiling your 64-bit Windows Development Binaries?
member
Activity: 81
Merit: 1002
It was only the wind.


Humm. I'm not sure why I'm showing you this, maybe because I have something to brag and I like bragging. Smiley

I made some small optimizations on the Wolf's neoscrypt kernel. Now it does 430khs on 280x, 450khs on r9 290, and 260khs on r9 270.

I'm thinking what I should do with this. There's no point to release this to public as this would just make net hashrate rocket and everyone would still get the same profit.



Either release it for free, or bury it and never release it.

Optomizing the kernel and skyrocketing the hashrate by releasing it does nothing but allow cards to get what they should really be getting anyway.

Burying it changes nothing.

Selling it, simply makes people that can't afford to buy it because of the low ROI on GPU's angry with you, and the whales that can afford to spread the ROI across many GPU's get fatter.

Also makes devs poorer. Just saying.

Selling it responsibly can be good for everyone involved - don't be a dick and sell a 10x faster miner, release most of it slowly, and sell one that's around 2x faster. That way, the public isn't too far behind.

Program it into a miner and have the miner auto donate 1%..  Easy enough.  Level playing field AND you get coin.

Don't you remem- oh, fuck it. I'm tired of teaching people crypto history.

Post a link, I'll figure it out, I'm good like that.

But finding that in the morass that is crypto, is damn near impossible.

It'd take several links, as it happened on BCT, but since you seem to care, I'll reiterate. There was a user named girino that made X11 50% faster, put in a 2% fee, and the community basically reverse engineered it, ripped out his code, and put it in sph-sgminer, which then got pulled into SGMiner. It is now called "darkcoin-mod" or "x11mod."

This community will do anything to not pay even a tiny fee - and anything can be reverse engineered, because if a computer can understand it, so can a human. So, the only thing you can do is make it very hard - but fuck up, and all your work will be for nothing. Having to risk that sucks.

It might be better if kernel was only released in binary form (*.bin), and not the source. The binaries could also be signed so if there is a leak, you could tell who has leaked..

Binary distribution would also eliminate the problem with different Catalyst versions. For example current neoscrypt kernel only compiles properly on Catalyst 14.6, anything newer or older generates HW errors or very slow speed. Then again all scrypt kernels compile best on 13.12, compiling on 14.x works but gives perhaps 30% lower hashrate..

The compiled binaries can be moved around with no problem. I have used the 14.6 neoscrypt binary with 13.12, and it works fine with full speed. Recompiling it under 13.12 halves the hashrate..

Still the biggest problem is, some users have 200 gpus and some have only a few. If you are selling a kernel, the price should be different! It should be "per GPU" price, but it is impossible to control. If the price is fixed, some big rig owner can easily pay a few BTC to get the kernel, and then ruin the profits for all "hobby" miners.

I like to optimize these just for my own fun. And obviously it's good if you get some profit from your work. But at the moment it seems the best way to profit, is just keep the kernel to yourself and enjoy the increased hashrate.. Any wider distribution will just lower my own profit.


Agreed. Thanks for the tip, btw - 290X does 520kh/s with some tweaking. I'm gonna work on it more, I think, along with Lyra2RE.

(nsfw): https://ottrbutt.com/miner/neoscryptwolf-12072014.png
sr. member
Activity: 384
Merit: 250
Hey Wolf0,

Sorry to bud in like this but I just came through the following, seems saying the sgminer support GPU/script and for AMD GPU only?
There also Win64 Build and apparently that build seem leading to you I assumed!

https://litecoin.info/Mining_software

Can you provided setting for litecoin GPU mining with scrypt support?
I did trying viewing options but cannot locate option leading to scrypt support!

While mining QRK since other members suggested using -i 14 and -g 2, I assume its the same for litecoins?

It would help by seeing the code leading to actual setting so I can test it as none GPU miner support script!
yes, I am using one GPU CARD!

Thank for your support

7970 just 38khs on Neoscrypt  Tongue first time, whats the setting for NEO and which is the best miner?

For 7970, look up the 280x settings.
Tried that but no luck. i am using wolf miner "wolf-neo-sgminer5-hawaii-11212014"

Don't use that one - use Nicehash's build. Hawaii chips are 290/290X.
sgminer uses ckolivas.cl instead of neo when i use that version.
bat file is something like this and neoscrypt.cl is in the same folder.
Code:
sgminer --algorithm neoscrypt -o stratum+tcp://stratum.ftc.theblocksfactory.com:3333 -u x.1 -p x

You need the develop version of SG 5.
hero member
Activity: 658
Merit: 500
Got Sapphire R9 290 Tri-x, amd 14.12 and only getting top 106Kh/s  Sad

Anybody has good settings?
newbie
Activity: 18
Merit: 0

I've moved into Neoscrypt with 280X cards, 14.6 Catalyst and Driver, and the recent Nicehash neoscrypt kernel.
I have my 280X's running 1000gpuclock / 1500memclock and 340KH/s   

However, I see that 400KH/s or better is doable, so hack at the kernel I must.         

I have already found some weird things with the compiler, such as crashing on perfectly good code,
and there are places where adding meaningless instructions actually makes it faster, so I assume there
is some fitment of code into a core size which I need to get a feel for.

Would anyone care to be so nice as to point me to a particular section of the kernel where I should
focus my attention, or at least a push in the right direction?  Several unrolls and coding functions inline
have resulted in just a few KH/s

I will start it off.....adding a temp variable to neoscrypt_blkmix makes it go 15KH/s faster. 

Jump to: