Pages:
Author

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

legendary
Activity: 1754
Merit: 1007
Hi Patrike, some suggestion:
Can you please add a rule trigger, where user can compare a difficulty value for selected algorithm and actions for add / remove selected pool / pool group to profit switching additional pools section. This will help to create a smart dynamic profit switching scenario, where actual algoritm difficulty is important, when no sence to switch to less liquidity coin, but at the moment this small coin/algo is quite more profitable as coin with big liquidity and trigger switching. Simple AM need a functionality to manage a "profit switch" additional pools list.
Regards.
There is a trigger for detecting a specific difficulty value. What is missing here would be an action to make impact on the profit switching decision for a specific pool or coin.

Instead of adding/removing pools from the profit switcher, it might would make more sense to set the profit factor of these pools or coins. This would impact the profit switching decision.
ok, understand. That can be a way.
Another thing: MiniZ miner have a new version. Please push update.
legendary
Activity: 3346
Merit: 1094
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.

I did that few times both with main app and remote agent. Nothing helped.
Thanks for the update. In case you still experience this issue and also verified in the Options dialog, Managed Hosts, that you don't have any duplicates in terms of IP addresses, please send me the Awesome Miner log file and I will investigate further.

You can send via the following link:
https://www.awesomeminer.com/contact

Thanks Patrike, will do that. I don't see log file in program directory, where should I look in Win64, %appdata% ? I couldn't overcome this issue and had to stop using AM at all for more than a week now, which super annoys me.
In Awesome Miner, please go to the toolbar Tools and click Log File. This will point you to the Awesome Miner log file.
legendary
Activity: 3346
Merit: 1094
Hi Patrike, some suggestion:
Can you please add a rule trigger, where user can compare a difficulty value for selected algorithm and actions for add / remove selected pool / pool group to profit switching additional pools section. This will help to create a smart dynamic profit switching scenario, where actual algoritm difficulty is important, when no sence to switch to less liquidity coin, but at the moment this small coin/algo is quite more profitable as coin with big liquidity and trigger switching. Simple AM need a functionality to manage a "profit switch" additional pools list.
Regards.
There is a trigger for detecting a specific difficulty value. What is missing here would be an action to make impact on the profit switching decision for a specific pool or coin.

Instead of adding/removing pools from the profit switcher, it might would make more sense to set the profit factor of these pools or coins. This would impact the profit switching decision.
legendary
Activity: 3346
Merit: 1094
Hello,

I found a problem trying to get on information tab the system uptime:


Please, it will be nice to see the uptime system on information Tab

Thanks for your question. For ASIC miners, Awesome Miner can only show the Mining Uptime. This is the time the mining process has been running, but it isn't the same as the operating system uptime. If Cgminer process on the ASIC miner is restarted, the Mining Uptime will reset although the system didn't reboot.

The Information Column has support for two kinds of uptime, the Mining Uptime and the System Uptime (OS uptime). For your ASIC miner, only Mining Uptime is supported. For Managed Miners, we can show both the Mining Uptime and also the System Uptime.

Nice!

And if the miner is not managed miner the information tab does not show any information about the uptime?
The information column has two properties related to uptime, "System Uptime" and "Mining Uptime". If you configured to display "System Uptime", your External Miner will show zero.
member
Activity: 280
Merit: 28
You must set your windows10 network to private.

I always thought that's the first thing to do when you set up your network after fresh install  Cool  It IS set to private and firewall rules are set accordingly.
member
Activity: 1558
Merit: 69
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.

I did that few times both with main app and remote agent. Nothing helped.
Thanks for the update. In case you still experience this issue and also verified in the Options dialog, Managed Hosts, that you don't have any duplicates in terms of IP addresses, please send me the Awesome Miner log file and I will investigate further.

You can send via the following link:
https://www.awesomeminer.com/contact

Thanks Patrike, will do that. I don't see log file in program directory, where should I look in Win64, %appdata% ? I couldn't overcome this issue and had to stop using AM at all for more than a week now, which super annoys me.

You must set your windows10 network to private.
legendary
Activity: 1754
Merit: 1007
Hi Patrike, some suggestion:
Can you please add a rule trigger, where user can compare a difficulty value for selected algorithm and actions for add / remove selected pool / pool group to profit switching additional pools section. This will help to create a smart dynamic profit switching scenario, where actual algoritm difficulty is important, when no sence to switch to less liquidity coin, but at the moment this small coin/algo is quite more profitable as coin with big liquidity and trigger switching. Simple AM need a functionality to manage a "profit switch" additional pools list.
Regards.
member
Activity: 280
Merit: 28
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.

