I have 5 GPUs on my setup currently:

$ sudo aticonfig --list-adapters
  * 0. 01:00.0 AMD Radeon (TM) R7 370 Series
    1. 02:00.0 AMD Radeon (TM) R7 370 Series
    2. 03:00.0 AMD Radeon (TM) R7 370 Series
    3. 04:00.0 AMD Radeon (TM) R7 370 Series
    4. 05:00.0 AMD Radeon (TM) R7 370 Series

However ethminer only seems to recognize one:

$ sudo ethminer --list-devices
Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Pitcairn

I followed the GPU setup instructions here: https://github.com/ethereum/go-ethereum/wiki/Mining#gpu-mining

Any advice on getting ethminer to recognize all GPUs?

  • I had this once, a reboot was enough, perhaps in your case too. Jun 30, 2016 at 6:07
  • @NicolasMassart I wish that was the fix. I've tried rebooting among many other things.
    – Dan
    Jun 30, 2016 at 14:39
  • Have you tried to run the following command ? sudo aticonfig --initial --adapter=all and then reboot ? Jun 30, 2016 at 15:30
  • Given your log i would say you didn't install the right drivers. Jul 1, 2016 at 7:23
  • I downloaded the latest drivers from AMD for the appropriate chipset and OS. I caved in and purchased ethOS - they're mining fine now. But would be awesome to not have to purchase an OS for future rigs.
    – Dan
    Jul 1, 2016 at 17:46

2 Answers 2


For people who're having this problem with a headless Windows box:

ethminer must be started from the system, not via Remote Desktop and there should be a dummy plug or a real monitor connected to one GPU.

This is how I solved it:

  1. create a bat file which starts ethminer
  2. press Windows + R -> type "shell:startup" -> ENTER
  3. put a link to your .bat file in the folder that opens
  4. Let your box login automatically
  5. reboot and you're done

If you want to check on the system from time to time remotely, use Teamviewer or Chrome remote desktop

  • I was about to buy a dummy plug, but this worked out great. Thanks! Just to point out - you can still use Remote Desktop as long as you set Windows to automatically login before remoting into the machine.
    – Concept211
    Jun 26, 2017 at 13:16

Finally fixed my issue. Here's what I had to do:

  • From the BIOS, I had to set the motherboard to use PCI-e graphics (it was set to use onboard graphics).
  • I had to make sure I plugged any monitor into the GPU on the 16x PCI-e slot (I have an ASRock BTC Pro motherboard, and there is on 16x PCI-e slot, and 5 1x).

With that done all seemed to magically work.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.