[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 205.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on February 13, 2019, 04:08:55 AM

Quote from: trucobit on February 12, 2019, 10:15:35 PM

Quote from: patrike on February 12, 2019, 05:42:21 AM

Quote from: crazydane on February 10, 2019, 04:07:15 PM

Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.

I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.

Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.

I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.

In general you should be able to view the mining income via External Miners as well. I just did some tests with Gminer here and I could see the issue you describe. The problem is that Awesome Miner didn't report any pool in this case, resulting in that the Pools tab wasn't updated correctly when you select the miner and the Define Pool Coin didn't work either.

A solution will be available in the next release. Thanks for finding it.

Ok, everything understood. I have already changed all the equipment to native OC, it works very well and the change is minimal. I only had the doubt of where to look at the oc that had been applied, once I looked at it. I no longer have problems.

MSI SERVER goes well but when it fails in 1 rig, you have to change the name and the folder and the task in all the machines. That was very annoying, it has already happened 12 times ..... I hope that with the native system everything is more stable.

The only thing I'm going to miss, is to see temperature graphs, but I can live without that.

Everything is better if you manage it AM natively, I do not do extreme OC, but I look for a configuration without exaggerating for each OC, now everything is much more controlled.

Thanks for the nice feedback on the new Native Overclocking feature.

I also have great news about the nVidia RTX GPU's - the fan control will very soon be supported. Once the implementation is ready and tested, it will be part of the next development release.

What a good update and how many new features in GPU now review them.

I have seen with pleasure the arrangement of the coins per day, and in the first tests and measurements, now if it is correct, it did not affect the profit but it was very confusing. Now it shows a correct number and works as it should.

When I see the GPU news, if I have questions, I will ask, I already use only the native mode

patrike

legendary

Activity: 3346

Merit: 1094

Awesome Miner version 6.1.13 (Development preview of 6.2)

GPU mining
- Native overclocking supports fan control for nVidia RTX 2000-series GPU
- Managed Profit Miners can be configured with a default GPU clocking profile to be used if there are no clocking configured for an algorithm in the Profit Profile.
- The benchmark can be configured to not automatically apply clocking according to configured profiles. Can be used when manually testing different GPU clocking settings.
Features
- The View GPU Details feature can be accessed from either the Diagnostics dialog or the GPU settings dialog. Includes detailed information about all GPUs.
- The display of Coins per day will take the coin profit factor into consideration
- Show Managed Miner uptime even if not reported via the mining software API
User interface
- Removed gradient for the lower panel in the Miners tab
- Updated coin images
- Consistently use GPU clocking to refer to the dialog where GPU overclocking and GPU settings are being performed
Mining software
- Bminer 14.3.1
- CcMiner KlausT 1.24
Corrections
- Correction to pool display for External Miners connected to Gminer

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

Direct download links
http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
http://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on February 12, 2019, 10:15:35 PM

Quote from: patrike on February 12, 2019, 05:42:21 AM

Quote from: crazydane on February 10, 2019, 04:07:15 PM

Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.

I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.

Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.

I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.

In general you should be able to view the mining income via External Miners as well. I just did some tests with Gminer here and I could see the issue you describe. The problem is that Awesome Miner didn't report any pool in this case, resulting in that the Pools tab wasn't updated correctly when you select the miner and the Define Pool Coin didn't work either.

A solution will be available in the next release. Thanks for finding it.

Ok, everything understood. I have already changed all the equipment to native OC, it works very well and the change is minimal. I only had the doubt of where to look at the oc that had been applied, once I looked at it. I no longer have problems.

MSI SERVER goes well but when it fails in 1 rig, you have to change the name and the folder and the task in all the machines. That was very annoying, it has already happened 12 times ..... I hope that with the native system everything is more stable.

The only thing I'm going to miss, is to see temperature graphs, but I can live without that.

Everything is better if you manage it AM natively, I do not do extreme OC, but I look for a configuration without exaggerating for each OC, now everything is much more controlled.

Thanks for the nice feedback on the new Native Overclocking feature.

I also have great news about the nVidia RTX GPU's - the fan control will very soon be supported. Once the implementation is ready and tested, it will be part of the next development release.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on February 12, 2019, 05:42:21 AM

Quote from: crazydane on February 10, 2019, 04:07:15 PM

Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.

I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.

Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.

I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.

In general you should be able to view the mining income via External Miners as well. I just did some tests with Gminer here and I could see the issue you describe. The problem is that Awesome Miner didn't report any pool in this case, resulting in that the Pools tab wasn't updated correctly when you select the miner and the Define Pool Coin didn't work either.

A solution will be available in the next release. Thanks for finding it.

Ok, everything understood. I have already changed all the equipment to native OC, it works very well and the change is minimal. I only had the doubt of where to look at the oc that had been applied, once I looked at it. I no longer have problems.

MSI SERVER goes well but when it fails in 1 rig, you have to change the name and the folder and the task in all the machines. That was very annoying, it has already happened 12 times ..... I hope that with the native system everything is more stable.

The only thing I'm going to miss, is to see temperature graphs, but I can live without that.

Everything is better if you manage it AM natively, I do not do extreme OC, but I look for a configuration without exaggerating for each OC, now everything is much more controlled.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on February 12, 2019, 10:24:17 AM

Quote from: patrike on February 08, 2019, 04:22:21 AM

Quote from: trucobit on February 07, 2019, 11:01:01 AM

Apperance > customize progress
"Coins/day: " + Math.Round(miningHelper.GetCoinsPerDay(), 4)

@patrike, I have a little problem. I leave you a capture so you can see that by configuration I added the coins per day.

The problem is the following. When I change the profit in a currency, this is reflected in the daily profit, even in coins that you recently included. But the coins per day do not change. It does not matter if I put 0.7 that the 1.5 coins per day that I calculate do not change, I understand why the profit factor does not affect the formula for the stamping of coins a day.

For me it is important, because when measuring pools / currencies to know their real profit and then put the resulting profit, this is not reflected in the currencies per day.

Please could you tell me how to improve the configuration line or that you fix it in the next update. It does not make sense for a currency to put a profit of 0.80, effectively falling into the daily profit, but the coins remain the same.

My recommendation, in my ignorance, is that it would be more appropriate for the PROFIT factor to affect the HASH, in that way it will affect the price and the coins per day.

I think that from what I see, the profit only affects the price, therefore it does not affect the currencies per day because it is fixed in the HASH

I hope to give some solution

This is actually a good point.

Right now the Profit Factor is applied after calculating the number of coins, to increase/decrease the revenue and profit of the coin. A better way of viewing it is to increase/decrease the number of coins you get per day like you point out. I will update the next release for this to at least consider the Profit Factor of a coin. It will unfortunately be a bit complex if you also consider the Pool Profit Factor here, but I will take a look at what is possible for that one as well.

Edit: I've implemented this for Pool Profit Factor as well

I am impatient waiting for an update with the correction of the currencies .... It is important that the profit affects the currencies day. I am realizing with grin, where I estimate 7.4, it does not matter what elprofit I put, and I get around 4.8, if my profit of 0.80 were applied, it would be close enough. But now it is difficult to measure pools / coins without that correct information.

There will be a new development version available within the next 1-2 days where the change is included.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on February 12, 2019, 10:22:03 AM

Quote from: patrike on February 10, 2019, 11:34:50 AM

Quote from: trucobit on February 08, 2019, 01:11:31 PM

I just did a test in a small rig. I have stopped MSI SERVER and in AM I have put the OC to be awesome miner.

I have forced several changes of something with different OC but in the rig the OC has not moved. I have left Aftherburner installed to know if the OC changes.

When I finished testing I went back to the usual with MSI SERVER and changed to AM and left it as usual.

That rig gave me problems, I had to go to the GPU and do the Mapping of the GPUs again to make it work.

As you said no info in your documentation please post the link here when you update it. I would like to use the most stable system. Sometimes the MSI SERVER stops working and you have to change the name of the folder in all the RIGS.

Right now I'm still with Aftherburne and MSI SERVER until there's more information on how to use your new OC version correctly.

I've updated the documentation page for GPU overclocking. It also contains information about how to troubleshoot if needed.
https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

Please note that for several of the OC settings, it's not possible to use MSI Afterburner to detect if it's applied correctly. For some settings, MSI Afterburner must be restarted for the new settings to show up and for a few other settings MSI Afterburner have it's own way of reading/setting clocking so any changes you define using other applications will not show up. For this reason I pointed out in the documentation that you should use the Reload-button in Awesome Miner to verify the settings.

You refer to that button on the right, restart monitoring? If that is the case, you could make the restart every single change of OC. Aftherburner is good because at first glance you can see the OC applied, here it does not seem so easy to know the OC. You could show the name of the OC profile in the Coins tab

The other problem is RTX, if it is not able to handle the fans, what happens? Use the auto factory curve or change that speed even if it is auto.

You will find the "Reload" button in the GPU settings dialog. Please see the screenshot below:
https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/35035563191/original/8L1-EJMif7gbZAi0OwGVkHxybSqvwDrfng?1549753601

There is no need to click the Reload button all the time - it's mainly intended for reloading all data you currently see in the GPU settings dialog for troubleshooting purposes. You can always open the GPU settings dialog to view the current clocking properties.

For the moment, the Native Overclocking will not touch the fan property on RTX cards. If you have them on "auto" speed which is the default, they will remain at "auto" even when you use Awesome Miner. If you used any other application to force a specific fan speed, that specific fan speed will remain.

The plan is of course to resolve this limitation.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on February 08, 2019, 04:22:21 AM

Quote from: trucobit on February 07, 2019, 11:01:01 AM

Apperance > customize progress
"Coins/day: " + Math.Round(miningHelper.GetCoinsPerDay(), 4)

@patrike, I have a little problem. I leave you a capture so you can see that by configuration I added the coins per day.

The problem is the following. When I change the profit in a currency, this is reflected in the daily profit, even in coins that you recently included. But the coins per day do not change. It does not matter if I put 0.7 that the 1.5 coins per day that I calculate do not change, I understand why the profit factor does not affect the formula for the stamping of coins a day.

For me it is important, because when measuring pools / currencies to know their real profit and then put the resulting profit, this is not reflected in the currencies per day.

Please could you tell me how to improve the configuration line or that you fix it in the next update. It does not make sense for a currency to put a profit of 0.80, effectively falling into the daily profit, but the coins remain the same.

My recommendation, in my ignorance, is that it would be more appropriate for the PROFIT factor to affect the HASH, in that way it will affect the price and the coins per day.

I think that from what I see, the profit only affects the price, therefore it does not affect the currencies per day because it is fixed in the HASH

I hope to give some solution

This is actually a good point.

Right now the Profit Factor is applied after calculating the number of coins, to increase/decrease the revenue and profit of the coin. A better way of viewing it is to increase/decrease the number of coins you get per day like you point out. I will update the next release for this to at least consider the Profit Factor of a coin. It will unfortunately be a bit complex if you also consider the Pool Profit Factor here, but I will take a look at what is possible for that one as well.

Edit: I've implemented this for Pool Profit Factor as well

I am impatient waiting for an update with the correction of the currencies .... It is important that the profit affects the currencies day. I am realizing with grin, where I estimate 7.4, it does not matter what elprofit I put, and I get around 4.8, if my profit of 0.80 were applied, it would be close enough. But now it is difficult to measure pools / coins without that correct information.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on February 10, 2019, 11:34:50 AM

Quote from: trucobit on February 08, 2019, 01:11:31 PM

I just did a test in a small rig. I have stopped MSI SERVER and in AM I have put the OC to be awesome miner.

I have forced several changes of something with different OC but in the rig the OC has not moved. I have left Aftherburner installed to know if the OC changes.

When I finished testing I went back to the usual with MSI SERVER and changed to AM and left it as usual.

That rig gave me problems, I had to go to the GPU and do the Mapping of the GPUs again to make it work.

As you said no info in your documentation please post the link here when you update it. I would like to use the most stable system. Sometimes the MSI SERVER stops working and you have to change the name of the folder in all the RIGS.

Right now I'm still with Aftherburne and MSI SERVER until there's more information on how to use your new OC version correctly.

I've updated the documentation page for GPU overclocking. It also contains information about how to troubleshoot if needed.
https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

Please note that for several of the OC settings, it's not possible to use MSI Afterburner to detect if it's applied correctly. For some settings, MSI Afterburner must be restarted for the new settings to show up and for a few other settings MSI Afterburner have it's own way of reading/setting clocking so any changes you define using other applications will not show up. For this reason I pointed out in the documentation that you should use the Reload-button in Awesome Miner to verify the settings.

You refer to that button on the right, restart monitoring? If that is the case, you could make the restart every single change of OC. Aftherburner is good because at first glance you can see the OC applied, here it does not seem so easy to know the OC. You could show the name of the OC profile in the Coins tab

The other problem is RTX, if it is not able to handle the fans, what happens? Use the auto factory curve or change that speed even if it is auto.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on February 11, 2019, 08:53:19 PM

----------------------------
Troubleshooting
Use the GPU settings dialog, via the toolbar Tools -> GPU Settings) for adjusting GPU settings on a single GPU to verify that all settings works as expected
To verify if the GPU settings were applied successfully, use the Reload button in the GPU settings dialog to reload all properties from the AMD and nVidia GPU drivers.
If the values show up as expected, the GPU settings and overclocking operations have been successfully applied
If one or more settings didn't have the expected value, please report which GPU model and which setting that didn't work together with the Awesome Miner log file.
Do not use the MSI Afterburner application to check if the GPU settings were applied successfully. MSI Afterburner uses different overclocking concepts than other applications and may not display the current GPU settings correctly when set from other applications.
-----------------------------------

