Troubleshooting

• 

  Articles on Image IMAGING vs CLONING
  • Paz  

  1
  1
  Votes
  1
  Posts
  1490
  Views

  

  This is more so I dont lose the pages. I along with many others consistently have problems with key validation, and flashing of the HD images. While the team is working hard on resolving this, it seems to be the same issue over and over again. People are used to "installing" software which means a program puts files on your operating system and the installers these days have checks to make sure everything got to where it should. Imaging is not the same thing. You take an IMG file and copy the data bit by bit to a destination drive. Based on how this works the utility has no way to know or determine if the source bit and destination bit are identical or correct. Assumption #1: Because my image loads linux, it should be fine Assumption #2: Because the key validator at least ran (and failed) the image flashed fine Apparently the data suggest this is not the case. If a few bits fail in random places, only certain things will not work properly. The team is trying very hard to come up with a new process that takes this uncertainty away. But for the meantime, PIMP DOES WORK and 1000s of users are doing this fine day to do. Dont be discouraged, have some faith. It's frustrating to do this over and over again without any luck, but that doesnt mean Pimp is broken. Here are a few links which I found today which might help. This guru knows HDDs inside and out and describes the difference between IMAGING and CLONING and what happens when you unknowingly write to a bad sector. Even brand new drives contain bad sectors, and truth be told, SSDs are even worse for this. SSD technology is known for static errors, so they implemented types of error correction which CANNOT be used in the img flashing process. http://www.hddoracle.com/viewtopic.php?f=117&t=1410 This article discusses a utility that helps you determine there are bad sectors and mark them to not be used. http://www.hddoracle.com/viewtopic.php?f=30&t=1183 I havent been able to test this yet, but will do so this week. If anyone beats me to the punch, please update here.
• 

  Top Known Bugs, Problems, and Questions
  • melt  

  2
  1
  Votes
  2
  Posts
  3057
  Views

  

  xmrig-cpu libssl error on 2.9.3+ Summary: error /opt/miners/xmrig-cpu/xmrig-cpu: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory Status: PiMP 2.9+ will contain this package. Workaround: apt install -y libssl1.1 is the fix Reason: They are using a newer version of the ssl library than what originally shipped with ubuntu.
• 

  SOLVED What is a Sick or Dead gpu? & how to fix
  • dasgutya  

  5
  0
  Votes
  5
  Posts
  2736
  Views

  S

  For me, the dead GPU issue was caused by poor GPU spacing. Nothing indicated overheating but I separated my GPU's to give them twice as much space and haven't had the problem again. When I did this, my hash rate also jumped up so I apparently wasn't given them enough breathing room.
• 

  Warnings and Error messages that can be safely ignored
  • melt  

  1
  0
  Votes
  1
  Posts
  1474
  Views

  

  Error : can't find command 'gfxmode' This is just a warning from an old boot configuration file. It does not cause any issues. tsc_firmware: This is just about CPU microcode firmware and does not affect mining at all. Error in creating .profile: This happened on older versions of PIMP on opening the GUI.
• 

  SOLVED i’m getting Cannot connect to the miner API - the mining program fails to start. What to do next?
  troubleshoot • • melt  

  1
  0
  Votes
  1
  Posts
  2020
  Views

  

  The miner could not start for any number of reasons. Basically, a read through of the helpme (PiMP Troubleshooter) can tell you whether your GPUs and software is ready to mine. After that, look at what the miner says to see if you have an error. Usually this error is due to user putting wrong information in the conf or pcfg file. To rule that out, we ask you to restore the default that we know works. Run pimpup to be sure you are on the latest pimp software. Run helpme and look at it. Are the GPUs detected properly by all the subsystems? Del your config file. (example: del claymore.dual.pcfg) This will show you if the known-good safe benchmark default configs work. What does pimp --test 1 do? Do you see the miner mining or any error? What does pimp --debug 1 do? Do you see the miner mining or any error? Try adding and running another PiMP managed mining profile and see what that does. Submit your helpme to the forum and/or discord to get some help.
• 

  (Archived) Previous Top Known bugs archive
  • melt  

  1
  0
  Votes
  1
  Posts
  1484
  Views

  

  Overview This list will contain previous support trends listed on Top Known Bugs page, and their fixes. For current Known Bugs: https://forum.getpimp.org/topic/57/top-known-bugs PiMP Does not support 5+ GPU on MSI Z170 boards [Cannot fix] Summary of the bug: Will not boot to PIMP at all. Who it effects: MSI motherboards with 5+ GPU. Status of fix: MSI upstream hardware issue, posted on forum. Workaround: none Network IP not detected on first or second boot on some networks. [Solved] Summary of the bug: First or second boot of PIMP on some networks does not show the IP or allow key entry. Who it effects: AMDGPU users on some networks. Status of fix: Fixed in 2.4 images. Workaround: Find the IP another way, such as looking in the router DHCP table. and SSH the key into the box. ETH DAG hashrate loss on Polaris (RX 4xx series) GPUs [Solved] Summary of the bug: Lower hashrate or hashrate falls after some time mining on AMDGPU. Who it effects: AMDGPU mining Ethereum. Status of fix: Fixed in 2.3.30-amd. Workaround: n/a Clocks/Power not shown on Claymore on 2.3.30-nvidia [Solved] Summary of the bug: 2.3.30-nvidia comes with claymore-dual-v9.7 Who it effects: People using Claymore Dual on Nvidia 2.3.30 Status of fix: Fixed by running pimpup on Claymore dual miner to v10. Workaround: n/a Cannot pimpup due to /tmp/gputype does not exist [Solved] Summary of the bug: There was a bug in a pimpup for a few hours on 20171106 which left this file out. Who it effects: Users who pimpuped imediately on 20171106 Status of fix: Was fixed in pimpup that day. Workaround: Do: echo NVI > /tmp/gputype for Nvidia or echo AMD > /tmp/gputype for AMD and then pimpup --force to force update. AMD Hashrates jumping or amdmeminfo 100% cpu load Summary of the bug: There was a bug in the upstream library amdmeminfo and they have patched it, now you can grab it with the next pimpup. Who it effects: AMD miners. Status of fix: Released in pimpup 20171111 Workaround: Do: pimpup
• 

  Networking Alternatives (Wireless, Static IP, etc)
  • CryptoNews  

  5
  0
  Votes
  5
  Posts
  2981
  Views

  

  @jmh said in Networking Alternatives (Wireless, Static IP, etc): how do you set a static ip? Check out the new video added to the original post!
• 

  Rescue shell
  • CryptoNews  

  1
  0
  Votes
  1
  Posts
  1781
  Views

  

  Overview This only applies to rigs that are not verified with key. PiMP requires networking in order to validate the PiMP key. If PiMP cannot get a network connection in the unverified mode, you will be given what is called the Rescue Shell. This is a special environment designed to do one thing: get you on the network so you can verify. UPDATE! Hot new video how to edit interfaces file: https://youtu.be/Uze50oEU33o Default networking behavior is DHCP PiMP will pull an address from the router using DHCP by default. It is recommended to have a wired ethernet connection for the best mining performance. Wireless support exists, you will have to read up on how to configure it. Also, we have added some example content in the /etc/network/interfaces file to help those users who would like to set their own static IP, etc. What tools are offered in Rescue Shell? First, it will allow you to edit /etc/network/inferfaces directly. Beyond that, some other work may be needed to get networking up. You are given a printout of all pertinent information about the network and network hardware, and a shell to go in and fix it. (Wireless users: this is where iw and iwconfig come into play.) Cannot get a network IP on the first boot? First step is to verify that your network is actually working correctly. Do not assume it is working - you must test it. Disconnect the Ethernet cable from your PiMP machine and connect it directly into a laptop or another computer and verify that it is working. Doing this will verify that your modem, router/gateway, any switches, and all cables are working. With your network verified good, now we can move on to your PiMP machine. PiMP OS uses DHCP as the default for network addressing. Some motherboards take longer than others to initialize their onboard NICs. This "delay" can cause PiMP to timeout and present you with the above image. To get past this, we will need to setup Static network addressing. (Note: Once you have PiMP up and running, you can change back to DHCP if you want.) As seen in the above image, if PiMP OS is not able to find a valid IP, you will be prompted: "Would you like to manually edit your interfaces file? (y/N)". Follow the steps below to establish a Static network address. Answer y followed by <Enter> (PiMP OS will save a backup of the interfaces file and open it for editing. First, we want to disable (adding # to the beginning of a line) of the two (2) DHCP lines. Next, we want to enable (removing the # from the beginning of a line) the eight (8) STATIC lines. Finally, we want to make changes to this data to match our network config. (Note in this example, I've set the Static IP to 192.168.1.209) (You can identify your network's config by inspecting the network addressing of another device on your network.) When complete, your interfaces file should look something close to this: Press Control+X, Y then <Enter> to save the changes. Once back at the command line, type reboot (There is no rb command in Rescue Shell) to reboot your PiMP machine. With a Static IP assigned, you should be presented with the following: Notice that the displayed detected IP address matches what was set in the interfaces file from step 4 above Once your PiMP Key has been validated and your machine reboots to the PiMP OS desktop, feel free to re-edit the /etc/network/interfaces file to re-enable DHCP and to disable STATIC then reboot your PiMP machine.
• 

  9th 1070 GPU in Asus B250 mines but throws errors...
  • 3B0LA  

  2
  0
  Votes
  2
  Posts
  25
  Views

  

  "helpme" output @ https://helpme.getpimp.org/miner1-1552802727.html what a killer tool =) I edited out entries in startup.sh and removed crontab entries so I could run them manually while I was trubbleshuutin 3B0LA
• J

  SOLVED Downloads are corrupt
  • jon1  

  14
  0
  Votes
  14
  Posts
  2084
  Views

  

  Hello, sorry for the troubles - we were able to determine that the issue was with our CDN, and it is reported by our testing to now be resolved. Please try again and let us know if you have further issues!
• T

  SOLVED Key failed validation: API Keys Not Set
  • tnewbold1  

  3
  0
  Votes
  3
  Posts
  43
  Views

  

  Further, "API Keys not set" can be fixed by setting API keys (once you have validated the rig with the PiMP OS 2.x Key)
• R

  SOLVED Neoscrypt config errors
  • rico402000  

  4
  0
  Votes
  4
  Posts
  977
  Views

  

  Hello, Did you ever figure out what settings to use in the .conf file? We can update the defaults if you've found something more appropriate.
• L

  Running Miner, but no mining.
  • laroche.genie.it  

  3
  0
  Votes
  3
  Posts
  69
  Views

  L

  Wow that was fast !! Thanks, I'll give you some feedback .
• S

  SOLVED speed drops with increasing number of cards
  • stas  

  5
  0
  Votes
  5
  Posts
  222
  Views

  

  Great - glad it is working for you with easy to set settings. Thanks for the update!
• P

  SOLVED How do I Release key from previous PIMP so it can be used after reimage?
  • phunk000  

  2
  0
  Votes
  2
  Posts
  155
  Views

  

  Hello phunk000, Please check out this post: https://forum.getpimp.org/topic/5620/tutorial-how-to-reset-your-pimp-os-key-in-miner-farm
• P

  XMRStak won't start after pimpup
  • phunk000  

  2
  0
  Votes
  2
  Posts
  109
  Views

  

  Hello phunk000, this is a limitation of the new xmrstak, you will have to update PIMP OS image to 2.8.6 to run that miner, or restore the backup from /opt/miners/xmrstak.backup to /opt/miners/xmrstak and run the older xmrstak that doesn't require a newer OS.
• D

  SOLVED Logout/login needed after miner.farm3 launch
  • Draugtor  

  3
  0
  Votes
  3
  Posts
  178
  Views

  D

  Thanks Solved...
• M

  SOLVED GPUs not running - detecting motherboard as GPU?
  • markbreen2112  

  4
  0
  Votes
  4
  Posts
  188
  Views

  M

  Thanks melt and docdrydenn, got it figured out!
• L

  SOLVED Insufficient CUDA driver 9010
  • laroche.genie.it  

  5
  0
  Votes
  5
  Posts
  384
  Views

  

  Well I found your order and fixed it for you just now. Refresh the page. For others, If you scroll through https://getpimp.org/home-landing/my-account/downloads/ and do not see it listed for some strange reason, then provide Order number and we can fix you right up. If you want to do so in private just jump on the Discord (discord.me/pimp) and we will help you out asap. Of course, this month we release miner.farm 3 and the downloads will be quick links right on your miner.farm account page in miner.farm 3, along with all your pimp keys and transaction history. Things are going to get a whole lot easier very soon. Thank you for supporting our work! :)
• Z

  SOLVED x16r (zEnemy) error while loading shared libraries: libcudart.so.9.2: cannot open shared object file: No such file or directory
  • zach.atkinson85  

  4
  0
  Votes
  4
  Posts
  166
  Views

  

  Zach, you probably did it right. Sometimes the files can take a few seconds to download and unpack in the background thread. I have caught myself doing pimpup --auto then trying to add right away or something and having to wait a few seconds. Thanks for your support! Post some numbers here if you can and we'll pass them on to DK and Zealot from the Z-enemy team :)