Troubleshooting

• 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
  7589
  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
  3214
  Views

  

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

  AMD missing GUI issues with PiMP 2.6
  • Anjin  

  1
  0
  Votes
  1
  Posts
  669
  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
  0
  Votes
  7
  Posts
  1972
  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
  1046
  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
  858
  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
  1197
  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
  2989
  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
  2111
  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.
• D

  amd Rig is crashing after running claymore dual for a long time
  • devinmosher  

  19
  0
  Votes
  19
  Posts
  3739
  Views

  D

  @docdrydenn Yes, thats exactly what I plan on doing. Im going to do a fresh install of an updated PiMP OS and flash my bios and go from there. It will be a few days as I work. But i will deffinitely keep you updated. Thanks for all your help. Very much appreciated
• 

  (FIX) Re-image Failure on a Windows Machine
  • docdrydenn  

  3
  0
  Votes
  3
  Posts
  1166
  Views

  

  Thanks, Melt. Updated post.
• M

  SOLVED Too many HW errors and low hashrate
  • milosbuncic  

  11
  0
  Votes
  11
  Posts
  4502
  Views

  

  @milosbuncic Any luck on your issue? If you solved it, please post what you did to fix it so that other Pimps who might be suffering the same problems can learn from what you did. Thank you.
• S

  Miner keeps stopping
  • sean  

  7
  0
  Votes
  7
  Posts
  2442
  Views

  

  Have you tried a different miner? Give ethminer a try and see if errors are thrown. If ethminer is good, we'll know the issue lies with the claymore miner.
• 5

  SOLVED Is it worth to start with Ethereum?
  • 5745hv1p3r  

  15
  0
  Votes
  15
  Posts
  3792
  Views

  P

  Thank you. I will keep you posted.
• P

  pimp os update. how to clean space
  • pozhidaev.alekcey  

  3
  0
  Votes
  3
  Posts
  981
  Views

  

  Thanks ldemorgan! Here is a screenshot: A few other notes: cleanlogs will clean up log folders. df -h to check how much space on /dev/sda1 And you can also use other common linux tricks to find out whats using space.
• D

  SOLVED Black screen after creating image on SSD
  • devinzz  

  5
  0
  Votes
  5
  Posts
  1540
  Views

  

  UEFI is required. That motherboard may not work. If you have old AMD GPUs along with that old motherboard you could potentially run pimp 1.9. Otherwise you need a more modern motherboard that supports mining.
• 

  Need Help Finding Your Rig's IP Address? - Let me introduce you to the Fing app (free).
  • docdrydenn  

  2
  1
  Votes
  2
  Posts
  1131
  Views

  

  This is a great guide for anyone who owns a wifi network. Nice work, thanks Doc!
• H

  Can't update installed miners after pimpup
  • hernanmorenom  

  1
  0
  Votes
  1
  Posts
  666
  Views

  H

  After pimpup, i see the "press any key to update installed miners...." but, after pressing any key (example a, or space) nothing happens and returns to the basic prompt. I have other rigs and it work on them, (it shows me the list of possible miner updates) but does not work on just one of them. What could be wrong? With thanks, HMM
• M

  Raven AMD sgminer conf file missing?
  • malucas72  

  4
  0
  Votes
  4
  Posts
  1065
  Views

  

  Apologies for this issue. The needed conf is being acquired.