TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI

[Shaddyr]

time to time i have an error on different PC. Miner lost connection to the main server and loop. Just doing nothing writing "lost connection to .." at console forever. Restarting fix error but it repeat later.
OS - win 8 or win 8.1
TT ver - 2.2.1

[1715029898]

1715029898

[1715029898]

1715029898

[TrailingStop]

time to time i have an error on different PC. Miner lost connection to the main server and loop. Just doing nothing writing "lost connection to .." at console forever. Restarting fix error but it repeat later.
OS - win 8 or win 8.1
TT ver - 2.2.1

like this one?
https://imgur.com/9JX4eRs

[TrailingStop]

time to time i have an error on different PC. Miner lost connection to the main server and loop. Just doing nothing writing "lost connection to .." at console forever. Restarting fix error but it repeat later.
OS - win 8 or win 8.1
TT ver - 2.2.1

like this one?
https://imgur.com/9JX4eRs


Can you try to run the miner, then remove the network-cable, plug it in again and let me know if the miner was able to reconnect please?

[TrailingStop]

hi, thats is the problem i mention about

https://imgur.com/9JX4eRs

Hi,

Can you try to run the miner, then remove the network-cable, plug it in again and let me know if the miner was able to reconnect please?
Thanks.

[Shaddyr]

hi, thats is the problem i mention about

https://imgur.com/9JX4eRs

Hi,

Can you try to run the miner, then remove the network-cable, plug it in again and let me know if the miner was able to reconnect please?
Thanks.

I did it. Miner wrote "connection lost" and hang) It did't repeat the error, my card still hot too. After network connected back nothing changed.

[stolarzz]

i understand, thing is my rig has higher average hashrates on mintpond using older 2.1.19 build with intesnity 20 and gridsize 4096 on all 5 GPU, with later builds it has intensity 15 and grid sizes are 7000+ for GTX1080Ti and 5000+ for GTX1080 but i don's see any hashrates improvements in 24 hour period, difference is around 1mh/sec daily average 16mh.sec+ VS 15mh.sec on newer builds, so maybe better to use older build at the moment with lower default gridsize, miner hashrates itself are more or less same with both builds

That's correct, older version reports better hashrate on poolside, it's about 3-4% in my case.

[solotrade]

hi, thats is the problem i mention about

https://imgur.com/9JX4eRs

Does it work again if you restart the miner?

yes, but is tired to check almost every single moment since the miner is not stable.

[TrailingStop]

Hey Trailing,

on MTP your miner atm is the fastest on GTX cards, but have some problems on mixed rigs with 1070/1080 cards, dunno why.

But on RTX cards your miner is much slower than your competitor. Are there any more improvements possible?

Hi,

did you try to 'play' around with intensity or grid size. You can set these values for each gpu separate. Please try this for the RTX as well - if you haven't tried it yet. Unfortunately I do not have a RTX available and cannot run my own test, but maybe someone from the community can help - or give me some more information what the problem could be???

Thanks.

>>>You can set these values for each gpu separate
Either but not both, this case will not work: -d 0,1,2 -i 15,16,17
You can't have both -d & -i at the command line.  Can you fix that?

Hi, is the bug fixed in the version I sent you?
Please let me know.

Thanks

[TrailingStop]

hi, thats is the problem i mention about

https://imgur.com/9JX4eRs

Hi,

please run this beta with the command line option -logpool and -log. I have added some more debug information that might help me to find out what's going on on your system. I tried a lot, but I could not reproduce it here on my Win10 systems.

https://TradeProject.de/download/Miner/TT-Miner-2.2.2-beta1.zip

If you see the bug, please stop the miner and send me the logfiles.

Thanks for your support.

[TrailingStop]

I noticed that miner doesn't stop mining threads when connection to pool stratum is lost, it's tries to reconnect but until then mining is not not suspended.
This is ok when disconnects are short, but when they are longer this is bad.

Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.

Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.

Hi,

thanks for your report.- I'm working on this issue already. You can specify a backup/fail-over pool until I found the bug and release a fix. Finding the sweet-spot for gridsize is somewhat tricky since all high values are very close together. I made the experience that from a certain value for gs the hash-rates starts high, but continue to drop  the shortly after.

Thanks for your support.

[EdgeOfSanity]

i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.

[TrailingStop]

i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.

Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?

[EdgeOfSanity]

i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.

Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?

I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.

[TrailingStop]

i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.

Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?

I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.

Hi- sorry, my bad. it should read 127.0.0.1 for localhost. Let me know if that works. I can add 0.0.0.0 to be localhost for a future release.

[EdgeOfSanity]

i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.

Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?

I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.

Hi- sorry, my bad. it should read 127.0.0.1 for localhost. Let me know if that works. I can add 0.0.0.0 to be localhost for a future release.

That unfortunately doesn't get it to work with localhost, however i got it running by pointing the software at 127.0.0.1:4068 I'm going to switch all my rigs over today, thanks for the help.

[hogwash.89m]

I noticed that miner doesn't stop mining threads when connection to pool stratum is lost, it's tries to reconnect but until then mining is not not suspended.
This is ok when disconnects are short, but when they are longer this is bad.

Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.

Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.

Hi,

thanks for your report.- I'm working on this issue already. You can specify a backup/fail-over pool until I found the bug and release a fix. Finding the sweet-spot for gridsize is somewhat tricky since all high values are very close together. I made the experience that from a certain value for gs the hash-rates starts high, but continue to drop  the shortly after.

Thanks for your support.

Hi I specified failover pool, that's working fine.

But I mean that when Internet connection is cut to rig, like when ISP went down, or when you unplug LAN cable from rig (to simulate loss of connectivity).
Miner just show that connection to stratum is lost and whole time Power Consumption/GPU Usage is same like mining regulary, but now is wasting power.
I wouldn't notice this flaw if my ISP didn't started having problems recent days, but they fixed their network infrastructure after few days.

[george2019]

i'm testing TT-Miner-2.2.2-beta2 and see some gridsize changes with default intensity, now it starts from lower gridsize and increasing little by little, also there's blocksize as well:

https://i.imgur.com/Fxs75ac.png

[The Cryptophilanthropist]

Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations?  The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already

[TrailingStop]

i'm testing TT-Miner-2.2.2-beta2 and see some gridsize changes with default intensity, now it starts from lower gridsize and increasing little by little, also there's blocksize as well:

https://i.imgur.com/Fxs75ac.png

Hi
- yes, this is one of the new function for the new release that comes with some fixes for re connection. If you do not specify a value for intensity and grid size TT-Miner will try to find the best setting. Depending on the algo this process may take up to 60 minutes. The miner have to wait for stable hash rates first before it can continue with the next value set. Let me know if that works for you.

[TrailingStop]

Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations?  The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already

Hi,

yes I heard about the Win7 performance lack. If my memory serves me right this is an issue that all miners for MTP shows - but I'm not sure about that? I think it is a Windows 7 issue. Maybe you can give a different miner a try and let me know iof it works well performance wise on your system. I will then check if I find some Windows 7 relates issues.

So please let me know.

Thanks for reporting.

P.S. Nice profile picture!