DMDE solved my problem. Thanks

@jonathan-olivier No, it did not help. Turns out, pimp was booting up, but not showing on the screen. I was able to ssh in though.

@anjin. Thanks bunches. Will check it out tomorrow, I have social obligations tonight.

Hello, sorry for the late reply, but this is how you set up the motherboard: https://forum.getpimp.org/topic/5076/asus-b250-mining-expert-bios-settings-pimp-os-v2-6

@Mal - Thanks again. I have followed the steps as prescribed and I also had a friend of mine burn it with his Linux setup. It appears it is a motherboard issue for me because it still won't boot. Thank you to everyone that has helped and now that I know what the proper image should look like (both of my new burns look exactly like what Mal posted) I can see that I have a MB issue to tackle. Might be time for a new one. Thank you again. Regards, DoctoreAz

Some mobos will enable iGPU by "Fallback" if it detects a "Fault" (riser connected without GEN2/GEN1 settings) or hardware issue... Can try simplifying rig down to 1 GPU in first x16 slot and verify proper operation/mining then build up from there.

Thank you for the quick reply.

its really making me crazy sometime hash rate ok after restart all up and down

MacOS Catalina user here: perfect install following this procedure: download image to iMac unpack plug in Wavlink USB-C connected cloning dock (SSD in "Target" slot) Initialise disk when MacOS recognised it was plugged in (disk was already formatted for ubuntu previous install 18.04) Start up balenaEtcher imaging tool drag .img pimp image to the Image side of the balenaEtcher tool select the SSD, USB-C connected disk Click "Image" Wait for it to finish turn off dock unplug SSD plug SSD into AMD GPU rig Startup connect from iMac via ssh to the rig once started. paste the key at the prompt hit "Enter" boom.

ok can you provide a helpme? run helpme at shell, you will get a shareable url to paste here.

You get Max agents added to key? Clear key rig count in Miner.farm Account page. Quick Video: https://youtu.be/awuWbLqT4Pk Still problems? re-write SSD, clean eject, and SSH key in: https://forum.getpimp.org/topic/268/can-not-validate-license-key/7 and https://forum.getpimp.org/topic/14/entering-the-key-for-the-first-boot

With ethminer, You get more settings to pick from, but you have to set them! Make sure you use your troubleshooting skills and the pimp --test and pimp --debug commands as well as the healthy amount of example pools. Or you can try another miner that is easier to use out of the box.

Merry Christmas!

Friends dont let friends use safari. Install ANY other browser and try again, perhaps. Or install discord. Or try on a phone. Or try one of these helpful videos: https://www.youtube.com/results?search_query=how+to+discord+on+mac

Yes, external nic or using a Layer3 switch will work until we develop a more robust fix. Thanks!

@dasgutya as far as I know some people had a similar problem with this board, but updating the BIOS had to solve this problem. Look at https://msi.com/Motherboard/support/Z170A-GAMING-M5#down-bios Try the latest version 7977v1F from 2017-06-10 or version 1.D from 2016-12-19 with support of multi graphic cards. I'm sure that this will solve the problem. And also after updating the BIOS check all the settings of the motherboard again, considering singularity of PCI-e slots operation in some models of MSI boards, it may be necessary to switch on GEN1 mode instead of GEN2. I will be glad to know the result. Good luck!

you need to disable your onboard video. i can see its still enabled here { "gpu_id": "0", "fanspeed": "90", "temptarget": "70" }, and here 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 610 (rev 04) (prog-if 00 [VGA controller]) This also looks like you are underpowering one of your risers. GPU 1: AMD Radeon RX 570, Temp: 25C, Fan: 88%, Core Clock: 1400 Mhz, Memory Clock: 2000 Mhz, Power profile: performance (DPM mode), Power Usage: 2.132 W GPU 2: AMD Radeon RX 570, Temp: unknown, Fan: unknown, Core Clock: unknown, Memory Clock: unknown, This is how it always goes on my machine. When one has a power issue i start getting unknown reports from the gputool --status or --config. Once one GPU has an issue the rest of the chain falls out despite there are fine. I recommend remove on GPU from the chain at a time, reboot and rebuild the gpu-config.json. You also have to reboot after rebuilding it before trying the --status because things about PCI bus config gets cached by the OS. Its an arduous task but generally helps to isolate a single card.