Hi,
any sugesstions about RX580 8GB how can i overclock it? i have premium version,for example my clocks are 1145 at clock and 2100 for mem but when i try to overclock them they show me max 2000 Mhz at mem how that;s possible? i'm using 18,4 on Ubuntu 16.4
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 119. (Read 703547 times)
December 28, 2019, 02:34:00 PM
December 28, 2019, 05:17:27 AM
Anyone else having problems with awesome miner firmware 3.8.6 on an Antminer L3+?
1) Quiet fan mode on startup straight up doesn't work, fans run full blast on reset
2) Autotune does not restart the miner on the "Restarting..." phase. I have to manually reset to get it to finish.
3) Antminer restarts for no reason every 2-12 hours...nothing in the log, tried every combination of settings, voltages, freqs. Even worse with quiet fan mode not working cause some of my miners are inside.
I used to run the Blissz custom firmware and did not have any of these issues. Support claimed no one else was having these issues, but it's happening on each one of my 35 miners. Can someone with an L3+ verify that they also have these issues?
1) Quiet fan mode on startup straight up doesn't work, fans run full blast on reset
2) Autotune does not restart the miner on the "Restarting..." phase. I have to manually reset to get it to finish.
3) Antminer restarts for no reason every 2-12 hours...nothing in the log, tried every combination of settings, voltages, freqs. Even worse with quiet fan mode not working cause some of my miners are inside.
I used to run the Blissz custom firmware and did not have any of these issues. Support claimed no one else was having these issues, but it's happening on each one of my 35 miners. Can someone with an L3+ verify that they also have these issues?
December 27, 2019, 07:36:42 AM
upd: Solved!
simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Thanks for all detailed feedback and good that you found a workaround. I will look into this scenario to find a better way for Remote Agent to handle it.simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Hi patrike
looks like my solution not works always(( sometimes yes, sometimes no. I have increased delay time, but this caused other problem, service stuck in "pre-start" state after rebooting.
Looks like awesome.service code must better check GPU initialization before delegate control to AwesomeMiner main program.
Hope you solve this quickly. Till this only manual restarting helps.
Regards.
December 27, 2019, 06:46:05 AM
There are times that some browsers have expired SSL and the connection is not secure, for example
https://explorer.zano.org/get_info
It would be nice if these requests left SSL aside, because when making the request AM you don't see the value. If I made the request regardless of SSL or non-SSL, I would always get the value.
Can you schedule the hash and difficulty Explorer requests, so they don't take SSL into account?
I have never used the suppliers, I use them as a reference and every currency that interests me I add the data dynamically and I perform performance tests. I do not serve the data of the providers, they are usually quite bad.
https://explorer.zano.org/get_info
It would be nice if these requests left SSL aside, because when making the request AM you don't see the value. If I made the request regardless of SSL or non-SSL, I would always get the value.
Can you schedule the hash and difficulty Explorer requests, so they don't take SSL into account?
I have never used the suppliers, I use them as a reference and every currency that interests me I add the data dynamically and I perform performance tests. I do not serve the data of the providers, they are usually quite bad.
December 27, 2019, 06:45:34 AM
Hi Patrike, I have not written to you for a long time, you are doing a great job as always, I remind you of an old request from me and I propose a new one.
Old request:
Know in statistics the times you make profit change in 24 hours and for each moment. To determine if that percentage of mining of a coin has done it in 1 change or in 30. It would help me to make better decisions
The other request is an improvement on something existing. I mean temperature control, which is going very well but I explain.
I use both methods, both the general by TDP with its two options and also the core reduction. My scheme is as follows
TDP 1 limitation: 72 degrees, you under the TDP
TDP 2 limitation: 74 degrees, even more under the TDP
Temperature limitation in each OC or core, I have it at 76 degrees
What is the problem ?, Well, it works well, but is constantly jumping temperature. I have a card that according to the Algorithm gets very hot and is always dancing the temperature of 72 to 76 degrees. Because what happens that when it falls to 71 or 72 the limitations are removed and reheated, when it is heated, the limitations are activated and the temperature is lowered, but then the limitations are removed and again heated. I think that so much temperature change, TDP and core can be even bad.
The idea or solution I see simple. If a card activates a temperature limit for example TDP 1, this limit remains active until it changes algorithm or currency. This way we avoid getting the cards receiving a constant change of TDP and CORE all the time. It is logical that if it reaches TDP 1 and 2 and the temperature drops, if we remove the limitation it warms up again. That's why I think it's a better idea to keep the limitations until you change your currency. That way the temperature would be more stable, and I wouldn't be hitting jumps all the time between 72 and 76 as is my case, I don't want it to reach 76 every time.
I hope it is understood and that you see it well as an idea, the implementation is very easy, basically because almost everything is done, just keep limitations until currency exchange, with which the temperature will not be jumping, we are not changing TDP and CORE several times per minute to the card
Old request:
Know in statistics the times you make profit change in 24 hours and for each moment. To determine if that percentage of mining of a coin has done it in 1 change or in 30. It would help me to make better decisions
The other request is an improvement on something existing. I mean temperature control, which is going very well but I explain.
I use both methods, both the general by TDP with its two options and also the core reduction. My scheme is as follows
TDP 1 limitation: 72 degrees, you under the TDP
TDP 2 limitation: 74 degrees, even more under the TDP
Temperature limitation in each OC or core, I have it at 76 degrees
What is the problem ?, Well, it works well, but is constantly jumping temperature. I have a card that according to the Algorithm gets very hot and is always dancing the temperature of 72 to 76 degrees. Because what happens that when it falls to 71 or 72 the limitations are removed and reheated, when it is heated, the limitations are activated and the temperature is lowered, but then the limitations are removed and again heated. I think that so much temperature change, TDP and core can be even bad.
The idea or solution I see simple. If a card activates a temperature limit for example TDP 1, this limit remains active until it changes algorithm or currency. This way we avoid getting the cards receiving a constant change of TDP and CORE all the time. It is logical that if it reaches TDP 1 and 2 and the temperature drops, if we remove the limitation it warms up again. That's why I think it's a better idea to keep the limitations until you change your currency. That way the temperature would be more stable, and I wouldn't be hitting jumps all the time between 72 and 76 as is my case, I don't want it to reach 76 every time.
I hope it is understood and that you see it well as an idea, the implementation is very easy, basically because almost everything is done, just keep limitations until currency exchange, with which the temperature will not be jumping, we are not changing TDP and CORE several times per minute to the card
Hi patrike, happy holidays. I would like you to tell me something about the suggestion I made.
I think the implementation is very easy, 90% is done. It is only to maintain the limitations if they are reached and even if the temperature drops, keep those limitations. Only if you change currency or make a change would you reset
Believe me that I have several cards constantly dancing between 72 and 76 and I do not like anything, and if under the OC it is for the entire Rig, while if a card reaches a limitation, it keeps it, instead of constantly activating and deactivating the limitations and producing a temperature dance. I have already broken one of those cards and I think it's because of the continuous dance, because it always reached the maximum, it went down to 71, it went back up, so 24 hours every day. Too much stress for the card.
Right now there is a limit of 30 seconds between the Power Limit changes. This will only prevent some of the changes - but I understand your point that it still can be too many. Maybe the change should be like this:
- The Power Limit can be decreased no more frequently than 30 seconds after last Power Limit change
- The Power Limit can be increased no more frequently than 5 minutes after last Power Limit change.
This would make the Power Limit go down as fast as today - but it will not be increased so fast again. It will stay on a lower level for some time before it even attempts to go back. So instead of possibly 120 changes per hours as you could have today, this concept would give about 11-12 changes per hour.
This concept would work fine even if you would be mining for a longer period of time - as you don't have to wait for a profit switch. It would also be working for those that doesn't do profit switching and runs the same mining software and pool all the time.
Please let me know what you think. Thanks!
I think it's fine, but that time of 5 minutes could be changed. So by default everyone 5 minutes away, but if I want it, I can put it for 30 minutes for example and so everyone would be happy.
December 27, 2019, 03:23:53 AM
upd: Solved!
simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Thanks for all detailed feedback and good that you found a workaround. I will look into this scenario to find a better way for Remote Agent to handle it. simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
December 27, 2019, 03:22:27 AM
Awesome Miner Version 7.2.3
Features
- Dynamic update of coin statistics can convert the exchange rate even if specified in other coins than BTC
Features
- Dynamic update of coin statistics can convert the exchange rate even if specified in other coins than BTC
How do i use this feature ?
1. api : https://api.coingecko.com/api/v3/simple/price?ids=turtlecoin&vs_currencies=eth
2. json property : turtlecoin.eth
3. arithmetic : helper.ExchangeFrom("ETH")
Error : Unable to read value
Code:
helper.ExchangeFrom("ETH")
toCode:
* helper.ExchangeFrom("ETH")
The expression field is an operation to perform on the value you read. An expression can be like "* 1.2" to increase a value with 20%. In this case it's an expression to multiply the value with the exchange rate of ETH. The result is that you get the Turtlecoin value expressed in ETH, then multiply it with the ETH exchange rate (relative BTC). The result will be the Turtlecoin exchange rate expressed in BTC.
December 26, 2019, 05:56:00 PM
in /lib/systemd/system i have found awesome.service file where you define order when and after which step awesome service must be started:
i see: After=network.target
and this is wrong, HiveOS not ready at this point with GPU initialization. Starting of awesome agent must be later (i dont know when)
I have try: After=hive.service but this not started service automatic. But if i start service manualy after that, all works good.
We need better starting point for awesome.service.
[Unit]
Description=Awesome Miner Remote Agent
After=network.target
[Service]
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Restart=on-failure
KillMode=process
[Install]
WantedBy=multi-user.target
upd: Solved!
simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Maybe developers of Awesome miner linux agent do some improvements and we see better solution in the next releases...
Regards
i see: After=network.target
and this is wrong, HiveOS not ready at this point with GPU initialization. Starting of awesome agent must be later (i dont know when)
I have try: After=hive.service but this not started service automatic. But if i start service manualy after that, all works good.
We need better starting point for awesome.service.
[Unit]
Description=Awesome Miner Remote Agent
After=network.target
[Service]
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Restart=on-failure
KillMode=process
[Install]
WantedBy=multi-user.target
upd: Solved!
simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)
I have added one string in [Service] section in awesome.service file:
[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux
Maybe developers of Awesome miner linux agent do some improvements and we see better solution in the next releases...
Regards
December 26, 2019, 08:57:18 AM
@patrike
Hi boss
looks like AwesomeMiner client for Linux not work properly if installed as a service. After restart/reboot, service not properly manage GPU overclocking, i can only manage power & fan, but not core clock and memory clock.
If i stop service and start again manualy, i can manage fan, power, core, memory.
How to solve this problem?
Linux platform: HiveOS 0.6-105 (on USB flash drive)
Rig: NVIDIA 8 x 2080TI
Drivers: 440.31
Hi boss
looks like AwesomeMiner client for Linux not work properly if installed as a service. After restart/reboot, service not properly manage GPU overclocking, i can only manage power & fan, but not core clock and memory clock.
If i stop service and start again manualy, i can manage fan, power, core, memory.
How to solve this problem?
Linux platform: HiveOS 0.6-105 (on USB flash drive)
Rig: NVIDIA 8 x 2080TI
Drivers: 440.31
December 26, 2019, 01:02:15 AM
Awesome Miner Version 7.2.3
Features
- Dynamic update of coin statistics can convert the exchange rate even if specified in other coins than BTC
Features
- Dynamic update of coin statistics can convert the exchange rate even if specified in other coins than BTC
How do i use this feature ?
1. api : https://api.coingecko.com/api/v3/simple/price?ids=turtlecoin&vs_currencies=eth
2. json property : turtlecoin.eth
3. arithmetic : helper.ExchangeFrom("ETH")
Error : Unable to read value
December 24, 2019, 12:06:09 PM
Hi community!
i want to use HiveOS as operating system for my mining rig and control, overclocking and switching over AwesomeMiner.
but i have a problem to disable autostart in HiveOS configured miner. (in fly sheet)
How to prevent autostart?
upd: solved, simple rename rig.conf file
i want to use HiveOS as operating system for my mining rig and control, overclocking and switching over AwesomeMiner.
but i have a problem to disable autostart in HiveOS configured miner. (in fly sheet)
How to prevent autostart?
upd: solved, simple rename rig.conf file
December 23, 2019, 10:24:04 PM
hello patrike,
I think it would be great if you could add a feature that will allow us to modify the profit estimate stats from profit switching pools, using a C# script or a custom formula.
then instead of using "current estimate/24hr estimate/24hr actual" for profit switching we could use some complicated formulas to improve the profit estimate accuracy - for example, the profit switcher could use arithmetic mean of current estimate and actual 24hr profit, and so on.
what do you think about this?
also, there's a bug with ProHashing 24hr actual profit stats. the values should be multiplied by 1000 to be correct.
thank you
Good point about the profit switcher. I will consider this request.I think it would be great if you could add a feature that will allow us to modify the profit estimate stats from profit switching pools, using a C# script or a custom formula.
then instead of using "current estimate/24hr estimate/24hr actual" for profit switching we could use some complicated formulas to improve the profit estimate accuracy - for example, the profit switcher could use arithmetic mean of current estimate and actual 24hr profit, and so on.
what do you think about this?
also, there's a bug with ProHashing 24hr actual profit stats. the values should be multiplied by 1000 to be correct.
thank you
Thanks for the comment about Prohashing 24h actual as well, I will correct that.
December 23, 2019, 10:08:34 PM
Hi all,
I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
NbMiner should work with dual mining, but unfortunately I've not yet a chance to enable dual mining for Gminer. I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
Thanks Patrike, have been able to get NBMiner to bench ckb+ethash, with a few issues though.
1.
The dual hashrate been recorded by default has been inversed, say, I have 85 MH/s for Eth and 1.2GH/s for Eaglesong, the benchmark will read and record
Code:
Eaglesong (Dual: 85MH/s)
Ethhash (Dual: 1.2GH/s)
Ethhash (Dual: 1.2GH/s)
I'm not sure if that's due to NBminer, when dual mining, it uses eaglesong as primary and ethash as secondary and made the metrics mixed up but I do suspect it to be the culprit.
2.
The dual hashrate and revenue from Eaglesong does not get taken into consideration in profit switching calculation, somehow even when populated with non "0" benchmarks into keccak, lbry, ckb 's dual mining hashrate in profit profiles, the Profit Switching tab for the miner still only lists 2 2ndary algos in my case:
Code:
(incl. Blake 2b:....)
(incl. Tensority:....)
(incl. Tensority:....)
and thus, it won't start dual mining ckb+eth as it isn't in the profitability list.
I have even just enabled only the eth and ckb pool in the profit profile to confirm the behaviour.
December 23, 2019, 09:24:13 PM
is there a problem with mapping cards to hashrate or something like that that no one told until?
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
Try to restart the rig and restart the awesomeminer.
I have the same issue before when the hashrate of the other card is in lower GPU and the lower hashrate is in the high-end GPU. I just rebooted the whole rig and restart and it detects my cards properly in the right position. Also, check the mapping try to play on those settings and change the position of other cards.
have 20 rigs with 6,8 and 12 cards...dont want to "try" - want to know how to fix this without wasting hours of time
btw. restarted rigs and awesome many times since i saw this problem first time - it looks like the problem exist only on AMD rigs
Which mining software is this?
What is a bit difficult for Awesome Miner is to figure out the order of the GPU's reported by the mining software. In many cases you need to resolve it manually via the "Map to system monitoring" dialog. Not only to enable the mapping, but also to use this dialog to move the GPU's up or down in the list to match the hashrates reported from the mining software.
December 23, 2019, 04:19:21 AM
hello patrike,
I think it would be great if you could add a feature that will allow us to modify the profit estimate stats from profit switching pools, using a C# script or a custom formula.
then instead of using "current estimate/24hr estimate/24hr actual" for profit switching we could use some complicated formulas to improve the profit estimate accuracy - for example, the profit switcher could use arithmetic mean of current estimate and actual 24hr profit, and so on.
what do you think about this?
also, there's a bug with ProHashing 24hr actual profit stats. the values should be multiplied by 1000 to be correct.
thank you
I think it would be great if you could add a feature that will allow us to modify the profit estimate stats from profit switching pools, using a C# script or a custom formula.
then instead of using "current estimate/24hr estimate/24hr actual" for profit switching we could use some complicated formulas to improve the profit estimate accuracy - for example, the profit switcher could use arithmetic mean of current estimate and actual 24hr profit, and so on.
what do you think about this?
also, there's a bug with ProHashing 24hr actual profit stats. the values should be multiplied by 1000 to be correct.
thank you
December 22, 2019, 08:18:41 PM
Hi all,
I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
NbMiner should work with dual mining, but unfortunately I've not yet a chance to enable dual mining for Gminer. I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
Thanks Patrike, have been able to get NBMiner to bench ckb+ethash, with a few issues though.
1.
The dual hashrate been recorded by default has been inversed, say, I have 85 MH/s for Eth and 1.2GH/s for Eaglesong, the benchmark will read and record
Code:
Eaglesong (Dual: 85MH/s)
Ethhash (Dual: 1.2GH/s)
Ethhash (Dual: 1.2GH/s)
I'm not sure if that's due to NBminer, when dual mining, it uses eaglesong as primary and ethash as secondary and made the metrics mixed up but I do suspect it to be the culprit.
2.
The dual hashrate and revenue from Eaglesong does not get taken into consideration in profit switching calculation, somehow even when populated with non "0" benchmarks into keccak, lbry, ckb 's dual mining hashrate in profit profiles, the Profit Switching tab for the miner still only lists 2 2ndary algos in my case:
Code:
(incl. Blake 2b:....)
(incl. Tensority:....)
(incl. Tensority:....)
and thus, it won't start dual mining ckb+eth as it isn't in the profitability list.
I have even just enabled only the eth and ckb pool in the profit profile to confirm the behaviour.
December 22, 2019, 01:44:17 PM
is there a problem with mapping cards to hashrate or something like that that no one told until?
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
Try to restart the rig and restart the awesomeminer.
I have the same issue before when the hashrate of the other card is in lower GPU and the lower hashrate is in the high-end GPU. I just rebooted the whole rig and restart and it detects my cards properly in the right position. Also, check the mapping try to play on those settings and change the position of other cards.
have 20 rigs with 6,8 and 12 cards...dont want to "try" - want to know how to fix this without wasting hours of time
btw. restarted rigs and awesome many times since i saw this problem first time - it looks like the problem exist only on AMD rigs
December 22, 2019, 01:37:06 PM
is there a problem with mapping cards to hashrate or something like that that no one told until?
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
Try to restart the rig and restart the awesomeminer.
I have the same issue before when the hashrate of the other card is in lower GPU and the lower hashrate is in the high-end GPU. I just rebooted the whole rig and restart and it detects my cards properly in the right position. Also, check the mapping try to play on those settings and change the position of other cards.
December 22, 2019, 08:48:59 AM
is there a problem with mapping cards to hashrate or something like that that no one told until?
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
https://ibb.co/Nn9SkrX
the "Performance" tab dont show the right GPU
the same shows in "Map to system monitoring"
December 22, 2019, 08:35:26 AM
Hi all,
I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
NbMiner should work with dual mining, but unfortunately I've not yet a chance to enable dual mining for Gminer. I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?
I somehow couldn't get it working automatically and wonder if I missed anything.
Jump to: