eLinux.org - User contributions [en]

User talk:Bredman

2012-11-22T09:15:21Z

Bredman:

Edit this page to send a message to bredman.

Hi there,

I have a suggestion for your "R-Pi NAS" article. Instead of creating init script, automatic mounting of USB hard drive can be done by editing /etc/fstab and adding following line:
/dev/sda1 /home/pi/yourMountedFolder auto uid=pi,gid=pi,noatime 0 0

Best regards,
Predrag

==Response==
Please feel free to edit the RPi_NAS page.

I did not add this init script, it must have been somebody else.

RPI-Wireless-Hotspot

2012-11-10T15:20:18Z

Bredman: /* What skill level is required? */

=What does it do?=

This project configures your Raspberry Pi to connect to the Internet through ethernet, and share that connection over WiFi.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A USB WiFi device that supports "Access Point" mode.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

To edit a configuration file (for example /etc/udhcpd.conf) use the following command
sudo nano /etc/udhcpd.conf
You will find yourself in a simple editor. Move around using the arrow keys. To save the file press Ctrl-o. To exit press Ctrl-x.

=How does it work?=
The Raspberry Pi is configured as a WiFi Hotspot, just like you would see
in an internet cafe. It allows you to connect to the internet over WiFi using the
Raspberry Pi as the bridge to the internet.
The basic steps are
*Enable a WiFi Access Point and broadcast on the channel of your choice
*Assign dynamic IP addresses to any device that connects to WiFi network
*Join the WiFi and Ethernet networks together by using Network Address Translation

=Instructions=
The following steps were performed on Raspbian but should be much the same on any Debian-based distro.

1. Install the necessary software.

sudo apt-get install hostapd udhcpd

2. Configure DHCP. Edit the file /etc/udhcpd.conf and configure it like this:

start 192.168.2.2 # This is the range of IPs that the hostspot will give to client devices.
end 192.168.2.20
interface wlan0 # The device uDHCP listens on.
remaining yes
opt dns 8.8.8.8 4.2.2.2 # The DNS servers client devices will use.
opt subnet 255.255.255.0
opt router 192.168.2.1 # The Pi's IP address on wlan0 which we will set up shortly.
opt lease 864000 # 10 day DHCP lease time in seconds

Edit the file /etc/default/udhcpd and change the line:
DHCPD_ENABLED="no"
to
#DHCPD_ENABLED="no"

You will need to give the Pi a static IP address with the following command:

sudo ifconfig wlan0 192.168.2.1

To set this up automatically on boot, edit the file /etc/network/interfaces and replace the line "iface wlan0 inet dhcp" to:

iface wlan0 inet static
address 192.168.2.1
netmask 255.255.255.0

If the line "iface wlan0 inet dhcp" is not present, add the above lines to the bottom of the file.

Change the lines:
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
to:
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp

3. Configure HostAPD. Edit the file /etc/hostapd/hostapd.conf (create it if it doesn't exist) and add the following lines:

interface=wlan0
ssid=Your Network Name Here
hw_mode=g
channel=6 # Change this channel to one of your choosing, between 1 and 12. If you have connection issues, try changing the channel.
auth_algs=1 # This will create an open, unencrypted WiFi network. Use at your own risk.
wmm_enabled=0 # Some wireless adapters/drivers have issues with 802.11n, this disables it (basically).

Change ssid= and channel= to values of your choice. SSID is the hotspot's name which is broadcast to other devices, channel is what frequency the hotspot will run on. For many, many more options see the file /usr/share/doc/hostapd/examples/hostapd.conf.gz

Edit the file /etc/default/hostapd and change the line:
#DAEMON_CONF=""
to:
DAEMON_CONF="/etc/hostapd/hostapd.conf"

4. Configure NAT. NAT (Network Address Translation) is a technique that allows several devices to use a single connection to the internet. Linux supports NAT using Netfilter (also known as iptables), and if fairly easy to set up. First, edit the file /etc/sysctl.conf and add the following line to the bottom of the file:

net.ipv4.ip_forward=1

This will enable NAT in the kernel. Second, run the following commands:

sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT

Your Pi is now NAT-ing. To make this permanent so you don't have to run the commands after each reboot, run the following command:

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"

Now edit the file /etc/network/interfaces and add the following line to the bottom of the file:

up iptables-restore < /etc/iptables.ipv4.nat

5. Fire it up! Run the following commands to start the access point:

sudo service hostapd start
sudo service udhcpd start

Your Pi should now be hosting a wireless hotspot. To get the hotspot to start on boot, run these additional commands:

sudo update-rc.d hostapd enable
sudo update-rc.d udhcpd enable

At the completion of these instructions, your Pi should be providing a wireless network and allowing other devices to connect to the Internet. From my experience, the Pi makes a decent access point, although with cheaper WiFi dongles range will be fairly limited. I haven't stress tested this setup, but it seems to work fairly well and is handy when a "real" access point isn't available. I wrote most of the instructions from memory, if you find any errors/typos I'll correct them.

This tutorial originally was a post on the Raspberry Pi forum [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=36&t=19120 here], you can reply to that topic if you have issues.

RPI-Wireless-Hotspot

2012-11-10T15:19:48Z

Bredman: /* What skill level is required? */

=What does it do?=

This project configures your Raspberry Pi to connect to the Internet through ethernet, and share that connection over WiFi.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A USB WiFi device that supports "Access Point" mode.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

To edit a configuration file (for example /etc/udhcpd.conf) use the following instructions
sudo nano /etc/udhcpd.conf
You will find yourself in a simple editor. Move around using the arrow keys. To save the file press Ctrl-o. To exit press Ctrl-x.

=How does it work?=
The Raspberry Pi is configured as a WiFi Hotspot, just like you would see
in an internet cafe. It allows you to connect to the internet over WiFi using the
Raspberry Pi as the bridge to the internet.
The basic steps are
*Enable a WiFi Access Point and broadcast on the channel of your choice
*Assign dynamic IP addresses to any device that connects to WiFi network
*Join the WiFi and Ethernet networks together by using Network Address Translation

=Instructions=
The following steps were performed on Raspbian but should be much the same on any Debian-based distro.

1. Install the necessary software.

sudo apt-get install hostapd udhcpd

2. Configure DHCP. Edit the file /etc/udhcpd.conf and configure it like this:

start 192.168.2.2 # This is the range of IPs that the hostspot will give to client devices.
end 192.168.2.20
interface wlan0 # The device uDHCP listens on.
remaining yes
opt dns 8.8.8.8 4.2.2.2 # The DNS servers client devices will use.
opt subnet 255.255.255.0
opt router 192.168.2.1 # The Pi's IP address on wlan0 which we will set up shortly.
opt lease 864000 # 10 day DHCP lease time in seconds

Edit the file /etc/default/udhcpd and change the line:
DHCPD_ENABLED="no"
to
#DHCPD_ENABLED="no"

You will need to give the Pi a static IP address with the following command:

sudo ifconfig wlan0 192.168.2.1

To set this up automatically on boot, edit the file /etc/network/interfaces and replace the line "iface wlan0 inet dhcp" to:

iface wlan0 inet static
address 192.168.2.1
netmask 255.255.255.0

If the line "iface wlan0 inet dhcp" is not present, add the above lines to the bottom of the file.

Change the lines:
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
to:
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp

3. Configure HostAPD. Edit the file /etc/hostapd/hostapd.conf (create it if it doesn't exist) and add the following lines:

interface=wlan0
ssid=Your Network Name Here
hw_mode=g
channel=6 # Change this channel to one of your choosing, between 1 and 12. If you have connection issues, try changing the channel.
auth_algs=1 # This will create an open, unencrypted WiFi network. Use at your own risk.
wmm_enabled=0 # Some wireless adapters/drivers have issues with 802.11n, this disables it (basically).

Change ssid= and channel= to values of your choice. SSID is the hotspot's name which is broadcast to other devices, channel is what frequency the hotspot will run on. For many, many more options see the file /usr/share/doc/hostapd/examples/hostapd.conf.gz

Edit the file /etc/default/hostapd and change the line:
#DAEMON_CONF=""
to:
DAEMON_CONF="/etc/hostapd/hostapd.conf"

4. Configure NAT. NAT (Network Address Translation) is a technique that allows several devices to use a single connection to the internet. Linux supports NAT using Netfilter (also known as iptables), and if fairly easy to set up. First, edit the file /etc/sysctl.conf and add the following line to the bottom of the file:

net.ipv4.ip_forward=1

This will enable NAT in the kernel. Second, run the following commands:

sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT

Your Pi is now NAT-ing. To make this permanent so you don't have to run the commands after each reboot, run the following command:

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"

Now edit the file /etc/network/interfaces and add the following line to the bottom of the file:

up iptables-restore < /etc/iptables.ipv4.nat

5. Fire it up! Run the following commands to start the access point:

sudo service hostapd start
sudo service udhcpd start

Your Pi should now be hosting a wireless hotspot. To get the hotspot to start on boot, run these additional commands:

sudo update-rc.d hostapd enable
sudo update-rc.d udhcpd enable

At the completion of these instructions, your Pi should be providing a wireless network and allowing other devices to connect to the Internet. From my experience, the Pi makes a decent access point, although with cheaper WiFi dongles range will be fairly limited. I haven't stress tested this setup, but it seems to work fairly well and is handy when a "real" access point isn't available. I wrote most of the instructions from memory, if you find any errors/typos I'll correct them.

This tutorial originally was a post on the Raspberry Pi forum [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=36&t=19120 here], you can reply to that topic if you have issues.

RPI-Wireless-Hotspot

2012-11-10T15:17:11Z

Bredman: How does it work

=What does it do?=

This project configures your Raspberry Pi to connect to the Internet through ethernet, and share that connection over WiFi.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A USB WiFi device that supports "Access Point" mode.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

=How does it work?=
The Raspberry Pi is configured as a WiFi Hotspot, just like you would see
in an internet cafe. It allows you to connect to the internet over WiFi using the
Raspberry Pi as the bridge to the internet.
The basic steps are
*Enable a WiFi Access Point and broadcast on the channel of your choice
*Assign dynamic IP addresses to any device that connects to WiFi network
*Join the WiFi and Ethernet networks together by using Network Address Translation

=Instructions=
The following steps were performed on Raspbian but should be much the same on any Debian-based distro.

1. Install the necessary software.

sudo apt-get install hostapd udhcpd

2. Configure DHCP. Edit the file /etc/udhcpd.conf and configure it like this:

start 192.168.2.2 # This is the range of IPs that the hostspot will give to client devices.
end 192.168.2.20
interface wlan0 # The device uDHCP listens on.
remaining yes
opt dns 8.8.8.8 4.2.2.2 # The DNS servers client devices will use.
opt subnet 255.255.255.0
opt router 192.168.2.1 # The Pi's IP address on wlan0 which we will set up shortly.
opt lease 864000 # 10 day DHCP lease time in seconds

Edit the file /etc/default/udhcpd and change the line:
DHCPD_ENABLED="no"
to
#DHCPD_ENABLED="no"

You will need to give the Pi a static IP address with the following command:

sudo ifconfig wlan0 192.168.2.1

To set this up automatically on boot, edit the file /etc/network/interfaces and replace the line "iface wlan0 inet dhcp" to:

iface wlan0 inet static
address 192.168.2.1
netmask 255.255.255.0

If the line "iface wlan0 inet dhcp" is not present, add the above lines to the bottom of the file.

Change the lines:
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
to:
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp

3. Configure HostAPD. Edit the file /etc/hostapd/hostapd.conf (create it if it doesn't exist) and add the following lines:

interface=wlan0
ssid=Your Network Name Here
hw_mode=g
channel=6 # Change this channel to one of your choosing, between 1 and 12. If you have connection issues, try changing the channel.
auth_algs=1 # This will create an open, unencrypted WiFi network. Use at your own risk.
wmm_enabled=0 # Some wireless adapters/drivers have issues with 802.11n, this disables it (basically).

Change ssid= and channel= to values of your choice. SSID is the hotspot's name which is broadcast to other devices, channel is what frequency the hotspot will run on. For many, many more options see the file /usr/share/doc/hostapd/examples/hostapd.conf.gz

Edit the file /etc/default/hostapd and change the line:
#DAEMON_CONF=""
to:
DAEMON_CONF="/etc/hostapd/hostapd.conf"

4. Configure NAT. NAT (Network Address Translation) is a technique that allows several devices to use a single connection to the internet. Linux supports NAT using Netfilter (also known as iptables), and if fairly easy to set up. First, edit the file /etc/sysctl.conf and add the following line to the bottom of the file:

net.ipv4.ip_forward=1

This will enable NAT in the kernel. Second, run the following commands:

sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT

Your Pi is now NAT-ing. To make this permanent so you don't have to run the commands after each reboot, run the following command:

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"

Now edit the file /etc/network/interfaces and add the following line to the bottom of the file:

up iptables-restore < /etc/iptables.ipv4.nat

5. Fire it up! Run the following commands to start the access point:

sudo service hostapd start
sudo service udhcpd start

Your Pi should now be hosting a wireless hotspot. To get the hotspot to start on boot, run these additional commands:

sudo update-rc.d hostapd enable
sudo update-rc.d udhcpd enable

At the completion of these instructions, your Pi should be providing a wireless network and allowing other devices to connect to the Internet. From my experience, the Pi makes a decent access point, although with cheaper WiFi dongles range will be fairly limited. I haven't stress tested this setup, but it seems to work fairly well and is handy when a "real" access point isn't available. I wrote most of the instructions from memory, if you find any errors/typos I'll correct them.

This tutorial originally was a post on the Raspberry Pi forum [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=36&t=19120 here], you can reply to that topic if you have issues.

RPI-Wireless-Hotspot

2012-11-10T15:07:08Z

Bredman: Improved introduction

=What does it do?=

This project configures your Raspberry Pi to connect to the Internet through ethernet, and share that connection over WiFi.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A USB WiFi device that supports "Access Point" mode.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

=Instructions=
The following steps were performed on Raspbian but should be much the same on any Debian-based distro.

1. Install the necessary software.

sudo apt-get install hostapd udhcpd

2. Configure DHCP. Edit the file /etc/udhcpd.conf and configure it like this:

start 192.168.2.2 # This is the range of IPs that the hostspot will give to client devices.
end 192.168.2.20
interface wlan0 # The device uDHCP listens on.
remaining yes
opt dns 8.8.8.8 4.2.2.2 # The DNS servers client devices will use.
opt subnet 255.255.255.0
opt router 192.168.2.1 # The Pi's IP address on wlan0 which we will set up shortly.
opt lease 864000 # 10 day DHCP lease time in seconds

Edit the file /etc/default/udhcpd and change the line:
DHCPD_ENABLED="no"
to
#DHCPD_ENABLED="no"

You will need to give the Pi a static IP address with the following command:

sudo ifconfig wlan0 192.168.2.1

To set this up automatically on boot, edit the file /etc/network/interfaces and replace the line "iface wlan0 inet dhcp" to:

iface wlan0 inet static
address 192.168.2.1
netmask 255.255.255.0

If the line "iface wlan0 inet dhcp" is not present, add the above lines to the bottom of the file.

Change the lines:
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
to:
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp

3. Configure HostAPD. Edit the file /etc/hostapd/hostapd.conf (create it if it doesn't exist) and add the following lines:

interface=wlan0
ssid=Your Network Name Here
hw_mode=g
channel=6 # Change this channel to one of your choosing, between 1 and 12. If you have connection issues, try changing the channel.
auth_algs=1 # This will create an open, unencrypted WiFi network. Use at your own risk.
wmm_enabled=0 # Some wireless adapters/drivers have issues with 802.11n, this disables it (basically).

Change ssid= and channel= to values of your choice. SSID is the hotspot's name which is broadcast to other devices, channel is what frequency the hotspot will run on. For many, many more options see the file /usr/share/doc/hostapd/examples/hostapd.conf.gz

Edit the file /etc/default/hostapd and change the line:
#DAEMON_CONF=""
to:
DAEMON_CONF="/etc/hostapd/hostapd.conf"

4. Configure NAT. NAT (Network Address Translation) is a technique that allows several devices to use a single connection to the internet. Linux supports NAT using Netfilter (also known as iptables), and if fairly easy to set up. First, edit the file /etc/sysctl.conf and add the following line to the bottom of the file:

net.ipv4.ip_forward=1

This will enable NAT in the kernel. Second, run the following commands:

sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT

Your Pi is now NAT-ing. To make this permanent so you don't have to run the commands after each reboot, run the following command:

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"

Now edit the file /etc/network/interfaces and add the following line to the bottom of the file:

up iptables-restore < /etc/iptables.ipv4.nat

5. Fire it up! Run the following commands to start the access point:

sudo service hostapd start
sudo service udhcpd start

Your Pi should now be hosting a wireless hotspot. To get the hotspot to start on boot, run these additional commands:

sudo update-rc.d hostapd enable
sudo update-rc.d udhcpd enable

At the completion of these instructions, your Pi should be providing a wireless network and allowing other devices to connect to the Internet. From my experience, the Pi makes a decent access point, although with cheaper WiFi dongles range will be fairly limited. I haven't stress tested this setup, but it seems to work fairly well and is handy when a "real" access point isn't available. I wrote most of the instructions from memory, if you find any errors/typos I'll correct them.

This tutorial originally was a post on the Raspberry Pi forum [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=36&t=19120 here], you can reply to that topic if you have issues.

RPi Easy SD Card Setup

2012-10-31T09:31:07Z

Bredman: Updated to 2012-10-28-wheezy-raspbian

[[Category: RaspberryPi]]
{{Template:RPi_Startup}}

=SD Card setup=
To boot the Raspberry Pi, you need an SD card installed with a bootloader and a suitable Operating System. Some Raspberry Pi kits will come with a ready-to-go card, but if you didn't receive one you will need to prepare your own:

Official images are available from http://www.raspberrypi.org/downloads and there is an overview of available distributions [[RPi_Distributions | here]].

Warning! When you write the Raspberry Pi image to your SD card you will lose all data that was on the card.

=Safest/Laziest way=
Buy a preloaded card from RS Components, element14 or [http://thepihut.com/ The Pi Hut's Raspberry Pi Store]

=Easiest way=

* Use an installer program. The [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix_Installation#SD_Card_Installation_Using_the_Installer Fedora ARM Installer] will download and install Raspberry Pi Fedora Remix images, but it will also install other images if they are already downloaded and in uncompressed or .gz format.

* ('''Mac''') The [https://github.com/exaviorn/RasPiWrite RasPiWrite] utility is a python script which will walk you through the process of installing to SD card, it works with any Raspberry Pi compatible disk image, and can download one of the currently available distros if you don't have one.

* If your Pi is connected to the Internet, you can use the [http://www.berryterminal.com/doku.php/berryboot BerryBoot installer] to let it download and install the operating system. This requires that you first use a normal Windows/Mac/Linux computer to download a small .zip file with the Berryboot system files and extract it to an empty SD card. Then you put the SD card in your Pi, and follow the on-screen prompts to complete the installation. An additional advantage is that Berryboot allows you to install more than one operating system on a single SD card.

=Easy way=

To write your SD card you start by downloading the SD image (the data you will write to the card). The best way to do this is using [http://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent]. This generally results in a faster download as it is a highly distributed system (you will be downloading the data from users who have previously downloaded it).

This guide assumes you have downloaded the Debian "wheezy" image, with name 2012-10-28-wheezy-raspbian. Obviously, if you are downloading a different or newer version, use the name of the version you have downloaded.

==Copying the image to an SD Card on Windows==

# Download the image from a mirror or torrent. The remainder of this assumes you are using the Raspbian “wheezy” download 2012-10-28-wheezy-raspbian.zip
#* http://www.raspberrypi.org/downloads
# Extract the image file 2012-10-28-wheezy-raspbian.img from the downloaded .zip file.
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example G:) by looking in the left column of Windows Explorer. If the card is not new, you should format it; otherwise Win32DiskImager may hang.
# Download the [https://launchpad.net/win32-image-writer Win32DiskImager] utility. The download links are on the right hand side of the page, you want the binary zip.
# Extract the executable from the zip file and run the Win32DiskImager utility. '''You should run the utility as Administrator!'''
# Select the 2012-10-28-wheezy-raspbian.img image file you extracted earlier
# Select the drive letter of the SD card in the device box. '''Be careful to select the correct drive; if you get the wrong one you can destroy your computer's hard disk!'''
# Click Write and wait for the write to complete.
# Exit the imager and eject the SD card.
# Insert the card in the Raspberry Pi, power it on, and it should boot up. There is an option in the configure script that comes up to expand the partitions to use all of the SD card if you have used one larger than 4 GB
''In Windows the SD card will appear only to have a fairly small size - about 75 Mbytes. This is because most of the card has a partition that is formatted for the Linux operating system that the RPi uses and is not visible in Windows.
''

==Copying the image to an SD Card on Windows if first option isn't successful==
I wasn't able to choose device in Win32DiskImager on my notebook so I found a different way to achieve the same thing on windows machine..

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file 2012-10-28-wheezy-raspbian.img from 2012-10-28-wheezy-raspbian.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example H:) by looking in the left column of Windows Explorer.
# Download flashnul software from http://shounen.ru/soft/flashnul/ here is [http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en Translated version]
#* Download the latest version at the time of writing it was flashnul-1rc1.
#* Download and Extract the application from archive.
#* Click Start button > All Programs > Accessories > Command Prompt, right click on it and Run as Administrator.
#* Run the flashnul with argument:
C:/flashnul/flashnul.exe -p
#* Flashnul will tell you something like:

Avaible physical drives:
0 size = 250059350016 (232 Gb)
1 size = 1990197248 (1898 Mb)

Avaible logical disks:
C:\
D:\
F:\
G:\
H:\

Press ENTER to exit.

'''SDCARD number is on left! In my case it is number 1'''

#* Now we will use Load argument:
C:/flashnul/flashnul.exe 1 -L C:/2012-10-28-wheezy-raspbian.img
where '''<Path to flashnul directory>'''flashnul.exe '''<device number>''' -L '''<img file path>'''

#* Flashnul will give you a device summary and proceed caution, have a quick scan through the information to make sure you have selected the correct device, then type yes and press enter.
#* If you get a access denied error, try re-plugging the SD card. Also make sure to close all explorer windows or folders open for the device.
#* If you still get a access denied error, try substitute the device number with the drive letter followed by a colon. Eg:
C:/flashnul/flashnul.exe H: -L C:/debian6/debian6-19-04-2012.img
* If the device summary does not match Your card (the size is smaller, e.g. 75MB), but you are sure, that the letter is correct - please continue and then try again with the device number.

==Copying an image to the SD Card in Mac OS X (mostly graphical interface)==
# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image by double clicking on the download file
# Connect the SD Card reader with the SD Card inside; note: must be formatted in FAT32!
# From the ''Apple () menu'', choose ''About This Mac'', then click on ''More info...''; if you are using Max OS X 10.8.x Mountain Lion then click on ''System report''.
# Click on ''USB'' then search for your SD Card in the upper right section of the window; click it, then search for ''BSD name'' in the lower right section: must be something like '''disk'''''n'' where ''n'' is a number (e.g.: disk4). Note this number
# Unmount the partition so that you will be allowed to overwrite the disk by opening Disk Utility and unmounting it (do not eject it, or you have to reconnect it)
# From the Terminal run:
#* '''sudo dd if=''path_of_your_image.img'' of=/dev/disk''n'' bs=1m'''
#* Remember to replace ''n'' with the number that you noted before!
# Wait a LONG time!
# You're done! Insert it in the raspberry pi, and have fun

==Copying an image to the SD Card in Mac OS X (command line)==

'''Note''': Some users have [http://www.raspberrypi.org/phpBB3/search.php?keywords=extra+files&t=8226&sf=msgonly reported issues] with using OSX to create SD Cards.
#These commands and actions need to be performed from an account that has administrator privileges.
# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key is the same (optional), in the terminal run:
#* '''shasum ~/Downloads/2012-10-28-wheezy-raspbian.zip'''
# Extract the image:
#* '''unzip ~/Downloads/2012-10-28-wheezy-raspbian.zip'''
#* ''(or: just double click the zip, it will extract automatically)''
# From the terminal run '''df -h'''
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again and look for the new device that wasn't listed last time. Record the device name of the filesystem's partition, e.g. '''/dev/disk3s1'''
# Unmount the partition so that you will be allowed to overwrite the disk:
#* '''sudo diskutil unmount /dev/disk3s1'''
#* ''(or: open Disk Utility and unmount the partition of the sdcard (do not eject it, or you have to reconnect it)
# Using the device name of the partition work out the raw device name for the entire disk, by omitting the final "s1" and replacing "disk" with "rdisk" ('''this is very important:''' you '''will''' lose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, rdisk3, not rdisk3s1. Similarly you might have another SD drive name/number like rdisk2 or rdisk4, etc. -- recheck by using the '''df -h''' command both before & after you insert your SD card reader into your Mac if you have any doubts!):
#* e.g. '''/dev/disk3s1''' => '''/dev/rdisk3'''
# In the terminal write the image to the card with this command, using the raw disk device name from above (read '''carefully''' the above step, to be sure you use the correct rdisk# here!):
#* '''sudo dd bs=1m if=~/Downloads/2012-10-28-wheezy-raspbian/2012-10-28-wheezy-raspbian.img of=/dev/rdisk3'''
#* if the above command report an error(dd: bs: illegal numeric value), please change bs=1M to bs=1m
#* (note that dd will not feedback any information until there is an error or it is finished, information will show and disk will re-mount when complete. However if you are curious as to the progresss - ctrl-T (SIGINFO, the status argument of your tty) will display some en-route statistics).
# After the dd command finishes, eject the card:
#* '''sudo diskutil eject /dev/rdisk3'''
#* ''(or: open Disk Utility and eject the sdcard)''
# Insert it in the raspberry pi, and have fun

==Copying an image to the SD Card in Linux (command line)==

Please note that the use of the "dd" tool can overwrite any partition of your machine. If you specify the wrong device in the instructions below you could delete your primary Linux partition. Please be careful.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key of the zip file is the same as shown on the downloads page (optional). Assuming that you put the zip file in your home directory (~/), in the terminal run:
#* '''sha1sum ~/2012-10-28-wheezy-raspbian.zip'''
#* This will print out a long hex number which should match the "SHA-1" line for the SD image you have downloaded
# Extract the image, with
#* '''unzip ~/2012-10-28-wheezy-raspbian.zip'''
# Run '''df -h''' to see what devices are currently mounted
# If your computer has a slot for SD cards, insert the card. If not, insert the card into an SD card reader, then connect the reader to your computer.
# Run '''df -h''' again. The device that wasn't there last time is your SD card. The left column gives the device name of your SD card. It will be listed as something like "/dev/mmcblk0p1" or "/dev/sdd1". The last part ("p1" or "1" respectively) is the partition number, but you want to write to the whole SD card, not just one partition, so you need to remove that part from the name (getting for example "/dev/mmcblk0" or "/dev/sdd") as the device for the whole SD card. Note that the SD card can show up more than once in the output of df: in fact it will if you have previously written a Raspberry Pi image to this SD card, because the RPi SD images have more than one partition.
# Now that you've noted what the device name is, you need to unmount it so that files can't be read or written to the SD card while you are copying over the SD image. So run the command below, replacing "/dev/sdd1" with whatever your SD card's device name is (including the partition number)
#* '''umount /dev/sdd1'''
#* If your SD card shows up more than once in the output of df due to having multiple partitions on the SD card, you should unmount all of these partitions.
# In the terminal write the image to the card with this command, making sure you replace the input file '''if=''' argument with the path to your .img file, and the "/dev/sdd" in the output file '''of=''' argument with the right device name ('''this is very important:''' you '''will''' lose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, sdd, not sdds1 or sddp1, or mmcblk0 not mmcblk0p1)
#* '''dd bs=4M if=~/2012-10-28-wheezy-raspbian.img of=/dev/sdd'''
#** Please note that block size set to 4M will work most of the time, if not, please try 1M, although 1M will take considerably longer.
#* Note that if you are not logged in as root you will need to prefix this with '''sudo '''
#* The dd command does not give any information of its progress and so may appear to have frozen. It could take more than five minutes to finish writing to the card. If your card reader has an LED it may blink during the write process, or you can run '''pkill -USR1 -n -x dd''' in another terminal (prefixed with '''sudo''' if you are not logged in as root).
# Instead of dd you can use dcfldd; it will give a progress report about how much has been written.
# You can check what's written to the SD card by dd-ing from the card back to your harddisk to another image, and then running diff (or md5sum) on those two images. There should be no difference.
# As root run the command '''sync''' or if a normal user run '''sudo sync''' (this will ensure the write cache is flushed and that it is safe to unmount your SD card)
# Remove SD card from card reader, insert it in the Raspberry Pi, and have fun

==Copying an image to the SD Card in Linux (graphical interface)==
If you are using Ubuntu and hesitate to use the terminal, you can use the ImageWriter tool (nice graphical user interface) to write the .img file to the SD card.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Right click the zip file and select "Extract here"
#* '''ATTENTION''': As of this writing (15 June 2012), there is a bug in the ImageWriter program that causes it to fail if the filename of the image file or its path (i.e. all the names of any parent folders that you extract the image file into) contain any space characters. Before going any further, ensure that neither the file name of the image you're using or the path contain any spaces (or other odd characters, for that matter). A bug has been opened for this issue: https://bugs.launchpad.net/usb-imagewriter/+bug/1013834 Once the issue is fixed, edit this page to advise people to use an updated/patched version of ImageWriter.
# Insert the SD card into your computer or connect the SD card reader with the SD card inside
# Install the ImageWriter tool from the Ubuntu Software Center
# Launch the ImageWriter tool (it needs your administrative password)
# Select the image file (example 2012-10-28-wheezy-raspbian.img) to be written to the SD card (note: because you started ImageWriter as administrator the starting point when selecting the image file is the administrator's home folder so you need to change to your own home folder to select the image file)
# Select the target device to write the image to (your device will be something like "/dev/mmcblk0" or "/dev/sdc")
# Click the "Write to device" button
# Wait for the process to finish and then insert the SD card in the Raspberry Pi

=Manually resizing the SD card partitions (Optional)=
The SD card image is sized for a 2GB card. The Fedora Remix will automatically resize the partitions on the card during the first boot. The Debian version won't, so you'll have to do it manually. It's much easier if you do this on another machine, as the SD card can't be mounted when you do this.

Look [[RPi_Resize_Flash_Partitions|here]] for instructions.

=Adding a data partition (Optional)=
If you would rather not resize the partition on another machine as described above, either because you do not have another working Linux machine or you wish to keep your data on another partition to your operating system, you can instead create a new data partition and have that mount automatically at boot.

*First you need to become root and install parted (I did all of this from the boot command prompt, although if you feel safer in a GUI, you can do all of this in a terminal window):
sudo su -
apt-get install parted
*Then you need to run parted on your SD card, mine is /dev/mmcblk0, ymmv:
parted /dev/mmcblk0
*Once running, set the display units to something usable and then print your partition table
unit chs
print
*You should see something like this:
Model: SD SD08G (sd/mmc)
Disk /dev/mmcblk0: 121279,3,31
Sector size (logical/physical): 512B/512B
BIOS cylinder,head,sector geometry: 121280,4,32. Each cylinder is 65.5kB.
Partition Table: msdos
Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
*Now you need to create your data partition - you need to choose one more than the end of partition 3 with ,0,0 as your start and use the number from the line that starts with Disk as your end:
mkpart primary 29744,0,0 121279,3,31
print
*That should show your new partition:
Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
4 29744,0,0 121279,3,31 primary
*Now quit and format the partition (again, ymmv with the specific device name, try ls /dev for some clues), and then label it:
quit
mkfs.ext4 /dev/mmcblk0p4
e2label /dev/mmcblk0p4 data
*Now we need to make sure that the partition is mounted automatically when the system boots (maybe don't use vi if you never have before, try nano):
vi /etc/fstab
*Enter a line exactly like this at the end of the file and save and quit your text editor:
/dev/mmcblk0p4 /data ext4 defaults 1 2
*Create the mount point:
mkdir /data
*Now mount the partition:
mount /data
cd /data
ls
Your new partition has been created!

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

R-Pi ConfigurationFile

2012-10-24T08:38:53Z

Bredman: /* How to edit from a Windows PC */

[[Category:RaspberryPi]]

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad. Note: Do not use the Wordpad editor or Microsoft Word to edit the file.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from OSX=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.
*Put the SD card in your Mac's card reader and wait for the card to appear on the Desktop.
*Open the card in Finder.
*Look to see if there is a file called config (or possibly config.txt).
*If this file exists, open it with TextEdit. If not, create a new file in Textedit as Plain Text format.
*Add the necessary configuration parameters.
*Save the file as "config" and quit TextEdit.
*In Finder eject the SD card by dragging it to the Trash or clicking the eject button in the Finder window.
*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=
This method is most useful if you can see the display of the Raspberry Pi and you wish to make minor adjustments.

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

'''NOTE:''' You may find that your changes to config.txt disappear after a reboot. This is a very rare problem and seems to depend on the type of SD card. In this case, use a Windows/Linux/OSX PC to edit the file, see instructions above.

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

=What configuration options are available?=
For a list of all the configuration options available, click [http://elinux.org/RPi_config.txt here]

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

R-Pi Troubleshooting

2012-10-12T12:53:14Z

Bredman: /* Composite displays only back and white or no image */

[[Category:RaspberryPi]]

Back to the [[R-Pi Hub|Hub]].

This page lists the most common problems and suggests some solutions.

See [[RPi_Bugs]] for problems that are bugs.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].

Note that the PI has no BIOS, so nothing will be displayed on screen unless the PI successfully boots!

===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.
*Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured from the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

If start.elf won't launch it may be corrupt and can be replaced with arm240_start.elf or any of the other armXXX_start.elf files.

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

Immediately after displaying the splash screen, the PI starts consuming a little more current, if the PI resets at that moment its an indication that your PSU isn't able to deliver the full current your PI requires, but dips its output voltage below a minimum when loaded with the full current the PI needs.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down (or restarts) soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.
*It could be that the SD memory card is not making proper contact with the Raspberry Pi. Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured fron the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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 WiFi 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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm240_start.elf : 240M ARM, 16M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm240_start.elf /boot/start.elf && sudo reboot

Note: the arm224_start.elf is usually the wrong choice. arm240_start.elf is almost always a better choice.

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==Networking==

===Ethernet connection is lost when a USB device is plugged in===
This is often 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. (More often than not, however, the reverse is true with cheap hubs—the Pi draws just enough power backwards from the powered hub to unsuccessfully attempt booting.)

There is an ongoing issue with the Ethernet connection being lost when low-speed devices, such as mice or keyboards are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi (assuming they draw less than 100 mA apiece).

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

===Crashes occur with high network load===

The USB driver allocates memory from the kernel, and when traffic is very high (e.g. when using torrents/newsgroup downloads) this memory can be exhausted causing crashes/hangs. You should have a line like:

vm.min_free_kbytes = 8192

in /etc/sysctl.conf. Try increasing that number to 16384 (or higher). If that doesn't work, try adding to /boot/cmdline.txt

smsc95xx.turbo_mode=N

which will reduce network throughput, but has improved stability issues for some.

===Network connection fails when a Graphical User Interface is being used===

The network connection may fail when the command startx is used to enter a Graphical User Interface. This is caused by a bug in the USB driver related to certain types of USB mouse.

As of 1 September 2012, this fault is fixed in the latest firmware. To load the latest firmware, see
[http://elinux.org/R-Pi_Troubleshooting#Updating_firmware http://elinux.org/R-Pi_Troubleshooting#Updating_firmware]

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root
*Bodhi: pi/bodhilinux

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

This is a fault in old Debian images previous to September 2012. If you are using an image with this fault, upgrade to a more modern image or enter the following command on the command line.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Screen is the wrong color===
Check and see if the DVI cable is screwed in properly. If that doesn't work then try [[#Interference_visible_on_a_HDMI_or_DVI_monitor|this]] section.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

Note that various adapters, such as HDMI-to-DVI, can also cause power loss and therefore require high values of config_hdmi_boost even with short cables.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

Also, check that your TV is set to the correct input, normally marked "AV". If your TV has multiple AV inputs, try all of the inputs, normally by pressing a button marked "AV" or "Input" or "Source" or "->O" on the remote control.

===Composite displays only black and white image===
The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

=References=
<references/>

{{Template:Raspberry Pi}}

[[Category:RaspberryPi]]

R-Pi Troubleshooting

2012-10-12T12:48:34Z

Bredman: /* Some programs refuse to accept my password */

[[Category:RaspberryPi]]

Back to the [[R-Pi Hub|Hub]].

This page lists the most common problems and suggests some solutions.

See [[RPi_Bugs]] for problems that are bugs.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].

Note that the PI has no BIOS, so nothing will be displayed on screen unless the PI successfully boots!

===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.
*Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured from the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

If start.elf won't launch it may be corrupt and can be replaced with arm240_start.elf or any of the other armXXX_start.elf files.

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

Immediately after displaying the splash screen, the PI starts consuming a little more current, if the PI resets at that moment its an indication that your PSU isn't able to deliver the full current your PI requires, but dips its output voltage below a minimum when loaded with the full current the PI needs.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down (or restarts) soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.
*It could be that the SD memory card is not making proper contact with the Raspberry Pi. Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured fron the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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 WiFi 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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm240_start.elf : 240M ARM, 16M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm240_start.elf /boot/start.elf && sudo reboot

Note: the arm224_start.elf is usually the wrong choice. arm240_start.elf is almost always a better choice.

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==Networking==

===Ethernet connection is lost when a USB device is plugged in===
This is often 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. (More often than not, however, the reverse is true with cheap hubs—the Pi draws just enough power backwards from the powered hub to unsuccessfully attempt booting.)

There is an ongoing issue with the Ethernet connection being lost when low-speed devices, such as mice or keyboards are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi (assuming they draw less than 100 mA apiece).

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

===Crashes occur with high network load===

The USB driver allocates memory from the kernel, and when traffic is very high (e.g. when using torrents/newsgroup downloads) this memory can be exhausted causing crashes/hangs. You should have a line like:

vm.min_free_kbytes = 8192

in /etc/sysctl.conf. Try increasing that number to 16384 (or higher). If that doesn't work, try adding to /boot/cmdline.txt

smsc95xx.turbo_mode=N

which will reduce network throughput, but has improved stability issues for some.

===Network connection fails when a Graphical User Interface is being used===

The network connection may fail when the command startx is used to enter a Graphical User Interface. This is caused by a bug in the USB driver related to certain types of USB mouse.

As of 1 September 2012, this fault is fixed in the latest firmware. To load the latest firmware, see
[http://elinux.org/R-Pi_Troubleshooting#Updating_firmware http://elinux.org/R-Pi_Troubleshooting#Updating_firmware]

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root
*Bodhi: pi/bodhilinux

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

This is a fault in old Debian images previous to September 2012. If you are using an image with this fault, upgrade to a more modern image or enter the following command on the command line.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Screen is the wrong color===
Check and see if the DVI cable is screwed in properly. If that doesn't work then try [[#Interference_visible_on_a_HDMI_or_DVI_monitor|this]] section.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

Note that various adapters, such as HDMI-to-DVI, can also cause power loss and therefore require high values of config_hdmi_boost even with short cables.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

=References=
<references/>

{{Template:Raspberry Pi}}

[[Category:RaspberryPi]]

RPi Beginners

2012-09-02T19:12:09Z

Bredman: /* Create a new user with sudo-privileges */

[[Category:RaspberryPi]]
{{Template:RPi_Startup}}

There is some restructuring going on , we are sorry for the inconvenience. '''

=Where to start?=
Any easy question to ask, but a very difficult one to answer!
# '''If you are looking for any information related to SD Cards and setup look [[RPi Easy SD Card Setup | here]]
# If you need to get a RPi, the see the [[RPi Buying Guide|Buying Guide]].
# 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.
# If you need to install/setup an SD card see the [[RPi Easy SD Card Setup|Preload your Card]] section.
# If something is not working, check the [[R-Pi_Troubleshooting|Troubleshooting]] section.
# If you need help with Debian, try the [http://wiki.debian.org/FrontPage Debian Wiki].
# If you have imaged a SD with the Debian Wheezy image and started your RPi here's some help with what you see first - the raspi-config menu [[RPi_raspi-config]]
# Help for Noob's with a quizical disposition and Wheezy or Raspbian instalations [[RPi_Noob_Guides_for_Wheezy_using_2012-16-18_beta|here]]
# If you don't have a composite monitor or HDMI then it may be worth you looking at [[RPi_A_Method_for_ssh_blind_login|Blind Login Method]]
# Build yourself a Wheezy [[RPi_A_Simple_Wheezy_LAMP_install|LAMP]] webserver.
# VNC connection for the monitorily challenged Noob [[RPi_Wheezy_VNC|VNC for a wheezy install]] (noobs that are using the Blind Login)
# If you've done all that, and you are wondering what next...'''welcome and read on!'''

References needed (idea for new section Living Without RPi, which can guide users or link to info to users who haven't got RPis)
Link to emulation builds or live linux cds setup for beginners (RacyPy2 for example)
If you don't have a Raspberry Pi yet, you can still try things out, see [http://sourceforge.net/projects/rpiqemuwindows/ Windows RPi Emulator] for details.

=What is Linux and why not use Windows?=
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.

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.

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!

For more information about Linux see
[http://en.wikipedia.org/wiki/Linux Wikipedia]

Also see [[RPi_End-user_FAQ End-User|FAQ]]
And [[Will_RPi_Run|Running XXX on the RPi]]

=Basic Debian RPi Setup=
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.

== Default login and password ==
See the ''Username:Password'' column of [[RPi_Distributions#Available Distributions|distributions table]] to access your Pi.

== Locale settings ==

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").

You can alter this with

sudo dpkg-reconfigure locales

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.

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.

''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.

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.

When you're done picking locale(s), press Enter. You will be prompted to select a default locale as well.

== Keyboard layout ==

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:

sudo dpkg-reconfigure keyboard-configuration

Follow the prompts.

'''Or:''' From the command line type:
sudo nano /etc/default/keyboard

Then find where it says

XKBLAYOUT="gb"

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]

Also, see the [[R-Pi_Troubleshooting#Re-mapping_the_keyboard_with_Debian_Squeeze|Troubleshooting Guide]] for more information about remapping the keyboard.

You may need to restart for the changes to take effect.

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:

sudo setupcon

If the selected keyboard layout is not applied in the console (that is, when not running under X), try:

sudo apt-get install console-data

== Timezone ==

Unless you live in Great Britain, you'll have to change the default timezone:

sudo dpkg-reconfigure tzdata

Select geographic area - Europe, America or whatever. Etc gives UNIX compatible time zones including CUT, GMT, UTC

Select city

Follow the prompts to finish the config. The change should be immediate.

== Create a new user with sudo-privileges ==

You may want to create a new user account for yourself.

Type in following command in the terminal to create a new user (for example the user john):

sudo adduser john

Follow the steps.

To allow the newly created user to use the "sudo" command, type:
sudo visudo

Add following line under the "root ALL=(ALL) ALL" Line:

john ALL=(ALL) ALL

Now press CTRL+O, X to save and exit the editor.

Alternatively instead of adding the user to the sudoers list, you can add your user to the sudo group with the following command:

adduser john sudo

== Debian Wheezy, using raspi-config ==
Debian Wheezy has a menu that will do some of the above and more [[RPi_raspi-config]]

=Intro to the CLI (Command Line Interface)=
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.

For an introductory guide to some basic commands please see: [http://elinux.org/CLI_Spells Command Line Interface "Must Have" Commands]. Featured on the Raspberry Pi [http://www.raspberrypi.org/archives/1414 home page] was also a link to this site for [http://linuxcommand.org/learning_the_shell.php "learning the shell"]

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:

startx

=Remote Access=
Your default install probably has a ssh (secure shell) "daemon" running.
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.

Prior to your initial remote access it is recommended that you regenerate unique host public/private ID keys with the following command
rm /etc/ssh/ssh_host_* && dpkg-reconfigure openssh-server

More details about remote access (including remote GUI are at [[RPi Remote Access]]

=Adding more software to your Raspberry Pi=
You will probably want to add software to your Raspberry Pi. Here you can find out how to do it.
[http://elinux.org/Add_software Adding Software]

=Adding USB Storage to Your Raspberry Pi=
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/RPi_Adding_USB_Drives Adding USB Drives to a Raspberry Pi]

=Beginner Projects=
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.

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.
Reference needed - a good guide on how to backup and restore cards or software to do this easily

==Backup your SD card==

For Windows users the 'Raw HDD Copy Tool' from HDD Guru works well to backup and restore your SD card between proejcts.
This can backup and restore the entire card sector by sector to/from an img file, and doesn't care which file system is on the card.

http://hddguru.com/software/HDD-Raw-Copy-Tool/

Linux users can use the dd tool that comes with most versions of Linux (including Raspbian) to save the contents of an SD card as an image file. Warning: be sure to use this tool carefully as accidentally choosing your hard drive as the output may destroy all data on it.

==Media Player==
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).

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]

You can download an installer from www.raspbmc.com which will install to your desktop (IOS, Windows, Linux) and write the latest install to your SD card. You then boot your Pi with the card and go through the config steps.

There is a breif video basic tutorial here: http://www.instructables.com/id/RaspberryPi-Media-center-XMBC/

''Reference needed - More information is needed on specific configuration choices for raspbmc, although raspbmc.com does have a wiki.''

==Play Games==
While there are not any commercial games for the Raspberry Pi (yet) there are plenty ways to play games on it.

Many distributions will have games built into them, and some may well support emulation of other platforms so you can run those games.

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).

Reference needed - game section is empty at the moment!
''See the [[RPi Games|Games Section]] for more details''

==Introducing Young Children To Computers==
Reference needed - some kid friendly and fun stuff!

==Teaching==
There is a huge number of groups, links and resources available within the [[RPi Education|Education]] section.
Reference needed - links to the learning pages, education links and school/university groups

==Learn To Program==
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.

There is a huge selection to choose from (not just Python...) which should suit any ability and a range of purposes.

If you are new to programming, there are plenty of tutorials for getting started in the [[RPi Tutorials|Tutorials]] Section.

Books about programming can be found in the [[RPi Programming Books|Books]] Section.

In the latest Debian, Python (+Pygame) and MIT Scratch are pre-installed.

Reference needed - links to the learning pages, recommended books?

==Interface With Hardware==
# [[RPi Interfacing with hardware|Interfacing with Arduino]]

Reference needed - links to basic circuits tutorials and expansion boards

==Word Processing/Internet Browsing etc==
Yes, the Raspberry Pi can do the majority of the dull stuff too which other computers do.

'''Debian''' currently comes with Midori installed for web browsing and word processing programs be installed rather easily.

*Entering "sudo apt-get install chromium-browser" into a terminal will install Chromium which is generally a faster and more featured browser than Midori
*Entering "sudo apt-get install openoffice.org" into a terminal will install OpenOffice.org, a free Microsoft Office-like application suite
*Entering "sudo apt-get install abiword-common" into a terminal will install AbiWord, a lighter weight but still fully functional word processor
*Entering "sudo apt-get install gnumeric" into a terminal will install Gnumeric, a lighter weight but still fully functional spreadsheet

More information needed

==Your Own Pet Project!==
The sky is the limit really, with some time and effort any number of projects can be achieved.

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.

Of course, if you do anything interesting then please let us know in the [[RPi Projects |Projects]] section.

=Living Without RPi=
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.

==Using Linux==
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).

RacyPy - This is a simple LiveCD of Puppy Linux which includes some basic programming languages and a light-weight graphical user interface (GUI).

You can get it from here:

[http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ teampython RacyPy]

==Trying Programming==
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.

==Controlling Hardware==
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).

=About This Page - For Contributors=

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.

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)!

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.

----

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

R-Pi Troubleshooting

2012-09-01T20:54:18Z

Bredman: /* Network connection fails when a Graphical User Interface is being used */

[[Category:RaspberryPi]]

Back to the [[R-Pi Hub|Hub]].

This page lists the most common problems and suggests some solutions.

See [[RPi_Bugs]] for problems that are bugs.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.
*Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured from the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

If start.elf won't launch it may be corrupt and can be replaced with arm240_start.elf or any of the other armXXX_start.elf files.

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

Immediately after displaying the splash screen, the PI starts consuming a little more current, if the PI resets at that moment its an indication that your PSU isn't able to deliver the full current your PI requires, but dips its output voltage below a minimum when loaded with the full current the PI needs.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down (or restarts) soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.
*It could be that the SD memory card is not making proper contact with the Raspberry Pi. Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured fron the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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 WiFi 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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm240_start.elf : 240M ARM, 16M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm240_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==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 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.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

===Crashes occur with high network load===

The USB driver allocates memory from the kernel, and when traffic is very high (e.g. when using torrents/newsgroup downloads) this memory can be exhausted causing crashes/hangs. You should have a line like:

vm.min_free_kbytes = 8192

in /etc/sysctl.conf. Try increasing that number to 16384 (or higher). If that doesn't work, try adding to /boot/cmdline.txt

smsc95xx.turbo_mode=N

which will reduce network throughput, but has improved stability issues for some.

===Network connection fails when a Graphical User Interface is being used===

The network connection may fail when the command startx is used to enter a Graphical User Interface. This is caused by a bug in the USB driver related to certain types of USB mouse.

As of 1 September 2012, this fault is fixed in the latest firmware. To load the latest firmware, see
[http://elinux.org/R-Pi_Troubleshooting#Updating_firmware http://elinux.org/R-Pi_Troubleshooting#Updating_firmware]

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root
*Bodhi: pi/bodhilinux

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

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.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Screen is the wrong color===
Check and see if the DVI cable is screwed in properly. If that doesn't work then try [[#Interference_visible_on_a_HDMI_or_DVI_monitor|this]] section.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

=References=
<references/>

{{Template:Raspberry Pi}}

[[Category:RaspberryPi]]

R-Pi Troubleshooting

2012-09-01T20:52:31Z

Bredman: New section, Network connection fails when a Graphical User Interface is being used

[[Category:RaspberryPi]]

Back to the [[R-Pi Hub|Hub]].

This page lists the most common problems and suggests some solutions.

See [[RPi_Bugs]] for problems that are bugs.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.
*Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured from the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

If start.elf won't launch it may be corrupt and can be replaced with arm240_start.elf or any of the other armXXX_start.elf files.

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

Immediately after displaying the splash screen, the PI starts consuming a little more current, if the PI resets at that moment its an indication that your PSU isn't able to deliver the full current your PI requires, but dips its output voltage below a minimum when loaded with the full current the PI needs.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down (or restarts) soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.
*It could be that the SD memory card is not making proper contact with the Raspberry Pi. Look at the SD card holder on the Raspberry Pi carefully. At first glance it may look fine but the contacts must be springy and they must protrude at least 2mm as measured fron the lower edge of the holder to the top of the contact bulge. This happens due to the solder process and the type of holder used. Some of the solder residue falls into the contact cavity restricting the springiness and the height that the contact protrudes. You can fix this yourself but remember you can void your warranty. The contacts are delicate so be carefull. Insert a needle pin under the contact bulge and pull lightly up until the one end of the contact unclips. Clean the cavity where the contact unclipped from of any solder or other residue by blowing into the cavity. Clip the contact back into the cavity by lightly pushing it into the cavity. Do this for all the contacts. Look at these photos. [[Media:SDcardHolder.JPG]], [[Media:UnclipContact.JPG]], [[Media:UnclippedContact.JPG]]

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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 WiFi 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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm240_start.elf : 240M ARM, 16M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm240_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==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 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.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

===Crashes occur with high network load===

The USB driver allocates memory from the kernel, and when traffic is very high (e.g. when using torrents/newsgroup downloads) this memory can be exhausted causing crashes/hangs. You should have a line like:

vm.min_free_kbytes = 8192

in /etc/sysctl.conf. Try increasing that number to 16384 (or higher). If that doesn't work, try adding to /boot/cmdline.txt

smsc95xx.turbo_mode=N

which will reduce network throughput, but has improved stability issues for some.

===Network connection fails when a Graphical User Interface is being used===

The network connection may fail when the command startx is used to enter a Graphical User Interface. This is caused by a bug in the USB driver related to certain types of USB mouse.

As of 1 September 2012, this fault is fixed in the latest firmware. To load the latest firmware, see
http://elinux.org/R-Pi_Troubleshooting#Updating_firmware

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root
*Bodhi: pi/bodhilinux

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

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.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Screen is the wrong color===
Check and see if the DVI cable is screwed in properly. If that doesn't work then try [[#Interference_visible_on_a_HDMI_or_DVI_monitor|this]] section.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

=References=
<references/>

{{Template:Raspberry Pi}}

[[Category:RaspberryPi]]

RPiconfig

2012-08-31T13:05:12Z

Bredman: Tidied up display_rotate text to make it easier to read

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value" where value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility. This is the same as the combination of: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0
hdmi_safe=1

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''edid_format_smart_match''' Allow fuzzy matching of modes described in edid. Picks the standard mode with matching resolution and closest framerate even if blanking is wrong.
edid_format_smart_match=1

'''hdmi_ignore_cec_init''' Doesn't sent initial active source message. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec_init=1

'''hdmi_ignore_cec''' Pretends CEC is not supported at all by TV. No CEC functions will be supported.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive=1 Normal DVI mode (No sound)
hdmi_drive=2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

'''display_rotate''' rotates the display on the screen (default=0)
display_rotate=0 Normal
display_rotate=1 90 degrees
display_rotate=2 180 degrees
display_rotate=3 270 degrees

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Licensed Codecs=
Hardware decoding of additional codecs can be enabled by purchasing a license that is locked to the CPU serial number of your Raspberry Pi.

'''decode_MPG2''' License key to allow hardware MPEG-2 decoding.
decode_MPG2=0x12345678

'''decode_WVC1''' License key to allow hardware VC-1 decoding.
decode_WVC1=0x12345678

License setup for SD-card sharing between multiple Pis
decode_XXXX=0x12345678,0xabcdabcd,0x87654321

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|avoid_pwm_pll
| Unlink core_freq from the rest of the gpu. Can cause low quality analog audio, which should be fixed with latest firmware. Default 0
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

This is not necessary with "avoid_pwm_pll=1".

==Tested values==
The following table shows some successfull attempts of overclocking, which can be used for orientation. These settings may not work on every device and can shorten the lifetime of the Broadcom SoC.

'''Warning: Warranty will be voided if overvoltage is used!'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|800 || || || || || || || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|-
|1050 || || || || || || ||6 ||
|-
|1150 || ||500 || || || ||600 ||8 ||
|}
There are [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&p=159188&hilit=hynix#p159160 reports] that Hynix RAM is not as good as Samsung RAM for overclocking.

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPiconfig

2012-08-31T12:56:01Z

Bredman: /* Video mode options */

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value" where value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility. This is the same as the combination of: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0
hdmi_safe=1

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''edid_format_smart_match''' Allow fuzzy matching of modes described in edid. Picks the standard mode with matching resolution and closest framerate even if blanking is wrong.
edid_format_smart_match=1

'''hdmi_ignore_cec_init''' Doesn't sent initial active source message. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec_init=1

'''hdmi_ignore_cec''' Pretends CEC is not supported at all by TV. No CEC functions will be supported.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive=1 Normal DVI mode (No sound)
hdmi_drive=2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Licensed Codecs=
Hardware decoding of additional codecs can be enabled by purchasing a license that is locked to the CPU serial number of your Raspberry Pi.

'''decode_MPG2''' License key to allow hardware MPEG-2 decoding.
decode_MPG2=0x12345678

'''decode_WVC1''' License key to allow hardware VC-1 decoding.
decode_WVC1=0x12345678

License setup for SD-card sharing between multiple Pis
decode_XXXX=0x12345678,0xabcdabcd,0x87654321

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|avoid_pwm_pll
| Unlink core_freq from the rest of the gpu. Can cause low quality analog audio, which should be fixed with latest firmware. Default 0
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

This is not necessary with "avoid_pwm_pll=1".

==Tested values==
The following table shows some successfull attempts of overclocking, which can be used for orientation. These settings may not work on every device and can shorten the lifetime of the Broadcom SoC.

'''Warning: Warranty will be voided if overvoltage is used!'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|800 || || || || || || || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|-
|1050 || || || || || || ||6 ||
|-
|1150 || ||500 || || || ||600 ||8 ||
|}
There are [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&p=159188&hilit=hynix#p159160 reports] that Hynix RAM is not as good as Samsung RAM for overclocking.

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Install software

2012-08-27T13:04:56Z

Bredman: Added sudo apt-get update

[[Category:RaspberryPi]]
Back to [[RPi Guides]].

'''Installing a software package on a Raspberry Pi'''

=What does it do?=

This guide shows you how to install a software package on a Raspberry Pi.

These instructions will show you how to install software from the command line. This is a very important skill if you wish to progress further with Linux.

=What do you need?=

*A Raspberry Pi, model B.
*A Debian SD card for the Raspberry Pi, size should be 2GB or larger.
*A network connection (Ethernet or WiFi).

=What skill level is required?=

Suitable for absolute beginners. No Linux knowledge is needed.

It is assumed that you have used a computer before, for example a Windows PC.

=Installing the software=
Unplug the power cable from the Raspberry Pi.

Insert a Debian SD card in the Raspberry Pi.

Connect the Ethernet cable from your Raspberry Pi to a modem or other internet service. You may also use a WiFi device, but you may need help to get this working.

Connect the power cable. Log in with your username and password.

To check if your internet connection is working, enter the following command and press enter at the end.
'''ping -c 1 www.raspberrypi.org'''

If your internet connection is working, you should see a statistics report which contains the following
'''1 packets transmitted, 1 received, 0% packet loss'''

If you get an error message instead, or a report of 100% packet loss, you have a problem with your internet connection. You must ask somebody to help fix this problem before you can proceed.

Enter the following command and press enter at the end.
'''sudo apt-get update'''
This command will fetch the latest software lists. The command may take a couple of minutes to complete, you can ignore any warnings that you see.

Enter the following command and press enter at the end.
'''sudo apt-get install xxxx'''
where xxxx is the name of the software package that you wish to install.

For example, to install the software package chromium-browser, you should use the command
'''sudo apt-get install chromium-browser'''

You may be asked for your password. Enter your password and press enter. Note that you will not be able to see your password.

[[File:RPiInstallChromium1.jpg]]

You may be asked for permission (yes/no) to install new software.

[[File:RPiInstallChromium2.jpg]]

Press the 'y' key and enter to continue.

Wait for the installation to complete.

[[File:RPiInstallChromium3.jpg]]

The software installation is now finished.

=Removing the software=
''Use these instructions if you wish to remove a software package.''

Follow the instructions above to install the software, but use this command instead.
'''sudo apt-get remove xxxx'''
where xxxx is the name of the software package that you wish to remove.

RPi VerifiedPeripherals

2012-08-16T12:29:33Z

Bredman: /* Working USB Wifi Adapters */

[[Category: Linux]]
[[Category: ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template: RPi_Hardware}}

'''A note about this page: For USB devices, please specify if they required a powered hub'''
==Notes==

19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the [http://www.raspberrypi.org/downloads default Debian distribution] unless stated otherwise. A suggested suffix markup scheme is as follows:

* (A) - Relates to model A production board
* (B) - Relates to model B production board
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different
* No markup - relates to all production boards

''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''

If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.

{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}

'''Generally speaking the model B raspberry PI was designed only for <100mA USB devices!''' That is because the PI's PSU was chosen with a power budget of 700mA in mind of which 200mA were assigned to the two USB ports, so the raspberry PI's (poly)fuses were designed only for <100mA devices, and typical 140mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100mA limit. As a consequence the USB ports are only directly suitable for "single current unit" USB devices which according to USB specifications are designed to work with just 4.4 Volt. Not only do non single current unit devices draw more current, (causing greater Voltage drops, and greater stress on the fuses) they also might require 4.75 Volt to work. Therefore any non single current unit devices will only work when powered from a powered hub.

== Powered USB Hubs ==
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.

If you use a powered hub and PI PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the PI through their interconnect cable, due to the 100mA limiting fuse in the PI the PI will be partially powered which may cause problems (unwanted writes to the SD card).

===Working USB Hubs===
*'''Acme'''
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but very cheap and small and works after a small modding: on usb-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the RasPI, and additionally connect GND and +5v from power supply to the same holes on usb-hub GND and V. Now there is common contacts: GND, D+ and D- between RasPI and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my RasPI.
*'''Belkin'''
** F4U040 4-Port Ultra-Slim Desktop hub (powered 5v, 2.6A)
** F5U224 4 port powered USB hub
** F5U231/F5U234 Hi-speed USB 2.0 Tertrahub - 4 port powered USB hub (verified.. able to power Raspberry Pi using micro USB directly from hub)
** F5U237 7 Port powered USB 2.0 5V 3.8A (5 back port 2 top ports)
** F5U259-ME USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time)
** F5U403 USB 2.-0 4 Port Hub (Powered, suspect see F5U404 in non-working, didn't test power the RPi from hub.)
** F5U700 USB 2.0 7-Port Hub (Powered, able to power Raspberry Pi via micro USB directly from hub)
** F5U706ea/uk 2-in-1 Hub (USB 2.0, powered, 7-port)
** F5U706701PerBlk 7-in-1 Hub (USB 2.0, powered 5V 2.5A , 7-port)
*'''Biltema'''
** 23-924 4-port powered USB 2.0 Hub (2.0A) Able to power Raspberry Pi via USB port
*'''CyberPower'''
** [http://www.newegg.com/Product/Product.aspx?Item=N82E16817804002] CP-H720P 7-port powered hub with 3.6A adapter. Internally, a NEC Corp 0409:0050 device. Works perfectly with Model B, regardless of whether the RPi is being powered by the hub or externally.
*'''Dell'''
** Dell 2001FP monitor has 4 USB ports and acts as a powered hub.
** Dell SP2309W monitor has 4 USB ports and acts as a powered hub.
*'''DELTACO'''
** [https://www.deltaco.se/products/items/itemid/(UH-715)/index.aspx UH-715 Rev 2] 7-port powered hub with 2A adapter.
*DYNEX
** 7port hob idVendor=0409, idProduct=0050 works
*'''D-Link'''
** [http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF] 7-Port USB Hub DUB-H7 (See note below - doesn't work for all, apparently). Working model marked BUBH7A....A5. Worked with Debian on production B model, for keyboard, mouse, and thumb drives, also worked with ArchLinux, didn't work with Bodhi Linux immediately thereafter.
** [http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] 4-Port USB Hub DUB-H4 Worked on Debian with keyboard, mouse, and thumb drive. Also, was able to apply power to raspberry pi via micro usb from this hub at same time.
*'''Digicom'''
** [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#] MiniHUB 4-Port USB 2.0 with PSU 5V - 2A .
*'''Eminent'''
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2A power adapter. It's able to power the RPi, external HDD and other peripherals.
* '''GearHead'''
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5V, 1A)
* '''Genesys Logic (sold at Fry's)'''
** Genesys Logic 4-Port USB 2.0 Hub 2.0 Amps (ID 05e3:0608) (Also at Radio Shack under their Gigaware brand, same ID shows up in lsusb)
* '''Hama'''
** Hama 4-way USB 2.0 Hub
*'''HP'''
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)
*'''Laser'''
** 7-Port USB Hub. 5V 1A (found at Harvey Norman Australia)(Also Australia Post Shops $9.95). You can power the PI by connecting both the main USB connector to the PI USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.
*'''Logik'''
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''
** Logik L4THUB10 4 Port powered hub works fine under raspbian/wheezy/model B. Captive usb cable, 2A power supply, convenient single top mounted usb socket. Unlike my last hub, will power wifi!
*'''LogiLink'''
** UA0085 USB 2.0 Hub, 4-Port with PSU 5V, 2A
** UA0091 USB 3.0 Hub, 4-Port with PSU 5V, 4A. Connected with USB2.0 cable. 1A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy.
** UA0096 USB 2.0 Hub, 10-Port with PSU 5V, 3.5A (Not suitable for powering RPi because it doesn't work unless there is working USB input present even with PSU plugged in.)
** UA0160 USB 2.0 Hub, 4-Port with PSU 5V, 2A. Able to power the RPi, keyboard, mouse and LogiLink UA0144 USB ethernet adapter. (More testing to come.)
* '''Manhattan'''
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000mA wall-wart (US style)
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A
*'''Nilox'''
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5V 1.0A
* '''Pluscom'''
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3Amp PSU. USB ID 1a40:0101. Powering Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Pi but not really a problem when powering Pi at the same time. (from [http://www.trendinguk.co.uk/7-port-usb-20-powered-hub-for-raspberry-pi.html TrendingUK ]) (also from [http://www.ebay.co.uk/itm/330749956598 eBay ])
*'''SumVision'''
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5V 1.0A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])
*'''Sitecom'''
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500 mA Voltcraft
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1A). Powering Pi via microUSB from a hub port.
*'''Targus'''
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)
** ACH63EU 4-port. Using a 5V 2A power supply, which isn't supplied with the hub, it is able to power the PI as well.
*'''Trendnet'''
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5V 2A)
*'''Tripp-Lite'''
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5V 2.5A) Powering RPi from Hub works
*'''Ultron'''
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5V, 3A. USB ID 1a40:0201.
*'''Z-TEK'''
** Z-TEK 7-port powered hub with PSU 5V, 4A. USB ID 1a40:0201.
*"Unknown"
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works

===Problem USB Hubs===

Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list

*'''Addon'''
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.
*'''Belkin'''
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, wifi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but still unstable with mass storage devices. Also, leaks current back to the Pi (can be fixed by overtaping GND and +5V pinouts)

** F4U022 7-Port powered USB hub (powered 5v, 2.6A), same as F4U018
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes.

*'''DELTACO'''
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills ethernet when X11 is started.

Dynex
7-Port USB Hub - Does not work in Debian 19-04 image.

*'''D-Link'''
** 7-Port USB Hub DUB-H7 (Prevents ethernet from being recognized so wrong time & no IP address). (See note above - it worked for me with some distros)

*'''E-Solution'''
** 4-Port 2A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]

*'''Fosmon'''
** 7-Port USB 2.0 Hub w/ 1A Power Supply (Causes interference with other USB devices and sends enough power to light up the pi with it's Micro USB cable unplugged).

*'''Gear Head'''
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.

*'''Hama'''
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but does not work for power hungry devices (HDD,WLAN). Doesnt boot when hub connected to RPi. The funniest thing is that RPi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608

*'''Kensington'''
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).

*'''Inland'''
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)

*'''Logik'''
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)

*'''Soniq'''
** 4-Port 5V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Pi has an isolated power line. Netgear WNA1100 WiFi Adapter (which is known to work in other setups is recognized, but unresponsive.

*'''Targus'''
** ACH115EU 7-port powered hub. 5V 3A power supply. Arduino communicates with RPi when connected directly to Pi's USB port, but it hangs soon if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.

*'''TCM'''
Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1A power supply. Model B, Wheezy raspian works ok with keyboard/mouse but problems with WiFi no connects. (insufficient power?)

*'''Trust'''
** 10-port USB 2.0 Hub (powered). Prevents ethernet from being recognised.
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents ethernet from being recognised. Keyboard sends multiple characters.

*'''Unbranded / Multiple Brands'''
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in)
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref>
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but strange USB failures when X session started. High speed devices such as hard drives had failures.

== USB Remotes ==
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

* [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] '''Rii''' Wireless 2.4 Ghz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]

* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. Pad works as mouse but not multi touch features. Keyboard works.

* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4 GHz wireless keyboard and touchpad

* ATI Remote Wonder (X10 Wireless Technology, Inc. X10 Receiver) — ID 0bc7:0004 — appears as a joystick-like 2 button mouse and a 0-9 keypad without drivers on console and X.

== USB Keyboards ==
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''
=== Working USB Keyboards ===
The following is a list of specific keyboards known to work and which appear to work fault-free.

* '''A4 Tech'''
** Model KL-5 USB Keyboard, 20mA.

* '''ABS'''
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)

* '''Action Star'''
** ACK-5010U Mini Keyboard And Mouse

* '''Accuratus'''
** KYB-Toughball-HI

* '''Acer'''
** KG-0917 Wireless Keyboard And Mouse Bundle (B)
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)

* '''Adesso'''
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.
** Model AKB-410UB. Keyboard with Touchpad.

* '''Apple'''
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Keyboard (109 keys) A1048] - requires external powered hub to work, does not work on PI directly!
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]

* '''Asda'''
** Basic Wired Keyboard HK2026 (B)
** Basic Wired Keyboard HK3014
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)
** Premium Wireless Keyboard (white keys, silver back) HK8028
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)

* '''Asus'''
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)

* '''BTC - Behavior Tech Computer Corp.'''
** Wired Portable Keyboard Model 6100 US (86+9 keys)
*** Works with or without a powered hub
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)

* '''Bush'''
** Wired Slimline Keyboard KU-0833
*** This does not require a USB hub in order to work with the Raspberry Pi
*** In the UK, it is available from Argos for £9.99

* '''Cerulian'''
** Mini wireless keyboard and mouse deskset (B)

* '''Cherry'''
** CyMotion Master Linux (B)
** RS 6000 USB ON
** G84-4100PTMUS (B) (Compact keyboard. Rated 100mA. Works directly in Pi)

* '''Dell'''
** SK-8115 (B) (Rated 100mA. Works directly in pi)
** L100 (B)
** RT7D50 (75mA) (run "sudo dpkg-reconfigure keyboard-configuration")
** KB1421 (100mA)
** KB2521 (100mA)
** 1HF2Y (Works directly in pi)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500mA but works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Das Keyboard'''
** Model S Professional Keyboard (Built in USB hub not tested) (B)
** Model S Ultimate Keyboard (Built in USB hub working) (B)

* '''Dynex'''
** DX_-WKBD (60ma) (B)
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle usb hub) (B)

* '''EAPPLY'''
** EBO-013 Wireless 2.4GHz compact keyboard with touchpad. Rated <40mA works directly from Pi. eBay ref 260962010276 from Shenzen, China.

* '''Emprex'''
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)

* '''Fujitsu Siemens'''
** KB SC USB UK (!)
** KB910 USB, with led light on the highest level (B)
** KB400 USB US

* '''Gear Head'''
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)
** KB1500U (USB Mini Keyboard) (B)
** KB5150 (2.4Ghz wireless keyboard/mouse Combo) (B)
*** Works well with a powered hub

* '''Genius'''
** Ergomedia 700 (GK-04008/C) used without Hub
** KB-06XE (K639) (B)
** Slimstar 8000 wireless keyboard

* '''HP'''
** KG-1061
** KG-0851 Wireless Keyboard and Mouse
** KU-0316 (B)
** LV290AA#ABA Wireless Keyboard and Mouse
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)
** SK-2880

* '''Hyundai'''
** HY-K201

* '''iConcepts'''
** 2.4GHz Wireless Keyboard and Optical Mouse Model 62550
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)

* '''Imation'''
** KBD-702 Multi-media Wired Keyboard
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)

* '''IOGEAR'''
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball
** IOGEAR GKM681R 2.4GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel

* '''iPazzPort'''

* '''i.t.works'''
** KC04 (direct and by usb hub)
** KC Silicone (only tested directly)

* '''Jenkins'''
** Jenkins Wireless Desktop Set Blue (B)

* '''KeySonic'''
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Pi.
** ACK-540RF+ (UK) WiFi keyboard inc touchpad with USB wifi dongle works fb with on model B/raspian/wheezy via powered hub
** ACK-3700C
** ACK-340U+(DE)
** ACK-3400U (UK) mini keyboard

* '''Laptopmate'''
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad

* '''LC-Power
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4GHz Trackball Keyboard) tested with Debian 6.0.4

* '''Lenovo'''
** SK-8825 UK (B)
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)
** Lenovo Mini Wireless Keyboard N5901 (US)

* '''Lindy'''
** 21840 (Wireless RF 2.4GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/raspian/wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Pi USB port.

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''

* '''Logitech'''
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, bluetooth w/ USB mini-receiver 967685-0403 (B)
** Wii wireless keyboard KG-0802 (!)
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)
** Deluxe 250 Keyboard
** Internet 350 (M/N 967740-0403)
** Internet Navigator Keyboard
** MK220 wireless keyboard and mouse
** MK250 wireless keyboard and mouse
** MK260 wireless keyboard and mouse
** MK300 wireless keyboard and mouse
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]
** MK520 wireless keyboard and mouse
** MK550 wireless keyboard and mouse (B)
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** K120 Keyboard (B)
** K200 Keyboard (B)
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K350 Wireless Keyboard (B)
** K400 wireless keyboard with touchpad - also listed unter problematic. works for weeks with openelec and raspbian without any problems.
** K520 Keyboard (B)
** K700 Wireless Keyboard with Touchpad and unifying receiver
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )
** S510 wireless keyboard and mouse (B)
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100 mA. OK direct into Model B RPi.
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hum in back of keyboard works too.
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.

''Keyboards and mice also together with Unifying receiver''

* '''Microsoft'''
**Microsoft Comfort Curve Keyboard 2000
**Microsoft Comfort Curve Keyboard 3000 for Business
**Microsoft Digital Media Pro Keyboard Model : 1031 (Debian 13-Apr-2012)
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)
**Microsoft Windows 2000 Keyboard (KB-USBK110610)

* '''Mikomi'''
** Wireless Deskset KM80545 Keyboard and mouse (Works but range is terrible less than a metre) (B)

* '''Monoprice'''
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.

* '''Motorola'''

** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below

* '''Novatech'''
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)

* '''Perixx'''
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/raspian wheezy)

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

* '''Rapoo'''
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad

*'''Rosewill'''
** RK-200 Standard Keyboard

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)
** Eclipse Backlit Keyboard PZ30AV (B)
** Expression Keyboard (US)
** Cyborg V.5 (B)

*'''SIIG'''
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)

*'''Silvercrest'''
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B)

*'''Sony'''
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5v1A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.

* '''SteelSeries'''
** Merc keyboard (B)

* '''Sun Microsystems'''
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard

* '''Technika'''
** WKEY03 (B)
** TKD-211

* '''Tesco'''
** Value Keyboard VK109 (B)
** Multimedia K211 Wired Keyboard (B)

*'''TrendingUK'''
** Super Slim Apple Style Keyboard (from [http://www.trendinguk.co.uk/usb-keyboard-for-the-raspberry-pi.html TrendingUK ]) (and [http://www.ebay.co.uk/itm/330742818099 eBay ])
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://www.trendinguk.co.uk/usb-keyboard--mouse-bundle-for-the-raspberry-pi.html TrendingUK ]) (and [http://www.ebay.co.uk/itm/330730092277 eBay ])

* '''Trust'''
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust ClassicLine Keyboard http://trust.com/17184
** Trust Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
** Trust Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)

* '''Unbranded'''
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller

* '''Unicomp'''
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub

* '''Q-Connect'''
** AK-808 (B)

* '''Xenta'''
** 2.4GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)
** Mini Multimedia Keyboard (Model no.: 808M) (B)

===Problem USB Keyboards===

Note that generally PS/2 keyboards with an USB adapter will not work directly on a PI port, due to the fact that PS/2 keyboards are designed for normal 5V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the PI may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0V. Some of these keyboards work when running the latest raspbian but not when using the overclocked xbmc version of raspbmc, probably due to the overclocking drawing more voltage away from the rest of the support system devices.

* '''Accuratus'''
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100mA). Tested with 1000mA cheap unbranded and Nokia 1200mA power adaptors.
*'''Argos'''
** Argos Value Wired Keyboard causes kernel panic
* '''Choidy'''
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic
* '''Cit'''
** KB-1807UB Causes kernel panic (Rated <200ma)
* '''Dell'''
** SK-8135 (B) (Rated 1.5A. Takes too much power from pi even when not used as USB hub. Symptom = repeated keystrokes)
** SK-8115 causes kernel panic (rated 100mA) Debian 6-19-04-2012 (B)
** Y-U0003-DEL5 Sticky / Non-responsive keys
* '''GMYLE'''
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]
* '''Gear Head'''
** KB2300U - Causes kernel panic (B)
* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Labtec'''
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)
* '''Logik'''
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''
* '''Logitech'''
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)
** K360 Wireless Keyboard - Occasional sticky keys. (B)
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)
** G510 Gaming Keyboard - lagging or unresponsive keys.
** MX5500 wireless keyboard and mouse with usb bluetooth reciever - Unstable, looses connection without prior notice
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).
* '''Microsoft'''
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.
** Arc wireless - Keyboard has 'sticky' keys. (B)
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)
* '''Novatech'''
** NOV-KEY2 - Causes kernel panic (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B) <ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.
* '''PC World Essentials'''
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, same Pi works with Asda keyboard. Me too, but caused a kernel panic -- tested on powered hub and direct.
* '''Razer'''
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED)
* '''Texet'''
** MB-768B standard keyboard (Rated 5V 1.5A(!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)
* '''Trust'''
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.
* '''Wilkinsons / TEXET'''
** Model MB-768B causes kernel panic on debian6-19-04-2012.
* '''Xenta'''
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up
* '''Jeway'''
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)

== USB Mouse devices ==
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.

===Working USB Mouse Devices===
The following is a list of specific mouse devices known to work and which appear to be fault-free.

* '''A4Tech'''
** OP-530NU Padless Wired Mouse

* '''Asda'''
** HM5058 (Smart Price) Wired Mouse
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)

* '''Asus'''
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)

* '''Belkin'''
**F8E882-OPT (B)

* '''Dell'''
** M-UVDEL1 (B)
** M056U0A (B)
** DZL-MS111-L (B) (100mA)
** MS-111P (100mA)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500mA but works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Dynex'''
** DX-WMSE (100mA) (B)

* '''Filand'''
** OP-102i Mini Optical Mouse

* '''Genius'''
** GM-04003A (B)
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)
** Traveler 515 Laser

* '''HP'''
** MN-UAE96 (The basic stock HP wired mouse)(B)

* '''iConcepts'''
** 2.4GHz Wireless Keyboard and Optical Mouse Model 62550
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)

* '''Jenkins'''
** Jenkins Wireless Desktop Set Blue (B)

* '''Logik'''
** Wired Optical Glow Mouse Model: LGGMO10. (B)

* '''Logitech'''
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE
** G5 Logitech Gaming Mouse (B)
** G5v2 Logitech Gaming Mouse (B)
** G500 Logitech Gaming Mouse (B)
** G700 Logitech Wireless Gaming Mouse (B)
** LX-700 Cordless Desktop Receiver (B)
** M90 optical mouse
** M185 Wireless Mouse (B)
** M210 (part of the MK260 set) (B)
** M305 Wireless Mouse
** M310 Cordless Mouse
** M325 Wireless Mouse
** M505 USB wireless laser, model no: 910-001324 (B)
** M510 Wireless Mouse (B)
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)
** M-BD58 Wheel Mouse (B)
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)
** M-BJ79 (B)
** M-BT96a Optical Mouse
** MX320/MX400 laser mouse (B)
** MX518 Optical wheel mouse (B)
** Optical USB Mouse (M/N 931643-0403)
** Performance Mouse MX (B)
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)
** VX Nano Cordless Laser Mouse for Notebooks
** Wheel Mouse (M/N BJ58)

* '''Medion'''
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5v 100ms Works fb on model B with raspian wheezy

* '''Microsoft'''
** Comfort Curve Mouse 3000 for Business
** Comfort Mouse 6000
** Compact optical mouse 500 V2.0 (B)
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)
** Microsoft Intellimouse Optical Mouse
** Microsoft Wireless Laser Mouse 8000
** Microsoft Wireless Mobile Mouse 3500
** Microsoft Wireless Mobile Mouse 4000
** Microsoft Wireless Mouse 700 v2.0
** Microsoft Comfort Mouse 4500
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)

* '''Novatech'''
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)

* '''Razer'''
** Boomslang Collectors Edition 2007 (B)

* '''Rosewill'''
** Rosewill RM-C2U

* '''Saitek'''
** Notebook Optical Mouse (PM46)

* '''Sun microsystems'''
** Model: FID-638 , SunPN: 371-0788-01

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015] Mini Wireless Optical Mouse

* '''Targus'''
** AMU2701EUK (B)

* '''Technika'''
** TKOPTM2 (B)
**TKD-211

* '''Tesco'''
** Wired optical mouse M211 (B)

*'''TrendingUK'''
** USB Mouse for Raspberry Pi ([http://www.ebay.co.uk/itm/330741942074 eBay ])
** Super Slim Keyboard & Mouse Set (from [http://www.trendinguk.co.uk/usb-keyboard--mouse-bundle-for-the-raspberry-pi.html TrendingUK ]) (and [http://www.ebay.co.uk/itm/330730092277 eBay ])

* '''Trust'''
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087

* '''Verbatiam'''
**Mini Nano Optical Mouse 97470 (wireless on non-powered 3 usb dongle hub) (B)

* '''Xenta'''
** MOW0810 (B)
** Wired Optical Mouse (from [http://www.trendinguk.co.uk/usb-mouse-for-the-raspberry-pi.html TrendingUK ])

* '''Generic'''
** Generic 2.4GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)

===Problem USB Mouse Devices===
The following is a list of specific mouse devices that have problems working with the Raspberry Pi
* '''HP'''
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors.

* '''Logik'''
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)

* '''Logitech'''
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000Hz out of the box, whereas the 518 is only 125Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.

* '''Razer'''
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works but the cursor doesn't move.

* '''Roccat'''
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)

* '''Trust'''
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)

* '''Xenta'''
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle

== USB WiFi Adapters ==

See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing

There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.

===Working USB Wifi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.

'''Note:''' A WiFi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the WiFi adapter to the WiFi Access Point. Therefore, you may need to plug the WiFi adapter into a powered USB hub.

* '''3COM'''
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)

* '''7DayShop'''
** W-3S01BLK, W-3S01BLKTWIN : Unbranded product available from 7DayShop, in a single or twin pack. [http://www.7dayshop.com/catalog/product_info.php?cPath=777_9&products_id=112046], [http://www.7dayshop.com/catalog/product_info.php?&products_id=112527]. Tested on Debian Wheezy, with the dongle attached directly to the RPi along with the wireless keyboard receiver. Shows up as a Ralink RT5370 device, and no drivers or additional software downloads required. Created wpa.conf, edited 'interfaces' file and restarted the networking. The manufacturer portion of the MAC address (7cdd90) is assigned to "Shenzhen Ogemray Technology Co., Ltd."

* '''Alfa'''
** AWUS036NEH: Tested on Debian Squeeze (with Ralink firmware package)
** AWUS036NH: Tested on Arch Linux ARM using the rt2800usb module.
** AWUS036NH: Tested on Debian Wheezy (with Ralink firmware package)

* '''AirLink101'''
** AWLL5088: Tested on Debian Wheezy. This adapter is based on the OEM Edimax EW-7811Un. For automatic installation, See MrEngmanns script listed below under the Edimax device.

* '''Asus'''
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B) (not needed with latest Raspbian “wheezy” 2012-07-15: this Asus works N10 out of the box)
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, works with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1 Adafruit Occidentalis v0.1 image] as it includes kernel [http://www.element14.com/community/message/57635#57660 with 8192u driver built-in] (B)
** WL-167G v1 USB ID 0b05:1706, Ralink RT2571 working out-of-the-box on Debian image from 2012-04-19. Requires powered hub, otherwise it is detected by OS but will not function.

* '''Belkin'''
** Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]. On Debian requires the firmware-ralink package from the non-free repository. The usbcore module needs to be added to /etc/modules [http://www.penguintutor.com/blog/viewblog.php?blog=6281 install instructions].
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Tested on OpenELEC (works OOB), RaspBMC (works OOB), Raspian - 2012-07-15-wheezy-raspbian (followed [http://forum.xbian.org/viewtopic.php?f=7&t=29 instructions here]) '''Powered hub required!'''
** Belkin Components F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU] USB ID 050d:945a, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
**Belkin Components F6D4050 V1 [Realtek RT3070] USB ID: 050d:935a Driver: RT3572STA(recommended),RT2800USB,RT2870STA. Tested under Arch using [https://wiki.archlinux.org/index.php/Setting_Up_Belkin_F6D4050_Wireless_USB_Dongles this] guide.
**Belkin Components F6D4050 V1/V2 [Realtek RT3070] USB ID: 050d:935a / 935b Driver: RT3572STA. Tested with Raspbian - See [http://iggy82.blogspot.co.uk/2012/08/wireless-n-raspberry-pi-belkin-f6d4050.html installation instructions] - Powered hub not required!
** Belkin Components F7D2102 "N300" Micro Wireless USB adapter. Tested with Occidentalis 0.1.

* '''BlueProton'''
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora & Arch; rtl8187 driver (B)

* '''Buffalo'''
** USB ID: 0411:01A2 WLI-UC-GNM - Tested on Raspbmc; rt2800usb driver

* '''Conrad'''
** WLAN Stick N150 mini. Works out of the box in OpenELEC, [http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/ requires firmware-realtek and r8712u kernel module on Debian].
** WLAN Stick N150 Nano [Realtek RTL8188CUS]. Requires a powered USB hub. See Micronet SP907NS for installation instructions and script.

* '''DIGICOM'''
** USBWAVE54 [chipset Zydas ZD1211] . [[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/UsbWave54]] Works out of the box in OpenELEC. With Raspbian or Debian squeezy/wheezy works with zd1211-firmware .
** USBWAVE300C [chipset Ralink 2870] . [[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/UsbWave300c]] Works out of the box in OpenELEC. With Raspbian or Debian squeezy/wheezy works with firmware-ralink .

* '''D-Link'''
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository. (However I experience total crashes on raspbian 2012-07-15 after a few minutes of load on the wlan. Will have to investigate via serial console.)
** AirPlus G DWL-G122 (rev. C). USB ID 07d1:3c03, Ralink RT2571. Working out-of-the-box on Arch image from 2012-04-29.
** AirPlus G DWL-G122 (rev. B1). USB ID 2001:3c00, Ralink RT2571. Working out-of-the-box on Arch image from 2012-06-13.
** DWA-110 (Version A1). Requires the ralink package from the non-free repository on Debian.
** DWA-123 (Version A1). USB ID 2001:3c17, Ralink RT2800. Working out-of-the-box on Arch image from 2012-04-29.
** DWA-131 USB ID 07d1:3303,Realtek RTL8192SU, 802.11n Wireless N Nano. Works out of the box on Raspbian “wheezy”. Verified with direct USB : no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd : wicd is a gui interface on LXDE for network configuration. Install it using command-line : <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.
** DWA-140 (Version B1). USB ID 07d1:3c09, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository.
** DWA-140 (Version B2). USB ID 07d1:3c0a, Ralink RT3072. Workaround for faulty firmware binary: Place file rt2870.bin from [https://launchpad.net/ubuntu/oneiric/+source/linux-firmware/1.53/+files/linux-firmware_1.53.tar.gz linux-firmware_1.53.tar.gz] in /lib/firmware. [https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/770232 Explanation].
** DWA-160 (Version B1). USB ID 07d1:3c11, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository.
** DWA-160 (Version A2). USB ID 07d1:3a09, Atheros AR9170. (NOTE: I can only get it to work through powered USB hub) requires carl9170-fw firmware [http://http://aur.archlinux.org/packages.php/packages.php?ID=44102]

* '''Edimax'''
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP ([http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html howto]) (B) - [http://dl.dropbox.com/u/80256631/8192cu-latest.tar.gz Alternative driver download link that works with Raspian]
** The EW-7811Un can be powered directly from the Raspberry Pi if the Raspberry Pi is powered using a well regulated power supply.
** A script-based installation for the [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] by MrEngman can be found [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6256&hilit=edimax on the RasPi forums]. Tested with Debian Squeeze and Raspbian. [http://dl.dropbox.com/u/80256631/install-rtl8188cus.txt An installation guide can be found here.]
** Instructions for getting the [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] working in Raspbmc (tested RC3) can be found [http://forum.stmlabs.com/showthread.php?tid=780 here].
** Simple step-by-step instructions for [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] which uses the RTL8192 chipset [[RPi_edimax_EW-7811Un]](B)
** [http://www.edimax.com/en/produce_detail.php?pd_id=8&pl1_id=1&pl2_id=44 EW-7318USg] USB ID 148f:2573, rt73usb. RT2573 chipset. Works with powered usb-hub or shorted polyfuses.

* '''edup'''
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS wifi adapter]] USB ID: 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter. Driver is the RT2800USB module, I had to install the firmware as rt2870.bin in /lib/firmware.([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from wheezy]) (B)
** [http://www.szedup.com/show.aspx?id=1681 edup nano EP-N8508] Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for debian. Requires powered USB hub for adequate power. When directly powered by Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or recieved the audio get disorted.

* '''EnGenius'''
** EUB9603 EXT - Realtek r8712u driver

* '''Gigabyte'''
** Gigabyte GN-WB32L 802.11n USB WLAN Card. Works with the rt2800usb driver.

* '''GMYLE'''
** Wireless 11n USB Adapter. Uses RTL8188CUS chipset - cheap on eBay. Installs and works using the install-rtl8188cus-latest.sh script.

* '''IOGear'''
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian Squeeze and install firmware-realtek from non-free squeeze repo. No need to download firmware when using Debian Wheezy (B)

* '''Linksys'''
** Linksys (Cisco) WUSB100 ver.2 1737:0078, tested on raspbian; follow [http://www.brucalipto.org/linux/the-raspberry-diary-wusb100-wireless-n/ Brucalipto.org] instructions; not stress tested but works without issues for light network load.
** Linksys (Cisco) WUSB600N, test on raspbian, details [http://elibtronic.ca/content/20120731/raspberry-pi-part-1-wifi-support here]

* '''Micronet'''
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into R-Pi USB (B) [http://dl.dropbox.com/u/80256631/install-rtl8188cus.txt Debian installation instructions] IMPORTANT: read the instructions first to avoid problems, and [http://dl.dropbox.com/u/80256631/install-rtl8188cus-latest.sh Auto-install script]. The script has been used to install other adapters using the RTL8188CUS chip. [http://dl.dropbox.com/u/80256631/8192cu-latest.tar.gz Updated driver] that handles the latest rpi-updates that kill the original driver, download for manual installation, automatically installed by the Auto-install script.

* '''MSI'''
** 0db0:6861 MSI-6861 802.11g WiFi adapter (US54G): works with external powered USB hub, requires firmware from [http://sourceforge.net/projects/zd1211/files/zd1211-firmware/ here], power management must be disabled: <code>iwconfig wlan0 power off</code>

* '''Netgear'''
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the <code>firmware-atheros</code> package from the <code>squeeze-backports</code> non-free repository (!)
** N150: Some versions reported as Realtek RTL8188CUS device. Read Micronet entry above and use RTL8188CUS script for installation. Works best plugged into powered USB hub.
** WG111v1: Prism54 chipset. Needs powered hub. Follow info for Prism54 chipset on Debian wiki.
** WG111v2: Realtek rtl8187 chipset (!)

* '''OvisLink'''
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink

* '''Patriot Memory'''
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered usb hub.
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module

* '''Ralink'''
** inner 02 joggler wifi usb RT2770F USB-ID 148f:2770 (firmware-ralink required) (only got dhcp on powered hub)
** [http://www.dx.com/p/24688 RT2070] USB-ID 148f:2070 firmware is already loaded into Raspbian. For Debian, the firmware must be installed ([http://wiki.debian.org/rt2870sta instructions]). Needs a powered USB hub.
** [http://www.element14.com/community/docs/DOC-44703 RT2501/RT2573] USB-ID 148f:2573 (firmware-ralink required) (B)
** RT5370 USB-ID 148f:5370 ([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from wheezy]) [[RPi_Ralink_WLAN_devices]](B)

* '''Rosewill'''
** RNX-N180UBE Wireless B/G/N Adapter
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172
*** Tested in Arch, works out of box. USB hub required.
** RNX-G1 Wireless B/G Adapter
*** Realtek RTL8187 chipset, USB-ID 0bda:8187
*** Tested in Arch, works out of box. USB hub required.

* '''Sagem'''
** Sagem Wireless USB stick XG-760N : USB ID 079b:0062, Module is not shipped in Debian image, but can be "sudo apt-get install zd1211-firmware"

* '''Sempre'''
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is shipped in Raspbian image. If you need to build it for other distros, read this: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/

* '''SMC'''
** SMCWUSBS-N : Hardware detected as rt2800 but missing firmware; "sudo apt-get install firmware-ralink" fixed it
** SMCWUSB-G : Gives "couldn't load firmware" error. "sudo apt-get install zd1211-firmware" fixes it.

* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
** Tenda W311U Mini 11N Wireless USB Adapter (USB-ID 148f:3070): Ralink 2870/3070 driver; needs powered hub. [http://blog.modmypi.com/2012/06/installing-tenda-w311u-mini-wireless.html Debian installation instructions]

* '''TP-Link'''
** TL-WN422G v2 (ath9k_htc) Works OOTB in Debian Wheezy Beta. Runs without powered Hub when plugged into running RasPi, but the RasPi won't boot while the stick is plugged in.
** TL-WN721N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw); needs powered USB Hub (B)
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw); needs powered USB Hub (B)
** TL-WN821N v3 (ath9k_htc, htc_7010.fw); works out of the box on ArchLinuxARM and on OpenElec (>r11211), Problems with prior OpenElec; needs powered USB Hub (B)

* '''Widemac'''
** RT5370 Wireless Adapter from [http://www.ebay.co.uk/itm/180887771838?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649 Ebay] runs without powered hub. Follow these [http://elinux.org/RPi_Ralink_WLAN_devices instructions] but go to [http://ftp.de.debian.org/debian/pool/non-free/f/firmware-nonfree/ ftp.de.debian.org/debian/pool/non-free/f/firmware-nonfree/] and pick the latest firmware-ralink_0.xx_all.deb

* '''ZyXEL'''
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)

===Problem USB Wifi Adapters===

These adapters were tested and found to have issues the Raspberry Pi. Note [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6928] as a possible solution/explanation for errors while running LXDE.

* '''Linksys'''
** WUSB300N (Vendor ID: 13B1, Product ID: 0029) - Tested with Raspbian, OpenELEC, among others. No Linux chipset support for Marvell 88W8362 at all.

* '''LogiLink'''
** WL0085 tested under debian (squeeze, wheezy, raspbian); no stable connection can be established. This gets even worse when X is running.

* '''MicroNEXT'''
** MN-WD152B (Debian image) modprobe hangs when plugged in, lsusb hangs. udevd errors in the logs. [http://www.element14.com/community/thread/17632] [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=6737]
*** Possible fix: try the new [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1 Adafruit Occidentalis v0.1] image (based on Raspbian Wheezy) as it includes the needed 8192cu driver builtin to the kernel

* '''Netgear'''
** WNDA3100v2 tested with debian (wheezy); no driver for broadcom chipset (see [http://www.wikidevi.com/wiki/Netgear_WNDA3100v2 http://www.wikidevi.com/wiki/Netgear_WNDA3100v2]).

* '''Realtek'''
** RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)

* '''Trendnet'''
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)

* '''TP-Link'''
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; errors with LXDE running (B)
** TL-WN723N USB ID: 0bda:8176; tested on Arch without a powered hub; it seems to draw too much current.

== USB Bluetooth adapters ==
===Working Bluetooth adapters===
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)
** Tesco own brand 'Technika' Nano Bluetooth Adaptor has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
** http://www.element14.com/community/message/58288
* Asus USB-BT211
** Apparently works with Raspbian.
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962

===Problem Bluetooth adapters===
* '''Belkin'''
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Pi itself is responsive when using directly. On removal of the device everything goes back to normal.
* '''Generic'''
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.

== USB Ethernet adapters ==
===Working Ethernet adapters===
* '''Wintech'''
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100 mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]
* '''LogiLink'''
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.
* '''Apple'''
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.

===Problem Ethernet adapters===
* Axago
** Axago ADE-X1 10/100 Ethernet Adapter (usb: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub.

== USB Sound Cards ==
You will usually want the <code>alsa</code> package for sound. In the Debian image for Raspberry Pi (and possibly other distributions) USB sound cards are prevented from loading as the first sound card, which can be an annoyance if it's the only device you have. To disable this behaviour edit <code>/etc/modprobe.d/alsa-base.conf</code> and comment out the last line; <code>options snd-usb-audio index=-2</code>

* '''Creative'''
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]
* '''Edirol'''
** [http://www.roland.com/products/en/UA-1A/ UA-1A]
* '''Logilink'''
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]

==USB 3G Dongles==
* Huawei E220
* Franklin U600 from Sprint / VirginMobile
** Use usb_modeswitch and vendor 0x1fac and product 0x0150/0x0151
* Digicom Internet Key 7.2 HSUPA '''MU372-L01''' [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MU372L01]
Tested on Raspbian and Archlinux. Detected as 230d:0001. Works with cdc_acm driver. Install usb_modeswitch.
There are 2 "com ports"( /dev/ttyACM0 and /dev/ttyACM1 ) . Tested with Network Manager.Works also perfectly with SAKYS3G [http://www.sakis3g.org/] tools (!! led is always off !!) and wvdial. A working wvdial.conf : http://ubuntuforums.org/showpost.php?p=10361881&postcount=28 . (for example for Vodafone IT , replace Init3 with this : Init3 = AT+CGDCONT=1,"IP","web.omnitel.it" and replace line Modem = /dev/ttyUSB0 with Modem = /dev/ttyACM1 ) and run with wvdial voda .

== USB IR Receivers==
SMK Manufacturing, Inc. eHome Infrared Receiver (Works out of the box with OpenELEC)

== USB Radio devices==
*FM Radio
** ADS InstantFM Music - FM radio tuner works fine under debian.

== USB TV Tuners and DVB devices==
*August
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.
*DVBSky
**[http://dvbsky.eu/Products_S860.html Mystique SaTiX-S2 Sky USB]: Scanning/watching SD and HD works via vdr and streamdev plugin, watching on the Pi directly is laggy as hell. DVB-USB and I2C support must be enabled in the kernel. Needs drivers/firmware from [http://dvbsky.eu/Support.html here].
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Pi itself. Tested with Astra 19.2E radio and SD-TV channels
*Hauppauge
** Hauppauge NOVA-T Stick (Revision 70xxx) DiBcom DiB0700 chipset, requires powered hub.
** Hauppauge NOVA-TD Stick (Revision 52xxx) DiBcom DiB0700 chipset, requires powered hub.
*Generic
** [http://www.onsources.com/product_images/a/757/watch_and_record_digital_tv_dongle__44323_zoom.jpg DVB-T USB Dongle (Silver casing)], based on AF9015 chipset.
** [http://www.electrodepot.fr/media/catalog/product/cache/1/image/500x/9df78eab33525d08d6e5fb8d27136e95/P926993.jpg DVB-T USB Dongle], based on RTL2832 FC12 (HD/SD), IR detected but not tested

== USB Webcams ==

Debian image is missing v4l kernel modules, so video devices are not available. Kernel and firmware upgrade can possibly be used to fix this[http://blog.pixelami.com/2012/06/raspberry-pi-firmware-update-for-debian-squeeze/].

===Working USB Webcams===
*'''Creative'''
**Creative VF0470 Live! (works out of the box on ArchLinux)
**Creative VF0260 Live! Cam Vista IM (works out of the box)
**Webcam Notebook PD1170 (detects, untested)

*'''HP'''
**Webcam HD-2200 [http://www.amazon.com/HP-Webcam-HD-2200-BR384AA-ABA/dp/B004UR9P9Q/ (Amazon)] [http://shopping.hp.com/en_US/home-office/-/products/Electronics/Webcams/BR384AA?HP-HD-2200-Webcam (HP)] [http://www.walmart.com/ip/HP-Webcam-HD-2200/16775645 (Walmart)]
**Webcam HP-3100 - UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and wheezy out of the box

*'''Logitech'''
**Webcam C200
**Webcam C270 (with external power)
**Webcam C310 does not require a powered hub to capture snapshots
**Webcam C510
**Webcam C525 (works fine without powered hub)
**QuickCam Orbit/Sphere USB webcam (ext. power)
**QuickCam Pro 9000 - powered by Raspi, working on debian wheezy
**Webcam Pro 9000 (046d:0809), powered by RPi (measured ~120 mA capturing at ~5 fps), works on Arch

*'''Medion'''
** MD86511 - powered by Raspi, working on Raspbian “wheezy” from 2012-07-15

*'''Microsoft'''
**Xbox Live Vision camera (045e:0294), powered by Raspi, working on Arch
**LifeCam NX-6000 - powered by Raspi, working on debian wheezy
**LifeCam VX-3000, on "raspbian" wheezy (though there do appear to be some issues with image quality and getting partial frames and such, with fswebcam)
**LifeCam VX-800, powered by Raspberry, working out of the box on Raspbian [http://www.amazon.it/Microsoft-JSD-00008-LifeCam-VX-800/dp/B0057FWVSC (Amazon)]

*'''Sony'''
**PlayStation Eye (for PlayStation 3) (the occasional frame is corrupted/stutters when running at 640x480)

*'''Trust'''
** 2MP Auto Focus Webcam (works out of the box on ArchLinux)

===Problem USB Webcams===
*'''Logitech'''
**Webcam Pro 9000 - Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).
**Webcam Pro 4000 - It uses pwc driver which does not work. Maybe it's because of general Raspi USB bug.

*'''Sony'''
**Eye Toy (PlayStation 2) model SLEH 00030 - (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012

*'''Trust'''
**SPACEC@M 200 - (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012

== USB GPS devices ==
*Royaltek
**Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually
*Garmin
**Garmin eTrex Vista HCx: Works but may draw much power. To get it working (software part): https://wiki.openstreetmap.org/wiki/USB_Garmin_on_GNU/Linux
*GlobalSat
**GlobalSat BU-353 Does not require a powered hub, works fine when directly plugged into the RPi. On Raspian, requires the gpsd and gpsd-client packages. For some reason, the gpsd daemon does not always start correctly on boot. You may need to do something like the following to manually restart it: <pre>sudo killall gpsd; sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock</pre>

*Wintec
**WBT-200: No problem on Debian
*Holux
**Holux M-215: Works fine on Arch, uses Silicon Labs CP210x RS232 serial adaptor driver
*Bluenext
**Bluenext BN903S: No problem on Debian image (19-04-2012).

== USB UART adapters ==
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.

*'''FTDI'''
**FT232 chip based adapters work, module ftdi_sio

*Prolific
**PL2303 chip based adaptors works fine on latest Debian tested with minicom and gtkterm

== Other, exotic USB devices ==
=== CAN Bus ===
*PEAK-System (www.peak-system.com)
**PCAN-USB using the driver (kernel module) from http://www.peak-system.com/fileadmin/media/linux/index.htm
=== Home automation ===
*Tellstick (www.telldus.com), installation [[R-Pi_Tellstick_core|instructions]]
**Depends on libftdi1

=== Touch Screen ===
*ACER T230H touch screen [http://support.acer.com/acerpanam/monitor/2009/acer/t230h/t230hnv.shtml]
**USB TS identifies as "Quanta Computer, Inc. Optical dual-touch panel", module hid_quanta
**Seems to draw over 200 mA from USB!
=== Floppy Disk Drive ===
*Samsung USB Floppy Drive SFD-321U/HP
**I suppose a floppy drive might be considered exotic nowadays!
**LSUSB lists it as Samsung Electro-Mechanics Co. Floppy Disk Drive
**Only tried connected to a powered USB hub, as the drive is labelled 5V at 0.5A on a Raspberry Pi running Debian Wheezy.
**tail -f /var/log/syslog looking for mount device when plugged in, came up as SDA in testing.
**sudo mkdir /media/floppy
**sudo mount /dev/sda /media/floppy
**Contents of floppy now available in /media/floppy
**To remove drive, ensure no sessions have the floppy directory as the current working directory.
**sudo umount /media/floppy
=== USB Missile Launcher ===
*USB Missile Launcher / Rocket Launcher sold in UK by Marks and Spencer but also sold under a range of other names.
**USB ID 1130:0202 Tenx Technology, Inc. Use apt-get install pymissile (python code) and there is C code at [http://sourceforge.net/projects/usbmissile/ usbmissile from Source Forge]
=== USB Docking Stations ===
*StarTech USB 3.0 to Dual 2.5"/3.5" SATA HDD Dock (SATDOCK2U3GB)
**This is an externally powered dual sata HDD docking station, which has USB2.0 compatibility with the Pi.
**Tested with latest raspbmc and debian wheezy raspbian, 3.1.9+ #168

== PS2 / AT to USB Converters ==

* Unbranded active converter known as the "blue cube". Based on the Cypress CY7C63723C 8 bit RISC. Please see http://geekhack.org/showwiki.php?title=PS2-to-USB+adapters for more information.
Note that although the adapter might work, PS/2 keyboards were not designed to be low power USB devices, so they might not meet the requirement to work with considerable lowered supply voltage (4.4 volt) provided by the USB ports of the raspberry PI. These keyboards should work when powered by a powered hub.

'''Tested PS2/AT keybords'''

All above tested with the famous "blue cube" on a powered USB hub.

*IBM Model F (please note requires an aditonal AT to PS2 converter)
*Dell AT101w
*Northgate Ominikey Ultra T (please note requires an aditonal AT to PS2 converter)

* 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller
** Working: Ipex RT215KTW PS/2 keyboard
** Not working: HP SK-2502 PS/2 keyboard (gets power but does not init - three LEDs remain permanently lit. Keyboard + Holtek converter work on a Linux PC, although this keyboard doesn't work with some native PS/2 ports.)

== Power adapters ==
The Raspberry Pi uses a standard Micro USB (type B) power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.

===Working power Adapters===
* '''AlcaPower'''
** 5V 2.5A Model AP5A - Charger/switching with 7 connectors(also Microusb)
* '''Ansmann'''
*** Dual USB charger slim, Model-Nr. 1201-0001
* '''Apple'''
** 5V 2.1A USB charger for iPad2, model A1357
** 5V 1.0A USB Charger for iPod
** 5V 1.0A USB Charger for iPhone 4
* '''Amazon'''
** 5V 0.85A USB charger for Kindle
** 5V 2A Mains to USB A adaptor, Branded "CostMad"
* '''Belkin'''
** 5V 2.6A 4 port Ultra-Slim Desktop hub (Model F4U040) (RPi running from USB Hub port)
** 5V 2.5A 4 port USB Hub (Model F5U404) (RPi running from USB Hub port)
** 5V 3.5A 7 port USB Hub (Model F5U706) (RPi running from USB Hub port)
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)
** Universal USB Wall Charger (5V 1A) (Model F8Z222uk)
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** Charger for Tour 9630
** 5V 0.7A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
** 5v 750mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)
** 5v 750mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)
* '''Dell'''
** USB Hub integrated in Dell monitors (B)
* '''Garmin'''
** 5V 1A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6ft cable (F3U151B06) works.
* '''Griffin'''
** Power Block Model P2417. 5V 2.1A
** Power Block Model P1190R2 Two USB 5V Outputs, 1Amp each
* '''Hama'''
** 1000mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)
* '''HP'''
** 5.3V 2A Charger for HP Touchpad (B)
* '''HTC'''
** 5V 1A TCP-300 USB phone charger (B)
** 5V 1A TC B250 USB charger (HTC R/N: 79H00096-00M)
** 5V 1A TC E250 USB charger (HTC R/N: 79H00098-02M)
* '''i-box (Philex Electronic Ltd)'''
** 5V 1A USB charger, 1 USB socket, no USB lead supplied, Model: 76971HS/02 (available from ASDA and others in the UK) (B).
* '''IDAPT'''
** [http://www.idaptweb.com/universal_chargers/i4/ i4 multi device charger] - 3 interchangeable device tips + USB A socket ([https://twitter.com/andrewmk/status/226057302879375361 see it in use])
* '''Innergie'''
**15W Dual USB Adapter. Model: mMini AC15. Output: 5V, 3A (max per port), 15W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Spec Sheet]
* '''Kodak'''
** 5V 1A TESA5G1-0501200
* '''LG'''
** 4.8V 1A Travel Adapter
**5.1V .7A Travel Adapter (Model: STA-U34WVI)
* '''Logic'''
** 4 port USB Hub (Model LP4HUB10). (RPi running from USB Hub port, red power line (+5v) inside hub cut) (B)
*'''LogiLink'''
**5V 2.1A Switching power supply, model PA0040 (B)
* '''Logitech'''
** 5V 1A SDC115-USB Remote Control Charger and cable
* '''Maplin Electronics'''
** 5V 1A dual USB power supply, model number H25B-MT-K2
** Micro USB Power Supply N19HX
* '''Medion'''
** 5V 1A USB power supply for OYO ebook reader
* '''Motorola'''
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5V 0.85A SPN5504 Charger with Cable]
* '''Nokia'''
** 5V 1.2A AC-10E Charger
* '''Noname'''
** 5V 2.1A KMS-AC09 4 port USB charger (B) [http://www.miniinthebox.com/kms-ac09-universal-ac-adapter-for-ipad-ipad-2-iphone-white_p208568.html]
** 5.2V 1A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]
* '''Novatel Wireless'''
** 5V 1.05A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5V 0.7A Charger for Orange San Francisco
* '''Palm'''
** 5V 1A Charger for Palm Pixi+ (B)
* '''Pantech'''
** 5.0V 1A CNR USB with LG DLC100 micro usb cable
* '''Phihong'''
** Switching Power Supply. Model: PSAC09R-050. Output: 5V, 1.8A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
* '''PortaPow'''
** PortaPow UK Mains Wall Power Supply
* '''RS Components'
** HNP06UK (RS 7263069) Switching Adapter 5.0V 1200mA
* '''Samsung'''
** 5V 0.7A Charger for Galaxy S model ETA0U10EBE
** 5V 0.7A Charger for Galaxy SII
** 5V 0.7A Charger for Galaxy S Vibrant (SGH-T959)
* '''Sony Ericsson'''
** 5V 0.7A Charger CST-80
* '''Travel Charger'''
** 5V 2.0A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]
* '''Technika'''
** 5V 1A USB Power Adapter, model MPASS01 (B)
* '''TrendingUK'''
** Micro USB Power Supply for the Raspberry Pi. 5V 1000mA (from [http://www.trendinguk.co.uk/micro-usb-power-supply-for-the-raspberry-pi.html TrendingUK ]) (also from [http://www.ebay.co.uk/itm/330757401271 eBay ])
** Can also power from 7 Port USB 2.0 Powered HUB for Raspberry Pi with 3A Power Supply
* '''Trisonic'''
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5V, 800mA) $3 at Daiso U.S. stores.
* '''TruePower'''
** [http://u-socket.com/ U-Socket] 5V 2.1A AC Receptacle with Built-in USB ports (2.1A per USB port) model ACE-7169
* '''Voltcraft'''
** SPS5-12W, 2500 mA, requires additional USB <-> miniUSB adapter/cable, works perfectly (bought from [http://www.conrad.de/ce/de/product/512660/VOLTCRAFT-SPS5-12W-Steckernetzteil-Steckernetzgeraet-5-VDC-2500-mA-12-Watt Conrad Shop])

===Problem power Adapters===
* '''Masterplug'''
** Masterplug Surge Protected USB Adaptor 2 x 1A USB Polished Black - USB ports and ethernet don't work with this adapter and some screen artefacts using HDMI.
* '''Monoprice'''
** 5v, 2A 3 Outlet Power Surge Protector Wall Tap w/ 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot. Measured less than 4.75v between TP1 and TP2 when used with a Monoprice cable.

===External Battery packs (with 5V regulated output)===
* '''Anker Astro3'''
** Anker Astro3 10000mAh with Dual 2A USB Output
* '''Duracell'''
** PPS2 Instant USB Charger
* '''Energizer/XPAL'''
** XP18000 18000mAh Power Pack
* '''Generic - eBay no brand'''
** 6000T Pocket Power 5000mAh - eBay item 271009959140
** Power Bank for iPad/iPhone 5000mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938
* '''New Trent'''
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)
* '''Sinoele'''
** Movpower - Power Bank 5200mAh (8hrs with Wifi active)
* '''TeckNet'''
** iEP387 Dual-Port 7000mAh External Power Bank (The charging lead can be used to connect the Tecknet to the RPi. Ran the RPi with wifi dongle and wireless keyboard receiver for over 9 hours of light use.)
** iEP392 Dual-Port 12000mAh External Power Bank (1A port, ~16.5 hours)
** Rayovac PS60 5v 800mAh

== Display adapters ==
Note that active converter boxes may draw power through the HDMI port, and thus will put an extra load on your PSU, and also increase the current running through the PI's primary input fuse. HDMI ports (and the raspberry PI) are designed so that they deliver a very limited amount of power (50mA) to the TV/Monitor/display-adapter and much more isn't in theory allowed. In fact there is a diode (D1) in series with the power line which can only handle 200mA, if the adapter tries to draw much more than that the diode might fail. Therefore only externally powered adapters are to be recommended. Despite this, many people report success with these high powered devices.

===HDMI->DVI-D===
There are three kinds of DVI. There is DVI-D, a digital signal fully compatible with HDMI, so a passive cable can be used. There is DVI-I, which is a connector with both analog pins and digital pins. An HDMI to DVI-D adapter fits in a DVI-I female connector. Finally, there is DVI-A. This a fairly rare connection, but occasionally it will be found on some monitors and is an analog interface, in fact the same as VGA!

Some adapters like Farnell part AK-CBHD03-BK are HDMI to DVI-I, which, while not fitting in a DVI-D monitor, are still compatible. The analog pins simply must be bent.

The HDMI to DVI-D cable provided by Apple with the 2010 Mac Mini worked. It does not appear this adapter can be purchased separately.

* AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.

===HDMI->VGA converter boxes===
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.

http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the RasPi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1A max forward current, much greater than the BAT54's 200 mA limit which may be exceeded by your HDMI -> VGA converter. Remember that the converter's current must come from your RasPi power supply and go through the Micro USB cable and polyfuse F3, so you may get extra voltage drops and/or cause F3 to trip depending on how much current the converter uses. As always with board modifications, YMMV. Also on the "Burning Raspberry!" thread, user "pwinwood" reported the Neewer's current to be 400 mA, which is twice the limit of BAT54 diode D1. "pwinwood" also took the Neewer apart and added its own +5V connection adapted from a USB cable, which bypasses RasPi's Micro USB cable and polyfuse F3.

http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA

http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.

This adapter -- http://www.ebay.co.uk/itm/300692770623 -- works from 640x480 up to 1920x1080, audio over HDMI works too.
Sadly the IC's on the PCB have all been scrubbed.
Requires HDMI boost and overscan, [[RPi_config.txt|config.txt]] settings for 640x480@60Hz:
 hdmi_drive=2
 hdmi_group=2
 hdmi_mode=4
 config_hdmi_boost=4
 overscan_top=-30
 overscan_bottom=-30
 overscan_left=-30
 overscan_right=-30

According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.
The [[RPi_config.txt|config.txt]] settings used are:
 hdmi_drive=2
 hdmi_group=2
 hdmi_mode=36
 disable_overscan=1

According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but are very pricey compared to alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4A, which is too much draw for the 5V supply available from the HDMI socket on the Raspberry Pi. Its power LED lights, but no picture is produced. In comparison to the HDFuryPro this picture from this device is sharper, but not enough to justify the extra cost.
The [[RPi_config.txt|config.txt]] settings used are:
 hdmi_drive=2
 hdmi_group=2
 hdmi_mode=36
 disable_overscan=1

http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"

Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):
 hdmi_drive=2
 hdmi_group=2
 hdmi_mode=16
 hdmi_force_hotplug=1
 disable_overscan=0

And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. Very cheap but works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC).
The /opt/vc/bin/tvservice is able to read monitor edid data. I tested the adapter using NEC 72VM 15" LCD. (1280x1024 60Hz, 1024x768 60Hz, 640x480 works) The adapter is based on Lontium LT8511A chip, but I was unable to get the spec for it.
The D1 diode is getting very hot though. Most likely the adapter drives more than 200mA. The standard RS Components 1,2A usb power supply is able to provide enough power for the RPi and the adapter. I'll try to modify the adapter to connect external power to bypass D1.
Marcin.

===DVI-D -> VGA active adapters===
None are currently listed

===Composite->SCART===
SCART adapters (SCART plugs with three RCA connectors in the back), will probably work when used with the yellow RCA plug connected to the R-PI's RCA video output. Additionally using a splitter cable (3.5mm jack plug on one end, and red-white RCA plugs on the other end) will probably work when plugged into the red and white (left and right audio channels) of the SCART adapter.

* Generic - works

===Composite->VGA converter boxes===
* [http://www.extron.com/product/product.aspx?id=dvs204| Extron DVS-204] - works no problem!

== SD cards ==

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.)
For this reason, please specify product numbers in the lists below, when possible.

You can also attach the following fields from your card's CID :
<pre>
cd /sys/class/mmc_host/mmc?/mmc?:*
echo "man:$(cat manfid) oem:$(cat oemid) name:$(cat name) hwrev:$(cat hwrev) fwrev:$(cat fwrev)"
</pre>

please merge with http://elinux.org/RPi_Performance#SD_card

===Working SD Cards===
* '''7DAYSHOP.COM'''
** 8GB Professional SDHC Class 10 (man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0)
* '''Adata'''
** 2GB SD Class 2 Speedy (8B0947 printed on back) This card works with every distro I tried. May be old, may not be the fastest, but is very stable.
** 8GB SDHC Class 2 (MMB3F08GWMCA-GE)
** 8GB SDHC Class 4 (MicroSD w/ adapter)
** 8GB SDHC Class 6 (MMAGR08GUDCA-DB)
** 8GB SDHC Class 10 (AUSDH8GCL10-R)
** 8GB SDHC Class 10 (ASDH8GCL10-R) Tested on 2012-06-18-wheezy-beta.zip
** 8GB SDHC Class 10 (P-SDH8G10-EC from BJ's USA tested on Raspbian)
** 16GB SDHC Class 6
** 16GB SDHC Class 10 (16GSDHC10)
** 16GB SDHC Class 10 (microSD w/ adapter AUSDH16GCL10-RA1)
** 32GB SDHC Class 10 (ASDH32GCL10-R) Tested on wheezy-beta with latest kernel and firmware and raspbian wheezy
* '''AmazonBasics'''
** [http://www.amazon.com/AmazonBasics-SDHC-Class-Secure-Digital/dp/B0058GH0LS 8GB SDHC Class 10 B0058GH0LS]
** [http://www.amazon.com/AmazonBasics-SDHC-Class-Secure-Digital/dp/B0058GH1IK 16GB SDHC Class 10 B0058GH1IK]
** 32GB SDHC Class 10
* '''Apacer'''
** 8GB microSDHC Class 10 (with adapter)
** 8GB SDHC Class 6
* '''Centon'''
** 16GB SDHC Class 4 (1447 printed on back)
* '''CnMemory'''
** 8GB SDHC Class 4 (Silver/Black label says 'High Capacity Card') 84209_8GB_SDHC, bought from Maplins. No error messages seen, but operation is much slower than with a SanDisk 4GB Class 4 card.
* '''Dane-Elec'''
** 16GB SDHC Class 4
** 16GB Pro 200X Class 10 DEMS16GB2683ENBA
* '''Dikom'''
** 16GB SDHC Class 10 (serial 207H3MD016IBSD)
* '''Duracell'''
** 4GB SDHC Class 4
** 16GB SDHC Class 10 (labelled Pro Photo 200x)
** 32GB SDHC Class 10 (man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0) (~4.6MB/s read, ~4.4MB/s write on debian6-19-04-2012, following [[RPi_Performance#SD_card]])
* '''Emtec'''
** 2GB SD man:0x000027 oem:0x5048 name:SD02G hwrev:0x2 fwrev:0x0
** 16GB SDHC Class 10 (EKMSD16G150XHC) (less than half as fast as Sandisk 16gb Class 10)
* '''Extrememory'''
** 16GB SDHC Class 10 (man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0)
** 32GB SDHC Class 10 (man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0)
* '''Fugi'''
** 32GB SDHC Class 10 (P10NM00580A) (man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0)
* '''Hama'''
** 2GB SD Class 2
** 8GB SDHC High Speed Pro Class 6
* '''Hema (Dutch dept. store)'''
** 4GB
** 8GB SDHC Class 4
* '''Goodram'''
** 8GB microSDHC Class 4
** 16GB microSDHC Class 4 (SDU16GHCAGRR10)
** 16GB SDHC Class 10
* '''HP'''
** 8GB SDHC Class 4 (doesn't reboot during first time startup process, but restart again and fine after that).
** [http://www.amazon.com/HP-CG790A-AZ-Flash-Memory-Class/dp/B007X7U224 32GB SDHC Class 10]
* '''ICIDU'''
** 4GB SDHC Class 10 (also had no issues)
** 16GB SDHC Class 10 (image write had issues, might be my inexperience. It boots & shows Xserver)
** 32GB SDHC Class 10 (had no issues whatsoever, the comment above might be a dud.)
** 8GB microSDHC Class 10
** 16GB microSDHC Class 10 (20MB/sec)
** 32GB microSDHC Class 10 (20MB/sec)
* '''Integral'''
** 4GB SDHC Ultima Pro Class 10
** 8GB SDHC Ultima Pro Class 6 (Works - initial error -110 but boots within 5 seconds with no further errors or issues)
** 8GB SDHC Ultima Pro Class 10 (20MB/s) (Works - initial error -110 but boots within 5 seconds with no further errors or issues)
** 16GB SDHC Ultima Pro Class 6
** [http://www.amazon.co.uk/gp/product/B0047T6XME 16GB SDHC Class 10 Ultima Pro (20MB/s)]
* '''Joyflash'''
** 16GB SDHC Class 10 (LTSD1112016GB)
* '''Kingmax'''
** 4GB SDHC Class 2
** 4GB microSDHC Class 4 (KM04GMCSDHC4) won`t reboot when it`s hot
** 8GB microSDHC Class 4 (KM08GMCSDHC41A) won`t reboot when it`s hot
* '''Kingston'''
** 2GB SD
** 2GB microSD (N0185-002.A00LF) + Adapter (File system .img written via Transcend microSDHC "USB stick-like" adapter - P3-102510)
** 4GB microSD Class 4
** 4GB SDHC Class 4 (SD4/4GB)
** [http://img341.imageshack.us/img341/1619/dsc0253y.jpg 8GB SDHC Class 4] ([http://img833.imageshack.us/img833/2028/dsc0254br.jpg SD4/8GB]) (does not work with current build of raspbmc)
** [http://img600.imageshack.us/img600/3849/dsc0251et.jpg 8GB microSDHC Class 4] ([http://img707.imageshack.us/img707/363/dsc0252ld.jpg SDC4/8GB])
** 8GB SDHC Class 6 (SD6/8GB) (errors on boot, boots Debian ok, does not work with raspbmc rc2)
** 8GB SDHC Class 10 (SD10G2/8GB, SD10V/8GB, ultimateX 100X, ultimateX 120X)
** 16GB SDHC Class 4 (SD4/16GB)
** 16GB microSDHC Class 10 (SDC10/16GB)
** 16GB SDHC Class 10 (SD10G2/16GB, ultimateX 100X)
** 16GB SDHC Class 10 (SD4/16GBET)
** 32GB SDHC Class 10 (SD10V)
** 32GB SDHC Class 10 (SD10G2/32GB, ultimateX 100X)
* '''Kodak'''
** 4GB SDHC Class 2
** 8GB SDHC Class 4
* '''Kruidvat'''
** 8GB SDHC Class 4
* '''Lexar'''
** 4GB SDHC Class 4 (Boots consistently and no error messages in log after 1/2 hour use ) (works with Raspbmc)
** 4GB SDHC Class 6 Platinum II (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])
** 8GB SDHC Class 4
** 8GB SDHC Class 6 Premium Series
** 8GB SDHC Class 6 Platinum II
** 16GB SDHC Class 6 Platinum II
** 32GB microSDHC HIGH-SPEED Class 10 (from [http://www.amazon.co.uk/Lexar-32GB-Micro-Speed-Reader/dp/B004BR2ZTM Amazon])
** 128GB SDXC UHS-I Card LSD128CTBNA400 (from [http://www.amazon.com/gp/product/B007BZRXK2 Amazon])
* '''Master'''
** 16GB SDHC Class 10 [man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0]
* '''Medion'''
** 8GB Class 4 SDHC UK sourced (Aldi)
* '''Microcenter Brand (sold in bins at checkout)'''
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349729 16GB SDHC Class 10]
* '''Mushkin'''
** 16GB SDHC Class 10 (MKNSDHCU1-16GB) [http://www.newegg.com/Product/Product.aspx?Item=N82E16820226324]
** 32GB SDHC Class 10 (MKNSDHCC10-32GB) [http://www.newegg.com/Product/Product.aspx?Item=N82E16820226235]
* '''Mustang'''
** [http://www.mustang-flash.de/Products/Flash%20Products/Secure%20Digital/SD-Card/8GB%20Mustang%20SDHC%20Card%20LeMans%2C%20Class%2010%2C%20Retail|SD8GHCCL10MU-R.html 8GB SDHC Class 10]
* '''MyMemory'''
** 8GB SDHC Class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10] (Latest batch not working)
** 16GB SDHC Class 10 (MYMESDH16G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-16GB-SD-Card-(SDHC)---Class-10]
* '''OCZ'''
** 8GB SDHC Class 6 Gold Series (08110596-8GB-6) tested with Debian Squeeze (official Raspberry Pi distribution debian6-19-04-2012.zip)
* '''Optima'''
** 8GB SDHC Class 10 (Pro-Speed)
* '''Panasonic'''
** 4GB SDHC Class 4
** 4GB SDHC Class 10 UHS-I (~11.2MB/s read, ~6.2MB/s write, following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 2 (~11.1MB/s read, ~9.7MB/s write, following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])
* '''Patriot'''
** 8GB SDHC Class 6 (PSF8GSDHC10-PC)
** 8GB SDHC Class 10 LX Series (PSF8GSDHC10-PC1)
** 16GB SDHC Class 10 (PSF16GMCSDHC10)
** 16GB SDHC Class 10 LX Series (PSF16GSDHC10) (19.3MB/s read, 9.3MB/s write)
** 16GB microSDHC Class 10 (PSF16GMSHC10) (requires recent kernel update for boot)
** 32GB SDHC Class 10 (PSF32GSDHC10)
** 32GB SDHC Class 10 UHS-1 (PEF32GSDHC10U1) (20.4MB/s read, 12.1MB/s write)
* '''Peak'''
** 4GB microSDHC Class 4 (MMBTR04GUBCA-ME) tested with Arch
* '''Philips'''
** 8GB SDHC Class 4 (FM08SD35B)
* '''Platinum'''
** 4GB SDHC Class 6
** 8GB SDHC Class 6 (man:0x00006f oem:0x0000 name:SMI hwrev:0x1 fwrev:0x0)
** 64GB SDCX Class 10
* '''Play.com'''
** 4GB SDHC Class 6 (S4E3CD04GEFAA 0907090121106)
* '''PNY'''
** 4GB SDHC Class 4
** 4GB SDHC Class 4 Optima (SD-K04G 0834TT1297Y)
** 4GB SDHC Class 4. Micro SD Card with adapter.
** 8GB SDHC Class 6
** 8GB SDHC Class 10. Micro SD card with adapter.
** 16GB SDHC Class 4
** 16GB SDHC Class 10 (P-SDHC16G10-GE)
*** See the note for P-SDHC16G10-EF. Works with Wheezy, does not work with Squeeze, Arch, or Fedora Remix.
** 16GB SDHC Class 10 (P-SDHC16G10-EF)
*** Works with [http://www.raspberrypi.org/archives/1435 Debian Wheezy]
*** Does not work with Debian Squeeze (debian6-19-04-2012: mmc0: timeout waiting for hardware interrupt).
*** Does not work with Arch Linux Arm (archlinuxarm-29-04-2012: no video is displayed, solid red power light, tiny green light)
** 16GB SDHC Class 10 Pro-Elite (P-SDH16U1-30-GE). Works with raspbmc, haven't tested others.
* '''pqi'''
** 8GB SDHC Class 6
*** Works with official debian6-19-04-2012
* '''PRETEC'''
** 8GB SDHC Class 10 (8DK52-122ME)
* '''Samsung'''
** 4GB SDHC
** 8GB SDHC Class 6 (MB-SS8GAEU)
** 8GB SDHC Class 10 (MB-MP8GA, MB-SP8GA/EU, MB-SP8GA/AM)
** 16GB SDHC Class 6 (MB-SSAGAEU)
** 16GB SDHC Class 10 (MB-SPAGA aka MB-SPAGAEU)
** 32GB SDHC Class 10 (MB-SSBGA, MBSSBGVEOBGA-SH) fine with [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=50&t=8071 Debian Wheezy], but does not work with Debian Squeeze (debian6-19-04-2012: mmc0: timeout waiting for hardware interrupt).
* '''SanDisk'''
** 2GB SD, white "SanDisk for Wii" branded, no class mentioned
** 2GB SD (with a circle 2 --probably class 2), writes at 3.5 Mb/s
** 2GB SD Class 2 (BE0816113150D)
** 2GB SD Class 4 Ultra (15MB/s)
** 2GB SD Class 4 Ultra II
** 2GB SD Ultra II (BE0719111366D)
** 2GB SD Extreme III (BE0715105083B)
** 2GB SD Extreme III (BE0804212046D) - 20MB/s - Class 6
** 4GB SDHC Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/4gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** 4GB SDHC Class 4 (SDSDB-004G-B35)
** 4GB SDHC Class 4 (SDSDB-004G-BT35). Confirmed working with stock debian6-19-04-2012.img
** 4GB SDHC Class 4 (BH1210821913G)
** 4GB SDHC Class 4 (SDSDH2-004G-AC11, BH1127216239D) Costco 2-pack, booting Wheezy 2012-07-15
** 4GB SDHC Class 4 Ultra (SDSDH-004G-U46) won`t reboot when it`s hot
** 4GB SDHC Class 4 Ultra II
** 4GB SDHC Class 6 Ultra (30MB/s BH1200421822D)
** 4GB SDHC Class 6 Ultra (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)
** 4GB SDHC Class 10 Extreme (BH10297143382G)
** 8GB SDHC Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/8gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** 8GB SDHC Class 4 (writes at ~1.5MB/s)
** 8GB SDHC Class 4 Ultra labelled as 15MB/s (BI1024716014G)
** 8GB SDHC Class 6 Ultra
** 8GB SDHC Class 6 micro - MMAGR08GUDCA-DB
*** also SDSDH-008G-U46 - BI1131222083D see [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=88625#p88625 update from andrew.blake]
*** except SDSRH-008G-A11 could be problematic, see below
** 8GB SDHC Class 6 Ultra labelled as 20MB/s (BI11321422083D)
** 8GB SDHC-I Class 6 Ultra labelled as 30MB/s (SDSDH2-008G-AC11)
*** requires updated Squeeze or Wheezy beta
** 8GB SDHC Class 10 Extreme (BI11017514367G)
** 8GB SDHC Class 10 Extreme (B11209116254G) - Managed to get it working with raspbian R3 [http://archive.raspbian.org/images/rpi_pisces_r3.zip rpi_pisces_r3.zip] however does not work with official squeeze nor Arch linux.
** 8GB SDHC Class 10 Extreme (30MB/s HD Video) - working with new [https://github.com/raspberrypi/firmware/blob/9308c7ed387e5422883753f7fb71a75506abd1f8/boot/bootcode.bin bootcode.bin]. Confirmed on 2012-07-10 for Debian Squeeze 2012-04-19 and Arch Linux 2012-06-13 images (BI1130916254G).
** 8GB SDHC Class 10 Ultra(30MB/s) (SDSDU-008G-U46) - Works with stock debian6-19-04-2012 or raspbian images but not with OpenELEC r11212 (works with OpenELEC r11493)
** 8GB SDHC Class 10 Extreme Pro (95MB/s UHS-I) (SDSDXPA-008G-X46) - Works with stock 2012-07-15-wheezy-raspbian
** 16GB SDHC Class 4
** 16GB SDHC Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/16gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** 16GB SDGC Class 4 (SDSDB-016G-B35) - working with [https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin bootcode.bin]. Confirmed on 2012-07-15 for Debian Squeeze 2012-04-19
** 16GB SDHC Class 6 Ultra (30MB/s) (BL1133921933G) - Work with OpenELEC r11324
** 16GB SDHC Class 10 Ultra(30MB/s) (SDSDU-016G-U46) - Work with stock debian6-19-04-2012 image. Gave Kernel Panic with stock debian6-19-04-2012 image. Worked fine with Wheezy image.
** 16GB SDHC Class 10 Extreme (30MB/s HD Video) (SDSDX3-016G-X46) - Works with 2012-06-18-wheezy-beta.img and updated firmware (tested 2012-07-02)
** 32GB SDHC Class 10 Ultra (30MB/s) - Works with stock debian6-19-04-2012 image
** 16GB SDHC Class 10 Extreme (45MB/s U1) (BL1203322025G) - Doesn't work with stock debian6-19-04-2012 image, but does work with freshly compiled kernel
** 16GB SDHC Class 10 Extreme Pro (95MB/s UHS-I) (SDSDXPA-016G-A75) - Doesn't work with stock debian6-19-04-2012 image, but does work with freshly compiled kernel
** 32GB SDHC Class 4
** 32GB SDHC Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/32gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** 32GB SDHC Class 6
** 32GB SDHC Class 10 Extreme (45 MB/s UHS-I) (SDSDX-032G-X46) - works with arch-04-29-image and latest firmware (booting problems without firmware update)
** 64GB SDXC Class 10 Extreme (45 MB/s UHS-I) (SDSDX-064G-X46) - works with 2012-07-15-wheezy-raspbian
** 4GB microSDHC Class 2
** 4GB microSDHC Class 4
** 8GB microSDHC Class 2
** 8GB microSDHC Class 4
** 8GB microSDHC Class 6 Mobile Ultra (SDSDQY-008G-U46A) working with the latest firmware, won`t reboot when it`s hot
** 32GB microSDHC Class 4 (SDSDQM-032G-B35)
** [http://img217.imageshack.us/img217/6435/dsc0255uc.jpg 64GB microSDXC Class 6 Mobile Ultra] (SDSDQY-064G-A11A) (boots up much more consistently with latest firmware)
* '''Silicon Power'''
** 4GB microSDHC Class 6 (SP004GBSTH006V10-SP)
** 16GB microSDHC Class 10 (SP016GBSDH010V10)
* '''Sony'''
** 4GB SDHC Class 4 (SF-4B4) (Write 6MB/s, Read 20MB/s)
** 4GB SDHC Class 4 (SF-4N4)
** 8GB SDHC Class 4 (Write 11.8MB/s, Read 17.4MB/s)
** [http://store.sony.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=10551&storeId=10151&langId=-1&partNumber=SF32NX/TQ#features 32GB SDHC Class 10 (SF-32NX/TQ)] (Max read speed of ~94MB/s, min write speed of ~10MB/s) - Works with archlinuxarm-29-04-2012 dd image with latest firmware update (as of 10-06-2012)
* '''Strontium'''
** 8GB SDHC Class 10 (SD-T08G 1045 US6923 G (White Shell - SKU 8 886450 703492))
* '''Super Talent'''
** 32GB Secure Digital High Capacity SDHC Card (Class 10), Model SDHC32-C10 SKU: 116-557-001 (works with Raspbmc RC4 and 2012-07-15-wheezy-raspbian))
* '''TakeMS'''
** 4GB microSDHC Class 4 (with adapter) [http://www.takems.com/products.php?categ=flash&prod=Micro_SDHC-Card Micro SDHC Class 4 + 1 Adapter(Order No.88662)]
* '''TDK'''
** 4GB SDHC Class 4 (1008WW5261B)
** 4GB SDHC Class 4 (80-56-10275-004G,Debian works '''BUT''' mmc0 errors when booting Fedora)
** 4GB microSDHC Class 4 (80-56-10301-004G)
** 4GB SDHC Class 6 (S404G1113) - Works with Debian Wheezy (2012-06-18 beta), not tried latest OpenELEC yet.
** 8GB SDHC Class 10 - Works with Raspbian 2012-07-15
** Sandisk 64GB Class 10 Ultra SDXC UHS-I FFP (3A114807)

* '''Toshiba'''
** 8GB mircoSDHC SD-C08GJ(BL3A
* '''Transcend'''
** 4GB SDHC Class 4 - we've found these to work without any errors and offer reasonable performance
** 4GB SDHC Class 4 (TS4GSDHC4 - BH1130821915G)
** 4GB SDHC Class 6 (TS4GSDHC6) - no problems. (does not work with Raspbmc as of 6/1/12)
** 4GB SDHC Class 10 (TS4GSDHC10E)
** [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-(SDHC)---Class-4 8GB SDHC Class 4] (TS8GSDHC4) (man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0) - works with both Debian "squeezy" and Raspbian "wheezy" distributions.
** 8GB SDHC Class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)
** 8GB SDHC Class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]
** 16GB SDHC Class 6 (TS16GSDHC6)
** 16GB SDHC Class 10 (TS16GSDHC10)(TS16GSDHC10E)
** [http://www.transcend.com.es/tarjetas-de-memoria/sd-sdhc/32gb-sdhc-class-10 32GB SDHC Class 10] (TS32GSDHC10)(TS32GSDHC10E)
** 64GB SDXC Class 10 (TS64GSDXC10)
* '''Verbatim'''
** 8GB SDHC Class 10 (43961)
** 16GB SDHC Class 10 (43962)
** 32GB SDHC Class 6 (44032)

*'''Traveler'''
**4GB High Speed Memory Card - no class mentioned. No problems. Tested with Raspbian.

* '''TrendingUK'''
** Sandisk 4GB Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/4gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** Sandisk 8GB Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/8gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])
** Sandisk 16GB Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/16gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ]
** Sandisk 32GB Class 4 - Preinstalled with Raspbian Wheezy Linux. (from [http://www.trendinguk.co.uk/32gb-sandisk-sdhc-card-with-raspbian-wheezy-linux-preinstalled.html TrendingUK ])

* '''Veho (http://www.veho-uk.com)'''
** 8Gb "Ultra Fast" Class 6. (man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0) 7.8Mb/s. Slow but tested with Arch Linux.

* '''W Photo (Walgreens photo)'''
** 1GB SD memory card. Works with raspbmc, have not tested others.
** 2GB SD memory card. Works with raspbian, not tested with others.

Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).

===Problem SD Cards===

Make sure that you buy your card from a reliable source. There are many cheap Chinese copies of (brand name) SD-Cards on the market, [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit/] in addition they are often mislabeled as having greater capacity than they really have. For example they might be sold as being 4GB, but are actually 2GB (or even less).

There were initially 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]

This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.

If you add an SD card here, please also mention the kernel date and the date you tried it. This allows people to estimate how likely it is that a driver-fix in the kernel has been fixed. (i.e. I think some/most of the cards here work fine now, because a problem in the kernel driver has been fixed).

* '''Acumem'''
** 8GB SDHC Class 6 (many errors on 6/7/2012)
* '''Adata'''
** 2GB Speedy (MMAGF02GWMCA -NA)
** 8GB SDHC Class 6 - Sometimes boots
** 16GB SDHC Class 6 (Possibly SD5MY168G0, label with gold <> black gradient) - Doesn't boot
* '''Agfa'''
** 16GB MicroSDHC class 6 (as written on SD-Adapter, MicroSD card itself no-name? ENAAJK121960): mixed results, such a card was working on another RPi
* '''Amazon Basics'''
** 16GB SDHC Class 10 (many errors on 6/7/2012)
* '''Delkin Devices'''
** 4GB SDHC Class 6 "Delkin pro" -- Note: works with Fedora Beefy Miracle 17
* '''GSkill'''
** 32GB SDHC Class 10
* '''Integral'''
** 16GB SDHC Class 6 Ultima Pro (SH016GAA2BB)
** 4GB SDHC class 4 (S404G1115)
* '''Kingston'''
** 2GB SD [http://www.geeks.com/details.asp?invtid=KING-SD-M02G-BULK looks like this] - boots the kernel, but damages the filesystem.
** 4GB SDHC Class 6 - Boots kernel but won't run init (times out)
** 8GB/Go SDHC Class 10 - SD10V/8GB Very slow writing images to card and then either won't boot, or boots very slowly
** 16GB SDHC Class 4 (SDC4/16GB17) - Device does not recognize it
* '''Memory2GO'''
** 4GB SDHC Class 6 (S404G1029) - I/O Errors leading to Kernel Panic on startup.
* '''Micro Center'''
**4GB SDHC Class 4 — hasn't worked with any of the images I've tried; appears to be completely unrecognized
* '''MyMemory.com'''
** 8GB SDHC Class 10
* '''Panasonic'''
** 8GB SDHC Class 10 (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]
* '''Patriot'''
** 8GB SDHC Class 10 (PSF8GSDHC10)
* '''Platinum'''
** 8GB SDHC Class 8 (O08G840 M3100487 TW)
* '''PNY'''
** 8GB Optima SDHC 120 HD Class 4 SD-K08G 0928 WF3673 - mmc -110 errors at init time on 6/12/12
** 32GB SDHC Class 10 Professional (P-SDHC32G10-EF) from [http://www.play.com/Electronics/Electronics/4-/18814903/-/Product.html play.com] (mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)
** 2GB card SD-M02G
* '''Polaroid'''
** 16GB SDHC C10 (P-SDHC16GB10-EFPOL) - mmc0: timeout waiting for hardware interrupt on debian6-19-04-2012
* '''PRETEC'''
** 8GB SDHC Class 10 233x - mmc0: timeout waiting for hardware interrupt, Sometimes does not boot, kernel panic, ...
* '''Reekin'''
** 4Gb HighSpeed SH4GC6M16MIN9C0812TE (old) don't boot ! (11/07/2012)
* '''Samsung'''
** 32GB SDHC Class 10 (MB-SSBGA, MBSSBGVEOBGA-SH) does not work with Debian Squeeze (debian6-19-04-2012: mmc0: timeout waiting for hardware interrupt), but works fine with [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=50&t=8071 Debian Wheezy]
* '''SanDisk'''
** 2GB SD Extreme III (BE0722702998D) (man:0x000003 oem:0x5344 name:SD02G hwrev:0x8 fwrev:0x0) - tested with Raspbian (build 2012-07-15) and Raspbmc installer (build 2012-07-13)
** 2GB SD (BE0916214253D)
** 2GB Ultra || 15MB/s (BE0828713280D)
** 4GB SDHC Class 2 - Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt.
** 4GB SDHC Class 2 "Limited Edition" (8H825413279G) - Error -110 whilst initialising sd card
** 4GB SDHC Class 4 (BH1030216016G) - Doesn't boot.
** 4GB SDHC Class 4 (BH1031116016G) - Doesn't boot.
** 4GB SDHC Class 6 Extreme (BH0822411730D)
** 4GB SDHC Class 6 Extreme III (30 MB/s) (BH0822712362G)
** 4GB SDHC Class 10 Extreme (SDSDX-004G-X46) (30 MB/s HD Video) doesn't boot (also not with new kernel.img and start.elf 17-06-2012 or "wheezy"-beta)
** 4GB SDHC Class 10 Extreme (30 MB/s HD Video) (Doesn't boot) - Works with new kernel.img and start.elf [https://github.com/raspberrypi/firmware/tree/master/boot]
** 4GB microSDHC Class 6 Mobile Ultra (tried 15-06-2012 with kernel 19-04-2012) error -84 transferring data, kernel panic: no init found
** 8GB SDHC Class 6 Ultra (B11201421964G)
** <del>8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )</del> see [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=88625#p88625 update from andrew.blake]
** 8GB SDHC Class 6 Ultra labelled as 30MB/s (BI1208721965G)) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra labelled as 30MB/s SDSRH-008G-A11 - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra labelled as 30MB/s SDSDH-008G-T11 - Boots kernel but won't run init ( debian6-19-04-2012: mmc timeout waiting for interrupt ) , but works fine with [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=50&t=8071 Debian Wheezy] on 6/22/12
** 8GB SDHC Class 6 Ultra I (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Extreme (BI1101116253G)
** 8GB SDHC Class 10 Extreme (BI1108716254G)
** 8GB SDHC Class 10 Extreme (BI1201416254G) - Still doesn't work with Debian Wheezy beta (2012-06-18)
** 8GB SDHC Class 10 Extreme (BI1201516254G) [[http://www.amazon.co.uk/gp/product/B00422FBJ2 amazon.co.uk]]+amazon.fr
** 8GB SDHC Class 10 Extreme (BI1200916252D/SDSDX-008G-X46) - Tried with Debian "Squeeze"(19/04/2012), Debian "Wheezy"(18/06/2012) and Arch Linux(13/06/2012). None works. With Debian "Wheezy" Green LED stays ON continuously, with the other two it turns on very faint.
** 8GB SDHC Class 10 Extreme Pro- Works with updated kernel/firmware, stock debian6-19-04-2012 boots kernel but won't run init ( mmc timeout waiting for interrupt )
** <del>16GB SDHC Class 10 Extreme (30MB/s HD Video) (SDSDX3-016G-X46) - Doesn't boot with debian6-19-04-2012.img, or newer firmware (tested 2012-06-17).</del>
** 16GB SDHC Class 6 Ultra (BL1202021933G)
** 16GB SDHC Class 6 Ultra I (BL1205921933G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
* '''Silicon Power'''
** 32GB SDHC Class 6 (LS2N732GQON03ASP) - boots debian6-19-04-2012.img, but frequent slow response / system hangs.
* '''TDK'''
** 4GB SDHC Class 6 (S404G1041) - Tried (end May 2012) with new kernel.img and start.elf [https://github.com/raspberrypi/firmware/tree/master/boot] but still won't run init.
** 4GB SDHC Class 6 (S404G1046) [Barcode: 4 902030 784447] - Tried (4th June 2012) with debian6-19-04-2012.img and with replacement kernel.img and start.elf from github [https://github.com/raspberrypi/firmware/tree/87a04c0be0c05e20f94f223183a0310b37c9bd89/boot] but still got 'Error -84' and 'Kernel panic - not syncing: No init found'

* '''Transcend'''
** 2GB MicroSD (MMAGR02GUECA-MB) - reads fine initially after image was written on a PC, gives mmc0 timeout errors reading back data after writing a large amount (in this case with 'pacman -Syu'). Still seems to work, but is *very* slow after this happens, even across reboots.
** 32GB MicroSD (TS32GUSDHC4) - Doesn't boot.
** 2GB SD (6451AG 2G O2DS1)
* '''Veho'''
** 4GB SDHC Class 6
* '''Verbatim'''
** 16GB SDHC Class 6 (47178) - Raspbian Pisces RC3 - boots, but after login: mmc timeout waiting for interrupt
** 8GB microSD Class 10 (44012) - ArchLinux - boots, but after system update develops segmentation faults

The usual warnings against less reputable sellers (such as Ebay merchants) apply.

Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):

mmc0: timeout waiting for hardware interrupt

=== Benchmarks ===

* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076
* http://forum.xda-developers.com/showthread.php?t=1005633 (Doesn't originate from R-Pi, but very related)

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}

RPI safe mode

2012-08-15T09:33:50Z

Bredman: Created page with "No text yet, see this post for information on safe mode. http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=12007"

No text yet, see this post for information on safe mode.

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=12007

R-Pi ConfigurationFile

2012-08-03T10:18:30Z

Bredman: /* How to edit from the Raspberry Pi */

[[Category:RaspberryPi]]

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from OSX=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.
*Put the SD card in your Mac's card reader and wait for the card to appear on the Desktop.
*Open the card in Finder.
*Look to see if there is a file called config (or possibly config.txt).
*If this file exists, open it with TextEdit. If not, create a new file in Textedit as Plain Text format.
*Add the necessary configuration parameters.
*Save the file as "config" and quit TextEdit.
*In Finder eject the SD card by dragging it to the Trash or clicking the eject button in the Finder window.
*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=
This method is most useful if you can see the display of the Raspberry Pi and you wish to make minor adjustments.

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

'''NOTE:''' You may find that your changes to config.txt disappear after a reboot. This is a very rare problem and seems to depend on the type of SD card. In this case, use a Windows/Linux/OSX PC to edit the file, see instructions above.

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

=What configuration options are available?=
For a list of all the configuration options available, click [http://elinux.org/RPi_config.txt here]

R-Pi ConfigurationFile

2012-08-03T10:17:45Z

Bredman: /* How to edit from OSX */

[[Category:RaspberryPi]]

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from OSX=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.
*Put the SD card in your Mac's card reader and wait for the card to appear on the Desktop.
*Open the card in Finder.
*Look to see if there is a file called config (or possibly config.txt).
*If this file exists, open it with TextEdit. If not, create a new file in Textedit as Plain Text format.
*Add the necessary configuration parameters.
*Save the file as "config" and quit TextEdit.
*In Finder eject the SD card by dragging it to the Trash or clicking the eject button in the Finder window.
*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

'''NOTE:''' You may find that your changes to config.txt disappear after a reboot. This is a very rare problem and seems to depend on the type of SD card. In this case, use a Windows/Linux/OSX PC to edit the file, see instructions above.

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

=What configuration options are available?=
For a list of all the configuration options available, click [http://elinux.org/RPi_config.txt here]

R-Pi ConfigurationFile

2012-08-03T10:14:59Z

Bredman: /* How to edit from the Raspberry Pi */

[[Category:RaspberryPi]]

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from OSX=

*Shut down your Raspberry Pi, remove the power and remove the SD card.
*Put the SD card in your Mac's card reader and wait for the card to appear on the Desktop.
*Open the card in Finder.
*Look to see if there is a file called config (or possibly config.txt).
*If this file exists, open it with TextEdit. If not, create a new file in Textedit as Plain Text format.
*Add the necessary configuration parameters.
*Save the file as "config" and quit TextEdit.
*In Finder eject the SD card by dragging it to the Trash or clicking the eject button in the Finder window.
*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

'''NOTE:''' You may find that your changes to config.txt disappear after a reboot. This is a very rare problem and seems to depend on the type of SD card. In this case, use a Windows/Linux/OSX PC to edit the file, see instructions above.

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

=What configuration options are available?=
For a list of all the configuration options available, click [http://elinux.org/RPi_config.txt here]

R-Pi Troubleshooting

2012-08-02T08:25:46Z

Bredman: /* Composite displays only back and white or no image */

Back to the [[R-Pi Hub|Hub]].

[[Category:RaspberryPi]]
This page lists the most common problems and suggests some solutions.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm224_start.elf : 224M ARM, 32M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm224_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==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 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.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

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.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

==References==
<references>
</references>

R-Pi Troubleshooting

2012-08-02T08:25:29Z

Bredman: /* Composite displays only back and white or no image */

Back to the [[R-Pi Hub|Hub]].

[[Category:RaspberryPi]]
This page lists the most common problems and suggests some solutions.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm224_start.elf : 224M ARM, 32M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm224_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==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 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.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

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.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI displayis connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

==References==
<references>
</references>

R-Pi Troubleshooting

2012-08-02T08:21:07Z

Bredman: New section - Unable to install new software

Back to the [[R-Pi Hub|Hub]].

[[Category:RaspberryPi]]
This page lists the most common problems and suggests some solutions.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===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. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(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>.

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
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>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<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.

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
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)).
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.

===Keyboard / Mouse interferes with USB WiFi device===
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.

===Wireless Keyboard trouble===
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.

===Re-mapping the keyboard with Debian Squeeze===
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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

===Slow keyboard mapping===
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:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm224_start.elf : 224M ARM, 32M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm224_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* 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.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* 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.
* 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>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==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 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.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
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
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

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.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
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)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
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.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC 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.

===Can only get 800x480 resolution in LXDE (Arch linux)===
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:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

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.

===Writing spills off the screen on HD monitors===

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.

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
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

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.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
Remember, the output display will be HDMI if detected, and composite if not. Make sure there isn't a HDMI cable connected when you are wanting composite output.

We default to NTSC output. Most TVs will show an image with that, but if not:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

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 and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

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.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

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. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

==References==
<references>
</references>

RPi Easy SD Card Setup

2012-06-12T13:59:30Z

Bredman: /* Copying an image to the SD Card in Linux (graphical interface) */

[[Category: RaspberryPi]]
{{Template:RPi_Startup}}

=SD Card setup=
To boot the Raspberry Pi, you need an SD card installed with a bootloader and a suitable Operating System. Some Raspberry Pi kits will come with a ready-to-go card, but if you didn't receive one you will need to prepare your own:

Official images are available from http://www.raspberrypi.org/downloads and there is an overview of available distributions [[RPi_Distributions | here]].

Warning! When you write the Raspberry Pi image to your SD card you will lose all data that was on the card.

=Safest/Laziest way=
Buy a preloaded card from RS Components or element14.

=Easiest way=

* Download and run the PiCard tool. It will guide you through the progress. See [http://code.google.com/p/rasp-pi-card/ the google code repo] and the [http://www.raspberrypi.org/forum/projects-and-collaboration-general/picard-gui-sd-preparation-tool/page-18 forum discussion].'''The PiCard project has now been disbanded'''

* Use an installer program. The [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix_Installation#SD_Card_Installation_Using_the_Installer Fedora ARM Installer] will download and install Raspberry Pi Fedora Remix images, but it will also install other images if they are already downloaded and in uncompressed or .gz format.

* ('''Mac''') The [http://exaviorn.com/raspiwrite/ RasPiWrite] utility is a python script which will walk you through the process of installing to SD card, it is works with any Raspberry Pi compatible disk image, and can download one of the currently available distros if you don't have one.

=Easy way=

To write your SD card you start by downloading the SD image (the data you will write to the card). The best way to do this is using [http://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent]. This generally results in a faster download as it is a highly distributed system (you will be downloading the data from users who have previously downloaded it).

This guide assumes you have downloaded the Debian "squeeze" image, with name debian6-13-04-2012. Obviously, if you are downloading a different or newer version, use the name of the version you have downloaded.

==Copying the image to an SD Card on Windows==

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file debian6-19-04-2012.img from the debian6-19-04-2012directory in the debian6-19-04-2012.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example G:) by looking in the left column of Windows Explorer.
# Download the [https://launchpad.net/win32-image-writer Win32DiskImager] utility. The download links are on the right hand side of the page, you want the binary zip.
# Extract the zip file and run the Win32DiskImager utility.
# Select the debian6-19-04-2012.img image file you extracted earlier
# Select the drive letter of the SD card in the device box. Be careful to select the correct drive; if you get the wrong one you can destroy your computer's hard disk!
# Click Write and wait for the write to complete.
# Exit the imager and eject the SD card.
# Insert the card in the Raspberry Pi, power it on, and it should boot up. Have fun!
''In Windows the SD card will appear only to have a fairly small size - about 75 Mbytes. This is because most of the card has a partition that is formatted for the Linux operating system that the RPi uses and is not visible in Windows.
''

==Copying the image to an SD Card on Windows if first option isn't successful==
I wasn't able to choose device in Win32DiskImager on my notebook so I found a different way to achieve the same thing on windows machine..

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file debian6-19-04-2012.img from the debian6-19-04-2012 directory in the debian6-19-04-2012.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example H:) by looking in the left column of Windows Explorer.
# Download flashnul software from http://shounen.ru/soft/flashnul/ here is [http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en Translated version]
#* Download the latest version at the time of writing it was flashnul-1rc1.
#* Download and Extract the application from archive.
#* Click Start button > All Programs > Accessories > Command Prompt, right click on it and Run as Administrator.
#* Run the flashnul with argument:
C:/flashnul/flashnul.exe -p
#* Flashnul will tell you something like:

Avaible physical drives:
0 size = 250059350016 (232 Gb)
1 size = 1990197248 (1898 Mb)

Avaible logical disks:
C:\
D:\
F:\
G:\
H:\

Press ENTER to exit.

'''SDCARD number is on left! In my case it is number 1'''

#* Now we will use Load argument:
C:/flashnul/flashnul.exe 1 -L C:/debian6/debian6-19-04-2012.img
where '''<Path to flashnul directory>'''flashnul.exe '''<device number>''' -L '''<img file path>'''

#* Flashnul will give you a device summary and proceed caution, have a quick scan through the information to make sure you have selected the correct device, then type yes and press enter.
#* If you get a access denied error, try re-plugging the SD card. Also make sure to close all explorer windows or folders open for the device.
#* If you still get a access denied error, try substitute the device number with the drive letter followed by a colon. Eg:
C:/flashnul/flashnul.exe H: -L C:/debian6/debian6-19-04-2012.img
* If the device summary does not match Your card (the size is smaller, e.g. 75MB), but you are sure, that the letter is correct - please continue and then try again with the device number.

----
--[[User:Kerbik|Kerbik]] 23:55, 24 April 2012 (UTC)
I hope that this will help someone :) (I didn't test this created SDcard on Pi, yet because I still doesn't have it in my hands :( )

--[[User:Radek|Radek]] 21:03, 18 May 2012 (UTC) Yes it works :)

==Copying an image to the SD Card in Mac OS X==

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key is the same (optional), in the terminal run:
#* '''shasum ~/Downloads/debian6-19-04-2012.zip'''
# Extract the image:
#* '''unzip ~/Downloads/debian6-19-04-2012.zip'''
#* ''(or: just double click the zip, it will extract automatically)''
# From the terminal run '''df -h'''
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again and look for the new device that wasn't listed last time. Record the device name of the filesystem's partition, e.g. '''/dev/disk1s1'''
# Unmount the partition so that you will be allowed to overwrite the disk:
#* '''diskutil unmount /dev/disk1s1'''
#* ''(or: open Disk Utility and unmount the partition of the sdcard (do not eject it, or you have to reconnect it))''
# Using the device name of the partition work out the raw device name for the entire disk, by missing out the final "s1" and replacing "disk" with "rdisk":
#* e.g. '''/dev/disk1s1''' => '''/dev/rdisk1'''
# In the terminal write the image to the card with this command, using the raw disk device name from above:
#* '''dd bs=1m if=~/Downloads/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/rdisk1'''
#* (note that dd will not feedback any information until it is finished, information will show and disk will re-mount when complete)
# After the dd command finishes, eject the card:
#* '''diskutil eject /dev/rdisk1'''
#* ''(or: open Disk Utility and eject the sdcard)''
# Insert it in the raspberry pi, and have fun

==Copying an image to the SD Card in Linux (command line)==

Please note that the use of the "dd" tool can overwrite any partition of your machine. If you specify the wrong device in the instructions below you could delete your primary Linux partition. Please be careful.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key of the zip file is the same as shown on the downloads page (optional). Assuming that you put the zip file in your home directory (~/), in the terminal run:
#* '''sha1sum ~/debian6-19-04-2012.zip'''
#* This will print out a long hex number which should match the "SHA-1" line for the SD image you have downloaded
# Extract the image, with
#* '''unzip ~/debian6-19-04-2012.zip'''
# Run '''df -h''' to see what devices are currently mounted
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again. The device that wasn't there last time is your SD card. The left column gives the device name of your SD card. It will be listed as something like "/dev/mmcblk0p1" or "/dev/sdd1". The last part ("p1" or "1" respectively) is the partition number, but you want to write to the whole SD card, not just one partition, so you need to remove that part from the name (getting for example "/dev/mmcblk0" or "/dev/sdd") as the device for the whole SD card. Note that the SD card can show up more than once in the output of df: in fact it will if you have previously written a Raspberry Pi image to this SD card, because the RPi SD images have more than one partition.
# Now that you've noted what the device name is, you need to unmount it so that files can't be read or written to the SD card while you are copying over the SD image. So run the command below, replacing "/dev/sdd1" with whatever your SD card's device name is (including the partition number)
#* '''umount /dev/sdd1'''
#* If your SD card shows up more than once in the output of df due to having multiple partitions on the SD card, you should unmount all of these partitions.
# In the terminal write the image to the card with this command, making sure you replace the input file '''if=''' argument with the path to your .img file, and the "/dev/sdd" in the output file '''of=''' argument with the right device name ('''this is very important:''' you '''will''' loose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, sdd, not sdds1 or sddp1, or mmcblk0 not mmcblk0p1)
#* '''dd bs=1M if=~/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/sdd'''
#* Note that if you are not logged in as root you will need to prefix this with '''sudo '''
#* The dd command does not give any information of its progress and so may appear to have froze.
# As root run the command '''sync''' or if a normal user run '''sudo sync''' (this will ensure the write cache is flushed and that it is safe to unmount your SD card)
# Remove SD card from card reader, insert it in the Raspberry Pi, and have fun

==Copying an image to the SD Card in Linux (graphical interface)==
If you are using Ubuntu and hesitate to use the terminal, you can use the ImageWriter tool (nice graphical user interface) to write the .img file to the SD card.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Right click the zip file and select "Extract here"
# Insert the SD card into your computer or connect the SD card reader with the SD card inside
# Install the ImageWriter tool from the Ubuntu Software Center
# Launch the ImageWriter tool (it needs your administrative password)
# Select the image file (example debian6-19-04-2012.img) to be written to the SD card
# Select the target device to write the image to (your device will be something like "/dev/mmcblk0" or "/dev/sdc")
# Click the "Write to device" button
# Wait for the process to finish and then insert the SD card in the Raspberry Pi

=Manually resizing the SD card partitions (Optional)=
The SD card image is sized for a 2GB card. The Fedora Remix will automatically resize the partitions on the card during the first boot. The Debian version won't, so you'll have to do it manually. It's much easier if you do this on another machine, as the SD card can't be mounted when you do this.

==Manually resizing the SD card on Linux==

Tutorial video here: http://www.youtube.com/watch?v=R4VovMDnsIE

Following on from the instructions above, keep the newly-written SD card in the card reader, but unmounted. We'll use the <code>parted</code> (partition editor) tool to resize the partitions.
* Use parted to examine the card
$ sudo parted /dev/sdd
(parted) unit chs
(parted) print
Disk /dev/sdd: 121535,3,31
Sector size (logical/physical): 512B/512B
BIOS cylinder,head,sector geometry: 121536,4,32. Each cylinder is 65.5kB.
Partition Table: msdos

Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
: This shows how my SD card was formatted after writing the image. Notice that nothing uses the card from end of 'cylinder' 29743 to the card's maximum at 121535.
: Partition 1 is the boot partition: we'll leave that alone. Partition 2 is the root partition, which we'll grow to fill most of the card. Partition 3 is the swap space, which needs to be moved to the end of the card. Note that on some other versions of linux (and some other versions of hardware) use /sde not /sdd.
* Move the swap partition (you'll have to adjust the numbers so that the end of partition 3 is at the end cylinder/head/sector of the card)
* to calculate the number to use in the following command do:- <code>(Maximum - (Partation 3 End - Partation 3 Start) ) - 1 = Partition 3 New Start</code> so in this example <code>(121535 - ( 29743 - 26688)) -1 = 118479 </code>
(parted) move 3 118479,0,0
* Now grow the root partition. This involves removing the partition, re-creating it, then using <code>resize2fs</code> to grow the filesystem to fill the partition. It won't destroy any data.
(parted) rm 2
(parted) mkpart primary 1232,0,0 118478,3,31
(parted) quit
: Note that the starting address of the new partition is identical to its original value, and the ending address is immediately before the start of the swap partition.
* Now clean and resize the root partition. As before, some users may need to use /sde2 instead.
$ sudo e2fsck -f /dev/sdd2
: (allow it to add lost-and-found)
$ sudo resize2fs /dev/sdd2
* Then put the card in the RPi and boot. You end up with a 7Gb partition to use.
pi@raspberrypi:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 94M 4.0K 94M 1% /lib/init/rw
udev 10M 168K 9.9M 2% /dev
tmpfs 94M 0 94M 0% /dev/shm
rootfs 7.1G 1.3G 5.4G 20% /
/dev/mmcblk0p1 75M 28M 48M 37% /boot

==Manually resizing the SD card on Raspberry Pi==

You can also resize the partitions of the SD card that your Pi is running on.

First you need to change the partition table with fdisk. You need to remove the existing partition entries and then create a single new partition than takes the whole free space of the disk. This will only change the partition table, not the partitions data on disk. '''The start of the new partition needs to be aligned with the old partition!'''

Start fdisk:

sudo fdisk -cu /dev/mmcblk0

Then delete partitions with ''d'' and create a new with ''n''. You can view the existing table with ''p''.

* ''p'' to see the current start of the main partition
* ''d'', ''3'' to delete the swap partition
* ''d'', ''2'' to delete the main partition
* ''n'' ''p'' ''2'' to create a new primary partition, next you need to enter the start of the old main partition and then the size (''enter'' for complete SD card). The main partition on the Debian image from 2012-04-19 starts at 157696, but the start of your partition might be different. Check the ''p'' output!
* ''w'' write the new partition table

Now you need to reboot:

sudo shutdown -r now

After the reboot you need to resize the actual partition. The <code>resize2fs</code> will resize your main partition to the new size from the changed partition table.

sudo resize2fs /dev/mmcblk0p2

This will take a few minutes, depending on the size and speed of your SD card.

When it is done, you can check the new size with:

df -h

{{Template:Raspberry Pi}}

RPi Easy SD Card Setup

2012-06-12T13:59:08Z

Bredman: /* Copying an image to the SD Card in Linux (graphical interface) */

[[Category: RaspberryPi]]
{{Template:RPi_Startup}}

=SD Card setup=
To boot the Raspberry Pi, you need an SD card installed with a bootloader and a suitable Operating System. Some Raspberry Pi kits will come with a ready-to-go card, but if you didn't receive one you will need to prepare your own:

Official images are available from http://www.raspberrypi.org/downloads and there is an overview of available distributions [[RPi_Distributions | here]].

Warning! When you write the Raspberry Pi image to your SD card you will lose all data that was on the card.

=Safest/Laziest way=
Buy a preloaded card from RS Components or element14.

=Easiest way=

* Download and run the PiCard tool. It will guide you through the progress. See [http://code.google.com/p/rasp-pi-card/ the google code repo] and the [http://www.raspberrypi.org/forum/projects-and-collaboration-general/picard-gui-sd-preparation-tool/page-18 forum discussion].'''The PiCard project has now been disbanded'''

* Use an installer program. The [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix_Installation#SD_Card_Installation_Using_the_Installer Fedora ARM Installer] will download and install Raspberry Pi Fedora Remix images, but it will also install other images if they are already downloaded and in uncompressed or .gz format.

* ('''Mac''') The [http://exaviorn.com/raspiwrite/ RasPiWrite] utility is a python script which will walk you through the process of installing to SD card, it is works with any Raspberry Pi compatible disk image, and can download one of the currently available distros if you don't have one.

=Easy way=

To write your SD card you start by downloading the SD image (the data you will write to the card). The best way to do this is using [http://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent]. This generally results in a faster download as it is a highly distributed system (you will be downloading the data from users who have previously downloaded it).

This guide assumes you have downloaded the Debian "squeeze" image, with name debian6-13-04-2012. Obviously, if you are downloading a different or newer version, use the name of the version you have downloaded.

==Copying the image to an SD Card on Windows==

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file debian6-19-04-2012.img from the debian6-19-04-2012directory in the debian6-19-04-2012.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example G:) by looking in the left column of Windows Explorer.
# Download the [https://launchpad.net/win32-image-writer Win32DiskImager] utility. The download links are on the right hand side of the page, you want the binary zip.
# Extract the zip file and run the Win32DiskImager utility.
# Select the debian6-19-04-2012.img image file you extracted earlier
# Select the drive letter of the SD card in the device box. Be careful to select the correct drive; if you get the wrong one you can destroy your computer's hard disk!
# Click Write and wait for the write to complete.
# Exit the imager and eject the SD card.
# Insert the card in the Raspberry Pi, power it on, and it should boot up. Have fun!
''In Windows the SD card will appear only to have a fairly small size - about 75 Mbytes. This is because most of the card has a partition that is formatted for the Linux operating system that the RPi uses and is not visible in Windows.
''

==Copying the image to an SD Card on Windows if first option isn't successful==
I wasn't able to choose device in Win32DiskImager on my notebook so I found a different way to achieve the same thing on windows machine..

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file debian6-19-04-2012.img from the debian6-19-04-2012 directory in the debian6-19-04-2012.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example H:) by looking in the left column of Windows Explorer.
# Download flashnul software from http://shounen.ru/soft/flashnul/ here is [http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en Translated version]
#* Download the latest version at the time of writing it was flashnul-1rc1.
#* Download and Extract the application from archive.
#* Click Start button > All Programs > Accessories > Command Prompt, right click on it and Run as Administrator.
#* Run the flashnul with argument:
C:/flashnul/flashnul.exe -p
#* Flashnul will tell you something like:

Avaible physical drives:
0 size = 250059350016 (232 Gb)
1 size = 1990197248 (1898 Mb)

Avaible logical disks:
C:\
D:\
F:\
G:\
H:\

Press ENTER to exit.

'''SDCARD number is on left! In my case it is number 1'''

#* Now we will use Load argument:
C:/flashnul/flashnul.exe 1 -L C:/debian6/debian6-19-04-2012.img
where '''<Path to flashnul directory>'''flashnul.exe '''<device number>''' -L '''<img file path>'''

#* Flashnul will give you a device summary and proceed caution, have a quick scan through the information to make sure you have selected the correct device, then type yes and press enter.
#* If you get a access denied error, try re-plugging the SD card. Also make sure to close all explorer windows or folders open for the device.
#* If you still get a access denied error, try substitute the device number with the drive letter followed by a colon. Eg:
C:/flashnul/flashnul.exe H: -L C:/debian6/debian6-19-04-2012.img
* If the device summary does not match Your card (the size is smaller, e.g. 75MB), but you are sure, that the letter is correct - please continue and then try again with the device number.

----
--[[User:Kerbik|Kerbik]] 23:55, 24 April 2012 (UTC)
I hope that this will help someone :) (I didn't test this created SDcard on Pi, yet because I still doesn't have it in my hands :( )

--[[User:Radek|Radek]] 21:03, 18 May 2012 (UTC) Yes it works :)

==Copying an image to the SD Card in Mac OS X==

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key is the same (optional), in the terminal run:
#* '''shasum ~/Downloads/debian6-19-04-2012.zip'''
# Extract the image:
#* '''unzip ~/Downloads/debian6-19-04-2012.zip'''
#* ''(or: just double click the zip, it will extract automatically)''
# From the terminal run '''df -h'''
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again and look for the new device that wasn't listed last time. Record the device name of the filesystem's partition, e.g. '''/dev/disk1s1'''
# Unmount the partition so that you will be allowed to overwrite the disk:
#* '''diskutil unmount /dev/disk1s1'''
#* ''(or: open Disk Utility and unmount the partition of the sdcard (do not eject it, or you have to reconnect it))''
# Using the device name of the partition work out the raw device name for the entire disk, by missing out the final "s1" and replacing "disk" with "rdisk":
#* e.g. '''/dev/disk1s1''' => '''/dev/rdisk1'''
# In the terminal write the image to the card with this command, using the raw disk device name from above:
#* '''dd bs=1m if=~/Downloads/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/rdisk1'''
#* (note that dd will not feedback any information until it is finished, information will show and disk will re-mount when complete)
# After the dd command finishes, eject the card:
#* '''diskutil eject /dev/rdisk1'''
#* ''(or: open Disk Utility and eject the sdcard)''
# Insert it in the raspberry pi, and have fun

==Copying an image to the SD Card in Linux (command line)==

Please note that the use of the "dd" tool can overwrite any partition of your machine. If you specify the wrong device in the instructions below you could delete your primary Linux partition. Please be careful.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key of the zip file is the same as shown on the downloads page (optional). Assuming that you put the zip file in your home directory (~/), in the terminal run:
#* '''sha1sum ~/debian6-19-04-2012.zip'''
#* This will print out a long hex number which should match the "SHA-1" line for the SD image you have downloaded
# Extract the image, with
#* '''unzip ~/debian6-19-04-2012.zip'''
# Run '''df -h''' to see what devices are currently mounted
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again. The device that wasn't there last time is your SD card. The left column gives the device name of your SD card. It will be listed as something like "/dev/mmcblk0p1" or "/dev/sdd1". The last part ("p1" or "1" respectively) is the partition number, but you want to write to the whole SD card, not just one partition, so you need to remove that part from the name (getting for example "/dev/mmcblk0" or "/dev/sdd") as the device for the whole SD card. Note that the SD card can show up more than once in the output of df: in fact it will if you have previously written a Raspberry Pi image to this SD card, because the RPi SD images have more than one partition.
# Now that you've noted what the device name is, you need to unmount it so that files can't be read or written to the SD card while you are copying over the SD image. So run the command below, replacing "/dev/sdd1" with whatever your SD card's device name is (including the partition number)
#* '''umount /dev/sdd1'''
#* If your SD card shows up more than once in the output of df due to having multiple partitions on the SD card, you should unmount all of these partitions.
# In the terminal write the image to the card with this command, making sure you replace the input file '''if=''' argument with the path to your .img file, and the "/dev/sdd" in the output file '''of=''' argument with the right device name ('''this is very important:''' you '''will''' loose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, sdd, not sdds1 or sddp1, or mmcblk0 not mmcblk0p1)
#* '''dd bs=1M if=~/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/sdd'''
#* Note that if you are not logged in as root you will need to prefix this with '''sudo '''
#* The dd command does not give any information of its progress and so may appear to have froze.
# As root run the command '''sync''' or if a normal user run '''sudo sync''' (this will ensure the write cache is flushed and that it is safe to unmount your SD card)
# Remove SD card from card reader, insert it in the Raspberry Pi, and have fun

==Copying an image to the SD Card in Linux (graphical interface)==
If you are using Ubuntu and hesitate to use the terminal, you can use the ImageWriter tool (nice graphical user interface) to write the .img file to the SD card.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Right click the zip file and select "Extract here"
# Insert the SD card into your computer or connect the SD card reader with the SD card inside
# Install the ImageWriter tool from the Ubuntu Software Center
# Launch the ImageWriter tool (it needs your administrative password)
# Select the image file (example debian6-19-04-2012.img) to be written to the SD card
# Select the target device to write the image to (your device will be something like "/dev/mmcblk0" or "/dev/sdc")
# Click the "Write to device button"
# Wait for the process to finish and then insert the SD card in the Raspberry Pi

=Manually resizing the SD card partitions (Optional)=
The SD card image is sized for a 2GB card. The Fedora Remix will automatically resize the partitions on the card during the first boot. The Debian version won't, so you'll have to do it manually. It's much easier if you do this on another machine, as the SD card can't be mounted when you do this.

==Manually resizing the SD card on Linux==

Tutorial video here: http://www.youtube.com/watch?v=R4VovMDnsIE

Following on from the instructions above, keep the newly-written SD card in the card reader, but unmounted. We'll use the <code>parted</code> (partition editor) tool to resize the partitions.
* Use parted to examine the card
$ sudo parted /dev/sdd
(parted) unit chs
(parted) print
Disk /dev/sdd: 121535,3,31
Sector size (logical/physical): 512B/512B
BIOS cylinder,head,sector geometry: 121536,4,32. Each cylinder is 65.5kB.
Partition Table: msdos

Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
: This shows how my SD card was formatted after writing the image. Notice that nothing uses the card from end of 'cylinder' 29743 to the card's maximum at 121535.
: Partition 1 is the boot partition: we'll leave that alone. Partition 2 is the root partition, which we'll grow to fill most of the card. Partition 3 is the swap space, which needs to be moved to the end of the card. Note that on some other versions of linux (and some other versions of hardware) use /sde not /sdd.
* Move the swap partition (you'll have to adjust the numbers so that the end of partition 3 is at the end cylinder/head/sector of the card)
* to calculate the number to use in the following command do:- <code>(Maximum - (Partation 3 End - Partation 3 Start) ) - 1 = Partition 3 New Start</code> so in this example <code>(121535 - ( 29743 - 26688)) -1 = 118479 </code>
(parted) move 3 118479,0,0
* Now grow the root partition. This involves removing the partition, re-creating it, then using <code>resize2fs</code> to grow the filesystem to fill the partition. It won't destroy any data.
(parted) rm 2
(parted) mkpart primary 1232,0,0 118478,3,31
(parted) quit
: Note that the starting address of the new partition is identical to its original value, and the ending address is immediately before the start of the swap partition.
* Now clean and resize the root partition. As before, some users may need to use /sde2 instead.
$ sudo e2fsck -f /dev/sdd2
: (allow it to add lost-and-found)
$ sudo resize2fs /dev/sdd2
* Then put the card in the RPi and boot. You end up with a 7Gb partition to use.
pi@raspberrypi:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 94M 4.0K 94M 1% /lib/init/rw
udev 10M 168K 9.9M 2% /dev
tmpfs 94M 0 94M 0% /dev/shm
rootfs 7.1G 1.3G 5.4G 20% /
/dev/mmcblk0p1 75M 28M 48M 37% /boot

==Manually resizing the SD card on Raspberry Pi==

You can also resize the partitions of the SD card that your Pi is running on.

First you need to change the partition table with fdisk. You need to remove the existing partition entries and then create a single new partition than takes the whole free space of the disk. This will only change the partition table, not the partitions data on disk. '''The start of the new partition needs to be aligned with the old partition!'''

Start fdisk:

sudo fdisk -cu /dev/mmcblk0

Then delete partitions with ''d'' and create a new with ''n''. You can view the existing table with ''p''.

* ''p'' to see the current start of the main partition
* ''d'', ''3'' to delete the swap partition
* ''d'', ''2'' to delete the main partition
* ''n'' ''p'' ''2'' to create a new primary partition, next you need to enter the start of the old main partition and then the size (''enter'' for complete SD card). The main partition on the Debian image from 2012-04-19 starts at 157696, but the start of your partition might be different. Check the ''p'' output!
* ''w'' write the new partition table

Now you need to reboot:

sudo shutdown -r now

After the reboot you need to resize the actual partition. The <code>resize2fs</code> will resize your main partition to the new size from the changed partition table.

sudo resize2fs /dev/mmcblk0p2

This will take a few minutes, depending on the size and speed of your SD card.

When it is done, you can check the new size with:

df -h

{{Template:Raspberry Pi}}

R-Pi NAS

2012-06-10T20:48:17Z

Bredman: /* Configure a public storage area on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

By default, the username pi is defined.
To allow pi to be a samba user
sudo smbpasswd -a pi
You will be asked to enter pi's password twice.

If you want to use another username for Samba, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter john's password twice.

if smbpasswd doesn't work try

<code>pdbedit -a -u john</code>

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter john's password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug=rwx,o=rx /home/shares/public

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

=Adding USB Storage=
If you are going to add some drives to share, and you have not already done so add them. For a tutorial on how to connect USB flash drives and hard drives to your Pi, see: [http://elinux.org/Adding_USB_Drives_to_a_Raspberry_Pi Adding USB Drives to a Raspberry Pi]

After reading the above tutorial you will want to tweak where your drives are mounted so that they mount in the share area. First create a directory then mount the drive there.
sudo mkdir /home/shares/public/disk1
sudo mount /dev/sdxx /home/shares/public/disk1
Where sdxx is where your drive is in the file system's device hierarchy. i.e. /dev/sda1

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Press the "+" on the top right.

Click on "Network"

Click on "Windows/Samba sharing"

Click on "Create new account"

Leave server domain empty

Set computer name to "raspberrypi"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

Click on the server named "pi" in the "File Sharing Servers" list.

{{Template:Raspberry Pi}}

RPi Beginners

2012-05-31T21:54:00Z

Bredman: /* Create a new User and add it to the sudoers list */

[[Category:RaspberryPi]]
{{Template:RPi_Startup}}

''' INFO : If you are looking for any information related to SD Cards and setup look
[[RPi Easy SD Card Setup | here]] There is some restructuring going on , we are sorry for the inconvenience. '''

=About This Page - For Contributors=
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.

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)!

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.

----

=Where to start?=
Any easy question to ask, but a very difficult one to answer!
# If you need to get a RPi, the see the [[RPi Buying Guide|Buying Guide]].
# 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.
# If you need to install/setup an SD card see the [[RPi Easy SD Card Setup|Preload your Card]] section.
# If something is not working, check the [[R-Pi_Troubleshooting|Troubleshooting]] section.
# If you need help with Debian, try the [http://wiki.debian.org/FrontPage Debian Wiki].
# If you've done all that, and you are wondering what next...'''welcome and read on!'''

References needed (idea for new section Living Without RPi, which can guide users or link to info to users who haven't got RPis)
Link to emulation builds or live linux cds setup for beginners (RacyPy2 for example)
If you don't have a Raspberry Pi yet, you can still try things out, see xxxx for details.

=What is Linux and why not use Windows?=
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.

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.

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!

For more information about Linux see
[http://en.wikipedia.org/wiki/Linux Wikipedia]

Also see [http://elinux.org/RPi_End-user_FAQ End-User FAQ]
And [http://elinux.org/Will_RPi_Run Running XXX on the RPi]

=Basic Debian RPi Setup=
When you first turn on your Raspberry Pi with it's fresh Debian image on the SD card, you may have to make some minor adjustments to the OS configuration files to suit your location. The default location setting (locale) is the UK.

You can alter this with

sudo dpkg-reconfigure locales

There are quite a lot of options - many people will want to use the UTF-8 variant for their locale. This will also allow you to set anomalous cases
like English keyboard but Danish locale.

Selecting All locales will generate all possible locales, take a very long time and use a great deal of space. Generate only those you wish to use.

The command above will open a list which begins

aa_DJ [Ambala, for Djibouti] ISO-8059-1 and goes down to zu_._UTF8 UTF-81 [Zulu for S. Africa]

You have various options for each language - UTF-8 is probably the most useful worldwide - Unicode characters.

Scroll down using a down arrow key, toggle with a space bar to select.

==Keyboard Mapping==

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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

Also, see the [[R-Pi_Troubleshooting#Re-mapping_the_keyboard_with_Debian_Squeeze|Troubleshooting Guide]] for more information about remapping the keyboard.

Changes will certainly be picked up at the next restart.

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:
sudo setupcon

==Create a new User and add it to the sudoers list==

Type in following command in the Terminal to create a new user:
sudo adduser username
Follow the Steps. After creating the new User you must get root Access with the following Command:
sudo su
Now you can add your user to the sudoers list:
visudo
Add following Line under the "root ALL=(ALL) ALL" Line:
yourUsername ALL=(ALL) ALL
Now press CTRL+K X to save and exit the editor.

Alternatively instead of adding the user to the sudoers list, you can add your user to the sudo group with the following command:
useradd -G sudo yourUsername

==Change the Timezone==
Unless you live in Great Britain, you'll have to change the default timezone. Use "sudo" to obtain temporary execute permissions.
sudo dpkg-reconfigure tzdata

Select geographic area - Europe, America or whatever. Etc gives UNIX compatible time zones including CUT, GMT, UTC

Select city

Follow the prompts to finish the config. The change should be immediate.

=Intro to the CLI (Command Line Interface)=
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.

For an introductory guide to some basic commands please see: [http://elinux.org/CLI_Spells Command Line Interface "Must Have" Commands]

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:

startx

=Remote Access=
Your default install probably has a ssh (secure shell) "daemon" running.
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.
[http://elinux.org/Remote_Access Remote Access]

=Adding more software to your Raspberry Pi=
You will probably want to add software to your Raspberry Pi. Here you can find out how to do it.
[http://elinux.org/Add_software Adding Software]

=Adding USB Storage to Your Raspberry Pi=
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]

=Beginner Projects=
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.

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.
Reference needed - a good guide on how to backup and restore cards or software to do this easily

==Media Player==
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).

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]

Reference needed - links to a specific wiki page covering this in detail or links to projects like
OpenElec, CrystalBuntu, Raspbmc etc

==Play Games==
While there are not any commercial games for the Raspberry Pi (yet) there are plenty ways to play games on it.

Many distributions will have games built into them, and some may well support emulation of other platforms so you can run those games.

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).

Reference needed - game section is empty at the moment!
''See the [[RPi Games|Games Section]] for more details''

==Introducing Young Children To Computers==
Reference needed - some kid friendly and fun stuff!

==Teaching==
There is a huge number of groups, links and resources available within the [[RPi Education|Education]] section.
Reference needed - links to the learning pages, education links and school/university groups

==Learn To Program==
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.

There is a huge selection to choose from (not just Python...) which should suit any ability and a range of purposes.

If you are new to programming, there are plenty of tutorials for getting started in the [[RPi Tutorials|Tutorials]] Section.

Books about programming can be found in the [[RPi Programming Books|Books]] Section.

In the latest Debian, Python (+Pygame) and MIT Scratch are pre-installed.

Reference needed - links to the learning pages, recommended books?

==Interface With Hardware==
# [[RPi Interfacing with hardware|Interfacing with Arduino]]

Reference needed - links to basic circuits tutorials and expansion boards

==Word Processing/Internet Browsing etc==
Yes, the Raspberry Pi can do the majority of the dull stuff too which other computers do.

'''Debian''' currently comes with Midori installed for web browsing and word processing programs be installed rather easily.

*Entering "sudo apt-get install openoffice.org" into a terminal will install OpenOffice.org, a free Microsoft Office-like application suite
*Entering "sudo apt-get install abiword-common" into a terminal will install AbiWord, a lighter weight but still fully functional word processor

More information needed

==Your Own Pet Project!==
The sky is the limit really, with some time and effort any number of projects can be achieved.

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.

Of course, if you do anything interesting then please let us know in the [[RPi Projects |Projects]] section.

=Living Without RPi=
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.

==Using Linux==
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).

RacyPy - This is a simple LiveCD of Puppy Linux which includes some basic programming languages and a light-weight graphical user interface (GUI).

You can get it from here:

[http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ teampython RacyPy]

==Trying Programming==
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.

==Controlling Hardware==
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).

=References=
<references/>
{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:46:41Z

Bredman: /* Configure private storage areas on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

By default, the username pi is defined.
To allow pi to be a samba user
sudo smbpasswd -a pi
You will be asked to enter pi's password twice.

If you want to use another username for Samba, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter john's password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter john's password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Press the "+" on the top right.

Click on "Network"

Click on "Windows/Samba sharing"

Click on "Create new account"

Leave server domain empty

Set computer name to "raspberrypi"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

Click on the server named "pi" in the "File Sharing Servers" list.

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:43:08Z

Bredman: /* Configuring the Samba client on an Android smartphone */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

By default, the username pi is defined. If you want to use another username for Samba, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Press the "+" on the top right.

Click on "Network"

Click on "Windows/Samba sharing"

Click on "Create new account"

Leave server domain empty

Set computer name to "raspberrypi"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

Click on the server named "pi" in the "File Sharing Servers" list.

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:30:14Z

Bredman: /* Configure a public storage area on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

By default, the username pi is defined. If you want to use another username for Samba, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:27:56Z

Bredman: /* Configure private storage areas on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

By default, the username pi is defined. If you want to use another username for Samba, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:25:42Z

Bredman: /* Configure private storage areas on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:24:34Z

Bredman: /* Configure private storage areas on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:23:39Z

Bredman: /* Configure private storage areas on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:21:06Z

Bredman: /* Enable security on the Samba server on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
Stopping Samba daemons: nmdb smdb
Starting Samba daemons: nmdb smdb

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:18:05Z

Bredman: Deleted section, not needed for average user /* Move home directory to a large USB disk */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
smbd start/running, process n

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:13:49Z

Bredman: /* Enable security on the Samba server on the RPi */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Move home directory to a large USB disk==
'''This section has not been decided yet. Only important if the user wishes to use a large external disk'''

How to do this easily? Lots of ways, but we need one that is guaranteed to work for an absolute beginner.

See the "discussion" tab for more details.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
# security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
smbd start/running, process n

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:12:29Z

Bredman: Removed Fedora

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Move home directory to a large USB disk==
'''This section has not been decided yet. Only important if the user wishes to use a large external disk'''

How to do this easily? Lots of ways, but we need one that is guaranteed to work for an absolute beginner.

See the "discussion" tab for more details.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
; security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
smbd start/running, process n

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:11:29Z

Bredman: Deleted section, it did not work /* Check if the RPi has a network host name defined */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

'''These instructions have not been tested on a Raspberry Pi yet.'''

These instructions were tested in a Debian environment. Anybody willing to submit a version in the empty Fedora chapter below?

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Fedora RPi
#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Fedora RPi=
'''Not available yet.''' Anybody is welcome to copy the Debian instructions into this section and edit as necessary.

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Move home directory to a large USB disk==
'''This section has not been decided yet. Only important if the user wishes to use a large external disk'''

How to do this easily? Lots of ways, but we need one that is guaranteed to work for an absolute beginner.

See the "discussion" tab for more details.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
; security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
smbd start/running, process n

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

R-Pi NAS

2012-05-30T21:07:34Z

Bredman: /* Check if the RPi has a network host name defined */

Back to [[RPi Guides]].

'''Raspberry Pi Network Attached Storage'''

'''These instructions have not been tested on a Raspberry Pi yet.'''

These instructions were tested in a Debian environment. Anybody willing to submit a version in the empty Fedora chapter below?

=What does it do?=

This project configures your Raspberry Pi to share files with any other computer on your local network. You can add a large hard disk to the RPi and use this to store your important files/photos/videos in a central location.

The files on your RPi can be easily accessed from any type of computer which is connected to your network, for example a Windows PC, a Linux PC, A Mac, a smartphone, etc. In a classroom, each student can have access to a private area, and also a public area for sharing files.

Warning: Make sure that you store your important files in more than one location. If the hard disk connected to the RPi becomes faulty, you may not be able to access your files.

Note: There are two major classes of Network Attached Storage
# Low-power NAS. This is used as a safe or convenient place to store files for very occasional access. The priority is on low cost and low energy usage. This guide is suitable for this type of NAS.
# High-power NAS. This is used to provide instant access to files or to stream HD video. The priority is speed. This guide is NOT suitable for this type of NAS.

=What do you need?=

*A Raspberry Pi, model B.
*A boot SD card for the Raspberry Pi.
*A large USB-connected hard drive.
*An Ethernet cable to connect to the local network.

=What skill level is required?=

This project does not require any coding or compilation. Very basic Linux and networking knowledge would be useful, but not essential.

You need to...
*Edit configuration files on the RPi
*Enter basic Linux commands to configure users and passwords
*Use standard software tools (Windows/Linux/Mac) to add a network drive to your PC
*Connect computers using ethernet cables

=How does it work?=

The RPi is configured as a Samba server and can expose its files to any Samba client. Samba was originally a Windows-only protocol named Server Message Block (SMB), but has become popular for other operating systems.

There are other methods possible (for example ftp) but Samba is very popular because it is built into Windows and Mac OS X, and is very easy to install in all versions of Linux.

The end effect is that the PC user will be able to read and write to a new drive which appears to be locally-attached but is actually attached to the RPi.

Note that Samba is is very easy to use but is not suitable for high performance. You may not be able to access high-definition video quickly enough using Samba.

=Overview of this project=
This project includes instructions to configure the Samba server (where the files are stored centrally) and the Samba client (the user's computer). You must follow the instructions for one of the following servers and at least one of the following clients.

#Configure a Samba server on Fedora RPi
#Configure a Samba server on Debian RPi
#Configuring the Samba client on a Windows PC
#Configuring the Samba client on a Linux PC
#Configuring the Samba client on a Mac
#Configuring the Samba client on an Android smartphone

=Configure a Samba server on Fedora RPi=
'''Not available yet.''' Anybody is welcome to copy the Debian instructions into this section and edit as necessary.

=Configure a Samba server on Debian RPi=
==Before you start==
To follow the instructions below, you must enter commands into a terminal. You must open a terminal before starting the instructions below. If necessary, search the internet for instructions by using search terms like "open terminal Gnome" or "open terminal LXDE" etc depending on your chosen desktop environment.

You may find it useful to open a web browser on the RPi so you can copy commands from this web page and paste them into the terminal. This saves a lot of work and errors. Most terminal programs allow you to paste by using a menu selections "Edit" then "Paste".

If you do not understand a command, do not paste it in blindly. You can learn more about commands by reading the manual, by using the "man" command. For example, to find out more about the mkdir command, give the command "man mkdir". Press "q" to exit the man program.

A lot of commands start with "sudo". The sudo prefix allows a normal user to enter commands which will affect all other users of the system.

==Move home directory to a large USB disk==
'''This section has not been decided yet. Only important if the user wishes to use a large external disk'''

How to do this easily? Lots of ways, but we need one that is guaranteed to work for an absolute beginner.

See the "discussion" tab for more details.

==Connect the RPi to a network==
Check that you have an internet connection.

Command:
ping www.google.com
Expect something like
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n
64 bytes from a.b.c.d: icmp_seq=n ttl=n time=n

where a, b, c d and n are replaced by numbers.

Press Control-C to stop the ping program

If you do not see the above response, you do not have an internet connection, so this must be fixed before you can continue.

==Install the samba software==

Command:
sudo apt-get install samba

Expect:
Do you want to continue? [Y/n]
Answer by pressing "y", then the [enter] key.

Make a copy of your samba configuration file, just in case something goes wrong with later instructions.

Command:
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.old

==Check if the RPi has a network host name defined==

Command:
cat /etc/hostname

Expect something like:
RaspberryPi

If you want to change the hostname, for example, to "bigdisk"

Command:
sudo echo bigdisk > /etc/hostname
sudo hostname bigdisk
sudo nano /etc/hosts
In the file /etc/hosts, change any occurrence of the old host name to the new host name.
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

'''Note:''' Do not use special characters in your host name. To be safe, only use letters and numbers. Never use apostrophes or spaces, as for example "John's Disk".

Examples in this guide use a host name of "bigdisk". If you select a different host name, please remember this when using the later examples.

Restart the RPi to force it to use the new host name. Warning: First, close any other programs that you may have running on the RPi.

Command:
sudo reboot

==Enable security on the Samba server on the RPi==
'''Note: This section is optional, but highly recommended. It forces the samba server to ask for a username and password before allowing another computer to connect.'''

Edit the samba configuration file
sudo nano /etc/samba/smb.conf
Search for the section marked ##### Authentication #####

Change the text
; security = user
to
security = user
Note that you must use the arrow keys to move around in the nano editor, you cannot use the mouse.

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
sudo /etc/init.d/samba restart

Expect:
smbd start/running, process n

==Configure private storage areas on the RPi==
Configure samba to allow each user to access his home directory.

Open the smb.conf file in nano
sudo nano /etc/samba/smb.conf
Search for the section starting [homes]

For each line in this section which begin with the ";" character, delete the ";" character.

The important lines should now look like

[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S

In the [homes] section, change from
read only = yes
to
read only = no

Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

If the required user does not already exist, add a new user
sudo useradd john -m -G users
sudo passwd john
You will be asked to enter the new password twice.

Allow this user to be a samba user
sudo smbpasswd -a john
You will be asked to enter the new password twice.

==Configure a public storage area on the RPi==
'''If you have more than one user, you may wish to define a public area where everybody can share files. This section is optional.'''

Create a directory to store public files
sudo mkdir /home/shares
sudo mkdir /home/shares/public
sudo chown -R root:users /home/shares/public
sudo chmod -R ug+rwx,o+rx-w /home/shares/public
Edit the samba configuration file
sudo nano /etc/samba/smb.conf
At the end of the file, add the following lines
[public]
comment = Public Storage
path = /home/shares/public
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
read only = no
Save the edited file
Press Control-X
Press y
Press [enter]

Restart samba to use the new configuration file.
/etc/init.d/samba restart

Expect:
smbd start/running, process n

=Configuring the Samba client on a Windows PC=
A Windows PC uses Samba automatically, no extra software is required.

In Windows, Network Attached Storage is known as a "network drive". Open up the Windows help and search for the term "network drive", you should see something like

[[File:RPI_NAS_Win1.JPG]]

If you follow the instructions, you will be asked to select a drive letter (Z: is default but you can select anything available) and the path to the network drive. (The following screen may be slightly different depending on your version of Windows)

[[File:RPI_NAS_Win2.JPG]]

Enter the path to the RPi and click on "Finish". The path is in the format \\computer_name\directory. In this example, the computer name is "bigdisk" and the user wishes to attach to the directory "john". Note that you may also enter the computer name in IP address format, such as "192.168.0.2".

If you enabled security on the RPi server, you will be asked for a username and a password.

[[File:RPI_NAS_Win3.JPG]]

This must be a valid username and password on the RPi server. To access a public area, any username is acceptable. To access a private area, the username must match the last part of the folder path (the part after the \ character).

Note that a Windows user can attach to multiple network drives at the same time. It is quite common for a user to attach to his private files (commonly drive H: is used to represent a home directory) and also attach to a public storage (commonly drive P: is used to represent a public drive).

=Configuring the Samba client on a Linux PC=
Not started yet.

Basic plan is to use the standard Linux package '''smbclient'''

=Configuring the Samba client on a Mac=

As with most OS X stuff the "it just works" fits this one. As long as; the Linux and Mac networking is setup right with both boxes on the same network and the "Finder Preferences" on the Mac is set to show "Connected Servers". When you open the "Finder" on the Mac the R-Pi's host name will show in the right of the finder window under the heading "SHARED". When you click on the name for the first time a message at the top of "Finder" window will show on the right "Connection Failed" with a button on the left marked "Connect as" press the button and the Mac will ask for "User name" and "Password" use the one set in the "SAMBA" setup and the shared discs will appear in the "Finder".

=Configuring the Samba client on an Android smartphone=
There are multiple Samba clients for Android. The following shows only one example called File Expert, but you can search for the text "smb" in the Android Market (Google Play) to find other apps.

Install the app "File Expert".

Open the app "File Expert"

Click on "Network"

Click on "Create new account"

Leave server domain empty

Set computer name to "bigdisk"

Set nickname to "john"

Set username to "john"

Set password to the password for John's account

Click on "Okay"

{{Template:Raspberry Pi}}

RPi Chromium

2012-05-29T10:15:09Z

Bredman: /* What does it do? */

[[Category:RaspberryPi]]
Back to [[RPi Guides]].

'''Adding Chromium web browser to a Raspberry Pi'''

=What does it do?=

This guide shows you how to install a Chromium web browser, which should be faster and more reliable than the standard Debian web browser.

=What do you need?=

*A Raspberry Pi, model B.
*A Debian SD card for the Raspberry Pi, size should be 2GB or larger.
*A network connection (Ethernet or WiFi).

=What skill level is required?=

Suitable for absolute beginners. No Linux knowledge is needed.

It is assumed that you have used a computer before, for example a Windows PC.

=Overview of this guide=
You need to
*Install Chromium software on the Raspberry Pi
*Start the Chromium web browser

=Installing the software=
Follow the instructions in [[RPi Install software]], using the command
'''sudo apt-get install chromium-browser'''

=Opening the Chromium web browser=
Enter the following command and press enter at the end.
'''startx'''
Wait for the desktop to finish loading.

Click on the LXDE icon (the strange X) in the bottom-left corner of the screen.

Move your mouse to point to "Internet".

Click on "Chromium Web Browser".

The Chromium web browser will open.

[[File:RPiChromiumMenu.jpg]]

RPi Chromium

2012-05-29T10:14:46Z

Bredman: Moved software install instructions to generic page

[[Category:RaspberryPi]]
Back to [[RPi Guides]].

'''Adding Chromium web browser to a Raspberry Pi'''

=What does it do?=

This guide shows you how to install a Chromium web browser, which should be faster and more reliable than the standard Debian web browser.

These instructions will show you how to install software from the command line. This is a very important skill if you wish to progress further with Linux.

=What do you need?=

*A Raspberry Pi, model B.
*A Debian SD card for the Raspberry Pi, size should be 2GB or larger.
*A network connection (Ethernet or WiFi).

=What skill level is required?=

Suitable for absolute beginners. No Linux knowledge is needed.

It is assumed that you have used a computer before, for example a Windows PC.

=Overview of this guide=
You need to
*Install Chromium software on the Raspberry Pi
*Start the Chromium web browser

=Installing the software=
Follow the instructions in [[RPi Install software]], using the command
'''sudo apt-get install chromium-browser'''

=Opening the Chromium web browser=
Enter the following command and press enter at the end.
'''startx'''
Wait for the desktop to finish loading.

Click on the LXDE icon (the strange X) in the bottom-left corner of the screen.

Move your mouse to point to "Internet".

Click on "Chromium Web Browser".

The Chromium web browser will open.

[[File:RPiChromiumMenu.jpg]]

RPi Install software

2012-05-29T10:11:06Z

Bredman: New page

[[Category:RaspberryPi]]
Back to [[RPi Guides]].

'''Installing a software package on a Raspberry Pi'''

=What does it do?=

This guide shows you how to install a software package on a Raspberry Pi.

These instructions will show you how to install software from the command line. This is a very important skill if you wish to progress further with Linux.

=What do you need?=

*A Raspberry Pi, model B.
*A Debian SD card for the Raspberry Pi, size should be 2GB or larger.
*A network connection (Ethernet or WiFi).

=What skill level is required?=

Suitable for absolute beginners. No Linux knowledge is needed.

It is assumed that you have used a computer before, for example a Windows PC.

=Installing the software=
Unplug the power cable from the Raspberry Pi.

Insert a Debian SD card in the Raspberry Pi.

Connect the Ethernet cable from your Raspberry Pi to a modem or other internet service. You may also use a WiFi device, but you may need help to get this working.

Connect the power cable. Log in with your username and password.

To check if your internet connection is working, enter the following command and press enter at the end.
'''ping -c 1 www.raspberrypi.org'''

If your internet connection is working, you should see a statistics report which contains the following
'''1 packets transmitted, 1 received, 0% packet loss'''

If you get an error message instead, or a report of 100% packet loss, you have a problem with your internet connection. You must ask somebody to help fix this problem before you can proceed.

Enter the following command and press enter at the end.
'''sudo apt-get install xxxx'''
where xxxx is the name of the software package that you wish to install.

For example, to install the software package chromium-browser, you should use the command
'''sudo apt-get install chromium-browser'''

You may be asked for your password. Enter your password and press enter. Note that you will not be able to see your password.

[[File:RPiInstallChromium1.jpg]]

You may be asked for permission (yes/no) to install new software.

[[File:RPiInstallChromium2.jpg]]

Press the 'y' key and enter to continue.

Wait for the installation to complete.

[[File:RPiInstallChromium3.jpg]]

The software installation is now finished.

=Removing the software=
''Use these instructions if you wish to remove a software package.''

Follow the instructions above to install the software, but use this command instead.
'''sudo apt-get remove xxxx'''
where xxxx is the name of the software package that you wish to remove.

RPiconfig

2012-05-29T09:22:32Z

Bredman: Added hdmi_force_hotplug

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=0x10
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''hdmi_force_hotplug''' overrides the normal selection of composite if no HDMI is detected
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type (default=1)

[rgh] I think values are 0 and 1 really, and the default 0 for CEA - at least with the latest firmware as of May 25th 2012.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. highter clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default matches display.

'''framebuffer_height''' console framebuffer height in pixels. Default matches display.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''hdmi_force_hotplug''' Make RPi ignore hotplug signal from display and assume it is asserted.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 80000000

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|}

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq
! gpu_freq
! core_freq
! h264_freq
! isp_freq
! v3d_freq
! sdram_freq
! over_voltage
! over_voltage_sdram
|-
|900
|250
|
|
|
|
|500
|
|
|-
|900
|350
|
|
|
|
|
|
|
|-
|1000
|
|
|
|
|
|
|6
|
|}

= Notes =
<references>

RPi Beginners

2012-05-23T15:00:32Z

Bredman: Deleted section - Change the root Password, this section is not suitable for beginners

[[Category:RaspberryPi]]
{{Template:RPi_Startup}}

''' INFO : If you are looking for any information related to SD Cards and setup look
[[RPi Easy SD Card Setup | here]] There is some restructuring going on , we are sorry for the inconvenience. '''

=About This Page - For Contributors=
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.

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)!

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.

----

=Where to start?=
Any easy question to ask, but a very difficult one to answer!
# If you need to get a RPi, the see the [[RPi Buying Guide|Buying Guide]].
# 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.
# If you need to install/setup an SD card see the [[RPi Easy SD Card Setup|Preload your Card]] section.
# If something is not working, check the [[R-Pi_Troubleshooting|Troubleshooting]] section.
# If you need help with Debian, try the [http://wiki.debian.org/FrontPage Debian Wiki].
# If you've done all that, and you are wondering what next...'''welcome and read on!'''

References needed (idea for new section Living Without RPi, which can guide users or link to info to users who haven't got RPis)
Link to emulation builds or live linux cds setup for beginners (RacyPy2 for example)
If you don't have a Raspberry Pi yet, you can still try things out, see xxxx for details.

=What is Linux and why not use Windows?=
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.

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.

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!

For more information about Linux see
[http://en.wikipedia.org/wiki/Linux Wikipedia]

Also see [http://elinux.org/RPi_End-user_FAQ End-User FAQ]
And [http://elinux.org/Will_RPi_Run Running XXX on the RPi]

=Basic Debian RPi Setup=
When you first turn on your Raspberry Pi with it's fresh Debian image on the SD card, you may have to make some minor adjustments to the OS configuration files to suit your location. The default location setting (locale) is the UK.

You can alter this with

sudo dpkg-reconfigure locales

There are quite a lot of options - many people will want to use the UTF-8 variant for their locale. This will also allow you to set anomalous cases
like English keyboard but Danish locale.

Selecting All locales will generate all possible locales, take a very long time and use a great deal of space. Generate only those you wish to use.

The command above will open a list which begins

aa_DJ [Ambala, for Djibouti] ISO-8059-1 and goes down to zu_._UTF8 UTF-81 [Zulu for S. Africa]

You have various options for each language - UTF-8 is probably the most useful worldwide - Unicode characters.

Scroll down using a down arrow key, toggle with a space bar to select.

==Keyboard Mapping==

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:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
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]

Also, see the [[R-Pi_Troubleshooting#Re-mapping_the_keyboard_with_Debian_Squeeze|Troubleshooting Guide]] for more information about remapping the keyboard.

Changes will certainly be picked up at the next restart.

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:
sudo setupcon

==Create a new User and add it to the sudoers list==

Type in following command in the Terminal to create a new user:
adduser username
Follow the Steps. After creating the new User you must get root Access with the following Command:
su
Now you can add your user to the sudoers list:
visudo
Add following Line under the "root ALL=(ALL) ALL" Line:
yourUsername ALL=(ALL) ALL
Now press CTRL+X.

Alternatively instead of adding the user to the sudoers list, you can add your user to the sudo group with the following command:
useradd -G sudo yourUsername

==Change the Timezone==
Unless you live in Great Britain, you'll have to change the default timezone. Use "sudo" to obtain temporary execute permissions.
sudo dpkg-reconfigure tzdata

Select geographic area - Europe, America or whatever. Etc gives UNIX compatible time zones including CUT, GMT, UTC

Select city

Follow the prompts to finish the config. The change should be immediate.

=Intro to the CLI (Command Line Interface)=
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.

For an introductory guide to some basic commands please see: [http://elinux.org/CLI_Spells Command Line Interface "Must Have" Commands]

=Adding more software to your Raspberry Pi=
You will probably want to add software to your Raspberry Pi. Here you can find out how to do it.
[http://elinux.org/Add_software Adding Software]

=Adding USB Storage to Your Raspberry Pi=
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]

=Beginner Projects=
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.

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.
Reference needed - a good guide on how to backup and restore cards or software to do this easily

==Media Player==
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).

DesignSpark have done a article on this, which is worth a look, [http://www.designspark.com/content/raspberry-pi-goes-movies DesignSpark - Raspberry Pi goes to the movies]

Reference needed - links to a specific wiki page covering this in detail or links to projects like
OpenElec, CrystalBuntu, Raspbmc etc

==Play Games==
While there are not any commercial games for the Raspberry Pi (yet) there are plenty ways to play games on it.

Many distributions will have games built into them, and some may well support emulation of other platforms so you can run those games.

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).

Reference needed - game section is empty at the moment!
''See the [[RPi Games|Games Section]] for more details''

==Introducing Young Children To Computers==
Reference needed - some kid friendly and fun stuff!

==Teaching==
There is a huge number of groups, links and resources available within the [[RPi Education|Education]] section.
Reference needed - links to the learning pages, education links and school/university groups

==Learn To Program==
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.

There is a huge selection to choose from (not just Python...) which should suit any ability and a range of purposes.

If you are new to programming, there are plenty of tutorials for getting started in the [[RPi Tutorials|Tutorials]] Section.

Books about programming can be found in the [[RPi Programming Books|Books]] Section.

In the latest Debian, Python (+Pygame) and MIT Scratch are pre-installed.

Reference needed - links to the learning pages, recommended books?

==Interface With Hardware==
# [[RPi Interfacing with hardware|Interfacing with Arduino]]

Reference needed - links to basic circuits tutorials and expansion boards

==Word Processing/Internet Browsing etc==
Yes, the Raspberry Pi can do the majority of the dull stuff too which other computers do.

'''Debian''' currently comes with Midori installed for web browsing and word processing programs be installed rather easily.

*Entering "sudo apt-get install openoffice.org" into a terminal will install OpenOffice.org, a free Microsoft Office-like application suite
*Entering "sudo apt-get install abiword-common" into a terminal will install AbiWord, a lighter weight but still fully functional word processor

More information needed

==Your Own Pet Project!==
The sky is the limit really, with some time and effort any number of projects can be achieved.

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.

Of course, if you do anything interesting then please let us know in the [[RPi Projects |Projects]] section.

=Living Without RPi=
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.

==Using Linux==
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).

RacyPy - This is a simple LiveCD of Puppy Linux which includes some basic programming languages and a light-weight graphical user interface (GUI).

You can get it from here:

[http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ teampython RacyPy]

==Trying Programming==
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.

==Controlling Hardware==
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).

=References=
<references/>
{{Template:Raspberry Pi}}

RPi VerifiedPeripherals

2012-05-22T15:06:01Z

Bredman: /* Working USB Wifi Adapters */

[[Category: Linux]]
[[Category: ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template: RPi_Hardware}}

==Notes==

19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the [http://www.raspberrypi.org/downloads default Debian distribution] unless stated otherwise. A suggested suffix markup scheme is as follows:

* (A) - Relates to model A production board
* (B) - Relates to model B production board
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different
* No markup - relates to all production boards

''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''

If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.

{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}

== Powered USB Hubs ==
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.

===Working USB Hubs===
*'''Belkin'''
** F5U224 4 port powered USB hub
** F5U231 Hi-speed USB 2.0 Tertrahub - 4 port powered USB hub
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub
*'''Logik'''
** LP4HUB10 4-Port USB Hub
*'''LogiLink'''
** UA0096 USB 2.0 Hub, 10-Port with PSU 5V, 3.5A
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A
*'''Targus'''
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)

===Problem USB Hubs===
*'''Unbranded / Multiple Brands'''
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref>

== USB Remotes ==
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

== USB Keyboards ==
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.
=== Working USB Keyboards ===
The following is a list of specific keyboards known to work and which appear to be fault-free.

* '''A4 Tech'''
** Model KL-5 USB Keyboard, 20mA.

* '''Acer'''
** Compact Keyboard KU-0906 (B) (Also known as Genius LuxeMate i200 Keyboard)
** Wireless Keyboard And Mouse Bundle KG-0917 (B)

* '''Apple'''
** Apple Keyboard (109 keys) A1048
** Apple Keyboard with Numeric Keypad (aluminium/wired) A1243

* '''Asda'''
** Premium Wireless Keyboard (white keys, silver back) HK8028

* '''Cerulian'''
** Mini wireless keyboard and mouse deskset (B)

* '''Cherry'''
** CyMotion Master Linux (B)

* '''Dell'''
** SK-8135 (B)
** SK-8115 (B)
** L100 (B)

* '''Fujitsu Siemens'''
** KB SC USB UK (!)
** KB910 USB, with led light on the highest level (B)
** KB400 USB US

* '''Genius'''
** KB-06XE (K639) (B)
** Slimstar 8000 wireless keyboard

* '''HP'''
** KG-1061

* '''KeySonic'''
** ACK-540RF
** ACK-3700C

* '''Lenovo'''
** SK-8825 UK (B)
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B)

* '''Logitech'''
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** Wii wireless keyboard KG-0802 (!)
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)
** MK 250 wireless keyboard and mouse
** K400 wireless keyboard with touchpad (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** K120 Keyboard (B)
** K200 Keyboard (B)

* '''Microsoft'''
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)

* '''SteelSeries'''
** Merc keyboard (B)

*'''Tesco'''
**Value Keyboard VK109 (B)

* '''Trust'''
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust ClassicLine Keyboard http://trust.com/17184

* '''Xenta'''
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)

===Problem USB Keyboards===

* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Microsoft'''
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)
** Arc wireless - Keyboard has 'sticky' keys. (B)
* '''Novatech'''
** (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B) <ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Logitech'''
** Logitech Illuminated Keyboard (unstable; not working with led light on; testet both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)
* '''Razor'''
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.
* '''Trust'''
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.

== USB Mouse devices ==
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.

===Working USB Mouse Devices===
The following is a list of specific mouse devices known to work and which appear to be fault-free.

* '''Belkin'''
**F8E882-OPT (B)

* '''Dell'''
** M-UVDEL1 (B)
** M056U0A (B)

* '''Genius'''
** GM-04003A (B)
** Slimstar 8000 wireless mouse

* '''Microsoft'''
** Compact optical mouse 500 V2.0 (B)
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)
** Microsoft Intellimouse Optical Mouse
** Microsoft Wireless Mobile Mouse 3500
** Microsoft Wireless Mobile Mouse 4000

* '''Logitech'''
** MX320/MX400 laser mouse. (B)
** M505 USB wireless laser, model no: 910-001324 (B)
** M-BJ79 (B)
** LX-700 Cordless Desktop Receiver (B)
** Logitech Wireless Gaming Mouse G700. (B)
** Optical wheel mouse. (B)

* '''Technika'''
** TKOPTM2 (B)

* '''Tesco'''
** Wired optical mouse M211 (B)

* '''Generic'''
** Generic 2.4GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)

== USB WiFi Adapters ==

See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing

There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.

===Working USB Wifi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.

'''Note:''' A WiFi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the WiFi adapter to the WiFi Access Point. Therefore, you may need to plug the WiFi adapter into a powered USB hub.

* '''3COM'''
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)
* '''Asus'''
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] compiled manufacturer driver for RTL8192CU per [http://www.raspberrypi.org/forum/troubleshooting/trying-to-get-an-rtl8188cus-wireless-usb-nic-working instructions] (B)
* '''Belkin'''
** Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]. On Debian requires the firmware-ralink package from the non-free repository. The usbcore module needs to be added to /etc/modules [http://www.penguintutor.com/blog/viewblog.php?blog=6281 install instructions].
* '''BlueProton'''
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora & Arch; rtl8187 driver (B)
* '''D-Link'''
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository.
* '''Edimax'''
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP ([http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html howto]) (B)
* '''Gigabyte'''
** Gigabyte GN-WB32L 802.11n USB WLAN Card. Works with the rt2800usb driver.
* '''IOGear'''
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
* '''Micronet'''
** Wireless USB adapter (uses Realtek rtl8188cus) works plugged directly into R-Pi USB (B)
* '''Netgear'''
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the <code>firmware-atheros</code> package from the <code>squeeze-backports</code> non-free repository (!)
** WG111v2: Realtek rtl8187 chipset (!)
* '''OvisLink'''
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink
* '''Ralink'''
** [http://www.dx.com/p/24688 RT2070] USB-ID 148f:2070 ([http://wiki.debian.org/rt2870sta requires firmware])
** [http://www.element14.com/community/docs/DOC-44703 RT2501/RT2573] USB-ID 148f:2573 (firmware required) (B)
** RT5370 USB-ID 148f:5370 ([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from wheezy]) (B)
* '''Sempre'''
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/
* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
* '''TP-Link'''
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)
* '''ZyXEL'''
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)

===Problem USB Wifi Adapters===

These adapters were tested and found to have issues the Raspberry Pi.

* '''Realtek'''
** RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)
* '''Trendnet'''
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)
* '''TP-Link'''
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; errors with LXDE running (B)

== USB Bluetooth adapters ==
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)

== USB Ethernet adapters ==

== USB IR Receivers==

== USB TV Tuners and DVB devices==
*August
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Pi itself. Tested with Astra 19.2E radio and SD-TV channels

== USB Webcam ==
*Sony
**PlayStation Eye (for PlayStation 3)

== USB GPS devices ==
*Royaltek
**Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually
*Garmin
**Garmin eTrex Vista HCx: Works but may draw much power. To get it working (software part): https://wiki.openstreetmap.org/wiki/USB_Garmin_on_GNU/Linux
*Wintec
**WBT-200: No problem on Debian

== USB UART adapters ==
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.

== Other, exotic USB devices ==
*PEAK-System (www.peak-system.com)
**PCAN-USB using the driver (kernel module) from http://www.peak-system.com/fileadmin/media/linux/index.htm
*Tellstick (www.telldus.com)
**Depends on libftdi1

== Power adapters ==
The Raspberry Pi uses a standard Micro USB (type B) power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.

===Wired Adaptors===
* '''All HTC mobile phone adaptors'''
** 5V 1A TCP-300 Single port USB mains phone charger (B)
* '''Amazon'''
** 5V 0.85A USB charger for Kindle
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** 5V 0.7A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
* '''HP'''
** 5V 2A Charger for HP Touchpad (B)
* '''HTC'''
** 5V 1A USB charger
* '''LG'''
** Travel Adapter (4.8V, 1.0A)
* '''Maplin Electronics'''
** 5V 1A dual USB power supply, model number H25B-MT-K2
* '''Nokia'''
** 5V 1.2A AC-10E Charger
* '''Noname'''
** 5V 2.1A KMS-AC09 4 port USB charger (B) [http://www.miniinthebox.com/kms-ac09-universal-ac-adapter-for-ipad-ipad-2-iphone-white_p208568.html]
* '''Novatel Wireless'''
** 5V 1.05A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5V 0.7A Charger for Orange San Francisco
* '''Palm'''
** 5V 1A Charger for Palm Pixi+ (B)
* '''Samsung'''
** 5V 0.7A Charger for Galaxy SII
* '''Sony Ericsson'''
** 5V 0.7A Charger CST-80

===External Batteries===
* ''' New Trent'''
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)
* ''' Sinoele'''
** Movpower - Power Bank 5200mAh (8hrs with Wifi active)

== Display adapters ==
While technically there shouldn't be a difference between one (for example) HDMI->DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI->DVI, CompositeRCA->SCART, CompositeRCA->VGA ''boxes/chipsets'', and HDMI->VGA ''boxes/chipsets''.

===HDMI->DVI-D===
None explicitly mentioned
===HDMI->VGA converter boxes===
Note that the [[RPi_config.txt]] file will have to be edited if the converter or VGA monitor does not support 1080p resolution, this is because the Rpi cannot detect the resolution. initially setting to VGA resolution is probably best

According to user "asb" -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.

This adapter (from Kanaan) -- http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- is working. Quality not wonderful, but certainly usable, on 1400x900 monitor.

According to user "na1pir" -- http://www.ebay.com/itm/BK-HDMI-Male-to-VGA-RGB-Female-HDMI-to-VGA-Video-Converter-adapter-1080P-for-PC-/140742987581

===Composite->SCART===
None explicitly mentioned
===Composite->VGA converter boxes===
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low
== SD cards ==

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.)
For this reason, please specify product numbers in the lists below, when possible.

===Working SD Cards===
* '''Adata'''
** 8GB SDHC Class 10 (AUSDH8GCL10-R)
** 16GB SDHC Class 6
* '''Dane-Elec'''
** 16GB SDHC Class 4
* '''Duracell'''
** 4GB SDHC Class 4
** 16GB SDHC Class 10 (labelled Pro Photo 200x)
* '''Extrememory'''
** 16GB SDHC Class 10
* '''Hama'''
** 8GB SDHC High Speed Pro Class 6
* '''HP'''
** 8GB SDHC Class 4 (doesn't reboot during first time startup process, but restart again and fine after that).
* '''Integral'''
** 8GB SDHC Ultima Pro Class 6 (Works - initial error -110 but boots within 5 seconds with no further errors or issues)
** [http://www.amazon.co.uk/gp/product/B0047T6XME 16GB SDHC Class 10 Ultima Pro (20MB/s)]
* '''Kingmax'''
** 4GB SDHC Class 2
** 4GB microSDHC Class 4 (KM04GMCSDHC4) won`t reboot when it`s hot
* '''Kingston'''
** 2GB SD
** 4GB microSD Class 4
** 4GB SDHC Class 4 (SD4/4GB)
** 8GB SDHC Class 4
** 8GB microSDHC Class 4
** 8GB SDHC Class 10 (SD10G2/8GB, SD10V/8GB, ultimateX 100X, ultimateX 120X)
** 16GB SDHC Class 10 (SD10G2/16GB, ultimateX 100X)
* '''Kodak'''
** 4GB SDHC Class 2
** 8GB SDHC Class 4
* '''Kruidvat'''
** 8GB SDHC Class 4
* '''Lexar'''
** 4GB SDHC Class 4 (Boots consistently and no error messages in log after 1/2 hour use )
** 4GB SDHC Class 6 Platinum II (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])
** 8GB SDHC Class 4
** 8GB SDHC Class 6 Platinum II
** 16GB SDHC Class 6 Platinum II
* '''Microcenter Brand (sold in bins at checkout)'''
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]
* '''MyMemory'''
** 8GB SDHC Class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10] (Latest batch not working)
* '''Optima'''
** 8GB SDHC Class 10 (Pro-Speed)
* '''Panasonic'''
** 8GB SDHC Class 6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])
* '''Peak'''
** 4GB microSDHC Class 4 (MMBTR04GUBCA-ME) tested with Arch
* '''Play.com'''
** 4GB SDHC Class 6 (S4E3CD04GEFAA 0907090121106)
* '''PNY'''
** 4GB SDHC Class 4
** Optima 4GB SDHC Class 4 (SD-K04G 0834TT1297Y)
** 16GB SDHC Class 4
* '''Samsung'''
** 4GB SDHC
** 8GB SDHC
** 8GB SDHC Class 10 (MB-MP8GA)
** 16GB SDHC Class 6 (MB-SSAGAEU)
** 16GB SDHC Class 10 (MB-SPAGA aka MB-SPAGAEU)
* '''SanDisk'''
** 2GB SD, white "SanDisk for Wii" branded, no class mentioned
** 2GB SD (with a circle 2 --probably class 2), writes at 3.5 Mb/s
** 2GB SD Class 4 Ultra (15MB/s)
** 2GB SD Class 4 Ultra II
** 2GB SD Extreme III (BE0715105083B)
** 4GB SDHC Class 4
** 4GB SDHC Class 4 Ultra II
** 4GB SDHC Class 4 Ultra (SDSDH-004G-U46) won`t reboot when it`s hot
** 4GB SDHC Class 6 Ultra (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)
** 4GB SDHC Class 10 Extreme (BH10297143382G)
** 8GB SDHC Class 4 (writes at ~1.5MB/s)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) (could be problematic, see below)
** 8GB SDHC Class 6 Ultra labelled as 20MB/s (BI11321422083D)
** 8GB SDHC Class 10 Extreme (BI11017514367G)
** 16GB SDHC Class 4
** 32GB SDHC Class 6
** 4GB microSDHC Class 2
** 4GB microSDHC Class 4
** 8GB microSDHC Class 2
** 8GB microSDHC Class 4
** 8GB microSDHC Class 6 Mobile Ultra (SDSDQY-008G-U46A) working with the latest firmware, won`t reboot when it`s hot
* '''Silicon Power'''
** 4GB microSDHC Class 6 (SP004GBSTH006V10-SP)
* '''Sony'''
** 4GB SDHC Class 4 (SF-4B4) (Write 6MB/s, Read 20MB/s)
* '''TDK'''
** 4GB SDHC Class 4 (1008WW5261B)
* '''Toshiba'''
** SD-C08GJ(BL3A (8GB mircoSD with Adapter)
* '''Transcend'''
** 4GB SDHC Class 4 - we've found these to work without any errors and offer reasonable performance
** 4GB SDHC Class 4 (TS4GSDHC4 - BH1130821915G)
** 4GB SDHC Class 6 (TS4GSDHC6) - no problems.
** 8GB SDHC Class 4
** 8GB SDHC Class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)
** 8GB SDHC Class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]
** 16GB SDHC Class 6 (TS16GSDHC6)
** 16GB SDHC Class 10 (TS16GSDHC10)

Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).

===Problem SD Cards===

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]

This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.
* '''Adata'''
** 16GB SDHC Class 6 (Possibly SD5MY168G0, label with gold <> black gradient) - Doesn't boot
* '''GSkill'''
** 32GB SDHC Class 10
* '''Panasonic'''
** 8GB SDHC Class 10 (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]
* '''Patriot'''
** 8GB SDHC Class 10 (PSF8GSDHC10)
* '''SanDisk'''
** 4GB SDHC Class 2 - Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt.
** 4GB SDHC Class 4 (BH1030216016G) - Doesn't boot.
** 4GB SDHC Class 6 Extreme (BH0822411730D)
** 4GB SDHC Class 10 Extreme (30 MB/s HD Video) (Doesn't boot)
** 8GB SDHC Class 6 Ultra (B11201421964G)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra labelled as 30MB/s (BI1208721965G)) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra I (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Extreme (BI1101116253G)
** 8GB SDHC Class 10 Extreme (BI1108716254G)
** 8GB SDHC Class 10 Extreme (BI1201516254G) [[http://www.amazon.co.uk/gp/product/B00422FBJ2 amazon.co.uk]]
** 8GB SDHC Class 10 Extreme Pro- Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 6 Ultra (BL1202021933G)
** 16GB SDHC Class 6 Ultra I (BL1205921933G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 10 Extreme (45MB/s U1)
* '''Kingston'''
** 4GB SDHC Class 6 - Boots kernel but won't run init (times out)
* '''Integral'''
** 16GB SDHC Class 6 Ultima Pro (SH016GAA2BB)
** 4GB SDHC class 4 (S404G1115)
* '''PNY'''
** 32GB SDHC Class 10 Professional (P-SDHC32G10-EF) from [http://www.play.com/Electronics/Electronics/4-/18814903/-/Product.html play.com] (mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)

The usual warnings against less reputable sellers (such as Ebay merchants) apply.

Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):

mmc0: timeout waiting for hardware interrupt

=== Benchmarks ===

* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}

RPi VerifiedPeripherals

2012-05-22T15:05:33Z

Bredman: /* Working USB Wifi Adapters */

[[Category: Linux]]
[[Category: ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template: RPi_Hardware}}

==Notes==

19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the [http://www.raspberrypi.org/downloads default Debian distribution] unless stated otherwise. A suggested suffix markup scheme is as follows:

* (A) - Relates to model A production board
* (B) - Relates to model B production board
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different
* No markup - relates to all production boards

''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''

If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.

{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}

== Powered USB Hubs ==
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.

===Working USB Hubs===
*'''Belkin'''
** F5U224 4 port powered USB hub
** F5U231 Hi-speed USB 2.0 Tertrahub - 4 port powered USB hub
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub
*'''Logik'''
** LP4HUB10 4-Port USB Hub
*'''LogiLink'''
** UA0096 USB 2.0 Hub, 10-Port with PSU 5V, 3.5A
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A
*'''Targus'''
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)

===Problem USB Hubs===
*'''Unbranded / Multiple Brands'''
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref>

== USB Remotes ==
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

== USB Keyboards ==
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.
=== Working USB Keyboards ===
The following is a list of specific keyboards known to work and which appear to be fault-free.

* '''A4 Tech'''
** Model KL-5 USB Keyboard, 20mA.

* '''Acer'''
** Compact Keyboard KU-0906 (B) (Also known as Genius LuxeMate i200 Keyboard)
** Wireless Keyboard And Mouse Bundle KG-0917 (B)

* '''Apple'''
** Apple Keyboard (109 keys) A1048
** Apple Keyboard with Numeric Keypad (aluminium/wired) A1243

* '''Asda'''
** Premium Wireless Keyboard (white keys, silver back) HK8028

* '''Cerulian'''
** Mini wireless keyboard and mouse deskset (B)

* '''Cherry'''
** CyMotion Master Linux (B)

* '''Dell'''
** SK-8135 (B)
** SK-8115 (B)
** L100 (B)

* '''Fujitsu Siemens'''
** KB SC USB UK (!)
** KB910 USB, with led light on the highest level (B)
** KB400 USB US

* '''Genius'''
** KB-06XE (K639) (B)
** Slimstar 8000 wireless keyboard

* '''HP'''
** KG-1061

* '''KeySonic'''
** ACK-540RF
** ACK-3700C

* '''Lenovo'''
** SK-8825 UK (B)
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B)

* '''Logitech'''
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** Wii wireless keyboard KG-0802 (!)
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)
** MK 250 wireless keyboard and mouse
** K400 wireless keyboard with touchpad (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** K120 Keyboard (B)
** K200 Keyboard (B)

* '''Microsoft'''
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)

* '''SteelSeries'''
** Merc keyboard (B)

*'''Tesco'''
**Value Keyboard VK109 (B)

* '''Trust'''
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust ClassicLine Keyboard http://trust.com/17184

* '''Xenta'''
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)

===Problem USB Keyboards===

* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Microsoft'''
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)
** Arc wireless - Keyboard has 'sticky' keys. (B)
* '''Novatech'''
** (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B) <ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Logitech'''
** Logitech Illuminated Keyboard (unstable; not working with led light on; testet both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)
* '''Razor'''
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.
* '''Trust'''
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.

== USB Mouse devices ==
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.

===Working USB Mouse Devices===
The following is a list of specific mouse devices known to work and which appear to be fault-free.

* '''Belkin'''
**F8E882-OPT (B)

* '''Dell'''
** M-UVDEL1 (B)
** M056U0A (B)

* '''Genius'''
** GM-04003A (B)
** Slimstar 8000 wireless mouse

* '''Microsoft'''
** Compact optical mouse 500 V2.0 (B)
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)
** Microsoft Intellimouse Optical Mouse
** Microsoft Wireless Mobile Mouse 3500
** Microsoft Wireless Mobile Mouse 4000

* '''Logitech'''
** MX320/MX400 laser mouse. (B)
** M505 USB wireless laser, model no: 910-001324 (B)
** M-BJ79 (B)
** LX-700 Cordless Desktop Receiver (B)
** Logitech Wireless Gaming Mouse G700. (B)
** Optical wheel mouse. (B)

* '''Technika'''
** TKOPTM2 (B)

* '''Tesco'''
** Wired optical mouse M211 (B)

* '''Generic'''
** Generic 2.4GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)

== USB WiFi Adapters ==

See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing

There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.

===Working USB Wifi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.

'''Note:''' A WiFi adaptor will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the WiFi adaptor to the WiFi Access Point. Therefore, you may need to plug the WiFi adaptor into a powered USB hub.

* '''3COM'''
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)
* '''Asus'''
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] compiled manufacturer driver for RTL8192CU per [http://www.raspberrypi.org/forum/troubleshooting/trying-to-get-an-rtl8188cus-wireless-usb-nic-working instructions] (B)
* '''Belkin'''
** Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]. On Debian requires the firmware-ralink package from the non-free repository. The usbcore module needs to be added to /etc/modules [http://www.penguintutor.com/blog/viewblog.php?blog=6281 install instructions].
* '''BlueProton'''
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora & Arch; rtl8187 driver (B)
* '''D-Link'''
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository.
* '''Edimax'''
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP ([http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html howto]) (B)
* '''Gigabyte'''
** Gigabyte GN-WB32L 802.11n USB WLAN Card. Works with the rt2800usb driver.
* '''IOGear'''
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
* '''Micronet'''
** Wireless USB adapter (uses Realtek rtl8188cus) works plugged directly into R-Pi USB (B)
* '''Netgear'''
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the <code>firmware-atheros</code> package from the <code>squeeze-backports</code> non-free repository (!)
** WG111v2: Realtek rtl8187 chipset (!)
* '''OvisLink'''
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink
* '''Ralink'''
** [http://www.dx.com/p/24688 RT2070] USB-ID 148f:2070 ([http://wiki.debian.org/rt2870sta requires firmware])
** [http://www.element14.com/community/docs/DOC-44703 RT2501/RT2573] USB-ID 148f:2573 (firmware required) (B)
** RT5370 USB-ID 148f:5370 ([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from wheezy]) (B)
* '''Sempre'''
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/
* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
* '''TP-Link'''
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)
* '''ZyXEL'''
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)

===Problem USB Wifi Adapters===

These adapters were tested and found to have issues the Raspberry Pi.

* '''Realtek'''
** RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)
* '''Trendnet'''
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)
* '''TP-Link'''
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; errors with LXDE running (B)

== USB Bluetooth adapters ==
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)

== USB Ethernet adapters ==

== USB IR Receivers==

== USB TV Tuners and DVB devices==
*August
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Pi itself. Tested with Astra 19.2E radio and SD-TV channels

== USB Webcam ==
*Sony
**PlayStation Eye (for PlayStation 3)

== USB GPS devices ==
*Royaltek
**Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually
*Garmin
**Garmin eTrex Vista HCx: Works but may draw much power. To get it working (software part): https://wiki.openstreetmap.org/wiki/USB_Garmin_on_GNU/Linux
*Wintec
**WBT-200: No problem on Debian

== USB UART adapters ==
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.

== Other, exotic USB devices ==
*PEAK-System (www.peak-system.com)
**PCAN-USB using the driver (kernel module) from http://www.peak-system.com/fileadmin/media/linux/index.htm
*Tellstick (www.telldus.com)
**Depends on libftdi1

== Power adapters ==
The Raspberry Pi uses a standard Micro USB (type B) power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.

===Wired Adaptors===
* '''All HTC mobile phone adaptors'''
** 5V 1A TCP-300 Single port USB mains phone charger (B)
* '''Amazon'''
** 5V 0.85A USB charger for Kindle
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** 5V 0.7A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
* '''HP'''
** 5V 2A Charger for HP Touchpad (B)
* '''HTC'''
** 5V 1A USB charger
* '''LG'''
** Travel Adapter (4.8V, 1.0A)
* '''Maplin Electronics'''
** 5V 1A dual USB power supply, model number H25B-MT-K2
* '''Nokia'''
** 5V 1.2A AC-10E Charger
* '''Noname'''
** 5V 2.1A KMS-AC09 4 port USB charger (B) [http://www.miniinthebox.com/kms-ac09-universal-ac-adapter-for-ipad-ipad-2-iphone-white_p208568.html]
* '''Novatel Wireless'''
** 5V 1.05A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5V 0.7A Charger for Orange San Francisco
* '''Palm'''
** 5V 1A Charger for Palm Pixi+ (B)
* '''Samsung'''
** 5V 0.7A Charger for Galaxy SII
* '''Sony Ericsson'''
** 5V 0.7A Charger CST-80

===External Batteries===
* ''' New Trent'''
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)
* ''' Sinoele'''
** Movpower - Power Bank 5200mAh (8hrs with Wifi active)

== Display adapters ==
While technically there shouldn't be a difference between one (for example) HDMI->DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI->DVI, CompositeRCA->SCART, CompositeRCA->VGA ''boxes/chipsets'', and HDMI->VGA ''boxes/chipsets''.

===HDMI->DVI-D===
None explicitly mentioned
===HDMI->VGA converter boxes===
Note that the [[RPi_config.txt]] file will have to be edited if the converter or VGA monitor does not support 1080p resolution, this is because the Rpi cannot detect the resolution. initially setting to VGA resolution is probably best

According to user "asb" -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.

This adapter (from Kanaan) -- http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- is working. Quality not wonderful, but certainly usable, on 1400x900 monitor.

According to user "na1pir" -- http://www.ebay.com/itm/BK-HDMI-Male-to-VGA-RGB-Female-HDMI-to-VGA-Video-Converter-adapter-1080P-for-PC-/140742987581

===Composite->SCART===
None explicitly mentioned
===Composite->VGA converter boxes===
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low
== SD cards ==

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.)
For this reason, please specify product numbers in the lists below, when possible.

===Working SD Cards===
* '''Adata'''
** 8GB SDHC Class 10 (AUSDH8GCL10-R)
** 16GB SDHC Class 6
* '''Dane-Elec'''
** 16GB SDHC Class 4
* '''Duracell'''
** 4GB SDHC Class 4
** 16GB SDHC Class 10 (labelled Pro Photo 200x)
* '''Extrememory'''
** 16GB SDHC Class 10
* '''Hama'''
** 8GB SDHC High Speed Pro Class 6
* '''HP'''
** 8GB SDHC Class 4 (doesn't reboot during first time startup process, but restart again and fine after that).
* '''Integral'''
** 8GB SDHC Ultima Pro Class 6 (Works - initial error -110 but boots within 5 seconds with no further errors or issues)
** [http://www.amazon.co.uk/gp/product/B0047T6XME 16GB SDHC Class 10 Ultima Pro (20MB/s)]
* '''Kingmax'''
** 4GB SDHC Class 2
** 4GB microSDHC Class 4 (KM04GMCSDHC4) won`t reboot when it`s hot
* '''Kingston'''
** 2GB SD
** 4GB microSD Class 4
** 4GB SDHC Class 4 (SD4/4GB)
** 8GB SDHC Class 4
** 8GB microSDHC Class 4
** 8GB SDHC Class 10 (SD10G2/8GB, SD10V/8GB, ultimateX 100X, ultimateX 120X)
** 16GB SDHC Class 10 (SD10G2/16GB, ultimateX 100X)
* '''Kodak'''
** 4GB SDHC Class 2
** 8GB SDHC Class 4
* '''Kruidvat'''
** 8GB SDHC Class 4
* '''Lexar'''
** 4GB SDHC Class 4 (Boots consistently and no error messages in log after 1/2 hour use )
** 4GB SDHC Class 6 Platinum II (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])
** 8GB SDHC Class 4
** 8GB SDHC Class 6 Platinum II
** 16GB SDHC Class 6 Platinum II
* '''Microcenter Brand (sold in bins at checkout)'''
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]
* '''MyMemory'''
** 8GB SDHC Class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10] (Latest batch not working)
* '''Optima'''
** 8GB SDHC Class 10 (Pro-Speed)
* '''Panasonic'''
** 8GB SDHC Class 6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])
* '''Peak'''
** 4GB microSDHC Class 4 (MMBTR04GUBCA-ME) tested with Arch
* '''Play.com'''
** 4GB SDHC Class 6 (S4E3CD04GEFAA 0907090121106)
* '''PNY'''
** 4GB SDHC Class 4
** Optima 4GB SDHC Class 4 (SD-K04G 0834TT1297Y)
** 16GB SDHC Class 4
* '''Samsung'''
** 4GB SDHC
** 8GB SDHC
** 8GB SDHC Class 10 (MB-MP8GA)
** 16GB SDHC Class 6 (MB-SSAGAEU)
** 16GB SDHC Class 10 (MB-SPAGA aka MB-SPAGAEU)
* '''SanDisk'''
** 2GB SD, white "SanDisk for Wii" branded, no class mentioned
** 2GB SD (with a circle 2 --probably class 2), writes at 3.5 Mb/s
** 2GB SD Class 4 Ultra (15MB/s)
** 2GB SD Class 4 Ultra II
** 2GB SD Extreme III (BE0715105083B)
** 4GB SDHC Class 4
** 4GB SDHC Class 4 Ultra II
** 4GB SDHC Class 4 Ultra (SDSDH-004G-U46) won`t reboot when it`s hot
** 4GB SDHC Class 6 Ultra (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)
** 4GB SDHC Class 10 Extreme (BH10297143382G)
** 8GB SDHC Class 4 (writes at ~1.5MB/s)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) (could be problematic, see below)
** 8GB SDHC Class 6 Ultra labelled as 20MB/s (BI11321422083D)
** 8GB SDHC Class 10 Extreme (BI11017514367G)
** 16GB SDHC Class 4
** 32GB SDHC Class 6
** 4GB microSDHC Class 2
** 4GB microSDHC Class 4
** 8GB microSDHC Class 2
** 8GB microSDHC Class 4
** 8GB microSDHC Class 6 Mobile Ultra (SDSDQY-008G-U46A) working with the latest firmware, won`t reboot when it`s hot
* '''Silicon Power'''
** 4GB microSDHC Class 6 (SP004GBSTH006V10-SP)
* '''Sony'''
** 4GB SDHC Class 4 (SF-4B4) (Write 6MB/s, Read 20MB/s)
* '''TDK'''
** 4GB SDHC Class 4 (1008WW5261B)
* '''Toshiba'''
** SD-C08GJ(BL3A (8GB mircoSD with Adapter)
* '''Transcend'''
** 4GB SDHC Class 4 - we've found these to work without any errors and offer reasonable performance
** 4GB SDHC Class 4 (TS4GSDHC4 - BH1130821915G)
** 4GB SDHC Class 6 (TS4GSDHC6) - no problems.
** 8GB SDHC Class 4
** 8GB SDHC Class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)
** 8GB SDHC Class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]
** 16GB SDHC Class 6 (TS16GSDHC6)
** 16GB SDHC Class 10 (TS16GSDHC10)

Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).

===Problem SD Cards===

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]

This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.
* '''Adata'''
** 16GB SDHC Class 6 (Possibly SD5MY168G0, label with gold <> black gradient) - Doesn't boot
* '''GSkill'''
** 32GB SDHC Class 10
* '''Panasonic'''
** 8GB SDHC Class 10 (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]
* '''Patriot'''
** 8GB SDHC Class 10 (PSF8GSDHC10)
* '''SanDisk'''
** 4GB SDHC Class 2 - Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt.
** 4GB SDHC Class 4 (BH1030216016G) - Doesn't boot.
** 4GB SDHC Class 6 Extreme (BH0822411730D)
** 4GB SDHC Class 10 Extreme (30 MB/s HD Video) (Doesn't boot)
** 8GB SDHC Class 6 Ultra (B11201421964G)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra labelled as 30MB/s (BI1208721965G)) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra I (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Extreme (BI1101116253G)
** 8GB SDHC Class 10 Extreme (BI1108716254G)
** 8GB SDHC Class 10 Extreme (BI1201516254G) [[http://www.amazon.co.uk/gp/product/B00422FBJ2 amazon.co.uk]]
** 8GB SDHC Class 10 Extreme Pro- Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 6 Ultra (BL1202021933G)
** 16GB SDHC Class 6 Ultra I (BL1205921933G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 10 Extreme (45MB/s U1)
* '''Kingston'''
** 4GB SDHC Class 6 - Boots kernel but won't run init (times out)
* '''Integral'''
** 16GB SDHC Class 6 Ultima Pro (SH016GAA2BB)
** 4GB SDHC class 4 (S404G1115)
* '''PNY'''
** 32GB SDHC Class 10 Professional (P-SDHC32G10-EF) from [http://www.play.com/Electronics/Electronics/4-/18814903/-/Product.html play.com] (mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)

The usual warnings against less reputable sellers (such as Ebay merchants) apply.

Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):

mmc0: timeout waiting for hardware interrupt

=== Benchmarks ===

* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}

RPi VerifiedPeripherals

2012-05-22T14:56:34Z

Bredman: Added RT2070

[[Category: Linux]]
[[Category: ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template: RPi_Hardware}}

==Notes==

19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the [http://www.raspberrypi.org/downloads default Debian distribution] unless stated otherwise. A suggested suffix markup scheme is as follows:

* (A) - Relates to model A production board
* (B) - Relates to model B production board
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different
* No markup - relates to all production boards

''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''

If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.

{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}

== Powered USB Hubs ==
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.

===Working USB Hubs===
*'''Belkin'''
** F5U224 4 port powered USB hub
** F5U231 Hi-speed USB 2.0 Tertrahub - 4 port powered USB hub
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub
*'''Logik'''
** LP4HUB10 4-Port USB Hub
*'''LogiLink'''
** UA0096 USB 2.0 Hub, 10-Port with PSU 5V, 3.5A
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A
*'''Targus'''
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)

===Problem USB Hubs===
*'''Unbranded / Multiple Brands'''
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref>

== USB Remotes ==
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

== USB Keyboards ==
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.
=== Working USB Keyboards ===
The following is a list of specific keyboards known to work and which appear to be fault-free.

* '''A4 Tech'''
** Model KL-5 USB Keyboard, 20mA.

* '''Acer'''
** Compact Keyboard KU-0906 (B) (Also known as Genius LuxeMate i200 Keyboard)
** Wireless Keyboard And Mouse Bundle KG-0917 (B)

* '''Apple'''
** Apple Keyboard (109 keys) A1048
** Apple Keyboard with Numeric Keypad (aluminium/wired) A1243

* '''Asda'''
** Premium Wireless Keyboard (white keys, silver back) HK8028

* '''Cerulian'''
** Mini wireless keyboard and mouse deskset (B)

* '''Cherry'''
** CyMotion Master Linux (B)

* '''Dell'''
** SK-8135 (B)
** SK-8115 (B)
** L100 (B)

* '''Fujitsu Siemens'''
** KB SC USB UK (!)
** KB910 USB, with led light on the highest level (B)
** KB400 USB US

* '''Genius'''
** KB-06XE (K639) (B)
** Slimstar 8000 wireless keyboard

* '''HP'''
** KG-1061

* '''KeySonic'''
** ACK-540RF
** ACK-3700C

* '''Lenovo'''
** SK-8825 UK (B)
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B)

* '''Logitech'''
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** Wii wireless keyboard KG-0802 (!)
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)
** MK 250 wireless keyboard and mouse
** K400 wireless keyboard with touchpad (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** K120 Keyboard (B)
** K200 Keyboard (B)

* '''Microsoft'''
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)

* '''SteelSeries'''
** Merc keyboard (B)

*'''Tesco'''
**Value Keyboard VK109 (B)

* '''Trust'''
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust ClassicLine Keyboard http://trust.com/17184

* '''Xenta'''
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)

===Problem USB Keyboards===

* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Microsoft'''
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)
** Arc wireless - Keyboard has 'sticky' keys. (B)
* '''Novatech'''
** (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B) <ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''Logitech'''
** Logitech Illuminated Keyboard (unstable; not working with led light on; testet both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)
* '''Razor'''
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.
* '''Trust'''
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.

== USB Mouse devices ==
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.

===Working USB Mouse Devices===
The following is a list of specific mouse devices known to work and which appear to be fault-free.

* '''Belkin'''
**F8E882-OPT (B)

* '''Dell'''
** M-UVDEL1 (B)
** M056U0A (B)

* '''Genius'''
** GM-04003A (B)
** Slimstar 8000 wireless mouse

* '''Microsoft'''
** Compact optical mouse 500 V2.0 (B)
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)
** Microsoft Intellimouse Optical Mouse
** Microsoft Wireless Mobile Mouse 3500
** Microsoft Wireless Mobile Mouse 4000

* '''Logitech'''
** MX320/MX400 laser mouse. (B)
** M505 USB wireless laser, model no: 910-001324 (B)
** M-BJ79 (B)
** LX-700 Cordless Desktop Receiver (B)
** Logitech Wireless Gaming Mouse G700. (B)
** Optical wheel mouse. (B)

* '''Technika'''
** TKOPTM2 (B)

* '''Tesco'''
** Wired optical mouse M211 (B)

* '''Generic'''
** Generic 2.4GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)

== USB WiFi Adapters ==

See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing

There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.

===Working USB Wifi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.

* '''3COM'''
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)
* '''Asus'''
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] compiled manufacturer driver for RTL8192CU per [http://www.raspberrypi.org/forum/troubleshooting/trying-to-get-an-rtl8188cus-wireless-usb-nic-working instructions] (B)
* '''Belkin'''
** Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]. On Debian requires the firmware-ralink package from the non-free repository. The usbcore module needs to be added to /etc/modules [http://www.penguintutor.com/blog/viewblog.php?blog=6281 install instructions].
* '''BlueProton'''
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora & Arch; rtl8187 driver (B)
* '''D-Link'''
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>squeeze-firmware</code> non-free repository.
* '''Edimax'''
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP ([http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html howto]) (B)
* '''Gigabyte'''
** Gigabyte GN-WB32L 802.11n USB WLAN Card. Works with the rt2800usb driver.
* '''IOGear'''
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware-realtek from non-free squeeze repo (B)
* '''Micronet'''
** Wireless USB adapter (uses Realtek rtl8188cus) works plugged directly into R-Pi USB (B)
* '''Netgear'''
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the <code>firmware-atheros</code> package from the <code>squeeze-backports</code> non-free repository (!)
** WG111v2: Realtek rtl8187 chipset (!)
* '''OvisLink'''
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink
* '''Ralink'''
** [http://www.dx.com/p/24688 RT2070] USB-ID 148f:2070 ([http://wiki.debian.org/rt2870sta requires firmware])
** [http://www.element14.com/community/docs/DOC-44703 RT2501/RT2573] USB-ID 148f:2573 (firmware required) (B)
** RT5370 USB-ID 148f:5370 ([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from wheezy]) (B)
* '''Sempre'''
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/
* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
* '''TP-Link'''
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)
* '''ZyXEL'''
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)

===Problem USB Wifi Adapters===

These adapters were tested and found to have issues the Raspberry Pi.

* '''Realtek'''
** RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)
* '''Trendnet'''
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)
* '''TP-Link'''
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; errors with LXDE running (B)

== USB Bluetooth adapters ==
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)

== USB Ethernet adapters ==

== USB IR Receivers==

== USB TV Tuners and DVB devices==
*August
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Pi itself. Tested with Astra 19.2E radio and SD-TV channels

== USB Webcam ==
*Sony
**PlayStation Eye (for PlayStation 3)

== USB GPS devices ==
*Royaltek
**Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually
*Garmin
**Garmin eTrex Vista HCx: Works but may draw much power. To get it working (software part): https://wiki.openstreetmap.org/wiki/USB_Garmin_on_GNU/Linux
*Wintec
**WBT-200: No problem on Debian

== USB UART adapters ==
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.

== Other, exotic USB devices ==
*PEAK-System (www.peak-system.com)
**PCAN-USB using the driver (kernel module) from http://www.peak-system.com/fileadmin/media/linux/index.htm
*Tellstick (www.telldus.com)
**Depends on libftdi1

== Power adapters ==
The Raspberry Pi uses a standard Micro USB (type B) power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.

===Wired Adaptors===
* '''All HTC mobile phone adaptors'''
** 5V 1A TCP-300 Single port USB mains phone charger (B)
* '''Amazon'''
** 5V 0.85A USB charger for Kindle
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** 5V 0.7A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
* '''HP'''
** 5V 2A Charger for HP Touchpad (B)
* '''HTC'''
** 5V 1A USB charger
* '''LG'''
** Travel Adapter (4.8V, 1.0A)
* '''Maplin Electronics'''
** 5V 1A dual USB power supply, model number H25B-MT-K2
* '''Nokia'''
** 5V 1.2A AC-10E Charger
* '''Noname'''
** 5V 2.1A KMS-AC09 4 port USB charger (B) [http://www.miniinthebox.com/kms-ac09-universal-ac-adapter-for-ipad-ipad-2-iphone-white_p208568.html]
* '''Novatel Wireless'''
** 5V 1.05A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5V 0.7A Charger for Orange San Francisco
* '''Palm'''
** 5V 1A Charger for Palm Pixi+ (B)
* '''Samsung'''
** 5V 0.7A Charger for Galaxy SII
* '''Sony Ericsson'''
** 5V 0.7A Charger CST-80

===External Batteries===
* ''' New Trent'''
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)
* ''' Sinoele'''
** Movpower - Power Bank 5200mAh (8hrs with Wifi active)

== Display adapters ==
While technically there shouldn't be a difference between one (for example) HDMI->DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI->DVI, CompositeRCA->SCART, CompositeRCA->VGA ''boxes/chipsets'', and HDMI->VGA ''boxes/chipsets''.

===HDMI->DVI-D===
None explicitly mentioned
===HDMI->VGA converter boxes===
Note that the [[RPi_config.txt]] file will have to be edited if the converter or VGA monitor does not support 1080p resolution, this is because the Rpi cannot detect the resolution. initially setting to VGA resolution is probably best

According to user "asb" -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.

This adapter (from Kanaan) -- http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- is working. Quality not wonderful, but certainly usable, on 1400x900 monitor.

According to user "na1pir" -- http://www.ebay.com/itm/BK-HDMI-Male-to-VGA-RGB-Female-HDMI-to-VGA-Video-Converter-adapter-1080P-for-PC-/140742987581

===Composite->SCART===
None explicitly mentioned
===Composite->VGA converter boxes===
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low
== SD cards ==

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.)
For this reason, please specify product numbers in the lists below, when possible.

===Working SD Cards===
* '''Adata'''
** 8GB SDHC Class 10 (AUSDH8GCL10-R)
** 16GB SDHC Class 6
* '''Dane-Elec'''
** 16GB SDHC Class 4
* '''Duracell'''
** 4GB SDHC Class 4
** 16GB SDHC Class 10 (labelled Pro Photo 200x)
* '''Extrememory'''
** 16GB SDHC Class 10
* '''Hama'''
** 8GB SDHC High Speed Pro Class 6
* '''HP'''
** 8GB SDHC Class 4 (doesn't reboot during first time startup process, but restart again and fine after that).
* '''Integral'''
** 8GB SDHC Ultima Pro Class 6 (Works - initial error -110 but boots within 5 seconds with no further errors or issues)
** [http://www.amazon.co.uk/gp/product/B0047T6XME 16GB SDHC Class 10 Ultima Pro (20MB/s)]
* '''Kingmax'''
** 4GB SDHC Class 2
** 4GB microSDHC Class 4 (KM04GMCSDHC4) won`t reboot when it`s hot
* '''Kingston'''
** 2GB SD
** 4GB microSD Class 4
** 4GB SDHC Class 4 (SD4/4GB)
** 8GB SDHC Class 4
** 8GB microSDHC Class 4
** 8GB SDHC Class 10 (SD10G2/8GB, SD10V/8GB, ultimateX 100X, ultimateX 120X)
** 16GB SDHC Class 10 (SD10G2/16GB, ultimateX 100X)
* '''Kodak'''
** 4GB SDHC Class 2
** 8GB SDHC Class 4
* '''Kruidvat'''
** 8GB SDHC Class 4
* '''Lexar'''
** 4GB SDHC Class 4 (Boots consistently and no error messages in log after 1/2 hour use )
** 4GB SDHC Class 6 Platinum II (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])
** 8GB SDHC Class 4
** 8GB SDHC Class 6 Platinum II
** 16GB SDHC Class 6 Platinum II
* '''Microcenter Brand (sold in bins at checkout)'''
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]
* '''MyMemory'''
** 8GB SDHC Class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10] (Latest batch not working)
* '''Optima'''
** 8GB SDHC Class 10 (Pro-Speed)
* '''Panasonic'''
** 8GB SDHC Class 6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])
* '''Peak'''
** 4GB microSDHC Class 4 (MMBTR04GUBCA-ME) tested with Arch
* '''Play.com'''
** 4GB SDHC Class 6 (S4E3CD04GEFAA 0907090121106)
* '''PNY'''
** 4GB SDHC Class 4
** Optima 4GB SDHC Class 4 (SD-K04G 0834TT1297Y)
** 16GB SDHC Class 4
* '''Samsung'''
** 4GB SDHC
** 8GB SDHC
** 8GB SDHC Class 10 (MB-MP8GA)
** 16GB SDHC Class 6 (MB-SSAGAEU)
** 16GB SDHC Class 10 (MB-SPAGA aka MB-SPAGAEU)
* '''SanDisk'''
** 2GB SD, white "SanDisk for Wii" branded, no class mentioned
** 2GB SD (with a circle 2 --probably class 2), writes at 3.5 Mb/s
** 2GB SD Class 4 Ultra (15MB/s)
** 2GB SD Class 4 Ultra II
** 2GB SD Extreme III (BE0715105083B)
** 4GB SDHC Class 4
** 4GB SDHC Class 4 Ultra II
** 4GB SDHC Class 4 Ultra (SDSDH-004G-U46) won`t reboot when it`s hot
** 4GB SDHC Class 6 Ultra (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)
** 4GB SDHC Class 10 Extreme (BH10297143382G)
** 8GB SDHC Class 4 (writes at ~1.5MB/s)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) (could be problematic, see below)
** 8GB SDHC Class 6 Ultra labelled as 20MB/s (BI11321422083D)
** 8GB SDHC Class 10 Extreme (BI11017514367G)
** 16GB SDHC Class 4
** 32GB SDHC Class 6
** 4GB microSDHC Class 2
** 4GB microSDHC Class 4
** 8GB microSDHC Class 2
** 8GB microSDHC Class 4
** 8GB microSDHC Class 6 Mobile Ultra (SDSDQY-008G-U46A) working with the latest firmware, won`t reboot when it`s hot
* '''Silicon Power'''
** 4GB microSDHC Class 6 (SP004GBSTH006V10-SP)
* '''Sony'''
** 4GB SDHC Class 4 (SF-4B4) (Write 6MB/s, Read 20MB/s)
* '''TDK'''
** 4GB SDHC Class 4 (1008WW5261B)
* '''Toshiba'''
** SD-C08GJ(BL3A (8GB mircoSD with Adapter)
* '''Transcend'''
** 4GB SDHC Class 4 - we've found these to work without any errors and offer reasonable performance
** 4GB SDHC Class 4 (TS4GSDHC4 - BH1130821915G)
** 4GB SDHC Class 6 (TS4GSDHC6) - no problems.
** 8GB SDHC Class 4
** 8GB SDHC Class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])
** 8GB SDHC Class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)
** 8GB SDHC Class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]
** 16GB SDHC Class 6 (TS16GSDHC6)
** 16GB SDHC Class 10 (TS16GSDHC10)

Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).

===Problem SD Cards===

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]

This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.
* '''Adata'''
** 16GB SDHC Class 6 (Possibly SD5MY168G0, label with gold <> black gradient) - Doesn't boot
* '''GSkill'''
** 32GB SDHC Class 10
* '''Panasonic'''
** 8GB SDHC Class 10 (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]
* '''Patriot'''
** 8GB SDHC Class 10 (PSF8GSDHC10)
* '''SanDisk'''
** 4GB SDHC Class 2 - Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt.
** 4GB SDHC Class 4 (BH1030216016G) - Doesn't boot.
** 4GB SDHC Class 6 Extreme (BH0822411730D)
** 4GB SDHC Class 10 Extreme (30 MB/s HD Video) (Doesn't boot)
** 8GB SDHC Class 6 Ultra (B11201421964G)
** 8GB SDHC Class 6 Ultra (SDSDH-008G-U46 - BI1131222083D) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra labelled as 30MB/s (BI1208721965G)) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Ultra I (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 8GB SDHC Class 6 Extreme (BI1101116253G)
** 8GB SDHC Class 10 Extreme (BI1108716254G)
** 8GB SDHC Class 10 Extreme (BI1201516254G) [[http://www.amazon.co.uk/gp/product/B00422FBJ2 amazon.co.uk]]
** 8GB SDHC Class 10 Extreme Pro- Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 6 Ultra (BL1202021933G)
** 16GB SDHC Class 6 Ultra I (BL1205921933G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )
** 16GB SDHC Class 10 Extreme (45MB/s U1)
* '''Kingston'''
** 4GB SDHC Class 6 - Boots kernel but won't run init (times out)
* '''Integral'''
** 16GB SDHC Class 6 Ultima Pro (SH016GAA2BB)
** 4GB SDHC class 4 (S404G1115)
* '''PNY'''
** 32GB SDHC Class 10 Professional (P-SDHC32G10-EF) from [http://www.play.com/Electronics/Electronics/4-/18814903/-/Product.html play.com] (mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)

The usual warnings against less reputable sellers (such as Ebay merchants) apply.

Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):

mmc0: timeout waiting for hardware interrupt

=== Benchmarks ===

* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}

RPiconfig

2012-05-22T08:11:24Z

Bredman: /* Video mode options */

RPiconfig

2012-05-20T08:52:10Z

Bredman: /* Video mode options */

RPiconfig

2012-05-20T08:46:43Z

Bredman: /* Which values are valid for my monitor? */