I did that few times both with main app and remote agent. Nothing helped.
Thanks for the update. In case you still experience this issue and also verified in the Options dialog, Managed Hosts, that you don't have any duplicates in terms of IP addresses, please send me the Awesome Miner log file and I will investigate further.

You can send via the following link:
https://www.awesomeminer.com/contact

Thanks Patrike, will do that. I don't see log file in program directory, where should I look in Win64, %appdata% ? I couldn't overcome this issue and had to stop using AM at all for more than a week now, which super annoys me.
full member
Activity: 237
Merit: 100
Hello,

I found a problem trying to get on information tab the system uptime:


Please, it will be nice to see the uptime system on information Tab

Thanks for your question. For ASIC miners, Awesome Miner can only show the Mining Uptime. This is the time the mining process has been running, but it isn't the same as the operating system uptime. If Cgminer process on the ASIC miner is restarted, the Mining Uptime will reset although the system didn't reboot.

The Information Column has support for two kinds of uptime, the Mining Uptime and the System Uptime (OS uptime). For your ASIC miner, only Mining Uptime is supported. For Managed Miners, we can show both the Mining Uptime and also the System Uptime.

Nice!

And if the miner is not managed miner the information tab does not show any information about the uptime?
legendary
Activity: 3346
Merit: 1094
Hello,

I found a problem trying to get on information tab the system uptime:


Please, it will be nice to see the uptime system on information Tab

Thanks for your question. For ASIC miners, Awesome Miner can only show the Mining Uptime. This is the time the mining process has been running, but it isn't the same as the operating system uptime. If Cgminer process on the ASIC miner is restarted, the Mining Uptime will reset although the system didn't reboot.

