Download the latest NeoGpuMiner (3.7.8) and Sgminer (5.0.1-git) here!
-
Hello to all,
Download the latest version of NeoGpuMiner and Sgminer here. For Sgminer, the other algorithms have been built into the program as well as NeoScrypt.
Please give feedback to us about any change in hashrate, stability, etc. Please note that for sgminer, your AMD drivers should be from 14.x but cannot be higher than 14.6_beta2. For Neogpuminer, any driver versions from 14.x can be used, with the exception of Omega driver i.e. 14.12.
Thanks!
-
Cheers Kete!
Already off to a flying start I see!
-
I’m testing it , thank you very kindly!
-
yes, we need a resources navigation on homepage.
-
Stay tuned because the latest version of Sgminer is coming as well!
-
epic
-
What is the problem exactly? I have updated the miners today again. Could you please test the newest ones?
It works fine here with 14.9. Are you using sgminer or neominer?
-
If you are testing sgminer, please downgrade to 14.6_rc2. For neogpuminer any drivers should be fine–the latest is the best.
-
neogpuminer and sgminer 5.1.0-dev-2-gf608-dirty don’t work with 14.7 rc3 for me.
Sorry, ketetefid, but I don’t have time tonight to change drivers.
I see. That’s fine. But neogpuminer should work. What is the error? Do you have the time to take a screenshot of the problem?
-
I found another PC to test the miners and yes, due to a recent version of AMD APP SDK which has been used in building the miner, it refused to work on older versions of AMD drivers. So if anyone wants to use this, they should update to the latest driver. I hope for Nvidia users there are not any problems.
-
So, hashrate on 7950, 280X, or 290X?
-
For me the hashrate did not change very much. At most 2 kh/s. Well, this is no surprise since GCC optimizations have little to do with the program output. But 2 kh/s is still 2 kh/s!
-
For me the hashrate did not change very much. At most 2 kh/s. Well, this is no surprise since GCC optimizations have little to do with the program output. But 2 kh/s is still 2 kh/s!
Ah, okay. Yeah, getting above 250kh/s on 270X needs global memory optimization work - host code won’t do it.
-
So just to verify, this is just slightly optimized mining software, and uses the wolf kernel that is not optimized for the hawaii cards?
-
This SGminer crashes immediately with no error message.
14.9 drivers are installed, and 14.6 dll’s are in the folder, and it does not matter if the bins from a working version of SGminer are in the folder or not.
Is this expected behavior?
-
This SGminer crashes immediately with no error message.
14.9 drivers are installed, and 14.6 dll’s are in the folder, and it does not matter if the bins from a working version of SGminer are in the folder or not.
Is this expected behavior?
Thank you very much for testing the miner.
Definitely that is not the expected behavior.
I should investigate the issue and I’ll provide an update for this soon.
-
CGminer 3.7.8 also immediately crashes with no errors, running 14.9 drivers.
-
CGminer 3.7.8 also immediately crashes with no errors, running 14.9 drivers.
I heard this happens with 14.12, you sure you’re not running that?
-
CGminer 3.7.8 also immediately crashes with no errors, running 14.9 drivers.
OK. I have been investigating this issue so far with little success. I am running the program with 14.9 drivers here with no problem. However, I could get the same problem (crashing with no errors) on another PC. Anyway, I am going to turn on debugging and trace the problem. Also, I am going to test different driver versions.
By the way, I just do not like Windows (I should say I hate Windows). On Linux, driver changing is a breeze, but on Windows it becomes a pain. I myself have used Display Driver Uninstaller and several other tools to get over the stale files. Mixing files from different versions might be your problem as well. So it is worth trying DDU. It is very simple and straight forward.
Thank you very much for your patience and your efforts for testing the software.
-
I heard this happens with 14.12, you sure you’re not running that?
Absolutely 100% positive that I’m running 14.9 and not 14.12.
