Author

Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 117. (Read 214431 times)

legendary
Activity: 1504
Merit: 1002
@zawawa - is dual mining of lbry active now on nvidia pascal cards?
sr. member
Activity: 1484
Merit: 253
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...

Did you update the display driver recently?
Besides the default number of threads, there shouldn't be any differences between 1.1.1 and 1.1.2 in terms of the CryptoNight kernel.
Yes. Driver 17.11.4 beta. In 1.1.1 with 2 threads about 495 h/s. In 1.1.2 with the same settings and driver about 400. 1 thread gives 325-350 h/s.
I will check it again right now...

P.S. On RX 580 with 2 threads on 1.1.2 speed the same as in 1.1.1. Default # of threads from 2 to 1 not for all cards?
sr. member
Activity: 728
Merit: 304
Miner Developer
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...

Did you update the display driver recently?
Besides the default number of threads, there shouldn't be any differences between 1.1.1 and 1.1.2 in terms of the CryptoNight kernel.
sr. member
Activity: 1484
Merit: 253
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...
sr. member
Activity: 728
Merit: 304
Miner Developer
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.
sr. member
Activity: 728
Merit: 304
Miner Developer
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.
sr. member
Activity: 1484
Merit: 253
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.
sr. member
Activity: 728
Merit: 304
Miner Developer
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.
sr. member
Activity: 1484
Merit: 253
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.
sr. member
Activity: 728
Merit: 304
Miner Developer
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...
sr. member
Activity: 728
Merit: 304
Miner Developer
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.
member
Activity: 140
Merit: 10
★777Coin.com★ Fun BTC Casino!
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.  Wink

That was quite quick, thanks!
sr. member
Activity: 1484
Merit: 253
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.  Wink
Good! Now can you take a little look into Pitcairns cryptonight issuie in 1.1.2?
sr. member
Activity: 728
Merit: 304
Miner Developer
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.  Wink
sr. member
Activity: 728
Merit: 304
Miner Developer
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.
member
Activity: 140
Merit: 10
★777Coin.com★ Fun BTC Casino!
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.
sr. member
Activity: 1484
Merit: 253
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.
sr. member
Activity: 728
Merit: 304
Miner Developer
I will look into other issues once I'm done with dual-mining with Pascal. No worries.
member
Activity: 102
Merit: 11
Is it not possible to create a regular ".exe" file, instead of setup installer each time.
sr. member
Activity: 1484
Merit: 253
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.
Jump to: