[Dev] NeoScrypt GPU Miner - Public Beta Test
-
miner compiled by wolf? 4.2.2 so called 5.xx??
im on win 7 64 bit . xi no use… i have no idea why
Make sure you are removing regular intensity setting from your config when you run xintensity.
-
No need since adding xintensity overrides intensity settings.
-
Make sure you are removing regular intensity setting from your config when you run xintensity.
yep, im not so stupid. still no idea what this is…
we been fooled…
-
try my dllls from previous post and update your results??
edit: my best test
getting best results so far using dlls from 14.201.1009( very little effect):
The 14.2 is what you posted. Exact same results as 14.6 and 14.7 for me.
-
yep, im not so stupid. still no idea what this is…
we been fooled…
Have you seen the screenshots from Wolf0 where he shows off his new kernel speeds? Notice how he uses just regular intensity? There’s a reason for that: xintensity and rawintensity are not necessarily the holy grail of mining. It’s a bitch to set up properly, and while it may work for one person, it may not work for another. This isn’t the first time I have seen someone make these type of claims about using xintensity or rawintensity, and it won’t be the last. I’ve spent countless hours tweaking settings to get xintensity and rawintensity configs for miners, and while sometimes it delivers, most times I just go back to regular intensity configs. I wouldn’t get worked up over claims of crazy high hash rates using xintensity or rawintensity.
-
The 14.2 is what you posted. Exact same results as 14.6 and 14.7 for me.
I believe they are going off the actual DLL versions of the files, and not using the Catalyst version like most of us do. So when they say 14.2 it is probably Catalyst 14.6 RC2 or Catalyst 14.7 RC3.
-
miner compiled by wolf? 4.2.2 so called 5.xx??
im on win 7 64 bit . xi no use… i have no idea why
No, I am not using the miner compiled by wolf0. I am using the sgminer-5.1.0-dev builds that are built by Nicehash.
Use the sgminer I posted here to use the same one as me:
-
^^ same build of SGminer that I have…
-
i made some notepad work, we should get 50% of original scrypt hashrate when kernel is optimal
-
Guys i use this miner
I have included a sgminer-5.1.0-dev 7z file with all of the changes listed above here:
https://drive.google.com/file/d/0B06N0FYvyFgDeHBnTVEtR3BVN2c/view?usp=sharing
and @majsta settings in my .bat file
sgminer.exe -k neoscrypt --xintensity 3 --worksize 256 -g 2 -o xxxx:xxxx -u x -p x --thread-concurrency 8192 -d 0,1
(280x+7950…3rd is 5850 and its off). 14.4 drivers, W7x64, 1000(gpu)/1500(mem) for both cards
and you can see results
edit:
.bat file without --thread-concurrency got only HW…
-
Well, after spending the afternoon screwing around with the xintensity, the best I could get was a bump up from 325k to 327k for the 290’s and a loss from 308k to 298k for the 290x’s.
Back to straight intensities for me… (for now)
-
Glad to see some are finally take note about xIntensity I posted about way back in this thread. I have never use sgminer much at all
and had pretty bad luck with it when I did test with it way back and since this went to neoscrypt so I didn’t put much time in trying to
find a working version of sgminer that has xIntensity. I still have my old tweaked settings for all my AMD cards and will test those out
soon and if there good to go I’ll post those to help others with the type of AMD cards I have on hand.
I did try some testing with cgminer back a few weeks ago but didn’t have the neoscrypt kernel we have now to test with. ;-)
-
Guys i use this miner
and @majsta settings in my .bat file
(280x+7950…3rd is 5850 and its off). 14.4 drivers, W7x64, 1000(gpu)/1500(mem) for both cards
and you can see results
edit:
.bat file without --thread-concurrency got only HW…
So you inspired me to test these settings on one of my mining rigs, which has a AMD HD 7950 (Hynix) and a AMD HD 7870 (Unknown). Here are the results:
Using previous settings:
Sapphire Reference AMD HD 7950 (Hynix) @ gpu-engine1100 gpu-memclock1500
I15 g1 w64
272 Kh/s
AMD HD 7870 (Unknown)
I15 g1 w64
115.6 Kh/s
Using new settings:
Sapphire Reference AMD HD 7950 (Hynix) @ gpu-engine1100 gpu-memclock1500
xI3 g2 w256 lookup-gap2 thread-concurrency8192
327.3 Kh/s
AMD HD 7870 (Unknown)
xI3 g2 w64 lookup-gap2 thread-concurrency8192
126 Kh/s
Hash Rate Summary:
Sapphire Reference AMD HD 7950 (Hynix): +20.2%
AMD HD 7870: +9%
Sapphire Vapor-X 290x (Hynix): Takes a performance hit. Traditional intensity works better.
-
solved!! used miner NOT compiled by wolf!
-
I believe they are going off the actual DLL versions of the files, and not using the Catalyst version like most of us do. So when they say 14.2 it is probably Catalyst 14.6 RC2 or Catalyst 14.7 RC3.
yep, not talking about catalyst version, but actual driver version
AMD Catalyst 14.9 (14.201.1009)
now trying 14.9rc2, first look seems its fastest(like 0.5%)
-
So you inspired me to test these settings on one of my mining rigs, which has a AMD HD 7950 (Hynix) and a AMD HD 7870 (Unknown). Here are the results:
Using previous settings:
Sapphire Reference AMD HD 7950 (Hynix) @ gpu-engine1100 gpu-memclock1500
I15 g1 w64
272 Kh/s
AMD HD 7870 (Unknown)
I15 g1 w64
115.6 Kh/s
Using new settings:
Sapphire Reference AMD HD 7950 (Hynix) @ gpu-engine1100 gpu-memclock1500
xI3 g2 w256 lookup-gap2 thread-concurrency8192
327.3 Kh/s
AMD HD 7870 (Unknown)
xI3 g2 w64 lookup-gap2 thread-concurrency8192
126 Kh/s
Hash Rate Summary:
Sapphire Reference AMD HD 7950 (Hynix): +20.2%
AMD HD 7870: +9%
Sapphire Vapor-X 290x (Hynix): Takes a performance hit. Traditional intensity works better.
That’s blazing fast! Just need to find those magic settings for the 290/290x now…
-
That’s blazing fast! Just need to find those magic settings for the 290/290x now…
The 290x is a bit of a mystery atm. Not quite sure why an AMD HD7950 can outperform it on neoscrypt.
-
yep, not talking about catalyst version, but actual driver version
AMD Catalyst 14.9 (14.201.1009)
now trying 14.9rc2, first look seems its fastest(like 0.5%)
AMD hasn’t changed the OpenCL 1.2 DLLs from 14.6 Beta all the way to 14.11. I doubt there will be any speed improvements.
I take that back. They have changed the AMD OpenCL drivers; however, in my testing anything higher than 14.7 RC3, which uses the same OpenCL 1.2 1526.3 as 14.6 RC2, you will get HW errors trying to generate bins. This new kernel from wolf doesn’t appear to get any boost from newer drivers after the bins are created.
-
file size is not same…
bins now created ok, no hw erros with 14.9-14.11 catalyst
-
file size is not same…
yeah the checksums aren’t going to match, most likely because they are re-signing the drivers on every release, which is going to end up with a different checksum every time even though versions are identical.