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

Yes please do click diagnostic button. But i think you didn´t set --cpu-threads in the commandline.

Hi patrike,

Nvidia's latest drivers (456.38) installed, under the speed on the right (lower window, GPU tab) the wattage used per GPU is missing under performance.

Can you fix that in the next release, thanks.

Can you please start SrbMiner (the latest) with the Diagnostics button in the toolbar? Please share the output with me as it will be of help trying to identify the incorrect configuration. Thanks!

Didn't touch anything, from the word at all. On two computers srb 4.7 starts, but there is no data, 5.0 starts and immediately turns off, writes an incorrect configuration. I am using this miner for cpu.

Okay thanks. Now THIS is a viable solution.
Thank you. I'll look into it tonight.

Wow! Great advice!  

I did. I even stated that I did. So sure... quote my answer please.
Here... allow me.


And following up I did... by PM. Not to you though. Sorry, I wasn't aware that I should have sent you a PM as well.
BTW I have static IP addresses on ALL devices on my network with my mining rigs. Everything is MANUALLY set.
I have 10.0.0.1, 192.168.1.1, 192.168.0.1 and 192.168.2.1 as networks. (Techinically I also have 192.168.5.1 as a backup LTE data connection as a failover connection to my primary router but I'm not counting that.) But all of my rigs have static IP addresses.
192.168.2.1 for my FIVE personal computers are ALSO manually set. To include network printers. The only devices that IP is assigned by DHCP is IoT and that is on a totally seperate network. So my garage door can't conflict

So... it's not a IP conflict. It's not a firewall. Out of the 42 (yes 42) devices on my home network (not including VPN connected devices) I've NEVER had an IP conflict with this configuration. Everything is it's only private network. IoT devices are seperate from my mining machines for example. All of this is for security reasons.

Distance between AwesomeMiner PC and rig??? What does that have to do with anything? Okay... I'll indulge you with an honest answer. Ready? About 2 feet. Seriously. It's all in a 4x4 tent in a 42U server rack. Machines 1 and 2 are in 4U Rosewill cases. Other machines are open frame.
BUT... the mining rigs are connected to an unmanaged switch which is connected to a managed switch with VLAN which is connected to a 10Gb unmanaged switch. So when you mean "distance" you don't mean literal distance because that makes no sense. Either way, I'm not a n00b when it comes to networking and placement of mining rigs. Please don't treat me as such. I've been using AwesomeMiner since April 2018 and the problem with the "Interface Offline" just started so it's nothing to do with "distance" or placement.

So... in conclusion it's not an IP conflict or firewall. I noticed that the firewall did somehow activate but even after deactivating everything I still had the same issue.
The only thing that I can think of is an issue with the Remote agent, the OS itself or maybe even the CAT5e cable that I'm using.
I've attempted to move the CAT5e cable to another switch but that didn't help.

The log file indicated timeouts when connecting to the Phoenix Miner API port. Can you please go to the Options dialog, Advanced section, where you can increase the "Miner API connection timeout".

I suspect some API part of Phoenix Miner running slow, making the connections to time out quite often. By increasing the timeout, Awesome Miner will wait longer for a response. It isn't a perfect solution, but it's the only kind of workaround that Awesome Miner can do in this case.

Can you please send me the API report (Toolbar: Tools - API Report) for the miner when it's running SrbMiner, but not showing hashrate/temperature? Thanks!

The API format changed in SrbMiner 0.5.x and recent Awesome Miner versions have been updated to the new API format. It could however be some case where it isn't working correctly, so I'm more than happy to look into your API Report and see if there is a problem.

You say 2 sites back that the firewall was on and that was the problem. Please deactivate it. Or should i quote your own answer? Check IP´s in your network, sometimes my smartphone take the same ip as one of my rigs. Distance between Awesomeminer MainPC and the Rig?

Yes i understand you and this is clear dude.
Then it is a config failure by yourself. I don´t know your setup or your config. Api is changed in the last srbminer version and Patrike changed Awesomeminer that it can read the new api. So i don´t know whats your problem. I think you changed software setup or something.

Any updates from the reports that I had sent you?

This is clear. Temperature, hashray, power is not reflected in awesome miner window.

Yes and srbminer 5.0.1 works perfect. some things changed, please look in the srbminer thread.
Set --cpu-threads in commandline, it must be specify.

Hi, Patrike!

After the last update, the api srbminer 4.7 stopped working. The srbminer 5.01 version does not start, it also looks like something with the API.

If you run a 20 minute benchmark, Awesome Miner will ignore the first 6 minutes as there are larger variations in the beginning and it also takes some time before all cards are up to speed. For the last 14 minutes, Awesome Miner will measure the hashrate every 5 seconds and calculate an average value. This average value is what will be the benchmark result.

As you point out, there can be some variations in the hashrate on certain combinations of pools and algorithms.

GPU clocking profiles works on Linux but must be re-created if they initially was created on Windows. The clocking properties on are not exactly the same on Windows and Linux.

EthPill will unfortunately not be loaded automatically.

Hi Patrik
The benchmark of Bminer ver. 16.3 deliver a wrong hashrate data (algo CuckaToo32).
I have tested a rig of 6x 1080ti on the 20 min. run on Nicehash. Benchmark show 4.34 H/s, but in reality if i start normal mining on the Nicehash, hashrate is only 3.7 H/s.  AM ver. 8.0.1 Check please. Regards

Upd. Now show Bminer normal, like in benchmark. Simple Bminer have very big fluctration in hashrate data on Nicehahsh.

What is everyone running as the OS when using the Linux remote agent?

Ubuntu 20.04 desktop edition or server edition or something completely different?

I'd like to keep my OS install as lean as possible but wasn't sure of it is a pain to install the graphics drivers on the server edition (or if it is even supported).

EDIT: I went ahead and installed 20.04 on a test rig with a single 1070.  Added the latest Nvidia driver and screen (not part of base desktop install) and of course the remote agent.

Added the new rig to AM and created a GPU Clocking Profile.

Started mining, which is working fine, but the GPU Clocking Profile is being ignored.

Are GPU clocking profiles not supported on Ubuntu?

EDIT2:  Will AM automatically start the ETH pill on rigs with 1080/1080Ti GPUs?

Hey Sxemini

Works perfectly! 

Thank you 

Have fun!  =8^)

Ah ... yea I have to admit I did not test that case xD It sets it to "AUTO" internally for pool switching ... but yes over CMD that does not work. Will fix it with 1.08 - use --coin in the meanwhile for this function.