Troubleshooting

• 

  Articles on Image IMAGING vs CLONING
  • Paz

  1
  1
  Votes
  1
  Posts
  530
  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

  1
  0
  Votes
  1
  Posts
  1635
  Views

  

  Top Known Questions What is the ssh password? username: root password: live How to change root password? passwd Miner is already running, how to see? pimp --test 1 or screen -r Is there a demo version? No. Is my GPU supported? Check https://getpimp.org/shop/pimp and a profitability calculator to see. Can I use USB stick? No. Can I use non-UEFI mobo? No. UEFI is required for pimp 2.x. Can I use nvidia quadro GPU for mining? Usually not profitable. Should I mine on my laptop? No. Heat will kill it. Can I re-use my pimp key on another rig? The key can be reused, as long as it is only one rig at a time using it. Wait 1 hour between reimage/revalidation attempts. My GUI doesn't load. Why? Your onboard GPU is still on, see below. Top Known Bugs and Problems This list will be updated regularly with the current support trends, similar to a status page, and as a quick link for those who want the quick fixes until the next pimpup or image comes out. Cannot validate key on initial boot Summary of the bug: Users are reporting trouble with key validation on a new or old key, and the only thing that resolves it is one or many reimages. Who it effects: All users imaging from Windows. Status of fix: Researching any possible improvements we can make. Workaround: Make sure to configure motherboard and update bios according to instructions on Getting Started in forum. Reimage (write the image to the rig again, or try another method or target disk) and clean eject (or power off the host machine, or use a live usb to dd the image directly using the live environment). Use SSH to key the rig like the SSH key video. Details: 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 When I RDP in the resolutions seems stuck on 640x480 Summary of the bug: No monitor was connected, so it guessed. Who it effects: Users with 2.2 or older images. Status of fix: Will be delivered in a future pimpup. Workaround: Do: /usr/bin/xrandr --fb 1920x1080 will sort the resolution for the RDP client. Doesn't last through a reboot, but you can add the same line into your /root/startup.sh if you like. USB ACPI or other error on boot Summary of the bug: An error in detecting some USB3 chipsets prevents proper boot to GUI. Who it effects: Some users. Status of fix: Researching solutions. Workaround: User must change USB3 to legacy or turn it off. It is not needed for mining. Gray cursor appears on screen after motherboard POSTS Summary of the bug: Incorrect motherboard settings, UEFI not enabled, or mobo has detected a fault in the connected GPUs and has fallen back to onboard GPU. Who it effects: Users who have not configured mobo according to https://forum.getpimp.org/topic/9/setting-up-motherboards-for-mining or more specific guides in forum "Getting started" category. Status of fix: User error. Workaround: Disable onboard GPU in the BIOS. Miner is mining but not showing up on miner.farm Summary of the bug: Not a bug, miner API failure or out-of-sync issue. Who it effects: Users with hobby-grade miners that have issues with their API or other code (ewbf, claymore, etc) Status of fix: Researching coding around this using pimp dev magic. Workaround: run pimpup and if that doesn't work, systemctl restart minerfarm or go in the agent console with minerfarm and restart the agent service with o, then x. Cannot RDP (error connecting to 5900) Summary of the bug: The GUI service stops after you quit RDP and must be restarted. Who it effects: Users who use RDP to access the rigs GUI. Status of fix: Researching. Workaround: systemctl start lightdm && systemctl start --user pimpvnc then RDP in. for archived top known bugs: https://forum.getpimp.org/topic/459/archived-previous-top-known-bugs-archive
• 

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

  5
  0
  Votes
  5
  Posts
  1192
  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
  558
  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
  1021
  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
  537
  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

  4
  0
  Votes
  4
  Posts
  867
  Views

  

  Edit the file /etc/network/interfaces. You will need to provide the following information: Static declaration as iface <interface> inet static Static IP address as address <ip address> Network Gateway as gateway <gateway ip> Netmask / subnet as netmask <netmask ip> Broadcast address as broadcast <broadcast ip> DNS nameservers as dns-nameservers <dns ip> When you edit the file, you will find lots of comments to guide you. Read them carefully, they are there to help. Jump to the end, and add a stanza for your network. As an example: auto eth0 iface eth0 inet static address 192.168.0.101 gateway 192.168.0.1 netmask 255.255.255.0 dns-nameservers 8.8.8.8 8.8.4.4 You can then simply reboot, or use the system service daemon to restart the network interfaces: systemctl restart network-manager.service systemctl restart networking.service systemctl restart resolvconf.service You can use ifconfig to double check the IP settings: [/etc/network]:# ifconfig -a eth0 Link encap:Ethernet HWaddr b0:6e:bf:5c:62:9b inet addr:192.168.1.189 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::b26e:bfff:fe5c:629b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:164541 errors:0 dropped:0 overruns:0 frame:0 TX packets:18415 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17523916 (17.5 MB) TX bytes:2334343 (2.3 MB)