I have done a test and I do not see results. On one side of his help he says that you have to reload or update to see if the changes are reflected. I could leave a capture of that menu, sometimes the translations are not perfect.

It is not advisable to have MSI aftherburner installed, but it also does not indicate whether a change has been made. That's why it's important that you identify that GPU window for the native OC

If the native mode is not compatible with the RTX fans. How do we control them? Do they only go by car?

For me the important thing is to know if the OC changes are applied using the native mode, but I do not identify which part of the program I have to give to see the changes, I would appreciate a capture.

-------------

Bminer problems.

Now I have been seeing that if it is true that it does not need to include the -al-go in the miner's configuration. In fact it works for me with many algos, but when I tried it it was with tensory and there if it is true that it does not work, I suppose it will be the miner's own fault.

Just to clarify, it's no problem at all to have MSI Afterburner installed at the same time as you use the Native Overclocking in Awesome Miner.

The point is that MSI Afterburner works a bit differently than other overclocking tools you will find, and even if an application correctly set some GPU properties and clocks - there are scenarios where MSI Afterburner simply doesn't show all these changes in the user interface.

For this reason it's very difficult to use MSI Afterburner to verify if specific clocking settings have been successfully applied or not.

When testing and doing troubleshooting, it's typically better to use the "Reload" button in Awesome Miner. When you click this one Awesome Miner will forget about all GPU properties and read all the values from the nVidia/AMD driver API's again. If the clocking properties show up correctly after a "Reload" it's a good indications that they have been set correctly.

Example of how you can test the clocking with Awesome Miner, using the GPU settings dialog
1) Change one or several properties, like Core Clock Boost, Memory Clock Boost, Power Limit, ...
2) Click Apply. Now all settings should be applied
3) If you want to verify, click the Reload button. Awesome Miner will ask the nVidia/AMD drivers for the current settings and display them.
4) In case a property isn't what you expect it to be, please let me know:
a) GPU model
b) Name of the Property that didn't work and what you tried to set it to
c) The log file from the Remote Agent

You can also find many GPU related properties via the new "GPU Report" button in the Diagnostics dialog. I will also add this button to the GPU settings dialog in the next release. This one will be really good for seeing all GPU properties.

For RTX-2000 fans, I think MSI Afterburner is the only application that can modify it right now and they must have some secret way of doing that. I don't think any other OC application can modify the fan speed of RTX cards yet as the nVidia driver API reports that it isn't supported and prevents it. The plan is of course to try to find a way to support setting fan speed on these GPU's as well.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: crazydane on February 10, 2019, 04:07:15 PM

Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.

I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.

Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.

I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.

In general you should be able to view the mining income via External Miners as well. I just did some tests with Gminer here and I could see the issue you describe. The problem is that Awesome Miner didn't report any pool in this case, resulting in that the Pools tab wasn't updated correctly when you select the miner and the Define Pool Coin didn't work either.

A solution will be available in the next release. Thanks for finding it.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: crazydane on February 10, 2019, 12:11:20 PM

Quote from: patrike on February 10, 2019, 11:39:23 AM

I assume you only have one single Host for this Linux miner defined in the Options dialog, Managed Hosts section. This host must have the "Linux" checkbox active and there shouldn't be any other hosts in the list connecting to the same computer. Can you verify this?

Yes, I only have a single host defined for this specific miner. I did have a windows hosts defined previously that I deleted and replaced with the nvOC based one. But this was also the case for the first rig that I converted from Windows to nvOC. One note on this is that I had to restart AM before it would "pick up" the first rig that I switched from windows to nvOC. And yes, I do have the "Linux" checkbox checked.

Quote

Can you also review the Awesome Miner application log file for any error message about this connection problem?

How do I access this log?

Also, will setting GPU clocks, power levels and fan control be a future option for the Linux remote agent?

btw, I really like the recently added native control of these with the windows version. So much simpler than having to use the Afterburner remote agent.

One thing I found is that I had to re-create my GPU Clocking Profiles as the old ones did not include the temp target values.

Thanks for the update.

The Awesome Miner log file can be found via the toolbar Tools -> Log File.

The latest development release of Awesome Miner includes GPU clocking and fan speed changes on Linux as well. This will be part of the public 6.2 release, planned to be available in a few days.

Thanks for the nice feedback on the Native Overclocking feature. The main purpose is that it should be easier to use. Your observations about which GPU properties that are available via MSI Afterburner and Awesome Miner may not always be the same - depending on which GPU's you have.

trucobit

jr. member

Activity: 756

Merit: 2

----------------------------
Troubleshooting
Use the GPU settings dialog, via the toolbar Tools -> GPU Settings) for adjusting GPU settings on a single GPU to verify that all settings works as expected
To verify if the GPU settings were applied successfully, use the Reload button in the GPU settings dialog to reload all properties from the AMD and nVidia GPU drivers.
If the values show up as expected, the GPU settings and overclocking operations have been successfully applied
If one or more settings didn't have the expected value, please report which GPU model and which setting that didn't work together with the Awesome Miner log file.
Do not use the MSI Afterburner application to check if the GPU settings were applied successfully. MSI Afterburner uses different overclocking concepts than other applications and may not display the current GPU settings correctly when set from other applications.
-----------------------------------

