Hi Zawawa, Can your miners be used by auto algo switcher tools ..... like ... Sniffdogminer.
I won't mind your devfee... if it can be simply launched and killed just like ccminer, as and when required during better profit coin.
Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 109. (Read 214410 times)
Literally just made a bitcoin forums account to say that i have a problem with neo scrypt and the second gpu doesnt work. read the last page here and see u already updated it and fixed it Zawawawa. You are the man and thankyou for ur ongoing development 
. Merry Xmas and Happy New Years
. Merry Xmas and Happy New Years
Anyone compared this miner with mkxminer for lyra2 algo?
mkx is pretty fast, but often (randomly) unstable for me
mkx is pretty fast, but often (randomly) unstable for me
Gateless Gate Sharp 1.1.6 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for Lyra2REv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for Lyra2REv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
That fixed it your a man among boys. Thank you.
At the moment there is a bloom of alt coins using these algos x17, Blake2s, Nist5, Phi, for example XVG price is sky rocketing and if it continuous it will attract a lot of miners. Maybe is good idea to add one of these algos also. Good luck with your work.
I don't know where you find "blooms" for this monets/algos. Good luck with your work.Most profitable monets/algos the same as they was most of time last year. It's cryptonight, equihash, ethash and neoscrypt.
At the moment there is a bloom of alt coins using these algos x17, Blake2s, Nist5, Phi, for example XVG price is sky rocketing and if it continuous it will attract a lot of miners. Maybe is good idea to add one of these algos also. Good luck with your work.
Good luck with your work. Gateless Gate Sharp 1.1.6 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for LyraREv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for LyraREv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
Thanks for the update! What is the performance of RX 570/580 on Lyra2v2 algo?
Gateless Gate Sharp 1.1.6 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for Lyra2REv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.6-alpha
* Added support for Lyra2REv2.
* Fixed a critical performance issue with NeoScrypt.
* Fixed a critical bug in the DEVFEE mode.
Thanks a lot for the bug reports!
Hi,
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
Please let me know what you need from me. Keep up teh good work!
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
Please let me know what you need from me. Keep up teh good work!
There was a bug that affects only the second card in the mix.
I will upload a new version with bug fixes right now.
Hi,
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
Please let me know what you need from me. Keep up teh good work!
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
Please let me know what you need from me. Keep up teh good work!
Does the poor performing card have a monitor or dummy plug connected to it?
Hi,
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
https://ibb.co/fRw4FR
Please let me know what you need from me. Keep up teh good work!
I am experiencing a problem when mining neoscrypt. GPU1 always get horrible hashrates. I removed the card in gpu1 slot(Tested with fans to see which on it was) and then the next card that takes that slot gets that bad rate.
Picture below :
https://ibb.co/fRw4FR
Please let me know what you need from me. Keep up teh good work!
I just found out CL_DEVICE_TOPOLOGY_AMD does not work with the latest AMD drivers.
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
The newest drivers are using the HSA/ROCm compiler, which is no longer targeted specifically at GPUs.
I suggest using -legacy at least as an interim solution.
See, the thing is, I need to get information about device topology before the program is built.
clGetDeviceInfo() is broken, and AMD people really have to get their act together and fix this issue.
I just found out CL_DEVICE_TOPOLOGY_AMD does not work with the latest AMD drivers.
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
The newest drivers are using the HSA/ROCm compiler, which is no longer targeted specifically at GPUs.
I suggest using -legacy at least as an interim solution.
My comment wasn't meant for newbies, but I'll humor you.
You probably can't change the OpenCL build options in the GUI. I can't say for sure since I don't use GGS (I do miner dev work only on Linux). You might be able to add it through an environment variable, and you can definitely add it in the source.
Oh okay I know what you mean, I thought I was missing something that didn't require recompiling.
I just found out CL_DEVICE_TOPOLOGY_AMD does not work with the latest AMD drivers.
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
The newest drivers are using the HSA/ROCm compiler, which is no longer targeted specifically at GPUs.
I suggest using -legacy at least as an interim solution.
My comment wasn't meant for newbies, but I'll humor you.
You probably can't change the OpenCL build options in the GUI. I can't say for sure since I don't use GGS (I do miner dev work only on Linux). You might be able to add it through an environment variable, and you can definitely add it in the source.
I just found out CL_DEVICE_TOPOLOGY_AMD does not work with the latest AMD drivers.
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
The newest drivers are using the HSA/ROCm compiler, which is no longer targeted specifically at GPUs.
I suggest using -legacy at least as an interim solution.
I just found out CL_DEVICE_TOPOLOGY_AMD does not work with the latest AMD drivers.
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
This explains why GGS cannot detect GPU's properly with these drivers. Grrrrr...
The newest drivers are using the HSA/ROCm compiler, which is no longer targeted specifically at GPUs.
I suggest using -legacy at least as an interim solution.
Hello Mister Z , are you planning on adding support for Vega cards and also are there any pairs we can mine monero with currently?
Cheer
Cheer
HI zawawa.
Also experiencing the low hashrate on one card with Neoscrypt
see include screen grab of HWinfo and GG.
cards used are rx470s,rx570s and rx580s with amd blockchain driver.
from HWINFO seems to be a gpu memory issue.
Otherwise speeds are awesome between 700hs-800khs for my cards
https://imgur.com/DJrNr9q
Also experiencing the low hashrate on one card with Neoscrypt
see include screen grab of HWinfo and GG.
cards used are rx470s,rx570s and rx580s with amd blockchain driver.
from HWINFO seems to be a gpu memory issue.
Otherwise speeds are awesome between 700hs-800khs for my cards
https://imgur.com/DJrNr9q
Waiting new big release excitedly 
Also, I really want to expose on-the-fly memory timing mods to the user.
We will see...
Thanks !!!It will be wonderful.. And Dear Zawawa, regarding to devfee pool : If I am mining cyptonight , during devfee it is changing to other algorithm(i.e ethash) for 1-2 minutes. Devfee is ok , but changing algoritm , screwing up the card`s fine overclock settings (fan/heat , even voltage , wattage), and sometimes hangs. u know what I mean.. can u not make it ,such that your devfee stays in the same algorithm?.
And it is lagging in opening and closing too much ..I think some other users also reported this previously..
I will fix the first one ASAP. One more bug to shoot down during the Christmas break. lol
Waiting new big release excitedly
Also, I really want to expose on-the-fly memory timing mods to the user.
We will see...
Thanks !!!It will be wonderful.. And Dear Zawawa, regarding to devfee pool : If I am mining cyptonight , during devfee it is changing to other algorithm(i.e ethash) for 1-2 minutes. Devfee is ok , but changing algoritm , screwing up the card`s fine overclock settings (fan/heat , even voltage , wattage), and sometimes hangs. u know what I mean.. can u not make it ,such that your devfee stays in the same algorithm?.
And it is lagging in opening and closing too much ..I think some other users also reported this previously..
Jump to: