i have stoped miner, rebooted linux and run your nvidia-smi query. And i got the same  GPU pci-bus ordering result.
Problem is, that the after reboot value of clocking values which was showed in AM is not equal to values from Profit Profile for this rig. I have no idea where come this values after reboot.
In  Profit Profile set so:
START: Power 95%, Core 140, Memory 1200, Fan 100  (for all GPUs)
STOP: Reset to Default

After reboot (before i do manualy stop/start of awesome.service) AM in GPU Clocking Tab show my only sliders for Power and Fan
with this strange values:
GPU 0: Power 100, Fan 90
GPU 1: Power 96, Fan 90
GPU 2: Power 96, Fan 90
GPU 3: Power 100, Fan 90
GPU 4: Power 96, Fan 90
GPU 5: Power 96, Fan 90
GPU 6: Power 96, Fan 90
GPU 7: Power 96, Fan 90
Why linux set this wrong values, where they saved on ln system??? I can remember i have set this values during test phase, but logicaly after reboot i must see values from Profit Profile. I dont understand whats going on.

I checked GPU tab in AM, Memory set +1200 for all cards, that is ok. Core clocks looks good too.

Now i manualy restart awesome.service:
and i see:
Core 150, Memory 1200, Power 90, Fan 90   but in GPU clocking profile is : Core 140, Memory 1200, Power 95, Fan 100 !!!!
before rebbot i played with clocking and applied clocking profile with Core 150, Mem 1200, Pow 90, Fan 90
but at the and i applied profile with: Core 140, Memory 1200, Power 95, Fan 100
looks like AM saved clocking data on linux but not always and not before miner stop. Maybe Reset to default profile is a root of this chaos.

Hi patrike
this is output:
root@hive2080TI:/awesomeminer-remoteagent# nvidia-smi --query-gpu=name,pci.bus,index,power.limit,power.min_limit,power.max_limit,power.default_limit,clocks.max.sm,clocks.max.memory --format=csv
name, pci.bus, index, power.limit [W], power.min_limit [W], power.max_limit [W], power.default_limit [W], clocks.max.sm [MHz], clocks.max.memory [MHz]
GeForce RTX 2080 Ti, 0x01, 0, 238.00 W, 100.00 W, 310.00 W, 250.00 W, 2100 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x02, 1, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x03, 2, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x05, 3, 238.00 W, 100.00 W, 310.00 W, 250.00 W, 2100 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x06, 4, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x07, 5, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x08, 6, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x0A, 7, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz

Maybe better use for GPU addressing pci.bus parameter like (0x07, 0x08 ...)  instead of simple GPU ID like 0, 1, 2 ...
But then i need to recreate all my GPU clocking profiles, where clocking parameters will be set for every GPU in rig.

Regards

looks like AwesomeMiner wrong identify a GPUs PCI_BUS_ID after rebooting linux. Maybe AM used old stored data.
if i try for example manualy change fan speed on selected card 7, awesome change randomly on other card. If i select all GPUs and try to set fan or power, changes only applied on first 4 of 8 cards. This simply dangerous how awesome.service manage GPUs overclocking.
I wont use Linux due correct GPU VRAM management, but looks like i must try using Win7 instead of Win10. Windows 10 is simply theft 20% of GPU memory for nothing (due new model of driver platform) https://social.technet.microsoft.com/Forums/Lync/en-US/15b9654e-5da7-45b7-93de-e8b63faef064/windows-10-does-not-let-cuda-applications-to-use-all-vram-on-especially-secondary-graphics-cards?forum=win10itprohardware
but for Linux is not so many mining software as for windows at the moment.

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.

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

@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 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

what happens with binary file for ver. 1.84 on GitHub

hi patrike

Mainer Profit profile need separate parameter field for dual mining scenario, at the moment we can save in profile only one parameter set, or for normal mining, or for dual. And this is a problem.

Please remove HTML tags if "Copy to clipboard " function in benchmark dialog will be used.
  LBRY;CcMiner 2.3.1;<font color="#909090">2,2 GH/s, 1066 W (02.12.2019, v2.3.1)</font>;2,17 GH/s, 1055 W

Regards

Hi boss
 big thanks for features in last update.
 can you add in benchmark: max reached value of hashrate during benchmark. No need to save in profile, only for information, than user know when benchmark can be stoped.
 can you add colors to miner hashrate value. If actual value less then saved value in profile, color go to the red color zone , if more then saved in profile then go in green color zone. In this case user can quick see if something wrong with miner or profile can be better optimized.

Regards
 

patrike, can you add power limit override function to Profit profile?
where with this new power setting all GPU power parameters for all algoritms will be override, only in this concrete profit profile.
At the moment i need create a new "profit profile" if i want create profile with 75% power, another one if i want 80% and so on...

and later you can improve rule section with this new function "override profile power settings" ....

Regards

Hi Boss
can you create small elements for this lists:
  GPU clocking profile;
  Profit Profile;
please add to this lists column sorting feature.

Any chance that we get functionality to export/import of "Profit profiles" ? I understand, that is not easy due database structure. Maybe you can create some tool, which created new database entries in destination database and so import can be done.

Regards

quick test of v1.5s
WIN10 pro, build 1909 activated, RAM 8GB 3000Mhz, i5-9400F
Rig: 8 x ASUS Rog Strix 2080 TI 11GB

BeamHashII ver1.5r 687,18 H/s, 1549 W (5 min ) ( P75 C150 M400 ) (--oc2 )
BeamHashII ver1.5s 690,91 H/s, 1549 W (5 min ) ( P75 C150 M400 ) (--oc2 )

Equihash 144,5 ver1.5r 975,99 H/s, 1548 W (5 min ) ( P75 C150 M400 ) (--oc2 )
Equihash 144,5 ver1.5s 995,08 H/s, 1550 W (5 min ) ( P75 C150 M400 ) (--oc2 )

Equihash 125,4  ver1.5r 643,77 H/s, 1548 W (5 min ) ( P75 C150 M0 ) (--oc2 )
Equihash 125,4  ver1.5s 662,42 H/s, 1547 W (5 min ) ( P75 C150 M0 ) (--oc2 )

confirm improvements.

v1.75 not work on GTX1070 8GB, out of memory...
win 10 pro N build 1903, RAM 8GB
NVIDIA Game Ready driver 431.60

Any way how i can install "standart" driver on computer? How to trick windows or nvidia installer? If i try to install standart driver, i get error from nvidia installation program.

that not helps( dont understand why windows ignore starting Agent. I have use option to install Agent as service and this works. Something wrong with windows settings.

UPD: SOLVED!!!! fixed it through the local security policy > local policies > security options and disabling
"User Account Control: run all administrators in admin approval mode"

Looks like last Windows update made System changes in this sector.

@patrike
Just updated NVIDiA drivers to the latest 411.12 DCH version. (RTX2080TI, WIN 10 pro, Build 1903) and now if AM switch my rig to other algo, settings from GPU clocking profile or GPU overclocking setting from miner object for fun speed will not be applied. Fun always will be set to "autofun" mode. Other clocking settings applied without problem.  Later i can set manually fun speed.
In my previous setup with NVIDIA 431.60 DCH drivers this problem never exist.

@patrike
Can you add new setting: "Delay before applying overclocking to GPU" in sec.
reason: Some mining software like NBminer, very slow starting mining threads and if in this initialization time overclocking will be applied, often mining process stucks.

Regards

@patrike
I have problem to set Awesome Miner Agent to run on system startup (remote host)
Win10 pro, Build 1903 activated. Fresh install, all Windows update done. No Awesome Miner installed or was installed on this host.
all settings in Agent set to start with windows start, InteliBreeze Service run automatic
i have manualy added shortcut to shell:startup, in Windows task manager is see that Agent is setted and not disabled.
Why Agent dont want start with windows??
Manualy i can start and all works fine!!!