I have done a test and I do not see results. On one side of his help he says that you have to reload or update to see if the changes are reflected. I could leave a capture of that menu, sometimes the translations are not perfect.

It is not advisable to have MSI aftherburner installed, but it also does not indicate whether a change has been made. That's why it's important that you identify that GPU window for the native OC

If the native mode is not compatible with the RTX fans. How do we control them? Do they only go by car?

For me the important thing is to know if the OC changes are applied using the native mode, but I do not identify which part of the program I have to give to see the changes, I would appreciate a capture.

-------------

Bminer problems.

Now I have been seeing that if it is true that it does not need to include the -al-go in the miner's configuration. In fact it works for me with many algos, but when I tried it it was with tensory and there if it is true that it does not work, I suppose it will be the miner's own fault.

moppidoo

jr. member

Activity: 348

Merit: 5

Quote from: GoRdiE on February 10, 2019, 04:35:30 PM

Quote from: patrike on February 10, 2019, 11:54:04 AM

Quote from: GoRdiE on February 08, 2019, 08:05:03 PM

Hello Patrike.

I think the Native overclocking does not work correctly or I can not configure it correctly. First, I do not understand why when we create an OC profile, we have to choose a particular miner and then a card. I guess a link is created between the OC profile and the miner or the card, right? I think this fact can be a headache because the ideal is to use it automatically in each algorithm that is needed applied only to profite profiles. Well, I'll explain. I have two different cards, one 1070ti and one 2070, and I have created several different OCs. The fact is that I apply the OC that I consider in the algorithms that I consider in each different profite profile, which is how we finally identify each one of the miners that we have. The fact is that when applied in a profite profile, the power limit is respected, but both the Core and the Mem are activated in the other profit profiles although they are not activated in the second. Logically, I keep the AB to see how the OC behaves. Can it be by using the option to clone profiles? Something does not work correctly Huh

To provide more information:

I started to realize when I noticed that some miners gave me an error. This happened because I have an OC for 2070 wild memory (+850) that the 1070ti can not support. The fact is that when the OC was activated for 2070, the 1070ti gave error by hanging the miner.

In this rig I only have two cards, but I have one rig with 6 cards and with 3 different types and I was going crazy

Another thing:

At the beginning I tried using the AB OC, since I have OC profiles in curve mode for the Core, that is, the AB allows you to create curved profiles for the different memory sets, so if your card is stable to +500 mem with Core +200 in power 70%, it is possible that with power 100% it is not, and these curved profiles allow you a stable OC setting only Mem, and vary the Core according to the Power that you set. The fact is that in the first tests, I left without clicking the Core, so that AM respected the core of the AB. The result is that when activated in a defined algorithm, it is respected, but at the same time the value is fixed in the AM, so in successive Oc profiles in AM, the core is fixed in advance, not respecting the changing value of the OC curve. I do not know if I explain myself very well.

This last one is the reason why I have rejected to do OC with the AB and to put myself with the native one, finding the problem exposed to me first.

The Clocking Profile concept will be redesigned soon. The difficulty is that depending on which GPU you have, the clocking properties are different. Some cards support Target Temperature while others don't, and so on. By forcing you to setup a Clocking Profile based on what a specific card supports will make sure you don't try to set properties that isn't supported.

Please note that as soon as you save the Clocking Profile, it has no link to the specific miner or GPU, and it can be applied to any miner and and GPU. If you try to apply it to a GPU where a property isn't supported, that specific property will be ignored.

Just like before when you used MSI Afterburner, you have to define a Clocking Group if you have a mix of GPU types and want to specify a unique profile for each GPU type.

The curve you are referring to, I assume it's the one in the "Voltage/Frequency curve editor" inside MSI Afterburner? Awesome Miner doesn't support this VFC feature yet but it's on the todo-list.

Hello Patrike, and thanks in advance for your attention.
I understand what you tell me and this is how I have done it. I explain it better.

I have two GPUs, one 1070 and another 2070.
I have 2 miners. 1070 and 2070
I have two profit profiles 1070 and 2070
I create an OC profile and apply it only to some algorithms of the profit profile 1070.

What I am saying is that when the OC is activated in profile 1070, it also applies in profit profile 2070 (and in this case it is clean of OC in the AM). When the OC is activated, the OC is applied to the two profit profiles and therefore to both cards and to both miners, when it should not be so, it should be applied only in the profit profile 1070, right?

At least in my case, so I do not know if I'm missing something in the configurations.

Regarding the second theme, yes, the curve I am referring to is the one in the "Voltage / Frequency curve editor"

Regards

EDIT:

Excuse, the OC is applied in both the Core and the Mem, The PL is OK (not applied in both)

***
Did you tried Clocking Profile Groups like patrike mentioned? I think (might be wrong) you'd need that even if you separate the miners.

GoRdiE

newbie

Activity: 162

Merit: 0

Quote from: patrike on February 10, 2019, 11:54:04 AM

Quote from: GoRdiE on February 08, 2019, 08:05:03 PM

Hello Patrike.

I think the Native overclocking does not work correctly or I can not configure it correctly. First, I do not understand why when we create an OC profile, we have to choose a particular miner and then a card. I guess a link is created between the OC profile and the miner or the card, right? I think this fact can be a headache because the ideal is to use it automatically in each algorithm that is needed applied only to profite profiles. Well, I'll explain. I have two different cards, one 1070ti and one 2070, and I have created several different OCs. The fact is that I apply the OC that I consider in the algorithms that I consider in each different profite profile, which is how we finally identify each one of the miners that we have. The fact is that when applied in a profite profile, the power limit is respected, but both the Core and the Mem are activated in the other profit profiles although they are not activated in the second. Logically, I keep the AB to see how the OC behaves. Can it be by using the option to clone profiles? Something does not work correctly Huh

To provide more information:

I started to realize when I noticed that some miners gave me an error. This happened because I have an OC for 2070 wild memory (+850) that the 1070ti can not support. The fact is that when the OC was activated for 2070, the 1070ti gave error by hanging the miner.

In this rig I only have two cards, but I have one rig with 6 cards and with 3 different types and I was going crazy

Another thing:

At the beginning I tried using the AB OC, since I have OC profiles in curve mode for the Core, that is, the AB allows you to create curved profiles for the different memory sets, so if your card is stable to +500 mem with Core +200 in power 70%, it is possible that with power 100% it is not, and these curved profiles allow you a stable OC setting only Mem, and vary the Core according to the Power that you set. The fact is that in the first tests, I left without clicking the Core, so that AM respected the core of the AB. The result is that when activated in a defined algorithm, it is respected, but at the same time the value is fixed in the AM, so in successive Oc profiles in AM, the core is fixed in advance, not respecting the changing value of the OC curve. I do not know if I explain myself very well.

This last one is the reason why I have rejected to do OC with the AB and to put myself with the native one, finding the problem exposed to me first.

The Clocking Profile concept will be redesigned soon. The difficulty is that depending on which GPU you have, the clocking properties are different. Some cards support Target Temperature while others don't, and so on. By forcing you to setup a Clocking Profile based on what a specific card supports will make sure you don't try to set properties that isn't supported.

Please note that as soon as you save the Clocking Profile, it has no link to the specific miner or GPU, and it can be applied to any miner and and GPU. If you try to apply it to a GPU where a property isn't supported, that specific property will be ignored.

Just like before when you used MSI Afterburner, you have to define a Clocking Group if you have a mix of GPU types and want to specify a unique profile for each GPU type.

The curve you are referring to, I assume it's the one in the "Voltage/Frequency curve editor" inside MSI Afterburner? Awesome Miner doesn't support this VFC feature yet but it's on the todo-list.

Hello Patrike, and thanks in advance for your attention.
I understand what you tell me and this is how I have done it. I explain it better.

I have two GPUs, one 1070 and another 2070.
I have 2 miners. 1070 and 2070
I have two profit profiles 1070 and 2070
I create an OC profile and apply it only to some algorithms of the profit profile 1070.

What I am saying is that when the OC is activated in profile 1070, it also applies in profit profile 2070 (and in this case it is clean of OC in the AM). When the OC is activated, the OC is applied to the two profit profiles and therefore to both cards and to both miners, when it should not be so, it should be applied only in the profit profile 1070, right?

At least in my case, so I do not know if I'm missing something in the configurations.

Regarding the second theme, yes, the curve I am referring to is the one in the "Voltage / Frequency curve editor"

Regards

EDIT:

https://i.imgur.com/kmnyksS.jpg
https://i.imgur.com/0eYN2V4.jpg

https://i.imgur.com/767C39S.jpg
https://i.imgur.com/Syx04CH.jpg

Excuse, the OC is applied in both the Core and the Mem, The PL is OK (not applied in both)

crazydane

full member

Activity: 558

Merit: 194

Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.

I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.

Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.

I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.

crazydane

full member

Activity: 558

Merit: 194

Quote from: patrike on February 10, 2019, 11:39:23 AM

I assume you only have one single Host for this Linux miner defined in the Options dialog, Managed Hosts section. This host must have the "Linux" checkbox active and there shouldn't be any other hosts in the list connecting to the same computer. Can you verify this?

