GMinerRelease
GMinerRelease copied to clipboard
Invalid Device at index # - Why has Gminer started ignoring undetected GPUs?
Why have recent releases started ignoring undetected GPU's? (I.E gminer now ignores --devices 0 1 2, and starts mining even with only 1 GPU detected.).
Since upgrading to one of the later releases (not sure which one exactly), I've noticed that gminer now behaves differently when a GPU is not detected at startup.
In the older version, if 3 GPU's were specified in --devices, but less than 3 are detected at gminer execution then it would exit and display an error message "invalid device at index #", this allowed the continuation of the batch (.bat) file, enabling me to automatically restart the system with a batch command. (I.E shutdown -r)
This happens every time I get a blue screen (hard crash), after the first blue-screen restart, often the culprit GPU would not be detected in Windows Device Manager. (I.E a second restart is often required to clear the glitch).
Can we return to the old behaviour in the next release please? When people are not home, (working etc), it is important that our rigs can resolve problems automatically.
Alternatively, is there a non-published (developer) command? To return to the old behaviour? (I.E --ignore_undetected_devices=0)?
Thank you.
Nick
P.S Please give us control back!
--devices 0 1 2
not 0, 1, 2,
--devices 0 1 2
not 0, 1, 2,
I know, it is set correctly in my config file. Don't worry about that.
The reason for my post still exists?
Thanks.