Hi patrike,
AM did not change the order of the PCI Bus ID in GPU tab if i change the orders of the gpu´s.
What the GPU mapping is doing is to map the hashrates reported from the mining software to a specific GPU. In case Awesome Miner would show the hashrate for the wrong GPU, you can change the order to make this hashrate show up for another GPU.
So it isn't really for moving up/down a GPU in the list in general, but about moving up/down the hashrate and similar details from the mining software to make it show up for the correct GPU
Ok but the name, temp and clocks also change if i map the gpu´s. Only ID did not change in my case.
The list will always start with ID 0 and continue with 1, 2 and so on. I see that I didn't express this very well in my last response - sorry for any confusion. The GPU ID isn't moving up/down, but the actual GPU details are. Let's show this with an example
GPU 0: Geforce RTX 3080 | Clock details | 50% | 60 C | 28 MH/s
GPU 1: Radeon VII | Clock details | 55% | 65 C | 42 MH/s
Let's say Awesome Miner didn't map the hashrates reported by the mining software to the correct GPU here. So what is wrong with the table above is that the higher hashrate (42MH/s) is actually the Geforce RTX GPU - but is incorrectly displayed for the Radeon VII GPU.
When using the mapping you can change the order and "move up" the Radeon VII GPU. The result will be the following:
GPU 0: Radeon VII | Clock details | 55% | 65 C | 28 MH/s
GPU 1: Geforce RTX 3080 | Clock details | 50% | 60 C | 42 MH/s
At this point, 42 MH/s is for the Geforce RTX GPU, which we considered as correct for this example. So it's all about mapping the hashrate to the correct GPU. By design the GPU ID is static - but maybe it it adds a bit confusion and it would make more sense to move it as well.
