Pages:
Author

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

member
Activity: 566
Merit: 16
_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131


Does an older version of TT work with NH? Can you try different pool - just to test please?
member
Activity: 566
Merit: 16
_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131


Let me check...
newbie
Activity: 40
Merit: 0
_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131
newbie
Activity: 40
Merit: 0
06:42:04.047 <- {"id":null,"method":"mining.notify","params":["00000206b3302574","d5de1142e363afff19fe147d2f3f1873c8544323eee14d3143f821256f95a660","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff360358750204e06dd65c08","1b324d696e6572732068747470733a2f2f326d696e6572732e636f6dffffffff07004e725300000 0001976a91455154ec4385f71c4a284731cafaf5d19406c030588ac8017b42c000000001976a914 e9d8e0514c1e74a0499018ae2dd5e64dff59eb1b88ac80f0fa02000000001976a9147d9ed014fc4 e603fca7c2e3f9097fb7d0fb487fc88ac80f0fa02000000001976a914bc7e5a5234db3ab82d74c3 96ad2b2af419b7517488ac80f0fa02000000001976a914ff71b0c9c2a90c6164a50a2fb523eb54a 8a6b55088ac80d1f008000000001976a9140654dd9b856f2ece1d56cb4ee5043cd9398d962c88ac 80f0fa02000000001976a9140b4bfb256ef4bfa360e3b9e66e53a0bd84d196bc88ac00000000",[],"00100020","d1050a1b","e06dd65c",true]}
06:42:04.282 <- {"id":3,"result":true,"error":null}
09:42:13.791 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:42:13.791 Disconnected
06:42:16.808 -> {"id":1,"method":"mining.subscribe","params":["TT-Miner/2.2.3"]}
09:42:16.808 SOCKET: Error connected(0) / _NetworkInterfaceSocket::_CommunicationLoop:615
06:42:17.240 <- {"id":1,"result":["e5ec5fec2d6294286a4a95682319abd2","0100000000005e92da"],"error":null}
06:42:17.240 -> {"id":2,"method":"mining.authorize","params":["32BKFGN2THJKCUxCkUmEfZ8khU.RIG1070","x"]}
06:42:17.458 <- {"id":2,"result":true,"error":null}
06:42:17.458 -> {"id":3,"method":"mining.extranonce.subscribe","params":[]}
06:42:17.475 <- {"id":null,"method":"mining.set_target","params":["0000000000000000000000000000000000000000000000000000f0ff0f000000"]}
newbie
Activity: 40
Merit: 0
TT-Miner.exe -A MTP-101 -P 32BKFGN2THJKZQ3xCkUmEfZ8khU.RIG1070:[email protected]:3374 -logpool
member
Activity: 566
Merit: 16
member
Activity: 566
Merit: 16
How I can mine on nicehash? I get an error that miner lost connection.

MTP? Ethash?
newbie
Activity: 40
Merit: 0
How I can mine on nicehash? I get an error that miner lost connection.
newbie
Activity: 15
Merit: 0
Just click the "Map to system monitoring" and mark "Display system monitoring data in the GPU tab". Problem solved  Wink

Thaaaanx bro you saved my day! Smiley
member
Activity: 130
Merit: 10
New version 2.2.3 release.

These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.

- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.

Happy mining!


And still no fix for API, not accessible anywhere, except localhost Sad
member
Activity: 418
Merit: 21
Just click the "Map to system monitoring" and mark "Display system monitoring data in the GPU tab". Problem solved  Wink
newbie
Activity: 15
Merit: 0
New version 2.2.3 release.

These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.

- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.

Happy mining!


thanks for new version.

Just want to report that this
Code:
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
is still not working for me on Awesome Miner 6.3.4 mining MTP (picture below , power usage should be showing under clocking).
Also would be nice that it could pass clocking info to Awesome Miner.

https://i.imgur.com/uFGKU7Q.jpg
member
Activity: 566
Merit: 16
v.2.2.3
single 1070Ti didn't like the version - screen attached. With the same settings v2.2.2 works fine. But 3x1066 agreied to work with no errors.

Hi,

I change the mining code to get some more hashes. It could be that OC settings that works with older version doesn't work now. I see that you have some accepted and some rejected shares. You have no rejected shares with 1660?

jr. member
Activity: 48
Merit: 2
v.2.2.3
single 1070Ti didn't like the version - screen attached. With the same settings v2.2.2 works fine. But 3x1066 agreied to work with no errors.
http://images.vfl.ru/ii/1557484566/5624cb2c/26482989.jpg

legendary
Activity: 3164
Merit: 1003



