Difference between revisions of "R-Pi Troubleshooting"
Linker3000 (Talk | contribs) (→Video does not play or plays very slowly) |
Linker3000 (Talk | contribs) |
||
| Line 3: | Line 3: | ||
This page lists the most common problems and suggests some solutions. | This page lists the most common problems and suggests some solutions. | ||
| − | ==Red power LED does not light, nothing on display== | + | ==Power / Start-up== |
| + | ===Red power LED does not light, nothing on display=== | ||
The power is not properly connected. | The power is not properly connected. | ||
| − | ==Red power LED is on, green LED does not flash, nothing on display== | + | ===Red power LED is on, green LED does not flash, nothing on display=== |
The Raspberry Pi cannot find a valid image on the SD card. | The Raspberry Pi cannot find a valid image on the SD card. | ||
| − | ==Raspberry Pi shuts down soon after booting up== | + | ===Raspberry Pi shuts down soon after booting up=== |
This is caused by a power supply with too low voltage or too high voltage. | This is caused by a power supply with too low voltage or too high voltage. | ||
| − | ==Keyboard randomly repeats key presses== | + | ==Keyboard / Mouse / Input Devices== |
| + | ===Keyboard randomly repeats key presses=== | ||
This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Try unplugging every USB device except the keyboard. | This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Try unplugging every USB device except the keyboard. | ||
| − | ==Ethernet connection is lost when a USB device is plugged in== | + | ==Networking== |
| + | |||
| + | ===Ethernet connection is lost when a USB device is plugged in=== | ||
This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Some cheap USB hubs suck power from the Raspberry Pi even if a USB power supply is connected. | This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Some cheap USB hubs suck power from the Raspberry Pi even if a USB power supply is connected. | ||
| − | ==Sound does not work== | + | ==Sound== |
| + | ===Sound does not work=== | ||
Device drivers for sound are still being developed. Please wait for the community to improve the situation. | Device drivers for sound are still being developed. Please wait for the community to improve the situation. | ||
| − | ==Video does not play or plays very slowly== | + | ==Display== |
| + | ===Video does not play or plays very slowly=== | ||
Device drivers for video are still being developed. The XMBC distribution is the only distribution with good video support at the moment. Please wait for the community to improve the situation. | Device drivers for video are still being developed. The XMBC distribution is the only distribution with good video support at the moment. Please wait for the community to improve the situation. | ||
| − | ==Can only get 800x480 resolution in LXDE (Arch linux)== | + | ===Can only get 800x480 resolution in LXDE (Arch linux)=== |
Known issue with distro package as of 17-Apri-2012 - there's some missing boot config info. Creating a suitable cmdline.txt fixes it - type the following at a command line: | Known issue with distro package as of 17-Apri-2012 - there's some missing boot config info. Creating a suitable cmdline.txt fixes it - type the following at a command line: | ||
| Line 30: | Line 36: | ||
echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt | echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt | ||
</pre> | </pre> | ||
| + | |||
| + | ==GPIO== | ||
Revision as of 09:29, 19 April 2012
Back to the Hub.
This page lists the most common problems and suggests some solutions.
Contents |
Power / Start-up
Red power LED does not light, nothing on display
The power is not properly connected.
Red power LED is on, green LED does not flash, nothing on display
The Raspberry Pi cannot find a valid image on the SD card.
Raspberry Pi shuts down soon after booting up
This is caused by a power supply with too low voltage or too high voltage.
Keyboard / Mouse / Input Devices
Keyboard randomly repeats key presses
This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Try unplugging every USB device except the keyboard.
Networking
Ethernet connection is lost when a USB device is plugged in
This is caused by inadequate power. Use a good power supply and a good power cable. Some USB devices require a lot of power, so they must be used with a powered USB hub. Some cheap USB hubs suck power from the Raspberry Pi even if a USB power supply is connected.
Sound
Sound does not work
Device drivers for sound are still being developed. Please wait for the community to improve the situation.
Display
Video does not play or plays very slowly
Device drivers for video are still being developed. The XMBC distribution is the only distribution with good video support at the moment. Please wait for the community to improve the situation.
Can only get 800x480 resolution in LXDE (Arch linux)
Known issue with distro package as of 17-Apri-2012 - there's some missing boot config info. Creating a suitable cmdline.txt fixes it - type the following at a command line:
echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
