[Dev] NeoScrypt GPU Miner - Public Beta Test
-
First, just so you know - the port was done by an official SGMiner dev who I happen to know - I just annoyed him until he did it and then compiled it, along with adding my kernel and changing it just a tiny bit for SGMiner.
Anyway, my FTC address: 6gD49TDWtSseGno9Hi17XahzejF1BKAtSb
I already knew that wolf. Just wanted to report my findings on using the miner for FTC. If I have a chance I will report the issue on the sgminer-dev github.
-
Alright, so after testing sgminer5 here are my observations:
It’s the same speed as cgminer-neoscrypt 3.7.8 with wolf0’s kernel.
It works great if you are going to be switching from mining FTC to other coins with different algorithms (sgminer5 is intended to be a unified miner).
It works great if you have one graphics card in your computer.
It works great if you have multiple graphics cards, BUT only if those cards all use the same worksize.
If you try and specify custom worksizes for multiple cards either through passing -w x,x through command line, or by specifying “worksize” : “x,x”, in config what happens is ONLY the first worksize is applied to ALL GPUs, so the resulting bin files will not be optimized for one or more cards.
If you use a multi-GPU setup, and the cards have different worksizes I recommend sticking with cgminer 3.7.8, as the custom worksizes will be applied properly, and the bin files will be optimized for each card.
Note: Copying bin files from cgminer 3.7.8 over to sgminer5 and renaming them to work in sgminer does not work for instances where you are trying to get multiple cards with different worksizes to work.
I have a multi-GPU setup - I use diff worksizes, and it’s fine.
-
I have a multi-GPU setup - I use diff worksizes, and it’s fine.
You are on linux though right?
-
You are on linux though right?
Yes, but I also use a config file, which could be it, too.
-
Yes, but I also use a config file, which could be it, too.
I am using config file, plus I have also tried passing -w 48,32 and --worksize 48,32 to command line and it still only generates bins with w48. Take a look at this screenshot:
The 7870 Pitcairn is what is taking a hit with sgminer5. It’s not a huge hit though, only about 5 Kh/s with w48 instead of w32, but using same config on cgminer 3.7.8 Neoscrypt it generates the bins with w48 and w32 respectively.
-
I am using config file, plus I have also tried passing -w 48,32 and --worksize 48,32 to command line and it still only generates bins with w48. Take a look at this screenshot:
The 7870 Pitcairn is what is taking a hit with sgminer5. It’s not a huge hit though, only about 5 Kh/s with w48 instead of w32, but using same config on cgminer 3.7.8 Neoscrypt it generates the bins with w48 and w32 respectively.
Odd - works for me, so maybe it is a Windows issue.
-
Odd - works for me, so maybe it is a Windows issue.
Yeah. Maybe I should just bite the bullet and install a Linux distro on my miner.
-
Ugh, I hate the AMD OpenCL compiler - not only does it sometimes mangle code, but it is STUPID. This thing should not have graduated from compiler kidnergarten. It’s also full of bugs - I just figured out it’s flat-out ignoring some of my loop unrolling instructions. I wrote a far better chacha round function and my hash on 280X dropped from 270kh/s to under 200kh/s. Now I need to make it into a macro so I can unroll it manually.
-
Hey Wolf0,
I really like what you are doing.
Sent you 50FTC as small tip.
;)
-
I am also following Wolf0’s great work. Thanks again. ++ Karma points to Wolf0.
-
try lowering core clock to 1100 and run w 48 i 15 g2 on 280x/7970 getting between 130 and 150 per card
sgminer stable overnigt and still going
clocks same as i used with cgminer
-I 15 not working, some kernel error( too low memory), im using -I 14 w 48 g2 135khs
-
sgminer stable overnigt and still going
clocks same as i used with cgminer
-I 15 not working, some kernel error( too low memory), im using -I 14 w 48 g2 135khs
With SGMiner, you may now set thread concurrency.
-
With SGMiner, you may now set thread concurrency.
YAY!!! More settings!!! lol
-
Finally got it compiled and could test a bit :)
Two things I noticed:
- on a 64Bit compile the A:xxx Value in the first line of the Display reads: A:22323232343463467722132415…
this looks like a 23bit overflow and happened on the first versions of cgminer-neoscryp, too
- Stratum doesn’t work for me, longoll works fine
errormessage: ‘message received: unknown method’
I run against a p2pool, that is working fine for cgminer.
- hashrate slightly increased on my HD 8400 GPU ( I know, I know, it’s just a laptop GPU.
-
Finally got it compiled and could test a bit :)
Two things I noticed:
- on a 64Bit compile the A:xxx Value in the first line of the Display reads: A:22323232343463467722132415…
this looks like a 23bit overflow and happened on the first versions of cgminer-neoscryp, too
- Stratum doesn’t work for me, longoll works fine
errormessage: ‘message received: unknown method’
I run against a p2pool, that is working fine for cgminer.
- hashrate slightly increased on my HD 8400 GPU ( I know, I know, it’s just a laptop GPU.
Use my SGMiner 5 compile for neoscrypt.
-
Use my SGMiner 5 compile for neoscrypt.
earlier was 4.2.2 version, is there another outhere?
-
earlier was 4.2.2 version, is there another outhere?
It’s actually SG5 - the dev branch is misnamed.
-
earlier was 4.2.2 version, is there another outhere?
Wolf0’s compile is a development snapshot of sgminer5. Every development snapshot of sgminer I have used has had the version as 4.2.2 even though it’s really version 5.
Edit: Wolf beat me to it
-
Use my SGMiner 5 compile for neoscrypt.
I used this link: https://github.com/sgminer-dev/sgminer
Do you have forked it?
-
I used this link: https://github.com/sgminer-dev/sgminer
Do you have forked it?
No, that’s the link - use the develop branch.
