TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 36.

solotrade

newbie

Activity: 16

Merit: 0

Quote from: TrailingStop on April 21, 2019, 08:14:48 PM

Quote from: solotrade on April 21, 2019, 06:15:21 PM

hi, im really curious that gs does actually affect anything? Huh

gs defines together with the blocksize the number of threads to execute. Blocksize is calculated and you cannot change it.

hmm, still dont get it. it affect the lifespan of gpu or use more cpu & gpu resources with gs size?

TrailingStop

member

Activity: 566

Merit: 16

Quote from: solotrade on April 21, 2019, 06:15:21 PM

hi, im really curious that gs does actually affect anything? Huh

gs defines together with the blocksize the number of threads to execute. Blocksize is calculated and you cannot change it.

solotrade

newbie

Activity: 16

Merit: 0

hi, im really curious that gs does actually affect anything? Huh

Vivik

full member

Activity: 197

Merit: 100

Quote from: TrailingStop on April 21, 2019, 02:01:08 AM

Quote from: Vivik on April 20, 2019, 07:41:43 PM

Version 2.2.2 when installed by default works without problems on farm 8 card.

Hi,

thanks you for your info - can you please add some additional information like, GPUs, OS, RAM, Virtual memory settings etc?

OS: win10-x64
RAM: 32Gb
Virtual MEM: 32 GB

PL : 70%

TrailingStop

member

Activity: 566

Merit: 16

Quote from: Ngenah Euy on April 20, 2019, 01:47:16 AM

is it also work for ZANO (ProgPOWZ)? thanks

Hi,

Zano uses a different revision of ProgPoW. I will release a version within the next few days. Form my understanding they plan to go live with this algo at the end of April?

TrailingStop

member

Activity: 566

Merit: 16

Quote from: abudfv2008 on April 21, 2019, 01:58:56 AM

Quote from: TrailingStop on April 19, 2019, 01:43:45 PM

Quote from: abudfv2008 on April 19, 2019, 01:20:37 PM

Quote from: TrailingStop on April 19, 2019, 11:02:27 AM

Quote from: abudfv2008 on April 19, 2019, 10:39:38 AM

TrailingStop
Is there any way to disable Crashdump file creation?

No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened? Huh

Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.

Thank you - now mining with 2.2.3beta.
Can you add config file option, like other miners have? Length of cmd string is limited and I can't add 2-3 failover pools.

Ah- I never reached that limit. Will try to add something like this in the release after next.

Thanks for your suggestion!

TrailingStop

member

Activity: 566

Merit: 16

Quote from: Vivik on April 20, 2019, 07:41:43 PM

Version 2.2.2 when installed by default works without problems on farm 8 card.

Hi,

thanks you for your info - can you please add some additional information like, GPUs, OS, RAM, Virtual memory settings etc?

abudfv2008

full member

Activity: 728

Merit: 106

Quote from: TrailingStop on April 19, 2019, 01:43:45 PM

Quote from: abudfv2008 on April 19, 2019, 01:20:37 PM

Quote from: TrailingStop on April 19, 2019, 11:02:27 AM

Quote from: abudfv2008 on April 19, 2019, 10:39:38 AM

TrailingStop
Is there any way to disable Crashdump file creation?

No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened? Huh

Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.

Thank you - now mining with 2.2.3beta.
Can you add config file option, like other miners have? Length of cmd string is limited and I can't add 2-3 failover pools.

Vivik

full member

Activity: 197

Merit: 100

Version 2.2.2 when installed by default works without problems on farm 8 card.

Shaddyr

jr. member

Activity: 48

Merit: 2

One bug yet: miner don't report if one of the card had crashed. It continue to work with others but failed one is absent. And didn't notice anything about situation at console.

PS: have a CrashDump.dmp. Will send it to TS via PM.

TrailingStop

member

Activity: 566

Merit: 16

Quote from: johndoughtoo on April 20, 2019, 05:28:24 AM

Quote from: TrailingStop on April 19, 2019, 09:17:11 PM

Quote from: johndoughtoo on April 17, 2019, 08:09:25 AM

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!

Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.

