-
Notifications
You must be signed in to change notification settings - Fork 124
Troubleshooting
If you have problems with PINN, you can try the following steps:
-
Remove anything attached to the GPIO pins.
Certain pins cause NOOBS/PIN to enter a safe rescue mode. To avoid this remove any HATs or other circuitry attached to the GPIO pins. Is this is not possible, edit recovery.cmdline in the first SD card partition and adddisablesafemode
to disable this feature. -
Try noobs-lite to see if you get the same problem.
PINN is very close to NOOBS, so if the same error occurs with NOOBS then it is more likely to be a common NOOBS issue that you should get sorted using the normal NOOBS issue troubleshooting process. Once you are sure it is not NOOBS related, then continue below. -
Check the debug log.
Press Ctrl-Alt-F2 to get to the recovery shell. Use the username:root password:raspberry. typecat /tmp/debug/
and review any log output for anything that might indicate an error. If the log is too long, you can browse it usingless /tmp/debug
. Press Ctrl-Alt-F1 to return to the GUI. -
Check system messages.
Press Ctrl-Alt-F2 to get to the recovery shell. Use the username:root password:raspberry. typedmesg | less
and review any log output for anything that might indicate an error. Press Ctrl-Alt-F1 to return to the GUI. -
Open an issue on this github repository.
If the problem can still not be identified, please post the following details in the new Issue:
- The exact steps you took
- What you expected to happen
- What actually happened
- Any error messages that were displayed on screen
- A copy of the debug log, and/or a copy of the dmesg output.
To capture the debug logs you can do the following: Press Ctrl-Alt-F2 to get to the recovery shell. Use the username:root password:raspberry.
cd \tmp
mount -o remount,rw /mnt
cp debug /mnt/debug.txt
dmesg >/mnt/dmesg.txt
sync
Now you can turn off the Pi, put your SD card in a PC and copy the debug.txt and dmesg.txt files to your PC.
- Alternative debug log capture.
To ease the capture of debug and system info, I have created a script called savelog, which can be downloaded from https://sourceforge.net/projects/pinn/files/testing/savelog/download.
Copy this to PINN's recovery partition. An easy way to do this is to put your SD card in a USB card reader and plug it into your PC, then copy this file onto it. Then pop it back into your RPi and boot PINN.
Try to recreate your issue. After it has occurred, press Ctrl-Alt-F2 to get to the recovery shell. Use the username:root password:raspberry. Then at the prompt, type:
/mnt/savelog
When the prompt returns, you can power down the Rpi, remove the SD card and put it back in your PC's USB card reader. There should be a file calledlog
which you can post to help identify the problem.