Hi Patrike,
i use the activity log and it is nice, but is it possibly to specify the source a little bit? It would be good to show the name of the rule that was triggert. I have many rules for tags, and at the moment i only see - source = rule, typ = miner and action = tags. But showing the rule name make it easier to find a failure for example. I know i can see the rule history with the rule name, but a little bit more information for the activiy log would be nice.
Thanks
@
Just got a license for 2 rigs to get out of HiveOS.
Unfortunately, I'm unable to overclock any of my 10 GPUs on the first rig where I want tot test AM.
RIG OS: Ubuntu 20.04
Linux agent installed (RIG is fully managed by AM)
Rig discovered by AM Windows app
Can stat mining... but useless as I can't at least set fan speeds to what I want. Overheat within a minute and I have to stop it
GPUs: RTX A4000 and RTX A2000 and one RTX 2060 super
Error message I get: Unable to read GPU information.
Should I conclude that overclocking feature is useless for a mining rig running on a Linux OS? if so, I will have to ask a refund as I don't want to run on Windows
Please try to run the following to re-initialize the configuration for nVidia overclocking:
sudo nvidia-xconfig -a --cool-bits=31 --allow-empty-initial-configuration
sudo reboot
Thanks for the update! We made a step forward, I can now see one GPU out of 10. I see only GPU ID: 0. It is probable something related about xorg or screen or else... sould I reinstall AM service?
Alos noticed lot of errors in the agent log
also I'm running uBuntu 22 and not 20 like stated earlier. I wil test with uBuntu 18 this week-end
Use the HiveOS distribution. It works well with AM, easy and fast install.