• 

  Rescue shell
  • CryptoNews

  1
  0
  Votes
  1
  Posts
  761
  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. 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? Try this: Disconnect the network cable from the rig. Boot When it says "Do you want to edit interfaces?" say Yes. Remove the # from the dns-nameservers 8.8.8.8 Control-X, Yes, [Enter] to save your changes. reboot (There is no rb command in Rescue Shell) should get an ip
• P

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

  1
  0
  Votes
  1
  Posts
  6
  Views

  P

  hello everybody, i install pimpos on compact flash drive 16 gb. yestarday i try to update system but recieve massege about low space . how can i clean space? p.s. sorry about my eng.
• H

  Can't update installed miners after pimpup
  • hernanmorenom

  1
  0
  Votes
  1
  Posts
  39
  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
  77
  Views

  

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

  Solved IP Conflict? Rigs are fighting for a place on miner.farm
  • info21

  5
  0
  Votes
  5
  Posts
  109
  Views

  

  Thanks for marking this solved
• I

  Solved Kernel panic - not syncing: timeout: Not all CPUs entered broadcast exception handler
  • info21

  9
  0
  Votes
  9
  Posts
  252
  Views

  I

  Okay I have updated pimpos with the following: And reapplied the miner config then started mining. I will see if this prevents the problem occuring again, thanks!
• C

  Rigs Disconnects from Network
  • chowhan

  7
  0
  Votes
  7
  Posts
  353
  Views

  I

  @nick Hi Nick, I am also having the same issue with agents showing as not checked in but when I SSH to them they show as mining. Could this suggest that my ISP is blocking a port? Or if that was the case would I not be able to SSH onto it?
• E

  Unsolved Keyboard not working
  • Enigma

  2
  0
  Votes
  2
  Posts
  96
  Views

  

  Hello Enigma, That’s annoying, you can always rdp or ssh in using another computer, or try using the same USB port that the mouse uses which you know works and see if it works with the keyboard. If it does then you know your keyboard works, and then try another USB port on your motherboard so that you can use the mouse again. It may be a problem with the USB port you are currently using with the Keyboard? Let us know how you get on. Best Louis
• S

  Solved Problems Booting After Re-imaging SSD
  • stevefrigon

  4
  0
  Votes
  4
  Posts
  104
  Views

  

  You are welcome. Happy mining.
• D

  Solved Full harddrive
  • danzarb

  5
  0
  Votes
  5
  Posts
  150
  Views

  

  Please see Wolfish reply to following post re resizing: https://forum.getpimp.org/topic/1738/how-to-expand-the-pimp-partition-to-use-unallocated-hard-drive-space/4
• M

  Solved Agent service is not running.
  • monk

  8
  0
  Votes
  8
  Posts
  244
  Views

  

  Seg fault usually means disk corruption, provide helpme and look in the "smartctl" section for errors or reallocated, and/or try a pimpup --force If that fails, reimage.
• T

  Solved Error message with new ccminer (result for nonce does not validate on CPU)
  • tnewbold1

  2
  0
  Votes
  2
  Posts
  129
  Views

  

  Try googling the error and you will see some options here: https://github.com/KlausT/ccminer/issues/69 namely, try backing clocks down, and/or run with --no-cpu-verify in the FLAGS= and see what happens. jjziets created this issue in KlausT/ccminer closed GPU #4: result does not validate on CPU! #69
• L

  Solved invalid device function problem
  • lee.stevens

  3
  0
  Votes
  3
  Posts
  123
  Views

  

  GT 730 is not listed as a compatible GPU for mining by the nvidia driver - you will have to purchase GPUs that are capable of mining. Generally $50 GPU is not "performance/gaming equipment needed for mining" Thanks