Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480!

[UnclWish]

Gateless Gate Sharp 1.1.2 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.1.2-alpha

* Added Lbry support.
* Fixed a critical bug around device management.
* Adjusted the DEVFEE mode.
* Various bug fixes and improvements.

The miner should be much more stable now.
I will keep experimenting with dual-mining...

@zawawa - Dual mining of LBRY doesn't work on Nvidia?  Mine is greyed out....  Please advise.

Lbry is only solo at this moment. Dual mining is still on development...

[1713414830]

1713414830

[1713414830]

1713414830

[1713414830]

1713414830

[1713414830]

1713414830

[UnclWish]

Strange situation with 270X 4Gb card and cryptonight
On 1.1.1 i can reach 490-500 h/s - a bit less than Claymore's 505-510 h/s on RawIntensity 464-472
On 1.1.2 max I can reach is various speed from 425 to 525 h/s but often it was at lower value. RawIntensity 464-472 gives not more than 400 h/s. Often 270X on rawintensity more 512 start to give wrong shares...

And in both 1.1.1 and 1.1.2 versions GGS didn't read 270X sensors. If it enabled with other cards togather, f.e. with RX 580, sensors didn't read on all  cards. But if 270X is disabled, sensors from RX 580 works.

[zawawa]

Alright, Pascal is working now. I will give dual-mining another shot tomorrow.
It should be pretty straight-forward...

[UnclWish]

zawawa, take a look into Pitcairn problem with cryptonight, please. I think there is a lot of peoples who has 270/370 cards.
But I was forced to return to 1.1.1 version. 1.1.2 gives too low speed.

And yet another wishlist:
1. Average speed for hour/minute/from start
2. Total finded/rejected shares.
3. Individual settings for each thread.
4. Individual algo for each GPU.
5. Info about current difficulty, dag #
6. Possibility to running multiple instances of GSS.
7. Possibility to start miner via command line.

[santan]

Is it not possible to create a regular ".exe" file, instead of setup installer each time.

[zawawa]

I will look into other issues once I'm done with dual-mining with Pascal. No worries.

[UnclWish]

I will look into other issues once I'm done with dual-mining with Pascal. No worries.

I hope that after dual-mining with Pascal you can make dual with lbry or decred. They are more profitable than pascal.

[Raimy]

So what is meant by * Adjusted the DEVFEE mode.?

I noticed the DevFee portion now runs for 120 seconds, up from the previous 60 seconds it used to run at. Did the fee go up or does the miner run longer now before running the DevFee again?

To be honest, I think I like Claymore's 15 minute delay better, as if we are tweaking our rigs and trying out new settings, you always get the first 2 minutes before we can even see our results.

[zawawa]

So what is meant by * Adjusted the DEVFEE mode.?

I noticed the DevFee portion now runs for 120 seconds, up from the previous 60 seconds it used to run at. Did the fee go up or does the miner run longer now before running the DevFee again?

To be honest, I think I like Claymore's 15 minute delay better, as if we are tweaking our rigs and trying out new settings, you always get the first 2 minutes before we can even see our results.

The fee stays the same at 1%. Actually, the DEVFEE mode at the beginning is quite annoying for me as well.
I will implement a 15 minute delay right now.

By the way, dual-mining with working as expected. I will keep you guys updated.

[zawawa]

So what is meant by * Adjusted the DEVFEE mode.?

I noticed the DevFee portion now runs for 120 seconds, up from the previous 60 seconds it used to run at. Did the fee go up or does the miner run longer now before running the DevFee again?

To be honest, I think I like Claymore's 15 minute delay better, as if we are tweaking our rigs and trying out new settings, you always get the first 2 minutes before we can even see our results.

The fee stays the same at 1%. Actually, the DEVFEE mode at the beginning is quite annoying for me as well.
I will implement a 15 minute delay right now.

By the way, dual-mining with working as expected. I will keep you guys updated.

Alright, done. 

[UnclWish]

So what is meant by * Adjusted the DEVFEE mode.?

I noticed the DevFee portion now runs for 120 seconds, up from the previous 60 seconds it used to run at. Did the fee go up or does the miner run longer now before running the DevFee again?

To be honest, I think I like Claymore's 15 minute delay better, as if we are tweaking our rigs and trying out new settings, you always get the first 2 minutes before we can even see our results.

The fee stays the same at 1%. Actually, the DEVFEE mode at the beginning is quite annoying for me as well.
I will implement a 15 minute delay right now.

By the way, dual-mining with working as expected. I will keep you guys updated.

Alright, done. 

