https://elinux.org/api.php?action=feedcontributions&user=Kwi&feedformat=atomeLinux.org - User contributions [en]2024-03-29T07:05:12ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=CEC_(Consumer_Electronics_Control)_over_HDMI&diff=204482CEC (Consumer Electronics Control) over HDMI2012-12-25T13:21:32Z<p>Kwi: libCEC gained support for the Raspberry Pi in version 1.8.0.[http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/]</p>
<hr />
<div>The Raspberry Pi (Broadcom BCM2835 SoC) hardware has integrated support for CEC (Consumer Electronics Control) over the HDMI port.<br />
<br />
CEC (Consumer Electronics Control) is the control protocol found in HDMI. If you have not heard of CEC, you may have heard of it in another form from television manufacturers; Sony call it Bravialink, LG call it Simplink, Sharp call it Aquos Link, Pioneer call it Kuro Link, Philips call it EasyLink, and Samsung call it Anynet+, and so on.<br />
<br />
Media center software XBMC and MythTV already support HDMI- CEC via libCEC[http://libcec.pulse-eight.com][http://github.com/Pulse-Eight/libcec];<br />
libCEC gained support for the Raspberry Pi in version 1.8.0.[http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/]<br />
<br />
Having Raspberry Pi's hardware support in libCEC means that you can control XBMC and MythTV front-end GUI via your television remote control without having a dedicated HTPC / MCE remote for your Raspberry Pi.<br />
<br />
Once connected your Raspberry Pi to your TV and receiver with HDMI you ''should'' enjoy seamless connectivity, XBMC will automatically turn on and off your TV, receivers, and other home theater equipment. Volume control from XBMC can be sent to your amplifier, manage your DVD or Blu-Ray player from inside XBMC, and redirect the active source on your TV to whichever equipment needs it, all from one remote control. No line of sight is required and cables can be hidden neatly out of sight!<br />
<br />
==What is HDMI CEC?==<br />
'''Consumer Electronics Control (CEC)''' is an HDMI feature designed to allow the user to command and control up-to ten CEC-enabled devices, that are connected through HDMI, by using only one of their remote controls (for example by controlling a television set, set-top box, PVR/DVR, and DVD player using only the remote control of the TV). CEC also allows for individual CEC-enabled devices to command and control each other without user intervention.<br />
<br />
It is a one-wire bidirectional serial bus that uses the industry-standard AV.link protocol to perform remote control functions. CEC wiring is mandatory, although implementation of CEC in a product is optional. It was defined in HDMI Specification 1.0 and updated in HDMI 1.2, HDMI 1.2a and HDMI 1.3a (which added timer and audio commands to the bus). USB to CEC Adapters exist that allow a computer to control CEC enabled devices.<br />
<br />
Trade names for CEC are Anynet+ (Samsung); Aquos Link (Sharp); BRAVIA Link and BRAVIA Sync (Sony); HDMI-CEC (Hitachi); E-link (AOC); Kuro Link (Pioneer); CE-Link and Regza Link (Toshiba); RIHD (Remote Interactive over HDMI) (Onkyo); RuncoLink (Runco International); SimpLink (LG); HDAVI Control, EZ-Sync, VIERA Link (Panasonic); EasyLink (Philips); and NetCommand for HDMI (Mitsubishi).<br />
<br />
=== Some of the available HDMI-CEC commands===<br />
* One Touch Play: the device will become active source when playback starts<br />
* System Standby: switches all connected devices to standby<br />
* Preset Transfer: transfers the tuner channel setup to another TV set<br />
* One Touch Record: start recording immediately<br />
* Timer Programming: allow one device (e.g. a TV set or HTPC) to set the timer programming of another (e.g. a PVR,/DVR or DVD-recorder)<br />
* System Information: checks all components for bus addresses and configuration<br />
* Deck Control: playback control<br />
* Tuner Control: control the tuner of another device<br />
* OSD Display: use the OSD of the TV set to display text<br />
* Device Menu Control: use the menus of another device<br />
* Routing Control: control the switching of signal sources<br />
* Remote Control Pass Through: pass through remote control commands<br />
* Device OSD Name Transfer: transfer the preferred device names to the TV set<br />
<br />
===Technical concept===<br />
CEC stands for Consumer Electronics Control. It is implemented as a single wire bus in the HDMI connector (pin 13). It allows various HDMI-enabled products to connect and communicate with each other. It allows various HDMI-enabled products to connect and communicate with each other. The intent is to enable one remote control to interface with all the A/V components. Various message opcodes can be exchanged between the connected systems in order to do device specific actions (like recording on a STB/DVR) or get general information across (like transferring remote control key press details).<br />
<br />
In any HDMI setup, the display is considered to be the root, and gets allocated two special tags, a physical address of 0.0.0.0 and a logical address of 0. In any given system, all CEC enabled devices have both physical and logical addresses, while the non-CEC devices have only physical addresses. Physical addresses are taken up based on the position of the device with respect to the root. For example, if an A/V receiver's output is connected to HDMI1 of the TV, it gets the physical address 1.0.0.0. A device connected to the first HDMI input port of the A/V receiver would get the address 1.1.0.0, while one connected to the second HDMI port would get 1.2.0.0. Logical addresses are taken on by the devices depending on their functionality (as mandated by the CEC specifications document). When the HDMI device menu is brought up on the display (On a Sony KDL46EX720, this is achieved by pressing the Sync Menu button), the display sends a broadcast over the CEC wire to all the downstream devices. It then collects the responses arriving over the CEC wire and presents the user with a list of CEC enabled devices. Choosing one of them ensures that future remote key presses are transferred by the TV to that particular address.<br />
<br />
If you are interested in learning about the bus protocol and a bit more in-depth overview, I suggest taking a look at [http://www.quantumdata.com/pdf/CEC_White_Paper.pdf QuantumData's excellent CEC whitepaper (PDF)]. For more details on the various messages which can be exchanged between the devices, the full CEC specifications from [http://xtreamerdev.googlecode.com/files/CEC_Specs.pdf the official HDMI documentation may be perused (PDF)].<br />
<br />
===CEC with XBMC Media Center software===<br />
CEC allows XBMC to turn your TV, receivers, and other attached equipment on and off (if they support HDMI CEC) adjust the volume or eject the disk from a drive. Start playback, etc. and much more.<br />
<br />
Likewise these same devices can tell XBMC what to do, for example, your TV remote can also control XBMC, or vice versa. With this device you can move that step closer to a clutter free living space while maintaining simple remote control for friends and family who may not be familiar with all of the features of a professional remote control.<br />
<br />
See CEC in action and read about what it can do with XBMC:<br />
* http://www.youtube.com/watch?v=1eDJbT35X5k<br />
* http://xbmc.org/natethomas/2011/11/01/the-usb-cec-adapter-is-a-look-into-the-future/<br />
<br />
==Where to begin developing CEC support for Raspberry Pi?==<br />
Best would be for someone to add support for the Raspberry Pi's CEC hardware to the libCEC library by Pulse-Eight available on GitHub.com<br />
* [http://libcec.pulse-eight.com/ http://libcec.pulse-eight.com/]<br />
* [http://github.com/Pulse-Eight/libcec http://github.com/Pulse-Eight/libcec]<br />
<br />
==libCEC==<br />
libCEC is an open-source dual licensed library originally designed for communicating with the [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx Pulse-Eight USB - HDMI CEC Adaptor].<br />
<br />
* [http://libcec.pulse-eight.com/ http://libcec.pulse-eight.com/]<br />
* [http://github.com/Pulse-Eight/libcec http://github.com/Pulse-Eight/libcec]<br />
<br />
libCEC needs the following dependencies in order to work correctly:<br />
* udev v151 or later<br />
* cdc-acm support compiled into the kernel or available as module<br />
<br />
===libCEC Features===<br />
* Windows, Mac OS X, and Linux support<br />
* Turns on/off TV and receivers (e.g. when the screensaver becomes active, to save power)<br />
* Switch the TV and receivers to the correct HDMI port when starting your media center software<br />
* Send and receive key presses from your TV's remote<br />
* Control the volume of a CEC capable A/V receiver from your media center software<br />
* Sniff active traffic on CEC bus<br />
* Interfaces for C, C++ and .NET/CLR<br />
* No binary-only or obfuscated code; everything is open and can be modified<br />
* Example implementations in C++ and C#<br />
* And much more...<br />
<br />
===libCEC supported software===<br />
* XBMC v11.0 "Eden" or higher<br />
* MythTV v0.25 or higher<br />
<br />
==Alternative open source libraries and code for CEC==<br />
Alternative, a cross-platform CEC library designed for Realtek SoC, a GPL v3 libraries exists for Arduino board (tmega series chip) and the TI msp430 chip the TI MSP430 chip, that could probably also be modified to work on the Broadcom BCM2835 SoC in the Raspberry Pi.<br />
<br />
Realtek 1283 SoC ('MARS') platforms with CEC, a cross CEC library and a CEC daemon/service<br />
* http://sourceforge.net/apps/trac/cecd/<br />
* http://sourceforge.net/projects/cecd<br />
* http://cecd.git.sourceforge.net/git/gitweb.cgi?p=cecd/cecd;a=summary<br />
<br />
cec-arduino - Arduino library for communicating with HDMI CEC equipment<br />
* http://code.google.com/p/cec-arduino/<br />
* http://www.andrewncarr.com/hdmi-cec.html<br />
* http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1261237176/all<br />
<br />
TI msp430 linux changes and CEC library repository<br />
* http://cgit.freedesktop.org/~deathsimple/cec/<br />
<br />
SH4 duckbox<br />
* http://gitorious.org/open-duckbox-project-sh4<br />
<br />
==External links with more information for developers==<br />
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf Broadcom BCM2835 ARM peripherals datasheet (PDF)]<br />
* [http://www.cec-o-matic.com/ CEC-O-Matic website, helps developers in decoding and creating CEC frames for communication] - For the general user, the cec-o-matic.com website also gives an idea as to what can be achieved in a home automation system using CEC with HDMI equipment<br />
* [http://www.quantumdata.com/pdf/CEC_White_Paper.pdf Quantum Data white paper - Designing CEC into your next HDMI Product (PDF)]<br />
* [http://www.hdmi.org/pdf/whitepaper/DesigningCECintoYourNextHDMIProduct.pdf HDMI.org - Designing CEC into your next HDMI Product (PDF)]<br />
* [http://www.hdmi.org/ces2008/presentations/2008_CES_HDMITechZone_SimplayLabs.pdf The Promise of HDMI-CEC (PDF)]<br />
* [http://xtreamerdev.googlecode.com/files/CEC_Specs.pdf HDMI-CEC Specifications v1.3a]<br />
* [http://rainshadowtech.com/downloads/HDMICECtoUSBandRS232v2.0.pdf RainShadow Tech LLC - HDMI-CEC to USB Bridge and HDMI-CEC to RS-232 Bridge (PDF)]<br />
* [http://www.kwikwai.com/index.php Kwikwai's HDMI CEC-Ethernet-USB-Serial bridge]</div>Kwihttps://elinux.org/index.php?title=RPi_Beginners&diff=136862RPi Beginners2012-06-04T22:01:54Z<p>Kwi: /* Basic Debian RPi Setup */</p>
<hr />
<div>[[Category:RaspberryPi]]<br />
{{Template:RPi_Startup}}<br />
<br />
''' INFO : If you are looking for any information related to SD Cards and setup look <br />
[[RPi Easy SD Card Setup | here]] There is some restructuring going on , we are sorry for the inconvenience. '''<br />
<br />
=About This Page - For Contributors=<br />
The intention of this page is to provide a '''starting point''' for beginners and to '''direct them to''' the kind of information a person would need in order to start doing something useful or interesting with a Raspberry Pi.<br />
<br />
It is not intended to contain or replicate much of the information already available on-line or elsewhere in the wiki, however please create new wiki pages and link them here if there is information beginners will find useful (similarly any section which grows too much here, should be separated into new pages as and when needed)!<br />
<br />
At the moment building up ideas of content of typical things beginners will want to know and the kind of things they will want to do first.<br />
<br />
----<br />
<br />
<br />
<br />
=Where to start?=<br />
Any easy question to ask, but a very difficult one to answer!<br />
# If you need to get a RPi, the see the [[RPi Buying Guide|Buying Guide]].<br />
# If you need to know what equipment you will need and how to set it up, see the [[RPi Hardware Basic Setup|Basic Hardware Setup]] page.<br />
# If you need to install/setup an SD card see the [[RPi Easy SD Card Setup|Preload your Card]] section.<br />
# If something is not working, check the [[R-Pi_Troubleshooting|Troubleshooting]] section.<br />
# If you need help with Debian, try the [http://wiki.debian.org/FrontPage Debian Wiki].<br />
# If you've done all that, and you are wondering what next...'''welcome and read on!'''<br />
<br />
<br />
References needed (idea for new section Living Without RPi, which can guide users or link to info to users who haven't got RPis)<br />
Link to emulation builds or live linux cds setup for beginners (RacyPy2 for example)<br />
If you don't have a Raspberry Pi yet, you can still try things out, see xxxx for details.<br />
<br />
=What is Linux and why not use Windows?=<br />
Linux is an operating system just like Windows, however, unlike Windows (which needs a set hardware requirement to run i.e. One Size fits or get different hardware), Linux comes in many varieties and configurations which means you can usually find a flavour (or Distribution) which fits your hardware big or small / fast or slow.<br />
<br />
The Raspberry Pi is not suited to running Windows due to its hardware, but there are plenty of Linux Distributions which fit nicely. In addition to this, most Distributions of Linux are free, however Windows can cost many times the price of the Raspberry Pi itself.<br />
<br />
Chances are you already have Linux running in your home without you even knowing it, since it is commonly used in modern TVs, Freeview and cable boxes to run things and ensure your recording of '''Inbetweeners''' or '''Prison Break''' gets done!<br />
<br />
For more information about Linux see <br />
[http://en.wikipedia.org/wiki/Linux Wikipedia]<br />
<br />
Also see [http://elinux.org/RPi_End-user_FAQ End-User FAQ]<br />
And [http://elinux.org/Will_RPi_Run Running XXX on the RPi]<br />
<br />
=Basic Debian RPi Setup=<br />
When you first turn on your Raspberry Pi with it's fresh Debian image on the SD card, you will likely want to tweak the system settings.<br />
<br />
== Locale settings ==<br />
<br />
By configuring the [[wikipedia:locale|locale]] settings, you can change the language and country settings (e.g. to get correct sorting behaviour) for much of the software available for the RPi. The default RPi locale is English/Great Britain ("en_GB").<br />
<br />
You can alter this with <br />
<br />
sudo dpkg-reconfigure locales<br />
<br />
You will get a very long list of possible locales. You can enable/disable a locale by pressing the spacebar (not Enter), and scroll through the list using the arrow keys or PgUp/PgDn.<br />
<br />
Selecting "All locales" will generate all possible locales, taking a very long time and using a great deal of space. Select only those you wish to use.<br />
<br />
''It is highly recommended to stick to the UTF-8 locales'', and to leave the en_GB.UTF-8 locale enabled, in addition to any other locales you enable.<br />
<br />
If you're unsure of which locale to pick, look up a [[wikipedia:List of ISO 639-1 codes|two-letter language code]] and a [[wikipedia:ISO 3166-1 alpha-2#Officially assigned code elements|two-letter country code]] on Wikipedia, and see if you can find a matching locale.<br />
<br />
When you're done picking locale(s), press Enter. You will be prompted to select a default locale as well.<br />
<br />
== Keyboard layout ==<br />
<br />
If different letters appear on-screen from that which you typed, you need to reconfigure you keyboard settings. In Debian, from a command line type:<br />
<br />
sudo dpkg-reconfigure keyboard-configuration<br />
<br />
Follow the prompts.<br />
<br />
'''Or:''' From the command line type:<br />
sudo nano /etc/default/keyboard<br />
<br />
Then find where it says<br />
<br />
XKBLAYOUT="gb"<br />
<br />
and change the gb to the [[wikipedia:ISO 3166-1 alpha-2#Officially assigned code elements|two-letter code]] for your country. [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=78325#p78325]<br />
<br />
Also, see the [[R-Pi_Troubleshooting#Re-mapping_the_keyboard_with_Debian_Squeeze|Troubleshooting Guide]] for more information about remapping the keyboard.<br />
<br />
You may need to restart for the changes to take effect.<br />
<br />
If you get a very long delay during the keyboard mapping at startup, type the following once on the command line after you have logged in:<br />
<br />
sudo setupcon<br />
<br />
If the selected keyboard layout is not applied in the console (that is, when not running under X), try:<br />
<br />
sudo apt-get install console-data<br />
<br />
== Timezone ==<br />
<br />
Unless you live in Great Britain, you'll have to change the default timezone:<br />
<br />
sudo dpkg-reconfigure tzdata<br />
<br />
Select geographic area - Europe, America or whatever. Etc gives UNIX compatible time zones including CUT, GMT, UTC<br />
<br />
Select city<br />
<br />
Follow the prompts to finish the config. The change should be immediate.<br />
<br />
== Create a new user with sudo-privileges ==<br />
<br />
You may want to create a new user account for yourself.<br />
<br />
Type in following command in the terminal to create a new user:<br />
<br />
sudo adduser username<br />
<br />
Follow the steps.<br />
<br />
To allow the newly created user to use the "sudo" command, type:<br />
sudo visudo<br />
<br />
Add following line under the "root ALL=(ALL) ALL" Line:<br />
<br />
yourUsername ALL=(ALL) ALL<br />
<br />
Now press CTRL+K, X to save and exit the editor.<br />
<br />
Alternatively instead of adding the user to the sudoers list, you can add your user to the sudo group with the following command:<br />
<br />
useradd -G sudo yourUsername<br />
<br />
=Intro to the CLI (Command Line Interface)=<br />
You will need to use the Command Line Interface at some point in your management of the RPi. The command line interface is a powerful way to interact with the Raspberry Pi and is well worth learning some basic commands to get started with.<br />
<br />
For an introductory guide to some basic commands please see: [http://elinux.org/CLI_Spells Command Line Interface "Must Have" Commands]<br />
<br />
Your SD card may boot into a GUI, if not and you are done with the text interface and want to use a graphical one instead, run:<br />
<br />
startx<br />
<br />
=Remote Access=<br />
Your default install probably has a ssh (secure shell) "daemon" running. <br />
This means that you can run everything on your Rpi with only the network attached. Provided you know which ip address it has. With appropriate software installed on your Winodws, Mac or Linux PC, you can also run a gui remotely.<br />
[[RPi Remote Access|Remote Access]]<br />
<br />
=Adding more software to your Raspberry Pi=<br />
You will probably want to add software to your Raspberry Pi. Here you can find out how to do it.<br />
[http://elinux.org/Add_software Adding Software]<br />
<br />
=Adding USB Storage to Your Raspberry Pi=<br />
Sooner or later, you're going to run out of room on the SD card used to boot up your Raspberry Pi. For a tutorial on how to connect USB flash drives and hard drives to your Pi to expand storage, see: [http://elinux.org/Adding_USB_Drives_to_a_Raspberry_Pi Adding USB Drives to a Raspberry Pi]<br />
<br />
=Beginner Projects=<br />
Here are a few things you can try out with your Raspberry Pi, in most cases all you'll need is your SD Card loaded with a particular preconfigured OS Distribution.<br />
<br />
It will be worth getting a few spare SD Cards if you think you will switch between setups regularly or become familiar with how to '''back up and restore''' your card.<br />
Reference needed - a good guide on how to backup and restore cards or software to do this easily<br />
<br />
<br />
==Media Player==<br />
With this configuration you will typically have the Raspberry Pi connected to a TV or large monitor and a source of videos/music/photos etc you wish to play (i.e. Internet/hard-drive/local network etc).<br />
<br />
DesignSpark have written an article on this, which is worth a look, [http://www.designspark.com/content/raspberry-pi-goes-movies DesignSpark - Raspberry Pi goes to the movies]<br />
<br />
Reference needed - links to a specific wiki page covering this in detail or links to projects like<br />
OpenElec, CrystalBuntu, Raspbmc etc<br />
<br />
==Play Games==<br />
While there are not any commercial games for the Raspberry Pi (yet) there are plenty ways to play games on it.<br />
<br />
Many distributions will have games built into them, and some may well support emulation of other platforms so you can run those games.<br />
<br />
Also, a lot of Raspberry Pi users will be writing simple games which will be available for others to enjoy (and if desired added to or modified).<br />
<br />
Reference needed - game section is empty at the moment!<br />
''See the [[RPi Games|Games Section]] for more details''<br />
<br />
<br />
==Introducing Young Children To Computers==<br />
Reference needed - some kid friendly and fun stuff!<br />
<br />
<br />
==Teaching==<br />
There is a huge number of groups, links and resources available within the [[RPi Education|Education]] section.<br />
Reference needed - links to the learning pages, education links and school/university groups<br />
<br />
<br />
==Learn To Program==<br />
There is a huge selection of [[RPi Programming|programming languages]] which you can use to write interesting programs, games, applications and utilities. There are also more great links within the [[RPi Education#Programming languages|Education]] section.<br />
<br />
There is a huge selection to choose from (not just Python...) which should suit any ability and a range of purposes.<br />
<br />
If you are new to programming, there are plenty of tutorials for getting started in the [[RPi Tutorials|Tutorials]] Section.<br />
<br />
Books about programming can be found in the [[RPi Programming Books|Books]] Section.<br />
<br />
In the latest Debian, Python (+Pygame) and MIT Scratch are pre-installed.<br />
<br />
Reference needed - links to the learning pages, recommended books?<br />
<br />
==Interface With Hardware==<br />
# [[RPi Interfacing with hardware|Interfacing with Arduino]]<br />
<br />
Reference needed - links to basic circuits tutorials and expansion boards<br />
<br />
<br />
==Word Processing/Internet Browsing etc==<br />
Yes, the Raspberry Pi can do the majority of the dull stuff too which other computers do.<br />
<br />
'''Debian''' currently comes with Midori installed for web browsing and word processing programs be installed rather easily.<br />
<br />
*Entering "sudo apt-get install chromium-browser" into a terminal will install Chromium which is generally a faster and more featured browser than Midori<br />
*Entering "sudo apt-get install openoffice.org" into a terminal will install OpenOffice.org, a free Microsoft Office-like application suite<br />
*Entering "sudo apt-get install abiword-common" into a terminal will install AbiWord, a lighter weight but still fully functional word processor<br />
*Entering "sudo apt-get install gnumeric" into a terminal will install Gnumeric, a lighter weight but still fully functional spreadsheet<br />
<br />
More information needed<br />
<br />
==Your Own Pet Project!==<br />
The sky is the limit really, with some time and effort any number of projects can be achieved.<br />
<br />
Even if you don't have the skill to do it yourself, you can join like minded people by getting involved with one of the numerous groups in the [[RPi Community|Community Section]], also within the [[RPi Education|Education]] pages or learn what you need in from the [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]] sections.<br />
<br />
Of course, if you do anything interesting then please let us know in the [[RPi Projects |Projects]] section.<br />
<br />
<br />
=Living Without RPi=<br />
Even if you do not have any Raspberry Pi hardware there are a number things you can do to learn about linux, programming or even controlling hardware.<br />
<br />
==Using Linux==<br />
You can install a version of Linux on most computers, and many you will be able to "try out" Linux by using a "Live CD" - this will start your computer up running from a CD or DVD and run Linux (without installing anything to the computer itself).<br />
<br />
RacyPy - This is a simple LiveCD of Puppy Linux which includes some basic programming languages and a light-weight graphical user interface (GUI).<br />
<br />
You can get it from here:<br />
<br />
[http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ teampython RacyPy]<br />
<br />
==Trying Programming==<br />
Many of the programming languages you can use on the Raspberry Pi can be installed on a Windows or Mac machine. Just visit the websites of the languages you are interested in and see if they have an installer for your operating system.<br />
<br />
==Controlling Hardware==<br />
As discussed in the [[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] tutorials, there are lots of alternative hardware you can use to experiment with (some as little as $5).<br />
<br />
<br />
<br />
=References=<br />
<references/><br />
{{Template:Raspberry Pi}}</div>Kwihttps://elinux.org/index.php?title=Template:Raspberry_Pi&diff=135506Template:Raspberry Pi2012-06-01T16:14:15Z<p>Kwi: + Troubleshooting</p>
<hr />
<div>{{Navbox<br />
| name = Raspberry Pi<br />
| title = [[R-Pi Hub|<span style="color:#FFFFFF">Raspberry Pi</span>]]<br />
|listclass = hlist<br />
| state = plain<br />
| style = width:100%<br />
| image = [[File:RpiFront.jpg|167px]]<br />
<br />
| basestyle = background:#00CC00;<br />
| groupstyle = background:#AA0033<br />
| liststyle = background:#FFE0FF;<br />
<br />
<br />
| group1 = '''<span style="color:#FFFFFF">Startup</span>'''<br />
| list1 = <br />
[[RPi Buying Guide|Buying Guide]] - [[RPi Easy SD Card Setup|SD Card Setup]] - [[RPi Hardware Basic Setup|Basic Setup]] - [[RPi Advanced Setup|Advanced Setup]] - [[RPi Beginners|Beginners Guide]] - [[R-Pi Troubleshooting|Troubleshooting]]<br />
<br />
| group2 = '''<span style="color:#FFFFFF">Hardware</span>'''<br />
| list2 = [[RPi Hardware|Hardware]] - [[RPi HardwareHistory|Hardware History]] - [[RPi Low-level peripherals|Low-level peripherals]] - [[RPi Expansion Boards|Expansion Boards]]<br />
<br />
| group3 = '''<span style="color:#FFFFFF">Peripherals</span>'''<br />
| list3 = <br />
[[RPi Screens|Screens]] - [[RPi Cases|Cases]] - [[RPi VerifiedPeripherals|Other Peripherals]]<br />
<br />
| group4 = '''<span style="color:#FFFFFF">Software</span>'''<br />
| list4 =<br />
[[RPi Software|Software]] - [[RPi Distributions|Distributions]] - [[RPi Kernel Compilation|Kernel]] - [[RPi Performance|Performance]] - [[RPi Programming|Programming]]<br />
<br />
| group5 = '''<span style="color:#FFFFFF">Projects</span>'''<br />
| list5 =<br />
[[RPi Tutorials|Tutorials]] - [[RPi Guides|Guides]] - [[RPi Projects|Projects]] - [[RPi Tasks|Tasks]] - [[RPi DatasheetCategories|DataSheets]] - [[RPi Education|Education]] - [[RPi Community|Communities]] <br />
<br />
<br />
| below =<br />
<br />
}}<noinclude>'''''Please use this template only for the English language version''''', and make a copy if you wish to use it for another language. Please be careful when editing and use preview, as this template appears on a number of pages.<br />
<br />
To add this to a page, use <nowiki>{{Template:Raspberry Pi}}</nowiki><br />
<br />
As the RaspberryPi category is included below, every article using this links table template should be forced to become a member of the category, but feel free to add the category tag to the article anyway as it does no harm.<br />
<br />
If you're wondering how this template is possible - it uses the Navbar, Navbox and Transclude templates from wikipedia under Creative Commons Sharealike licence, with CSS info added manually as eLinux doesn't allow editing of the master CSS.</noinclude><br />
<br />
[[Category:RaspberryPi]]</div>Kwihttps://elinux.org/index.php?title=R-Pi_Troubleshooting&diff=132512R-Pi Troubleshooting2012-05-27T16:27:02Z<p>Kwi: /* Memory Cards */</p>
<hr />
<div>Back to the [[R-Pi Hub|Hub]].<br />
<br />
[[Category:RaspberryPi]]<br />
This page lists the most common problems and suggests some solutions.<br />
<br />
==Power / Start-up==<br />
A good power supply that will supply 5V is vital. There is more information about [[RPi_Hardware#Power|power supplies and troubleshooting]].<br />
===Red power LED does not light, nothing on display===<br />
The power is not properly connected.<br />
<br />
===Red power LED is on, green LED does not flash, nothing on display===<br />
*The Raspberry Pi cannot find a valid image on the SD card. Check that you have correctly written a Raspberry Pi image to the card. Some SD cards work when cold, but not when warm from use<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=79008#p79008</ref>. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].<br />
*The voltage is too low (not 5 V), try a different power supply. See also, [[#Troubleshooting_power_problems|Power Problems]].<br />
*''(unlikely)'' hardware abuse, for example by connecting a 7 V supply to a 3v3 GPIO output pin<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76503#p76503</ref> or powering up the board after a solder splash shorts some traces<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76654#p76654</ref>.<br />
<br />
===Kernel Panic on boot ===<br />
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards. <br />
Try again with nothing in the USB.<br />
<br />
===Raspberry Pi shuts down soon after booting up===<br />
This is caused by a power supply with too low voltage or too high voltage. <br />
Or it could be the cable. See: [[On_the_RPi_usb_power_cable]]<br />
<br />
===Pi boots sometimes but not always===<br />
With a known good power supply and known good SD card, the R-Pi boots occasionally, but other times shows only a tiny green flicker from the "OK" LED and it fails to start, even with no USB devices and no Ethernet. This has been reported several times<ref>http://www.raspberrypi.org/forum/troubleshooting/will-not-boot-consistently-any-suggestions-before-i-send-my-pi-back</ref><br />
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref><br />
<ref>http://www.raspberrypi.org/forum/troubleshooting/possible-fault-pi-boots-sometimes-but-not-always</ref> and remains an open issue. Low voltage or an improper SD card can cause it. Some SD cards will work until they warm up slightly, and then fail<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=79008#p79008</ref>. When exposed to 21 C room temperature the warmest part of an uncased working R-Pi should be 41 C<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=78973#p78973</ref>. The wiki has a [[RPi_VerifiedPeripherals#SD_cards | list of working SD cards]]. Buy from a reliable vendor as it has been [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit/ claimed] that 1/3 of all "Sandisk" labelled memory cards are counterfeit.<br />
<br />
==Keyboard / Mouse / Input Devices==<br />
===Keyboard randomly repeats key presses===<br />
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power: most will have a label showing the voltage and mA requirements. They should be 5v 100mA each max, any more than this they must be used with a powered USB hub. Try unplugging every USB device except the keyboard (you should also note that some keyboards have built in hubs and can try to draw 150mA (Pi can only handle 100mA per USB slot without a hub)).<br />
Also, use the latest software. Forum user MrEngman [http://www.raspberrypi.org/forum/absolute-beginners/using-a-powered-usb-port-to-power-a-rpi#p76485 reported] some keyboard repeats and wireless hangs until [http://www.raspberrypi.org/downloads upgrading] to the debian6-19-04-2012 kernel, which he reports stable with no problems even with a low [[R-Pi_Troubleshooting#Troubleshooting_power_problems | TP1-TP2 voltage]] of 4.65 - 4.68 volts.<br />
<br />
===Keyboard / Mouse interferes with USB WiFi device===<br />
Connecting a keyboard and/or mouse while a USB WiFi device is connected, may cause one or both devices to malfunction. On April 30 2012, there was a bugfix<ref>https://github.com/raspberrypi/linux/commit/e09244e60881148431ecd016ccc42f1fa0678556</ref> relating to USB sharing between high-speed (eg. WiFi) and full/low-speed devices (eg. keyboard/mouse). User spennig<ref>http://www.raspberrypi.org/forum/troubleshooting/usb-power-hub-wifi/page-4#p74609</ref><ref>http://www.raspberrypi.org/forum/troubleshooting/success-with-kb-mouse-wifi?value=3761&type=8&include=1&search=1</ref> reports this patch did not fix the Mouse/WiFi conflict. On 2012-05-12, user spennig was pleased to confirm that wifi was working with a USB keyboard and mouse, as long as the Raspberry Pi had a good PSU and a powered hub. Even so, some experimentation was needed, e.g. USB mouse connected to the device, and the keyboard and mouse connected to the powered hub. Some experimentation may be necessary to find a working combination; however a good power supply is essential.<br />
<br />
===Wireless Keyboard trouble===<br />
Some wireless keyboards, for example the Microsoft Wireless Keyboard 800 are reported to fail<ref>http://www.raspberrypi.org/forum/troubleshooting/display-and-keyboard-issues-on-a-real-pi#p74816</ref> even though the current drawn by the wireless adaptor is within the R-Pi USB spec limit of 100 mA. This may be a software driver problem.<br />
<br />
===Re-mapping the keyboard with Debian Squeeze===<br />
If different letters appear on-screen from that which you typed, you need to reconfigure you keyboard settings. In Debian, from a command line type:<br />
sudo dpkg-reconfigure keyboard-configuration<br />
Follow the prompts. Then restart your RasPi.<br />'''Or:'''<br /> From the command line type:<br />
sudo nano /etc/default/keyboard<br />
Then find where it says <blockquote>XKBLAYOUT=”gb”</blockquote>and change the gb to the two letter code for your country. [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=78325#p78325]<br />
<br />
===Slow keyboard mapping=== <br />
If you have remapped your keyboard and get a very long delay during the keyboard mapping at startup, type the following once on the command line after you have logged in:<br />
sudo setupcon<br />
<br />
== SD cards ==<br />
<br />
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].<br />
* If you are having problems setting up your SD card you might want to start by erasing it completely - especially if it has been used elsewhere and still contains data / partitions.<br />
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/<br />
* After writing the image to the SD card, verify that you can see the boot partition when you insert the SD card into your computer. The partition should contain a number of files, including ''start.elf'' and ''kernel.img''. If you do not see these files on the SD card, you have made an error writing the image file.<br />
* If you are manually preparing your SD card on Linux or Mac OS using the ''dd'' command, this operation will completely erase any existing data and partitions. Make sure you write to the whole card (e.g. <tt>/dev/sdd</tt>) and not to an existing partition (e.g. <tt>/dev/sdd1</tt>).<br />
<br />
==Networking==<br />
<br />
===Ethernet connection is lost when a USB device is plugged in===<br />
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power (>100 mA), 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.<br />
<br />
===Ethernet connects at 10M instead of 100M===<br />
The LED in the corner of the board labelled "10M" is mislabeled. When that LED is on, the R-Pi is actually connected at 100 Mbps. You can confirm the true transfer rate using a network benchmark such as iperf. You can also read the current network speed with<br />
cat /sys/class/net/eth0/speed<br />
<br />
==Passwords==<br />
===I do not know the password to login===<br />
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.<br />
<br />
<br />
Debian from later dates - pi/raspberry<br />
Debian Feb 17 - pi/suse<br />
Arch - root/root<br />
<br />
===Some programs refuse to accept my password===<br />
While using Debian, some programs may ask for your password but refuse to accept a valid password.<br />
<br />
This is a fault in some Debian images and will be fixed soon. If you are using an image with this fault, enter the following command on the command line.<br />
gconftool-2 -\-type bool -\-set /apps/gksu/sudo-mode true<br />
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.<br />
<br />
==Sound==<br />
===Sound does not work with an HDMI monitor===<br />
This is caused by some computer monitors which select DVI mode even if an HDMI cable is connected. This fix may be necessary even if other HDMI devices work perfectly on the same monitor (or TV)!<br />
<br />
Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file:<br />
hdmi_drive=2<br />
<br />
This will force it to select HDMI mode.<br />
<br />
===Sound does not work at all, or in some applications===<br />
The ALSA sound driver is "alpha" and has issues, but some applications do work. If you are running Debian, try<br />
<br />
cd /opt/vc/src/hello_pi/hello_audio<br />
make<br />
./hello_audio.bin<br />
<br />
to test analogue output. And<br />
<br />
./hello_audio.bin 1<br />
<br />
to test HDMI.<br />
<br />
To test other applications (''before'' "startx"), type<br />
<br />
sudo apt-get install alsa-utils<br />
sudo modprobe snd_bcm2835<br />
sudo aplay /usr/share/sounds/alsa/Front_Center.wav<br />
<br />
By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:<br />
<br />
sudo amixer cset numid=3 <n><br />
<br />
where n is 0=auto, 1=headphones, 2=hdmi.<br />
<br />
==Display==<br />
===Startx fails to start===<br />
If you just get errors instead of a desktop when typing<br />
startx<br />
you may be out of storage space on the SD card. By default there are only a few hundred MB free in the 2 GB main partition, which can quickly fill up if you download files. Make sure there is some space free (gparted can expand a partition, if the SD card is > 2GB). Also, installing some software may incorrectly create or modify a .Xauthority file in your home directory, causing startx to fail, according to [http://www.raspberrypi.org/forum/troubleshooting/startx-fails-worked-yesterday this thread]. Temporarily renaming, moving, or deleting that file may fix the problem.<br />
<br />
===Video does not play or plays very slowly===<br />
The only hardware-accelerated video player is the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XMBC distribution] and its command line variant [[omxplayer]]. H264 is the only hardware-accelerated codec, for playback. No hardware encoding is supported. Additional codecs were not purchased as licensing fees would have increased the R-Pi's price.<br />
<br />
===Can only get 800x480 resolution in LXDE (Arch linux)===<br />
Known issue with distro package as of 17th April 2012 - there's some missing boot config information. Creating a suitable cmdline.txt fixes it - type the following at the Raspberry Pi command line:<br />
<br />
<pre><br />
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt<br />
</pre><br />
<br />
===Big black borders around small image on HD monitors===<br />
<br />
Out of the box, R-Pi graphics don't necessarily fill the 1080p (ie Full HD) screen. This is due to something called "Underscan", and it can be fixed easily.<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following lines to the configuration file...<br />
<br />
If your display has no overscan:<br />
<br />
<pre><br />
<br />
disable_overscan=1<br />
<br />
</pre><br />
<br />
or if your display has some overscan:<br />
<br />
<pre><br />
<br />
overscan_left=-20<br />
<br />
overscan_right=-20<br />
<br />
overscan_top=-20<br />
<br />
overscan_bottom=-20<br />
<br />
</pre><br />
<br />
Making the R-Pi graphics fill the screen is a matter of experimenting with the numbers you put in the config.txt file. Change the numbers – try jumps of 5 or 10 at a time. Bigger negative numbers reduce the black borders (so -40 means less black border than -20). The numbers do not all have to be the same; you can use this feature to centre the display on the screen.<br />
<br />
===Writing spills off the screen on HD monitors===<br />
<br />
Out of the box, R-Pi graphics may be larger than the 1080p (ie Full HD) screen. This is due to something called "Overscan", and it can be fixed easily by creating a simple text file on the R-Pi SD card by using Notepad on your PC.<br />
<br />
Follow the instructions in the section "Big black borders around small image on HD monitors", but use positive numbers for the overscan settings, for example<br />
<pre><br />
<br />
overscan_left=20<br />
<br />
overscan_right=20<br />
<br />
overscan_top=20<br />
<br />
overscan_bottom=20<br />
<br />
</pre><br />
<br />
===Interference visible on a HDMI or DVI monitor===<br />
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.<br />
[[File:RPi_HDMI_interference.jpg|600px]]<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file<br />
config_hdmi_boost=4<br />
<br />
You may experiment with different values of config_hdmi_boost. Value 1 is used for very short cables, value 7 is used for very long cables.<br />
<br />
===Composite displays only back and white or no image===<br />
We default to NTSC output. Most TVs will show an image with that, but if not:<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file<br />
sdtv_mode=2<br />
<br />
(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)<br />
<br />
==GPIO==<br />
Remember that the GPIO pins are 3.3V logic level only, and are <strong>NOT</strong> 5V tolerant.<br />
<br />
If you momentarily shorted the two end GPIO pins together (+3.3V and +5V), or a supply pin to ground, and the Pi appears to be dead, don't panic. The input polyfuse may have tripped. It is self-resetting after it cools down. Disconnect power and wait for 30 minutes, then try to restart.<br />
<br />
==General==<br />
===The time is incorrect===<br />
If the clock is off by a series of hours, in the command line type:<br />
sudo dpkg-reconfigure tzdata<br />
<br />
==Troubleshooting power problems==<br />
If you think you have a problem with your power supply, it is a good idea to check the actual voltage<br />
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board<br />
to facilitate voltage measurements.<br />
<br />
Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable.<br />
<br />
If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]<br />
<br />
Note: Even if the multimeter shows the correct voltage, you may have some power supply problems. A multimeter only displays the average voltage. If there are very short-lived dips or spikes in the voltage, these will not be shown by the multimeter. <br />
<br />
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]<br />
<br />
==References==<br />
<references><br />
</references></div>Kwihttps://elinux.org/index.php?title=R-Pi_Troubleshooting&diff=132362R-Pi Troubleshooting2012-05-27T13:00:20Z<p>Kwi: /* Sound does not work at all, or in some applications */ alsa-utils is not installed on the Debian image, so no there's no aplay/amixer by default. Also: Specify a known good wav in the example</p>
<hr />
<div>Back to the [[R-Pi Hub|Hub]].<br />
<br />
[[Category:RaspberryPi]]<br />
This page lists the most common problems and suggests some solutions.<br />
<br />
==Power / Start-up==<br />
A good power supply that will supply 5V is vital. There is more information about [[RPi_Hardware#Power|power supplies and troubleshooting]].<br />
===Red power LED does not light, nothing on display===<br />
The power is not properly connected.<br />
<br />
===Red power LED is on, green LED does not flash, nothing on display===<br />
*The Raspberry Pi cannot find a valid image on the SD card. Check that you have correctly written a Raspberry Pi image to the card. Some SD cards work when cold, but not when warm from use<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=79008#p79008</ref>. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].<br />
*The voltage is too low (not 5 V), try a different power supply. See also, [[#Troubleshooting_power_problems|Power Problems]].<br />
*''(unlikely)'' hardware abuse, for example by connecting a 7 V supply to a 3v3 GPIO output pin<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76503#p76503</ref> or powering up the board after a solder splash shorts some traces<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76654#p76654</ref>.<br />
<br />
===Kernel Panic on boot ===<br />
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards. <br />
Try again with nothing in the USB.<br />
<br />
===Raspberry Pi shuts down soon after booting up===<br />
This is caused by a power supply with too low voltage or too high voltage. <br />
Or it could be the cable. See: [[On_the_RPi_usb_power_cable]]<br />
<br />
===Pi boots sometimes but not always===<br />
With a known good power supply and known good SD card, the R-Pi boots occasionally, but other times shows only a tiny green flicker from the "OK" LED and it fails to start, even with no USB devices and no Ethernet. This has been reported several times<ref>http://www.raspberrypi.org/forum/troubleshooting/will-not-boot-consistently-any-suggestions-before-i-send-my-pi-back</ref><br />
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref><br />
<ref>http://www.raspberrypi.org/forum/troubleshooting/possible-fault-pi-boots-sometimes-but-not-always</ref> and remains an open issue. Low voltage or an improper SD card can cause it. Some SD cards will work until they warm up slightly, and then fail<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=79008#p79008</ref>. When exposed to 21 C room temperature the warmest part of an uncased working R-Pi should be 41 C<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=78973#p78973</ref>. The wiki has a [[RPi_VerifiedPeripherals#SD_cards | list of working SD cards]]. Buy from a reliable vendor as it has been [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit/ claimed] that 1/3 of all "Sandisk" labelled memory cards are counterfeit.<br />
<br />
==Keyboard / Mouse / Input Devices==<br />
===Keyboard randomly repeats key presses===<br />
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power: most will have a label showing the voltage and mA requirements. They should be 5v 100mA each max, any more than this they must be used with a powered USB hub. Try unplugging every USB device except the keyboard (you should also note that some keyboards have built in hubs and can try to draw 150mA (Pi can only handle 100mA per USB slot without a hub)).<br />
Also, use the latest software. Forum user MrEngman [http://www.raspberrypi.org/forum/absolute-beginners/using-a-powered-usb-port-to-power-a-rpi#p76485 reported] some keyboard repeats and wireless hangs until [http://www.raspberrypi.org/downloads upgrading] to the debian6-19-04-2012 kernel, which he reports stable with no problems even with a low [[R-Pi_Troubleshooting#Troubleshooting_power_problems | TP1-TP2 voltage]] of 4.65 - 4.68 volts.<br />
<br />
===Keyboard / Mouse interferes with USB WiFi device===<br />
Connecting a keyboard and/or mouse while a USB WiFi device is connected, may cause one or both devices to malfunction. On April 30 2012, there was a bugfix<ref>https://github.com/raspberrypi/linux/commit/e09244e60881148431ecd016ccc42f1fa0678556</ref> relating to USB sharing between high-speed (eg. WiFi) and full/low-speed devices (eg. keyboard/mouse). User spennig<ref>http://www.raspberrypi.org/forum/troubleshooting/usb-power-hub-wifi/page-4#p74609</ref><ref>http://www.raspberrypi.org/forum/troubleshooting/success-with-kb-mouse-wifi?value=3761&type=8&include=1&search=1</ref> reports this patch did not fix the Mouse/WiFi conflict. On 2012-05-12, user spennig was pleased to confirm that wifi was working with a USB keyboard and mouse, as long as the Raspberry Pi had a good PSU and a powered hub. Even so, some experimentation was needed, e.g. USB mouse connected to the device, and the keyboard and mouse connected to the powered hub. Some experimentation may be necessary to find a working combination; however a good power supply is essential.<br />
<br />
===Wireless Keyboard trouble===<br />
Some wireless keyboards, for example the Microsoft Wireless Keyboard 800 are reported to fail<ref>http://www.raspberrypi.org/forum/troubleshooting/display-and-keyboard-issues-on-a-real-pi#p74816</ref> even though the current drawn by the wireless adaptor is within the R-Pi USB spec limit of 100 mA. This may be a software driver problem.<br />
<br />
===Re-mapping the keyboard with Debian Squeeze===<br />
If different letters appear on-screen from that which you typed, you need to reconfigure you keyboard settings. In Debian, from a command line type:<br />
sudo dpkg-reconfigure keyboard-configuration<br />
Follow the prompts. Then restart your RasPi.<br />'''Or:'''<br /> From the command line type:<br />
sudo nano /etc/default/keyboard<br />
Then find where it says <blockquote>XKBLAYOUT=”gb”</blockquote>and change the gb to the two letter code for your country. [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=78325#p78325]<br />
<br />
===Slow keyboard mapping=== <br />
If you have remapped your keyboard and get a very long delay during the keyboard mapping at startup, type the following once on the command line after you have logged in:<br />
sudo setupcon<br />
<br />
==Memory Cards==<br />
===General / Formatting===<br />
If you are having problems setting up your memory card you might want to try erasing it completely - especially if it has been used elsewhere and still contains data / partitions. <br />
* Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/<br />
<br />
* If you are preparing your SD card on a Linux-based system using the ''dd'' command, this operation will completely erase any existing data and partitions. Make sure you put the source image on the whole card, e.g. /dev/sdd, NOT /dev/sdd1.<br />
<br />
===SD Card Does Not Boot===<br />
Some memory cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].<br />
<br />
==Networking==<br />
<br />
===Ethernet connection is lost when a USB device is plugged in===<br />
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power (>100 mA), 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.<br />
<br />
===Ethernet connects at 10M instead of 100M===<br />
The LED in the corner of the board labelled "10M" is mislabeled. When that LED is on, the R-Pi is actually connected at 100 Mbps. You can confirm the true transfer rate using a network benchmark such as iperf. You can also read the current network speed with<br />
cat /sys/class/net/eth0/speed<br />
<br />
==Passwords==<br />
===I do not know the password to login===<br />
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.<br />
<br />
<br />
Debian from later dates - pi/raspberry<br />
Debian Feb 17 - pi/suse<br />
Arch - root/root<br />
<br />
===Some programs refuse to accept my password===<br />
While using Debian, some programs may ask for your password but refuse to accept a valid password.<br />
<br />
This is a fault in some Debian images and will be fixed soon. If you are using an image with this fault, enter the following command on the command line.<br />
gconftool-2 -\-type bool -\-set /apps/gksu/sudo-mode true<br />
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.<br />
<br />
==Sound==<br />
===Sound does not work with an HDMI monitor===<br />
This is caused by some computer monitors which select DVI mode even if an HDMI cable is connected. This fix may be necessary even if other HDMI devices work perfectly on the same monitor (or TV)!<br />
<br />
Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file:<br />
hdmi_drive=2<br />
<br />
This will force it to select HDMI mode.<br />
<br />
===Sound does not work at all, or in some applications===<br />
The ALSA sound driver is "alpha" and has issues, but some applications do work. If you are running Debian, try<br />
<br />
cd /opt/vc/src/hello_pi/hello_audio<br />
make<br />
./hello_audio.bin<br />
<br />
to test analogue output. And<br />
<br />
./hello_audio.bin 1<br />
<br />
to test HDMI.<br />
<br />
To test other applications (''before'' "startx"), type<br />
<br />
sudo apt-get install alsa-utils<br />
sudo modprobe snd_bcm2835<br />
sudo aplay /usr/share/sounds/alsa/Front_Center.wav<br />
<br />
By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:<br />
<br />
sudo amixer cset numid=3 <n><br />
<br />
where n is 0=auto, 1=headphones, 2=hdmi.<br />
<br />
==Display==<br />
===Startx fails to start===<br />
If you just get errors instead of a desktop when typing<br />
startx<br />
you may be out of storage space on the SD card. By default there are only a few hundred MB free in the 2 GB main partition, which can quickly fill up if you download files. Make sure there is some space free (gparted can expand a partition, if the SD card is > 2GB). Also, installing some software may incorrectly create or modify a .Xauthority file in your home directory, causing startx to fail, according to [http://www.raspberrypi.org/forum/troubleshooting/startx-fails-worked-yesterday this thread]. Temporarily renaming, moving, or deleting that file may fix the problem.<br />
<br />
===Video does not play or plays very slowly===<br />
The only hardware-accelerated video player is the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XMBC distribution] and its command line variant [[omxplayer]]. H264 is the only hardware-accelerated codec, for playback. No hardware encoding is supported. Additional codecs were not purchased as licensing fees would have increased the R-Pi's price.<br />
<br />
===Can only get 800x480 resolution in LXDE (Arch linux)===<br />
Known issue with distro package as of 17th April 2012 - there's some missing boot config information. Creating a suitable cmdline.txt fixes it - type the following at the Raspberry Pi command line:<br />
<br />
<pre><br />
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt<br />
</pre><br />
<br />
===Big black borders around small image on HD monitors===<br />
<br />
Out of the box, R-Pi graphics don't necessarily fill the 1080p (ie Full HD) screen. This is due to something called "Underscan", and it can be fixed easily.<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following lines to the configuration file...<br />
<br />
If your display has no overscan:<br />
<br />
<pre><br />
<br />
disable_overscan=1<br />
<br />
</pre><br />
<br />
or if your display has some overscan:<br />
<br />
<pre><br />
<br />
overscan_left=-20<br />
<br />
overscan_right=-20<br />
<br />
overscan_top=-20<br />
<br />
overscan_bottom=-20<br />
<br />
</pre><br />
<br />
Making the R-Pi graphics fill the screen is a matter of experimenting with the numbers you put in the config.txt file. Change the numbers – try jumps of 5 or 10 at a time. Bigger negative numbers reduce the black borders (so -40 means less black border than -20). The numbers do not all have to be the same; you can use this feature to centre the display on the screen.<br />
<br />
===Writing spills off the screen on HD monitors===<br />
<br />
Out of the box, R-Pi graphics may be larger than the 1080p (ie Full HD) screen. This is due to something called "Overscan", and it can be fixed easily by creating a simple text file on the R-Pi SD card by using Notepad on your PC.<br />
<br />
Follow the instructions in the section "Big black borders around small image on HD monitors", but use positive numbers for the overscan settings, for example<br />
<pre><br />
<br />
overscan_left=20<br />
<br />
overscan_right=20<br />
<br />
overscan_top=20<br />
<br />
overscan_bottom=20<br />
<br />
</pre><br />
<br />
===Interference visible on a HDMI or DVI monitor===<br />
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.<br />
[[File:RPi_HDMI_interference.jpg|600px]]<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file<br />
config_hdmi_boost=4<br />
<br />
You may experiment with different values of config_hdmi_boost. Value 1 is used for very short cables, value 7 is used for very long cables.<br />
<br />
===Composite displays only back and white or no image===<br />
We default to NTSC output. Most TVs will show an image with that, but if not:<br />
<br />
Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].<br />
<br />
Add the following line to the configuration file<br />
sdtv_mode=2<br />
<br />
(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)<br />
<br />
==GPIO==<br />
Remember that the GPIO pins are 3.3V logic level only, and are <strong>NOT</strong> 5V tolerant.<br />
<br />
If you momentarily shorted the two end GPIO pins together (+3.3V and +5V), or a supply pin to ground, and the Pi appears to be dead, don't panic. The input polyfuse may have tripped. It is self-resetting after it cools down. Disconnect power and wait for 30 minutes, then try to restart.<br />
<br />
==General==<br />
===The time is incorrect===<br />
If the clock is off by a series of hours, in the command line type:<br />
sudo dpkg-reconfigure tzdata<br />
<br />
==Troubleshooting power problems==<br />
If you think you have a problem with your power supply, it is a good idea to check the actual voltage<br />
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board<br />
to facilitate voltage measurements.<br />
<br />
Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable.<br />
<br />
If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]<br />
<br />
Note: Even if the multimeter shows the correct voltage, you may have some power supply problems. A multimeter only displays the average voltage. If there are very short-lived dips or spikes in the voltage, these will not be shown by the multimeter. <br />
<br />
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]<br />
<br />
==References==<br />
<references><br />
</references></div>Kwihttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=101444RPi VerifiedPeripherals2012-02-21T00:18:39Z<p>Kwi: /* SD cards */ Note that manufacturers change their designs over time; note on Class 10 SDHC issue apparently due to a bug in the Broadcom bootloader...</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category:ARM Development Boards]]<br />
[[Category: Broadcom]]<br />
[[Category: Development Boards]]<br />
[[Category: RaspberryPi]]<br />
[[Category: Education]]<br />
{{Template:RPi_Hardware}}<br />
<br />
<br />
==Notes==<br />
<br />
Please note that all information on this page is provisional. Details relate to the default Debian distribution on the Alpha boards unless otherwise noted.<br />
<br />
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''<br />
<br />
== USB Keyboards ==<br />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. The following is a list of specific keyboards known to work and which appear to be fault-free.<br />
<br />
* Logitech Wii wireless keyboard KG-0802<br />
* Fujitsu Siemens KB SC USB UK<br />
* Logitech diNovo Mini wireless keyboard with media controls and clickpad 920-000586<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work. The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* Microsoft Wheel Optical Mouse (wheel and additional buttons not tested)<br />
<br />
= USB WiFi Adapters =<br />
* Tenda USB 11n adapter on a G network<br />
** Ralink 2870/3070 driver<br />
* Netgear WG111v2<br />
** Realtek rtl8187 chipset<br />
* 3COM 3CRUSB10075<br />
** ZyDAS zd1211rw chipset<br />
<br />
== USB Bluetooth adapters ==<br />
<br />
== USB Ethernet adapters ==<br />
<br />
== USB UART adapters ==<br />
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC. The USB end connects to the PC and the UART header end connects to the USB. While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.<br />
<br />
== Power adapters ==<br />
* Alpha board: Stontronics S2097ST switching PSU, 7.5V 1.6A<br />
<br />
== SD cards ==<br />
<br />
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)<br />
For this reason, please specify product numbers in the lists below, when possible.<br />
<br />
===Working Cards===<br />
* Adata Class 10 8GB (AUSDH8GCL10-R)<br />
* Dane-Elec 16Gb class 4<br />
* Kingston SDHC 8GB class 4<br />
* Kingstone SD 2GB (no class mentioned)<br />
* Kingston SDHC 8GB class 4<br />
* SanDisk Ultra 2GB Class 4 (15MB/s)<br />
* Sandisk Ultra II SD 2GB class 4<br />
* Sandisk 2GB (non sdhc but with a circle 2), writes at 3.5 Mb/s<br />
* Transcend SDHC 8GB class 6<br />
<br />
Known good (and pre-loaded) cards will be available for sale from the RPi foundation at a ''later'' date (TBA).<br />
<br />
===Problem Cards===<br />
<br />
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]<br />
<br />
* Patriot Class 10 8GB (PSF8GSDHC10)<br />
<br />
The usual warnings against less reputable sellers (such as Ebay merchants) apply.<br />
<br />
=== Benchmarks ===<br />
<br />
http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html<br />
<br />
== Foreign Language Translations ==<br />
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]<br />
<br />
<br />
{{Template:Raspberry Pi}}</div>Kwi