 Show Posts
|
|
Pages: [1] 2 »
|
|
Hi casper77 & CryptoDredge dev:
Help! Using CryptoDredge with latest nVidia drivers causing high load CPU usage.
Other miner apps like T-Rex, z-enemy, etc. have already fixed this issue.
Please do so with CryptoDredge!
Thank you.
|
|
|
|
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!
Hi. Any change on "-b" or "--api-bind" arguments, so it can be accessed from other computer in same network (not just from rig's local computer)? Thanks. |
|
|
|
|
@TrailingStop,
TT-Miner has issue mining MTP (ZCoin) at "2miners' pool (xzc.2miners.com:8080).
Miner is hashing, but no shares accepted. Thus pool shows zero hashrate of the miner.
I tried v2.1.17 up to v2.1.19, and it has the same issue.
I'd also tried CryptoDredge, and it runs smoothly at that pool.
Please kindly fix it ASAP.
I hate to use slower miner just because the fastest one has issue with certain pools.
Thank you.
|
|
|
|
|
Hi CryptoDredge Dev,
CryptoDredge v.1.13.0 is much slower than CryptoDredge v.1.11.0 in: Lyra2z, Phi2, and Allium.
Hope you can fix it. Thanks.
|
|
|
|
|
Hi CryptoDredge dev,
Thank you for such great miner.
Please help!
I get 54 Mh/s (Allium algo) on GTX 1070 Ti rigs with CryptoDredge 0.11.0, while only get 47 Mh/s with CryptoDredge 0.12.0 (same cards and same settings with both versions).
Why is v0.12.0 slower than v.0.11.0 for Allium algo?
|
|
|
|
Hi cryptodredge dev. Please help.
I try to change the intensity for Phi2 algo with CryptoDredge 0.9.1 (Windows 10).
I set "-i 5", but the miner still use intensity "6" for my GTX1070Ti.
Is this a bug? Need your advise. Thank you.
Try "--intensity=5" Yes, I tried that and it worked. Thank you! Yet miner still crashed though (even though it runs well with Lyra2z with the same OC). Well, I guess I need to lower the OC.  |
|
|
|
|
Hi cryptodredge dev. Please help.
I try to change the intensity for Phi2 algo with CryptoDredge 0.9.1 (Windows 10).
I set "-i 5", but the miner still use intensity "6" for my GTX1070Ti.
Is this a bug? Need your advise. Thank you.
|
|
|
|
You don't have to reflash firmware if you recompile bmminer to use fixed frequency. Then you just replace bmminer.sh on the miner with your modified version.
Hi Tazers, Thank you for your reply. The first step of your Upgrade Instructions is to Flash Fixed Frequency firmware. That's why I thought I need to replace the auto-freq firmware with the older fix-650M one, before I can replace the bmminer.sh with your modified version. Now you say I don't have to do the first step? Just want to confirm that. Okay, if you said that, then I will skip the first step and go to the next ones. Hope it will works. Thanks again. |
|
|
|
|
Hi Tazers,
I tried to flash fix-650M firmware ("Antminer-S9-all-201705031838-650M-user-Update2UBI-NF.tar/gz") to my S9 (which has the default auto-freq Nov 2017 firmware), and I got this "Invalid Upgrade version" messages.
The S9 rebooted itself and it still has the default auto-freq version. So the flash failed.
Could you kindly advise what should I do to flash the fix-650M ?
Thank you very much.
|
|
|
|
@Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks. There is no need to add :x behind your BTC address. Yes, I would advise you to edit your config file for 6 GPUs, but it should work either way, excavator is ignoring commands send for devices that do not exist. Ok, got it. Thanks again for your help. Cheers! |
|
|
|
Ok, I see the problem, we modified excavator API with 1.5.x versions. Try this (change btc address in subscribe method):
[
{"time":1,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.jp.nicehash.com:3200","BTC address"]}
]},
{"time":2,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["lyra2rev2", "0"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "1"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "2"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "3"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "4"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "5"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "6"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "7"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "8"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "9"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "10"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "11"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speeds","params":[]},
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]
FYI, you said you have 6 devices in the rig, the config file is made for 13 GPUs. @Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks. |
|
|
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work.
How should I setup it with AM? Should I setup the Json file ?
I have 6 of GTX 1070 TI.
Please help. Thanks.
I'm not familiar how Awesome Miner passes the commands to Excavator. Probably through the config file, can you post here the json file you mentioned? @Dropky, Here is the "awesome.json" file made by Awesome Miner in Excavator 1.5.4a folder (and it doesn't work): [
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2","lyra2rev2.jp.nicehash.com:3347","76FG5wMYLzy4KHrEsqCDBZ65KzuF8ambE:x"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","4"]},
{"id":1,"method":"worker.add","params":["0","5"]},
{"id":1,"method":"worker.add","params":["0","6"]},
{"id":1,"method":"worker.add","params":["0","7"]},
{"id":1,"method":"worker.add","params":["0","8"]},
{"id":1,"method":"worker.add","params":["0","9"]},
{"id":1,"method":"worker.add","params":["0","10"]},
{"id":1,"method":"worker.add","params":["0","11"]},
{"id":1,"method":"worker.add","params":["0","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
] |
-------------------------------------------------------------------------------------------------------------------------------------- And here is the "awesome.json" file made by Awesome Miner in Excavator 1.4.4a folder (and it works) : [
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2","lyra2rev2.jp.nicehash.com:3347","76FG5wMYLzy4KHrEsqCDBZ65KzuF8ambE:x"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","4"]},
{"id":1,"method":"worker.add","params":["0","5"]},
{"id":1,"method":"worker.add","params":["0","6"]},
{"id":1,"method":"worker.add","params":["0","7"]},
{"id":1,"method":"worker.add","params":["0","8"]},
{"id":1,"method":"worker.add","params":["0","9"]},
{"id":1,"method":"worker.add","params":["0","10"]},
{"id":1,"method":"worker.add","params":["0","11"]},
{"id":1,"method":"worker.add","params":["0","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
] |
Please help. Thanks a lot. |
|
|
|
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work.
How should I setup it with AM? Should I setup the Json file ?
I have 6 of GTX 1070 TI.
Please help. Thanks.
|
|
|
|
Hi, need an enlightenment here. Does CPUminer-Opt has built-in command line options to set CPU affinity? Thanks before. start /affinity 55 cpuminer...... or --cpu-affinity 0x55 Got it. Thank you. |
|
|
|
Hi, need an enlightenment here. Does CPUminer-Opt has built-in command line options to set CPU affinity? Thanks before. |
|
|
|
@PhoenixMiner, I run PhoenixMiner 2.7c on 6 x GTX1070 Ti (Win 10 Pro build 1709) smoothly, until these last several days. Every time after I run it for several minutes, one of my cards suddenly lost its memory OC setting and back to is default memory setting. It happens when the miner restart, right after it crash (after connection error to "d3pool.eu/api/status"). I tried to ping " www.d3pool.eu", but the connection is okay and no packet loss. Here is what I found in the log file : 3/12/2018 2:29:50 PM.911 [015] [E]Failed to download string from: http://www.d3pool.eu/api/status System.Net.WebException: The remote server returned an error: (503) Server Unavailable. 3/12/2018 2:29:54 PM.634 [001] ['S][ManagedMiner#3 - MNG-01] Interface connected 3/12/2018 2:29:55 PM.650 [001] ['S][ManagedMiner#9 - MNG-01 CPU - Cryptonight] Interface connected 3/12/2018 2:35:48 PM.468 [011] [E]Failed to download string from: http://www.d3pool.eu/api/status System.Net.WebException: The remote server returned an error: (503) Server Unavailable. 3/12/2018 2:40:48 PM.328 [011] [E]Failed to download string from: http://www.d3pool.eu/api/status System.Net.WebException: The remote server returned an error: (503) Server Unavailable. 3/12/2018 2:44:24 PM.773 [005] [W][ManagedMiner#3 - MNG-01] process not running. Restarting... 3/12/2018 2:44:24 PM.773 [001] ['S]Received system notification: Mining process not running, initiating restart 3/12/2018 2:44:24 PM.773 [005] ['S][ManagedMiner#3 - MNG-01] Stopping... 3/12/2018 2:44:24 PM.773 [005] ['S][ManagedMiner#3 - MNG-01] Quit command successfully sent 3/12/2018 2:44:27 PM.789 [005] ['S][ManagedMiner#3 - MNG-01] Performing stop 3/12/2018 2:44:27 PM.789 [005] ['S][ManagedMiner#3 - MNG-01] Stopping Mining Software 3/12/2018 2:44:27 PM.789 [005] ['S] Process already closed 3/12/2018 2:44:29 PM.805 [005] ['S][ManagedMiner#3 - MNG-01] Starting... 3/12/2018 2:44:29 PM.805 [005] ['S][ManagedMiner#3 - MNG-01] Starting Mining Software 3/12/2018 2:44:29 PM.805 [005] ['S][ManagedMiner#3 - MNG-01] Setting up Miner Engine. Instance: 1 3/12/2018 2:44:29 PM.805 [005] ['S][ManagedMiner#3 - MNG-01] Engine Type: PhoenixMiner, Auto Download: False, EnginePath: C:\Users\MNG-01\AppData\Local\AwesomeMiner\PhoenixMiner_2.7c\PhoenixMiner.exe, Subtype: Disabled, CustomExecutable: 3/12/2018 2:44:29 PM.805 [005] ['S]EngineSetup: PhoenixMiner 3/12/2018 2:44:29 PM.805 [005] ['S][ManagedMiner#3 - MNG-01] : GetStaticSortedPools, Enginetype: PhoenixMiner, Algorithms: Ethereum Please help. Thank you. |
|
|
|
A bit more fast claymore 11.3 now
So the Calymore 11.3 is faster than the 2.7C? Sure, Rig with 8 rx580 : Phoenix 2.7c 245,4 mh/s and Clay 11.3 246,1 It means Claymore 11.3 about 0.285 % faster than Phoenix 2.7c. But if you deduct that 0.285% with 0.35% (Phoenix's fee only 0.65% compare to Claymore's 1% fee), then you get (minus) -0.065%. Still prefer Phoenix. Btw; on my GTX 1070 Ti, Phoenix 2.7c still around 0.74% faster than Claymore 11.3. If you add that 0.74% with 0.35%, you get around (plus) 1%. Still prefer Phoenix. Just my test and dumb calculation. |
|
|
|
Hello dstm,
Thank you for your great work. I have been using your software to mine for a while.
I would like to ask, if it possible to make your software "restart" after a cuda memory fail on a gpu.
I have several rigs running and I am not always checking on them, it`s not nice to see that I had one rig not working for a entire night or day because there was a error.
This happens more in rigs where I have 6 different gpu`s from nvidia, it`s not easy to find the best OC. So if, a error happens, it should be logged and the mining should restart. That way I would check for the logs and know that I should reduce a OC on a gpu but i wouldn`t lost several hours of mining.
Thank you very much and keep the good work.
Sorry about my poor english.
I've already done some tests with respect to this. This can't be done reliable from the context of zm. If an unstable/overclocked GPU crashes it stops responding to driver calls most of the time such that it's impossible to restart the GPUs from zm's context. You need something external - like a simple script - which restarts zm on GPU crashes. However this won't work reliable too - sometimes you have to restart your whole system after a GPU crash. If possible zm reports the affected GPU but even this is not always possible on unstable hardware. When DSTM crashes it displays the windows error message box (like unhandled exception) from the DSTM process. So if I run it from the loop batch script it waits until I press OK button on that MessageBox, then process exists and then the batch can loop and restart. My question, is it possible to avoid it, put some kind of global try-catch, quietly log the error and exit process. Maybe this could help : https://www.raymond.cc/blog/disable-program-has-stopped-working-error-dialog-in-windows-server-2008/ |
|
|
|
|
@Funakoshi: how does it compare to DSTM ? Because DSTM is faster than EWBF. Please advise. Thank you.
|
|
|
|
In my opinion : that actually, should be the number one priority in your plan and schedule. Smiley
I'm pretty sure if you do that, so many people will undoubtedly dump other miners and jump in instantly. Smiley
Just a thought. He said that he would add an option to opt out the second part of the communication, not the first part. So there will be still a private connection ongoing. The first communication checks the update and receives license information, including for example where to mine devfee. Because of security reasons, it would be very hard to eliminate this private communication.
The follow-up communications only send runtime information of bminer, like the mining speed of each card and performance status. This may enable bminer to choose better optimization strategies. I understand that you do that so people cannot disable the dev fee, but we still don't want it. Just live with that, most of us don't want to use your miner if there is ANY kind of encrypted connection ongoing. There are alternatives we can use, so you should focus to gain more popularity instead of making your incomes ultra secure or whatever you want to do. You're going against the people who can provide you your 2%, so just think about it, how many people would mess with some shady no dev fee mods if there is a stable and fast miner available, also secure and virus free, with an active development? I don't think many. So you lose this way more than you would lose if a few morons decide to remove the dev fee. Also you're gaining a bad reputation this way. People are talking already that your miner reports the hashrare higher than it actually is. Just think about it. Actually, that's what I mean, buddy! I just not smart enough to use words to express my thought. ) Hopefully, Realbminer could understand what we meant, and not take it negatively. Happy mining! |
|
|
|
|