That only works in managed miner mode (having the awesome miner software installed directly on each of the miner systems directly)
I do not use any "managed" miners - they are all external miners. And the only way to monitor an external miner is with the API.
Thank you for the info and option, If i install AM on the miner itself, this would be VERY HELPFUL.

Hi,

I will try to find a better solution for you.

johndoughtoo

newbie

Activity: 4

Merit: 0

Quote from: TrailingStop on April 19, 2019, 09:17:11 PM

Quote from: johndoughtoo on April 17, 2019, 08:09:25 AM

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!

Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.

That only works in managed miner mode (having the awesome miner software installed directly on each of the miner systems directly)
I do not use any "managed" miners - they are all external miners. And the only way to monitor an external miner is with the API.
Thank you for the info and option, If i install AM on the miner itself, this would be VERY HELPFUL.

TrailingStop

member

Activity: 566

Merit: 16

Quote from: Ngenah Euy on April 20, 2019, 01:47:16 AM

is it also work for ZANO (ProgPOWZ)? thanks

Do not know - will check. Will let you know later today.

Ngenah Euy

jr. member

Activity: 207

Merit: 5

is it also work for ZANO (ProgPOWZ)? thanks

TrailingStop

member

Activity: 566

Merit: 16

Quote from: johndoughtoo on April 17, 2019, 08:09:25 AM

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!

Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.

TrailingStop

member

Activity: 566

Merit: 16

Quote from: abudfv2008 on April 19, 2019, 01:20:37 PM

Quote from: TrailingStop on April 19, 2019, 11:02:27 AM

Quote from: abudfv2008 on April 19, 2019, 10:39:38 AM

TrailingStop
Is there any way to disable Crashdump file creation?

No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened? Huh

Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.

TrailingStop

member

Activity: 566

Merit: 16

Quote from: abudfv2008 on April 19, 2019, 01:20:37 PM

Quote from: TrailingStop on April 19, 2019, 11:02:27 AM

Quote from: abudfv2008 on April 19, 2019, 10:39:38 AM

TrailingStop
Is there any way to disable Crashdump file creation?

No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened? Huh

Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Got it. I compile you a beta without crashdump. If you can it would be great if you can DM me the crashdump anyway because I would like to fix any bugs that are in the miner. The crashdump would help me a lot to find a bug.

abudfv2008

full member

Activity: 728

Merit: 106

Quote from: TrailingStop on April 19, 2019, 11:02:27 AM

Quote from: abudfv2008 on April 19, 2019, 10:39:38 AM

TrailingStop
Is there any way to disable Crashdump file creation?

No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened? Huh

Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

TrailingStop

member

Activity: 566

Merit: 16

Quote from: Shivoreun on April 19, 2019, 12:12:45 PM

Quote from: TrailingStop on April 19, 2019, 09:37:02 AM

Quote from: Shivoreun on April 19, 2019, 09:20:40 AM

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.

Thanks for reply

Previously I was using 2.1.14 and there were no such problem Undecided

Didn't tested another older versions yet...
Then, what I should set in "-b" option to allow API requests from any address?.. Looks like, that regardless of the settings, the miner accepts only connections from locahost Sad

Hi,

the miner does not filter any addresses. It looks to me like you have 2 (or more) network interfaces and the API bind to the wrong. The address you use for the api command is to tell the miner which network interface to enable for api access. If you have only one localhost is fine, if you have more it makes sense to tell the miner which one to use. You can check your IPs with 'ipconfig -all' command in the console. Let me know if that help or if you still have problems to get connected.

Shivoreun

member

Activity: 130

Merit: 10

Quote from: TrailingStop on April 19, 2019, 09:37:02 AM

Quote from: Shivoreun on April 19, 2019, 09:20:40 AM

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.

Thanks for reply

Previously I was using 2.1.14 and there were no such problem Undecided

Didn't tested another older versions yet...
Then, what I should set in "-b" option to allow API requests from any address?.. Looks like, that regardless of the settings, the miner accepts only connections from locahost Sad

Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 36. (Read 132169 times)