 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
AND NOW I SEE THE PROBLEM. DUAL MINING ETC+ZIL is only possible if you generate a new DAG every time on windows pcīs. ETC+ZIL DAG is now lightly over 4GB in windows for sure - linux have a little bit more time. Lolminer cannot caching the Zil DAG on ETC (reported to lolliedieb so often, but he donīt care about it)
You must delete the command: --eth_dag_cache=0
Thank you for reply! Yes, I'am using tripple mining  ETC+ZIL+TON (ezil.me) There is no --eth_dag_cache=0 key present, but I've also tried to add it, and no result  Now trying to play with --eth_4g_max_alloc, but still no result. |
|
|
|
Hi to all. Please, help me to solve the problem. I'am trying to mine ETC+TON with TRM 0.9.3 on polaris (574/584), and can't figure out, what I'am doing worng. The hashrate of primary algo (ETC) is extremely low, while the 2nd algo is vary from normal to low. Tried to fully auto-tune, the same as playing with "eth_config" and "dual_intensity" parameters, but results are nearly the same - I'am getting 3.8-4 MH/s on primary algo ETC, and 0.86-0.9 GH/s on secondary TON algo Using Win10 with drv 20.9.2, compute mode is ON. The competitor's software produces normal hashes, up to 30 MH/s on ETC and 0.36-0.4 GH/s on TON, so I don't think that there is some drivers/mode mess. Sorry for a long post... 1)There is a fully automated tuning of TRM, no additional options defined, all the miner defaults:
[2022-02-22 23:52:49] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC Power ETH Cfg
[2022-02-22 23:52:49] 0 01:00.0 32 1250 0 2050 48C 48C 48C 54.00% 2152 893 mV 98 W A64 (1.00)
[2022-02-22 23:52:49] 1 02:00.0 32 1245 0 2015 47C 47C 47C 48.00% 1959 906 mV 99 W A64 (1.00)
[2022-02-22 23:52:49] 2 03:00.0 32 1175 0 2000 49C 49C 49C 57.00% 1594 900 mV 89 W A64 (1.00)
[2022-02-22 23:52:49] 3 06:00.0 32 1270 0 2050 49C 49C 49C 57.00% 2243 893 mV 100 W A64 (1.00)
[2022-02-22 23:52:49] 4 07:00.0 36 1245 0 2025 47C 47C 47C 48.00% 1916 875 mV 98 W A64 (1.00)
[2022-02-22 23:52:49]
[2022-02-22 23:52:49] Stats Uptime: 0 days, 00:03:18
[2022-02-22 23:52:49] ----------------------------------------- GPU Status -------------------------------------------
[2022-02-22 23:52:49] GPU 0 [48C, fan 54%] ethash: 3.951Mh/s, avg 3.252Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 1 [47C, fan 48%] ethash: 4.022Mh/s, avg 3.690Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 2 [49C, fan 57%] ethash: 3.849Mh/s, avg 3.190Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 3 [49C, fan 57%] ethash: 745.1kh/s, avg 637.4kh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 4 [47C, fan 48%] ethash: 731.3kh/s, avg 625.2kh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] Total ethash: 13.30Mh/s, avg 11.39Mh/s, pool 0.000 h/s a:0 r:0
[2022-02-22 23:52:49] ----------------------------------------- Pool Status ------------------------------------------
[2022-02-22 23:52:49] eu.ezil.me ethash: 13.14Mh/s, avg 11.17Mh/s, pool 0.000 h/s a:0 r:0
[2022-02-22 23:52:49] ----------------------------------------- GPU Status -------------------------------------------
[2022-02-22 23:52:49] GPU 0 [48C, fan 54%] ton: 921.4Mh/s, avg 804.3Mh/s, pool 2.218Gh/s a:2 r:0 hw:0
[2022-02-22 23:52:49] GPU 1 [47C, fan 48%] ton: 917.9Mh/s, avg 796.6Mh/s, pool 1.111Gh/s a:1 r:0 hw:0
[2022-02-22 23:52:49] GPU 2 [49C, fan 57%] ton: 860.8Mh/s, avg 746.5Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 3 [49C, fan 57%] ton: 967.8Mh/s, avg 774.7Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] GPU 4 [47C, fan 48%] ton: 1.075Gh/s, avg 846.2Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:52:49] Total ton: 4.743Gh/s, avg 3.968Gh/s, pool 3.329Gh/s a:3 r:0
[2022-02-22 23:52:49] ----------------------------------------- Pool Status ------------------------------------------
[2022-02-22 23:52:49] pplns.toncoinpool.io/stratum (PROXY) ton: 4.943Gh/s, avg 3.876Gh/s, pool 3.327Gh/s a:3 r:0
[2022-02-22 23:52:49] ------------------------------------------------------------------------------------------------
2)Next step, I trying to set --dual_intensity=0.25 to get a 75% of GPU power directed to primary algo ETC
[2022-02-22 23:37:07] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC Power ETH Cfg
[2022-02-22 23:37:07] 0 01:00.0 32 1250 0 2050 44C 44C 44C 42.00% 1807 893 mV 68 W A128 (0.25)
[2022-02-22 23:37:07] 1 02:00.0 32 1245 0 2015 42C 42C 42C 36.00% 1593 906 mV 80 W A128 (0.25)
[2022-02-22 23:37:07] 2 03:00.0 32 1175 0 2000 44C 44C 44C 42.00% 1184 900 mV 70 W A128 (0.25)
[2022-02-22 23:37:07] 3 06:00.0 32 1270 0 2050 43C 43C 43C 39.00% 1697 893 mV 79 W A128 (0.25)
[2022-02-22 23:37:07] 4 07:00.0 36 1245 0 2025 42C 42C 42C 36.00% 1542 875 mV 75 W A128 (0.25)
[2022-02-22 23:37:07]
[2022-02-22 23:37:07] Stats Uptime: 0 days, 00:07:49
[2022-02-22 23:37:07] ----------------------------------------- GPU Status -------------------------------------------
[2022-02-22 23:37:07] GPU 0 [44C, fan 42%] ethash: 710.2kh/s, avg 665.8kh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 1 [42C, fan 36%] ethash: 4.025Mh/s, avg 3.760Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 2 [44C, fan 42%] ethash: 3.900Mh/s, avg 3.775Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 3 [43C, fan 39%] ethash: 755.0kh/s, avg 711.2kh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 4 [42C, fan 36%] ethash: 740.6kh/s, avg 698.3kh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] Total ethash: 10.13Mh/s, avg 9.610Mh/s, pool 0.000 h/s a:0 r:0
[2022-02-22 23:37:07] ----------------------------------------- Pool Status ------------------------------------------
[2022-02-22 23:37:07] eu.ezil.me ethash: 9.731Mh/s, avg 9.506Mh/s, pool 0.000 h/s a:0 r:0
[2022-02-22 23:37:07] ----------------------------------------- GPU Status -------------------------------------------
[2022-02-22 23:37:07] GPU 0 [44C, fan 42%] ton: 475.4Mh/s, avg 449.9Mh/s, pool 1.329Gh/s a:3 r:0 hw:0
[2022-02-22 23:37:07] GPU 1 [42C, fan 36%] ton: 465.6Mh/s, avg 454.5Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 2 [44C, fan 42%] ton: 436.0Mh/s, avg 422.8Mh/s, pool 443.5Mh/s a:1 r:0 hw:0
[2022-02-22 23:37:07] GPU 3 [43C, fan 39%] ton: 481.1Mh/s, avg 461.2Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] GPU 4 [42C, fan 36%] ton: 538.5Mh/s, avg 525.1Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2022-02-22 23:37:07] Total ton: 2.397Gh/s, avg 2.313Gh/s, pool 1.772Gh/s a:4 r:0
[2022-02-22 23:37:07] ----------------------------------------- Pool Status ------------------------------------------
[2022-02-22 23:37:07] pplns.toncoinpool.io/stratum (PROXY) ton: 2.268Gh/s, avg 2.283Gh/s, pool 1.772Gh/s a:4 r:0
[2022-02-22 23:37:07] ------------------------------------------------------------------------------------------------
As you can see, the secondary algo hashrate goes down, but at the same time there is no increase of h/r in primary algo Any ideas, what I need to tune, to get the normal hashes, please?.. Thanks. |
|
|
|
|
Hi to all. Sorry, if this quiestion was already asked and answered...
How to configure Gminer for ETH+ZIL mining, but with different pools for each coin?
|
|
|
|
Can I dual mine ETH + ZIL with this miner using 2 different pools?
Have the same question! Didn't find in documentation anything like pool-strategy option, to switch to pool with lowest epoch.. |
|
|
|
Unfortunatelly, near a 40min ago Phoenix is died Epoch #329 - not enough VRAM on 4Gb GPUs. |
|
|
|
When 5.0 version?
Why you need newer version, the miner works perfectly? The miner works not perfectly, there is an issue present. Also waiting for a fixed version. |
|
|
|
Hi. I have a problem with strap settings (-mt value) - the miner can't set the timings ----------------------------------------------- GPU0: Unable to set VMEM timing to 2 - error: -8 GPU1: Unable to set VMEM timing to 2 - error: -8 GPU2: Unable to set VMEM timing to 2 - error: -8 ----------------------------------------------- Rig is on AMD RX570 8Gb, under Win10, driver 18.3.4 (tried the 19.12.3 as well). Phoenix 4.9c Miner is running via "Run as admin..." Any thoughts, what can be an issue?.. So, looks like -mt parameter is broken in current version. It's doesn't work on any of the rig (tried only win, linux is not tested). Or there is some trick needed for win10, which is not described in miner's documentation Hope, this will be fixed in future releases. |
|
|
|
Hi. I have a problem with strap settings (-mt value) - the miner can't set the timings ----------------------------------------------- GPU0: Unable to set VMEM timing to 2 - error: -8 GPU1: Unable to set VMEM timing to 2 - error: -8 GPU2: Unable to set VMEM timing to 2 - error: -8 ----------------------------------------------- Rig is on AMD RX570 8Gb, under Win10, driver 18.3.4 (tried the 19.12.3 as well). Phoenix 4.9c Miner is running via "Run as admin..." Any thoughts, what can be an issue?.. So, nobody didn't has this issue? It's only me "lucky"? |
|
|
|
Hi. I have a problem with strap settings (-mt value) - the miner can't set the timings ----------------------------------------------- GPU0: Unable to set VMEM timing to 2 - error: -8 GPU1: Unable to set VMEM timing to 2 - error: -8 GPU2: Unable to set VMEM timing to 2 - error: -8 ----------------------------------------------- Rig is on AMD RX570 8Gb, under Win10, driver 18.3.4 (tried the 19.12.3 as well). Phoenix 4.9c Miner is running via "Run as admin..." Any thoughts, what can be an issue?.. |
|
|
|
In addition to the log file (C:/Users/USERNAME/AppData/Local/AwesomeMiner as pointed out by @narousberg), could you also send me the GPU details from Awesome Miner? Please select the miner and go to the GPU tab at the bottom of the screen. Click "View GPU details". Please send me this information via mail or the web site ( https://www.awesomeminer.com/contact). Thanks! Thank you for reply. Unfortunatelly, now I already have no access to rigs, because going to business trip:( Reverted them back to 3rd-party HW control (MSI AB). Will experiment again after return... |
|
|
|
Did you try to restart the rig first then test it again if not work there something wrong in your rig.
*If not running correctly, please verify that either Microsoft .NET Framework 2.0 or 3.5 is installed (having only .NET Framework 4.X installed is not enough).
Yes, restarted rig few times. And the same situation on the 2nd rig, where AMD+NVIDIA cards are mixed. .net 3.5 + 4.7 are installed, as the VC++ 2013 and 2015 Running Win10 Ent. |
|
|
|
Thanks for the question. It sounds like you do everything correctly, but the behavior in Awesome Miner may not be fully consistent here. When you manually (or via Rule) apply a profile it will only be applied for the specific GPU that was used to create the profile.
Using a Clocking Group Profile should however have worked. If you define Matching rule as "GPU Name" and the expression as "1060" - a rule that is using this Clocking Group Profile should apply it to all your nVidia 1060 GPU's. If this isn't working, could you please send me the Awesome Miner Remote Agent log file via e-mail and let me know the time you applied the clocking? Thanks!
Tried with "GPU Name" also - not working. Please, advice, where the debug log located? |
|
|
|
Hi to community. Please, advice with the GPU Clocking Profiles in v7.0.6 There is a profile created with such strings: Power Limit 70 Core Clock Boost 175 Memory Clock Boost 600 Temperature Limit 65 This is NVIDIA 1060 rig. The Profile is set in miner properties -> GPU CLocking Profiles -> Apply ... when starting -> Profile name. This is applied at the miner start to all GPUs, it's OK. But later, after some time, there is a need to change overclocking settings, and there is a separate Profile is created. It's applying via the rule, by time (but the manual applying has the same result). The problem is, the profile is applying only to GPU0, and all other GPUs are not affected. Both, via the rule, and if applied manually via the right-click menu. I've read the guide, and there is said: If a system consist of similar GPU's where the clocking settings are to be the same - a single clocking profile can be used to apply the setting to all GPU's. But this is not working Even tried to create clocking profile group, tried to put there vendor, or pci bus ID's, or GPU name - no result, OC settings applying only for GPU0. Pleae, advice, is this a bug, or I did something wrong? |
|
|
|
На данном канале кидают доверчивых хомяков на крипту. Этот "трейдер" активно зазывает отдать средства в ДУ, выкладывает липовые скрины выплат инвесторам. На просьбу вывести депозит из ДУ, или его часть - полный игнор. Его предидущий аккаунт в телеграме уже пометили, как скамера, он сменил на новый @Andrey_D_U |
|
|
|
Commandline for the miner is: tt-miner -a mtp -A MTP-100 -P stratum+tcp://<address>.nvidia01:x@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4035 The rig is on Win10, has local IP 192.168.128.21, firewall is disabled for all networks, WinDefender disabled via registry. IPv6 is disabled. The telnet localhost 4035 - miner answering. The telnet 127.0.0.1 4035 - miner answering. Trying from another rig, in the same network (192.168.128.20) telnet 192.168.128.21 4035 - connection denied. No wonders as you have bound API to 127.0.0.1 which is localhost. It is not accessible from LAN. Technically you should modify the command line to utilize --api-bing 0.0.0.0:4035 0.0.0.0 means ALL of the computer IP addresses present, so it should include 127.0.0.1 and 192.168.128.21 which I assume is your LAN IP address. However, looking at what TrailingStop wrote above "0.0.0.0 will be translated to localhost (127.0.0.1)." I doubt this will work until TT fixes this behavior. OR Just use --api-bind 192.168.128.21:4035 and API will be accessible from LAN, but you may have issues with your miner (awesomeminer or NHML or smth else) if any. Hi, This is 100% correct. I bound 127.0.0.1 to localhost. I was not aware that it should bound to all. Will fix that in next release. Thanks for pointing to this issue. Dear developer, when we can expect for fixing this issue?  BTW, thanks for this miner. It's the best now for MTP  |
|
|
|
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 |
|
|
|
Hi to all.
Does anybody know, how to tell monerod.exe to not start mining? I've trying to set-up own monero node, and everything is OK, except one annonying thing - the monero daemon begins to mine on all cores after 5-10min from launch. The flag --bg-mining-enable is NOT set (looks like it has no arguments, so, the mining is allowed only, when the flag is present?) Also, tried to play with --mining-threads --bg-mining-idle-threshold --bg-mining-miner-target flags, to set the conditions, when mining will not start, but looks like the v0.14.0.x is completely ignoring these settings - mining starting anyway, after a few minutes.
How to disable the mining function?..
Found a solution by myself. There is need to add a flag --restricted-rpc |
|
|
|
|
Hi to all.
Does anybody know, how to tell monerod.exe to not start mining? I've trying to set-up own monero node, and everything is OK, except one annonying thing - the monero daemon begins to mine on all cores after 5-10min from launch. The flag --bg-mining-enable is NOT set (looks like it has no arguments, so, the mining is allowed only, when the flag is present?) Also, tried to play with --mining-threads --bg-mining-idle-threshold --bg-mining-miner-target flags, to set the conditions, when mining will not start, but looks like the v0.14.0.x is completely ignoring these settings - mining starting anyway, after a few minutes.
How to disable the mining function?..
|
|
|
|
|
