WildRig Multi 0.12.0 Beta With More Algorithms and Performance
I've just implemented support for WildRig and it will be included in the next release. There will probably be a development release available in about 2 days from now. |
|
|
|
patrikeI stumbled on the Internet for two more online calculators, can I also collect statistics from them? https://crypt0.zone/https://shittomine.com/the second refers to the little-known coins, but in turn they are fired up to x10 Question: when statistics are collected for the same coin, IMHO to calculate the average figure? because sometimes there is a 2-3 times difference Thanks for your suggestions. At the moment, none of these sites provides any interfaces (API) where applications can get coin statistics. If they have an interest of providing that in the future, it could be supported via Awesome Miner. It will depend on if they are willing to share this information outside their own web site. |
|
|
|
Hello, i have some problems with Awesome Miner, i installed it on small laptop nb33 with intel atom 1.33 ghz cpu and 2MB memory, with just 35-40 devices it works very very slow and often hangs, do you have any advices on how to make it run normally?
Because this is a low-end system, I would first of all recommend you to go to the Options dialog, Advanced section, and enable "Performance Mode". Is Awesome Miner running any better after making this change? What is the CPU load indicated in the Task Manager when Awesome Miner is running slow? |
|
|
|
Strange bug with the Linux client report. ./awesome-upgrade.sh
./service-install.sh
./service-start.sh
root@simpleminer:~/awesomeminer-remoteagent# ps aux | grep awesome
root 4942 0.0 0.0 14224 992 pts/0 S+ 14:02 0:00 grep --color=auto awesome
root 18900 0.0 0.0 27344 2828 ? Ss Sep28 0:04 SCREEN -dmS awesome0001 /root/.local/share/AwesomeMinerService/UploadedSoftware/teamredminer-v0.3.1/awesome-start.sh
root 18902 0.0 0.0 12528 3076 pts/2 Ss+ Sep28 0:00 /bin/bash /root/.local/share/AwesomeMinerService/UploadedSoftware/teamredminer-v0.3.1 awesome-start.sh
root@simpleminer:~/awesomeminer-remoteagent# ./service-log.sh
-- Logs begin at Thu 2018-10-04 09:23:05 CEST. --
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Service hold-off time over, scheduling restart.
Oct 04 14:01:30 simpleminer systemd[1]: Stopped Awesome Miner Remote Agent.
Oct 04 14:01:30 simpleminer systemd[1]: Started Awesome Miner Remote Agent.
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Main process exited, code=exited, status=203/EXEC
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Unit entered failed state.
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Failed with result 'exit-code'.
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Service hold-off time over, scheduling restart.
Oct 04 14:01:30 simpleminer systemd[1]: Stopped Awesome Miner Remote Agent.
Oct 04 14:01:30 simpleminer systemd[1]: awesome.service: Start request repeated too quickly.
Oct 04 14:01:30 simpleminer systemd[1]: Failed to start Awesome Miner Remote Agent.
Mining starts. However, AwesomeMiner shows the client as service offline. The script awesome-upgrade.sh is a file generated on the fly by Remote Agent while upgrading. It's not intended to be executed manually. What might happen is that ./AwesomeMiner.RemoteAgent.Linux didn't get the correct execution permission. You could also try to execute this file manually to see if you get any other error message. |
|
|
|
Awesome Miner version 5.6.1
Hi, Patrike. Is it possible to implement such functionality in next version?.. Hi to community.
Please, advice, is there any way, to do the following...
The situation: There is a managed local miner created with the selected ETH pool. There is a rule for this miner, that switch a pool to ETC at the specified time, and the 2nd rule, that switch the pool back to ETH, also st the specified time.
The problem: if the pool was changed to ETC, and during the miner work the rig hangs/crashes, after system reboot it's back to ETH, that selected in the managed miner settings.
The question: How to prevent switching back to ETH pool, after the rig crashes and Awesome Miner restarts? Is there any way to force Awesome to remember the last settings?
Thanks in advance... It could work if you define multiple rules for this scenario. It might be a little complex, but the concept could be something like: 1) A rule with a Time trigger where you use the action to set Miner Tag - for example set the tag ETH at 6 AM. 2) A rule that remove this tag, for example at 9 PM. 3) A rule that uses two triggers, one to detect if Miner Tag is ETH (trigger: Detect miner tag) and a second trigger that detect (trigger: Detect Pool) if the pool isn't your ETH pool. Select Match All. Run the action to change to the ETH pool. 4) A trigger similar to #3, but detect if the tag ETH doesn't exist on the miner and if the pool isn't your ETC pool. Run the action to change to the ETC pool. What I can do to simplify this is to add support for a new trigger that is triggering between two (or more) time intervales. This would reduce the complexity of the above. |
|
|
|
Thanks for pointing this out. They even copied the copyright notice - amazing guys. Hopefully it will smell enough scam so no one will download their malware. I think everyone knows this already, but I might as well point it out: 1) The Awesome Miner software should always be downloaded from the official web site 2) If someone is trying to sell a license at a discount, I can assure that it's not a valid license they are trying to sell 3) I've also received reports from users that downloaded a 5000 miner version of Awesome Miner and ended up with a great collection of malware on their systems. I probably don't need to point out that it wasn't downloaded from the official web site in this case. |
|
|
|
I configured rules for idle/use scenarios, but "stop miner" will also trigger if I manually press a Start button
How to prevent that?
I think the reason it will trigger Stop Miner is because the rule will detect that the system is in use if you press the Start button. I assume the miner is running on the Awesome Miner computer itself, and not on a Remote Agent? |
|
|
|
Hi patrike,
Re: Registration code: Upgrade code issued
Does the old Reg code still work as well ?
Hi, If you have a license, for example Standard Edition and then you upgrade it to Professional Edition, you will receive a new license code for Professional Edition. Because you only paid for the price difference when upgrading, you need to use the new code you got for the Professional Edition. Your old code for Standard Edition can no longer be used and will eventually expire. |
|
|
|
WildRig Multi 0.11.6 Beta is Becoming Even More Useful Multi-algorithm Miner
Hi Patrike, +1 for integrating it into AM The miner is somewhat using compatible commandline + API as XMRig so I could add it to AM as custom software without issue. But reading from the API seemed to have a bit of issue with the hashrate units so far. eg, mining HMQ1725, API reports hashrate of 5000 kH/s, but AM is reading 5 kH/s FYI. edit: it applies to tribus, bcd as well (i suspect all) that kH/s are all parsed as H/s I will take a look at this one. Thanks for your suggestions. Hi Patrike, Seems they have fixed the API reporting unit from kH/s to H/s so on unit inconsistencies side of things, this is not an issue anymore 0.11.9
- speedup x16r/x16s in some cases on final step
- fixed regress for simd, so should speedup x16r/x16s and return speed for other algos(bcd, sonoa, etc.)
- added hex algo
- now intensity can be set using sgminer-like numbers(old one supported too)
- improved API a bit, now threads contains hashrate per GPU, not per thread, so it should be correct now for HiveOS/etc.
- fixed GPU numbering at start when --opencl-threads used
0.11.8
- regen job now per GPU, should increase poolside hashrate
- added x16r, x16s and timetravel algorithms
- 30% boost for hmq1725
- grouped print of hashrate per GPU when use --opencl-threads parameter
- H/s unit in API instead of kH/s But....now a new issue arises and I don't know which party should handle this, as suggested, it's more optimal to run multiple threads per GPU (via --opencl-threads) as per example posted in software's thread, but since the update to 0.11.9 from 0.11.6, AM is only reporting hashrate of 1 thread (I think it's the first) from each GPU, so say, my hashrate is now 8MH/s (4 MH/s per GPU) but running 3 threads per GPU, it is reporting 2.3MH/s to AM (or AM is reading 2.3 MH/s from the API anyway), below is the API output from the hashrate section: "algo": "hmq1725",
"donate_level": 2,
"uptime": 2928,
"hashrate": {
"total": [
8331449,
8336995,
8342576
],
"highest": 8444092,
"threads": [
[
1133473,
1132772,
1133680
],
[
1141292,
1140633,
1130904
]
]
}, Hi, it's a bug in miner API, I will fix it in newer version. Just found that I forgot "+" in formula... Thanks for the update. I was just about to point out that Awesome Miner is only reading the first value for each GPU (the current hashrate), which in this case would be GPU0: 1133473 and GPU1:1141292. If these numbers are made into the total numbers for all GPU threads in the next update, it should be working fine with Awesome Miner. |
|
|
|
|
Awesome Miner version 5.6.1
- Added a guide for Antminer and ASIC miner troubleshooting - can be accessed via the Antminer Diagnostics dialog
- Notification actions can be configured with a custom authorization header for webhooks
- Added more predefined Block Explorers for wallet balance
- Include more detailed information about the Awesome Miner license and subscription via the status bar button for license information
- Z-enemy miner 1.21
- CryptoDredge 0.9.2
- EWBF Equihash Miner 0.6
- Bminer 10.4, with support for Personalization flag
- Correction to path for uploaded software on Remote Agent for Linux
- Correction to ASIC device count on dashboard when running a system with a mix of GPU and ASIC miners
|
|
|
|
I have a question - I currently have 5 ASICs, 2 GPU and 2 CPU mining rigs connected to Awesome Miner. However on the dashboard, it shows a total of 9 and that all 9 are active. So far that is right - but then in the next area, it shows 2 GPU 8 CPU and 9 ASICs (I realize it is counting the cores for CPU but why does it have all the miners grouped under ASICs? And with my CPU's and GPU's it shows the profits that those miners make but not for the ASICs - I have to manually log into the pool to see that.
Is there also any way to link our wallets so that we can see our balances in the Awesome Miner Interface? - edit: I have found the area to do this and am working to add my various wallets. second edit... my main wallet generates a different address for each transaction, so it seems I have to link quite a few "wallets"
The ASIC count for Dashboard will be fixed in the new release that will be available soon. |
|
|
|
@patrike Can be changed --devices to -d in the ccminer configuration?. To achieve greater compatibility in the user defined mining software. I do not know if this change would be detrimental to other mining software  This is a good point and I was considering making this change when I found out that some ccminer clones uses "--device" while other uses "--devices", while "-d" looked like a more universal solution. I was however a bit afraid of breaking things, but I can investigate this in more detail and make the change next time I make a development version available. Thanks for your feedback. |
|
|
|
I might need a bit more details about this scenario. Is TeamRedMiner added as a Managed Software? Compatible with Ccminer or similar? Have you explicitly enabled a few algorithms for it in the same dialog where you set the compatibility?
Yes, it is added as managed software, CCMINER command line compatible with no API. Lyra2Z algo enabled. From what I can see, the only scenario this can happen is if the miner is a Managed Profit Miner (not Managed Miner) and that Awesome Miner doesn't think the pool algorithm can be used for this software. Can you share the log lines just above those you provided, saying something like "GetStaticSortedPools, Enginetype: ". On that line it should also list the algorithms. In the Managed Software configuration, I assume you made sure that it's not only says "Enabled" in the Default-column, but that it also says "Enabled" (or "Default") in the next column called "Enabled / Disabled"? |
|
|
|
Hello Patrik,
could you please add the very very new Lyra2Z WIN miner TeamRedMiner v0.3.2 ? It is working properly but i would like to see more info in AM(i guess they need to add reports etc. too).
Thank you!
I am also running new teamredminer-v.0.3.2-win windows version with Vega 56. Getting 8Mh/s phi2 and 5Mh/s lyra2z on Vega56. But no api info for AM. Thanks for your suggestions. I looked at this mining software but it doesn't provide any monitoring interface (API) where Awesome Miner can connect and get mining information. This mining software can be supported in the future if it's popular and provides an API. |
|
|
|
Why hasrate/consumption does not scale linearly? I mean I have a set HR for X16 algo, 150Mh @1300W, take out some cards from the system, and it shows a negative income, while the one with all 6 cards shows positive. It happens on all algos.
You need to use the concept of Profile Groups in this scenario (see link below). It's fully possible to have a mix of different GPU types, and Awesome Miner needs to know how many of each GPU's in order to know the power consumption for the profit switching feature. https://support.awesomeminer.com/support/solutions/articles/35000086086-profit-switching-for-gpu-and-cpu-mining#profileThat is stupid, why can't you just make a normal linear relation to the set HR/W. I mean if in any set algo 10KH@1000w then 1KH&100w. Its just not working. Even if an asic board is out, its just shows false profit. Awesome Miner currently allows you to have a Profit Profile where you specify the power usage for a GPU. Using the Profile Groups you can make combinations where you say that you have 3 nVidia 1080 and 3 RX570. If you add 3 more RX570, you simply tell Awesome Miner that you have 6 of them instead and the total power usage estimations are still good. For this scenario the linear approximation will probably not work too well. If all your GPU's are identical, I do see your point that it can make sense to support this kind of linear approximation (although it's not fully true because underclocking typically gives higher hashrate per Watt compared to Overclocking). I will consider adding a setting for this. |
|
|
|
@Patrike you have to face the new RTX 2xxx range from nvidia.
The OC does not work, I have installed aftherburner 4.6 beta that supports RTX, but no AM does not change OC, I guess they will also have to update the remoteserver.
No miner today is up to date, to the point that t-rex is totally useless in RTX and is one of the most used. I know it does not depend on you, but I would appreciate quick updates when they leave. It is always more comfortable to be through AM update than to put a custom miner, then there are many miners in my platform.
It would be necessary to see why the RTX change OC, and be very attentive to the new miners or updates.
RTX2080 is a card that is coming en masse right now and I expect frequent updates from AM adding the new miners and making everything work correctly, since as I say the change of OC does not work with the current remoteserver, or I do not know if you could do something about this
I have already written in all photos of miners, cryptodredge, t-rex, z-enemy etc ... so that they take into account as soon as possible these cards that use another memory and require Cuda 10.
I understand you point and agree. Please note that it often take a little while when a new GPU is relesed before all software, drivers and tools are fully up-to-date and taking advantage of it. We will probably also see that the mining software developers will find new ways of optimizing the hashing based on the behaviors of the new RTX 2000-series. The plan is of course that Awesome Miner should work fine with the RTX 2000-series as well, but it may not be the case the first period of time. I'm trying to follow this closely and if you or anyone else make any additional findings related to the RTX 2000-series, please let me know. I will try to get one of these cards myself during next week to do some testing. |
|
|
|
Why hasrate/consumption does not scale linearly? I mean I have a set HR for X16 algo, 150Mh @1300W, take out some cards from the system, and it shows a negative income, while the one with all 6 cards shows positive. It happens on all algos.
You need to use the concept of Profile Groups in this scenario (see link below). It's fully possible to have a mix of different GPU types, and Awesome Miner needs to know how many of each GPU's in order to know the power consumption for the profit switching feature. https://support.awesomeminer.com/support/solutions/articles/35000086086-profit-switching-for-gpu-and-cpu-mining#profile |
|
|
|
Can you please add support automatic switching Algo in Baikal X10
One limitation on the Baikal miner is that change of both pool and algorithm over the management interface (API) isn't supported. This limitation is not in Awesome Miner, but in the Baikal miner itself. However, the profit switching feature might still work as it only changes the priority of the pools. What was the result when you tested it? |
|
|
|
Worked around this by specifying the path to the miner with a full explicit path "/root/.local/share/AwesomeMinerService/UploadedSoftware/teamredminer-v0.3.1/teamredminer"
I will correct the path issue for uploaded software in the next release. Thanks for finding out the scenario and sharing all details. EDIT: And on to the next problem. I've now converted to a managed miner and get the following strange error: 9/28/18 4:45:30 PM.964 [016] [S][ManagedMiner#20 - random] : GetStaticSortedPools, ignoring pools: stratum+tcp://blockmasters.co:4553, Lyra2z. stratum+tcp://us-east.ethash-hub.miningpoolhub.com:17020, Ethereum. etc-us-east1.nanopool.org:19999, Ethereum. stratum+tcp://eth-us-east1.nanopool.org:9999, Ethereum. pirl.minerpool.net:8004, Ethereum. stratum+tcp://us-east.lyra2z-hub.miningpoolhub.com:17025, Lyra2z. stratum+tcp://lyra2z.mine.blazepool.com:4553, Lyra2z. stratum+tcp://us-east.lyra2z-hub.miningpoolhub.com:20581, Lyra2z. stratum+tcp://lyra2z.na.mine.zpool.ca:4553, Lyra2z. stratum+tcp://lyra2z.mine.zergpool.com:4553, Lyra2z. stratum+tcp://lyra2z.mine.ahashpool.com:4553, Lyra2z. stratum+tcp://lyra2z.us.hashrefinery.com:4553, Lyra2z. stratum+tcp://67.40.164.173:3833, ProgPow.
9/28/18 4:45:30 PM.964 [016] [S][ManagedMiner#20 - random] : Adding pool:
9/28/18 4:45:30 PM.964 [016] [S]Set execution permission for: /root/.local/share/AwesomeMinerService/UploadedSoftware/teamredminer-v0.3.1/teamredminer
I might need a bit more details about this scenario. Is TeamRedMiner added as a Managed Software? Compatible with Ccminer or similar? Have you explicitly enabled a few algorithms for it in the same dialog where you set the compatibility? |
|
|
|
I can't get to work T-Rex as managed miner, it always cut 2 letters from stratum. What is wrong?
It's from the begining when you added t-rex to your software.
Other miners working without any problems.
Second thing as profit switching it works with zergpool or nicehash.
Please share the diagnostics output (toolbar button: Diagnostics) for this scenario. Please also share a screenshot of your Pool (Options dialog, Pools section) used by this miner. Thanks! |
|
|
|
|
Show Posts