How can I display the individual hashrate of each card?

Hi,

not sure what you mean exactly? If you run TT you should see after some seconds something like this>

06:34:45 GPU[0]: 13.195 MH/s  CClk:1.354 GHz MClk:1.307 GHz 62C 76% 125W 105.56 kH/W [A540:R0 0.0%]  LastShare: 00:00:04
06:34:45 GPU[1]: 12.656 MH/s  CClk:1.759 GHz MClk:3.898 GHz 69C 55% 152W 83.263 kH/W [A482:R0 0.0%]  LastShare: 00:00:04
06:34:45 Rig-Speed[2 min]: 25.851 MH/s 277W 93.323 kH/W [A1022:R0 0.0%] Uptime: 05:04:36  LastShare: 00:00:04
06:34:45 Luck: avg.time per share (424.19 MH @ 25.851 MH/s) 17 secs. passed 4 secs. luck share: 27% session: 99%

The first number after GPU[0] and GPU[1] is the hashrate for that card. Please clarify is this is not what you are locking for.

Thanks.

I'm sorry..I should have said the name of each card.. like GPU[0]gtx 1080..or GPU[1]gtx 2080..ect.

Like this picture.







Hi,

ah - got it. I will make that as an option since many ppl have the same GPU in a rig and this information is just a wast of space in that case.




Thank you.  Yes to make that an option would be great.  Smiley
member
Activity: 566
Merit: 16



How can I display the individual hashrate of each card?

Hi,

not sure what you mean exactly? If you run TT you should see after some seconds something like this>

06:34:45 GPU[0]: 13.195 MH/s  CClk:1.354 GHz MClk:1.307 GHz 62C 76% 125W 105.56 kH/W [A540:R0 0.0%]  LastShare: 00:00:04
06:34:45 GPU[1]: 12.656 MH/s  CClk:1.759 GHz MClk:3.898 GHz 69C 55% 152W 83.263 kH/W [A482:R0 0.0%]  LastShare: 00:00:04
06:34:45 Rig-Speed[2 min]: 25.851 MH/s 277W 93.323 kH/W [A1022:R0 0.0%] Uptime: 05:04:36  LastShare: 00:00:04
06:34:45 Luck: avg.time per share (424.19 MH @ 25.851 MH/s) 17 secs. passed 4 secs. luck share: 27% session: 99%

The first number after GPU[0] and GPU[1] is the hashrate for that card. Please clarify is this is not what you are locking for.

Thanks.

I'm sorry..I should have said the name of each card.. like GPU[0]gtx 1080..or GPU[1]gtx 2080..ect.

Like this picture.







Hi,

ah - got it. I will make that as an option since many ppl have the same GPU in a rig and this information is just a wast of space in that case.


legendary
Activity: 3164
Merit: 1003



How can I display the individual hashrate of each card?

Hi,

not sure what you mean exactly? If you run TT you should see after some seconds something like this>

06:34:45 GPU[0]: 13.195 MH/s  CClk:1.354 GHz MClk:1.307 GHz 62C 76% 125W 105.56 kH/W [A540:R0 0.0%]  LastShare: 00:00:04
06:34:45 GPU[1]: 12.656 MH/s  CClk:1.759 GHz MClk:3.898 GHz 69C 55% 152W 83.263 kH/W [A482:R0 0.0%]  LastShare: 00:00:04
06:34:45 Rig-Speed[2 min]: 25.851 MH/s 277W 93.323 kH/W [A1022:R0 0.0%] Uptime: 05:04:36  LastShare: 00:00:04
06:34:45 Luck: avg.time per share (424.19 MH @ 25.851 MH/s) 17 secs. passed 4 secs. luck share: 27% session: 99%

The first number after GPU[0] and GPU[1] is the hashrate for that card. Please clarify is this is not what you are locking for.

Thanks.

I'm sorry..I should have said the name of each card.. like GPU[0]gtx 1080..or GPU[1]gtx 2080..ect.

Like this picture.





member
Activity: 566
Merit: 16
Refresh of the version 2.2.3.

Added the cuda 10.0 and cuda 9.2 version of ProgPoWZ for Zano and a small fix for fairpool.

Let me know if you have any issues.

Happy mining.
member
Activity: 566
Merit: 16
My cclk is default setting about 800. I want add cclk more around 1500. I do how?

Try MSI Afterburner and increase core clock.

I'm setting MSI afterburner +160 cc.

if you want to have 1500 you need to set cc to +700 - not sure if you will get a stable system with these settings. TT-Miner doesn't do any OC - so I cannot help much, sorry.
Pages:
Jump to: