Post
Topic
Board Mining software (miners)
Re: CGWatcher 1.3.6, the GUI/monitor for CGMiner and BFGMiner to prevent downtime
by
sapstar
on 31/03/2014, 09:42:23 UTC
sapstar: I replied to your email. I'll also post here in case anyone else having a similar problem reads this. Nothing worse than finding someone with the same problem with you on a forum and then never finding the solution.

You need to fix or correct the GPU map inside of CGWatcher. You can do this by clicking "Incorrect hashrate for this GPU?" under the Average Hashrate in the GPU tab. It looks like a map was already created at one point for 4 GPUs. Note that this is the same idea as the "gpu-map" setting in cgminer, but CGWatcher has its own internal mapping. When you click the "Incorrect hashrate for this GPU?" link, it will open the GPU Map window, where you match detected GPUs (ADL) to their correct hashrates (OpenCL). You can also clear the existing map (Clear Map button... this will not clear cgminer's "gpu-map" setting, only CGWatcher's mapping) and see if this is enough for CGWatcher to match ADL to OpenCL devices - but if not you may have to map them yourself. Usually CGWatcher is pretty good at doing this, but in this case you're mapping GPUs with the "gpu-map" setting in cgminer and this can cause it to mis-map them sometimes. Once you do this the GPUs should start being reported correctly.

Thanks very much for the info Milone. Now I know what caused the issue. It has been a coincidence that I have added a GPU after the update. I think that caused the gpu-map incorrect.