Yes, I only have a single host defined for this specific miner. I did have a windows hosts defined previously that I deleted and replaced with the nvOC based one. But this was also the case for the first rig that I converted from Windows to nvOC. One note on this is that I had to restart AM before it would "pick up" the first rig that I switched from windows to nvOC. And yes, I do have the "Linux" checkbox checked.

Quote

Can you also review the Awesome Miner application log file for any error message about this connection problem?

How do I access this log?

Also, will setting GPU clocks, power levels and fan control be a future option for the Linux remote agent?

btw, I really like the recently added native control of these with the windows version. So much simpler than having to use the Afterburner remote agent.

One thing I found is that I had to re-create my GPU Clocking Profiles as the old ones did not include the temp target values.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: moppidoo on February 09, 2019, 11:30:17 PM

Quote from: trucobit on February 09, 2019, 11:03:53 AM

Quote from: powerstr on February 08, 2019, 10:12:15 PM

bminer-v14.3.0-cbb8683-amd64

https://bitcointalksearch.org/topic/annbminer-a-fast-equihashethashcuckaroo29z-miner-for-amdnvidia-gpus-1649-2519271
It can not be that, several people in my telegram group have the same url, which is the default one in AM and to them if it works, although it does not include the ticket of each a-l-g-o

It is the default download on your page, you can see it on the Ann link of BTC talk
and also I repeat that it is the one that AM includes by default

What is your Bminer url in the options> managed software> BMINER panel?

Default AM BMiner URL for version v6.1.12 is:

Code:

https://www.bminercontent.com/releases/bminer-v14.1.0-373029c-amd64.zip

This requires CUDA 10 and I have not used this version since not all my rigs are migrated to the CUDA 10 drivers.

BMiner doesn't require the algo input parameter and thus the screen says you're unable to configure command line arguments in the said screenshot. I beleive it just negotiates and choose the algo automatically when connecting to pool stratums.

You may need to deliberately run diagnostics and see the output as to why it hasn't been working properly for you, either manually execute the command line through command prompt window, via .bat file, or if you want to do it in AM for a profit miner, probably easiest to do is to

-> Duplicate a profile (or just create a blank profile) for the problematic miner
-> Disable all software except bminer in profit profile
-> Optional (artificially inflate hashrate one of the BMiner supported algos that you have identified as problematic)
-> Assign the problematic miner with this temporary profit profile
-> Right click -> Diagnostics
-> Share the output of the diagnostics and see if anyone can pickup what might be wrong if it's not trivial.

Thanks for sharing all good points above.

I just wanted to give a short comment about why Awesome Miner don't have the algorithm names listed in the Managed Software dialog for Bminer.

For most mining software you have a concept of a command line argument specifying the algorithm, for example "phi2" that will give the result "-a phi2" for example. Using the Managed Software dialog you can customize this per algorithm to make it "phi2 -I 15" resulting in "-a phi2 -I 15".

For Bminer you don't have a separate command line argument for the algorithm name, instead it's part of the generated URL parameter that looks something like "cuckaroo29://username:[email protected]:13654" where Awesome Miner automatically set the part "cuckaroo29" based on the algorithm you have for the pool/coin. As the algorithm argument is part of the URL with Bminer, it's not possible to simply add additional command line arguments to it with the current design.

I agree with all troubleshooting steps above. The Diagnostics button is my best friend

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: GoRdiE on February 08, 2019, 08:05:03 PM

Hello Patrike.

I think the Native overclocking does not work correctly or I can not configure it correctly. First, I do not understand why when we create an OC profile, we have to choose a particular miner and then a card. I guess a link is created between the OC profile and the miner or the card, right? I think this fact can be a headache because the ideal is to use it automatically in each algorithm that is needed applied only to profite profiles. Well, I'll explain. I have two different cards, one 1070ti and one 2070, and I have created several different OCs. The fact is that I apply the OC that I consider in the algorithms that I consider in each different profite profile, which is how we finally identify each one of the miners that we have. The fact is that when applied in a profite profile, the power limit is respected, but both the Core and the Mem are activated in the other profit profiles although they are not activated in the second. Logically, I keep the AB to see how the OC behaves. Can it be by using the option to clone profiles? Something does not work correctly Huh

To provide more information:

I started to realize when I noticed that some miners gave me an error. This happened because I have an OC for 2070 wild memory (+850) that the 1070ti can not support. The fact is that when the OC was activated for 2070, the 1070ti gave error by hanging the miner.

In this rig I only have two cards, but I have one rig with 6 cards and with 3 different types and I was going crazy

Another thing:

