Bitcoin Forum
November 07, 2024, 05:58:48 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 [36] 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
Author Topic: TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI  (Read 132176 times)
tbearhere
Legendary
*
Offline Offline

Activity: 3206
Merit: 1003



View Profile
May 09, 2019, 02:42:39 AM
 #701




How can I display the individual hashrate of each card?
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 04:39:34 AM
 #702




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.
danspasiva
Full Member
***
Offline Offline

Activity: 417
Merit: 105


View Profile
May 09, 2019, 04:49:25 AM
 #703




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.

Hello, for some reason this miner will not start as it says "connected to pool xxxxxxxxxxxx" and then it says "lost connection to pool xxxxxxxxxxx" over and over and never starts, the same pool works well with a different software
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 05:01:46 AM
 #704




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.

can you please show me your command line? Let me check if there is an issue - could also be a problem in the miner if the pools uses some command the miner do not know.



Hello, for some reason this miner will not start as it says "connected to pool xxxxxxxxxxxx" and then it says "lost connection to pool xxxxxxxxxxx" over and over and never starts, the same pool works well with a different software
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 05:07:12 AM
 #705

My cclk is default setting about 800. I want add cclk more around 1500. I do how?

Try MSI Afterburner and increase core clock.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 05:40:59 AM
 #706

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.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 09:08:57 AM
 #707

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.
tbearhere
Legendary
*
Offline Offline

Activity: 3206
Merit: 1003



View Profile
May 09, 2019, 09:18:35 AM
Last edit: May 09, 2019, 09:49:07 AM by tbearhere
 #708




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.





TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 09, 2019, 11:28:15 AM
 #709




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.


tbearhere
Legendary
*
Offline Offline

Activity: 3206
Merit: 1003



View Profile
May 09, 2019, 02:03:18 PM
 #710




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
Shaddyr
Jr. Member
*
Offline Offline

Activity: 48
Merit: 2


View Profile
May 10, 2019, 10:37:57 AM
 #711

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.


TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 10, 2019, 11:04:24 AM
 #712

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?

c0mrade69
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
May 10, 2019, 06:04:38 PM
 #713

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
joseph32
Member
**
Offline Offline

Activity: 418
Merit: 21


View Profile
May 10, 2019, 07:30:43 PM
 #714

Just click the "Map to system monitoring" and mark "Display system monitoring data in the GPU tab". Problem solved  Wink
Shivoreun
Member
**
Offline Offline

Activity: 130
Merit: 10


View Profile
May 10, 2019, 10:10:09 PM
 #715

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

P.S. Sorry for errors in English - it's not my native language...
c0mrade69
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
May 11, 2019, 12:24:30 AM
 #716

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
gusknure
Newbie
*
Offline Offline

Activity: 40
Merit: 0


View Profile
May 11, 2019, 06:38:23 AM
 #717

How I can mine on nicehash? I get an error that miner lost connection.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 11, 2019, 06:40:02 AM
 #718

How I can mine on nicehash? I get an error that miner lost connection.

MTP? Ethash?
gusknure
Newbie
*
Offline Offline

Activity: 40
Merit: 0


View Profile
May 11, 2019, 06:41:51 AM
 #719

MTP
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
May 11, 2019, 06:43:28 AM
 #720

MTP

Make sure you do not have -RH or -rate on the command line
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 [36] 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!