Good! Now can you take a little look into Pitcairns cryptonight issuie in 1.1.2?

[Raimy]

So what is meant by * Adjusted the DEVFEE mode.?

I noticed the DevFee portion now runs for 120 seconds, up from the previous 60 seconds it used to run at. Did the fee go up or does the miner run longer now before running the DevFee again?

To be honest, I think I like Claymore's 15 minute delay better, as if we are tweaking our rigs and trying out new settings, you always get the first 2 minutes before we can even see our results.

The fee stays the same at 1%. Actually, the DEVFEE mode at the beginning is quite annoying for me as well.
I will implement a 15 minute delay right now.

By the way, dual-mining with working as expected. I will keep you guys updated.

Alright, done. 

That was quite quick, thanks!

[zawawa]

zawawa, take a look into Pitcairn problem with cryptonight, please. I think there is a lot of peoples who has 270/370 cards.
But I was forced to return to 1.1.1 version. 1.1.2 gives too low speed.

And yet another wishlist:
1. Average speed for hour/minute/from start
2. Total finded/rejected shares.
3. Individual settings for each thread.
4. Individual algo for each GPU.
5. Info about current difficulty, dag #
6. Possibility to running multiple instances of GSS.
7. Possibility to start miner via command line.

I would look at the number of threads.
I had to change the default number of threads from 2 to 1 because 2 did not work for some AMD drivers.

[zawawa]

zawawa, take a look into Pitcairn problem with cryptonight, please. I think there is a lot of peoples who has 270/370 cards.
But I was forced to return to 1.1.1 version. 1.1.2 gives too low speed.

And yet another wishlist:
1. Average speed for hour/minute/from start
2. Total finded/rejected shares.
3. Individual settings for each thread.
4. Individual algo for each GPU.
5. Info about current difficulty, dag #
6. Possibility to running multiple instances of GSS.
7. Possibility to start miner via command line.

See, it is not that hard to add more information on the Dashboard tab page, but I don't want to stuff too much in there. I got to come up with a good idea...

[UnclWish]

What about Pitcairns low speed in 1.1.2?
Why Pitcairn sensors didn't work?
And why enabled Pitcairn card disables hardware sensors on all cards.

[zawawa]

What about Pitcairns low speed in 1.1.2?
Why Pitcairn sensors didn't work?
And why enabled Pitcairn card disables hardware sensors on all cards.

Please see my post above. Problems with sensors are actually driver problems, and there is not much I can do about it at this point. Sadly, it seems that AMD's support for GCN1 cards is faltering... I will probably able to fix this problem when I update the codes for hardware management, but that would take weeks, if not months.

[UnclWish]

What about Pitcairns low speed in 1.1.2?
Why Pitcairn sensors didn't work?
And why enabled Pitcairn card disables hardware sensors on all cards.

Please see my post above. Problems with sensors are actually driver problems, and there is not much I can do about it at this point. Sadly, it seems that AMD's support for GCN1 cards is faltering... I will probably able to fix this problem when I update the codes for hardware management, but that would take weeks, if not months.

Understand. Sensors can wait. Please check the speed issue on Pitcairns with 1.1.2.

[zawawa]

What about Pitcairns low speed in 1.1.2?
Why Pitcairn sensors didn't work?
And why enabled Pitcairn card disables hardware sensors on all cards.

Please see my post above. Problems with sensors are actually driver problems, and there is not much I can do about it at this point. Sadly, it seems that AMD's support for GCN1 cards is faltering... I will probably able to fix this problem when I update the codes for hardware management, but that would take weeks, if not months.

Understand. Sensors can wait. Please check the speed issue on Pitcairns with 1.1.2.

I suggested in a post above that you should check the number of threads.

[zawawa]

On a more general note, support for GCN1 cards is sketchy at best as AMD's OpenCL drivers behave very differently with these cards. I will get to this issue eventually, but my current priority is to implement all the relevant algorithms for more recent cards.

[UnclWish]

What about Pitcairns low speed in 1.1.2?
Why Pitcairn sensors didn't work?
And why enabled Pitcairn card disables hardware sensors on all cards.

Please see my post above. Problems with sensors are actually driver problems, and there is not much I can do about it at this point. Sadly, it seems that AMD's support for GCN1 cards is faltering... I will probably able to fix this problem when I update the codes for hardware management, but that would take weeks, if not months.

Understand. Sensors can wait. Please check the speed issue on Pitcairns with 1.1.2.

I suggested in a post above that you should check the number of threads.

I tried 1 thread, but it gives even lower speed than 2...
I will try more...