The Information Column has support for two kinds of uptime, the Mining Uptime and the System Uptime (OS uptime). For your ASIC miner, only Mining Uptime is supported. For Managed Miners, we can show both the Mining Uptime and also the System Uptime.
legendary
Activity: 3346
Merit: 1094
hello everyone.
a bit of a noobie question, but i have not found an answer through search. (or i didn't do my search criteria right)

Does the linux agent handle the O.C. on gpus with the set clocking parameters like on the windows version? or do i need something else to set it up?
or do i need to use claymore instead of phoenix to get it working?
or is there no support for clocking through linux agent?


i see there are ways to do it manually, but would like the easy of AM doing it for me.

cheers
Thanks for your questions.

GPU overclocking is supported by Remote Agent on Linux as well. The properties available for overclocking may not be identical as those available on Windows, so if you ever created a GPU Clocking Profile on Windows you will have to re-create it if you move to Linux.

Thanks for the reply.

I ask because i don't even see my GPU's listed in the clocking tab. They are in the GPU tab, and i have a clocking profile set, but the memory is not clocked up according to the linux profile i made for ETH.
Running 18.04 ubuntu. should i try some other disto, or maybe the 20.04 version is better supported?
GPU's are gtx 1070's.


thanks for your continued efforts.   Smiley
Thanks for the update. Can you please try to run the following for nVidia clocking on Ubuntu:
sudo nvidia-xconfig -a --cool-bits=31 --allow-empty-initial-configuration
sudo reboot

ok, so i had upgrade to 20.04. but it started crashing. after a fresh install on 18.04 again, i am back to where i was.
i have cards on gpu tab.  but now, after your command,  i have gpu 0 only on clocking tab also.

cheers
Thanks for the update. Please restart Remote Agent once, go to the GPU clocking tab for the miner again, then send me the Remote Agent log file.

ok, am not able to do this at this point. Am using cpu gpu for console use. however, i now have a black screen on boot. Rig is running and mining, but only the 1 GPU in clocking tab. 6 gpu's in gpu tab.
also, i noticed on the console tab that, on startup , after a reboot, the mining software on startup says that GPU0 is using kernel #4 while all other gpu's are using kernel #2. and GPU#0 is the only one showing up in the clocking tab. not sure if this helps.
I'll wait for your reply, but may have to wipe and reinstall again to get console screen back. or should i turn off CPU GPU and use the 1070 for cosole use?

also might add that all 1070 GPU shows up in LSPCI, but only 1 GPU shows up when i ran 'ubuntu-drivers devices' before i run your last command.
cheers

I would have to investigate the Remote Agent log file to get a full understanding. You can access this log file via Awesome Miner as well, via the toolbar Tools -> Log File -> Remote Agent log file.

Is the "nvidia-smi" command showing everything it should?
legendary
Activity: 3346
Merit: 1094
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.

I did that few times both with main app and remote agent. Nothing helped.
Thanks for the update. In case you still experience this issue and also verified in the Options dialog, Managed Hosts, that you don't have any duplicates in terms of IP addresses, please send me the Awesome Miner log file and I will investigate further.

You can send via the following link:
https://www.awesomeminer.com/contact
member
Activity: 1558
Merit: 69
Hello,

I found a problem trying to get on information tab the system uptime:




Please, it will be nice to see the uptime system on information Tab


You use external miner, but you must use managed miners to get the uptime in the information column.

There is no need for that information. I think AM will populate this field on next version. Let's see.. lol

lol and your information is also not needed. This field is populate if you are using MANAGED MINERS, if not, AM can´t show this!!!!!
I am using AM for over 4 years and i am very experienced but you want no help and give useless answer.

You can see the miner uptime in progress column if needed.
full member
Activity: 237
Merit: 100
Hello,

I found a problem trying to get on information tab the system uptime:




Please, it will be nice to see the uptime system on information Tab


You use external miner, but you must use managed miners to get the uptime in the information column.

There is no need for that information. I think AM will populate this field on next version. Let's see.. lol
member
Activity: 1558
Merit: 69
Hello,

I found a problem trying to get on information tab the system uptime:




Please, it will be nice to see the uptime system on information Tab


You use external miner, but you must use managed miners to get the uptime in the information column.
full member
Activity: 237
Merit: 100
Hello,

I found a problem trying to get on information tab the system uptime:




Please, it will be nice to see the uptime system on information Tab
newbie
Activity: 23
Merit: 0
hello everyone.
a bit of a noobie question, but i have not found an answer through search. (or i didn't do my search criteria right)

Does the linux agent handle the O.C. on gpus with the set clocking parameters like on the windows version? or do i need something else to set it up?
or do i need to use claymore instead of phoenix to get it working?
or is there no support for clocking through linux agent?


i see there are ways to do it manually, but would like the easy of AM doing it for me.

cheers
Thanks for your questions.

GPU overclocking is supported by Remote Agent on Linux as well. The properties available for overclocking may not be identical as those available on Windows, so if you ever created a GPU Clocking Profile on Windows you will have to re-create it if you move to Linux.

Thanks for the reply.

I ask because i don't even see my GPU's listed in the clocking tab. They are in the GPU tab, and i have a clocking profile set, but the memory is not clocked up according to the linux profile i made for ETH.
Running 18.04 ubuntu. should i try some other disto, or maybe the 20.04 version is better supported?
GPU's are gtx 1070's.


thanks for your continued efforts.   Smiley
Thanks for the update. Can you please try to run the following for nVidia clocking on Ubuntu:
sudo nvidia-xconfig -a --cool-bits=31 --allow-empty-initial-configuration
sudo reboot

ok, so i had upgrade to 20.04. but it started crashing. after a fresh install on 18.04 again, i am back to where i was.
i have cards on gpu tab.  but now, after your command,  i have gpu 0 only on clocking tab also.

cheers
Thanks for the update. Please restart Remote Agent once, go to the GPU clocking tab for the miner again, then send me the Remote Agent log file.

ok, am not able to do this at this point. Am using cpu gpu for console use. however, i now have a black screen on boot. Rig is running and mining, but only the 1 GPU in clocking tab. 6 gpu's in gpu tab.
also, i noticed on the console tab that, on startup , after a reboot, the mining software on startup says that GPU0 is using kernel #4 while all other gpu's are using kernel #2. and GPU#0 is the only one showing up in the clocking tab. not sure if this helps.
I'll wait for your reply, but may have to wipe and reinstall again to get console screen back. or should i turn off CPU GPU and use the 1070 for cosole use?

also might add that all 1070 GPU shows up in LSPCI, but only 1 GPU shows up when i ran 'ubuntu-drivers devices' before i run your last command.
cheers
member
Activity: 280
Merit: 28
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.

I did that few times both with main app and remote agent. Nothing helped.
legendary
Activity: 3346
Merit: 1094
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Please try to restart the Awesome Miner main application once. If you change a computer from Linux to Windows, the connection may not be correctly initiated after a change to the "Remote Agent for Linux" checkbox.
member
Activity: 280
Merit: 28
Weird thing is happening and I can't beat it for almost 2 days now. One of my rigs was running Linux and had hardware issues, so I disassembled it changed motherboard, few cards etc. Altered all OC settings, GPU number etc in the settings, started the rig... It loses cards in less than 1 minute, they just stop hashing and go offline. After deleting miner from the system, setting OC again nothing changed. Okay, thought I, let's try a different approach. I took another SSD, installed fresh copy of Windows on it, installed Remote agent for Windows, searched for a new miner, found and configured it... Now it shows the rig is offline, though when I run Managed host - Test connection and uncheck Remote Agent for Linux tickbox (it's checked by default) - connection test goes OK. All this time the rig has the same IP. What am I doing wrong and how can I solve this?
Pages:
Jump to: