You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting a little bug arround when i mine just for some selected GPU.
have in rig:
GPU 0 - 3090
GPU 1 - 3060ti LHR
GPU 2 - 3070 non LHR
GPU 3 - 3070 non LHR
GPU 4 - 3070 non LHR
When select just to use the GPU: 0,2,3,4 using the command --cuda-devices [0,2,3,4] the report in the miner come with a bug.
The last GPU in report always stay with value 0 shares , but during the time, miner get a share and represent it in the values of total shares, but never in report board.
@bitcointalk
I'm getting a little bug arround when i mine just for some selected GPU.
have in rig:
GPU 0 - 3090
GPU 1 - 3060ti LHR
GPU 2 - 3070 non LHR
GPU 3 - 3070 non LHR
GPU 4 - 3070 non LHR
When select just to use the GPU: 0,2,3,4 using the command --cuda-devices [0,2,3,4] the report in the miner come with a bug.
The last GPU in report always stay with value 0 shares , but during the time, miner get a share and represent it in the values of total shares, but never in report board.
https://cdn.discordapp.com/attachments/444585576792981520/919605989597130772/TBM_report_bug.PNG
As can be seen in the picture above, it getting pushing values for a GPU 1 that i effectively turn it off.
I assume that GPU0 it's ok , GPU1 it's for the GPU2 report, GPU2 for the GPU3 and GPU3 for the GPU4.
It's just a report number bug in the miner because not even equal the shares done and shares reported in the board.
With all the cuda devices running, this bug don't appear, just when selecting specific GPU to work.
Running HiveOS
TBM 1.32
Extra config arguments
![TBM_report_bug](https://user-images.githubusercontent.com/9572668/145721710-438cb837-c487-4552-b22d-9ddc0df0a2f9.png)
--cuda-devices [0,2,3,4]
--algo ethash
--log
The text was updated successfully, but these errors were encountered: