TrailingStop (OP)
Member
 Offline
Activity: 566
Merit: 16
|
 |
May 24, 2019, 04:36:04 AM |
|
It looks like the 2.2.4 fixes the issues from 2.2.3 so I was able to upgrade from 2.2.2 - great work man! 2 Questions: what is the default intensity? And can you explain how the hash report to the pool works with -rate? What does that effectively do? Does that affect how much the rate attribution to the miner is?
Thanks
Dan
Hi, happy to hear if things work  The default intensity is calculated and differs from card to card. You should see at start something like this: 06:26:58 Miner: GPU[0] use default intensity 12, Gridsize: 275 06:26:58 Miner: GPU[0] uses Gridsize: 275 and Blocksize: 448 so you get all information. The calculation is made after the algo is send to the gpu. For newer ProgPoW algos you can see this information whenever the algo changes. After 50 blocks. -rate send the miner hashrate to the pool so that it can compare the hashrate from miner & from pool side. You can see this on ethermine.org - they support -rate! Let me know if you have more questions - happy to help. |
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
dkmontague
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 24, 2019, 07:26:26 AM |
|
It looks like the 2.2.4 fixes the issues from 2.2.3 so I was able to upgrade from 2.2.2 - great work man! 2 Questions: what is the default intensity? And can you explain how the hash report to the pool works with -rate? What does that effectively do? Does that affect how much the rate attribution to the miner is?
Thanks
Dan
Hi, happy to hear if things work The default intensity is calculated and differs from card to card. You should see at start something like this: 06:26:58 Miner: GPU[0] use default intensity 12, Gridsize: 275 06:26:58 Miner: GPU[0] uses Gridsize: 275 and Blocksize: 448 so you get all information. The calculation is made after the algo is send to the gpu. For newer ProgPoW algos you can see this information whenever the algo changes. After 50 blocks. -rate send the miner hashrate to the pool so that it can compare the hashrate from miner & from pool side. You can see this on ethermine.org - they support -rate! Let me know if you have more questions - happy to help. I thought it was fixed but unfortunately it looks like it still suffers from the same issues as 2.2.3 with slower speed and higher rejected shares  2.2.0 is still the best for me. . I dont think I am the only one either, as zergpool shows most miners as using version 2.2.0. You must have changed something going forward from there man ....do you know what is causing this? If you went back to however it was structured back in 2.2.0 and then added your other fixes/features you'd probably get a lot more people using the miner (more dev fee for you) |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 24, 2019, 07:32:32 AM |
|
It looks like the 2.2.4 fixes the issues from 2.2.3 so I was able to upgrade from 2.2.2 - great work man! 2 Questions: what is the default intensity? And can you explain how the hash report to the pool works with -rate? What does that effectively do? Does that affect how much the rate attribution to the miner is?
Thanks
Dan
Hi, happy to hear if things work The default intensity is calculated and differs from card to card. You should see at start something like this: 06:26:58 Miner: GPU[0] use default intensity 12, Gridsize: 275 06:26:58 Miner: GPU[0] uses Gridsize: 275 and Blocksize: 448 so you get all information. The calculation is made after the algo is send to the gpu. For newer ProgPoW algos you can see this information whenever the algo changes. After 50 blocks. -rate send the miner hashrate to the pool so that it can compare the hashrate from miner & from pool side. You can see this on ethermine.org - they support -rate! Let me know if you have more questions - happy to help. I thought it was fixed but unfortunately it looks like it still suffers from the same issues as 2.2.3 with slower speed and higher rejected shares 2.2.0 is still the best for me. . I dont think I am the only one either, as zergpool shows most miners as using version 2.2.0. You must have changed something going forward from there man ....do you know what is causing this? If you went back to however it was structured back in 2.2.0 and then added your other fixes/features you'd probably get a lot more people using the miner (more dev fee for you) I guess you are on MTP and zergpool? |
|
|
|
|
dkmontague
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 24, 2019, 09:07:27 PM |
|
It looks like the 2.2.4 fixes the issues from 2.2.3 so I was able to upgrade from 2.2.2 - great work man! 2 Questions: what is the default intensity? And can you explain how the hash report to the pool works with -rate? What does that effectively do? Does that affect how much the rate attribution to the miner is?
Thanks
Dan
Hi, happy to hear if things work The default intensity is calculated and differs from card to card. You should see at start something like this: 06:26:58 Miner: GPU[0] use default intensity 12, Gridsize: 275 06:26:58 Miner: GPU[0] uses Gridsize: 275 and Blocksize: 448 so you get all information. The calculation is made after the algo is send to the gpu. For newer ProgPoW algos you can see this information whenever the algo changes. After 50 blocks. -rate send the miner hashrate to the pool so that it can compare the hashrate from miner & from pool side. You can see this on ethermine.org - they support -rate! Let me know if you have more questions - happy to help. I thought it was fixed but unfortunately it looks like it still suffers from the same issues as 2.2.3 with slower speed and higher rejected shares 2.2.0 is still the best for me. . I dont think I am the only one either, as zergpool shows most miners as using version 2.2.0. You must have changed something going forward from there man ....do you know what is causing this? If you went back to however it was structured back in 2.2.0 and then added your other fixes/features you'd probably get a lot more people using the miner (more dev fee for you) I guess you are on MTP and zergpool? Nah I just look at zergpool to see what everyone is using. I just mine XZC MTP at mintpond |
|
|
|
|
dannyprats
Member
Offline
Activity: 132
Merit: 10
|
|
May 24, 2019, 10:11:42 PM |
|
Hello folks..
Does this miner work for ProgPow?
when Claymore ProgPow miner?
Yes it does - check your revision you need, depending on the coin you want to mine: 1. ProgPoW for BCI (BitcoinInterest) 2. ProgPoWz for Zano 3. progPoWH for HORA 4. ProgPoW Rev. 0.9.2 for SUN (Solidum) any plans for support AMD devices in the future? |
|
|
|
|
YAOZHENG
Newbie
Offline
Activity: 7
Merit: 0
|
|
May 24, 2019, 11:15:17 PM |
|
How should I use this software to mine HORA?
I am Windows10 always prompting me to drive the update?
|
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 24, 2019, 11:50:31 PM
Last edit: May 25, 2019, 05:38:54 AM by TrailingStop |
|
How should I use this software to mine HORA?
I am Windows10 always prompting me to drive the update?
You have a screenshot? Sounds like you need a newer nvidia driver. Please check. |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 25, 2019, 05:40:43 AM |
|
Hello folks..
Does this miner work for ProgPow?
when Claymore ProgPow miner?
Yes it does - check your revision you need, depending on the coin you want to mine: 1. ProgPoW for BCI (BitcoinInterest) 2. ProgPoWz for Zano 3. progPoWH for HORA 4. ProgPoW Rev. 0.9.2 for SUN (Solidum) any plans for support AMD devices in the future? Hi, not at the moment - sorry. I have Linux next on my list. Maybe later if there is some demand for AMD. |
|
|
|
|
|
|
|
|
crairezx20
Legendary
Offline
Activity: 1638
Merit: 1046
|
|
May 26, 2019, 12:54:50 PM
Last edit: May 26, 2019, 01:18:28 PM by crairezx20 |
|
Unable to access the site Timed out waiting for a response from the tradeproject.de site.  You will not access it if you just enter this tradeproject.de you should use the direct link from the first page to directly download the miner or try use awesomeminer so that you can mine anything you want and you can directly use TT-miner through awesomeminer. The good thing you can benchmark which miner is the best to mine with any different algos. |
|
|
|
|
Shaddyr
Jr. Member
Offline
Activity: 48
Merit: 2
|
|
May 27, 2019, 10:52:29 AM |
|
yesterday has updated version to 2.2.4. Today at 6:30 it stopped mining with cycle message "POOL: Unknown protocol - cannot continue". After close and restart works fine. Logs will be sended wia PM.
|
|
|
|
|
george2019
Jr. Member
Offline
Activity: 83
Merit: 3
|
|
May 28, 2019, 04:45:57 AM |
|
i have same error using both hora and zano coins, 2 days ago it was working fine but now both say unknown protocol both 2.2.4 and 2.2.5 beta1 versions
AM POOL: Unknown protocol - cannot continue
mtp algo working fine
|
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 28, 2019, 04:48:57 AM |
|
i have same error using both hora and zano coins, 2 days ago it was working fine but now both say uknown protocol both 2.2.4 and 2.2.5 beta1 versions
Yes- see the problem here. Will fix it if I'm back from work. Thanks both of you for reporting! |
|
|
|
|
Shaddyr
Jr. Member
Offline
Activity: 48
Merit: 2
|
|
May 28, 2019, 08:48:38 PM |
|
Again got UNKNOWN. Will wait for the fix)
|
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 29, 2019, 05:53:02 PM |
|
Version 2.2.5 release
- fix for Zano (please update if you see invalid shares)
- fix for mining to dwarfpool
New release with more fixed (reconnect issue) will come very soon.
Thanks.
|
|
|
|
|
WARMANGALAXY
Jr. Member
Offline
Activity: 69
Merit: 1
|
|
June 01, 2019, 12:01:37 PM |
|
Hello, and when to appear at least beta test linux version?
|
|
|
|
|
kondiomir
Legendary
Offline
Activity: 1568
Merit: 1000
Twitter @Acimirov
|
|
June 01, 2019, 01:56:42 PM |
|
CPU load stays at 100% with this miner on progpowz.
Is there a way to fix this?
|
|
|
|
|
cryptoyes
Member
Offline
Activity: 297
Merit: 10
|
|
June 03, 2019, 10:50:55 PM |
|
You list windows and linux driver versions for cuda in the op but the miner seems windows only ... is there a linux version or not?
|
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
June 04, 2019, 12:27:32 AM |
|
You list windows and linux driver versions for cuda in the op but the miner seems windows only ... is there a linux version or not?
There isn't ... Yet! #crysx |
|
|
|
|