At the beginning I tried using the AB OC, since I have OC profiles in curve mode for the Core, that is, the AB allows you to create curved profiles for the different memory sets, so if your card is stable to +500 mem with Core +200 in power 70%, it is possible that with power 100% it is not, and these curved profiles allow you a stable OC setting only Mem, and vary the Core according to the Power that you set. The fact is that in the first tests, I left without clicking the Core, so that AM respected the core of the AB. The result is that when activated in a defined algorithm, it is respected, but at the same time the value is fixed in the AM, so in successive Oc profiles in AM, the core is fixed in advance, not respecting the changing value of the OC curve. I do not know if I explain myself very well.

This last one is the reason why I have rejected to do OC with the AB and to put myself with the native one, finding the problem exposed to me first.

Thanks for taking the time to try out this.

The Clocking Profile concept will be redesigned soon. The difficulty is that depending on which GPU you have, the clocking properties are different. Some cards support Target Temperature while others don't, and so on. By forcing you to setup a Clocking Profile based on what a specific card supports will make sure you don't try to set properties that isn't supported.

Please note that as soon as you save the Clocking Profile, it has no link to the specific miner or GPU, and it can be applied to any miner and and GPU. If you try to apply it to a GPU where a property isn't supported, that specific property will be ignored.

Just like before when you used MSI Afterburner, you have to define a Clocking Group if you have a mix of GPU types and want to specify a unique profile for each GPU type.

I've also updated the documentation for GPU overclocking with the Native feature and some troubleshooting suggestions:
https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

The curve you are referring to, I assume it's the one in the "Voltage/Frequency curve editor" inside MSI Afterburner? Awesome Miner doesn't support this VFC feature yet but it's on the todo-list.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: crazydane on February 08, 2019, 03:35:48 PM

I've been playing around with the Linux remote agent. My first rig came up and started working right away, but I'm having issues with my 2nd rig. When I look at the remote agent log, I see a bunch of these:

Code:

Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.696 [010] [S]Setting callback channel
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.699 [010] [S]IntelliServer::AddChannel - Client: 10.0.1.212:2524, Channel: 32 connected
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.700 [010] [E]ChannelHandler::ReadAsync - Channel: 32 failed

After a while it changes to:

Code:

Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 669, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 481, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 357, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 292, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [028] [E]ChannelHandler::CommandAsync - Channel: 356, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.744 [028] [E]ChannelHandler::CommandAsync - Channel: 223, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.744 [062] [E]ChannelHandler::CommandAsync - Channel: 224, CommunicationError

So in AM, the miner shows up as "Service offline", but when I go to Managed Hosts and click "Test connection", I get the following message:

Successfully connected to Awesome Miner Remote Agent/Service 6.1.11

I uninstalled and reinstalled the remote agent, but I still have the issue.

I'm running nvOC 19.30 (Ubuntu 18.04), btw. I like this distro since it is all setup for mining out of the box and has a bash file where I set the GPU clocks and power.

If there's another distro that provides basics I need, I'm not opposed to give that a go. What Linux distro do you guys use with AM?

EDIT: Did a clean install of Ubuntu 18.04 LTS Server and after getting it all setup with the latest drivers, etc, I installed the remote agent. Getting the exact same errors as on the nvOC distro.

Thanks for your question

I assume you only have one single Host for this Linux miner defined in the Options dialog, Managed Hosts section. This host must have the "Linux" checkbox active and there shouldn't be any other hosts in the list connecting to the same computer. Can you verify this?

Can you also review the Awesome Miner application log file for any error message about this connection problem?

I know that a number of users have been running Remote Agent on HiveOS. I will however give nvOC a try to see if I can reproduce the problem you point out.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on February 08, 2019, 01:11:31 PM

I just did a test in a small rig. I have stopped MSI SERVER and in AM I have put the OC to be awesome miner.

I have forced several changes of something with different OC but in the rig the OC has not moved. I have left Aftherburner installed to know if the OC changes.

When I finished testing I went back to the usual with MSI SERVER and changed to AM and left it as usual.

That rig gave me problems, I had to go to the GPU and do the Mapping of the GPUs again to make it work.

As you said no info in your documentation please post the link here when you update it. I would like to use the most stable system. Sometimes the MSI SERVER stops working and you have to change the name of the folder in all the RIGS.

Right now I'm still with Aftherburne and MSI SERVER until there's more information on how to use your new OC version correctly.

I've updated the documentation page for GPU overclocking. It also contains information about how to troubleshoot if needed.
https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

Please note that for several of the OC settings, it's not possible to use MSI Afterburner to detect if it's applied correctly. For some settings, MSI Afterburner must be restarted for the new settings to show up and for a few other settings MSI Afterburner have it's own way of reading/setting clocking so any changes you define using other applications will not show up. For this reason I pointed out in the documentation that you should use the Reload-button in Awesome Miner to verify the settings.

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 205. (Read 703148 times)