Any possibility of getting Sero ProgPoW added to the list?
yes!!!!
Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 27. (Read 132207 times)
July 13, 2019, 07:55:52 AM
yes!!!!
July 12, 2019, 08:21:15 AM
Any possibility of getting Sero ProgPoW added to the list?
July 11, 2019, 12:07:53 PM
Hi, I'm rewriting most of the miner at the moment to get it ready for linux as well. so with this rewrite a new communication layer will come, I will address this issue as well for this version.
We are very much looking forward to the Linux version, and especially the appearance of the TT-Miner in HIVE OS
July 09, 2019, 02:59:32 PM
Hi, I'm rewriting most of the miner at the moment to get it ready for linux as well. so with this rewrite a new communication layer will come, I will address this issue as well for this version.
We are very much looking forward to the Linux version, and especially the appearance of the TT-Miner in HIVE OS
July 08, 2019, 12:08:37 PM
anonce from 2.2.5
"A new full release with more fixes will follow very soon"
Realy? How soon? Half of year? Some years?
"A new full release with more fixes will follow very soon"
Realy? How soon? Half of year? Some years?
July 08, 2019, 09:19:52 AM
TT-Miner 2.2.5 vs Phoenix Miner 4.2c
1. Hash rate (winner=TT-Miner 2.2.5)
2. Accepted shares (winner=Phoenix Miner 4.2c)
3. Rejected shares (winner=Phoenix Miner 4.2c=NONE)
4. Dev fee (winner=Phoenix Miner 4.2c=0.65%)
1. Hash rate (winner=TT-Miner 2.2.5)
2. Accepted shares (winner=Phoenix Miner 4.2c)
3. Rejected shares (winner=Phoenix Miner 4.2c=NONE)
4. Dev fee (winner=Phoenix Miner 4.2c=0.65%)
July 04, 2019, 10:17:53 AM
It has been over a month since you promised a quick fix for the connection issue and you've been largely absent from this board during that time. When the miner can't connect I lose hours of mining. This must be fixed immediately or I will use a different miner...we shouldn't have to wait for the miner to be rewritten. Using a slightly slower miner is going to make more money in the long term because it will actually work. The issue seems to be in protocol detection. Here are logs from this morning using v2.2.5.
When it is broken, it detects "EthProxy-Stratum" instead of "Stratum" (the last four lines repeated for an hour and a half before I noticed it):
When it works correctly:
When it is broken, it detects "EthProxy-Stratum" instead of "Stratum" (the last four lines repeated for an hour and a half before I noticed it):
8:16:42 AM POOL: Connecting to mtp.usa.nicehash.com:3374 - PoolID: 0
8:16:42 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol Stratum
8:16:43 AM Miner: GPU[0] use default intensity 14, Gridsize: 2560
8:16:43 AM Miner: GPU[0] uses Gridsize: 2560 and Blocksize: 256
8:16:46 AM POOL: Unknown protocol - cannot continue
8:16:46 AM POOL: Subscribed to mtp.usa.nicehash.com:3374 - detected protocol: EthProxy-Stratum
8:16:46 AM POOL: Worker authorized: worker1
8:16:46 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 66C 59% 49W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:16:46 AM Rig-Speed[2 min]: 0.000 H/s 49W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:04 LastShare: -
8:17:00 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 62C 58% 49W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:17:00 AM Rig-Speed[2 min]: 0.000 H/s 49W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:17 LastShare: -
8:17:15 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 59C 55% 47W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:17:15 AM Rig-Speed[2 min]: 0.000 H/s 47W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:32 LastShare: -
8:17:16 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:16 AM POOL: Mining temporary stopped
8:17:19 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:19 AM POOL: Mining resumed
8:17:19 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:19 AM POOL: Mining temporary stopped
8:17:22 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:22 AM POOL: Mining resumed
8:17:22 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:22 AM POOL: Mining temporary stopped
8:17:25 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:25 AM POOL: Mining resumed
When it works correctly:
9:48:33 AM POOL: Connecting to mtp.usa.nicehash.com:3374 - PoolID: 0
9:48:33 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol Stratum
9:48:33 AM POOL: Subscribed to mtp.usa.nicehash.com:3374 - detected protocol: Stratum
9:48:33 AM POOL: Worker authorized: worker1
9:48:33 AM POOL: Received new job#: 233c184868a
9:48:34 AM Miner: GPU[0] use default intensity 14, Gridsize: 2560
9:48:34 AM Miner: GPU[0] uses Gridsize: 2560 and Blocksize: 256
9:48:34 AM POOL: difficulty up from 0.000 H to 268.44 MH
9:48:36 AM GPU[0]: *Merkle tree created in 0.5 seconds
Hi,
please try this to avoid protocol detection:
TT-Miner.exe -A MTP -log -luck -logpool -P stratum+tcp://
Sorry for the delay.
July 04, 2019, 10:01:56 AM
It has been over a month since you promised a quick fix for the connection issue and you've been largely absent from this board during that time. When the miner can't connect I lose hours of mining. This must be fixed immediately or I will use a different miner...we shouldn't have to wait for the miner to be rewritten. Using a slightly slower miner is going to make more money in the long term because it will actually work. The issue seems to be in protocol detection. Here are logs from this morning using v2.2.5.
When it is broken, it detects "EthProxy-Stratum" instead of "Stratum" (the last four lines repeated for an hour and a half before I noticed it):
When it works correctly:
When it is broken, it detects "EthProxy-Stratum" instead of "Stratum" (the last four lines repeated for an hour and a half before I noticed it):
8:16:42 AM POOL: Connecting to mtp.usa.nicehash.com:3374 - PoolID: 0
8:16:42 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol Stratum
8:16:43 AM Miner: GPU[0] use default intensity 14, Gridsize: 2560
8:16:43 AM Miner: GPU[0] uses Gridsize: 2560 and Blocksize: 256
8:16:46 AM POOL: Unknown protocol - cannot continue
8:16:46 AM POOL: Subscribed to mtp.usa.nicehash.com:3374 - detected protocol: EthProxy-Stratum
8:16:46 AM POOL: Worker authorized: worker1
8:16:46 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 66C 59% 49W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:16:46 AM Rig-Speed[2 min]: 0.000 H/s 49W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:04 LastShare: -
8:17:00 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 62C 58% 49W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:17:00 AM Rig-Speed[2 min]: 0.000 H/s 49W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:17 LastShare: -
8:17:15 AM GPU[0]: 0.000 H/s CClk:1.695 GHz MClk:218.03 MHz 59C 55% 47W 0.000 H/W [A0:R0 0.0%] LastShare: -
8:17:15 AM Rig-Speed[2 min]: 0.000 H/s 47W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:32 LastShare: -
8:17:16 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:16 AM POOL: Mining temporary stopped
8:17:19 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:19 AM POOL: Mining resumed
8:17:19 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:19 AM POOL: Mining temporary stopped
8:17:22 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:22 AM POOL: Mining resumed
8:17:22 AM POOL: Lost connection to mtp.usa.nicehash.com:3374
8:17:22 AM POOL: Mining temporary stopped
8:17:25 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol EthProxy-Stratum
8:17:25 AM POOL: Mining resumed
When it works correctly:
9:48:33 AM POOL: Connecting to mtp.usa.nicehash.com:3374 - PoolID: 0
9:48:33 AM POOL: Connected to: mtp.usa.nicehash.com:3374 - IP4: 172.65.221.202:3374, Protocol Stratum
9:48:33 AM POOL: Subscribed to mtp.usa.nicehash.com:3374 - detected protocol: Stratum
9:48:33 AM POOL: Worker authorized: worker1
9:48:33 AM POOL: Received new job#: 233c184868a
9:48:34 AM Miner: GPU[0] use default intensity 14, Gridsize: 2560
9:48:34 AM Miner: GPU[0] uses Gridsize: 2560 and Blocksize: 256
9:48:34 AM POOL: difficulty up from 0.000 H to 268.44 MH
9:48:36 AM GPU[0]: *Merkle tree created in 0.5 seconds
July 04, 2019, 03:11:12 AM
Hi
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
This is long time ago many times reported, but still no answer and no repair of this bug
I am not able to use this excavator with my rigs (1070, 1070Ti, 2070) - doesnt matter what card.
Hi, I'm rewriting most of the miner at the moment to get it ready for linux as well. so with this rewrite a new communication layer will come, I will address this issue as well for this version.
July 04, 2019, 03:05:16 AM
Hi
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
This is long time ago many times reported, but still no answer and no repair of this bug
I am not able to use this excavator with my rigs (1070, 1070Ti, 2070) - doesnt matter what card.
July 03, 2019, 11:47:25 AM
Quote
did you make a clean install? and removed the old version first?
of course. to a new directory. win10 64
(sorry, but 1 PM per 24 hour)
July 02, 2019, 01:37:23 AM
Hello,
Can you make progpow compatible with 'super sero' plz?
Thanks
Can you make progpow compatible with 'super sero' plz?
Thanks
July 01, 2019, 11:42:24 AM
me too
July 01, 2019, 08:39:22 AM
Hi
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
June 30, 2019, 07:07:55 AM
not interested in testing ccminer ? currently faster than those (or very close to t-rex)
Which one DJM? ...
Has been a long time since I have seen you here on BCT. Rune hasn't come back with a mouthful of crap to spark anyone up as far as I can see, so I guess that must be it
TTMiner is superb at the moment, though waiting on the Linux version to become ready for use for us to trial it. What link is the one you are talking about? Your one? Do you have the link available?
#crysx
June 30, 2019, 06:42:56 AM
Hi TrailingStop,
I can't increase insensitive more then 14
Rig with 6*1080ti, Virtual memory tried with 64Gb up to 160Gb - no luck
installed memory 4G, tried to put 8Gb, but same result
How to increase an insensitive, any ideas?
I can't increase insensitive more then 14
Rig with 6*1080ti, Virtual memory tried with 64Gb up to 160Gb - no luck
installed memory 4G, tried to put 8Gb, but same result
How to increase an insensitive, any ideas?
June 28, 2019, 02:26:33 PM
not interested in testing ccminer ? currently faster than those (or very close to t-rex)
June 28, 2019, 02:00:28 PM
June 26, 2019, 01:24:47 PM
Hi
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
I use TT-Miner 2.2.5
thank you for the fine program!
several rig at the same time work for me
approximately once a day some of rig ceases to connect to the server and ceases to mine
it is enough to restart NiceHashMinerLegasy, and then mining of zany begins to work.
if just to restart TT-Miner, a problem and remains
https://drive.google.com/open?id=1mu4H9SYFbgDd_VnpqVEU4QqQc9fCw9-5
June 25, 2019, 03:43:03 AM
Yes you can pm me, I will test it. Tnx.
Jump to: