Troubleshooting

• A

  SOLVED Error : can't find command 'gfxmode' Pimping your Rig. Press any key to continue... on My Asus B250 Expert Mining + 7x MSI RX580 Armor 8Gb
  • andrytantalus  

  9
  0
  Votes
  9
  Posts
  3360
  Views

  

  Resolved with latest BIOS updates and settings - Closing topic
• 

  SOLVED ACPI Exception AE_NOT_FOUND at boot time.
  • melt  

  9
  0
  Votes
  9
  Posts
  6146
  Views

  

  Resolved with BIOS updates and proper settings - Closing topic
• V

  SOLVED Sgminer crashes and rig reboots after pimpup
  • vincitmining  

  4
  0
  Votes
  4
  Posts
  1165
  Views

  

  Okay Vincit, Glad you got it worked out. Thanks for updating us. See you soon!
• J

  SOLVED BUS_id does not match busid detected for this card
  • Jorpheus  

  4
  0
  Votes
  4
  Posts
  1340
  Views

  

  Thanks Doc.. Now it's on his permanent record. LOL :)
• 

  How to Disable Onboard Video if there is No Option in the BIOS to do it.
  • docdrydenn  

  2
  2
  Votes
  2
  Posts
  1203
  Views

  L

  An easy way to narrow down the list of devices from 'lspci' is to filter it for the keyword VGA, like so: 'lspci | grep VGA'. This "pipes" the output from 'lspci' to the 'grep' command to look for the keyword VGA using the "|" character, which is known as a 'pipe'. The output from this piped command will only be the lines from 'lspci' that have the keyword VGA in them.
• 

  optiminer wont start after pimpup? Workaround for this problem!
  • Anjin  

  4
  0
  Votes
  4
  Posts
  1302
  Views

  

  Simple fix: Use Claymore's ZCash AMD GPU Miner v12.6 instead. LOL
• M

  SOLVED Agent service is not running.
  • monk  

  13
  0
  Votes
  13
  Posts
  3923
  Views

  

  Thanks trmead. In the future we hope to minimize re-image needs. We don't like reimaging either! :)
• T

  This topic is deleted!
  • trmead  

  0
  0
  Votes
  0
  Posts
  17
  Views

  No one has replied

• A

  SOLVED Pci Error ?? PIBUS HUB0
  • allan.s  

  2
  0
  Votes
  2
  Posts
  1298
  Views

  

  disable onboard graphics update mobo try pimp 1.9.31 for that old gpu
• J

  What to do when pimp user login box shows on desktop?
  • jman472  

  2
  0
  Votes
  2
  Posts
  1066
  Views

  

  SSH into the box and start mining. Try 2.6 image. Disable onboard graphics and plug monitor to first mining GPU.
• D

  This topic is deleted!
  • DMK4ever  

  1
  0
  Votes
  1
  Posts
  3
  Views
• C

  SOLVED Rigs Disconnects from Network (Asrock H110 Btc+)
  • chowhan  

  20
  0
  Votes
  20
  Posts
  10025
  Views

  

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

  ethermine update to 0.16 and stopped working
  • ph75  

  13
  0
  Votes
  13
  Posts
  4082
  Views

  

  Downloads can be found from your account on the main website.
• 

  SOLVED AMD missing GUI issues with PiMP 2.6
  • Anjin  

  1
  0
  Votes
  1
  Posts
  806
  Views

  

  We have had multiple reports of issues with some brands of AMD cards not booting to a GUI with PiMP 2.6 release. First of all, everything that should be done with a rig, could be done over SSH. If you start a GUI, one of your GPUs will sacrifice hashing power to display management. For the most stable and productive hashing, a headless environment cannot be beat. After much debugging and diagnostics on some cards failing to load a GUI, we find that the following procedure should work for most. There will still be issues for some 7+ AMD only GPU rigs, and only if they are specific models and types. If you have issues, and are running 7+, simply try moving a differing vendor/model into the first PCIe slot as detailed at the bottom of this thread. First, we need to stub in an older library and toolkit to get around the recent AMD driver issues. From an SSH session, or the terminal screen. Type the following command apt-get install fglrx-pxpress ubuntu-drivers-common [Agent: m194-580navy (Running) Total HR: [26.78Mh/s] Miners running [1] GPUs [A]] [12:14 PM][Uptime: 11d 18:07][root@pimp2(10.0.0.194)] [/root]:# apt-get install fglrx-pxpress ubuntu-drivers-common Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: alsa-utils libfftw3-double3 python3-xkit Suggested packages: libfftw3-bin libfftw3-dev The following NEW packages will be installed: alsa-utils fglrx-pxpress libfftw3-double3 python3-xkit ubuntu-drivers-common 0 upgraded, 5 newly installed, 0 to remove and 101 not upgraded. Need to get 1,744 kB of archives. After this operation, 4,856 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libfftw3-double3 amd64 3.3.4-2ubuntu1 [718 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 python3-xkit all 0.5.0ubuntu2 [18.6 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 alsa-utils amd64 1.1.0-0ubuntu5 [956 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 ubuntu-drivers-common amd64 1:0.4.17.7 [49.9 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 fglrx-pxpress amd64 1:0.4.17.7 [1,310 B] Fetched 1,744 kB in 0s (13.9 MB/s) Preconfiguring packages ... Selecting previously unselected package libfftw3-double3:amd64. (Reading database ... 156354 files and directories currently installed.) Preparing to unpack .../libfftw3-double3_3.3.4-2ubuntu1_amd64.deb ... Unpacking libfftw3-double3:amd64 (3.3.4-2ubuntu1) ... Selecting previously unselected package python3-xkit. Preparing to unpack .../python3-xkit_0.5.0ubuntu2_all.deb ... Unpacking python3-xkit (0.5.0ubuntu2) ... Selecting previously unselected package alsa-utils. Preparing to unpack .../alsa-utils_1.1.0-0ubuntu5_amd64.deb ... Unpacking alsa-utils (1.1.0-0ubuntu5) ... Selecting previously unselected package ubuntu-drivers-common. Preparing to unpack .../ubuntu-drivers-common_1%3a0.4.17.7_amd64.deb ... Unpacking ubuntu-drivers-common (1:0.4.17.7) ... Selecting previously unselected package fglrx-pxpress. Preparing to unpack .../fglrx-pxpress_1%3a0.4.17.7_amd64.deb ... Unpacking fglrx-pxpress (1:0.4.17.7) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up libfftw3-double3:amd64 (3.3.4-2ubuntu1) ... Setting up python3-xkit (0.5.0ubuntu2) ... Setting up alsa-utils (1.1.0-0ubuntu5) ... Setting up ubuntu-drivers-common (1:0.4.17.7) ... Setting up fglrx-pxpress (1:0.4.17.7) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.2) ... Processing triggers for ureadahead (0.100.0-19) ... Next, we are going to force the boot configuration utility that is built into PiMP. Simply execute this command rm /tmp/gpu* ; /opt/pimp/bootdetect. Nothing will be returned by this command, by you can check the /tmp/gpu* files to see if they got created, and that the GPU type and list are correct. Once complete, reboot the rig with rb or reboot Upon restart, the GUI should load on rigs with 1 ~ 6 AMD only GPUs. Keep an eye on this topic for more information! If you continue to have issues, please just note them here with the URL from the helpme command. This procedure is not required for NVIDIA, but will not hurt an NVIDIA or mixed GPU rig either. Good luck and happy mining!
• S

  No GUI after 7th gpu installation
  • spphoenix  

  7
  1
  Votes
  7
  Posts
  2336
  Views

  

  We find with AMD rigs, there are bugs with the AMD drivers that prevent the X11 GUI from indexing the GPUs past 6. So 7+, AMD only, will have some issues. We are working actively to find a resolution to the issue.
• A

  Pimp won't auto login into gui
  • Angelos2  

  3
  0
  Votes
  3
  Posts
  1252
  Views

  A

  Awesome thank you glad I’m not the cause this time hehe :) and I’ll keep a look out for updates. Cheers Ange
• G

  Retrying PimpOs..... how to validate?
  • Gilbert.A.Bedia  

  3
  0
  Votes
  3
  Posts
  1077
  Views

  T

  yes eject the reimaged disk properly making cold as the manual ejection happens if u dont key imput will in many cases give isseus so, in window right bottom side of the clock press the arrow pointing up select and click usb drive select the proper disk and eject it accordingly when u get he popup its safe to pull it u may pull it from u physical usb slot after the isseu should be resolved one more tip try to use diskapart before the imaging proces usually that give a high probability to succeed
• E

  SOLVED Keyboard not working
  • Enigma  

  3
  0
  Votes
  3
  Posts
  1465
  Views

  

  Hey, Enigma Were you able to fix the keyboard issues?
• H

  SOLVED Key not validated after upgrade to 2.6 (wait 1 hour between validations)
  • hernanmorenom  

  13
  0
  Votes
  13
  Posts
  3658
  Views

  

  @hernanmorenom Hello HMM, Brilliant news that you found a way to resolve the problem by copy and pasting from one rig to the other, not the conventional way but I’m so glad for you it resolved the issue. I will pass this info to the dev team if I may, and thank you for persevering with it. Have a good weekend and thank you for your continued support. Best Louis
• J

  SOLVED Can't boot, error: file `/boot/grub/x86_64-efi/normal.mod' not found. grub rescue
  • jimbob22  

  8
  0
  Votes
  8
  Posts
  2531
  Views

  

  Sorry, you're still having this issue. As soon as can find the time, I'll reboot my rig and go into the BIOS... maybe if I see it again, I can remember which setting it was that I had to change to make this error go away.