eLinux.org - User contributions [en]

User:TrevorGowen

2013-05-14T07:42:14Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 13.05.2013, Now trying out expansion/proto-typing boards - mainly with a "Model A" version. Three more USB PSU's evaluated).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User:TrevorGowen

2013-05-07T18:53:23Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 07.05.2013, Now trying out expansion/proto-typing boards - mainly with a "Model A" version. Three more USB PSU's evaluated).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User:TrevorGowen

2013-04-18T14:32:49Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 18.04.2013, Now trying out expansion/proto-typing boards and a "Model A" version).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User:TrevorGowen

2013-03-30T22:38:32Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 30.03.2013, Now trying out expansion/proto-typing boards and a "Model A" version).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User:TrevorGowen

2013-03-12T09:50:29Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 12.03.2013, Now trying out expansion/proto-typing boards and a "Model A" version).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

RPi VerifiedPeripherals

2013-03-11T18:01:46Z

TrevorGowen: /* Working USB Mouse Devices */ Added ASDA Traveler 8000 and another Trust mouse

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

==Power Usage Notes==
{{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 Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75 V), 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.}}

'''Model B Hardware Revisions and USB Power limits'''
'''Hardware Revision 1.0'''
The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximately 100 mA. USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA 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.

'''Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change'''
This had the polyfuses removed, removing the 100 mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012. {{Warning|}}Because the polyfuses have been removed, back feeding of the PI, by applying power via its normal USB output, can damage D 17 if triggered by an over-voltage, and so lead to consequential over-heating. This can be discovered by melts, scorching, smoke or worse.[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=34149]

==Linux Driver Issues==
Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=12097&start=76] [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5249&start=44]
A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image.

== 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 the Raspberry 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 Raspberry Pi through their interconnect cable, due to the 100 mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).

===Working USB Hubs===
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''USB Version'''
| '''Number of Ports'''
| '''Power Rating*'''
| '''Powers Raspberry Pi'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F5FAFF;"
|Atlantis
|HUB USB2.0 7P
|P014-GH902-B
|
|USB 2.0
|7-Port
|5 V - 2 A
|Verified
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|4-Port Ultra-Slim Desktop Hub
|F4U040
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|8-Port ExpressBus for iMac
|F5U010
|
|USB 2.0
|8-Port 7x"A" 1x"B"
|
|Verified
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U224
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|TetraHub™ USB 2.0 4-Port Hub
|F5U231
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U234
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|No backfeed, can power the RPi. Comes with a 2.4 A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''“Per Port Current Self-Powered Mode: 500mA (max)”''. However, I've attached a HD that requires 850 mA and it worked fine.

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237
|
|USB 2.0
|7-Port
|5 V - 3.8 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|MyEssentials 7-Port High-Speed USB 2.0 Hub
|F5U259-ME
|
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Lighted Hub
|F5U403
|
|USB 2.0
|4-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Lighted Hub
|F5U700
|
|USB 2.0
|7-Port
|
|Verified
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hub 2-en-1
|F5U706ea
|
|USB 2.0
|7-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237v1
|
|USB 2.0
|7-Port
|5 V - 2.5 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U040v
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U039qukAPL
|05e3:0608
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Benq
|
|E2220HD
|
|USB 2.0
|4-Port
|
|Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|BUFFALO
|4 Port Hub
|BSH4aAE06
|05e3:0608
|USB 2.0
|4-Port
|5 V
|Verified
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB

|- valign="top" align="left" style="background: #F5FAFF;"
|Cyberpower
|High-speed Hub
|CP-H720P
|0409:0050
|USB 2.0
|7-Port
|3.6 A
|Verified
|May Contain dual 05e3:0608 instead of 0409:0050

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2001FP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|SP2309W
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2407FWP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|U3011
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub - Card Reader Works - May work with SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|
|B/N61393
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|USB 2.0 External Hub 7 Port
|B/N87467
|
|USB 2.0
|7-Port
|5 V - 3.5 A
|Verified
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.

|- valign="top" align="left" style="background: #F5FAFF;"
|Deltaco
|
|UH-715 Rev 2
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|
|
|0409:0050
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|Dynex USB 2.0 7 Port Hub
|DX-HB7PT
|
|USB 2.0
|7-Port
|5.0 V / 2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|D-Link 7 Port USB Hub
|DUB-H7/B
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7 High Speed USB 2.0 7-Port Hub
|BUBH7A A5
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7
|EUBH7EB H/W Ver:B1
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-4 High Speed USB 2.0 4-Port Hub
|DUB-H4
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi
This is not the case for Ver/Rev. C1 of the hub with the RPi Model B. It works fine with the Charging port. Has been verified on two RPis with two of the hubs.
|- valign="top" align="left" style="background: #F5FAFF;"
|Digicom
|
|
|
|USB 2.0
|4-Port
|5 V - 2.0 A
|Not Verified
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]

|- valign="top" align="left" style="background: #F5FAFF;"
|ednet
|USB 2.0 7 port Hub
|85014
|
|2.0
|7-Port
|
|Not Verified
|Works with keyboard, mouse, audio devices

|- valign="top" align="left" style="background: #F5FAFF;"
|GigaWare
|USB 2.0 4 port Hub
|Model 26-160
|
|2.0
|4-Port
|
|Verified
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.

|- valign="top" align="left" style="background: #F5FAFF;"
|König Electronic
|7 port USB2.0 HUB
|CMP-USB2HUB55
|1a40:0201
|2.0
|7-Port
|2.0A
|Verified
|Backpowers Raspberry Pi well.

|- valign="top" align="left" style="background: #F5FAFF;"
|Medi@com
|USB 2.0 4 ports Hub
|M-HX30
|
|2.0
|4-port
|
|Verified
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]

|- valign="top" align="left" style="background: #F5FAFF;"
|mbeat
|13 Port USB Hub
|USB-M13HUB
|
|USB 2.0
|13-port
|5V - 3A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Monoprice
|Aquagate USB Hub
|5328
|
|2.0
|7-port
|2.0 A
|Verified
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]

|- valign="top" align="left" style="background: #F5FAFF;"
|Plugable
|7 Port High Speed USB Hub
|USB2-HUB-AG7
|
|USB 2.0
|7-Port
|5V - 3A
|Verified
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Plugable
|4 Port Hub with Battery Charging 1.1 Support
|USB2-HUB4BC
|
|USB 2.0
|4-Port
|5V - 2.5A
|Verified
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|10 Port USB 2.0 Hub
|USB2-HUB10S
|
|USB 2.0
|10-Port
|5V - 2.5A
|Not Verified
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|4 Port USB 3.0 Hub
|USB2-HUB-81X4
|
|USB 3.0
|4-Port
|5V - 4A
|Not Verified
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|7 Port USB 3.0 Hub
|USB2-HUB7-81X
|
|USB 3.0
|7-Port
|5V - 4A
|Not Verified
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
|Plata 4 port USB 2.0 hub
|18687
|
|2.0
|4-port
|1.0 A
|Not Verified
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Zipp
|USB 7-Port HUB
|N294
|
|USB 2.0
|7-Port
|5V - 2.0A
|Verified
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)

|-
|}

'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.
</div>

*'''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 it is 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 Raspberry Pi, and additionally connect GND and +5 V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.

*'''Digitus'''
** 7-port USB2.0 Powered Hub. Model DA-70226.
*'''Eminent'''
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
* '''GearHead'''
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5 V, 1 A)
*'''Gembird'''
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.
* '''Genesys Logic (sold at Fry's)'''
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref>
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)
* '''Hama'''
** Hama 4-way USB 2.0 Hub
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)
*'''HP'''
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)

*'''Laser'''
** "7 port USB hub with AC adapter Version 2.0". 5 V 1 A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry 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, 2 A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!
*'''LogiLink'''
** UA0085 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0090 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0091 USB 3.0 Hub, 4-Port with PSU 5 V, 4 A. Connected with USB2.0 cable. 1 A 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 5 V, 3.5 A (Not suitable for powering Raspberry Pi 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 5 V, 2 A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.
* '''Macally'''
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000 mA wall-wart (US style)
* '''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 1000 mA wall-wart (US style)
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500 mA each) + (4 USB 3.0 Ports @900 mA each) Power Switches on each port, AC Powered and Includes a 5 V 4 A wall-wart (US style)
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5 V 1 A
** NLUSB2-222P 4 port USB 2.0 Hub with 5 V 2 A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])
*'''Nilox'''
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5 V 1.0 A
* '''Plugable'''
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5 V 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port.
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5 V 3 A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)

* '''Pluscom'''
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3 A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.
*'''Satechi'''
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.
*'''Staples (Business Depot) (Bureau EN GROS)'''
** Staples 4-port hub Item 607477-CA
*'''StarTech.com'''
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5 V 2 A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).
*'''SumVision'''
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5 V 1.0 A (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 Raspberry 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 (1 A). Powering Raspberry Pi via microUSB from a hub port.
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]
*'''Sweex'''
** US014 4 Port USB 2.0 Hub
*'''Targus'''
** ACH81xx 7-port powered hub. 5 V 3 A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)
** ACH63EU 4-port. Using a 5 V 2 A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.
*'''The Pi Hut'''
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
*'''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 (5 V 2 A)
*'''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 (5 V 2.5 A) Powering Raspberry Pi from the 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 5 V, 3 A. USB ID 1a40:0201.
*'''VANTEC'''
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5 V 2 A AC/DC adapter. Go 2.0 Mini hub.
*'''Z-TEK'''
** Z-TEK 7-port powered hub with PSU 5 V, 4 A. 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, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5 V pinouts)
** F4U022 7-Port powered USB hub (powered 5 V, 2.6 A), 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. (Works always without powering the Raspberry Pi, haven't tried that)

*'''Dell'''
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.

*'''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.
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.

*'''Dynamode'''
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1 A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification.

*'''D-Link'''
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)

*'''E-Solution'''
** 4-Port 2 A 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 with 1 A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry 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.
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.

*'''Hama'''
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi 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).

*'''iBall'''
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.

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

*'''LogiLink'''
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.

*'''Soniq'''
** 4-Port 5 V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).

*'''Targus'''
** ACH115EU 7-port powered hub. 5 V 3 A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as 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. 1 A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi 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). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2 A 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 there are strange USB failures when X session started. High speed devices such as hard drives had failures.

== USB Remotes ==
* ASUS TV FM Remote IR - ID 3353:3713 - works. Receiver connected to an USB Hub. Tested with archlinux in X. It works also as pointer (pressing "Toggle" button)

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

* [http://www.amazon.com/gp/product/B005DKZTMG/ref=oh_details_o02_s00_i00 Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070)] - keyboard and touchpad work. Have not verified multi-touch features.

* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4 GHz wireless keyboard and touchpad.

* Pan.Code D1000 - 2.4GHz Wireless keyboard and touchpad.

* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.

* [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], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]. Working perfectly, just plug & play.

* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6753651&CatId=3680# Exo Ultra U12-41310 Mini Keyboard] Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work.[https://github.com/thunderbirdtr/rs-pi-exo-keyboard Exo Installer script]

== 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, 20 mA.

* '''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, 100 mA (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''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))
** [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]
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]

* '''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)

* '''Banbridge'''
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)

* '''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)
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5 V/100 mA, works directly

* '''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)

* '''CD Training'''
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]

* '''Cherry'''
** CyMotion Master Linux (B)
** RS 6000 USB ON
** G84-4100PTMUS (B) (Compact keyboard. Rated 100 mA. Works directly in Raspberry Pi)
** G85-23100DE-2 (B) (Rated 40 mA, tested with RPi powered by a 1000 mA power supply unit)
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.

* '''Compaq'''
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5 V 100 mA. Works directly connected to Raspberry Pi

* '''Das Keyboard'''
** Model S Professional Keyboard (Built in USB hub not tested) (B)
** Model S Ultimate Keyboard (Built in USB hub working) (B)

* '''Dell'''
** SK-8115 (B) (Rated 100 mA. Works directly in Raspberry Pi)
** L100 (B)
** RT7D40 (100 mA. Works directly in Raspberry Pi)
** RT7D50 (75 mA) (run "sudo dpkg-reconfigure keyboard-configuration")
** KB1421 (100 mA)
** KB2521 (100 mA)
** KB212-B (Works directly in Raspberry Pi, without powered hub)
** 1HF2Y (Works directly in Raspberry Pi)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4
** USB Keyboard 413c:2107 - Works with and without USB hub

* '''Delux'''
** K8050

* '''Digicom'''
** WKEYPE01 Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

* '''Dynex'''
** DX_-WKBD (60 mA) (B)
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)

* '''EAPPLY'''
** EBO-013 Wireless 2.4 GHz compact keyboard with touchpad. Rated <40 mA works directly from Raspberry 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

* '''GE'''
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)

* '''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 >> also see Problem USB Keyboards
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)
** KB1500U (USB Mini Keyboard) (B)
** KB5150 (2.4 GHz wireless keyboard/mouse Combo) (B)
*** Works well with a powered hub

* '''Generic'''
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.

* '''Genius'''
** Ergomedia 700 (GK-04008/C) used without Hub
** KB-06XE (K639) (B)
** LuxeMate i200 (GK-090017; not tested with Hub)
** Slimstar 8000 wireless keyboard

* '''Gigabyte'''
** GK-KM7580 2.4 GHz Wireless Multimedia Keyboard & Mouse

* '''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.4 GHz 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.4 GHz 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 Raspberry Pi. Also works with Raspbmc with powered hub.
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub
** ACK-3700C
** ACK-340U+(DE)
** ACK-3400U (UK) mini keyboard
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi

* '''Labtec'''
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat 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.4 GHz 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.4 GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver

* '''Logitech'''
** Comfort Wave 450, labeled 100 mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine
** 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
** MK120 wired keyboard and mouse
** MK220 wireless keyboard and mouse
** MK250 wireless keyboard and mouse (no hub needed)
** MK260 wireless keyboard and mouse (no hub needed)
** 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]
** MK350 wireless keyboard (using Unifying receiver)
** MK520 wireless keyboard and mouse
** MK550 wireless keyboard and mouse (B)
** MX3200 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.
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]
** K120 Keyboard (B)
** K200 Keyboard (B)
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)
** K310 Washable Keyboard
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K350 Wireless Keyboard (B)
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". +1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.
** K520 Keyboard (B)
** K700 Wireless Keyboard with Touchpad and unifying receiver
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).
** 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 Raspberry Pi.
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub 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.
** V470 Bluetooth Laser Mouse

''Keyboards and mice also together with Unifying receiver''

* '''macally'''
**macally iKey slim (IKEY5V2)

* '''Medion'''
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref>

* '''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)
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5 V/100 mA (Wheezy 5-Sept-2012)

* '''Mikomi'''
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the 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)

* '''ONN'''
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.

* '''Ortek'''
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.

* '''Perixx'''
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

* '''Prodige'''
**Nanox Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]

* '''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]
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.
**RT-MWK01 mini wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

*'''Rosewill'''
** RK-200 Standard Keyboard

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.
** Expression Keyboard (US)
** Cyborg V.5 (B)

*'''SelecLine'''
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (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)

*'''SolidTek'''
** Solid Tek KB-P3100BU ASK-3100U.

*'''Sony'''
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5 V 1 A 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)

*'''The Pi Hut'''
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.

* '''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.4 GHz 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 Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5 V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry 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.0 V. 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 power away from the rest of the support system devices.

* '''A4 Tech'''
** Model GL-6 USB Keyboard, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''Accuratus'''
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100 mA). Tested with 1000 mA cheap unbranded and Nokia 1200 mA power adaptors.
* '''Apple'''
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub.
*'''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 <200 mA)
* '''Dell'''
** SK-8135 (B) (Rated 1.5 A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)
** SK-8115 causes kernel panic (rated 100 mA) Debian 6-19-04-2012 (B)
** Y-U0003-DEL5 Sticky / Non-responsive keys
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V
* '''Gear Head'''
** KB2300U - Causes kernel panic (B)
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)
* '''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/]
* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Jeway'''
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)
* '''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)
** MK 260 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 receiver - 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)
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000 mA power supply unit)
* '''Novatech'''
** NOV-KEY2 - Causes kernel panic (B)
* '''PC World Essentials'''
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it 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).
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5 V 500 mA. (B)
* '''SIIG'''
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.
* '''Texet'''
** MB-768B standard keyboard (Rated 5 V 1.5 A (!), 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.
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B)
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.
* '''Verbatim'''
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)
* '''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

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

* '''Apple'''
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).

* '''Asda'''
** HM5058 (Smart Price) Wired Mouse
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> 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)
** MG-0919 (wireless)

* '''Belkin'''
** F8E882-OPT (B)

* '''Cellink'''
** OPM-602 Small wireless optical mouse

* '''Cerulian Technology'''
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA

* '''Dell'''
** M-UVDEL1 (B)
** MOC5UO (100 mA)
** M056U0A (B)
** DZL-MS111-L (B) (100 mA)
** MS-111P (100 mA)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.

* '''Dynex'''
** DX-WMSE (100 mA) (B)

* '''Fellowes'''
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (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.4 GHz 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)

* '''Kensington'''
** Kensington Expert Mouse Trackball K64325
** Kensington Expert Mouse "Slimblade" K72327US

* '''Labtec'''
** Corded Laser Glow Mouse 1600, rated 5 V 100 mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)

* '''Lenovo'''
** Wired Optical Mouse Model: MO28UOL

* '''Logik'''
** Wired Optical Glow Mouse Model: LGGMO10. (B)

* '''Logitech'''
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)
** B105 Mouse for Laptops (OEM)
** 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)
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).
** 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 5 V 100 mA. Works fb on model B with Raspbian Wheezy
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref>

* '''Microsoft'''
** Comfort Curve Mouse 3000 for Business
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).
** 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 1000
** 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)

* '''Perixx'''
** PERIMICE-210 U Red (Part No.R1J)

* '''Razer'''
** Boomslang Collectors Edition 2007 (B)

* '''Rosewill'''
** Rosewill RM-C2U

* '''Saitek'''
** Notebook Optical Mouse (PM46)

* '''Samsung'''
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50 mA)

* '''Sun microsystems'''
** Model: FID-638 , SunPN: 371-0788-01

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]

* '''Swiftpoint'''
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.

* '''Targus'''
** AKM02UK (Associated keyboard not checked)
** AMU2701EUK (B)

* '''Technika'''
** TKOPTM2 (B)
**TKD-211
**TKNM110

* '''Tesco'''
** Wired optical mouse M211 (B)

*'''The Pi Hut'''
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Model 15313 - large, 5-button wireless mouse
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.

* '''Verbatiam'''
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)

* '''Xenta'''
** MOW0810 (B)
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Generic'''
** Generic 2.4 GHz 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
* '''A4Tech'''
** Model G7-630 Wireless Mouse, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''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 1000 Hz out of the box, whereas the 518 is only 125 Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot

* '''Microsoft'''
** Microsoft Touch Mouse - Does not see right clicks, Only left.
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.

* '''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.
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus

* '''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 Real Time Clocks ==
*Cymbet
** Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)
Device information at http://www.cymbet.com/pdfs/DS-72-22.pdf
Code to access the RTC from Linux: https://github.com/owendelong/Cymbet-RTC
Does not require a powered hub.

== USB Wi-Fi 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 Wi-Fi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but it has not yet been tried.

'''Note:''' A Wi-Fi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the Wi-Fi adapter to the Wi-Fi Access Point. Therefore, you may need to plug the Wi-Fi 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 Raspberry Pi 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."
** It works without additional software connected directly to a Rev 2 Raspberry Pi, but it stops working after a period of time (3 to 4 hours) with a fully updated Wheezy and all the 'USB workarounds' [http://elinux.org/Rpi_USB_check-list] in place.

* '''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). Tested on Raspbian too (drivers from aircrack-ng).
** AWUS036H (500 mW version): Tested on Raspbian (drivers from aircrack-ng).
** AWUS036H (1 W version): Tested on Raspbian (drivers from aircrack-ng). Needs USB powered HUB or Rev2 of the board / polyfuse bypass.
** AWUS036NHA: Tested on Raspbian (drivers from aircrack-ng). Works fine if connected after boot, otherwise Raspberry Pi won't boot up.

* '''AirLink101''' [[File:Airlink101.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-airlink101|100px|Airlink 101 Wireless N 150 Ultra Mini-USB Adapter]]
** 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.
** AWLL5099: Tested on Raspian Wheezy. [http://www.savagehomeautomation.com/raspi-airlink101 Step-by-step installation and configuration instructions] with screenshots can be found [http://www.savagehomeautomation.com/raspi-airlink101 here]. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** [http://www.airlink101.com/products/awll6075.php AWLL6075]: Tested on Raspian Wheezy 16-Dec-2012 build and distro upgrade as of 09-Jan-2013. lsusb reports: 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter. Driver installed is r8712u. Powers OK from Model B Pi (Rev 000f) USB port (1200mA supply tested). Dongle does get hot under use when directly connected to USB port (slightly reduced when USB extender cable used).

* '''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 repository (B) (not needed with latest Raspbian “Wheezy” 2012-07-15: this Asus works N10 out of the box) Does not support nl80211 APIS, so hostapd won't work.
** [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 it will not function.
** WL-167G v3 USB ID 0b05:1791, working out-of-the-box on Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17. Does not require powered hub.
[[File:AusPiWiFi.png|thumb|right|link=http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/|100px|AusPi Technologies 802.11n WiFi Adapter]]
* '''AusPi Technologies'''
** AusPi Wireless Adapter [Realtek RTL8188S]. Works without a powered HUB. Tested on OpenELEC (works OOB), RaspBMC (works OOB) and 2012-08-08 Raspbian Wheezy (works OOB). Free shipping worldwide from [http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/ Buy Raspberry Pi Australia].

* '''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 '''Powered hub required!'''
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Works on RaspBMC OOB (with NetworkManager plugin). Works WITHOUT powered hub on 5 V 800 mA power with 6 overvolt (nothing else connected to USB)
** 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 repository (B). Verified working with 2012-12-16-wheezy-raspbian right out of the box.
**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. Tested and working on Rasbian Wheezy (and RaspBMC), driver RTL8192CU, no powered hub needed (dongle directly attached to the onboard ports)
** Belkin Components F9L1001v1 "N150" Wireless USB Adapter. Tested and working on Rasbian Wheezy WITHOUT powered hub.
** Belkin Surf Micro WLAN USB-Adapter (Raspbian Wheezy, unpowered hub, "N150")

* '''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
** USB ID: WLI-UC-G300N - Works on Raspbmc out of the box. Tested after a factory reset of the Raspbmc.

* '''Comfast'''
** WU710N: chipset RTL8188CUS. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** WU810N (150M): Works out of the box on wheezy raspbian of version 2012-12-16.

* '''Conceptronic'''
** C300RU. Works out of the box in Raspbian. Causes reboot when plugging on a live Rev. 2 Raspberry Pi

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

* '''DealExtreme'''
** ISG-1507N Mini USB 2.4GHz 150Mbps 802.11b/g/n WiFi. Has the ralink 5370 chipset, works directly plugged into the Raspberry Pi rev.1 under OpenELEC. Note: Driver (rt2800usb) only permits B/G operation and throughput is low (10Mbit).

* '''DELL'''
** Wireless 1450 [Intersil ISL3887]. Works out of the box, but it requires a powered hub (the Raspberry Pi boots with this dongle plugged in, recognizes and configures it, works for some time, but then it crashes randomly under heavy traffic. A powered hub seems to fix the issue).

* '''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-121 (Version A1). Wireless N 150 Pico. Works out-of-the-box with Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)
** DWA-123 (Version A1). USB ID 2001:3c17, Ralink RT2800. Working out-of-the-box on Arch image from 2012-04-29. (working without UBS Hub - not yet sure if it achieves full speed though.)
** DWA-130 (rev. E1) Works out of the box with Raspbmc Frodo. Updated Raspbmc upon plugging in and powering up. Had issues timing out. Changed DNS to openDNS address. Works good after that.
** DWA-131 (rev. A1) USB ID 07d1:3303,Realtek RTL8192SU, 802.11n Wireless N Nano. Important : revision A1 works, revision B1 does not. 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]
** WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.

* '''Edimax''' [[File:Edimax-ew-7811un.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-edimax-ew-7811un|100px|Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter]]
** [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]. Note: With current Raspbian (2012-09-18-Wheezy) it is recognized immediately, the default module works fine; the configuration is easy using wireless-essid and wireless-key in /etc/network/interfaces.
*** The EW-7811Un can be powered directly from the Raspberry Pi if the Raspberry Pi is powered using a well regulated power supply.
*** EW-7811Un [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un step-by-step installation and configuration instructions] for Debian & Raspian with screenshots can be found here: [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un here]
*** 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 Raspberry Pi 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]]
*** EW-7811Un[USB ID 7392:7811](Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Worked right out of the box - only needed to configure WPA.
(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.
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=261&pl1_id=1&pl2_id=44 EW-7711UAn], Ralink RT2870, works perfectly on Arch with a powered hub (not tested without yet). Simply required wireless_tools and wpa_supplicant, the drivers/firmware are included in kernel 3.0. I followed the Arch [https://wiki.archlinux.org/index.php/Wireless_Setup Wireless Setup] instructions.

* '''edup'''
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS Wi-Fi 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://dx.com/p/ultra-mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network-adapter-48166?item=1&Utm_rid=24958662&Utm_source=affiliate Ultra-Mini Nano USB 2.0 802.11n 150 Mbit/s Wi-Fi/WLAN Wireless Network Adapter] USB ID: ID 0bda:8176 Works stable when using VLC for internet radio receiver. Works stable 24/7 on two of my Raspberries used as webserver. Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian. Seems to be the same as EW-7811Un using the RTL8188CUS chipset.

** [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 Raspberry Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or received the audio get distorted. Use script from [http://dl.dropbox.com/u/80256631/install-wheezy-beta-rtl8188cus-20120619.sh here] for Wheezy.

* '''Eminent'''
** EM4575 - rt2800usb driver.

* '''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 repository. No need to download firmware when using Debian Wheezy (B)

* '''ISY'''
** USB Wireless Micro Adapter IWL 2000, tested on Raspbian; follow [http://daniel-lnx.blogspot.nl/2013/01/raspberry-pi-and-isy-usb-wireless-micro.html these] instructions.

* '''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 it 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]
** Linksys WUSB54GC (manufactured 07/2008) No issues! needs powered hub on version 1.0 boards - 13b1:0020
** Linksys WUSB54G ver.4, Works well even when plugged directly to the Raspberry Pi. Requires 300mA max, hence recommended to use powered usb hub for extended operation.

* '''LogiLink'''
** Wireless LAN USB 2.0 Nano Adapter 802.11n LogiLink [http://www.logilink.eu/showproduct/WL0084B.htm] is working even USB powered.

* '''Lutec'''
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.

* '''Micronet'''
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into Raspberry 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 Wi-Fi 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>

* '''Mvix'''
** Mvix Nubbin (MS-811N): works out of the box on Raspbian "Wheezy" and does not need a powered USB hub.

* '''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. Seems to draw a lot of power; e.g. I can't power this and a USB thumb drive simultaneously.
** WG111v3: Realtek RTL8187B chipset. Works straight out of the box using a powered USB hub.
** WNA1000M works with Raspberry Pi Model B Board v. BS1233. However, when downloading torrents and when they pick up speed, the system becomes unresponsive.

* '''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 Wi-Fi 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.
** RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.
** [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). An image of an adapter with this chip can be found [http://i.imgur.com/wRF7L.jpg here].
** RT5370 supports Access Point and it be used for hostapd

* '''Rosewill'''
** RNX-N180UBE Wireless B/G/N Adapter
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172
*** Tested in Arch, works out of box. Powered USB hub required.
*** Tested in Raspbian, used wicd to configure network settings. Powered USB hub Required.
*** Tested in Raspbmc. Needs package firmware - Realtek and used wicd-curses to configure. Powered 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.
** RNX-MiniN1 (RWLD-110001) Wireless-N 2.0 Dongle (Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter)
*** Tested in Raspbian, powered from USB hub.

* '''Sabrent'''
** USB-A11N: Mini USB 2.0 Wireless-N WiFi Network Adapter: USB ID 0bda:8176, works automatically in Raspbian using rtl8192cu driver along with Logitech BT mini-receiver (keyboard/mousepad) without external hub using 5.25V 1 A psu (4.99V T1/T2) on rev 2.0 (B)

* '''Sagem'''
** Sagem Wireless USB stick XG-760N: USB ID 079b:0062, Module is not shipped in Debian image, but it 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/

* '''Sitecom'''
** Sitecom Wi-Fi USB Adapter N300: USB ID 0a5c:5800, Realtek r8712u driver + firmware Realtek. Module available in shipped Raspbian image. '''NOTE:''' although this dongle will also work without powered hub, if there is a voltage problem (either on the Raspberry or on the hub, but verified only on the hub so far) this wifi dongle will receive signal perfectly (RX), but not be capable of sending anything (TX) and the MAC address will be permanently set to FF:FF:FF:FF:FF:FF (this is indicative that there is not enough power) [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]

* '''SL'''
** SL-1507N: USB 802.11n 150M Wi-Fi Wireless LAN Network Card Adapter SL-1507N Black
*** I bought this on on eBay for $4.19 (free shipping) @ http://www.ebay.com/itm/270853614804?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649#ht_4379wt_1199
*** It worked out of the box on Raspbmc RC4, with the network manager add-on; seems to be an rt2800usb
*** dmesg output "usbcore: registered new interface driver rt2800usb"

* '''SMC'''
** SMCWUSBS-N: Hardware detected as rt2800, but it is 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.

* '''Sony'''
** Sony UWA-BR100 802.11abgn Wireless Adapter [Atheros AR7010+AR9280] (Vendor ID: 0411, Product ID: 017f) - Tested with Raspbian. Needs package firmware-atheros.(B)

* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
** Tenda W311M Wireless N150 Nano USB Adapter ([http://www.tenda.cn/tendacn/Product/show.aspx?productid=375 product page]) - Works out-of-the-box with Raspbian as of 2012-12. Tested in WPA-Personal network. Runs without Powered Hub when plugged into Raspberry Pi.
** Tenda W311MI Wireless N Pico USB Adapter (identified as Ralink RT5370 Wireless Adapter; USB-ID: 148f:5370) - Works out-of-the-box for Raspian 2012/09/18 or later. An earlier version gave me problems.
** 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]
** Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.

*'''The Pi Hut'''
** USB 802.11n Wi-Fi adapter (from [http://thepihut.com/products/usb-wifi-adapter-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''TP-Link'''
** TL-WN321G (Ralink RT2501/RT2573, rt73_usb) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v? (Atheros AR9271, ath9k_htc) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v2 (ath9k_htc) Works OOTB in Debian Wheezy Beta. Runs without powered Hub when plugged into running Raspberry Pi, but the Raspberry Pi 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) | works OOTB with Wheezy Raspbian (2012-08-16) connected directly to raspberry pi (B) and AP functionality tested with hostapd.
** 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-WN723N (RTL8188SU); works OOTB with Raspbian 2012-09-17, (B) stable with 1 A PSU and without powered USB hub on r2.0. (a model B Pi with Arch Linux reboots if the dongle is plugged, restart sees the device without problems afterwards)
** TL-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.
** TL-WN821N v3 (ath9k_htc, htc_7010.fw); works out of the box on ArchLinuxARM, Wheezy and on OpenElec (>r11211), Problems with prior OpenElec; needs powered USB Hub (B). This chipset is also compatible with hostapd (wireless AP software)
** TL-WN822N v2 (ath9k_htc) works on ArchLinuxARM, with powered USB Hub. Successfully tested hostapd/dnsmasq.
** TL-WN823N Works out of box on Raspian using powered USB Hub

* '''Trendnet'''
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-648UBM TEW-648UBM] USB ID: 20f4:648b, works OOTB with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/ Adafruit Occidentials Raspbian Wheezy variant] as it includes kernel with [http://www.wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model%3A%3ARTL8188CUS%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols%0D%0A%3FMIMO+status%0D%0A%3FOUI%0D%0A&sort_num=&order_num=ASC&eq=yes&p%5Bformat%5D=broadtable&p%5Blimit%5D=500&p%5Bsort%5D=&p%5Boffset%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Blink%5D=all&p%5Bsearchlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&eq=yes RTL8188CUS driver built-in] (B)
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-649UB TEW-649UB] Works with OpenElec 3.0, chipset Realtek RTL8191SU

* '''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)
** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package

===Problem USB Wi-Fi 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.

* '''Alfa'''
** AWUS036NHA (Vendor ID: 0cf3, Product ID: 9271) - Tested with Raspbian. Works fine if connected after boot. Kills boot process if previously attached. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=16809&p=169469#p169469 Details here.]

* '''D-Link'''
** DWA-131 (rev. B1)
** DWL-G132 - In archlinux it is recognized - lsusb: 2001:3a03 D-Link Corp. DWL-G132 (no firmware) [Atheros AR5523] - but no wlan0 device is created - perhaps it needs the firmware to be loaded

* '''Edimax'''
** EW-7811Un (Vendor ID: 7397, Product ID: 7811) - Reports as containing the Realtek RTL8188CUS chipset listed below, no lockup or kernel oops under Wheezy, but dmesg reports constant timeouts trying to initialize the module. This appears to be resolved on 2012-09-18-Wheezy-raspbian and newer versions. EW-7811Un causes sporadic USB Issues when used together with steelseries 6G keyboard (repeated keys, possible file system corruption)
** EW-7811Un (Vendor ID: 7397, Product ID: 7811) - There have been issues with receiving UDP multicast packages in combination with most (not all) wireless routers. Nearly impossible to debug, since running a sniffer on the Pi makes everything work as expected.
** EW-7811Un It doesn't support Access Point and you can't use it for hostapd.

* '''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.
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].

== USB Bluetooth adapters ==
===Working Bluetooth adapters===
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.
* 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 Adapter 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
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
** http://www.element14.com/community/message/58288
* IOGear GBU321 (Broadcom BCM2045 Chipset)
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
* Trust BT-2400p
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).

===Working Bluetooth/Wifi Combo adapters===
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>

===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. Raspberry 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.
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.
* Asus USB-BT211
** Shows up as HCI device in Raspbian, but it does not scan or pair.
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962

== USB Ethernet adapters ==
===Working Ethernet adapters===
* '''AVM'''
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.
* '''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.
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
* '''Apple'''
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.
* '''Edimax'''
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.
* '''D-Link'''
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)
* '''LinkSys'''
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.
* '''Sabrent'''
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)
* '''Sitecom'''
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.
* '''A-Link'''
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.

The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190 mA, so there might be stability issues if additional power is not provided.
* '''Hama'''
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.
* '''Newlink'''
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.

===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. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out

== 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> . If you are not user ''pi'' you may need to add your username to the ''audio'' group thus: <code>sudo adduser yourusername audio</code> (user ''pi'' usually belongs to this group anyway).

* '''Creative'''
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]
* '''Daffodil'''
** [http://www.amazon.co.uk/gp/product/B002FI7GWK/ref=oh_details_o03_s00_i00 USB Sound Adapter US01]. Tested with low-cost headphone/microphone set via ''audacity'' (See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/DaffodilUSBSoundAdapter.html CPM-Spectre-Pi...DaffodilUSBSoundAdapter]).
* '''Edirol'''
** [http://www.roland.com/products/en/UA-1A/ UA-1A]
* '''GWCtech'''
** [http://www.gwctech.com/product3.asp?listid=3&id=4&subid=10&pid=788&typeid=96 AA1570 USB 7.1 Sound Card] (aka [http://www.conrad.com/ce/en/product/872990/USB-SoundBox-71 Conrad AA 1570 7.1 SoundBox]) - playback works fine, Recording stutters unless dwc_otg.speed=1 is set
* '''Hercules'''
** [http://www.hercules.com/fr/Cartes-Son/bdd/p/123/gamesurround-muse-xl-pocket-lt3/ Gamesurround Muse XL (Pocket LT3)]
* '''Logilink'''
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]
* '''Logitech'''
** [http://www.amazon.com/Logitech-Wireless-Gaming-Headset-Surround/dp/B003VANOFY/ref=sr_1_1?ie=UTF8&qid=1358114107&sr=8-1&keywords=g930 Logitech G930 Wireless Gaming Headset with 7.1 Surround Sound] (stereo works with ALSA, have not tried 7.1 Surround Sound)
* '''NuForce uDAC-2'''
** [http://www.nuforce.com/hp/products/iconudac2/index.php NuForce uDAC-2 Headphone Amplifier and USB DAC]
* '''Plantronics'''
** [http://www.ebay.com/itm/Genuine-New-Plantronics-External-USB-Audio-Soundcard-New-Sealed-/300845395889?pt=US_Sound_Card_External&hash=item460bc86fb1 Plantronics Stereo USB Adapter -01] (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter)
* '''Terratec'''
** [http://www.terratec.net/fr/produkte/Aureon_Dual_USB_12339.html Aureon Dual USB] (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers)
* '''Texas Instruments PCM2704'''
** [http://www.ti.com/product/pcm2704 PCM2704 98 dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]

==USB 3G Dongles==
* Huawei E1750
* Huawei E173
* Huawei E220
* Huawei E160 (AT commands only)
* 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 Raspberry 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].
*Sundtek
**Sundtek MediaTV Digital Home
**Sundtek MediaTV Pro
**Sundtek SkyTV Ultimate
**[http://shop.sundtek.de DVB-C, DVB-T, DVB-S/S2]: digital TV works, streaming to Windows / Linux is no problem. Easy installation [http://support.sundtek.com/index.php/topic,4.0.html English]
*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.
** Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer)
** Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian)
*K-World
** K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick. IR and supplied remote work with XBMC.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Raspberry Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Raspberry Pi itself. Tested with Astra 19.2E radio and SD-TV channels
*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 was detected, but it is not tested.
** [http://obrazki.elektroda.pl/8081115000_1317678968.jpg HDTV USB DVB-T] dongle, based on IT9135. This tuner comes in two revisions. Revision is printed on PCB.
*** rev. 1.0; should work with 3.2+ kernel, need confirmation.
*** rev. 2.0; works with kernel 3.6.11, without a powered hub. This tuner also requires a firmware (dvb-usb-it9135-02.fw) which can be downloaded from [http://logout.hu/bejegyzes/azbest/usb_dvb-t_tuner_it9135_rev2/hsz_1-50.html this page]. It's in Hungarian, so google translate or equivalent is recommended. The remote also works. According to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=29141 this post], there may be issues on some software configurations when using ''omxplayer''.

== USB Webcams ==

This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!

<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''Verified OS'''
| '''Verified OS version'''
| '''Verified Resolution'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F6D2CF;"
|Canyon
|
|CNR-WCAM820
|
| raspbian/wheezy
|
| 1280x1024
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK

|- valign="top" align="left" style="background: #F5FAFF;"
|CBR
|
| CW 835M Black
|
| raspbian/wheezy
| 2013-02-12
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Live!
| VF0470
|
| ArchLinux
|
|
| works out of the box on ArchLinux

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Socialize HD
| VF0610
|041e:4080
| raspbian/wheezy
| 2012-11-26
| 960x544
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Vista IM
| VF0640
|
| raspbian/wheezy
|
|
| works on Raspbian at 320x240 resolution, 15fps

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Webcam Notebook
| PD1170
|
|
|
|
| Detects, untested.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Webcam Pro
| PD1030
|
|
|
|
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")

|- valign="top" align="left" style="background: #F5FAFF;"
|HP
|WebcamHD-2200
| HD-2200
|
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|HP
|Webcam HD-2300
| HD-2300
|
|
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|HP
|Webcam HP-3100
|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

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C100
| V-U0013
|
| raspbian/wheezy
| 2012-08-16
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C200
|
| 046d:0802
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C210
|
| 046d:0819
| Raspbian/wheezy
| 2012-12-16
| 320x240, 640x480
| Works fine without external power.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C270
|
|
|
|
|
| With external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C300
|V-U0004
|046d:0805
|Raspbian/Wheezy
|2013-02-09
|320x240, 640x480, 1280x1024
|Works out of the box. Does not appear to require a powered hub.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C310
|
|
|
|
|
| Does not require a powered hub to capture snapshots

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C510
|
|
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C525
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C615
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C905
|
|046d:080a
|occidentalis
|v0.2
|1600x1200
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C910
|
|
|
|
|
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C920
|
|
| raspbian/wheezy
|
|
| With powered hub, detected out of box as Video0 V4L device

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Orbit/Sphere
|
|
|
|
|
| Works with external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro 9000
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro for Notebooks
|960-000047
|046d:0991
|Raspbian Wheezy
|2012-12-16
|160x120 320x240 640x480
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Ultra Vision
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 4000
|
|
|
|
|
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 9000
|
| 046d:0809
| Arch Linux
|
|
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).

|- valign="top" align="left" style="background: #F5FAFF;"
|Medion
|
| MD86511
|
| raspbian/wheezy
| 2012-07-15
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Mexxcom
|
| M-104
|
| raspbian/wheezy
| 2012-12-16
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam Cinemap 720p USB HD Webcam
| H5D-00001
|
| raspbian/wheezy
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
| Microsoft
| LiveCam HD-3000
| HD-3000
| 045e:0779
| Archlinux
| 2013-02-06
| 160x120
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam HD-5000
|
|
|
|
|
| Picture breaks up at the bottom

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam HD-6000
|
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| VX-7000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-3000
|
| raspbian/wheezy
|
|
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-500
|
| raspbian/wheezy
|
|
| Up to 352x288. Higher resolutions do not work.

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-800
|
| raspbian/wheezy
|
| 352x288
| Doesn't work at full resolution

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam Studio/Cinema
|
|
|
|
|
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|Xbox Live Vision
|
| 045e:0294
| Arch Linux
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|MSI
|MSI StarCam 370i
|370i (snake)
|
| Raspbian Wheezy
|
| 352 x 288
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.

|- valign="top" align="left" style="background: #A4B2CF;"
|Philips
| Webcam
| SPC 900NC
| 0471:0329
| Raspbian Wheezy
| 2012-12-16
| 160x120
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg

|- valign="top" align="left" style="background: #F6D2CF;"
|Realtek
|Generic Camera
|2SF022
|0bda:5801
|Raspbian Wheezy
|
|
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second
|- valign="top" align="left" style="background: #F6D2CF;"
|Silicon Motion
| SM731 Camera
|
| 090c:71b3
| Raspbian Wheezy
|
|
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS3
|
|
|
|
|
| The occasional frame is corrupted/stutters when running at 640x480

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
|
|
|
|
|
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
| SLEH 00030
|
| Arch Linux
|
|
| (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 Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012

|- valign="top" align="left" style="background: #F6D2CF;"
|T'nB
| Minipix 100K pixels
| IMWB032992
| 1e4e:0100
| raspbian/wheezy
| 2012-12-16
|
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
| 2 MP Auto Focus Webcam
|
|
| Arch Linux
|
|
| works out of the box

|- valign="top" align="left" style="background: #F6D2CF;"
|Trust
| SPACEC@M 200
|
|
| Arch Linux
|
|
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012

|-
|}

== USB GPS devices ==

*Columbus
** Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients)
*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: It works, but it may draw too 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 Raspberry Pi. 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 and USB to Serial (RS-232) adapters ==
A 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.

===Working USB to Serial Adapters===
*'''FTDI'''
**FT232 chip based adapters works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio.

** FT2232D dual RS232/FIFO works (used in various JTAG devices)

*'''Prolific'''
**PL2303 chip based adaptors works fine on latest Debian tested with ''minicom'' and ''gtkterm''

A USB to Serial (RS-232) adapter is used the other way around, ie. the USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment.

*"Best Connectivity" (Possibly also sold under the "Newlink HQ" or "Kenable HQ" labels)
**FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by ''lsusb'' as <code>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</code>. Appears as <code>/dev/ttyUSB0</code>, and requires the user to be a member of the ''dialout'' group (which ''pi'' is for ''Raspbian Wheezy''). Initially tested using an old RS Datalinker setup in "loopback" mode via ''microcom'' upto 9600 baud, and ''gtkterm'' after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently ''gtkterm'' was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

===Problem USB to Serial Adapters===
'''HL-340'''
*CH340 Chipset - '''Currently not supported by RPi''' but there is a patch of kernel code [http://tiagovaz.wordpress.com/2008/01/04/using-a-hl-340-usb-serial-adapter-against-2623-linux-kernel/ here], but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work.

== Other, exotic USB devices ==
=== Joysticks / Joypads ===
*'''Microsoft'''
**Xbox360 Controller (045e:028e): works. Tested with archlinux, connected to an USB Hub, used as "mouse" in X, package xf86-input-joystick

=== Numpads ===
*'''Conceptronic / Holtek'''
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub

=== USB to Parallel Port/Printer Adapters ===
*'''Prolific'''
**PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under [[RPi_Distributions#RISC_OS| RISC OS Raspberry Pi]] with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBtoParPrntAdapter.html CPM-Spectre-Pi...USBtoParPrntAdapter] for more info. and also a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/WheezyCUPS.html CUPS/Wheezy installation guide])

=== USB to SATA ===
*'''Nippon Labs'''
** 2.5" SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi. Built-in "Y" power adapter. Does work direct on some ver2.0 boards if used with 5.25 power supply, or Y adapter

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

=== Weather station ===
*Oregon Scientific WMRS-200 : Work out of the box (tested with Raspbian & wview)

=== 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 5 V at 0.5 A 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 it is 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 Raspberry Pi.
**Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168
=== USB RFID Reader ===
*Unbranded 125 kHz EM4100 RFID reader from eBay sellers (< £7), the one with a Windows logo on (easily scratches off for Linux users).
**Initially would not work when plugged in directly to Raspberry Pi. Worked when connected via an unpowered Trust hub. Worked after Raspberry Pi was modified with 10K resistors over the USB polyfuses (warranty invalidated). Probably would work fine with powered hub.
**Sends a 10 digit string to current window or console as if it was a keyboard. Can be captured independently of keyboard using Linux event interface (/dev/input), but the kernel in current distributions does not have CONFIG_INPUT_EVDEV selected so kernel rebuild is necessary.
=== JTAG ===
* FTDI2232D dual RS232/FIFO based JTAG (e.g. SheevaPlug JTAGKey USB-ID 9e88:9e8f)
** works using the Raspberry Pi as a development host
=== USB 3.0 Multi-Card Reader ===
* US Robotics All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously
** SD/MMC + MS/MS PRO or DUO/DUO PRO + CF/MD + SM + SD/MMC or MS/MS PRO. Useful for backing up cards containing other OS Distros
=== Tinkerforge Bricks and Bricklets (http://www.tinkerforge.com) ===
* Read out sensors and control motors over USB with open source hardware.
* Tested with the brickd_armhf.deb from [[http://www.tinkerforge.com/doc/Downloads.html#tools: here]] with:
** sudo apt-get install libusb-1.0-0 libudev0
** wget http://download.tinkerforge.com/tools/brickd/linux/brickd_linux_latest_armhf.deb
** sudo dpkg -i brickd_linux_latest_armhf.deb
* Tested languages: C/C++, C# (mono), Free Pascal (Lazerus), Java, PHP, Python, Ruby (see [[http://www.tinkerforge.com/doc/Software/API_Bindings.html: here]] for installation).
* If a big amount of Bricks is used, a powered USB Hub may be required.

== 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 keyboards'''

All above tested with the famous "blue cube" on a powered USB hub.

*IBM Model F (please note requires an additional AT to PS2 converter)
*Dell AT101w
*Northgate Ominikey Ultra T (please note requires an additional 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 it 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 5 V. 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===
* '''Adafruit'''
** 5.25 V 1 A Model 501 (Newark 44W4932) USB 110-240 VAC power supply [4.99-5.01 V @ T1/T2 with 100 mA BT and/or mini wireless-n on RPi USB ports]
* '''AlcaPower'''
** 5 V 2.5 A Model AP5A - Charger/switching with 7 connectors(also Microusb)
* '''Ansmann'''
*** Dual USB charger slim, Model-Nr. 1201-0001
* '''Apple'''
Note that apple designs its charger products to work optimally as '''chargers''', in practice this means that apple chargers drop their output voltages somewhat with output current, so that the charging circuits do not need to dissipate more heat than is strictly necessary. Because of this, and although many people have reported apple products to power their basic PI setup reliably, its still not an optimal choice for a PI system that uses power hungry USB devices. Also, because of the popularity and high price of these chargers there are many very sub standard, but almost impossible to recognize as fake copies on the market, and some of these fakes are about the worst things you can try to power your PI with! Not only do they not work, they may actually be dangerous to use!
** 5 V 2.1 A USB charger for iPad2, model A1357
** 5 V 1.0 A USB Charger for iPod
** 5 V 1.0 A USB Charger for iPhone 4
* '''Amazon'''
** 5 V 0.85 A USB charger for Kindle
** 5 V 2 A Mains to USB A adaptor, Branded "CostMad"
* '''Asus'''
** 5 V 2.0 A USB charger for Google Nexus 7
* '''Bandridge'''
** 5 V 1.0 A Mobile Phone Charger (Model: BPC3102EC)
* '''Belkin'''
** 5 V 2.6 A 4 port Ultra-Slim Desktop hub (Model F4U040) (Raspberry Pi running from USB hub port)
** 5 V 2.5 A 4 port USB Hub (Model F5U404) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB 2.0 Mobile Powered Hub (Model F4U018) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB Hub (Model F5U706) (Raspberry Pi running from USB hub port)
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)
** Universal USB Wall Charger (5 V 1 A) (Model F8Z222uk)
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** Charger for Tour 9630
** 5 V 0.7 A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
** 5 V 750 mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)
** 5 V 750 mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)
** 5 V 2 A Model PSAC10R-050QT, RIM Part Number HDW-34725-001
** 5 V 550 mA curve 8520 charger works with raspberry pi Model B Board v. BS1233. It does not work with Raspbmc image.Symtoms are frequent key board and external hdd disconnects.
* '''Deal Extreme'''
** [http://dx.com/p/5v-2a-regulated-switching-power-supply-110-220v-94518 S-10-5 5 V 2 A Regulated Switching Power Supply (110~220 V)] (DIY: requires additional micro-USB connector and wiring)
* '''Dell'''
** USB Hub integrated in Dell monitors (B)
* '''The FX Factory'''
** 5 V 1 A (1.2 A max) AC Travel Charger Model KJ-USB Mains. Typically provides 4.9 V at 1 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>
* '''Garmin'''
** 5 V 1 A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6 ft cable (F3U151B06) works.
* '''Gembird'''
** 5 V 2 A Universal USB Charger (Model: MP3A-UC-AC5). Test: 1080p TV (1xHDMI), USB Wi-fi adapter (1xUSB), wireless keyboard and mouse (1xUSB). Results: ~5.3V, works without any problems (own usb cable required).
* '''Globe Electric'''
** 2-Outlet Tap with Surge Protection and 2 USB Chargers ([http://globe-electric.com/product/2-outlet-tap-with-surge-protection-and-2-usb-chargers-grounded-white/ 46082]). Rated at 1000 mA. 120 V systems only.
* '''Griffin'''
** Power Block Model P2417. 5 V 2.1 A
** Power Block Model P1190R2 Two USB 5 V Outputs, 1 A each
* '''Hama'''
** 1000 mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)
* '''Hartig + Heiling GmbH & Co. KG'''
** H+H SN 6 USB
* '''HP'''
** 5.3 V 2 A Charger for HP Touchpad (B)
* '''HTC'''
** 5 V 1 A TCP-300 USB phone charger (B)
** 5 V 1 A TC B250 USB charger (HTC R/N: 79H00096-00M)
** 5 V 1 A TC E250 USB charger (HTC R/N: 79H00098-02M)
* '''i-box (Philex Electronic Ltd)'''
** 5 V 1 A 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'''
**15 W Dual USB Adapter. Model: mMini AC15. Output: 5 V, 3 A (max per port), 15 W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Specification sheet]
* '''Kodak'''
** 5 V 1 A TESA5G1-0501200
** 5 V 1.0 A K20-AM
* '''König'''
** 5 V 1 A PSUP-GSM01
* '''LG'''
** 4.8 V 1 A Travel Adapter
** 5.1 V 0.7 A Travel Adapter (Model: STA-U34WVI)
** 5.1 V 0.7 A Travel Adapter (Model: STA-U12ER)
* '''Logic'''
** 4 port USB Hub (Model LP4HUB10). (Raspberry Pi running from USB Hub port, red power line (+5 V) inside hub cut) (B)
*'''LogiLink'''
**5 V 2.1 A Switching power supply, model PA0040 (B)
* '''Logitech'''
** 5 V 1 A SDC115-USB Remote Control Charger and cable
* '''Maplin Electronics'''
** 5 V 1 A dual USB power supply, model number H25B-MT-K2
** Micro USB Power Supply N19HX
* '''Medion'''
** 5 V 1 A USB power supply for OYO ebook reader
* '''Microsoft'''
*** Zune Zune AC Adapter v2
* '''ModMyPi'''
** [https://www.modmypi.com/shop/5v-2A-modmypi-raspberry-pi-power-supply 5.25V 2A HQ Raspberry Pi USB Power Supply] (Detachable USB) [5.01 - 5.07V @ T1/T2 with Wifi dongle and Wireless Mouse/Keyboard on RPi USB ports]
* '''Motorola'''
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5 V 0.85 A SPN5504 Charger with Cable]
* '''Noname'''
** 5 V 2.1 A 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.2 V 1 A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]
** 5 V 1 A Model H-IP008 Serial No. H10T80L068
* '''Novatel Wireless'''
** 5 V 1.05 A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5 V 0.7 A Charger for Orange San Francisco
* '''Palm'''
** 5 V 1 A Charger for Palm Pixi+ (B)
* '''Pantech'''
** 5.0 V 1 A CNR USB with LG DLC100 micro USB cable
* '''Petzl'''
** 5.0 V 1 A Charger that came with the Tikka core2 XP
* '''Phihong'''
** Switching Power Supply. Model: PSAC09R-050. Output: 5 V, 1.8 A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
* '''PortaPow'''
** PortaPow UK Mains Wall Power Supply
* '''PowerGen'''
** PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. [http://www.amazon.com/gp/product/B0073FCPSK Amazon Link]
* '''Rayovac'''
** Universal USB Charger Model: PS69 100-240 VAC to 5 V 1 A (small cube w/folding plug) works w/wireless keyboard/mouse and mini-Wifi connected
* '''RS Components'
** HNP06UK (RS 7263069) Switching Adapter 5.0 V 1200 mA
* '''Samsung'''
** 5 V 0.7 A Charger for Galaxy S model ETA0U10EBE
** 5 V 0.7 A Charger for Galaxy SII
** 5 V 1 A Charger for Galaxy SIII
** 5 V 1 A Charger for Galaxy Nexus
** 5 V 0.7 A Charger for Galaxy S Vibrant (SGH-T959)
** 5 V 0.7 A Travel Adapter model ATADU10EBE
** 5 V 1 A? Samsung C Series TV USB-port for external HDDs. Running stable with openelec
** 5 V ?A (Unknown) Samsung Service Port (USB) on LN32A330J1DXZA 720p 32 inch HDTV
** 5 V Unknown Ampere Samsung UA22D5000 & UA32D5000 TV USB Port. Test with Raspbian Wheezy, Raspbmc, and RPITC
* '''Shun Shing'''
** 100-240 VAC to 5 VDC 1 A USB power supply, model SP5Q-AU [http://jaycar.co.nz/productView.asp?ID=MP3455 Jaycar]
* '''Sony Ericsson'''
** 5 V 0.7 A Charger CST-80
** 5 V 0.85 A Greenheart Charger EP800. Typically provides 4.8 V at 0.85 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>.
* '''StarTech'''
** 4 Port USB 2.0 Hub Raspberry Pi can be powered just by plugging USB input into the Raspberry Pi, don't need power in micro USB port.
* '''Travel Charger'''
** 5 V 2.0 A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]
* '''Technika'''
** 5 V 1 A USB Power Adapter, model MPASS01 (B)
* '''The Pi Hut'''
** Micro USB Power Supply for the Raspberry Pi. 5 V 1000 mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])
* '''Trisonic'''
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5 V, 800 mA) $3 at Daiso U.S. stores.
* '''TruePower'''
** [http://u-socket.com/ U-Socket] 5 V 2.1 A AC Receptacle with Built-in USB ports (2.1 A 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])
* '''ZTE'''
** ZTE Blade charger STC-A22O501700USBA-A 5 V 700 mA

===Problem power Adapters===
* '''Nokia'''
** 5 V 1.2 A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2
** [http://accessories.nokia.com/products/nokia-fast-usb-charger-ac-16/ 5 V 1 A AC-16E Charger] Provides only 4.7V across TP1 & TP2 when at idle

* '''Masterplug'''
** Masterplug Surge Protected USB Adaptor 2 x 1 A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artifacts using HDMI.
* '''Monoprice'''
** 5 V, 2 A 3 Outlet Power Surge Protector Wall Tap with 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot. Measured to less than 4.75 V between TP1 and TP2 when used with a Monoprice cable.
* '''Sony Ericsson'''
** 5 V, 850 mA EP800. Some failures to boot, Ethernet loops at boot.

===Working external Battery packs (with 5 V regulated output)===
* '''Anker Astro3'''
** Anker Astro3 10000 mAh with dual 2 A USB output
* '''Duracell'''
** PPS2 Instant USB Charger
* '''Energizer/XPAL'''
** XP18000 18000 mAh Power Pack
* '''Generic - eBay no brand'''
** 6000T Pocket Power 5000 mAh - eBay item 271009959140
** Power Bank for iPad/iPhone 5000 mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938
* '''Mophie'''
** 38113BBR Juice Pack Powerstation 4000 mAh: output 2.1 A max: included charging cable powers RPi, 7.5 hrs light use w/keyboard and mini-Wifi on RPi ports
* '''New Trent'''
** iCurve IMP70D 7000 mAh (Approx 12 hours from full charge)
** IMP120D 12000 mAh
* '''Sinoele'''
** Movpower - Power Bank 5200 mAh (8 hours with Wi-Fi active)
* '''TeckNet'''
** iEP387 Dual-Port 7000 mAh External Power Bank (The charging lead can be used to connect the Tecknet to the Raspberry Pi. Ran the Raspberry Pi with Wi-Fi dongle and wireless keyboard receiver for over 9 hours of light use.)
** iEP392 Dual-Port 12000 mAh External Power Bank (1 A port, ~16.5 hours)
** Rayovac PS60 5 V 800 mAh
* '''VINZO'''
** Power Bank 5000 mAh Grey Output 5 V 1000 mA
* '''Kodak Power Pack KP1000'''
** 1 A USB rechargeable battery pack - see [http://blog.sheasilverman.com/2012/09/its-alive/ Shea Silverman's blog]

== 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 Raspberry Pi's primary input fuse. HDMI ports (and the raspberry PI) are designed so that they deliver a very limited amount of power (50 mA) 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 200 mA, 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 non externally powered devices. If you have bought a non externally powered HDMI to VGA adapter, and you experience problems with it (It behaves badly, D1 burns out, F3 "blows", or your PSU overloads), then not all is lost, there are cheap (a few dollars) adapters that allow you to add external power to the HDMI cable! An example can be found here: [http://dx.com/p/hdmi-male-to-hdmi-female-adapter-w-power-input-port-black-155361].

===HDMI->DVI-D cables===
HDMI to DVI-D cables, or HDMI cables with an DVI-D adapters should work, connected to a DVI-D monitor, that is because both HDMI and DVI use the same kind of digital signaling (LVDS). The only limitation being that DVI-D misses the signal channel for audio.

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.

* '''The Pi Hut'''
** HDMI to DVI Cable for the Raspberry Pi (from [http://thepihut.com/collections/video-output/products/hdmi-to-dvi-cable-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
* '''Other Variants'''
** AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.
** [http://www.ebay.com/itm/DVI-Female-to-HDMI-Male-Adapter-Converter-Adaptor-Gold-for-HDTV-Full-HD-/320946033059?pt=US_Video_Cables_Adapters&hash=item4ab9dfd1a3 A generic HDMI-to-DVI converter from eBay]. Works well, but it's probably the cause of some power loss between the Raspberry Pi and the monitor, causing [http://elinux.org/R-Pi_Troubleshooting#Interference_visible_on_a_HDMI_or_DVI_monitor this] problem. A setting of config_hdmi_boost='''5''' in /etc/boot solved this. Note that config_hdmi_boost='''4''', as suggested in the troubleshooting guide, helped, but it did not solve the problem completely.

===HDMI->VGA Cables===
HDMI to VGA cables do not work!
They rely on logic incorporated in a video card that isn't available in a PI.
Somehow such a video card outputs analog signal on the otherwise purely digital HDMI connector, that seems to be the only way for it to work.
But normally HDMI cables never carry analog signals and the PI surely doesn't output analog signals either, almost no HDMI output device does, as its completely against HDMI specifications.

===HDMI->VGA converter boxes===
HDMI to VGA converters do work, they convert the digital serial data streams from HDMI and using complex logic, and digital to analog converters they convert the HDMI signal to the analog signals needed for VGA, and sometimes also convert HDMI audio to an analog stereo signal. But note that if they feed off the PI it can cause a problem, as the PI only is designed to provide about 50mA to the (HDMI or DVI-D) monitor, and these adapters use >200mA, while the absolute maximum the PI can let through is 200mA.
These adapters also thus use about half the energy that the PI (without USB devices) uses.
Therefore its much better to use an adapter that has an external power input. Alternatively there are HDMI dongles (male to female HDMI adapters) that have a barrel input connector to feed the adapter with.

Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.

At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.

[http://www.element14.com/community/groups/raspberry-pi/blog/2012/08/16/raspberry-pi-hdmi-to-vga-converter Sanoxy HDMI to VGA converter], $27 from Amazon, no changes required with official Raspbian Wheezy image (2012-Jul-15), note: had already disabled overscan previously

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 Raspberry Pi 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 1 A 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 Raspberry Pi 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 +5 V connection adapted from a USB cable, which bypasses Raspberry Pi's Micro USB cable and polyfuse F3.

* Link to a gallery with detailed images & steps of the same adapter modification: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

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. In-depth review http://raspi.tv/2013/hdmi-to-vga-video-converter-with-sound-for-raspberry-pi-review.
Requires HDMI boost and overscan, [[RPi_config.txt|config.txt]] settings for 640x480 @60 Hz:
 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

It seems unlikely any of these HDMI->VGA converters could be used for driving a SCART RGB SD CRT TV with a suitable lead (as shown here for ATI/Nvidia PC output http://www.mythtv.org/wiki/RGB_Scart) because they only output preset progressive resolutions, whereas the TV will need an interlaced resolution and probably custom timings.

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 it is very pricey compared to the 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.4 A, which is too much draw for the 5 V 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 it is 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. It is very cheap, but it 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 60 Hz, 1024x768 60 Hz, 640x480 works) The adapter is based on Lontium LT8511A chip, but I was unable to get the specification for it.
The D1 diode is getting very hot though. Most likely the adapter drives more than 200 mA. The standard RS Components 1.2 A USB power supply is able to provide enough power for the Raspberry Pi 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 Raspberry Pi's RCA video output. Additionally using a splitter cable (3.5 mm 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 ==

The SD card section has been moved to a separate page. See [[RPi SD cards]]

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}
♦
nbsp;V 1nbsp;V 1000

User:TrevorGowen

2013-03-07T11:07:44Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 07.03.2013, Now trying out expansion/proto-typing boards and a "Model A" version).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

R-Pi Troubleshooting

2013-03-05T13:09:40Z

TrevorGowen: /* No HDMI output at all */ HDMI "hotplug" detection issues with 2013-02-09-wheezy-raspbian (update)

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

===Normal LED status===
There are five LEDS near the USB connector.
{| border="1"
|+ LED statuses
! LED
! colour
! function
! normal status
|-
| ACT || green || card status || flashing during SD card activity
|-
| PWR || red || power || steady ON when PI receives some power
|-
| FDX || orange || full duplex || on when Ethernet connection is full duplex
|-
| LNK || orange || link || on when Ethernet is connected
|-
| 100 || orange || 100 Mbps || on when connection is 100 Mbps off when 10 Mbps
|}

See the next sections for how to interpret other statuses.

===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===
''note; For technical reasons the green LED might light up very faintly, this is normal, but it doesn't mean it "burns" (or that it, too rapidly to see "blinks"). In fact the faint glow means '''no boot code has ever been executed''', as almost the first thing that the boot code does is to turn the faint glow off! When flashing/blinking the green LED should light up as bright as the power LED.''
*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. Did you have admin rights when you used the SD-card writer software? Without it the software might go through the motions without actually doing anything! To check if the writing process did actually happen Insert the SD card into a Windows machine and you should see bootcode.bin, fixup.dat and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]]. It is also possible that the image you are writing to the card is corrupt, as downloads do occasionally end up corrupted or truncated. You can check with the checksum utility if your download is correct.

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

*Confirm the USB cable is properly seated in the power slot. The red power LED does not necessarily mean it is fully connected.

*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 may be 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]]

*If for whatever reason the main polyfuse F3 has been overheated previously it may happen that it hasn't completely recovered, in which case, if you turn the PI on, a considerable amount of energy from the power supply is lost in the fuse and doesn't reach the PI. Try if the polyfuse seems hot. For this problem too read [[#Troubleshooting_power_problems]].

*Some problems have been reported if the ambient temperature is low that might be related to micro-fractures, fissures in solder or other issues. Try heating the Raspberry Pi with a hair dryer for just a few seconds (do not use excessive heat or you may cause irreversible damage!) and reconnect the power. Check this video http://www.youtube.com/watch?v=AwF6v-4NFdg

===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
* 7 flashes: <tt>kernel.img</tt> not found

Firmware since 20th October 2012 no longer requires loader.bin, and the flashes mean:

* 3 flashes: <tt>start.elf</tt> not found
* 4 flashes: <tt>start.elf</tt> not launched
* 7 flashes: <tt>kernel.img</tt> not found

If start.elf won't launch it may be corrupt.

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

With recent firmware, a coloured splash screen (actually its just four pixels "blown up" by the GPU to full screen) is displayed after GPU 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===
''note:during entering the password most linux distro's wont show that you typed in anything (not even "*" characters) this is normal behaviour, try the keyboard while entering the user name!''

This is most 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: 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.

Some users have reported that their keyboards work fine on Arch linux, but on Debian distro's, their keyboards become erratic (repeats and/or skips key presses). One suggested remedy to this, which has some positive feedback, is to adjust the USB bus speed. To do this, you need to edit the cmdline.txt file, and add "dwc_otg.speed=1" (without quotes) to the end of the file (found in the /boot directory).

Worst case scenario, some (advanced) keyboards, such as the Roccat Arvo, have kernel modules that need activating. If you have access to another keyboard temporarily, you will need to modprobe the relevent driver. Or if this is not possible, you can rebuild the kernel (instructions available on the wiki page) with the modules installed. (to find the drivers for keyboards etc, you need to find "Device Drivers -> hid Devices".)

===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/512M of RAM is divided between the ARM and GPU:
gpu_mem=16 : 16M GPU, 240M/496M ARM split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
gpu_mem=64 : 64M GPU, 192M/448M ARM split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
gpu_mem=128 : 128M GPU, 128M/384M ARM split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch, edit the gpu_mem= setting in your config.txt and reboot.

Note: other amounts are also possible, but setting gpu_mem=32 is usually the wrong choice. gpu_mem=16 is almost always a better choice.

Also note that before the release of the 51MB PI a different method was used based on splitting the 256MB RAM in a part for the CPU and GPU. As this noting system was causing trouble if the amount of RAM was not always the same. the above new method was adapted.

Make sure your editor doesn't change the first letter of the line into an uppercase letter, as some editors do. The entry is case sensitive.

== 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 on the rev 1.0 PC board. It is correctly labeled "100" on the rev 2.0 PC board. When that LED is on, RasPi is 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:
* Raspian "wheezy" pi/raspberry
*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.

'''More reasons why sound does not work with an HDMI monitor'''

With an HDMI connection it might be possible to hear:
./hello_audio.bin 1
but not:
aplay /usr/share/sounds/alsa/Front_Center.wav

Firstly, it seems that some HD TVs mute audible sound output when there is no digital input, and slowly fade the sound up and down at the start and end of digital input. This means that short duration sounds will not be heard. A work around is to play longer duration wav files.

Secondly, it seems that some HD TVs mute audible sound output when there is only one channel of digital input. So, as the file Front_Center.wav is mono, it might not be heard. ALSA aplay uses the file information header to configure its digital output. And the aplay -c 2 option does not over-ride the settings aplay picks up from the file information header. So, if your HD TV doesn't accept just one channel of digital input, you cannot use aplay to hear a mono wav file. However, with the command speaker-test, the -c2 option does work, and sets 2 channels in the digital stream. So speaker-test can be used to hear the file Front_Center.wav in either the left or right speaker using the -s option 1 or 2.
For example
Speaker-test -c 2 -s 1 -t wav -W /usr/share/sounds/alsa -w Front_Center.wav
should be heard on the left speaker. But note that the command speaker-test seems only to like mono wav files, and seems not to play stereo wav files.

The command aplay plays 2 channel stereo wav files in stereo sound without problem (provided they last longer than the time it takes the TV to unmute and remute). A helpful example I found is the stereo file LRMonoPhase4.wav at the Kozco web site [http://www.kozco.com/tech/soundtests.html]

===Sound does not work at all, or in some applications===
Enter the command 'alsamixer' and use the control to check that the volume is up (arrow keys) and that the output is not muted (M key).

In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To install support for sound, type the following from a command line (from the command prompt ''before'' "startx" or in a terminal window)

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled by default, so the 'modprobe' step is not necessary. Next try:

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:

amixer cset numid=3 <n>

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

If you have pulseaudio installed you need to also specify the card number:

amixer -c 0 cset numid=3 <n>

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.

Following this setup, you should be able to play wav files with the command

aplay "my file.wav"
Other command features can be found with
aplay --help
You will find numerous test files under /usr/share/scratch/Media/Sounds/ .

===Removal of installed pulseaudio===
Between December 2012 and February 2013 the standard raspbian wheezy distribution, and apt-get upgrade, included pulseaudio. Forum posts suggest that pulseaudio can break alsa. Whilst some members identify various workarounds, others find only removal of pulseaudio restores sound output.
sudo apt-get --purge remove pulseaudio

===Playing MP3 files===
The alsa app included in the standard distribution plays wav files. If you want to play mp3 files, do the following to install an mp3 player (after installing alsa-utils):

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install mpg321

You can play mp3 files with the command

mpg321 "my file.mp3"

Other command options can be determined with
mpg321 --help
The mp3 support with this app is complete but not robust.

==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. At your own risk, you can go up to 11, but risk frying a sensitive monitor.

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|Troubleshooting Power Problems]].

===No HDMI output at all===
[[File:GPIOs.png|thumb|200px|right|The PI's GPIO header P1 [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]
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 Rasbian Wheezy] image (recommended) then try
hdmi_safe=1
Which will force the PI to boot in "safe mode".

For a quicker way to force wheezy into booting in safe mode, which doesn't need editing config.sys, you can also try to boot while holding the GPIO header P1-pin-5 (GPIO 1, SCL) low. This pin is normally held high with a pullup, but if you place a jumper between pin 5, (GPIO 1) and pin 6, (GND) of the GPIO header it will force the PI to boot in safe mode, which will force a 640x480 VGA screen mode, which any HDMI device should be able to display. Be very careful not to connect any other pins, especially not pins 1 and 2 (3V3 and 5V) as doing so, with power on, will damage your PI!

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

A similar problem has occured following the installation of [http://www.raspberrypi.org/downloads Rasbian Wheezy image] "2013-02-09-wheezy-raspbian" - the hotplug signal appeared to be no longer detected when a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/HDMI3PortSwitcher.html HDMI 3 Port Switcher] was in use for the Pi running from that image. An older, but updated and upgraded image still worked, as did a similar image on the other Pi connected to the switch, but, unless the above override was implemented, the Pi with the new image would only provide a HDMI display when '''directly''' connected to the monitor. The same problem has re-occurred when using that wheezy image with a new (in March 2013) "Model A" Pi.

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|Troubleshooting Power Problems]].

Here's a rare cause: A standard HDMI cable has five individual ground wires plus a shield. Some cheap HDMI cables do not implement the individual grounds and just have a common foil shield that's connected to the HDMI plug shells at both ends. This works OK in most HDMI applications since most HDMI sources (like RasPi) and most monitors connect the shells to circuit ground. However, some HDMI or DVI monitors may requires individual ground lines. You can tell if an HDMI cable implements the individual grounds by checking for continuity using an Ohmmeter or multimeter. You can find the HDMI pinout for full-size connectors at [http://en.wikipedia.org/wiki/HDMI Wikipedia].

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

===HDMI -> VGA adapters===
Some good information can be found here:
* [[RPi_VerifiedPeripherals#HDMI-.3EVGA_converter_boxes]]
* [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 (RPi forum) Serious HDMI Problems. What's that smell? Burning Raspberry!]

A commonly used adapter from Ebay: gallery with detailed images & steps of a modification to use external power source: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

==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 commands
sudo apt-get update
sudo apt-get upgrade

==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 Micro USB power cable is low quality. Some Micro USB cables have very thin conductors, resulting in enough voltage drop for RasPi to fail even if the power supply itself is fine. For details, 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.
* The F3 Polyfuse could be blown or bad, see below for how to test.
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]]

'''How to test the F3 polyfuse<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=22318</ref>'''

# Remove all the things plugged into your Raspberry Pi, including SD card.
# Locate the TP2 test point on the top of the board.
# Turn your board over and find the TP2 test point on the bottom of the board. One lead of your multi-meter will always be on the TP2 point on the bottom of the board for all tests.
# Plug your power supply into the micro usb port and power your board.
# Place one lead of your multi-meter on the TP2 point on the bottom of the board and one lead on the side of the F3 fuse closest to the edge of the board. Note the voltage. This is the voltage coming into your RPi from your power supply.
# Keeping one lead on TP2, move the other lead to the side of F3 closest to the SD card slot. This is the voltage coming out of the F3 fuse.

[[File:F3-testing.jpg|none|frame|Multi-meter lead placement for testing the Raspberry Pi F3 Polyfuse]]

If the voltage is different by more than about 0.3v you probably have an issue with the F3 fuse<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24005&p=222526#p222526</ref>.

When polyfuses "blow" their resistance increases dramatically, there by limiting the voltage that can pass through them. If your power problem suddenly appeared after your board was known to be working fine, it is probable the fuse is just "blown" and will return to normal. Polyfuses recover from the tripped state to near their normal value in a few minutes, but do take some hours to fully recover so leave it unpowered and check it again in a little while.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24005&p=222549#p222543</ref> If your power problem has been since the first time you plugged in your board, the fuse was probably bad when it arrived and should be returned to place you purchased it.

Also, on a related issue, do note that if you do not power the PI in the "official manner", that is through it's micro-USB port, but use any alternative way (such as through the GPIO header, the test points TP1 and TP2), but also by back-powering it, '''you are actually bypassing the PI's input polyfuse protection device!''' This can have extreme consequences if ever you manage to put more than 6V on the PI, even for a very short period. As this causes the overvoltage device D17 on the the PI to trigger and short the 5V supply! Without the polyfuse limiting the current through D17, it will burn out, probably melting the PI's enclosure with it, (if you have any) and possibly causing a fire-hazard. It will probably also create a permanent short of the 5V supply! So be warned, and if you use back power make sure your hub or its PSU has a fuse to prevent this from happening. If not, add your own fuse.

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

User:TrevorGowen

2013-03-03T14:25:30Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 03.03.2013, Now trying out expansion/proto-typing boards and a "Model A" version).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, "Model B" Pi, with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure] - eventually repaired with black [https://slatersplastikard.com/ "plastikard"]) and a new "Model A" Pi

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User talk:Wmat

2013-02-24T21:52:10Z

TrevorGowen:

Test talk page email.

Hi there. Are you able to remove spam user accounts? I've been blanking out their user pages but it would be good to remove the accounts completely. [[User:Andrewmk|Andrewmk]] 15:35, 3 August 2012 (UTC)

Yes, I typically monitor the Recent Changes and when I see spam, I delete it and ban the User. --[[User:Wmat|Wmat]] 15:57, 3 August 2012 (UTC)

== Adminship ==

Hi, I'm Jeff, and I'd love to help you out on eLinux. I am on MediaWiki.org (User:Jeffwang) and I also run my own web host service (http://www.mywikis.com). I have years of experience on wikis and with adminship, I can help you ban spam users. Thank you. --[[User:Jeff|Jeff]] 23:04, 20 September 2012 (UTC)
:Replied to your email. Good luck with those bogus accounts!

== Image uploads are broken ==

FYI. --[[User:Shinnsm|Shinnsm]] ([[User talk:Shinnsm|talk]]) 16:09, 2 November 2012 (UTC)

THanks, I'll look into it. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 16:11, 2 November 2012 (UTC)

Uploads should be fixed now. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 17:12, 2 November 2012 (UTC)

== Difference between guides and tutorials in the Pi section ==

Hi!, not sure what is the difference between both of them? They sound kind of redundant. Shouldn't it be better if they were fused?. --[[User:Itxaka|Itxaka]] ([[User talk:Itxaka|talk]]) 03:59, 23 December 2012 (UTC)

If you see guides and tutorials that could be merged together, feel free to merge them. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 13:38, 23 December 2012 (UTC)

== Re: "Jeff's" "Raspberry Pi Wiki Council" ==
Although I offerred to help with the above "in good faith" I now believe I was misled and somewhat naive. I have now disassociated myself with the above but hope that my contributions elsewhere will still be welcome. --[[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) 21:52, 24 February 2013 (UTC)

eLinux.org:RPi Council

2013-02-24T21:39:10Z

TrevorGowen: /* Current council aldermen */

{{Hub Flags}}
{{Clear}}
Because of the messed up stuff on the Raspberry Pi wiki, I have found it necessary to create a governing council for the RPi wiki. Please edit the below section if you'd like to become a member (alderman) of the council.

Note: This is official and is ok with the administration of eLinux.

== Supplemental guidelines ==
''If anything is wrong with these guidelines please feel free to edit them. Thank you.''
=== Guidelines are made from consensus ===
All supplemental guidelines and decisions will now be made by the RPWC and eLinux administration.

== Current council aldermen ==
* President - [[User:Jeff|Jeff]]
* <s>[[User:TrevorGowen|Trevor Gowen]]</s>

== Current issues ==
=== Users ===
==== Mahjongg ====
<s>As he is not answering my requests for identity, he may be impersonating Mahjongg on the forums. I propose the account be blocked indefinitely because it clearly is copying the RPi forum mod's user name.</s> --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:26, 5 October 2012 (UTC)
:Verified thru PM. Case closed. :) --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 21:16, 5 October 2012 (UTC)

==== Ghans ====
I propose that since he ruined a lot of formatting that he is not to edit the Raspberry Pi Wiki's formatting for 1 month. You can see clearly [[RPi Wiki Best Practice|here]]. He, in fact, misguided everyone in best practices! I want you to go to Wikipedia and take a hard stare and compare the articles! They are misleading! He clearly cannot go on with this! Anyone else agree? --[[User:Jeff|Jeff]] 02:15, 2 October 2012 (UTC) '''Edit: and also add a block of 1 month if he does not comply.''' --[[User:Jeff|Jeff]] 22:39, 2 October 2012 (UTC) 
(Note: This decision must be concluded by Wednesday, October 3, 2012.)
:Having compared [[RPi Wiki Best Practice|Ghans' "Best Practice"]] with which, I believe, are the equivalent areas of Wikipedia and parts of the Help sections here I can see what you mean. However, using Wikipedia as a guide, one also has to assume that he was writing with the best of intentions. Unfortunately he does not reveal much about his background, experience etc. on his user page. However, having had the experience of encouraging "best practice" within a mixed group of programmer's of different backgrounds (scientific, computational) and training (formal, informal, none), I am well aware that when considering adopting such from a related area, one also has to consider the needs etc. of the intended users ie. adopt as much as is appropriate, adapt or reject the remainder. An analogy would be that when preparing a presentation one may end up with several versions depending upon the expected audience. Hence, whilst I am prepared to support your proposal, it is on the understanding that this is done so to allow us to begin to formulate more suitable guidelines, given that, eventually, hopefully, there will be younger, enthusiastic but less experienced contributers whom I would not wish to discourage. --[[User:TrevorGowen|TrevorGowen]] 14:40, 2 October 2012 (UTC)
::So you're a support? --[[User:Jeff|Jeff]] 22:32, 2 October 2012 (UTC)
:::Assuming I'm interpreting your update above correctly, to mean that he is requested to refrain from edits that change formatting aspects of the Raspbery Pi sections of the Wiki for one month and ignores that request, yes. Hopefully such a request will generate a response, therebye opening up a dialogue, which may resolve matters such that a formal block need not be imposed. --[[User:TrevorGowen|TrevorGowen]] 12:09, 3 October 2012 (UTC)
I guess I will close this with a warning to Ghans. Block not implemented. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:39, 3 October 2012 (UTC)

=== Content ===
==== Shutdown of most other language "hubs" ====
'''Due to the importance of this topic, ''everyone'' is invited to post their opinions, even users that are not a council member.''' 
These hubs serve no purpose but to point the respective language speakers to English pages. This is utterly useless. If I only spoke Greek, I would be able to understand the hub, but the hub's purpose is to link to other pages. Unfortunately I would ask a Greek community for help because the links are to ENGLISH pages! Why don't we just tell everyone a bold message: THIS IS AN ENGLISH WIKI! I propose to redirect all these pages to the English page; as for the template Hub Flags, I propose it be renamed as the RPi Hub header, or something like so. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:27, 11 October 2012 (UTC) 
'''This shall be concluded on Friday, October 12, 2012 at 9:00pm (21:00) Eastern Standard Time, or whenever an obvious consensus closes.'''
:Is this for real?... it goes against the actions of the Raspberry Pi Foundation, see http://www.raspberrypi.org/archives/1715. If they want to spread their Forum into multiple languages, then so should the wiki. [[User:Simon Small|SimonSmall]] 20:31, 11 October 2012 (UTC)
::'''THIS IS NEITHER CONTROLLED BY NOR SANCTIONED BY THE RASPI FOUNDATION'''. Unless YOU want to make all the different language pages, you really need to knock some sense into yourself. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 22:57, 11 October 2012 (UTC)
:Whilst it is my understanding that this section of the eLinux Wiki was created by members of the Raspi Foundation's forum (who, presumably, were already active contributors here), most of the non-english language pages appear to have been created in the early part of 2012 '''before''' the Raspberry Pi was generally available. As the number of active RasPi users grew, it was somewhat inevitable that contributions to this wiki area would increase. Unfortunately this has been at such a pace that, even where there had been significant translation effort in the early stages, at present, there appear to be too few people with the necessary skills to maintain those pages. I certainly don't have them (my French skills learned some 45 years ago are far too "rusty"). From the RPWC's president's comments above, I assume he's in a similar position. Hence, until such time that there are enough RPWC members with sufficient skills and "spare" time to properly check/moderate any translated pages, I agree that it is probably necessary to "shut them down". However, out of respect for the effort put into those early pages, I hope that such a shutdown will not result in complete deletion (where there has been significant effort), just in case their restoration becomes viable. --[[User:TrevorGowen|TrevorGowen]] 17:52, 12 October 2012 (UTC)
::Yes, I will only redirect them. Very well. I guess we have finally reached consensus. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 02:50, 19 October 2012 (UTC)

Well, yes the dictator reach a consensus. FR:RPi-Hub was maintained, I did some change as well as other during the last few months. Now what will happend when french speaking people go the this site. They will see an english only site and move on. Well Done!!

Papillon

If the non-English "hubs" have been shutdown/redirected/whatever, maybe the list at http://elinux.org/RPi_Hub#Translations should be cleaned up too? [[User:AndrewS|AndrewS]] 23:13, 23 October 2012 (UTC)

=== Supplemental guidelines ===
==== This isn't the RPi Forums ====
This will officially tell all that the RPi Forums are not how the RPi Wiki works! Closes whenever consensus is apparently reached. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 23:01, 11 October 2012 (UTC)

==== Official language ====
'''Note: Due to the importance of this topic, all users, regardless of RPWC membership, may discuss this.'''
As amending to the above, English should be the official language of the wiki. We are in Amnet/Engnet/Euronet, not Runet or Chinet, so let's just say ENGLISH really should be the official language. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:37, 11 October 2012 (UTC)
(closes on Friday)

I strongly disagree with that opinion. If you do make all hub page point to english, what is the point of having translation? You are not alone on this planet. A hole bunch of people don't speak (read) english at all.

The point of having translation, is to offer the same information in different languages so as much as possible persons can read thing about the RPi. I know that it is not possible (practically speaking) to have all hub pages having the same exact information but at least the info is there in as much language possible.

If you make english to only language here (even if just for the hub) people will go else where for a wiki and all your good work will be of no use. Just look around http://frenchmagpi.site-mpe.fr/index.php/Accueil, the magpi is being translated to french, issue 5 is already published and issue 6 is in good progress.

In my opinion, "my language is the official one" opinion is selfish and close minded. The goal of a public wiki on the web like this one is to let people share as much as possible their information. Look at the succes of wikipedia, it is available in I don't know many language, there are pages on the same subject in many many languages that don't have all the same information but at least there is information for every one and a lot more people can find information than if just english is available.

It is ok to have the default page point to the english hub but keep the flag and translated hub available to all. Do not trow to garbage the work of all the people who translated (updated) the hub to there own language.

Papillon
:: Thank you for your comments - I've been waiting for further contributions to this discussion since, without proper feedback from the wiki users, this "council" has no mandate for its efforts. Personally, I do not like the term "official language", and feel it would be more appropriate to use the term "primary language". Whilst this wiki has "public access", it appears to be "privately hosted", hence I do not regard it as a "public wiki" like wikipedia. I've already indicated above that I do not wish the existing translation work to be "thrown away", however, some of the "translated hubs" appear to be "skeletal forms" with minimal content. As such they are potentially misleading as to the level and quality of content of this area of work. Should such pages be marked more clearly with their "translation status" (in their "native" language '''and''' English), and with the category "needs editing" (or similar) then I'd be much happier for them to remain linked to.--[[User:TrevorGowen|TrevorGowen]] 08:34, 16 October 2012 (UTC)

Hi, I'm not an English native speaker either - and I agree with the proposal of having English as the primary language ... but also with keeping of the already created translations and the hub - in maybe some form of "unofficial" sub-pages without guarantee that they contain the same/verified/complete information. If they really posses any valuable information rather than being just a fork pointing to English articles, they should be kept available (at least as read-only), otherwise it's rational to clean up. The term "official language" may not be the best choice, "primary language" sounds much better, but in my belief this is not about any selfishness, discrimination or anything else than an effort to keep this wiki well organized, readable, oriented on quality content, brief and clear. Maybe the language-hub can be placed somewhere at the bottom or as a sidebar menu (change to official wiki style?) with a clear marking, that its purpose is to provide extra space for smaller communities of people speaking other languages, and/or as some kind of mirrored clones with basic info from the main pages. Well, if that's what this wiki's objectives are... I understand very well that, this wiki may have a specific orientation and every contributor should respect the rules. Also, one wiki cannot meet everybody's wishes. There are plenty other options for specific language oriented wikis, forums, creating own, etc. On the other hand, if there is someone who would like to take over the role of an editor for a specific language and properly maintain the contents of that pages, I'm sure he will be greatly welcome. One more note - everybody should be aware that this is not a official Raspberry Pi Foundation's wiki. It is a publicly available private wiki (notwithstanding that it is created mostly by public community) for embedded Linux systems in general (correct me if necessary), where RPi is one of such systems/devices. It just happened to be the best available place for this purpose at the time, and thus the Raspberry Pi Foundation simply provided a link to this wiki (instead of creating its own, having to maintain it, moderate, etc.). We should be happy for having this place available for public collaboration. But without proper administration, it may easily become just a mess of unreadable contributions and literally lose its point... Who would want that? ;) --[[User:Pinoccio|Pinoccio]] 14:30, 16 October 2012 (UTC)

==== Wiki Design principles ====

<s>All good things require a good design. To improve this site, we should (re)define / clarify its purpose. The following principles are suggested:

Users of the Raspberry Pi will be of three types (or a mixture of these);
(a) competent Linux user,
(b) experienced hardware and/or software modifier / hobbyist
(c) beginner

Each page should consider WHY a reader would be using that page.

A competent Linux user would only want to know how to get the Raspberry Pi working and set up, and any 'peculiarities' relating to the hardware or Linux distribution. The hobbyist would additionally want to know how to use the GPIO ports and associated software, or how to modify / build the distribution or packages not included in that distribution. There should be clear pointers on the first page for the sections relating to these groups.

The beginner will need careful guidance in their first steps. For this, instructions should be clear:
* they lead the user from what they know into what they don't, with each step being small and simple with the 'objective' clearly defined.
* they use simple steps, and should skip optional complications that are not relevant to the current 'lesson', e.g. half of the raspi-config settings are 'advanced'.
* they should include a link to complete documentation for the topic, with a warning that this may cover advanced material, e.g. full raspi-config instructions.
* the writer should take into account that the site, and users, will be global, with english as a second language.
* the writer should take into account the variations of hardware and distribution installed, e.g. the raspi-config utility is not available in many distributions.
* the instructions should clearly state if they are specific to a particular set up, or are 'date sensitive' to changes.
* pages should be separated into GUI and command line pages and flows.
* instructions should be free from point-of-view opinions.
* instructions should link to 'choice' pages that give pros and cons regarding that choice, e.g. which text editor should be used and if it is available / installable.

The beginner guidance should stop at the point where other sites can take over, e.g. once sufficient Linux has been covered, other Linux sites can provide more advanced or specific information. It should also be aligned to the objectives stated by the Raspberry Pi Foundation for why the Raspberry Pi exists.

Proposal, in absence of anything similar. [[User:Simon Small|SimonSmall]] 16:54, 4 October 2012 (UTC)</s>
:I strongly oppose this. We should NEVER split users into "social classes" and English is our official language, just as English is the Raspberry Pi's preferred language. I think this overhaul is too much right now. Why don't we focus on something else first? Also, you can't make proposals unless you already are a council alderman, in which case, as of my posting time, you currently are not. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:40, 5 October 2012 (UTC)
::As you clearly don't know much about a wiki, I suggest you become more mature when you apply for alderman in the future. I have rejected your request for aldermanship. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:43, 5 October 2012 (UTC)
:::Interesting. Explanation? Quote from above "If anything is wrong with these guidelines please feel free to edit them. Thank you." This raises two questions; (1) What is being done to fix the Wiki? (2) How will (the wiki) encourage new users to contribute, especially the enthusiastic but inexperienced who likely form the target demographic? [[User:Simon Small|SimonSmall]] 21:45, 5 October 2012 (UTC)
::::That means minor changes, not major, overhauling changes. Also, nothing is ''wrong'' with the guidelines! --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 04:30, 7 October 2012 (UTC)

== If you are interested edit here ==
'''Please indicate your interest in joining the council below here, along with a link to your userpage.'''

I have no interest in joining the council myself (just don't have the time), but I think any self-appointed "wiki council" should give itself some validity by spending some time coming up with practical guidelines / recommendations (without being ''too'' restrictive of course) rather than the "petty squabbling" that this page seems to be about so far ;-)
For example maybe you could have a list of pages that you've already "cleaned up", so that we can at least see what "best practices" look like. And maybe you could come up with some guidelines for how pages like [[RPi_Hardware]] and [[RPi_Low-level_peripherals]] should document things which are different for the different revisions of RaspberryPi boards that exist? And Jeff, it might be useful to link to this page from your userpage :) [[User:AndrewS|AndrewS]] 23:31, 23 October 2012 (UTC)

Some more things I've spotted after a quick poke around...
* I see you reverted the change Ryanteck made when adding Rastrack, citing "Self advertising" - IMHO Rastrack is a useful link (it's been featured on the RPi blog) and shouldn't count as self-advertising. When deleting links from the wiki (e.g. if they're on "the wrong page"), maybe you could add them onto "the right page" at the same time? We '''do''' want the wiki to be newbie-friendly, don't we? :)
* In terms of "guidelines", should all pages like e.g. [[Raspcontrol]] be renamed to e.g. "RPi_Raspcontrol" ?
* Surely it'd have been better just to edit the existing [[RPi_Wiki_Best_Practice]] rather than nominating it for deletion (and removing all links to it) ? I'm afraid I'm not a wiki-expert so could you explain how it's "clearly misleading from Wikipedia's policies" and how the policies of Wikipedia are relevant to elinux.org ?
* Is the [[RPi Model Wizard]] a joke? Currently there's only one model available to buy... (and even if there ''were'' two models on sale, the "wizard" seems pretty pointless IMHO)
[[User:AndrewS|AndrewS]] 00:37, 24 October 2012 (UTC)

Hope you don't mind me adding further comments here... 
Something else that it might be nice for the "wiki council" to clean up, is that there are several orphaned RPi-related pages (see [http://elinux.org/index.php?title=Special:LonelyPages&limit=50&offset=100 here]) so I guess it would be nice if either i) links were added back to those pages or ii) the content from those pages is moved/edited to more appropriate/relevant pages or iii) those pages are marked as "redundant info, please delete" or something ?
[[User:AndrewS|AndrewS]] 01:45, 30 October 2012 (UTC)
:Thank you for the info. w.r.t. orphaned pages. I'm still finding my way around here myself, but, being retired, I have more time to deal with such issues than, maybe, Jeff has. (That is, when I'm not trying things out etc. with my raspbery pi boxes). I'll take a look at them as soon as I get the chance. --[[User:TrevorGowen|TrevorGowen]] 14:40, 30 October 2012 (UTC)

I am really bothered by the nonsense at the top of the hub page. The "model wizard" and following pages are quite absurd, and even if they weren't, they don't belong there. Is anybody opposed to removing this content or at least moving it?
[[User:HBrydon|HBrydon]] 22:40 23 Feb 2013 (UTC)
: You have my support, but I suspect "Jeff" will object :-/ I personally think this whole "wiki council" (and it's claim of authority, coupled with lack of action) is absurd too. I added some (personal) comments to [[User_talk:Zootboy]] which in hindsight I should probably have added here. [[User:AndrewS|AndrewS]] ([[User talk:AndrewS|talk]]) 13:00, 24 February 2013 (UTC)
:: This wiki is not governed by anyone other than the community. I do my best to remove spam and keep content as current as possible. Should a [[Project:RPi_Council|Raspberry Pi Wiki Council]] wish to maintain a tightly controlled wiki elsewhere, they're welcome to do so. Should you have any questions, feel free to contact [[User:wmat]]. The wiki has worked well for over 8 years in this manner. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 14:17, 24 February 2013 (UTC)
::: I had begun to suspect that "Jeff"'s claims of a "mandate" for a "Raspberry Pi Wiki Council" were not as "firm" as I had been led to believe - this being my first venture into a wiki community I guess I was somewhat naive. Any comments or contributions made here were intended to be constructive. However most of my contributions, like those of others, are based upon my current investigations and experimentation with raspberry pi hardware etc., and added, hopefully, to appropriate pages. --[[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) 21:32, 24 February 2013 (UTC)

eLinux.org:RPi Council

2013-02-24T21:32:39Z

TrevorGowen: /* If you are interested edit here */

{{Hub Flags}}
{{Clear}}
Because of the messed up stuff on the Raspberry Pi wiki, I have found it necessary to create a governing council for the RPi wiki. Please edit the below section if you'd like to become a member (alderman) of the council.

Note: This is official and is ok with the administration of eLinux.

== Supplemental guidelines ==
''If anything is wrong with these guidelines please feel free to edit them. Thank you.''
=== Guidelines are made from consensus ===
All supplemental guidelines and decisions will now be made by the RPWC and eLinux administration.

== Current council aldermen ==
* President - [[User:Jeff|Jeff]]
* [[User:TrevorGowen|Trevor Gowen]]

== Current issues ==
=== Users ===
==== Mahjongg ====
<s>As he is not answering my requests for identity, he may be impersonating Mahjongg on the forums. I propose the account be blocked indefinitely because it clearly is copying the RPi forum mod's user name.</s> --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:26, 5 October 2012 (UTC)
:Verified thru PM. Case closed. :) --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 21:16, 5 October 2012 (UTC)

==== Ghans ====
I propose that since he ruined a lot of formatting that he is not to edit the Raspberry Pi Wiki's formatting for 1 month. You can see clearly [[RPi Wiki Best Practice|here]]. He, in fact, misguided everyone in best practices! I want you to go to Wikipedia and take a hard stare and compare the articles! They are misleading! He clearly cannot go on with this! Anyone else agree? --[[User:Jeff|Jeff]] 02:15, 2 October 2012 (UTC) '''Edit: and also add a block of 1 month if he does not comply.''' --[[User:Jeff|Jeff]] 22:39, 2 October 2012 (UTC) 
(Note: This decision must be concluded by Wednesday, October 3, 2012.)
:Having compared [[RPi Wiki Best Practice|Ghans' "Best Practice"]] with which, I believe, are the equivalent areas of Wikipedia and parts of the Help sections here I can see what you mean. However, using Wikipedia as a guide, one also has to assume that he was writing with the best of intentions. Unfortunately he does not reveal much about his background, experience etc. on his user page. However, having had the experience of encouraging "best practice" within a mixed group of programmer's of different backgrounds (scientific, computational) and training (formal, informal, none), I am well aware that when considering adopting such from a related area, one also has to consider the needs etc. of the intended users ie. adopt as much as is appropriate, adapt or reject the remainder. An analogy would be that when preparing a presentation one may end up with several versions depending upon the expected audience. Hence, whilst I am prepared to support your proposal, it is on the understanding that this is done so to allow us to begin to formulate more suitable guidelines, given that, eventually, hopefully, there will be younger, enthusiastic but less experienced contributers whom I would not wish to discourage. --[[User:TrevorGowen|TrevorGowen]] 14:40, 2 October 2012 (UTC)
::So you're a support? --[[User:Jeff|Jeff]] 22:32, 2 October 2012 (UTC)
:::Assuming I'm interpreting your update above correctly, to mean that he is requested to refrain from edits that change formatting aspects of the Raspbery Pi sections of the Wiki for one month and ignores that request, yes. Hopefully such a request will generate a response, therebye opening up a dialogue, which may resolve matters such that a formal block need not be imposed. --[[User:TrevorGowen|TrevorGowen]] 12:09, 3 October 2012 (UTC)
I guess I will close this with a warning to Ghans. Block not implemented. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:39, 3 October 2012 (UTC)

=== Content ===
==== Shutdown of most other language "hubs" ====
'''Due to the importance of this topic, ''everyone'' is invited to post their opinions, even users that are not a council member.''' 
These hubs serve no purpose but to point the respective language speakers to English pages. This is utterly useless. If I only spoke Greek, I would be able to understand the hub, but the hub's purpose is to link to other pages. Unfortunately I would ask a Greek community for help because the links are to ENGLISH pages! Why don't we just tell everyone a bold message: THIS IS AN ENGLISH WIKI! I propose to redirect all these pages to the English page; as for the template Hub Flags, I propose it be renamed as the RPi Hub header, or something like so. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:27, 11 October 2012 (UTC) 
'''This shall be concluded on Friday, October 12, 2012 at 9:00pm (21:00) Eastern Standard Time, or whenever an obvious consensus closes.'''
:Is this for real?... it goes against the actions of the Raspberry Pi Foundation, see http://www.raspberrypi.org/archives/1715. If they want to spread their Forum into multiple languages, then so should the wiki. [[User:Simon Small|SimonSmall]] 20:31, 11 October 2012 (UTC)
::'''THIS IS NEITHER CONTROLLED BY NOR SANCTIONED BY THE RASPI FOUNDATION'''. Unless YOU want to make all the different language pages, you really need to knock some sense into yourself. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 22:57, 11 October 2012 (UTC)
:Whilst it is my understanding that this section of the eLinux Wiki was created by members of the Raspi Foundation's forum (who, presumably, were already active contributors here), most of the non-english language pages appear to have been created in the early part of 2012 '''before''' the Raspberry Pi was generally available. As the number of active RasPi users grew, it was somewhat inevitable that contributions to this wiki area would increase. Unfortunately this has been at such a pace that, even where there had been significant translation effort in the early stages, at present, there appear to be too few people with the necessary skills to maintain those pages. I certainly don't have them (my French skills learned some 45 years ago are far too "rusty"). From the RPWC's president's comments above, I assume he's in a similar position. Hence, until such time that there are enough RPWC members with sufficient skills and "spare" time to properly check/moderate any translated pages, I agree that it is probably necessary to "shut them down". However, out of respect for the effort put into those early pages, I hope that such a shutdown will not result in complete deletion (where there has been significant effort), just in case their restoration becomes viable. --[[User:TrevorGowen|TrevorGowen]] 17:52, 12 October 2012 (UTC)
::Yes, I will only redirect them. Very well. I guess we have finally reached consensus. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 02:50, 19 October 2012 (UTC)

Well, yes the dictator reach a consensus. FR:RPi-Hub was maintained, I did some change as well as other during the last few months. Now what will happend when french speaking people go the this site. They will see an english only site and move on. Well Done!!

Papillon

If the non-English "hubs" have been shutdown/redirected/whatever, maybe the list at http://elinux.org/RPi_Hub#Translations should be cleaned up too? [[User:AndrewS|AndrewS]] 23:13, 23 October 2012 (UTC)

=== Supplemental guidelines ===
==== This isn't the RPi Forums ====
This will officially tell all that the RPi Forums are not how the RPi Wiki works! Closes whenever consensus is apparently reached. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 23:01, 11 October 2012 (UTC)

==== Official language ====
'''Note: Due to the importance of this topic, all users, regardless of RPWC membership, may discuss this.'''
As amending to the above, English should be the official language of the wiki. We are in Amnet/Engnet/Euronet, not Runet or Chinet, so let's just say ENGLISH really should be the official language. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:37, 11 October 2012 (UTC)
(closes on Friday)

I strongly disagree with that opinion. If you do make all hub page point to english, what is the point of having translation? You are not alone on this planet. A hole bunch of people don't speak (read) english at all.

The point of having translation, is to offer the same information in different languages so as much as possible persons can read thing about the RPi. I know that it is not possible (practically speaking) to have all hub pages having the same exact information but at least the info is there in as much language possible.

If you make english to only language here (even if just for the hub) people will go else where for a wiki and all your good work will be of no use. Just look around http://frenchmagpi.site-mpe.fr/index.php/Accueil, the magpi is being translated to french, issue 5 is already published and issue 6 is in good progress.

In my opinion, "my language is the official one" opinion is selfish and close minded. The goal of a public wiki on the web like this one is to let people share as much as possible their information. Look at the succes of wikipedia, it is available in I don't know many language, there are pages on the same subject in many many languages that don't have all the same information but at least there is information for every one and a lot more people can find information than if just english is available.

It is ok to have the default page point to the english hub but keep the flag and translated hub available to all. Do not trow to garbage the work of all the people who translated (updated) the hub to there own language.

Papillon
:: Thank you for your comments - I've been waiting for further contributions to this discussion since, without proper feedback from the wiki users, this "council" has no mandate for its efforts. Personally, I do not like the term "official language", and feel it would be more appropriate to use the term "primary language". Whilst this wiki has "public access", it appears to be "privately hosted", hence I do not regard it as a "public wiki" like wikipedia. I've already indicated above that I do not wish the existing translation work to be "thrown away", however, some of the "translated hubs" appear to be "skeletal forms" with minimal content. As such they are potentially misleading as to the level and quality of content of this area of work. Should such pages be marked more clearly with their "translation status" (in their "native" language '''and''' English), and with the category "needs editing" (or similar) then I'd be much happier for them to remain linked to.--[[User:TrevorGowen|TrevorGowen]] 08:34, 16 October 2012 (UTC)

Hi, I'm not an English native speaker either - and I agree with the proposal of having English as the primary language ... but also with keeping of the already created translations and the hub - in maybe some form of "unofficial" sub-pages without guarantee that they contain the same/verified/complete information. If they really posses any valuable information rather than being just a fork pointing to English articles, they should be kept available (at least as read-only), otherwise it's rational to clean up. The term "official language" may not be the best choice, "primary language" sounds much better, but in my belief this is not about any selfishness, discrimination or anything else than an effort to keep this wiki well organized, readable, oriented on quality content, brief and clear. Maybe the language-hub can be placed somewhere at the bottom or as a sidebar menu (change to official wiki style?) with a clear marking, that its purpose is to provide extra space for smaller communities of people speaking other languages, and/or as some kind of mirrored clones with basic info from the main pages. Well, if that's what this wiki's objectives are... I understand very well that, this wiki may have a specific orientation and every contributor should respect the rules. Also, one wiki cannot meet everybody's wishes. There are plenty other options for specific language oriented wikis, forums, creating own, etc. On the other hand, if there is someone who would like to take over the role of an editor for a specific language and properly maintain the contents of that pages, I'm sure he will be greatly welcome. One more note - everybody should be aware that this is not a official Raspberry Pi Foundation's wiki. It is a publicly available private wiki (notwithstanding that it is created mostly by public community) for embedded Linux systems in general (correct me if necessary), where RPi is one of such systems/devices. It just happened to be the best available place for this purpose at the time, and thus the Raspberry Pi Foundation simply provided a link to this wiki (instead of creating its own, having to maintain it, moderate, etc.). We should be happy for having this place available for public collaboration. But without proper administration, it may easily become just a mess of unreadable contributions and literally lose its point... Who would want that? ;) --[[User:Pinoccio|Pinoccio]] 14:30, 16 October 2012 (UTC)

==== Wiki Design principles ====

<s>All good things require a good design. To improve this site, we should (re)define / clarify its purpose. The following principles are suggested:

Users of the Raspberry Pi will be of three types (or a mixture of these);
(a) competent Linux user,
(b) experienced hardware and/or software modifier / hobbyist
(c) beginner

Each page should consider WHY a reader would be using that page.

A competent Linux user would only want to know how to get the Raspberry Pi working and set up, and any 'peculiarities' relating to the hardware or Linux distribution. The hobbyist would additionally want to know how to use the GPIO ports and associated software, or how to modify / build the distribution or packages not included in that distribution. There should be clear pointers on the first page for the sections relating to these groups.

The beginner will need careful guidance in their first steps. For this, instructions should be clear:
* they lead the user from what they know into what they don't, with each step being small and simple with the 'objective' clearly defined.
* they use simple steps, and should skip optional complications that are not relevant to the current 'lesson', e.g. half of the raspi-config settings are 'advanced'.
* they should include a link to complete documentation for the topic, with a warning that this may cover advanced material, e.g. full raspi-config instructions.
* the writer should take into account that the site, and users, will be global, with english as a second language.
* the writer should take into account the variations of hardware and distribution installed, e.g. the raspi-config utility is not available in many distributions.
* the instructions should clearly state if they are specific to a particular set up, or are 'date sensitive' to changes.
* pages should be separated into GUI and command line pages and flows.
* instructions should be free from point-of-view opinions.
* instructions should link to 'choice' pages that give pros and cons regarding that choice, e.g. which text editor should be used and if it is available / installable.

The beginner guidance should stop at the point where other sites can take over, e.g. once sufficient Linux has been covered, other Linux sites can provide more advanced or specific information. It should also be aligned to the objectives stated by the Raspberry Pi Foundation for why the Raspberry Pi exists.

Proposal, in absence of anything similar. [[User:Simon Small|SimonSmall]] 16:54, 4 October 2012 (UTC)</s>
:I strongly oppose this. We should NEVER split users into "social classes" and English is our official language, just as English is the Raspberry Pi's preferred language. I think this overhaul is too much right now. Why don't we focus on something else first? Also, you can't make proposals unless you already are a council alderman, in which case, as of my posting time, you currently are not. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:40, 5 October 2012 (UTC)
::As you clearly don't know much about a wiki, I suggest you become more mature when you apply for alderman in the future. I have rejected your request for aldermanship. --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:43, 5 October 2012 (UTC)
:::Interesting. Explanation? Quote from above "If anything is wrong with these guidelines please feel free to edit them. Thank you." This raises two questions; (1) What is being done to fix the Wiki? (2) How will (the wiki) encourage new users to contribute, especially the enthusiastic but inexperienced who likely form the target demographic? [[User:Simon Small|SimonSmall]] 21:45, 5 October 2012 (UTC)
::::That means minor changes, not major, overhauling changes. Also, nothing is ''wrong'' with the guidelines! --[[User:Jeff|'''Jeff''']] • [[User_talk:Jeff|(talk)]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|RPWC President]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 04:30, 7 October 2012 (UTC)

== If you are interested edit here ==
'''Please indicate your interest in joining the council below here, along with a link to your userpage.'''

I have no interest in joining the council myself (just don't have the time), but I think any self-appointed "wiki council" should give itself some validity by spending some time coming up with practical guidelines / recommendations (without being ''too'' restrictive of course) rather than the "petty squabbling" that this page seems to be about so far ;-)
For example maybe you could have a list of pages that you've already "cleaned up", so that we can at least see what "best practices" look like. And maybe you could come up with some guidelines for how pages like [[RPi_Hardware]] and [[RPi_Low-level_peripherals]] should document things which are different for the different revisions of RaspberryPi boards that exist? And Jeff, it might be useful to link to this page from your userpage :) [[User:AndrewS|AndrewS]] 23:31, 23 October 2012 (UTC)

Some more things I've spotted after a quick poke around...
* I see you reverted the change Ryanteck made when adding Rastrack, citing "Self advertising" - IMHO Rastrack is a useful link (it's been featured on the RPi blog) and shouldn't count as self-advertising. When deleting links from the wiki (e.g. if they're on "the wrong page"), maybe you could add them onto "the right page" at the same time? We '''do''' want the wiki to be newbie-friendly, don't we? :)
* In terms of "guidelines", should all pages like e.g. [[Raspcontrol]] be renamed to e.g. "RPi_Raspcontrol" ?
* Surely it'd have been better just to edit the existing [[RPi_Wiki_Best_Practice]] rather than nominating it for deletion (and removing all links to it) ? I'm afraid I'm not a wiki-expert so could you explain how it's "clearly misleading from Wikipedia's policies" and how the policies of Wikipedia are relevant to elinux.org ?
* Is the [[RPi Model Wizard]] a joke? Currently there's only one model available to buy... (and even if there ''were'' two models on sale, the "wizard" seems pretty pointless IMHO)
[[User:AndrewS|AndrewS]] 00:37, 24 October 2012 (UTC)

Hope you don't mind me adding further comments here... 
Something else that it might be nice for the "wiki council" to clean up, is that there are several orphaned RPi-related pages (see [http://elinux.org/index.php?title=Special:LonelyPages&limit=50&offset=100 here]) so I guess it would be nice if either i) links were added back to those pages or ii) the content from those pages is moved/edited to more appropriate/relevant pages or iii) those pages are marked as "redundant info, please delete" or something ?
[[User:AndrewS|AndrewS]] 01:45, 30 October 2012 (UTC)
:Thank you for the info. w.r.t. orphaned pages. I'm still finding my way around here myself, but, being retired, I have more time to deal with such issues than, maybe, Jeff has. (That is, when I'm not trying things out etc. with my raspbery pi boxes). I'll take a look at them as soon as I get the chance. --[[User:TrevorGowen|TrevorGowen]] 14:40, 30 October 2012 (UTC)

I am really bothered by the nonsense at the top of the hub page. The "model wizard" and following pages are quite absurd, and even if they weren't, they don't belong there. Is anybody opposed to removing this content or at least moving it?
[[User:HBrydon|HBrydon]] 22:40 23 Feb 2013 (UTC)
: You have my support, but I suspect "Jeff" will object :-/ I personally think this whole "wiki council" (and it's claim of authority, coupled with lack of action) is absurd too. I added some (personal) comments to [[User_talk:Zootboy]] which in hindsight I should probably have added here. [[User:AndrewS|AndrewS]] ([[User talk:AndrewS|talk]]) 13:00, 24 February 2013 (UTC)
:: This wiki is not governed by anyone other than the community. I do my best to remove spam and keep content as current as possible. Should a [[Project:RPi_Council|Raspberry Pi Wiki Council]] wish to maintain a tightly controlled wiki elsewhere, they're welcome to do so. Should you have any questions, feel free to contact [[User:wmat]]. The wiki has worked well for over 8 years in this manner. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 14:17, 24 February 2013 (UTC)
::: I had begun to suspect that "Jeff"'s claims of a "mandate" for a "Raspberry Pi Wiki Council" were not as "firm" as I had been led to believe - this being my first venture into a wiki community I guess I was somewhat naive. Any comments or contributions made here were intended to be constructive. However most of my contributions, like those of others, are based upon my current investigations and experimentation with raspberry pi hardware etc., and added, hopefully, to appropriate pages. --[[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) 21:32, 24 February 2013 (UTC)

RPi VerifiedPeripherals

2013-02-17T20:28:11Z

TrevorGowen: /* Working USB Mouse Devices */ Another "re-packaged Trust mouse" added

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

==Power Usage Notes==
{{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 Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75 V), 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.}}

'''Model B Hardware Revisions and USB Power limits'''
'''Hardware Revision 1.0'''
The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximately 100 mA. USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA 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.

'''Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change'''
This had the polyfuses removed, removing the 100 mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012.

==Linux Driver Issues==
Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=12097&start=76] [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5249&start=44]
A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image.

== 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 the Raspberry 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 Raspberry Pi through their interconnect cable, due to the 100 mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).

===Working USB Hubs===
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''USB Version'''
| '''Number of Ports'''
| '''Power Rating*'''
| '''Powers Raspberry Pi'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|4-Port Ultra-Slim Desktop Hub
|F4U040
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|8-Port ExpressBus for iMac
|F5U010
|
|USB 2.0
|8-Port 7x"A" 1x"B"
|
|Verified
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U224
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|TetraHub™ USB 2.0 4-Port Hub
|F5U231
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U234
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|No backfeed, can power the RPi. Comes with a 2.4 A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''“Per Port Current Self-Powered Mode: 500mA (max)”''. However, I've attached a HD that requires 850 mA and it worked fine.

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237
|
|USB 2.0
|7-Port
|5 V - 3.8 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|MyEssentials 7-Port High-Speed USB 2.0 Hub
|F5U259-ME
|
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Lighted Hub
|F5U403
|
|USB 2.0
|4-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Lighted Hub
|F5U700
|
|USB 2.0
|7-Port
|
|Verified
|[http://www.amazon.com/gp/product/B000SDW84K]

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hub 2-en-1
|F5U706ea
|
|USB 2.0
|7-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237v1
|
|USB 2.0
|7-Port
|5 V - 2.5 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U040v
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U039qukAPL
|05e3:0608
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Benq
|
|E2220HD
|
|USB 2.0
|4-Port
|
|Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|BUFFALO
|4 Port Hub
|BSH4aAE06
|05e3:0608
|USB 2.0
|4-Port
|5 V
|Verified
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB

|- valign="top" align="left" style="background: #F5FAFF;"
|Cyberpower
|High-speed Hub
|CP-H720P
|0409:0050
|USB 2.0
|7-Port
|3.6 A
|Verified
|May Contain dual 05e3:0608 instead of 0409:0050

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2001FP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|SP2309W
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2407FWP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|U3011
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub - Card Reader Works - May work with SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|
|B/N61393
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|USB 2.0 External Hub 7 Port
|B/N87467
|
|USB 2.0
|7-Port
|5 V - 3.5 A
|Verified
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.

|- valign="top" align="left" style="background: #F5FAFF;"
|Deltaco
|
|UH-715 Rev 2
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|
|
|0409:0050
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|Dynex USB 2.0 7 Port Hub
|DX-HB7PT
|
|USB 2.0
|7-Port
|5.0 V / 2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|D-Link 7 Port USB Hub
|DUB-H7/B
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7 High Speed USB 2.0 7-Port Hub
|BUBH7A A5
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7
|EUBH7EB H/W Ver:B1
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-4 High Speed USB 2.0 4-Port Hub
|DUB-H4
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi

|- valign="top" align="left" style="background: #F5FAFF;"
|Digicom
|
|
|
|USB 2.0
|4-Port
|5 V - 2.0 A
|Not Verified
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]

|- valign="top" align="left" style="background: #F5FAFF;"
|ednet
|USB 2.0 7 port Hub
|85014
|
|2.0
|7-Port
|
|Not Verified
|Works with keyboard, mouse, audio devices

|- valign="top" align="left" style="background: #F5FAFF;"
|GigaWare
|USB 2.0 4 port Hub
|Model 26-160
|
|2.0
|4-Port
|
|Verified
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.

|- valign="top" align="left" style="background: #F5FAFF;"
|Medi@com
|USB 2.0 4 ports Hub
|M-HX30
|
|2.0
|4-port
|
|Verified
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]

|- valign="top" align="left" style="background: #F5FAFF;"
|mbeat
|13 Port USB Hub
|USB-M13HUB
|
|USB 2.0
|13-port
|5V - 3A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Monoprice
|Aquagate USB Hub
|5328
|
|2.0
|7-port
|2.0 A
|Verified
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]

|- valign="top" align="left" style="background: #F5FAFF;"
|Plugable
|7 Port High Speed USB Hub
|USB2-HUB-AG7
|
|USB 2.0
|7-Port
|5V - 3A
|Verified
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Plugable
|4 Port Hub with Battery Charging 1.1 Support
|USB2-HUB4BC
|
|USB 2.0
|4-Port
|5V - 2.5A
|Verified
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|10 Port USB 2.0 Hub
|USB2-HUB10S
|
|USB 2.0
|10-Port
|5V - 2.5A
|Not Verified
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|4 Port USB 3.0 Hub
|USB2-HUB-81X4
|
|USB 3.0
|4-Port
|5V - 4A
|Not Verified
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.

|- valign="top" align="left" style="background: #FFFDFD;"
|Plugable
|7 Port USB 3.0 Hub
|USB2-HUB7-81X
|
|USB 3.0
|7-Port
|5V - 4A
|Not Verified
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
|Plata 4 port USB 2.0 hub
|18687
|
|2.0
|4-port
|1.0 A
|Not Verified
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Zipp
|USB 7-Port HUB
|N294
|
|USB 2.0
|7-Port
|5V - 2.0A
|Verified
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)

|-
|}

'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.
</div>

*'''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 it is 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 Raspberry Pi, and additionally connect GND and +5 V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.

*'''Digitus'''
** 7-port USB2.0 Powered Hub. Model DA-70226.
*'''Eminent'''
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
* '''GearHead'''
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5 V, 1 A)
*'''Gembird'''
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.
* '''Genesys Logic (sold at Fry's)'''
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware and Belkin, same ID shows up in lsusb)
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)
* '''Hama'''
** Hama 4-way USB 2.0 Hub
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)
*'''HP'''
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)
* '''König Electronic'''
** CMP-USB2HUB55 - 7 port USB2.0 HUB, (ID 1a40:0201 Terminus Technology Inc. Hub) 2.0 A power supply, backpowers Raspberry Pi well.
*'''Laser'''
** "7 port USB hub with AC adapter Version 2.0". 5 V 1 A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry 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, 2 A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!
*'''LogiLink'''
** UA0085 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0090 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0091 USB 3.0 Hub, 4-Port with PSU 5 V, 4 A. Connected with USB2.0 cable. 1 A 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 5 V, 3.5 A (Not suitable for powering Raspberry Pi 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 5 V, 2 A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.
* '''Macally'''
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000 mA wall-wart (US style)
* '''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 1000 mA wall-wart (US style)
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500 mA each) + (4 USB 3.0 Ports @900 mA each) Power Switches on each port, AC Powered and Includes a 5 V 4 A wall-wart (US style)
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5 V 1 A
** NLUSB2-222P 4 port USB 2.0 Hub with 5 V 2 A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])
*'''Nilox'''
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5 V 1.0 A
* '''Plugable'''
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5 V 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port.
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5 V 3 A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)

* '''Pluscom'''
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3 A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.
*'''Satechi'''
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.
*'''Staples (Business Depot) (Bureau EN GROS)'''
** Staples 4-port hub Item 607477-CA
*'''StarTech.com'''
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5 V 2 A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).
*'''SumVision'''
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5 V 1.0 A (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 Raspberry 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 (1 A). Powering Raspberry Pi via microUSB from a hub port.
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]
*'''Sweex'''
** US014 4 Port USB 2.0 Hub
*'''Targus'''
** ACH81xx 7-port powered hub. 5 V 3 A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)
** ACH63EU 4-port. Using a 5 V 2 A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.
*'''The Pi Hut'''
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
*'''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 (5 V 2 A)
*'''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 (5 V 2.5 A) Powering Raspberry Pi from the 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 5 V, 3 A. USB ID 1a40:0201.
*'''VANTEC'''
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5 V 2 A AC/DC adapter. Go 2.0 Mini hub.
*'''Z-TEK'''
** Z-TEK 7-port powered hub with PSU 5 V, 4 A. 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, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5 V pinouts)
** F4U022 7-Port powered USB hub (powered 5 V, 2.6 A), 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. (Works always without powering the Raspberry Pi, haven't tried that)

*'''Dell'''
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.

*'''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.
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.

*'''Dynamode'''
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1 A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification.

*'''D-Link'''
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)

*'''E-Solution'''
** 4-Port 2 A 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 with 1 A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry 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.
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.

*'''Hama'''
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi 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).

*'''iBall'''
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.

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

*'''LogiLink'''
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.

*'''Soniq'''
** 4-Port 5 V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).

*'''Targus'''
** ACH115EU 7-port powered hub. 5 V 3 A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as 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. 1 A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi 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). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2 A 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 there are strange USB failures when X session started. High speed devices such as hard drives had failures.

== USB Remotes ==
* 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.

* [http://www.amazon.com/gp/product/B005DKZTMG/ref=oh_details_o02_s00_i00 Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070)] - keyboard and touchpad work. Have not verified multi-touch features.

* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4 GHz wireless keyboard and touchpad.

* Pan.Code D1000 - 2.4GHz Wireless keyboard and touchpad.

* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.

* [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], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]. Working perfectly, just plug & play.

* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6753651&CatId=3680# Exo Ultra U12-41310 Mini Keyboard] Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work.[https://github.com/thunderbirdtr/rs-pi-exo-keyboard Exo Installer script]

== 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, 20 mA.

* '''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, 100 mA (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''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))
** [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]
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]

* '''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)

* '''Banbridge'''
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)

* '''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)
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5 V/100 mA, works directly

* '''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)

* '''CD Training'''
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]

* '''Cherry'''
** CyMotion Master Linux (B)
** RS 6000 USB ON
** G84-4100PTMUS (B) (Compact keyboard. Rated 100 mA. Works directly in Raspberry Pi)
** G85-23100DE-2 (B) (Rated 40 mA, tested with RPi powered by a 1000 mA power supply unit)
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.

* '''Compaq'''
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5 V 100 mA. Works directly connected to Raspberry Pi

* '''Das Keyboard'''
** Model S Professional Keyboard (Built in USB hub not tested) (B)
** Model S Ultimate Keyboard (Built in USB hub working) (B)

* '''Dell'''
** SK-8115 (B) (Rated 100 mA. Works directly in Raspberry Pi)
** L100 (B)
** RT7D40 (100 mA. Works directly in Raspberry Pi)
** RT7D50 (75 mA) (run "sudo dpkg-reconfigure keyboard-configuration")
** KB1421 (100 mA)
** KB2521 (100 mA)
** KB212-B (Works directly in Raspberry Pi, without powered hub)
** 1HF2Y (Works directly in Raspberry Pi)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Delux'''
** K8050

* '''Digicom'''
** WKEYPE01 Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

* '''Dynex'''
** DX_-WKBD (60 mA) (B)
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)

* '''EAPPLY'''
** EBO-013 Wireless 2.4 GHz compact keyboard with touchpad. Rated <40 mA works directly from Raspberry 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

* '''GE'''
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)

* '''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 >> also see Problem USB Keyboards
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)
** KB1500U (USB Mini Keyboard) (B)
** KB5150 (2.4 GHz wireless keyboard/mouse Combo) (B)
*** Works well with a powered hub

* '''Generic'''
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.

* '''Genius'''
** Ergomedia 700 (GK-04008/C) used without Hub
** KB-06XE (K639) (B)
** LuxeMate i200 (GK-090017; not tested with Hub)
** Slimstar 8000 wireless keyboard

* '''Gigabyte'''
** GK-KM7580 2.4 GHz Wireless Multimedia Keyboard & Mouse

* '''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.4 GHz 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.4 GHz 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 Raspberry Pi. Also works with Raspbmc with powered hub.
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub
** ACK-3700C
** ACK-340U+(DE)
** ACK-3400U (UK) mini keyboard
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi

* '''Labtec'''
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat 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.4 GHz 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.4 GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver

* '''Logitech'''
** Comfort Wave 450, labeled 100 mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine
** 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
** MK120 wired keyboard and mouse
** MK220 wireless keyboard and mouse
** MK250 wireless keyboard and mouse (no hub needed)
** MK260 wireless keyboard and mouse (no hub needed)
** 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]
** MK350 wireless keyboard (using Unifying receiver)
** MK520 wireless keyboard and mouse
** MK550 wireless keyboard and mouse (B)
** MX3200 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.
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]
** K120 Keyboard (B)
** K200 Keyboard (B)
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K350 Wireless Keyboard (B)
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". +1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.
** K520 Keyboard (B)
** K700 Wireless Keyboard with Touchpad and unifying receiver
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).
** 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 Raspberry Pi.
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub 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.
** V470 Bluetooth Laser Mouse

''Keyboards and mice also together with Unifying receiver''

* '''macally'''
**macally iKey slim (IKEY5V2)

* '''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)
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5 V/100 mA (Wheezy 5-Sept-2012)

* '''Mikomi'''
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the 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)

* '''ONN'''
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.

* '''Ortek'''
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.

* '''Perixx'''
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

* '''Prodige'''
**Nanox Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]

* '''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]
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.
**RT-MWK01 mini wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

*'''Rosewill'''
** RK-200 Standard Keyboard

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.
** Expression Keyboard (US)
** Cyborg V.5 (B)

*'''SelecLine'''
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (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)

*'''SolidTek'''
** Solid Tek KB-P3100BU ASK-3100U.

*'''Sony'''
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5 V 1 A 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)

*'''The Pi Hut'''
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.

* '''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.4 GHz 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 Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5 V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry 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.0 V. 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 power away from the rest of the support system devices.

* '''A4 Tech'''
** Model GL-6 USB Keyboard, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''Accuratus'''
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100 mA). Tested with 1000 mA cheap unbranded and Nokia 1200 mA power adaptors.
* '''Apple'''
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub.
*'''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 <200 mA)
* '''Dell'''
** SK-8135 (B) (Rated 1.5 A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)
** SK-8115 causes kernel panic (rated 100 mA) Debian 6-19-04-2012 (B)
** Y-U0003-DEL5 Sticky / Non-responsive keys
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V
* '''Gear Head'''
** KB2300U - Causes kernel panic (B)
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)
* '''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/]
* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Jeway'''
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)
* '''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)
** MK 260 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 receiver - 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)
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000 mA power supply unit)
* '''Novatech'''
** NOV-KEY2 - Causes kernel panic (B)
* '''PC World Essentials'''
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it 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).
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5 V 500 mA. (B)
* '''SIIG'''
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.
* '''Texet'''
** MB-768B standard keyboard (Rated 5 V 1.5 A (!), 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.
* '''Unbranded'''
** Compuparts
** model no. HK-6106 (B)
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.
* '''Verbatim'''
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)
* '''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

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

* '''Apple'''
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).

* '''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)
** MG-0919 (wireless)

* '''Belkin'''
** F8E882-OPT (B)

* '''Cellink'''
** OPM-602 Small wireless optical mouse

* '''Cerulian Technology'''
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA

* '''Dell'''
** M-UVDEL1 (B)
** MOC5UO (100 mA)
** M056U0A (B)
** DZL-MS111-L (B) (100 mA)
** MS-111P (100 mA)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.

* '''Dynex'''
** DX-WMSE (100 mA) (B)

* '''Fellowes'''
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (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.4 GHz 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)

* '''Kensington'''
** Kensington Expert Mouse Trackball K64325
** Kensington Expert Mouse "Slimblade" K72327US

* '''Labtec'''
** Corded Laser Glow Mouse 1600, rated 5 V 100 mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)

* '''Lenovo'''
** Wired Optical Mouse Model: MO28UOL

* '''Logik'''
** Wired Optical Glow Mouse Model: LGGMO10. (B)

* '''Logitech'''
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)
** B105 Mouse for Laptops (OEM)
** 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)
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).
** 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 5 V 100 mA. Works fb on model B with Raspbian Wheezy

* '''Microsoft'''
** Comfort Curve Mouse 3000 for Business
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).
** 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 1000
** 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)

* '''Perixx'''
** PERIMICE-210 U Red (Part No.R1J)

* '''Razer'''
** Boomslang Collectors Edition 2007 (B)

* '''Rosewill'''
** Rosewill RM-C2U

* '''Saitek'''
** Notebook Optical Mouse (PM46)

* '''Samsung'''
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50 mA)

* '''Sun microsystems'''
** Model: FID-638 , SunPN: 371-0788-01

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]

* '''Swiftpoint'''
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.

* '''Targus'''
** AKM02UK (Associated keyboard not checked)
** AMU2701EUK (B)

* '''Technika'''
** TKOPTM2 (B)
**TKD-211
**TKNM110

* '''Tesco'''
** Wired optical mouse M211 (B)

*'''The Pi Hut'''
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Model 15313 - large, 5-button wireless mouse
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.

* '''Verbatiam'''
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)

* '''Xenta'''
** MOW0810 (B)
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Generic'''
** Generic 2.4 GHz 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
* '''A4Tech'''
** Model G7-630 Wireless Mouse, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''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 1000 Hz out of the box, whereas the 518 is only 125 Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot

* '''Microsoft'''
** Microsoft Touch Mouse - Does not see right clicks, Only left.
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.

* '''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.
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus

* '''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 Real Time Clocks ==
*Cymbet
** Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)
Device information at http://www.cymbet.com/pdfs/DS-72-22.pdf
Code to access the RTC from Linux: https://github.com/owendelong/Cymbet-RTC
Does not require a powered hub.

== USB Wi-Fi 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 Wi-Fi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but it has not yet been tried.

'''Note:''' A Wi-Fi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the Wi-Fi adapter to the Wi-Fi Access Point. Therefore, you may need to plug the Wi-Fi 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 Raspberry Pi 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."
** It works without additional software connected directly to a Rev 2 Raspberry Pi, but it stops working after a period of time (3 to 4 hours) with a fully updated Wheezy and all the 'USB workarounds' [http://elinux.org/Rpi_USB_check-list] in place.

* '''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). Tested on Raspbian too (drivers from aircrack-ng).
** AWUS036H (500 mW version): Tested on Raspbian (drivers from aircrack-ng).
** AWUS036H (1 W version): Tested on Raspbian (drivers from aircrack-ng). Needs USB powered HUB or Rev2 of the board / polyfuse bypass.
** AWUS036NHA: Tested on Raspbian (drivers from aircrack-ng). Works fine if connected after boot, otherwise Raspberry Pi won't boot up.

* '''AirLink101''' [[File:Airlink101.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-airlink101|100px|Airlink 101 Wireless N 150 Ultra Mini-USB Adapter]]
** 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.
** AWLL5099: Tested on Raspian Wheezy. [http://www.savagehomeautomation.com/raspi-airlink101 Step-by-step installation and configuration instructions] with screenshots can be found [http://www.savagehomeautomation.com/raspi-airlink101 here]. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** [http://www.airlink101.com/products/awll6075.php AWLL6075]: Tested on Raspian Wheezy 16-Dec-2012 build and distro upgrade as of 09-Jan-2013. lsusb reports: 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter. Driver installed is r8712u. Powers OK from Model B Pi (Rev 000f) USB port (1200mA supply tested). Dongle does get hot under use when directly connected to USB port (slightly reduced when USB extender cable used).

* '''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 repository (B) (not needed with latest Raspbian “Wheezy” 2012-07-15: this Asus works N10 out of the box) Does not support nl80211 APIS, so hostapd won't work.
** [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 it will not function.
** WL-167G v3 USB ID 0b05:1791, working out-of-the-box on Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17. Does not require powered hub.

* '''AusPi Technologies'''
** AusPi Wireless Adapter [Realtek RTL8188S]. Works without a powered HUB. Tested on OpenELEC (works OOB), RaspBMC (works OOB), XBian (works OOB) and 2012-08-08 Raspbian Wheezy (works OOB). Distributed in Australia by [http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/ Buy Raspberry Pi Australia].

* '''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 '''Powered hub required!'''
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Works on RaspBMC OOB (with NetworkManager plugin). Works WITHOUT powered hub on 5 V 800 mA power with 6 overvolt (nothing else connected to USB)
** 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 repository (B). Verified working with 2012-12-16-wheezy-raspbian right out of the box.
**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. Tested and working on Rasbian Wheezy (and RaspBMC), driver RTL8192CU, no powered hub needed (dongle directly attached to the onboard ports)
** Belkin Components F9L1001v1 "N150" Wireless USB Adapter. Tested and working on Rasbian Wheezy WITHOUT powered hub.
** Belkin Surf Micro WLAN USB-Adapter (Raspbian Wheezy, unpowered hub, "N150")

* '''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
** USB ID: WLI-UC-G300N - Works on Raspbmc out of the box. Tested after a factory reset of the Raspbmc.

* '''Comfast'''
** WU710N: chipset RTL8188CUS. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** WU810N (150M): Works out of the box on wheezy raspbian of version 2012-12-16.

* '''Conceptronic'''
** C300RU. Works out of the box in Raspbian. Causes reboot when plugging on a live Rev. 2 Raspberry Pi

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

* '''DealExtreme'''
** ISG-1507N Mini USB 2.4GHz 150Mbps 802.11b/g/n WiFi. Has the ralink 5370 chipset, works directly plugged into the Raspberry Pi rev.1 under OpenELEC. Note: Driver (rt2800usb) only permits B/G operation and throughput is low (10Mbit).

* '''DELL'''
** Wireless 1450 [Intersil ISL3887]. Works out of the box, but it requires a powered hub (the Raspberry Pi boots with this dongle plugged in, recognizes and configures it, works for some time, but then it crashes randomly under heavy traffic. A powered hub seems to fix the issue).

* '''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-121 (Version A1). Wireless N 150 Pico. Works out-of-the-box with Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)
** DWA-123 (Version A1). USB ID 2001:3c17, Ralink RT2800. Working out-of-the-box on Arch image from 2012-04-29. (working without UBS Hub - not yet sure if it achieves full speed though.)
** 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]
** WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.

* '''Edimax''' [[File:Edimax-ew-7811un.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-edimax-ew-7811un|100px|Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter]]
** [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]. Note: With current Raspbian (2012-09-18-Wheezy) it is recognized immediately, the default module works fine; the configuration is easy using wireless-essid and wireless-key in /etc/network/interfaces.
*** The EW-7811Un can be powered directly from the Raspberry Pi if the Raspberry Pi is powered using a well regulated power supply.
*** EW-7811Un [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un step-by-step installation and configuration instructions] for Debian & Raspian with screenshots can be found here: [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un here]
*** 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 Raspberry Pi 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]]
*** EW-7811Un[USB ID 7392:7811](Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Worked right out of the box - only needed to configure WPA.
(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.
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=261&pl1_id=1&pl2_id=44 EW-7711UAn], Ralink RT2870, works perfectly on Arch with a powered hub (not tested without yet). Simply required wireless_tools and wpa_supplicant, the drivers/firmware are included in kernel 3.0. I followed the Arch [https://wiki.archlinux.org/index.php/Wireless_Setup Wireless Setup] instructions.

* '''edup'''
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS Wi-Fi 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://dx.com/p/ultra-mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network-adapter-48166?item=1&Utm_rid=24958662&Utm_source=affiliate Ultra-Mini Nano USB 2.0 802.11n 150 Mbit/s Wi-Fi/WLAN Wireless Network Adapter] USB ID: ID 0bda:8176 Works stable when using VLC for internet radio receiver. Works stable 24/7 on two of my Raspberries used as webserver. Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian. Seems to be the same as EW-7811Un using the RTL8188CUS chipset.

** [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 Raspberry Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or received the audio get distorted. Use script from [http://dl.dropbox.com/u/80256631/install-wheezy-beta-rtl8188cus-20120619.sh here] for Wheezy.

* '''Eminent'''
** EM4575 - rt2800usb driver.

* '''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 repository. No need to download firmware when using Debian Wheezy (B)

* '''ISY'''
** USB Wireless Micro Adapter IWL 2000, tested on Raspbian; follow [http://daniel-lnx.blogspot.nl/2013/01/raspberry-pi-and-isy-usb-wireless-micro.html these] instructions.

* '''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 it 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]
** Linksys WUSB54GC (manufactured 07/2008) No issues! needs powered hub on version 1.0 boards.
** Linksys WUSB54G ver.4, Works well even when plugged directly to the Raspberry Pi. Requires 300mA max, hence recommended to use powered usb hub for extended operation.

* '''LogiLink'''
** Wireless LAN USB 2.0 Nano Adapter 802.11n LogiLink [http://www.logilink.eu/showproduct/WL0084B.htm] is working even USB powered.

* '''Lutec'''
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.

* '''Micronet'''
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into Raspberry 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 Wi-Fi 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>

* '''Mvix'''
** Mvix Nubbin (MS-811N): works out of the box on Raspbian "Wheezy" and does not need a powered USB hub.

* '''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. Seems to draw a lot of power; e.g. I can't power this and a USB thumb drive simultaneously.
** WG111v3: Realtek RTL8187B chipset. Works straight out of the box using a powered USB hub.
** WNA1000M works with Raspberry Pi Model B Board v. BS1233. However, when downloading torrents and when they pick up speed, the system becomes unresponsive.

* '''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 Wi-Fi 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.
** RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.
** [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). An image of an adapter with this chip can be found [http://i.imgur.com/wRF7L.jpg here].

* '''Rosewill'''
** RNX-N180UBE Wireless B/G/N Adapter
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172
*** Tested in Arch, works out of box. Powered USB hub required.
*** Tested in Raspbian, used wicd to configure network settings. Powered USB hub Required.
*** Tested in Raspbmc. Needs package firmware - Realtek and used wicd-curses to configure. Powered 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.
** RNX-MiniN1 (RWLD-110001) Wireless-N 2.0 Dongle (Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter)
*** Tested in Raspbian, powered from USB hub.

* '''Sabrent'''
** USB-A11N: Mini USB 2.0 Wireless-N WiFi Network Adapter: USB ID 0bda:8176, works automatically in Raspbian using rtl8192cu driver along with Logitech BT mini-receiver (keyboard/mousepad) without external hub using 5.25V 1 A psu (4.99V T1/T2) on rev 2.0 (B)

* '''Sagem'''
** Sagem Wireless USB stick XG-760N: USB ID 079b:0062, Module is not shipped in Debian image, but it 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/

* '''Sitecom'''
** Sitecom Wi-Fi USB Adapter N300: USB ID 0a5c:5800, Realtek r8712u driver + firmware Realtek. Module available in shipped Raspbian image. '''NOTE:''' although this dongle will also work without powered hub, if there is a voltage problem (either on the Raspberry or on the hub, but verified only on the hub so far) this wifi dongle will receive signal perfectly (RX), but not be capable of sending anything (TX) and the MAC address will be permanently set to FF:FF:FF:FF:FF:FF (this is indicative that there is not enough power) [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]

* '''SL'''
** SL-1507N: USB 802.11n 150M Wi-Fi Wireless LAN Network Card Adapter SL-1507N Black
*** I bought this on on eBay for $4.19 (free shipping) @ http://www.ebay.com/itm/270853614804?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649#ht_4379wt_1199
*** It worked out of the box on Raspbmc RC4, with the network manager add-on; seems to be an rt2800usb
*** dmesg output "usbcore: registered new interface driver rt2800usb"

* '''SMC'''
** SMCWUSBS-N: Hardware detected as rt2800, but it is 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.

* '''Sony'''
** Sony UWA-BR100 802.11abgn Wireless Adapter [Atheros AR7010+AR9280] (Vendor ID: 0411, Product ID: 017f) - Tested with Raspbian. Needs package firmware-atheros.(B)

* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
** Tenda W311M Wireless N150 Nano USB Adapter ([http://www.tenda.cn/tendacn/Product/show.aspx?productid=375 product page]) - Works out-of-the-box with Raspbian as of 2012-12. Tested in WPA-Personal network. Runs without Powered Hub when plugged into Raspberry Pi.
** Tenda W311MI Wireless N Pico USB Adapter (identified as Ralink RT5370 Wireless Adapter; USB-ID: 148f:5370) - Works out-of-the-box for Raspian 2012/09/18 or later. An earlier version gave me problems.
** 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]
** Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.

*'''The Pi Hut'''
** USB 802.11n Wi-Fi adapter (from [http://thepihut.com/products/usb-wifi-adapter-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''TP-Link'''
** TL-WN321G (Ralink RT2501/RT2573, rt73_usb) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v? (Atheros AR9271, ath9k_htc) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v2 (ath9k_htc) Works OOTB in Debian Wheezy Beta. Runs without powered Hub when plugged into running Raspberry Pi, but the Raspberry Pi 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) | works OOTB with Wheezy Raspbian (2012-08-16) connected directly to raspberry pi (B) and AP functionality tested with hostapd.
** 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-WN723N (RTL8188SU); works OOTB with Raspbian 2012-09-17, (B) stable with 1 A PSU and without powered USB hub on r2.0. (a model B Pi with Arch Linux reboots if the dongle is plugged, restart sees the device without problems afterwards)
** TL-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.
** TL-WN821N v3 (ath9k_htc, htc_7010.fw); works out of the box on ArchLinuxARM, Wheezy and on OpenElec (>r11211), Problems with prior OpenElec; needs powered USB Hub (B). This chipset is also compatible with hostapd (wireless AP software)
** TL-WN822N v2 (ath9k_htc) works on ArchLinuxARM, with powered USB Hub. Successfully tested hostapd/dnsmasq.
** TL-WN823N Works out of box on Raspian using powered USB Hub

* '''Trendnet'''
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-648UBM TEW-648UBM] USB ID: 20f4:648b, works OOTB with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/ Adafruit Occidentials Raspbian Wheezy variant] as it includes kernel with [http://www.wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model%3A%3ARTL8188CUS%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols%0D%0A%3FMIMO+status%0D%0A%3FOUI%0D%0A&sort_num=&order_num=ASC&eq=yes&p%5Bformat%5D=broadtable&p%5Blimit%5D=500&p%5Bsort%5D=&p%5Boffset%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Blink%5D=all&p%5Bsearchlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&eq=yes RTL8188CUS driver built-in] (B)
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-649UB TEW-649UB] Works with OpenElec 3.0, chipset Realtek RTL8191SU

* '''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)
** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package

===Problem USB Wi-Fi 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.

* '''Alfa'''
** AWUS036NHA (Vendor ID: 0cf3, Product ID: 9271) - Tested with Raspbian. Works fine if connected after boot. Kills boot process if previously attached. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=16809&p=169469#p169469 Details here.]

* '''EDIMAX'''
** EW-7811Un (Vendor ID: 7397, Product ID: 7811) - Reports as containing the Realtek RTL8188CUS chipset listed below, no lockup or kernel oops under Wheezy, but dmesg reports constant timeouts trying to initialize the module. This appears to be resolved on 2012-09-18-Wheezy-raspbian and newer versions.

* '''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.
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].

== USB Bluetooth adapters ==
===Working Bluetooth adapters===
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.
* 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 Adapter 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
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
** http://www.element14.com/community/message/58288
* IOGear GBU321 (Broadcom BCM2045 Chipset)
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
* Trust BT-2400p
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).

===Working Bluetooth/Wifi Combo adapters===
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>

===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. Raspberry 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.
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.
* Asus USB-BT211
** Shows up as HCI device in Raspbian, but it does not scan or pair.
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962

== USB Ethernet adapters ==
===Working Ethernet adapters===
* '''AVM'''
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.
* '''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.
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
* '''Apple'''
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.
* '''Edimax'''
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.
* '''D-Link'''
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)
* '''Sabrent'''
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)
* '''Sitecom'''
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.
* '''A-Link'''
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.

The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190 mA, so there might be stability issues if additional power is not provided.
* '''Hama'''
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.
* '''Newlink'''
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.

===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. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out

== 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> . If you are not user ''pi'' you may need to add your username to the ''audio'' group thus: <code>sudo adduser yourusername audio</code> (user ''pi'' usually belongs to this group anyway).

* '''Creative'''
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]
* '''Daffodil'''
** [http://www.amazon.co.uk/gp/product/B002FI7GWK/ref=oh_details_o03_s00_i00 USB Sound Adapter US01]. Tested with low-cost headphone/microphone set via ''audacity'' (See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/DaffodilUSBSoundAdapter.html CPM-Spectre-Pi...DaffodilUSBSoundAdapter]).
* '''Edirol'''
** [http://www.roland.com/products/en/UA-1A/ UA-1A]
* '''Hercules'''
** [http://www.hercules.com/fr/Cartes-Son/bdd/p/123/gamesurround-muse-xl-pocket-lt3/ Gamesurround Muse XL (Pocket LT3)]
* '''Logilink'''
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]
* '''Logitech'''
** [http://www.amazon.com/Logitech-Wireless-Gaming-Headset-Surround/dp/B003VANOFY/ref=sr_1_1?ie=UTF8&qid=1358114107&sr=8-1&keywords=g930 Logitech G930 Wireless Gaming Headset with 7.1 Surround Sound] (stereo works with ALSA, have not tried 7.1 Surround Sound)
* '''NuForce uDAC-2'''
** [http://www.nuforce.com/hp/products/iconudac2/index.php NuForce uDAC-2 Headphone Amplifier and USB DAC]
* '''Plantronics'''
** [http://www.ebay.com/itm/Genuine-New-Plantronics-External-USB-Audio-Soundcard-New-Sealed-/300845395889?pt=US_Sound_Card_External&hash=item460bc86fb1 Plantronics Stereo USB Adapter -01] (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter)
* '''Terratec'''
** [http://www.terratec.net/fr/produkte/Aureon_Dual_USB_12339.html Aureon Dual USB] (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers)
* '''Texas Instruments PCM2704'''
** [http://www.ti.com/product/pcm2704 PCM2704 98 dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]

==USB 3G Dongles==
* Huawei E1750
* Huawei E173
* Huawei E220
* Huawei E160 (AT commands only)
* 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 Raspberry 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].
*Sundtek
**Sundtek MediaTV Digital Home
**Sundtek MediaTV Pro
**Sundtek SkyTV Ultimate
**[http://shop.sundtek.de DVB-C, DVB-T, DVB-S/S2]: digital TV works, streaming to Windows / Linux is no problem. Easy installation [http://support.sundtek.com/index.php/topic,4.0.html English]
*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.
** Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer)
** Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian)
*K-World
** K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick. IR and supplied remote work with XBMC.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Raspberry Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Raspberry Pi itself. Tested with Astra 19.2E radio and SD-TV channels
*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 was detected, but it is not tested.
** [http://obrazki.elektroda.pl/8081115000_1317678968.jpg HDTV USB DVB-T] dongle, based on IT9135. This tuner comes in two revisions. Revision is printed on PCB.
*** rev. 1.0; should work with 3.2+ kernel, need confirmation.
*** rev. 2.0; works with kernel 3.6.11, without a powered hub. This tuner also requires a firmware (dvb-usb-it9135-02.fw) which can be downloaded from [http://logout.hu/bejegyzes/azbest/usb_dvb-t_tuner_it9135_rev2/hsz_1-50.html this page]. It's in Hungarian, so google translate or equivalent is recommended. The remote also works. According to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=29141 this post], there may be issues on some software configurations when using ''omxplayer''.

== USB Webcams ==

This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!

<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''Verified OS'''
| '''Verified OS version'''
| '''Verified Resolution'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F6D2CF;"
|Canyon
|
|CNR-WCAM820
|
| raspbian/wheezy
|
| 1280x1024
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK

|- valign="top" align="left" style="background: #F5FAFF;"
|CBR
|
| CW 835M Black
|
| raspbian/wheezy
| 2013-02-12
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Live!
| VF0470
|
| ArchLinux
|
|
| works out of the box on ArchLinux

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Socialize HD
| VF0610
|041e:4080
| raspbian/wheezy
| 2012-11-26
| 960x544
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Vista IM
| VF0640
|
| raspbian/wheezy
|
|
| works on Raspbian at 320x240 resolution, 15fps

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Webcam Notebook
| PD1170
|
|
|
|
| Detects, untested.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Webcam Pro
| PD1030
|
|
|
|
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")

|- valign="top" align="left" style="background: #F5FAFF;"
|HP
|WebcamHD-2200
| HD-2200
|
|
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|HP
|Webcam HP-3100
|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

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C100
| V-U0013
|
| raspbian/wheezy
| 2012-08-16
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C200
|
| 046d:0802
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C210
|
| 046d:0819
| Raspbian/wheezy
| 2012-12-16
| 320x240, 640x480
| Works fine without external power.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C270
|
|
|
|
|
| With external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C310
|
|
|
|
|
| Does not require a powered hub to capture snapshots

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C510
|
|
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C525
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C615
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C905
|
|046d:080a
|occidentalis
|v0.2
|1600x1200
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C910
|
|
|
|
|
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C920
|
|
| raspbian/wheezy
|
|
| With powered hub, detected out of box as Video0 V4L device

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Orbit/Sphere
|
|
|
|
|
| Works with external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro 9000
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro for Notebooks
|960-000047
|046d:0991
|Raspbian Wheezy
|2012-12-16
|160x120 320x240 640x480
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Ultra Vision
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 4000
|
|
|
|
|
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 9000
|
| 046d:0809
| Arch Linux
|
|
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).

|- valign="top" align="left" style="background: #F5FAFF;"
|Medion
|
| MD86511
|
| raspbian/wheezy
| 2012-07-15
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Mexxcom
|
| M-104
|
| raspbian/wheezy
| 2012-12-16
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam Cinemap 720p USB HD Webcam
| H5D-00001
|
| raspbian/wheezy
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
| Microsoft
| LiveCam HD-3000
| HD-3000
| 045e:0779
| Archlinux
| 2013-02-06
| 160x120
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam HD-5000
|
|
|
|
|
| Picture breaks up at the bottom

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam HD-6000
|
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| VX-7000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-3000
|
| raspbian/wheezy
|
|
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-500
|
| raspbian/wheezy
|
|
| Up to 352x288. Higher resolutions do not work.

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-800
|
| raspbian/wheezy
|
| 352x288
| Doesn't work at full resolution

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam Studio/Cinema
|
|
|
|
|
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|Xbox Live Vision
|
| 045e:0294
| Arch Linux
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|MSI
|MSI StarCam 370i
|370i (snake)
|
| Raspbian Wheezy
|
| 352 x 288
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.

|- valign="top" align="left" style="background: #A4B2CF;"
|Philips
| Webcam
| SPC 900NC
| 0471:0329
| Raspbian Wheezy
| 2012-12-16
| 160x120
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg

|- valign="top" align="left" style="background: #F6D2CF;"
|Silicon Motion
| SM731 Camera
|
| 090c:71b3
| Raspbian Wheezy
|
|
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS3
|
|
|
|
|
| The occasional frame is corrupted/stutters when running at 640x480

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
|
|
|
|
|
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
| SLEH 00030
|
| Arch Linux
|
|
| (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 Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012

|- valign="top" align="left" style="background: #F6D2CF;"
|T'nB
| Minipix 100K pixels
| IMWB032992
| 1e4e:0100
| raspbian/wheezy
| 2012-12-16
|
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
| 2 MP Auto Focus Webcam
|
|
| Arch Linux
|
|
| works out of the box

|- valign="top" align="left" style="background: #F6D2CF;"
|Trust
| SPACEC@M 200
|
|
| Arch Linux
|
|
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012

|-
|}

== USB GPS devices ==

*Columbus
** Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients)
*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: It works, but it may draw too 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 Raspberry Pi. 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 and USB to Serial (RS-232) adapters ==
A 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.

===Working USB to Serial Adapters===
*'''FTDI'''
**FT232 chip based adapters works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio.

** FT2232D dual RS232/FIFO works (used in various JTAG devices)

*'''Prolific'''
**PL2303 chip based adaptors works fine on latest Debian tested with ''minicom'' and ''gtkterm''

A USB to Serial (RS-232) adapter is used the other way around, ie. the USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment.

*"Best Connectivity" (Possibly also sold under the "Newlink HQ" or "Kenable HQ" labels)
**FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by ''lsusb'' as <code>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</code>. Appears as <code>/dev/ttyUSB0</code>, and requires the user to be a member of the ''dialout'' group (which ''pi'' is for ''Raspbian Wheezy''). Initially tested using an old RS Datalinker setup in "loopback" mode via ''microcom'' upto 9600 baud, and ''gtkterm'' after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently ''gtkterm'' was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

===Problem USB to Serial Adapters===
'''HL-340'''
*CH340 Chipset - '''Currently not supported by RPi''' but there is a patch of kernel code [http://tiagovaz.wordpress.com/2008/01/04/using-a-hl-340-usb-serial-adapter-against-2623-linux-kernel/ here], but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work.

== Other, exotic USB devices ==
=== USB to Parallel Port/Printer Adapters ===
*'''Prolific'''
**PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under [[RPi_Distributions#RISC_OS| RISC OS Raspberry Pi]] with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBtoParPrntAdapter.html CPM-Spectre-Pi...USBtoParPrntAdapter] for more info. and also a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/WheezyCUPS.html CUPS/Wheezy installation guide])

=== USB to SATA ===
*'''Nippon Labs'''
** 2.5" SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi. Built-in "Y" power adapter. Does work direct on some ver2.0 boards if used with 5.25 power supply, or Y adapter

=== 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 5 V at 0.5 A 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 it is 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 Raspberry Pi.
**Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168
=== USB RFID Reader ===
*Unbranded 125 kHz EM4100 RFID reader from eBay sellers (< £7), the one with a Windows logo on (easily scratches off for Linux users).
**Initially would not work when plugged in directly to Raspberry Pi. Worked when connected via an unpowered Trust hub. Worked after Raspberry Pi was modified with 10K resistors over the USB polyfuses (warranty invalidated). Probably would work fine with powered hub.
**Sends a 10 digit string to current window or console as if it was a keyboard. Can be captured independently of keyboard using Linux event interface (/dev/input), but the kernel in current distributions does not have CONFIG_INPUT_EVDEV selected so kernel rebuild is necessary.
=== JTAG ===
* FTDI2232D dual RS232/FIFO based JTAG (e.g. SheevaPlug JTAGKey USB-ID 9e88:9e8f)
** works using the Raspberry Pi as a development host
=== USB 3.0 Multi-Card Reader ===
* US Robotics All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously
** SD/MMC + MS/MS PRO or DUO/DUO PRO + CF/MD + SM + SD/MMC or MS/MS PRO. Useful for backing up cards containing other OS Distros
=== Tinkerforge Bricks and Bricklets (http://www.tinkerforge.com) ===
* Read out sensors and control motors over USB with open source hardware.
* Tested with the brickd_armhf.deb from [[http://www.tinkerforge.com/doc/Downloads.html#tools: here]] with:
** sudo apt-get install libusb-1.0-0 libudev0
** wget http://download.tinkerforge.com/tools/brickd/linux/brickd_linux_latest_armhf.deb
** sudo dpkg -i brickd_linux_latest_armhf.deb
* Tested languages: C/C++, C# (mono), Free Pascal (Lazerus), Java, PHP, Python, Ruby (see [[http://www.tinkerforge.com/doc/Software/API_Bindings.html: here]] for installation).
* If a big amount of Bricks is used, a powered USB Hub may be required.

== 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 keyboards'''

All above tested with the famous "blue cube" on a powered USB hub.

*IBM Model F (please note requires an additional AT to PS2 converter)
*Dell AT101w
*Northgate Ominikey Ultra T (please note requires an additional 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 it 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 5 V. 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===
* '''Adafruit'''
** 5.25 V 1 A Model 501 (Newark 44W4932) USB 110-240 VAC power supply [4.99-5.01 V @ T1/T2 with 100 mA BT and/or mini wireless-n on RPi USB ports]
* '''AlcaPower'''
** 5 V 2.5 A Model AP5A - Charger/switching with 7 connectors(also Microusb)
* '''Ansmann'''
*** Dual USB charger slim, Model-Nr. 1201-0001
* '''Apple'''
Note that apple designs its charger products to work optimally as '''chargers''', in practice this means that apple chargers drop their output voltages somewhat with output current, so that the charging circuits do not need to dissipate more heat than is strictly necessary. Because of this, and although many people have reported apple products to power their basic PI setup reliably, its still not an optimal choice for a PI system that uses power hungry USB devices. Also, because of the popularity and high price of these chargers there are many very sub standard, but almost impossible to recognize as fake copies on the market, and some of these fakes are about the worst things you can try to power your PI with! Not only do they not work, they may actually be dangerous to use!
** 5 V 2.1 A USB charger for iPad2, model A1357
** 5 V 1.0 A USB Charger for iPod
** 5 V 1.0 A USB Charger for iPhone 4
* '''Amazon'''
** 5 V 0.85 A USB charger for Kindle
** 5 V 2 A Mains to USB A adaptor, Branded "CostMad"
* '''Asus'''
** 5 V 2.0 A USB charger for Google Nexus 7
* '''Bandridge'''
** 5 V 1.0 A Mobile Phone Charger (Model: BPC3102EC)
* '''Belkin'''
** 5 V 2.6 A 4 port Ultra-Slim Desktop hub (Model F4U040) (Raspberry Pi running from USB hub port)
** 5 V 2.5 A 4 port USB Hub (Model F5U404) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB 2.0 Mobile Powered Hub (Model F4U018) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB Hub (Model F5U706) (Raspberry Pi running from USB hub port)
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)
** Universal USB Wall Charger (5 V 1 A) (Model F8Z222uk)
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** Charger for Tour 9630
** 5 V 0.7 A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
** 5 V 750 mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)
** 5 V 750 mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)
** 5 V 2 A Model PSAC10R-050QT, RIM Part Number HDW-34725-001
** 5 V 550 mA curve 8520 charger works with raspberry pi Model B Board v. BS1233. It does not work with Raspbmc image.Symtoms are frequent key board and external hdd disconnects.
* '''Deal Extreme'''
** [http://dx.com/p/5v-2a-regulated-switching-power-supply-110-220v-94518 S-10-5 5 V 2 A Regulated Switching Power Supply (110~220 V)] (DIY: requires additional micro-USB connector and wiring)
* '''Dell'''
** USB Hub integrated in Dell monitors (B)
* '''The FX Factory'''
** 5 V 1 A (1.2 A max) AC Travel Charger Model KJ-USB Mains. Typically provides 4.9 V at 1 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>
* '''Garmin'''
** 5 V 1 A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6 ft cable (F3U151B06) works.
* '''Gembird'''
** 5 V 2 A Universal USB Charger (Model: MP3A-UC-AC5). Test: 1080p TV (1xHDMI), USB Wi-fi adapter (1xUSB), wireless keyboard and mouse (1xUSB). Results: ~5.3V, works without any problems (own usb cable required).
* '''Globe Electric'''
** 2-Outlet Tap with Surge Protection and 2 USB Chargers ([http://globe-electric.com/product/2-outlet-tap-with-surge-protection-and-2-usb-chargers-grounded-white/ 46082]). Rated at 1000 mA. 120 V systems only.
* '''Griffin'''
** Power Block Model P2417. 5 V 2.1 A
** Power Block Model P1190R2 Two USB 5 V Outputs, 1 A each
* '''Hama'''
** 1000 mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)
* '''Hartig + Heiling GmbH & Co. KG'''
** H+H SN 6 USB
* '''HP'''
** 5.3 V 2 A Charger for HP Touchpad (B)
* '''HTC'''
** 5 V 1 A TCP-300 USB phone charger (B)
** 5 V 1 A TC B250 USB charger (HTC R/N: 79H00096-00M)
** 5 V 1 A TC E250 USB charger (HTC R/N: 79H00098-02M)
* '''i-box (Philex Electronic Ltd)'''
** 5 V 1 A 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'''
**15 W Dual USB Adapter. Model: mMini AC15. Output: 5 V, 3 A (max per port), 15 W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Specification sheet]
* '''Kodak'''
** 5 V 1 A TESA5G1-0501200
** 5 V 1.0 A K20-AM
* '''König'''
** 5 V 1 A PSUP-GSM01
* '''LG'''
** 4.8 V 1 A Travel Adapter
** 5.1 V 0.7 A Travel Adapter (Model: STA-U34WVI)
** 5.1 V 0.7 A Travel Adapter (Model: STA-U12ER)
* '''Logic'''
** 4 port USB Hub (Model LP4HUB10). (Raspberry Pi running from USB Hub port, red power line (+5 V) inside hub cut) (B)
*'''LogiLink'''
**5 V 2.1 A Switching power supply, model PA0040 (B)
* '''Logitech'''
** 5 V 1 A SDC115-USB Remote Control Charger and cable
* '''Maplin Electronics'''
** 5 V 1 A dual USB power supply, model number H25B-MT-K2
** Micro USB Power Supply N19HX
* '''Medion'''
** 5 V 1 A USB power supply for OYO ebook reader
* '''Microsoft'''
*** Zune Zune AC Adapter v2
* '''Motorola'''
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5 V 0.85 A SPN5504 Charger with Cable]
* '''Noname'''
** 5 V 2.1 A 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.2 V 1 A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]
** 5 V 1 A Model H-IP008 Serial No. H10T80L068
* '''Novatel Wireless'''
** 5 V 1.05 A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5 V 0.7 A Charger for Orange San Francisco
* '''Palm'''
** 5 V 1 A Charger for Palm Pixi+ (B)
* '''Pantech'''
** 5.0 V 1 A CNR USB with LG DLC100 micro USB cable
* '''Petzl'''
** 5.0 V 1 A Charger that came with the Tikka core2 XP
* '''Phihong'''
** Switching Power Supply. Model: PSAC09R-050. Output: 5 V, 1.8 A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
* '''PortaPow'''
** PortaPow UK Mains Wall Power Supply
* '''PowerGen'''
** PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. [http://www.amazon.com/gp/product/B0073FCPSK Amazon Link]
* '''Rayovac'''
** Universal USB Charger Model: PS69 100-240 VAC to 5 V 1 A (small cube w/folding plug) works w/wireless keyboard/mouse and mini-Wifi connected
* '''RS Components'
** HNP06UK (RS 7263069) Switching Adapter 5.0 V 1200 mA
* '''Samsung'''
** 5 V 0.7 A Charger for Galaxy S model ETA0U10EBE
** 5 V 0.7 A Charger for Galaxy SII
** 5 V 1 A Charger for Galaxy SIII
** 5 V 1 A Charger for Galaxy Nexus
** 5 V 0.7 A Charger for Galaxy S Vibrant (SGH-T959)
** 5 V 0.7 A Travel Adapter model ATADU10EBE
** 5 V 1 A? Samsung C Series TV USB-port for external HDDs. Running stable with openelec
** 5 V ?A (Unknown) Samsung Service Port (USB) on LN32A330J1DXZA 720p 32 inch HDTV
** 5 V Unknown Ampere Samsung UA22D5000 & UA32D5000 TV USB Port. Test with Raspbian Wheezy, Raspbmc, and RPITC
* '''Shun Shing'''
** 100-240 VAC to 5 VDC 1 A USB power supply, model SP5Q-AU [http://jaycar.co.nz/productView.asp?ID=MP3455 Jaycar]
* '''Sony Ericsson'''
** 5 V 0.7 A Charger CST-80
** 5 V 0.85 A Greenheart Charger EP800. Typically provides 4.8 V at 0.85 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>.
* '''StarTech'''
** 4 Port USB 2.0 Hub Raspberry Pi can be powered just by plugging USB input into the Raspberry Pi, don't need power in micro USB port.
* '''Travel Charger'''
** 5 V 2.0 A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]
* '''Technika'''
** 5 V 1 A USB Power Adapter, model MPASS01 (B)
* '''The Pi Hut'''
** Micro USB Power Supply for the Raspberry Pi. 5 V 1000 mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])
* '''Trisonic'''
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5 V, 800 mA) $3 at Daiso U.S. stores.
* '''TruePower'''
** [http://u-socket.com/ U-Socket] 5 V 2.1 A AC Receptacle with Built-in USB ports (2.1 A 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])
* '''ZTE'''
** ZTE Blade charger STC-A22O501700USBA-A 5 V 700 mA

===Problem power Adapters===
* '''Nokia'''
** 5 V 1.2 A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2
** [http://accessories.nokia.com/products/nokia-fast-usb-charger-ac-16/ 5 V 1 A AC-16E Charger] Provides only 4.7V across TP1 & TP2 when at idle

* '''Masterplug'''
** Masterplug Surge Protected USB Adaptor 2 x 1 A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artifacts using HDMI.
* '''Monoprice'''
** 5 V, 2 A 3 Outlet Power Surge Protector Wall Tap with 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot. Measured to less than 4.75 V between TP1 and TP2 when used with a Monoprice cable.
* '''Sony Ericsson'''
** 5 V, 850 mA EP800. Some failures to boot, Ethernet loops at boot.

===Working external Battery packs (with 5 V regulated output)===
* '''Anker Astro3'''
** Anker Astro3 10000 mAh with dual 2 A USB output
* '''Duracell'''
** PPS2 Instant USB Charger
* '''Energizer/XPAL'''
** XP18000 18000 mAh Power Pack
* '''Generic - eBay no brand'''
** 6000T Pocket Power 5000 mAh - eBay item 271009959140
** Power Bank for iPad/iPhone 5000 mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938
* '''Mophie'''
** 38113BBR Juice Pack Powerstation 4000 mAh: output 2.1 A max: included charging cable powers RPi, 7.5 hrs light use w/keyboard and mini-Wifi on RPi ports
* '''New Trent'''
** iCurve IMP70D 7000 mAh (Approx 12 hours from full charge)
** IMP120D 12000 mAh
* '''Sinoele'''
** Movpower - Power Bank 5200 mAh (8 hours with Wi-Fi active)
* '''TeckNet'''
** iEP387 Dual-Port 7000 mAh External Power Bank (The charging lead can be used to connect the Tecknet to the Raspberry Pi. Ran the Raspberry Pi with Wi-Fi dongle and wireless keyboard receiver for over 9 hours of light use.)
** iEP392 Dual-Port 12000 mAh External Power Bank (1 A port, ~16.5 hours)
** Rayovac PS60 5 V 800 mAh
* '''VINZO'''
** Power Bank 5000 mAh Grey Output 5 V 1000 mA
* '''Kodak Power Pack KP1000'''
** 1 A USB rechargeable battery pack - see [http://blog.sheasilverman.com/2012/09/its-alive/ Shea Silverman's blog]

== 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 Raspberry Pi's primary input fuse. HDMI ports (and the raspberry PI) are designed so that they deliver a very limited amount of power (50 mA) 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 200 mA, 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 non externally powered devices. If you have bought a non externally powered HDMI to VGA adapter, and you experience problems with it (It behaves badly, D1 burns out, F3 "blows", or your PSU overloads), then not all is lost, there are cheap (a few dollars) adapters that allow you to add external power to the HDMI cable! An example can be found here: [http://dx.com/p/hdmi-male-to-hdmi-female-adapter-w-power-input-port-black-155361].

===HDMI->DVI-D cables===
HDMI to DVI-D cables, or HDMI cables with an DVI-D adapters should work, connected to a DVI-D monitor, that is because both HDMI and DVI use the same kind of digital signaling (LVDS). The only limitation being that DVI-D misses the signal channel for audio.

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.

* '''The Pi Hut'''
** HDMI to DVI Cable for the Raspberry Pi (from [http://thepihut.com/collections/video-output/products/hdmi-to-dvi-cable-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
* '''Other Variants'''
** AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.
** [http://www.ebay.com/itm/DVI-Female-to-HDMI-Male-Adapter-Converter-Adaptor-Gold-for-HDTV-Full-HD-/320946033059?pt=US_Video_Cables_Adapters&hash=item4ab9dfd1a3 A generic HDMI-to-DVI converter from eBay]. Works well, but it's probably the cause of some power loss between the Raspberry Pi and the monitor, causing [http://elinux.org/R-Pi_Troubleshooting#Interference_visible_on_a_HDMI_or_DVI_monitor this] problem. A setting of config_hdmi_boost='''5''' in /etc/boot solved this. Note that config_hdmi_boost='''4''', as suggested in the troubleshooting guide, helped, but it did not solve the problem completely.

===HDMI->VGA Cables===
HDMI to VGA cables do not work!
They rely on logic incorporated in a video card that isn't available in a PI.
Somehow such a video card outputs analog signal on the otherwise purely digital HDMI connector, that seems to be the only way for it to work.
But normally HDMI cables never carry analog signals and the PI surely doesn't output analog signals either, almost no HDMI output device does, as its completely against HDMI specifications.

===HDMI->VGA converter boxes===
HDMI to VGA converters do work, they convert the digital serial data streams from HDMI and using complex logic, and digital to analog converters they convert the HDMI signal to the analog signals needed for VGA, and sometimes also convert HDMI audio to an analog stereo signal. But note that if they feed off the PI it can cause a problem, as the PI only is designed to provide about 50mA to the (HDMI or DVI-D) monitor, and these adapters use >200mA, while the absolute maximum the PI can let through is 200mA.
These adapters also thus use about half the energy that the PI (without USB devices) uses.
Therefore its much better to use an adapter that has an external power input. Alternatively there are HDMI dongles (male to female HDMI adapters) that have a barrel input connector to feed the adapter with.

Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.

At under ten pound this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.

[http://www.element14.com/community/groups/raspberry-pi/blog/2012/08/16/raspberry-pi-hdmi-to-vga-converter Sanoxy HDMI to VGA converter], $27 from Amazon, no changes required with official Raspbian Wheezy image (2012-Jul-15), note: had already disabled overscan previously

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 Raspberry Pi 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 1 A 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 Raspberry Pi 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 +5 V connection adapted from a USB cable, which bypasses Raspberry Pi's Micro USB cable and polyfuse F3.

* Link to a gallery with detailed images & steps of the same adapter modification: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

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 @60 Hz:
 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 it is very pricey compared to the 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.4 A, which is too much draw for the 5 V 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 it is 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. It is very cheap, but it 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 60 Hz, 1024x768 60 Hz, 640x480 works) The adapter is based on Lontium LT8511A chip, but I was unable to get the specification for it.
The D1 diode is getting very hot though. Most likely the adapter drives more than 200 mA. The standard RS Components 1.2 A USB power supply is able to provide enough power for the Raspberry Pi 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 Raspberry Pi's RCA video output. Additionally using a splitter cable (3.5 mm 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 ==

The SD card section has been moved to a separate page. See [[RPi SD cards]]

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}
♦
nbsp;V 1nbsp;V 1000

R-Pi Troubleshooting

2013-02-16T17:00:55Z

TrevorGowen: /* No HDMI output at all */ HDMI "hotplug" detection issues with 2013-02-09-wheezy-raspbian

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

===Normal LED status===
There are five LEDS near the USB connector.
{| border="1"
|+ LED statuses
! LED
! colour
! function
! normal status
|-
| ACT || green || card status || flashing during SD card activity
|-
| PWR || red || power || steady ON when PI receives some power
|-
| FDX || orange || full duplex || on when Ethernet connection is full duplex
|-
| LNK || orange || link || on when Ethernet is connected
|-
| 100 || orange || 100 Mbps || on when connection is 100 Mbps off when 10 Mbps
|}

See the next sections for how to interpret other statuses.

===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===
''note; For technical reasons the green LED might light up very faintly, this is normal, but it doesn't mean it "burns". When flashing/blinking the green LED should light up as bright as the power LED.''
*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. Did you have admin rights when you used the SD-card writer software? Without it the software might go through the motions without actually doing anything! To check if the writing process did actually happen Insert the SD card into a Windows machine and you should see bootcode.bin, fixup.dat and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]]. It is also possible that the image you are writing to the card is corrupt, as downloads do occasionally end up corrupted or truncated. You can check with the checksum utility if your download is correct.

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

*Confirm the USB cable is properly seated in the power slot. The red power LED does not necessarily mean it is fully connected.

*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 may be 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]]

*If for whatever reason the main polyfuse F3 has been overheated previously it may happen that it hasn't completely recovered, in which case, if you turn the PI on, a considerable amount of energy from the power supply is lost in the fuse and doesn't reach the PI. Try if the polyfuse seems hot. For this problem too read [[#Troubleshooting_power_problems]].

*Some problems have been reported if the ambient temperature is low that might be related to micro-fractures, fissures in solder or other issues. Try heating the Raspberry Pi with a hair dryer for just a few seconds (do not use excessive heat or you may cause irreversible damage!) and reconnect the power. Check this video http://www.youtube.com/watch?v=AwF6v-4NFdg

===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
* 7 flashes: <tt>kernel.img</tt> not found

Firmware since 20th October 2012 no longer requires loader.bin, and the flashes mean:

* 3 flashes: <tt>start.elf</tt> not found
* 4 flashes: <tt>start.elf</tt> not launched
* 7 flashes: <tt>kernel.img</tt> not found

If start.elf won't launch it may be corrupt.

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

With recent firmware, a coloured splash screen (actually its just four pixels "blown up" by the GPU to full screen) is displayed after GPU 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===
''note:during entering the password most linux distro's wont show that you typed in anything (not even "*" characters) this is normal behaviour, try the keyboard while entering the user name!''

This is most 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: 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.

Some users have reported that their keyboards work fine on Arch linux, but on Debian distro's, their keyboards become erratic (repeats and/or skips key presses). One suggested remedy to this, which has some positive feedback, is to adjust the USB bus speed. To do this, you need to edit the cmdline.txt file, and add "dwc_otg.speed=1" (without quotes) to the end of the file (found in the /boot directory).

Worst case scenario, some (advanced) keyboards, such as the Roccat Arvo, have kernel modules that need activating. If you have access to another keyboard temporarily, you will need to modprobe the relevent driver. Or if this is not possible, you can rebuild the kernel (instructions available on the wiki page) with the modules installed. (to find the drivers for keyboards etc, you need to find "Device Drivers -> hid Devices".)

===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/512M of RAM is divided between the ARM and GPU:
gpu_mem=16 : 16M GPU, 240M/496M ARM split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
gpu_mem=64 : 64M GPU, 192M/448M ARM split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
gpu_mem=128 : 128M GPU, 128M/384M ARM split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch, edit the gpu_mem= setting in your config.txt and reboot.

Note: other amounts are also possible, but setting gpu_mem=32 is usually the wrong choice. gpu_mem=16 is almost always a better choice.

Also note that before the release of the 51MB PI a different method was used based on splitting the 256MB RAM in a part for the CPU and GPU. As this noting system was causing trouble if the amount of RAM was not always the same. the above new method was adapted.

Make sure your editor doesn't change the first letter of the line into an uppercase letter, as some editors do. The entry is case sensitive.

== 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 on the rev 1.0 PC board. It is correctly labeled "100" on the rev 2.0 PC board. When that LED is on, RasPi is 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:
* Raspian "wheezy" pi/raspberry
*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.

'''More reasons why sound does not work with an HDMI monitor'''

With an HDMI connection it might be possible to hear:
./hello_audio.bin 1
but not:
aplay /usr/share/sounds/alsa/Front_Center.wav

Firstly, it seems that some HD TVs mute audible sound output when there is no digital input, and slowly fade the sound up and down at the start and end of digital input. This means that short duration sounds will not be heard. A work around is to play longer duration wav files.

Secondly, it seems that some HD TVs mute audible sound output when there is only one channel of digital input. So, as the file Front_Center.wav is mono, it might not be heard. ALSA aplay uses the file information header to configure its digital output. And the aplay -c 2 option does not over-ride the settings aplay picks up from the file information header. So, if your HD TV doesn't accept just one channel of digital input, you cannot use aplay to hear a mono wav file. However, with the command speaker-test, the -c2 option does work, and sets 2 channels in the digital stream. So speaker-test can be used to hear the file Front_Center.wav in either the left or right speaker using the -s option 1 or 2.
For example
Speaker-test -c 2 -s 1 -t wav -W /usr/share/sounds/alsa -w Front_Center.wav
should be heard on the left speaker. But note that the command speaker-test seems only to like mono wav files, and seems not to play stereo wav files.

The command aplay plays 2 channel stereo wav files in stereo sound without problem (provided they last longer than the time it takes the TV to unmute and remute). A helpful example I found is the stereo file LRMonoPhase4.wav at the Kozco web site [http://www.kozco.com/tech/soundtests.html]

===Sound does not work at all, or in some applications===
Enter the command 'alsamixer' and use the control to check that the volume is up (arrow keys) and that the output is not muted (M key).

In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To install support for sound, type the following from a command line (from the command prompt ''before'' "startx" or in a terminal window)

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled by default, so the 'modprobe' step is not necessary. Next try:

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:

amixer cset numid=3 <n>

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

If you have pulseaudio installed you need to also specify the card number:

amixer -c 0 cset numid=3 <n>

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.

Following this setup, you should be able to play wav files with the command

aplay "my file.wav"
Other command features can be found with
aplay --help
You will find numerous test files under /usr/share/scratch/Media/Sounds/ .

===Removal of installed pulseaudio===
Since December 2012 the standard raspbian wheezy distribution, and apt-get upgrade, have included pulseaudio. Forum posts suggest that pulseaudio can break alsa. Whilst some members identify various workarounds, others find only removal of pulseaudio restores sound output.
sudo apt-get --purge remove pulseaudio

===Playing MP3 files===
The alsa app included in the standard distribution plays wav files. If you want to play mp3 files, do the following to install an mp3 player (after installing alsa-utils):

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install mpg321

You can play mp3 files with the command

mpg321 "my file.mp3"

Other command options can be determined with
mpg321 --help
The mp3 support with this app is complete but not robust.

==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. At your own risk, you can go up to 11, but risk frying a sensitive monitor.

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|Troubleshooting Power Problems]].

===No HDMI output at all===
[[File:GPIOs.png|thumb|200px|right|The PI's GPIO header P1 [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]
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 Rasbian Wheezy] image (recommended) then try
hdmi_safe=1
Which will force the PI to boot in "safe mode".

For a quicker way to force wheezy into booting in safe mode, which doesn't need editing config.sys, you can also try to boot while holding the GPIO header P1-pin-5 (GPIO 1, SCL) low. This pin is normally held high with a pullup, but if you place a jumper between pin 5, (GPIO 1) and pin 6, (GND) of the GPIO header it will force the PI to boot in safe mode, which will force a 640x480 VGA screen mode, which any HDMI device should be able to display. Be very careful not to connect any other pins, especially not pins 1 and 2 (3V3 and 5V) as doing so, with power on, will damage your PI!

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

A similar problem has occured following the installation of [http://www.raspberrypi.org/downloads Rasbian Wheezy image] "2013-02-09-wheezy-raspbian" - the hotplug signal appeared to be no longer detected when a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/HDMI3PortSwitcher.html HDMI 3 Port Switcher] was in use for the Pi running from that image. An older, but updated and upgraded image still worked, as did a similar image on the other Pi connected to the switch, but, unless the above override was implemented, the Pi with the new image would only provide a HDMI display when '''directly''' connected to the monitor.

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|Troubleshooting Power Problems]].

Here's a rare cause: A standard HDMI cable has five individual ground wires plus a shield. Some cheap HDMI cables do not implement the individual grounds and just have a common foil shield that's connected to the HDMI plug shells at both ends. This works OK in most HDMI applications since most HDMI sources (like RasPi) and most monitors connect the shells to circuit ground. However, some HDMI or DVI monitors may requires individual ground lines. You can tell if an HDMI cable implements the individual grounds by checking for continuity using an Ohmmeter or multimeter. You can find the HDMI pinout for full-size connectors at [http://en.wikipedia.org/wiki/HDMI Wikipedia].

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

===HDMI -> VGA adapters===
Some good information can be found here:
* [[RPi_VerifiedPeripherals#HDMI-.3EVGA_converter_boxes]]
* [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 (RPi forum) Serious HDMI Problems. What's that smell? Burning Raspberry!]

A commonly used adapter from Ebay: gallery with detailed images & steps of a modification to use external power source: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

==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 commands
sudo apt-get update
sudo apt-get upgrade

==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 Micro USB power cable is low quality. Some Micro USB cables have very thin conductors, resulting in enough voltage drop for RasPi to fail even if the power supply itself is fine. For details, 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.
* The F3 Polyfuse could be blown or bad, see below for how to test.
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]]

'''How to test the F3 polyfuse<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=22318</ref>'''

# Remove all the things plugged into your Raspberry Pi, including SD card.
# Locate the TP2 test point on the top of the board.
# Turn your board over and find the TP2 test point on the bottom of the board. One lead of your multi-meter will always be on the TP2 point on the bottom of the board for all tests.
# Plug your power supply into the micro usb port and power your board.
# Place one lead of your multi-meter on the TP2 point on the bottom of the board and one lead on the side of the F3 fuse closest to the edge of the board. Note the voltage. This is the voltage coming into your RPi from your power supply.
# Keeping one lead on TP2, move the other lead to the side of F3 closest to the SD card slot. This is the voltage coming out of the F3 fuse.

[[File:F3-testing.jpg|none|frame|Multi-meter lead placement for testing the Raspberry Pi F3 Polyfuse]]

If the voltage is different by more than about 0.3v you probably have an issue with the F3 fuse<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24005&p=222526#p222526</ref>.

When polyfuses "blow" their resistance increases dramatically, there by limiting the voltage that can pass through them. If your power problem suddenly appeared after your board was known to be working fine, it is probable the fuse is just "blown" and will return to normal. Polyfuses recover from the tripped state to near their normal value in a few minutes, but do take some hours to fully recover so leave it unpowered and check it again in a little while.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24005&p=222549#p222543</ref> If your power problem has been since the first time you plugged in your board, the fuse was probably bad when it arrived and should be returned to place you purchased it.

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 Expansion Boards

2013-02-14T18:02:01Z

TrevorGowen: /* Slice of Pi */ Slice of PI/O variation added

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

==Introduction==
On the Raspberry Pi, there are several connections which can be used for expansion:
* The [[RPi Low-level peripherals|Rpi GPIO]] (General Purpose Input/Output) pins are exposed, that means that expansion boards are able to talk directly to the CPU.
* The DSI connector will allow low-level interfacing with LCDs and other displays.
* The CSI connector will allow camera modules to be added in future.

==Current expansion boards==

=== AFLEX Robotic Board ===
[http://www.web4robot.com AFLEX Robotic Board] is dual motor control and data acquisition board with I2C and Serial interfaces. The board provides 2 motor control drivers with max current up to 3.5A, 8-bits data port with each pin setup as digital input /output or analog input, 10-bits ADC with up to 5 analog channels, 4 inputs for the sensor connections, infrared (IR) remote control. The board provides direct connection to Raspberry Pi.

=== ADC Pi, Delta Sigma Pi and RTC Pi===
ADC Pi from AB Electronics UK brings 8 channel 15 bit analogue sampling to the Raspberry Pi platform. A buffered 5V i2c bus and stackable headers make this a useful addition to your Raspberry Pi project. The Delta Sigma Pi is a 18 bit Delta Sigma ADC board with 8 inputs, a buffered 5V i2c bus and stackable headers. The RTC Pi is a Real Time Clock module with a buffered 5V i2c bus and stackable headers.
http://www.abelectronics.co.uk/default.aspx (see also: [[RPi_ADC_I2C_Python|setup tutorial]])

=== Arduino Shield and Raspberry Pi ===
a little board with Arduino socket and Raspberry Pi socket
you can power the boards with 12Volt or 5Volt
http://www.progetti-hw-sw.it/raspberry.htm

===Buffer Board===
[http://www.thebox.myzen.co.uk/Raspberry/Buffer_Board.html Buffer Board] How to make a Pi Buffer on Veroboard. Each of the 14 outputs can drive up to 500mA using a Darlington array.

=== Buzzberry Buzz-Board Interface ===
[http://fortito.com Buzzberry] is an interface board enabling expansion using the Buzz-Board modular system designed primarily for educational use.

===CJE/4D RTC===
On 2nd January 2012, CJE/4D announced that they have a real-time clock (RTC) expansion board in the works: [http://www.raspberrypi.org/forum/features-and-requests/rtc]

===GertBoard===
::''main page: [[RPi Gertboard]]''
This board is a buffer between your Rpi and the real world, use it to flash LEDs on and off, drive motors, run sensors and all that other fun stuff.<ref>http://www.raspberrypi.org/archives/411</ref>

===GELI 'jelly'(GPIO Experimenter and Lab Interface Board)===
[http://www.fulburncams.gb.net/ Raspberry Geli Board] Extends the GPIO and provides I2C, D2A/A2D, DC Motor(L298), RS232, Realtime Clock (DS1307), 1-wire and prototyping area on 150 * 100mmm PCB.

=== GPIO isolated expansion/RTC ===
[http://www.utelectronics.com UT Electronics] is developing a expansion board containing a fully isolated 16-I/O I2C GPIO expander and RTC, with extensive options for further expansion. C and Python libraries will be available at launch. The board will probably be sold as a kit, with SMT components already in place.

Update: According to their website, the realities of life prevent them from bringing the product to market. They are hoping someone will pick up the ball. They have released the PCB layout and all documentation for free on their website.

=== Heber x10i ===
[http://www.heber.co.uk/gaming-amusement/xline/x10i-overview/ Heber Ltd] X10i integrates real time I/O into a RPi control system. A secure real-time controller that permits control over multiple and different types of inputs and outputs, and uses the USB 2.0 communication standard. It is an all in one plug and play board for developing LED drivers, control, sensing of different switches, and driving stepper motors. Exclusive features include a real time clock, battery backed static ram, a Dallas chip (for unique board identification), 2 serial communication ports, a powerful audio amp and a independent dedicated on board processor.

Heber now offers drivers in C/C++ and Linux to make it even easier for programmers, inventors and developers to connect with the outside world using X10i and their Raspberry Pi.

=== aLaMode ===
[http://wyolum.com/?p=824 “À la mode”] is an Arduino clone specifically designed to interface with the Raspberry Pi. You can of course connect a standard Arduino to a Pi USB port using a cord, but when you want a turnkey solution, how about an Arduino compatible “plate” (shield) that fits right on top of the Raspberry Pi with direct access to GPIO port? The Linux side handles all of the displays, human interfaces, and number crunching. The low power Arduino compatible “à la mode” board handles sensors, servos/motors, and provides a highly accurate real time clock.

=== LedBorg ===
[http://www.piborg.org/ledborg LedBorg] is an ultra bright RGB LED add on board for your Raspberry Pi. Capable of 27 colour combinations and controllable from either a GUI or the command line, it can also perform patterns.
Small board which connects directly to the GPIO header.

=== Paper-Duino-Pi ===
[http://www.paperpcb.dernulleffekt.de/doku.php?id=raspberry_boards:paperduinopi Paper-Duino-Pi] is an Arduino shield for the Raspberry Pi. Due to the fact that it is designed as Paper-PCB it is easy to create and one doesn't need a printed circuit board. All components are cheap standard electronic parts. [http://youtu.be/e-x_ZPg8ymo A video is found here].

=== PiBorg ===
[http://www.piborg.org PiBorg] is a Robotics add on board which adds the ability to control motors - from small to large (including DC motors, Stepper motors, BLDC motors and Solenoids) from your Raspberry Pi. It supports feedback via Encoders and Potentiometers, allowing closed loop (servo) control of motors to set positions, velocities and accelerations and it is capable of monitoring drive current and voltages. The loop is PID based and as PiBorg is an [http://sourceforge.net/p/piborg/wiki/Home/ Open Source project], you may change the code as you please. It has the ability to drive 10A motors and more, so you'll never be left underpowered with this board!

=== Pi Crust ===
[http://picru.st picru.st] is a very compact and cheap breakout board for your Raspberry Pi that allows easy access to the Pi's pins, grouping them into a logical order and adding clear labeling. Small and simple.

===Piface===
[http://piface.openlx.org.uk Piface] is simpler than the [[RPi Gertboard]] (it's aimed at less experienced users), but also intended to connect to PCs and Android to be platform agnostic

===Pi232 RS232 board===
[http://www.logicethos.com/Blog/2012-06-21:_Pi232_Raspberry_Pi_RS232_boards Pi232] is an RS232 expansion board that plugs onto GPIO connector.

=== PiDuino ===
[http://www.youtube.com/watch?v=u5c1Dfaf57g Youtube video] showing prototype board

=== Pi Plates ===
[http://www.adafruit.com Adafruit Industries] announced in March 2012 the intention of making expansion boards for the Raspberry Pi under the "Pi Plate" name.<ref>
http://www.adafruit.com/blog/2012/03/14/adafruit-experimenting-with-pi-plates-for-raspberry_pi-shields-for-the-raspberry-pi/</ref>.

The first board available is a [http://adafruit.com/products/801 prototyping board] that overlays the Raspberry Pi via a long plug-in header. It has screw terminals for all the Pi [[GPIO]] lines.

=== PiPLUS Multifunction I/O Extension Board ===
[http://www.web4robot.com PiPLUS Multifunction I/O Extension Board] is designed as versatile, general-purpose data acquisition and control module.
Key Features: Battery-backed Real Time Clock; 3.5A DC motor driver chip; 8-bits digital I/O Data Port; 10-bits ADC with 4 analog channels; DAC; 4 high power outputs; 4 PWM outputs; IR Remote Control input; 2 user's buttons; AVR ATMEGA328P microcontroller with a preloaded Arduino bootloader and Arduino Shields connectors; 3V - 5V buffers for I2C, SPI and Serial interfaces; Power supply with 5V and 3V regulators.

PiPLUS board also works as a bridge between Raspberry Pi and ARDUINO and provides a direct connection to Arduino Shields. You can use the standard ARDUINO environment and graphical interface for Windows or Linux for software development and ATMEGA328P microcontroller programming.

=== Pi Tin ===
Not yet tested, comments welcome
Project files for Eagle here: [http://www.delong.com/Raspbery%20PI/]
Schematic and Board images: [http://elinux.org/File:PiTin_Schematic.png] [http://elinux.org/File:PiTin_Boardpng.png]
This board uses Microchip 16-pin GPIO expanders driven by SPI to provide up to 256 additional GPIO pins at a very low cost. Optionally, it can supply power
for the board and the Raspberry PI.

The board can be made in a stackable manner allowing you to also place additional peripherals on the GPIO connector. It makes non-exclusive use of all
four SPI pins as well as exclusive use of the CE0 Pin.

If you install (and power) the power supply components, the board will supply up to 1A at 5VDC. This is not enough to power all GPIO pins on a fully populated board, but in most applications should be sufficient to power the RPI and a reasonable number of GPIOs. An external power supply should be used for higher-power applications. This board should never be powered from the RPI as even one of the chips can draw more than the RPI can provide.

The power supply is quite flexible and will accept anything from 8-25VAC or 8-42VDC. It is based on a Recom module which provides a switching power supply in a form factor that is a drop-in replacement for 7805 series TO-220 linear regulators.

The 8 chips can be had for about $4@ or less and the power supply components total about $15. A fully populated board is about $49+PCB, $31+PCB for 64 GPIO pins.

You can have the PCB made at a variety of fabricators. [http://batchpcb.com] does very nice work and is hobbyist friendly at very reasonable prices.

===Pi-Wire===
[http://go.je/18z Pi-Wire] Homelabs are developing options for connection of a 1-wire bus to the RaspberryPi. Boards include SPI breakout connections for future boards.

=== Ponte ===
[http://omer.me/2012/05/introducing-ponte/ PONTE initial post] An arduino shield bridge from Omer and SKPang

=== Quick2Wire GPIO Expansion Board ===
[http://quick2wire.com Quick2Wire GPIO board and experimenters kit] is an extension board for the Raspberry Pi that has level converters to allow the driving of TTL and real world devices such as LED's and switches. It will also provide an experimenters kit, a software framework and a number of tutorials.

=== Raspberry Pi IO Interface ===
[http://dangerousprototypes.com/forum/viewtopic.php?f=56&t=3996 forum thread] showing 'paper mockup'. Another buffered IO expander.

=== Raspberry Pi to Arduino Shields Connection Bridge ===
[http://www.cooking-hacks.com/index.php/documentation/tutorials/raspberry-pi-to-arduino-shields-connection-bridge Raspberry Pi to Arduino Shields Connection Bridge] allows you to use any of the shields, boards and modules designed for Arduino in Raspberry Pi. It includes also the possibility of connecting digital and analog sensors, using the same pinout of Arduino but with the power and capabilities of Raspberry. Using arduPi library, you will be able to make programs in Raspberry with the same code used in Arduino. To do so, Cooking Hacks Team have implemented conversion functions so that you can control in the same way as in Arduino all the I/O interfaces: i2C, SPI, UART, analog, digital, in Raspberry Pi.

=== Relay board and Raspberry Pi GPIO ===
a board with 8 relays and 8 input with a Raspberry Pi socket
you can power the boards with 12Volt, the board has a DIN rail container
http://www.progetti-hw-sw.it/raspberry.htm

=== MiniPiio L293D ===
[http://zuzebox.wordpress.com/2012/09/07/minipiio-l293d-board-v0-10/] is a small (50x40mm) add-on board which provides a dual H-Bridge DC-Motor circuit using the venerable L293D chip.

=== MiniPiio Relay2 ===
[http://zuzebox.wordpress.com/2012/09/07/minipiio-relay2-board-v0-10/] is a small (50x40mm) add-on board which provides a two 1A DPCO Relays. Each relay has a set of screw terminals for easy wiring.

=== MiniPiio DIO16 ===
[http://zuzebox.wordpress.com/2012/06/24/minipiio-dio16-v0-10/ MiniPiio DIO16] is a small (50x40mm) add-on board which provides an additional 16-channels of Digital Input/Outputs for the RPi. It can use either a MCP23S17 (SPI) or MCP23017 (I2C) Port Expander.

=== MiniPiio RS232 ===
[http://zuzebox.wordpress.com/2012/06/24/minipiio-rs232-v0-10/ MiniPiio RS232] is a small (50x40mm) add-on board which provides a basic RS232 to TTL interface for the RPi. It uses a 3.3V MAX3232 to provide the RS232 interface.

=== MiniPiio ULN2803 ===
[http://zuzebox.wordpress.com/2012/06/24/minipiio-uln2803-v0-10/ MiniPiio ULN2803] is a small(50x40mm) add-on board which connects a ULN2803 Darlington Driver chip to the RPi's GPIO allowing the RPi to control electronic circuits which require more current to drive them.

=== RPi MIDI Breakout Board ===
[http://zuzebox.wordpress.com/2012/03/18/midi-breakout-board-for-raspberry-pi-v0-10/ RPi MIDI Breakout Board] is a simple MIDI breakout board for the Raspberry Pi using the hardware UART from the RPi's expansion interface

=== RPi Protoboard SM===
[http://zuzebox.wordpress.com/2012/06/25/raspberry-pi-protoboard-sm-v0-10/ RPi Protoboard SM] is a simple prototype board for the Raspberry Pi 
[http://www.designspark.com/knowledge/raspberry-pi-prototype-board-files another link] to the same project?

=== RPi "UserPort" ===
[http://zuzebox.wordpress.com/2012/03/14/userport-for-raspberry-pi-v0-10/ RPi UserPort] is a digital and analogue I/O board for the Raspberry Pi. UserPort replicates the original BBC Micros digital User Port and Analogue Port but uses more modern components such as the MCP23S17 16-ch GPIO and MCP3204 4-ch 12-bit ADC.

===rpi_serial===
BitWizard has a [http://www.bitwizard.nl/wiki/index.php/Raspberry_pi_expansion_system_page#expansion_boards Raspberrypi serial breakout board]. It breaks out four serial buses from the GPIO port.

BitWizard then has a series SPI (or I2C) expansion boards that can be daisy-chained off the SPI (or I2C) buses of the expansion board. A virtually unlimited number of expansion boards can be connected. Expansion boards are available that drive a simple 16x2 text LCD, more general purpose IOs, servos, temperature sensors, relays, optocouplers etc.

===RPi RS232 Breakout Board===
[http://zuzebox.wordpress.com/2012/02/07/rs232-breakout-board-v0-20-for-raspberry-pi/ RPi RS232 Breakout Board] is a simple RS232 breakout board for the Raspberry Pi

=== 1-Wire Masters from Sheepwalk Electronics ===

[http://www.sheepwalkelectronics.co.uk/ Sheepwalk Electronics] are currently developing a series of expansion boards for the Raspberry Pi to interface your Raspberry Pi to a Dallas/Maxim 1-Wire network. The range includes a simple passive "master" (called the RPI1) to allow easy use of the kernel 1-Wire driver, a single channel I2C master based around the DS2482-100 (called the RPI2) and an 8 channel I2C master based around the DS2482-800 (the RPI3). The RPI1 and RPI2 modules are now available on our website. The RPI3 8 channel master is still under development. The modules are all available as a bare PCB, kit of parts or fully assembled/tested.

===Slice of Pi===
[http://shop.ciseco.co.uk/slice-of-pi/ Slice of Pi] Ciseco have produced a convienient small break out board for the Raspberry PI. XBee style connector for XRF / XBee / RN-XV / XBT / RF-BEE etc. Has the SPI and I2C pins on one standard 8 way header and the Raspberry PI's 8 general purpose I/O pins on another for easy access. Comes as a kit of parts that needs to be soldered. Construction is very easy and suitable for children with basic soldering skills.

[http://shop.ciseco.co.uk/k002-slice-of-pi-o/ Slice of PI/O] is a variation of the above produced by Ciseco based upon [http://nathan.chantrell.net/20120602/raspberry-pi-io-expander-board/ Nathan Chantrell's MCP23017/Slice of Pi "project"]. The MCP23017 may be powered from either the Pi's 3.3V/5.0V GPIO pins or, with care, an external psu. The use of a 5.0V power source means that the MCP23017's 16 (2 x 8) GPIO's can interface directly with 5V logic families etc. However, the Pi's own GPIO's, also available, will still need 3.3V - 5.0V level shifters. [[User:TrevorGowen|Trevor Gowen]]'s experimental [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SliceOfPio.html LED BarGraph "board"] has been "piggy-backed" onto one of these.

=== XBee ZB SMT Backpack ===
The [http://www.bootc.net/archives/2012/06/20/raspberry-pi-xbee-smt-backpack/ Raspberry Pi XBee ZB SMT Backpack] by [[User:bootc|bootc]] is a carrier board for [http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-smt Digi XBee ZB SMT] modules. These are different to the normal XBee modules because they are surface mount and additionally can interface to a host using SPI as well as serial. The backpack also features 3 LEDs for status signals as well as two FTDI headers (one for the RPi and one for the XBee), as well as being able to host a 'normal' XBee module (though of course you can't use SPI with those).

=== RPi Servo board ===
The [http://electronics.chroma.se/rpisb.php Raspberry Pi Servo board] by [[User:adent|adent]] is a small expansion board for connecting up to eight RC servos and/or an ESC (Electronic Speed Controller) to the RPi. It has a pass through for the GPIO port and it uses the serial line in it for commands. The interface is a simple ASCII-protocol via the serial port. It also has five own GPIO-pins that is not supported by card firmware yet. Firmware is released as GPL. Can power RPi from ESC or external source.
Youtube clip of [http://youtu.be/_W1WXnL9MeA first prototype]. Working on an alternate firmware to connect DHT22/11 humidity/temperature sensors to the board instead.

=== RPi SOFTWARE Servo board ===
The [http://electronics.chroma.se/rpiswsb.php Raspberry Pi SOFTWARE Servo board] by [[User:adent|adent]] is a small expansion board for connecting up to eight RC servos and/or an ESC (Electronic Speed Controller) to the RPi. It has a pass through for the GPIO port. Can power RPi from ESC or external source.
It needs a [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=37&t=15011&hilit=servo kernel module] to work. The card only buffers the GPIO of the RPi and
provides convenient connectors. Since there was room on the PCB, the serialport, GND and 3V3 is broken out.

=== Raspy Juice Exp Board ===
[http://2-watt-elements.myshopify.com/ Raspy Juice] by 2-Watt Elements is an experimental board that supplies the Raspberry Pi with +5V through the GPIO header. With its wide input voltage range (6~23V), the buck regulator can be powered by batteries, 12V Adapters, solar, etc. Other features are the RS232 level console port, PCF8523 RTC, and an expansion ATmega168A microcontroller as an I2C slave. This latter MCU has interfaces of an RS485 port, an additional RS232 port, 4 RC-servo ports and unused-pins expansion header. The MCU firmware is updateable through the I2C interface. Hardware details are in http://code.google.com/p/raspy-juice/wiki/1_Hardware_Description

=== pyMCU ===
[http://www.pymcu.com pyMCU] is a python controlled microcontroller that works with the Raspberry Pi, connects to the USB port and uses the pyMCU python module and pyserial to control the microcontroller in your python script. You can communicate with i2c, spi, serial, and one wire devices, software configurable pulse in / out functions, has 13 Digital IO Pins, 6 10-bit Analog Pins, 5 10-Bit PWM Pins, blink LEDs, control servos and motors, read various sensors, built-in functions for sound generation: arbitrary frequency generator, misc. sound / tone generator, DTMF generator. PyBootloader - python script for uploading new firmware versions or your own microcontroller code. Check out some of the [http://pymcu.com/Tutorials.html Tutorials] and [http://pymcu.com/Examples.html Examples]

=== RPi CC1101-OneWire-Clock extension ===
The [http://busware.de/tiki-index.php?page=COC RPi-COC board] from [http://busware.de busware.de] adds Onewire, a Sub-1 GHz RF Transceiver, RTC and an EEPROM mainly for smart home automation. The Onewire RJ11 port is driven by a DS2482 chip supported by 5V levelshifter and strong pullup. The DS1339-RTC is powered by CR2032 battery or on-board 60mF supercap. The 2Kbit EEPROM (at24c02) is mainly to hold board specific config data. The CC1101 Sub-1 GHz RF Transceiver is controlled by an atmega1284 to pre-process air data. It is connected to RPis UART and contains a avr109-bootloader for firmware updates. The popular [http://culfw.de culfw-firmware] lets you interact with FS20, Homematic, Intertechno or similar actors and sensors - easily using [http://fhem.de FHEM]-home automation server. In addition a secured 5V power socket for external power supplies is provided.

=== RFM12Pi - Wireless OpenEnergyMonitor Base-station ===
Add's RFM12B wireless (868/433/912Mhz) RF transceiver capability to the Raspberry Pi. The RFM12pi has got an-board ATtiny84 microcontroller pre-loaded with firmware to decode RFM12B packets from [http://jeelabs.org JeeNode] and [http://openenergymonitor.org OpenEnergyMonitor] sensor modules onto Raspberry Pi's internal serial UART. Designed to be used with [http://emoncms.org emoncms] running on a Raspberry Pi web-server to make a low power energy, temperature and other environmental data logging and visualisation server. Developed as part of the [http://openenergymonitor.org openenergymonitor.org] project. For more info see [http://openenergymonitor.blogspot.com/2012/11/raspberry-pi-emonbase.html introductory blog] post, [http://openenergymonitor.org/emon/emonbase/raspberrypi overview documentation page] and [http://wiki.openenergymonitor.org/index.php?title=Raspberry_Pi technical documentation wiki].

=== Rs-Pi 4 USB hub & multi-function I2C AD/DA RTC RS232 board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 4 Ports USB hub with multi-function I2C board
size 71mm x 54mm small than Raspberry Pi
(RTC-DS1307, Temperature Sensor-TMP102, D/A MCP4725,A/D ADS1015,EEPROM, MCP23008, FT232RL, ZT3243)
[http://www.pridopia.co.uk/pi-usb-hub-i2c-ad-da-ft232-r1.html Rs-Pi-USB-hub-I2C-multi-function AD/DA Board]
with USB to RS232 full DB9 9pin signal or USB to TTL (FT232RL) console port), RTC with CR1220 battrey, USB with 1.6A PTC fuse for all four USB ports. No extra extension cable need. and no extra Power adapter for USB hub.
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

We have four different models with different function, you can choose anyone you want.
* 1. Rs-Pi 4 USB Hub with ( ds1307) [http://www.pridopia.co.uk/pi-usb-4hub-rtc-lite2.html Rs-Pi 4 USB Hub RTC -Lite]
* 2. Rs-Pi 4 USB Hub with ( ds1307,tmp102, mcp4725,24c32) [http://www.pridopia.co.uk/pi-usb-hub-i2c-lite.html Rs-Pi USB Hub-Lite]
* 3. Rs-Pi 4 USB Hub with ( ds1307,tmp102, mcp4725,24c32, ft232RL) - with USB to TTL (just need one USB cable plug-in your PC and Rs-Pi) [http://www.pridopia.co.uk/pi-usb-hub-i2c-ft232-lite.html Rs-Pi USB Hub FT232RL-Lite ]
* 4 Rs-Pi 4 USB Hub with ( ds1307,tmp102, mcp4725,ads1015, 24c32, mcp23008, ft232RL, zt3243) with USB to RS232 (DB9 full 9pin RS232 COM port output) or USB to TTL console port [http://www.pridopia.co.uk/pi-usb-hub-i2c-ad-da-ft232-r1.html Rs-Pi-USB-hub-I2C-multi-function AD/DA Board]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi 4 USB hub with I2C 23017x2 32 GPIO board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 4 Ports USB hub with I2C 23017x2 32 GPIO board
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-usb-4-hub-i2c-23017-2.html Rs-Pi-4-USB-hub-I2C-23017x2 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi 4 USB hub with SPI 23s17x2 32 GPIO board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 4 Ports USB hub with SPI 23s17x2 32 GPIO board
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-usb-4-hub-spi-23s17-2.html Rs-Pi-4-USB-hub-SPI-23s17x2 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi 7 USB hub with multi-function I2C AD/DA board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 7 Ports USB hub with multi-function I2C board
size 71mm x 54mm small than Raspberry Pi
(RTC-DS1307, Temperature Sensor-TMP102, D/A MCP4725,A/D ADS1015,EEPROM)
[http://www.pridopia.co.uk/pi-usb-7-hub-i2c-ad-da.html Rs-Pi-7-USB-hub-I2C-multi-function AD/DA Board]
RTC with CR2032 battrey, USB with 2 x 1.6A PTC fuse for all seven USB ports. No extra extension cable need. and no extra Power adapter for USB hub.
All from [http://www.pridopia.co.uk/index.html Pridopia]

We have two different models with different function, you can choose anyone you want.
* 1. Rs-Pi 7 USB Hub with ( ds1307,tmp102,24c32) [http://www.pridopia.co.uk/pi-usb-7-hub-i2c-lite.html Rs-Pi 7 USB Hub -Lite]
* 2. Rs-Pi 7 USB Hub with ( ds1307,tmp102,24c32,ads1015,mcp4725 ) [http://www.pridopia.co.uk/pi-usb-7-hub-i2c-ad-da.html Rs-Pi 7 USB Hub AD/DA Board ]

All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi 7 USB hub with I2C 23017x1 16 GPIO board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 7 Ports USB hub with I2C 23017 16 GPIO board
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-usb-7-hub-i2c-23017-1.html Rs-Pi-7-USB-hub-I2C-23017 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi 7 USB hub with SPI 23s17x1 16 GPIO board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi Internal 7 Ports USB hub with SPI 23S17 16 GPIO board
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-usb-7-hub-spi-23s17-1.html Rs-Pi-7-USB-hub-SPI-23S17 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 23017x2 32 GPIO with uln2803 x2 board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi I2C 23017x2 32 GPIO with 8 Switch input & uln2803x2 output board
each 23017 port A output to ULN2803, first one 23017 port B for 8 switch input, second one 23017 port B for normal output with 8 LED.
with 3.5mm block terminal 9pin output, can plug in our 2803 relay board
with two Step motor connector (5V,D0,D1,D2,D3) (5V,D4,D5,D6,D7) can use Step motor (28BYJ-48 5VDC)
with 4 5V motor output port
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-i2c-23017x2-2803x2.html Rs-Pi-I2C-23017x2-2803x2 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi SPI 23s17x2 32 GPIO with uln2803 x2 board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* The Rs-Pi SPI 23s17x2 32 GPIO with 8 Switch input & uln2803x2 output board
each 23s17 port A output to ULN2803, first one 23s17 port B for 8 switch input, second one 23s17 port B for normal output with 8 LED.
with 3.5mm block terminal 9pin output, can plug in our 2803 relay board
with two Step motor connector (5V,D0,D1,D2,D3) (5V,D4,D5,D6,D7) can use Step motor (28BYJ-48 5VDC)
with 4 5V motor output port
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-spi-23s17x2-2803x2.html Rs-Pi-SPI-23s17x2-2803x2 Board]
All from [http://www.pridopia.co.uk/index.html Pridopia]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 23017-2 32 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 23017 x2 32GPIO board I2C interface
size 49mm x 49mm
with 32 Blue SMD LED [http://www.pridopia.co.uk/pi-23017-2-lp.html Rs-Pi-23017-2]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi SPI 23s17-2 32 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi SPI 23s17 x2 32GPIO Board SPI Interface
size 49mm x 49mm
with 32 Blue SMD LED [http://www.pridopia.co.uk/pi-23s17-2-lp.html Rs-Pi-23S17-2]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi ULN2803 & SPI AD/DA Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi ULN2803 & SPI AD/DA Board
ULN2803 8 Darlington transistor array output
can output to 8 5V relay
with 2 Step motor connector,can connect Step motor(28BYJ-48 5VDC)
and MCP3002 SPI Interface 10 bit Analog-to-Digital Converter
and MCP4802 SPI Interface 8 bit Digital-to-Analog Converter
size 49mm x 39mm
[http://www.pridopia.co.uk/pi-2803-sm-ad-da-lp.html Rs-Pi-2803-ADDA]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi ULN2803 8bit 2 Relay Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi ULN2803 2 Relay Board
ULN2803 8 Darlington transistor array output
size 49mm x 40mm
[http://www.pridopia.co.uk/pi-2803-2relay.html Rs-Pi-2803-2Relay]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi ULN2803 8bit 4 Relay Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi ULN2803 4 Relay Board
ULN2803 8 Darlington transistor array output
size 76mm x 36mm
[http://www.pridopia.co.uk/pi-2803-4relay.html Rs-Pi-2803-4Relay]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi USB to TTL console Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi USB to TTL Console Board
USB to TTL Console module plug in Rs-Pi with normal USb to Mini USb cable with your PC or Mac
size 32mm x 39mm
[http://www.pridopia.co.uk/pi-usb-ttl.html Rs-Pi-USB-TTL Console Board]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi RS232 DB9 cable ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi RS232 DB9 console cable with 90cm length cable [http://www.pridopia.co.uk/pi-232r1-db9.html Rs-Pi-RS232-DB9]

All of our Rs-Pi Products are design and Made in UK
All can plug in our RS-Pi USB hub multi-function Board and work together.

=== (MyPiShop) Pi 8 LED & 8 Button ===
[http://mypishop.com/Pi%208%20LED%20&%208%20Button.html Pi 8 LED & 8 Button] interface board for Raspberry Pi.

Perfect way to learn how to use the GPIO pins. 
Plugs directly into the Raspberry Pi GPIO connector. (P1 header) 
Has eight bright green LED's and eight momentary switches. 
For a more detailed description see: http://mypishop.com/Pi%208%20LED%20&%208%20Button.html

=== (MyPiShop) Stepper Motor Controller Board ===
[http://mypishop.com/Stepper.html Pi Stepper Motor Controller] interface board for Raspberry Pi.

The stepper board uses 8 GPIO pins to drive up to two stepper motors. 
(One stepper motor is included in the kit) 
Plugs directly into the Raspberry Pi GPIO connector. (P1 header) 
The board can use the 5 VDC provided by the Raspberry Pi or you can optionally provide your own source voltage to drive the motors. 
This board includes a ULN2803 8 Channel Darlington Driver and can be used to control other higher current devices such as relay boards, etc. 
For a more detailed description see: http://mypishop.com/Stepper.html

=== (MyPiShop) Read Your Pi !(LCD Interface Board) ===
[http://mypishop.com/Read%20Your%20Pi%20!.html Read Your Pi (LCD)] interface board for Raspberry Pi.

Available kits with 20x4 LCD display or 16x2 LCD display.
The interface board uses the GPIO pins display characters on a LCD display. 
Plugs directly into the Raspberry Pi GPIO connector. (P1 header) 
For a more detailed description see: http://mypishop.com/Read%20Your%20Pi%20!.html

=== (MyPiShop) Protect Your Pi ! (16 or 32 IO Expansion Kit) ===
[http://mypishop.com/ Protect Your Pi (LCD)] interface board for Raspberry Pi.

Available kits with 16 or 32 GPIO expansion pins.
The expansion board uses the I2C bus on the Raspberry Pi to provide up to 32 additional GPIO pins. 
Plugs directly into the Raspberry Pi GPIO connector. (P1 header) 
For a more detailed description see: http://mypishop.com

=== (MyPiShop) Pi MATRIX ! 8X8 LED Matrix with 16 bit I/O ! ===
[http://mypishop.com/ Pi MATRIX !] 8X8 LED Matrix with 16 bit I/O kit for the Raspberry Pi.

HUGE 8X8 LED MATRIX 
Plugs directly into the Raspberry Pi GPIO connector. (P1 header) 
Take the display off and use it for 16 bits of I/O 
For a more detailed description see: http://mypishop.com

=== BerryClip 6 LED Buzzer Board ===
The [http://www.raspberrypi-spy.co.uk/berryclip-6-led-add-on-board/ BerryClip] is a small board providing 6 coloured LEDs, 1 buzzer and 1 switch. It provides an easy and quick introduction to GPIO experimenting. The board plugs directly onto the Raspberry Pi GPIO connector and there are lots of Python example scripts available. 
For a more detailed description see: [http://www.raspberrypi-spy.co.uk/berryclip-6-led-add-on-board/ BerryClip on Raspberrypi-spy.co.uk]

=== Rs-Pi I2C 23017-8 128 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 23017 x8 128GPIO board I2C interface
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-23017-8-lp.html Rs-Pi-23017-8]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi SPI 23s17-8 128 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi SPI 23s17 x8 128GPIO Board SPI Interface
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-23s17-8-lp.html Rs-Pi-23S17-8]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 23017-4 64 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 23017 x4 64 GPIO board I2C interface
size 71mm x 54mm small than Raspberry Pi
with 64 Blue SMD LED [http://www.pridopia.co.uk/pi-23017-4-lp.html Rs-Pi-23017-4]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi SPI 23s17-4 64 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi SPI 23s17 x4 64 GPIO Board SPI Interface
size 71mm x 54mm small than Raspberry Pi
with 64 Blue SMD LED [http://www.pridopia.co.uk/pi-23s17-4-lp.html Rs-Pi-23S17-4]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 32 Channel PWM /Servo Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 32 channel PWM / Servo board I2C interface
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-9685-2-lp.html Rs-Pi-9685-2]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 16 Channel PWM /Servo & I2C 23017 16 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 32 channel PWM / Servo board & I2C 23017-1 16 GPIO + uln2803 for Port A
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-9685-23017-lp.html Rs-Pi-9685-23017]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi I2C 16 Channel PWM /Servo & SPI 23s17 16 GPIO Board ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi I2c 32 channel PWM / Servo board & SPI 23S17-1 16 GPIO + uln2803 for Port A
size 71mm x 54mm small than Raspberry Pi
[http://www.pridopia.co.uk/pi-9685-23s17-lp.html Rs-Pi-9685-23s17]
All of our Rs-Pi Products are design and Made in UK

=== Rs-Pi ULN2803 8bit 2 Relay Board + 2 Step Motor Port ===
[http://www.pridopia.co.uk/ixx-rspi.html Pridopia] P-pi serials for Raspberry Pi
* Rs-Pi ULN2803 2 Relay Board + 2 Step Motor Port
ULN2803 8 Darlington transistor array output
size 55mm x 40mm
[http://www.pridopia.co.uk/pi-2803-step.html Rs-Pi-2803-2Relay-StepMotor]
All of our Rs-Pi Products are design and Made in UK

==References==
<references/>

{{Template:Raspberry Pi}}

User:TrevorGowen

2013-02-14T17:35:33Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 14.02.2013, Now trying out expansion/proto-typing boards).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, recent "Model B" with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure])

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

RPi VerifiedPeripherals

2013-01-24T18:48:25Z

TrevorGowen: /* Working USB Mouse Devices */ Added Dell 8K89 and two "Trust" wired mice

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

==Power Usage Notes==
{{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 Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75 V), 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.}}

'''Model B Hardware Revisions and USB Power limits'''
'''Hardware Revision 1.0'''
The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximatly 100 mA. USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA 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.

'''Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change'''
This had the polyfuses removed, removing the 100 mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012.

==Linux Driver Issues==
Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=12097&start=76] [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5249&start=44]
A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image.

== 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 the Raspberry 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 Raspberry Pi through their interconnect cable, due to the 100 mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).

===Working USB Hubs===
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''USB Version'''
| '''Number of Ports'''
| '''Power Rating*'''
| '''Powers Raspberry Pi'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|4-Port Ultra-Slim Desktop Hub
|F4U040
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|8-Port ExpressBus for iMac
|F5U010
|
|USB 2.0
|8-Port 7x"A" 1x"B"
|
|Verified
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U224
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|TetraHub™ USB 2.0 4-Port Hub
|F5U231
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U234
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|No backfeed, can power the RPi. Comes with a 2.4 A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''“Per Port Current Self-Powered Mode: 500mA (max)”''. However, I've attached a HD that requires 850 mA and it worked fine.

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237
|
|USB 2.0
|7-Port
|5 V - 3.8 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|MyEssentials 7-Port High-Speed USB 2.0 Hub
|F5U259-ME
|
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Lighted Hub
|F5U403
|
|USB 2.0
|4-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Lighted Hub
|F5U700
|
|USB 2.0
|7-Port
|
|Verified
|[http://www.amazon.com/gp/product/B000SDW84K]

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hub 2-en-1
|F5U706ea
|
|USB 2.0
|7-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237v1
|
|USB 2.0
|7-Port
|5 V - 2.5 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U040v
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U039qukAPL
|05e3:0608
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Benq
|
|E2220HD
|
|USB 2.0
|4-Port
|
|Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|BUFFALO
|4 Port Hub
|BSH4aAE06
|05e3:0608
|USB 2.0
|4-Port
|5 V
|Verified
|No Problem using Webcam & wifi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB

|- valign="top" align="left" style="background: #F5FAFF;"
|Cyberpower
|High-speed Hub
|CP-H720P
|0409:0050
|USB 2.0
|7-Port
|3.6 A
|Verified
|May Contain dual 05e3:0608 instead of 0409:0050

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2001FP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|SP2309W
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2407FWP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|U3011
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub - Card Reader Works - May work with SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|
|B/N61393
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|USB 2.0 External Hub 7 Port
|B/N87467
|
|USB 2.0
|7-Port
|5 V - 3.5 A
|Verified
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.

|- valign="top" align="left" style="background: #F5FAFF;"
|Deltaco
|
|UH-715 Rev 2
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|
|
|0409:0050
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|Dynex USB 2.0 7 Port Hub
|DX-HB7PT
|
|USB 2.0
|7-Port
|5.0 V / 2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|D-Link 7 Port USB Hub
|DUB-H7/B
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7 High Speed USB 2.0 7-Port Hub
|BUBH7A A5
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7
|EUBH7EB H/W Ver:B1
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-4 High Speed USB 2.0 4-Port Hub
|DUB-H4
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi

|- valign="top" align="left" style="background: #F5FAFF;"
|Digicom
|
|
|
|USB 2.0
|4-Port
|5 V - 2.0 A
|Not Verified
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]

|- valign="top" align="left" style="background: #F5FAFF;"
|ednet
|USB 2.0 7 port Hub
|85014
|
|2.0
|7-Port
|
|Not Verified
|Works with keyboard, mouse, audio devices

|- valign="top" align="left" style="background: #F5FAFF;"
|Medi@com
|USB 2.0 4 ports Hub
|M-HX30
|
|2.0
|4-port
|
|Verified
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]

|- valign="top" align="left" style="background: #F5FAFF;"
|mbeat
|13 Port USB Hub
|USB-M13HUB
|
|USB 2.0
|13-port
|5V - 3A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Monoprice
|Aquagate USB Hub
|5328
|
|2.0
|7-port
|2.0 A
|Verified
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
|Plata 4 port USB 2.0 hub
|18687
|
|2.0
|4-port
|1.0 A
|Not Verified
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.

|-
|}

'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.
</div>

*'''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 it is 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 Raspberry Pi, and additionally connect GND and +5 V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.

*'''Digitus'''
** 7-port USB2.0 Powered Hub. Model DA-70226.
*'''Eminent'''
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
* '''GearHead'''
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5 V, 1 A)
*'''Gembird'''
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.
* '''Genesys Logic (sold at Fry's)'''
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware and Belkin, same ID shows up in lsusb)
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, 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)
* '''König Electronic'''
** CMP-USB2HUB55 - 7 port USB2.0 HUB, (ID 1a40:0201 Terminus Technology Inc. Hub) 2.0 A power supply, backpowers Raspberry Pi well.
*'''Laser'''
** "7 port USB hub with AC adapter Version 2.0". 5 V 1 A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry 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, 2 A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!
*'''LogiLink'''
** UA0085 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0091 USB 3.0 Hub, 4-Port with PSU 5 V, 4 A. Connected with USB2.0 cable. 1 A 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 5 V, 3.5 A (Not suitable for powering Raspberry Pi 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 5 V, 2 A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.
* '''Macally'''
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000 mA wall-wart (US style)
* '''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 1000 mA wall-wart (US style)
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500 mA each) + (4 USB 3.0 Ports @900 mA each) Power Switches on each port, AC Powered and Includes a 5 V 4 A wall-wart (US style)
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5 V 1 A
** NLUSB2-222P 4 port USB 2.0 Hub with 5 V 2 A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])
*'''Nilox'''
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5 V 1.0 A
* '''Plugable'''
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5 V 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port.
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5 V 3 A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0].

* '''Pluscom'''
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3 A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.
*'''Satechi'''
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.
*'''Staples (Business Depot) (Bureau EN GROS)'''
** Staples 4-port hub Item 607477-CA
*'''StarTech.com'''
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5 V 2 A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).
*'''SumVision'''
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5 V 1.0 A (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 Raspberry 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 (1 A). Powering Raspberry Pi via microUSB from a hub port.
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]
*'''Sweex'''
** US014 4 Port USB 2.0 Hub
*'''Targus'''
** ACH81xx 7-port powered hub. 5 V 3 A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)
** ACH63EU 4-port. Using a 5 V 2 A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.
*'''The Pi Hut'''
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
*'''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 (5 V 2 A)
*'''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 (5 V 2.5 A) Powering Raspberry Pi from the 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 5 V, 3 A. USB ID 1a40:0201.
*'''VANTEC'''
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5 V 2 A AC/DC adapter. Go 2.0 Mini hub.
*'''Z-TEK'''
** Z-TEK 7-port powered hub with PSU 5 V, 4 A. 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, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5 V pinouts)
** F4U022 7-Port powered USB hub (powered 5 V, 2.6 A), 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. (Works always without powering the Raspberry Pi, haven't tried that)

*'''Dell'''
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.

*'''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.
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root filesystem from a USB drive.

*'''Dynamode'''
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1 A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification.

*'''D-Link'''
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)

*'''E-Solution'''
** 4-Port 2 A 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 with 1 A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry 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.
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.

*'''Hama'''
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi 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).

*'''iBall'''
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power suply.

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

*'''LogiLink'''
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.

*'''Soniq'''
** 4-Port 5 V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).

*'''Targus'''
** ACH115EU 7-port powered hub. 5 V 3 A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as 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. 1 A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi 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). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2 A 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 there are strange USB failures when X session started. High speed devices such as hard drives had failures.

== USB Remotes ==
* 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.

* [http://www.amazon.com/gp/product/B005DKZTMG/ref=oh_details_o02_s00_i00 Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070)] - keyboard and touchpad work. Have not verified multi-touch features.

* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4 GHz wireless keyboard and touchpad.

* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.

* [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], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]. Working perfectly, just plug & play.

* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6753651&CatId=3680# Exo Ultra U12-41310 Mini Keyboard] Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work.[https://github.com/thunderbirdtr/rs-pi-exo-keyboard Exo Installer script]

== 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, 20 mA.

* '''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, 100 mA (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''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))
** [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)

* '''Banbridge'''
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)

* '''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)
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5 V/100 mA, works directly

* '''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)

* '''CD Training'''
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]

* '''Cherry'''
** CyMotion Master Linux (B)
** RS 6000 USB ON
** G84-4100PTMUS (B) (Compact keyboard. Rated 100 mA. Works directly in Raspberry Pi)
** G85-23100DE-2 (B) (Rated 40 mA, tested with RPi powered by a 1000 mA power supply unit)
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.

* '''Compaq'''
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5 V 100 mA. Works directly connected to Raspberry Pi

* '''Das Keyboard'''
** Model S Professional Keyboard (Built in USB hub not tested) (B)
** Model S Ultimate Keyboard (Built in USB hub working) (B)

* '''Dell'''
** SK-8115 (B) (Rated 100 mA. Works directly in Raspberry Pi)
** L100 (B)
** RT7D40 (100 mA. Works directly in Raspberry Pi)
** RT7D50 (75 mA) (run "sudo dpkg-reconfigure keyboard-configuration")
** KB1421 (100 mA)
** KB2521 (100 mA)
** KB212-B (Works directly in Raspberry Pi, without powered hub)
** 1HF2Y (Works directly in Raspberry Pi)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Delux'''
** K8050

* '''Digicom'''
** WKEYPE01 Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

* '''Dynex'''
** DX_-WKBD (60 mA) (B)
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)

* '''EAPPLY'''
** EBO-013 Wireless 2.4 GHz compact keyboard with touchpad. Rated <40 mA works directly from Raspberry 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

* '''GE'''
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)

* '''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 >> also see Problem USB Keyboards
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)
** KB1500U (USB Mini Keyboard) (B)
** KB5150 (2.4 GHz wireless keyboard/mouse Combo) (B)
*** Works well with a powered hub

* '''Generic'''
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.

* '''Genius'''
** Ergomedia 700 (GK-04008/C) used without Hub
** KB-06XE (K639) (B)
** LuxeMate i200 (GK-090017; not tested with Hub)
** Slimstar 8000 wireless keyboard

* '''Gigabyte'''
** GK-KM7580 2.4 GHz Wireless Multimedia Keyboard & Mouse

* '''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.4 GHz 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.4 GHz 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 Raspberry Pi. Also works with Raspbmc with powered hub.
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub
** ACK-3700C
** ACK-340U+(DE)
** ACK-3400U (UK) mini keyboard
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi

* '''Labtec'''
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat 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.4 GHz 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.4 GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver

* '''Logitech'''
** Comfort Wave 450, labeled 100 mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine
** 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
** MK120 wired keyboard and mouse
** MK220 wireless keyboard and mouse
** MK250 wireless keyboard and mouse (no hub needed)
** MK260 wireless keyboard and mouse (no hub needed)
** 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]
** MK350 wireless keyboard (using Unifying receiver)
** MK520 wireless keyboard and mouse
** MK550 wireless keyboard and mouse (B)
** MX3200 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.
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]
** K120 Keyboard (B)
** K200 Keyboard (B)
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K350 Wireless Keyboard (B)
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". +1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.
** K520 Keyboard (B)
** K700 Wireless Keyboard with Touchpad and unifying receiver
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).
** 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 Raspberry Pi.
** 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.
** V470 Bluetooth Laser Mouse

''Keyboards and mice also together with Unifying receiver''

* '''macally'''
**macally iKey slim (IKEY5V2)

* '''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)
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5 V/100 mA (Wheezy 5-Sept-2012)

* '''Mikomi'''
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the 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)

* '''ONN'''
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.

* '''Ortek'''
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.

* '''Perixx'''
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

* '''Prodige'''
**Nanox Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]

* '''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]
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.
**RT-MWK01 mini wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

*'''Rosewill'''
** RK-200 Standard Keyboard

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.
** Expression Keyboard (US)
** Cyborg V.5 (B)

*'''SelecLine'''
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (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)

*'''SolidTek'''
** Solid Tek KB-P3100BU ASK-3100U.

*'''Sony'''
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5 V 1 A 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)

*'''The Pi Hut'''
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.

* '''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.4 GHz 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 Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5 V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry 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.0 V. 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 power away from the rest of the support system devices.

* '''A4 Tech'''
** Model GL-6 USB Keyboard, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''Accuratus'''
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100 mA). Tested with 1000 mA cheap unbranded and Nokia 1200 mA power adaptors.
* '''Apple'''
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub.
*'''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 <200 mA)
* '''Dell'''
** SK-8135 (B) (Rated 1.5 A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)
** SK-8115 causes kernel panic (rated 100 mA) Debian 6-19-04-2012 (B)
** Y-U0003-DEL5 Sticky / Non-responsive keys
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V
* '''Gear Head'''
** KB2300U - Causes kernel panic (B)
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)
* '''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/]
* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Jeway'''
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)
* '''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)
** MK 260 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)
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000 mA power supply unit)
* '''Novatech'''
** NOV-KEY2 - Causes kernel panic (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''PC World Essentials'''
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it 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).
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5 V 500 mA. (B)
* '''SIIG'''
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.
* '''Texet'''
** MB-768B standard keyboard (Rated 5 V 1.5 A (!), 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.
* '''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.
* '''Verbatim'''
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)
* '''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

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

* '''Apple'''
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).

* '''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)
** MG-0919 (wireless)

* '''Belkin'''
** F8E882-OPT (B)

* '''Cellink'''
** OPM-602 Small wireless optical mouse

* '''Cerulian Technology'''
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA

* '''Dell'''
** M-UVDEL1 (B)
** MOC5UO (100 mA)
** M056U0A (B)
** DZL-MS111-L (B) (100 mA)
** MS-111P (100 mA)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.

* '''Dynex'''
** DX-WMSE (100 mA) (B)

* '''Fellowes'''
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (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.4 GHz 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)

* '''Kensington'''
** Kensington Expert Mouse Trackball K64325
** Kensington Expert Mouse "Slimblade" K72327US

* '''Labtec'''
** Corded Laser Glow Mouse 1600, rated 5 V 100 mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)

* '''Lenovo'''
** Wired Optical Mouse Model: MO28UOL

* '''Logik'''
** Wired Optical Glow Mouse Model: LGGMO10. (B)

* '''Logitech'''
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)
** B105 Mouse for Laptops (OEM)
** 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)
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).
** 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 5 V 100 mA. Works fb on model B with Raspbian Wheezy

* '''Microsoft'''
** Comfort Curve Mouse 3000 for Business
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).
** 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 1000
** 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)

* '''Perixx'''
** PERIMICE-210 U Red (Part No.R1J)

* '''Razer'''
** Boomslang Collectors Edition 2007 (B)

* '''Rosewill'''
** Rosewill RM-C2U

* '''Saitek'''
** Notebook Optical Mouse (PM46)

* '''Samsung'''
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50 mA)

* '''Sun microsystems'''
** Model: FID-638 , SunPN: 371-0788-01

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]

* '''Swiftpoint'''
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.

* '''Targus'''
** AKM02UK (Associated keyboard not checked)
** AMU2701EUK (B)

* '''Technika'''
** TKOPTM2 (B)
**TKD-211
**TKNM110

* '''Tesco'''
** Wired optical mouse M211 (B)

*'''The Pi Hut'''
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Model 15313 - large, 5-button wirless mouse
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087
** Fachi and a "Car" Mouse. Both wired mice, reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.

* '''Verbatiam'''
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)

* '''Xenta'''
** MOW0810 (B)
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Generic'''
** Generic 2.4 GHz 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
* '''A4Tech'''
** Model G7-630 Wireless Mouse, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''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 1000 Hz out of the box, whereas the 518 is only 125 Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.

* '''Microsoft'''
** Microsoft Touch Mouse - Does not see right clicks, Only left.
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.

* '''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 Real Time Clocks ==
*Cymbet
** Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)
Device information at http://www.cymbet.com/pdfs/DS-72-22.pdf
Code to access the RTC from Linux: https://github.com/owendelong/Cymbet-RTC
Does not require a powered hub.

== USB Wi-Fi 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 Wi-Fi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but it has not yet been tried.

'''Note:''' A Wi-Fi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the Wi-Fi adapter to the Wi-Fi Access Point. Therefore, you may need to plug the Wi-Fi 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 Raspberry Pi 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."
** It works without additional software connected directly to a Rev 2 Raspberry Pi, but it stops working after a period of time (3 to 4 hours) with a fully updated Wheezy and all the 'USB workarounds' [http://elinux.org/Rpi_USB_check-list] in place.

* '''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). Tested on Raspbian too (drivers from aircrack-ng).
** AWUS036H (500 mW version): Tested on Raspbian (drivers from aircrack-ng).
** AWUS036H (1 W version): Tested on Raspbian (drivers from aircrack-ng). Needs USB powered HUB or Rev2 of the board / polyfuse bypass.
** AWUS036NHA: Tested on Raspbian (drivers from aircrack-ng). Works fine if connected after boot, otherwise Raspberry Pi won't boot up.

* '''AirLink101''' [[File:Airlink101.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-airlink101|100px|Airlink 101 Wireless N 150 Ultra Mini-USB Adapter]]
** 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.
** AWLL5099: Tested on Raspian Wheezy. [http://www.savagehomeautomation.com/raspi-airlink101 Step-by-step installation and configuration instructions] with screenshots can be found [http://www.savagehomeautomation.com/raspi-airlink101 here]. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** [http://www.airlink101.com/products/awll6075.php AWLL6075]: Tested on Raspian Wheezy 16-Dec-2012 build and distro upgrade as of 09-Jan-2013. lsusb reports: 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter. Driver installed is r8712u. Powers OK from Model B Pi (Rev 000f) USB port (1200mA supply tested). Dongle does get hot under use when directly connected to USB port (slightly reduced when USB extender cable used).

* '''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 repository (B) (not needed with latest Raspbian “Wheezy” 2012-07-15: this Asus works N10 out of the box) Does not support nl80211 APIS, so hostapd won't work.
** [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 it will not function.
** WL-167G v3 USB ID 0b05:1791, working out-of-the-box on Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17. Does not require powered hub.

* '''AusPi Technologies'''
** AusPi Wireless Adapter [Realtek RTL8188S]. Works without a powered HUB. Tested on OpenELEC (works OOB), RaspBMC (works OOB), XBian (works OOB) and 2012-08-08 Raspbian Wheezy (works OOB). Distributed in Australia by [http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/ Buy Raspberry Pi Australia].

* '''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 '''Powered hub required!'''
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Works on RaspBMC OOB (with NetworkManager plugin). Works WITHOUT powered hub on 5 V 800 mA power with 6 overvolt (nothing else connected to USB)
** 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 repository (B). Verified working with 2012-12-16-wheezy-raspbian right out of the box.
**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. Tested and working on Rasbian Wheezy (and RaspBMC), driver RTL8192CU, no powered hub needed (dongle directly attached to the onboard ports)
** Belkin Components F9L1001v1 "N150" Wireless USB Adapter. Tested and working on Rasbian Wheezy WITHOUT powered hub.
** Belkin Surf Micro WLAN USB-Adapter (Raspbian Wheezy, unpowered hub, "N150")

* '''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
** USB ID: WLI-UC-G300N - Works on Raspbmc out of the box. Tested after a factory reset of the Raspbmc.

* '''Comfast'''
** WU710N: chipset RTL8188CUS. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** WU810N (150M): Works out of the box on wheezy raspbian of version 2012-12-16.

* '''Conceptronic'''
** C300RU. Works out of the box in Raspbian. Causes reboot when plugging on a live Rev. 2 Raspberry Pi

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

* '''DealExtreme'''
** ISG-1507N Mini USB 2.4GHz 150Mbps 802.11b/g/n WiFi. Has the ralink 5370 chipset, works directly plugged into the Raspberry Pi rev.1 under OpenELEC. Note: Driver (rt2800usb) only permits B/G operation and throughput is low (10Mbit).

* '''DELL'''
** Wireless 1450 [Intersil ISL3887]. Works out of the box, but it requires a powered hub (the Raspberry Pi boots with this dongle plugged in, recognizes and configures it, works for some time, but then it crashes randomly under heavy traffic. A powered hub seems to fix the issue).

* '''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-121 (Version A1). Wireless N 150 Pico. Works out-of-the-box with Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)
** DWA-123 (Version A1). USB ID 2001:3c17, Ralink RT2800. Working out-of-the-box on Arch image from 2012-04-29. (working without UBS Hub - not yet sure if it achieves full speed though.)
** 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]
** WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.

* '''Edimax''' [[File:Edimax-ew-7811un.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-edimax-ew-7811un|100px|Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter]]
** [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]. Note: With current Raspbian (2012-09-18-Wheezy) it is recognized immediately, the default module works fine; the configuration is easy using wireless-essid and wireless-key in /etc/network/interfaces.
*** The EW-7811Un can be powered directly from the Raspberry Pi if the Raspberry Pi is powered using a well regulated power supply.
*** EW-7811Un [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un step-by-step installation and configuration instructions] for Debian & Raspian with screenshots can be found here: [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un here]
*** 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 Raspberry Pi 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]]
*** EW-7811Un[USB ID 7392:7811](Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Worked right out of the box - only needed to configure WPA.
(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.
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=261&pl1_id=1&pl2_id=44 EW-7711UAn], Ralink RT2870, works perfectly on Arch with a powered hub (not tested without yet). Simply required wireless_tools and wpa_supplicant, the drivers/firmware are included in kernel 3.0. I followed the Arch [https://wiki.archlinux.org/index.php/Wireless_Setup Wireless Setup] instructions.

* '''edup'''
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS Wi-Fi 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://dx.com/p/ultra-mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network-adapter-48166?item=1&Utm_rid=24958662&Utm_source=affiliate Ultra-Mini Nano USB 2.0 802.11n 150 Mbit/s Wi-Fi/WLAN Wireless Network Adapter] USB ID: ID 0bda:8176 Works stable when using VLC for internet radio receiver. Works stable 24/7 on two of my Raspberries used as webserver. Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian. Seems to be the same as EW-7811Un using the RTL8188CUS chipset.

** [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 Raspberry Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or recieved the audio get disorted. Use script from [http://dl.dropbox.com/u/80256631/install-wheezy-beta-rtl8188cus-20120619.sh here] for Wheezy.

* '''Eminent'''
** EM4575 - rt2800usb driver.

* '''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 repository. No need to download firmware when using Debian Wheezy (B)

* '''ISY'''
** USB Wireless Micro Adapter IWL 2000, tested on Raspbian; follow [http://daniel-lnx.blogspot.nl/2013/01/raspberry-pi-and-isy-usb-wireless-micro.html these] instructions.

* '''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 it 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]
** Linksys WUSB54GC (manufactured 07/2008) No issues! needs powered hub on version 1.0 boards.

* '''LogiLink'''
** Wireless LAN USB 2.0 Nano Adapter 802.11n LogiLink [http://www.logilink.eu/showproduct/WL0084B.htm] is working even USB powered.

* '''Lutec'''
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.

* '''Micronet'''
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into Raspberry 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 Wi-Fi 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>

* '''Mvix'''
** Mvix Nubbin (MS-811N): works out of the box on Raspbian "Wheezy" and does not need a powered USB hub.

* '''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. Seems to draw a lot of power; e.g. I can't power this and a USB thumb drive simultaneously.
** WG111v3: Realtek RTL8187B chipset. Works straight out of the box using a powered USB hub.
** WNA1000M works with Raspberry Pi Model B Board v. BS1233.However when downloading torrents, when torrent pick up speed system become unresponsive.

* '''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 Wi-Fi 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.
** RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.
** [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). An image of an adapter with this chip can be found [http://i.imgur.com/wRF7L.jpg here].

* '''Rosewill'''
** RNX-N180UBE Wireless B/G/N Adapter
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172
*** Tested in Arch, works out of box. Powered USB hub required.
*** Tested in Raspbian, used wicd to configure network settings. Powered USB hub Required.
*** Tested in Raspbmc. Needs package firmware - Realtek and used wicd-curses to configure. Powered 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.
** RNX-MiniN1 (RWLD-110001) Wireless-N 2.0 Dongle (Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter)
*** Tested in Raspbian, powered from USB hub.

* '''Sabrent'''
** USB-A11N: Mini USB 2.0 Wireless-N WiFi Network Adapter: USB ID 0bda:8176, works automatically in Raspbian using rtl8192cu driver along with Logitech BT mini-receiver (keyboard/mousepad) without external hub using 5.25V 1 A psu (4.99V T1/T2) on rev 2.0 (B)

* '''Sagem'''
** Sagem Wireless USB stick XG-760N: USB ID 079b:0062, Module is not shipped in Debian image, but it 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/

* '''Sitecom'''
** Sitecom Wi-Fi USB Adapter N300: USB ID 0a5c:5800, Realtek r8712u driver + firmware Realtek. Module available in shipped Raspbian image. '''NOTE:''' although this dongle will also work without powered hub, if there is a voltage problem (either on the Raspberry or on the hub, but verified only on the hub so far) this wifi dongle will receive signal perfectly (RX), but not be capable of sending anything (TX) and the MAC address will be permanently set to FF:FF:FF:FF:FF:FF (this is indicative that there is not enough power) [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]

* '''SL'''
** SL-1507N: USB 802.11n 150M Wi-Fi Wireless LAN Network Card Adapter SL-1507N Black
*** I bought this on on eBay for $4.19 (free shipping) @ http://www.ebay.com/itm/270853614804?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649#ht_4379wt_1199
*** It worked out of the box on Raspbmc RC4, with the network manager add-on; seems to be an rt2800usb
*** dmesg output "usbcore: registered new interface driver rt2800usb"

* '''SMC'''
** SMCWUSBS-N: Hardware detected as rt2800, but it is 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.

* '''Sony'''
** Sony UWA-BR100 802.11abgn Wireless Adapter [Atheros AR7010+AR9280] (Vendor ID: 0411, Product ID: 017f) - Tested with Raspbian. Needs package firmware-atheros.(B)

* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
** Tenda W311MI Wireless N Pico USB Adapter (identified as Ralink RT5370 Wireless Adapter; USB-ID: 148f:5370) - Works out-of-the-box for Raspian 2012/09/18 or later. An earlier version gave me problems.
** 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]
** Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.

*'''The Pi Hut'''
** USB 802.11n Wi-Fi adapter (from [http://thepihut.com/products/usb-wifi-adapter-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''TP-Link'''
** TL-WN321G (Ralink RT2501/RT2573, rt73_usb) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v? (Atheros AR9271, ath9k_htc) Works out of the box when plugged in before boot. Plugging in after boot only with powered USB hub. RasPi Model B, Rev. 2.0
** TL-WN422G v2 (ath9k_htc) Works OOTB in Debian Wheezy Beta. Runs without powered Hub when plugged into running Raspberry Pi, but the Raspberry Pi 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) | works OOTB with Wheezy Raspbian (2012-08-16) connected directly to raspberry pi (B) and AP functionality tested with hostapd.
** 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-WN723N (RTL8188SU); works OOTB with Raspbian 2012-09-17, (B) stable with 1 A PSU and without powered USB hub on r2.0.
** TL-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub.
** TL-WN821N v3 (ath9k_htc, htc_7010.fw); works out of the box on ArchLinuxARM, Wheezy and on OpenElec (>r11211), Problems with prior OpenElec; needs powered USB Hub (B). This chipset is also compatible with hostapd (wireless AP software)
** TL-WN823N Works out of box on Raspian using powered USB Hub

* '''Trendnet'''
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-648UBM TEW-648UBM] USB ID: 20f4:648b, works OOTB with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/ Adafruit Occidentials Raspbian Wheezy variant] as it includes kernel with [http://www.wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model%3A%3ARTL8188CUS%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols%0D%0A%3FMIMO+status%0D%0A%3FOUI%0D%0A&sort_num=&order_num=ASC&eq=yes&p%5Bformat%5D=broadtable&p%5Blimit%5D=500&p%5Bsort%5D=&p%5Boffset%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Blink%5D=all&p%5Bsearchlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&eq=yes RTL8188CUS driver built-in] (B)
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-649UB TEW-649UB] Works with OpenElec 3.0, chipset Realtek RTL8191SU

* '''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)
** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package

===Problem USB Wi-Fi 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.

* '''Alfa'''
** AWUS036NHA (Vendor ID: 0cf3, Product ID: 9271) - Tested with Raspbian. Works fine if connected after boot. Kills boot process if previously attached. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=16809&p=169469#p169469 Details here.]

* '''EDIMAX'''
** EW-7811Un (Vendor ID: 7397, Product ID: 7811) - Reports as containing the Realtek RTL8188CUS chipset listed below, no lockup or kernal oops under Wheezy, but dmesg reports constant timeouts trying to initialize the module. This appears to be resolved on 2012-09-18-Wheezy-raspbian and newer versions.

* '''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.
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].

== USB Bluetooth adapters ==
===Working Bluetooth adapters===
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.
* 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 Adapter 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
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
** http://www.element14.com/community/message/58288
* IOGear GBU321 (Broadcom BCM2045 Chipset)
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
* Trust BT-2400p
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).

===Working Bluetooth/Wifi Combo adapters===
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>

===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. Raspberry 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.
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.
* Asus USB-BT211
** Shows up as HCI device in Raspbian, but it does not scan or pair.
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962

== USB Ethernet adapters ==
===Working Ethernet adapters===
* '''AVM'''
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.
* '''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.
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
* '''Apple'''
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.
* '''Edimax'''
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.
* '''D-Link'''
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)
* '''Sabrent'''
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)
* '''Sitecom'''
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.
* '''A-Link'''
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.

The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190 mA, so there might be stability issues if additional power is not provided.
* '''Hama'''
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.

===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. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out

== 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> . If you are not user ''pi'' you may need to add your username to the ''audio'' group thus: <code>sudo adduser yourusername audio</code> (user ''pi'' usually belongs to this group anyway).

* '''Creative'''
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]
* '''Daffodil'''
** [http://www.amazon.co.uk/gp/product/B002FI7GWK/ref=oh_details_o03_s00_i00 USB Sound Adapter US01]. Tested with low-cost headphone/microphone set via ''audacity'' (See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/DaffodilUSBSoundAdapter.html CPM-Spectre-Pi...DaffodilUSBSoundAdapter]).
* '''Edirol'''
** [http://www.roland.com/products/en/UA-1A/ UA-1A]
* '''Hercules'''
** [http://www.hercules.com/fr/Cartes-Son/bdd/p/123/gamesurround-muse-xl-pocket-lt3/ Gamesurround Muse XL (Pocket LT3)]
* '''Logilink'''
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]
* '''Logitech'''
** [http://www.amazon.com/Logitech-Wireless-Gaming-Headset-Surround/dp/B003VANOFY/ref=sr_1_1?ie=UTF8&qid=1358114107&sr=8-1&keywords=g930 Logitech G930 Wireless Gaming Headset with 7.1 Surround Sound] (stereo works with ALSA, have not tried 7.1 Surround Sound)
* '''NuForce uDAC-2'''
** [http://www.nuforce.com/hp/products/iconudac2/index.php NuForce uDAC-2 Headphone Amplifier and USB DAC]
* '''Plantronics'''
** [http://www.ebay.com/itm/Genuine-New-Plantronics-External-USB-Audio-Soundcard-New-Sealed-/300845395889?pt=US_Sound_Card_External&hash=item460bc86fb1 Plantronics Stereo USB Adapter -01] (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter)
* '''Terratec'''
** [http://www.terratec.net/fr/produkte/Aureon_Dual_USB_12339.html Aureon Dual USB] (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers)
* '''Texas Instruments PCM2704'''
** [http://www.ti.com/product/pcm2704 PCM2704 98 dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]

==USB 3G Dongles==
* Huawei E173
* Huawei E220
* Huawei E160 (AT commands only)
* 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 Raspberry 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].
*Sundtek
**Sundtek MediaTV Digital Home
**Sundtek MediaTV Pro
**Sundtek SkyTV Ultimate
**[http://shop.sundtek.de DVB-C, DVB-T, DVB-S/S2]: digital TV works, streaming to Windows / Linux is no problem. Easy installation [http://support.sundtek.com/index.php/topic,4.0.html English]
*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.
** Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer)
** Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian)
*K-World
** K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick. IR and supplied remote work with XBMC.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Raspberry Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Raspberry Pi itself. Tested with Astra 19.2E radio and SD-TV channels
*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 was detected, but it is not tested.
** [http://obrazki.elektroda.pl/8081115000_1317678968.jpg HDTV USB DVB-T] dongle, based on IT9135. This tuner comes in two revisions. Revision is printed on PCB.
*** rev. 1.0; should work with 3.2+ kernel, need confirmation.
*** rev. 2.0; works with kernel 3.6.11, without a powered hub. This tuner also requires a firmware (dvb-usb-it9135-02.fw) which can be downloaded from [http://logout.hu/bejegyzes/azbest/usb_dvb-t_tuner_it9135_rev2/hsz_1-50.html this page]. It's in Hungarian, so google translate or equivalent is recommended. The remote also works. According to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=29141 this post], there may be issues on some software configurations when using ''omxplayer''.

== USB Webcams ==

This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!

<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''Verified OS'''
| '''Verified OS version'''
| '''Verified Resolution'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F6D2CF;"
|Canyon
|
|CNR-WCAM820
|
| raspbian/wheezy
|
| 1280x1024
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Live!
| VF0470
|
| ArchLinux
|
|
| works out of the box on ArchLinux

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Socialize HD
| VF0610
|041e:4080
| raspbian/wheezy
| 2012-11-26
| 960x544
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Vista IM
| VF0640
|
| raspbian/wheezy
|
|
| works on Raspbian at 320x240 resolution, 15fps

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Webcam Notebook
| PD1170
|
|
|
|
| Detects, untested.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Webcam Pro
| PD1030
|
|
|
|
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")

|- valign="top" align="left" style="background: #F5FAFF;"
|HP
|WebcamHD-2200
| HD-2200
|
|
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|HP
|Webcam HP-3100
|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

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C100
| V-U0013
|
| raspbian/wheezy
| 2012-08-16
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C200
|
| 046d:0802
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C270
|
|
|
|
|
| With external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C310
|
|
|
|
|
| Does not require a powered hub to capture snapshots

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C510
|
|
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C525
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C615
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C905
|
|046d:080a
|occidentalis
|v0.2
|1600x1200
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C910
|
|
|
|
|
| With external power, is uncvideo

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C920
|
|
| raspbian/wheezy
|
|
| With powered hub, detected out of box as Video0 V4L device

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Orbit/Sphere
|
|
|
|
|
| Works with external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro 9000
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 4000
|
|
|
|
|
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 9000
|
| 046d:0809
| Arch Linux
|
|
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).

|- valign="top" align="left" style="background: #F5FAFF;"
|Medion
|
| MD86511
|
| raspbian/wheezy
| 2012-07-15
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Mexxcom
|
| M-104
|
| raspbian/wheezy
| 2012-12-16
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam Cinemap 720p USB HD Webcam
| H5D-00001
|
| raspbian/wheezy
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam HD-5000
|
|
|
|
|
| Picture breaks up at the bottom

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam HD-6000
|
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| VX-7000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-3000
|
| raspbian/wheezy
|
|
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-800
|
| raspbian/wheezy
|
| 352x288
| Doesn't work at full resolution

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam Studio/Cinema
|
|
|
|
|
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|Xbox Live Vision
|
| 045e:0294
| Arch Linux
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Silicon Motion
| SM731 Camera
|
| 090c:71b3
| Raspbian Wheezy
|
|
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS3
|
|
|
|
|
| The occasional frame is corrupted/stutters when running at 640x480

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
|
|
|
|
|
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
| SLEH 00030
|
| Arch Linux
|
|
| (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 Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012

|- valign="top" align="left" style="background: #F6D2CF;"
|T'nB
| Minipix 100K pixels
| IMWB032992
| 1e4e:0100
| raspbian/wheezy
| 2012-12-16
|
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
| 2 MP Auto Focus Webcam
|
|
| Arch Linux
|
|
| works out of the box

|- valign="top" align="left" style="background: #F6D2CF;"
|Trust
| SPACEC@M 200
|
|
| Arch Linux
|
|
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012

|-
|}

== USB GPS devices ==

*Columbus
** Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients)
*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: It works, but it may draw too 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 Raspberry Pi. 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 and USB to Serial (RS-232) adapters ==
A 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.

===Working USB to Serial Adapters===
*'''FTDI'''
**FT232 chip based adapters works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio.

** FT2232D dual RS232/FIFO works (used in various JTAG devices)

*'''Prolific'''
**PL2303 chip based adaptors works fine on latest Debian tested with ''minicom'' and ''gtkterm''

A USB to Serial (RS-232) adapter is used the other way around, ie. the USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment.

*"Best Connectivity" (Possibly also sold under the "Newlink HQ" or "Kenable HQ" labels)
**FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by ''lsusb'' as <code>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</code>. Appears as <code>/dev/ttyUSB0</code>, and requires the user to be a member of the ''dialout'' group (which ''pi'' is for ''Raspbian Wheezy''). Initially tested using an old RS Datalinker setup in "loopback" mode via ''microcom'' upto 9600 baud, and ''gtkterm'' after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently ''gtkterm'' was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

===Problem USB to Serial Adapters===
'''HL-340'''
*CH340 Chipset - '''Currently not supported by RPi''' but there is a patch of kernel code [http://tiagovaz.wordpress.com/2008/01/04/using-a-hl-340-usb-serial-adapter-against-2623-linux-kernel/ here], but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work.

== Other, exotic USB devices ==
=== USB to Parallel Port/Printer Adapters ===
*'''Prolific'''
**PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under [[RPi_Distributions#RISC_OS| RISC OS Raspberry Pi]] with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBtoParPrntAdapter.html CPM-Spectre-Pi...USBtoParPrntAdapter] for more info. and also a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/WheezyCUPS.html CUPS/Wheezy installation guide])

=== USB to SATA ===
*'''Nippon Labs'''
** 2.5" SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi. Built-in "Y" power adapter. Does work direct on some ver2.0 boards if used with 5.25 power supply, or Y adapter

=== 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 5 V at 0.5 A 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 it is 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 Raspberry Pi.
**Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168
=== USB RFID Reader ===
*Unbranded 125 kHz EM4100 RFID reader from eBay sellers (< £7), the one with a Windows logo on (easily scratches off for Linux users).
**Initially would not work when plugged in directly to Raspberry Pi. Worked when connected via an unpowered Trust hub. Worked after Raspberry Pi was modified with 10K resistors over the USB polyfuses (warranty invalidated). Probably would work fine with powered hub.
**Sends a 10 digit string to current window or console as if it was a keyboard. Can be captured independently of keyboard using Linux event interface (/dev/input), but the kernel in current distributions does not have CONFIG_INPUT_EVDEV selected so kernel rebuild is necessary.
=== JTAG ===
* FTDI2232D dual RS232/FIFO based JTAG (e.g. SheevaPlug JTAGKey USB-ID 9e88:9e8f)
** works using the Raspberry Pi as a development host
=== USB 3.0 Multi-Card Reader ===
* US Robotics All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously
** SD/MMC + MS/MS PRO or DUO/DUO PRO + CF/MD + SM + SD/MMC or MS/MS PRO. Useful for backing up cards containing other OS Distros

== 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 additional 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 it 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 5 V. 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===
* '''Adafruit'''
** 5.25 V 1 A Model 501 (Newark 44W4932) USB 110-240 VAC power supply [4.99-5.01 V @ T1/T2 with 100 mA BT and/or mini wireless-n on RPi USB ports]
* '''AlcaPower'''
** 5 V 2.5 A Model AP5A - Charger/switching with 7 connectors(also Microusb)
* '''Ansmann'''
*** Dual USB charger slim, Model-Nr. 1201-0001
* '''Apple'''
Note that apple designs its charger products to work optimally as '''chargers''', in practice this means that apple chargers drop their output voltages somewhat with output current, so that the charging circuits do not need to dissipate more heat than is strictly necessary. Because of this, and although many people have reported apple products to power their basic PI setup reliably, its still not an optimal choice for a PI system that uses power hungry USB devices. Also, because of the popularity and high price of these chargers there are many very sub standard, but almost impossible to recognize as fake copies on the market, and some of these fakes are about the worst things you can try to power your PI with! Not only do they not work, they may actually be dangerous to use!
** 5 V 2.1 A USB charger for iPad2, model A1357
** 5 V 1.0 A USB Charger for iPod
** 5 V 1.0 A USB Charger for iPhone 4
* '''Amazon'''
** 5 V 0.85 A USB charger for Kindle
** 5 V 2 A Mains to USB A adaptor, Branded "CostMad"
* '''Asus'''
** 5 V 2.0 A USB charger for Google Nexus 7
* '''Bandridge'''
** 5 V 1.0 A Mobile Phone Charger (Model: BPC3102EC)
* '''Belkin'''
** 5 V 2.6 A 4 port Ultra-Slim Desktop hub (Model F4U040) (Raspberry Pi running from USB hub port)
** 5 V 2.5 A 4 port USB Hub (Model F5U404) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB 2.0 Mobile Powered Hub (Model F4U018) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB Hub (Model F5U706) (Raspberry Pi running from USB hub port)
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)
** Universal USB Wall Charger (5 V 1 A) (Model F8Z222uk)
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** Charger for Tour 9630
** 5 V 0.7 A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
** 5 V 750 mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)
** 5 V 750 mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)
** 5 V 2 A Model PSAC10R-050QT, RIM Part Number HDW-34725-001
** 5 V 550 mA curve 8520 charger works with raspberry pi Model B Board v. BS1233. It does not work with Raspbmc image.Symtoms are frequent key board and external hdd disconnects.
* '''Deal Extreme'''
** [http://dx.com/p/5v-2a-regulated-switching-power-supply-110-220v-94518 S-10-5 5 V 2 A Regulated Switching Power Supply (110~220 V)] (DIY: requires additional micro-USB connector and wiring)
* '''Dell'''
** USB Hub integrated in Dell monitors (B)
* '''The FX Factory'''
** 5 V 1 A (1.2 A max) AC Travel Charger Model KJ-USB Mains. Typically provides 4.9 V at 1 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>
* '''Garmin'''
** 5 V 1 A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6 ft cable (F3U151B06) works.
* '''Globe Electric'''
** 2-Outlet Tap with Surge Protection and 2 USB Chargers ([http://globe-electric.com/product/2-outlet-tap-with-surge-protection-and-2-usb-chargers-grounded-white/ 46082]). Rated at 1000 mA. 120 V systems only.
* '''Griffin'''
** Power Block Model P2417. 5 V 2.1 A
** Power Block Model P1190R2 Two USB 5 V Outputs, 1 A each
* '''Hama'''
** 1000 mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)
* '''Hartig + Heiling GmbH & Co. KG'''
** H+H SN 6 USB
* '''HP'''
** 5.3 V 2 A Charger for HP Touchpad (B)
* '''HTC'''
** 5 V 1 A TCP-300 USB phone charger (B)
** 5 V 1 A TC B250 USB charger (HTC R/N: 79H00096-00M)
** 5 V 1 A TC E250 USB charger (HTC R/N: 79H00098-02M)
* '''i-box (Philex Electronic Ltd)'''
** 5 V 1 A 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'''
**15 W Dual USB Adapter. Model: mMini AC15. Output: 5 V, 3 A (max per port), 15 W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Specification sheet]
* '''Kodak'''
** 5 V 1 A TESA5G1-0501200
** 5 V 1.0 A K20-AM
* '''LG'''
** 4.8 V 1 A Travel Adapter
** 5.1 V 0.7 A Travel Adapter (Model: STA-U34WVI)
** 5.1 V 0.7 A Travel Adapter (Model: STA-U12ER)
* '''Logic'''
** 4 port USB Hub (Model LP4HUB10). (Raspberry Pi running from USB Hub port, red power line (+5 V) inside hub cut) (B)
*'''LogiLink'''
**5 V 2.1 A Switching power supply, model PA0040 (B)
* '''Logitech'''
** 5 V 1 A SDC115-USB Remote Control Charger and cable
* '''Maplin Electronics'''
** 5 V 1 A dual USB power supply, model number H25B-MT-K2
** Micro USB Power Supply N19HX
* '''Medion'''
** 5 V 1 A USB power supply for OYO ebook reader
* '''Microsoft'''
*** Zune Zune AC Adapter v2
* '''Motorola'''
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5 V 0.85 A SPN5504 Charger with Cable]
* '''Noname'''
** 5 V 2.1 A 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.2 V 1 A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]
** 5 V 1 A Model H-IP008 Serial No. H10T80L068
* '''Novatel Wireless'''
** 5 V 1.05 A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5 V 0.7 A Charger for Orange San Francisco
* '''Palm'''
** 5 V 1 A Charger for Palm Pixi+ (B)
* '''Pantech'''
** 5.0 V 1 A CNR USB with LG DLC100 micro USB cable
* '''Petzl'''
** 5.0 V 1 A Charger that came with the Tikka core2 XP
* '''Phihong'''
** Switching Power Supply. Model: PSAC09R-050. Output: 5 V, 1.8 A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
* '''PortaPow'''
** PortaPow UK Mains Wall Power Supply
* '''PowerGen'''
** PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. [http://www.amazon.com/gp/product/B0073FCPSK Amazon Link]
* '''Rayovac'''
** Universal USB Charger Model: PS69 100-240 VAC to 5 V 1 A (small cube w/folding plug) works w/wireless keyboard/mouse and mini-Wifi connected
* '''RS Components'
** HNP06UK (RS 7263069) Switching Adapter 5.0 V 1200 mA
* '''Samsung'''
** 5 V 0.7 A Charger for Galaxy S model ETA0U10EBE
** 5 V 0.7 A Charger for Galaxy SII
** 5 V 1 A Charger for Galaxy SIII
** 5 V 1 A Charger for Galaxy Nexus
** 5 V 0.7 A Charger for Galaxy S Vibrant (SGH-T959)
** 5 V 0.7 A Travel Adapter model ATADU10EBE
** 5 V 1 A? Samsung C Series TV USB-port for external HDDs. Running stable with openelec
** 5 V ?A (Unknown) Samsung Service Port (USB) on LN32A330J1DXZA 720p 32 inch HDTV
** 5 V Unknown Ampere Samsung UA22D5000 & UA32D5000 TV USB Port. Test with Raspbian Wheezy, Raspbmc, and RPITC
* '''Shun Shing'''
** 100-240 VAC to 5 VDC 1 A USB power supply, model SP5Q-AU [http://jaycar.co.nz/productView.asp?ID=MP3455 Jaycar]
* '''Sony Ericsson'''
** 5 V 0.7 A Charger CST-80
** 5 V 0.85 A Greenheart Charger EP800. Typically provides 4.8 V at 0.85 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>.
* '''StarTech'''
** 4 Port USB 2.0 Hub Raspberry Pi can be powered just by plugging USB input into the Raspberry Pi, don't need power in micro USB port.
* '''Travel Charger'''
** 5 V 2.0 A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]
* '''Technika'''
** 5 V 1 A USB Power Adapter, model MPASS01 (B)
* '''The Pi Hut'''
** Micro USB Power Supply for the Raspberry Pi. 5 V 1000 mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])
* '''Trisonic'''
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5 V, 800 mA) $3 at Daiso U.S. stores.
* '''TruePower'''
** [http://u-socket.com/ U-Socket] 5 V 2.1 A AC Receptacle with Built-in USB ports (2.1 A 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===
* '''Nokia'''
** 5 V 1.2 A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2
** [http://accessories.nokia.com/products/nokia-fast-usb-charger-ac-16/ 5 V 1 A AC-16E Charger] Provides only 4.7V across TP1 & TP2 when at idle

* '''Masterplug'''
** Masterplug Surge Protected USB Adaptor 2 x 1 A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artefacts using HDMI.
* '''Monoprice'''
** 5 V, 2 A 3 Outlet Power Surge Protector Wall Tap with 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot. Measured to less than 4.75 V between TP1 and TP2 when used with a Monoprice cable.
* '''Sony Ericsson'''
** 5 V, 850 mA EP800. Some failures to boot, Ethernet loops at boot.

===Working external Battery packs (with 5 V regulated output)===
* '''Anker Astro3'''
** Anker Astro3 10000 mAh with dual 2 A USB output
* '''Duracell'''
** PPS2 Instant USB Charger
* '''Energizer/XPAL'''
** XP18000 18000 mAh Power Pack
* '''Generic - eBay no brand'''
** 6000T Pocket Power 5000 mAh - eBay item 271009959140
** Power Bank for iPad/iPhone 5000 mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938
* '''Mophie'''
** 38113BBR Juice Pack Powerstation 4000 mAh: output 2.1 A max: included charging cable powers RPi, 7.5 hrs light use w/keyboard and mini-Wifi on RPi ports
* '''New Trent'''
** iCurve IMP70D 7000 mAh (Approx 12 hours from full charge)
** IMP120D 12000 mAh
* '''Sinoele'''
** Movpower - Power Bank 5200 mAh (8 hours with Wi-Fi active)
* '''TeckNet'''
** iEP387 Dual-Port 7000 mAh External Power Bank (The charging lead can be used to connect the Tecknet to the Raspberry Pi. Ran the Raspberry Pi with Wi-Fi dongle and wireless keyboard receiver for over 9 hours of light use.)
** iEP392 Dual-Port 12000 mAh External Power Bank (1 A port, ~16.5 hours)
** Rayovac PS60 5 V 800 mAh
* '''VINZO'''
** Power Bank 5000 mAh Grey Output 5 V 1000 mA
* '''Kodak Power Pack KP1000'''
** 1 A USB rechargeable battery pack - see [http://blog.sheasilverman.com/2012/09/its-alive/ Shea Silverman's blog]

== 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 Raspberry Pi's primary input fuse. HDMI ports (and the raspberry PI) are designed so that they deliver a very limited amount of power (50 mA) 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 200 mA, 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 non externally powered devices. If you have bought a non externally powered HDMI to VGA adapter, and you experience problems with it (It behaves badly, D1 burns out, F3 "blows", or your PSU overloads), then not all is lost, there are cheap (a few dollars) adapters that allow you to add external power to the HDMI cable! An example can be found here: [http://dx.com/p/hdmi-male-to-hdmi-female-adapter-w-power-input-port-black-155361].

===HDMI->DVI-D cables===
HDMI to DVI-D cables, or HDMI cables with an DVI-D adapters should work, connected to a DVI-D monitor, that is because both HDMI and DVI use the same kind of digital signaling (LVDS). The only limitation being that DVI-D misses the signal channel for audio.

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.

* '''The Pi Hut'''
** HDMI to DVI Cable for the Raspberry Pi (from [http://thepihut.com/collections/video-output/products/hdmi-to-dvi-cable-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
* '''Other Variants'''
** AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.
** [http://www.ebay.com/itm/DVI-Female-to-HDMI-Male-Adapter-Converter-Adaptor-Gold-for-HDTV-Full-HD-/320946033059?pt=US_Video_Cables_Adapters&hash=item4ab9dfd1a3 A generic HDMI-to-DVI converter from eBay]. Works well, but it's probably the cause of some power loss between the Raspberry Pi and the monitor, causing [http://elinux.org/R-Pi_Troubleshooting#Interference_visible_on_a_HDMI_or_DVI_monitor this] problem. A setting of config_hdmi_boost='''5''' in /etc/boot solved this. Note that config_hdmi_boost='''4''', as suggested in the troubleshooting guide, helped, but it did not solve the problem completely.

===HDMI->VGA Cables===
HDMI to VGA cables do not work!
They rely on logic incorporated in a videocard that isn't available in a PI.
Somehow such a videocard outputs analog signal on the otherwise purely digital HDMI connector, that seems to be the only way for it to work.
But normally HDMI cables never carry analog signals and the PI surely doesn't output analog signals either, almost no HDMI output device does, as its completely against HDMI specifications.

===HDMI->VGA converter boxes===
HDMI to VGA converters do work, they convert the digital serial data streams from HDMI and using complex logic, and digital to analog converters they convert the HDMI signal to the analog signals needed for VGA, and sometimes also convert HDMI audio to an analog stereo signal. But note that if they feed off the PI it can cause a problem, as the PI only is designed to provide about 50mA to the (HDMI or DVI-D) monitor, and these adapters use >200mA, while the absolute maximum the PI can let through is 200mA.
These adapters also thus use about half the energy that the PI (without USB devices) uses.
Therefore its much better to use an adapter that has an external power input. Alternatively there are HDMI dongles (male to female HDMI adapters) that have a barrel input connector to feed the adapter with.

Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.

[http://www.element14.com/community/groups/raspberry-pi/blog/2012/08/16/raspberry-pi-hdmi-to-vga-converter Sanoxy HDMI to VGA converter], $27 from Amazon, no changes required with official Raspbian Wheezy image (2012-Jul-15), note: had already disabled overscan previously

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 Raspberry Pi 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 1 A 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 Raspberry Pi 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 +5 V connection adapted from a USB cable, which bypasses Raspberry Pi's Micro USB cable and polyfuse F3.

* Link to a gallery with detailed images & steps of the same adapter modification: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

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 @60 Hz:
 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 it is very pricey compared to the 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.4 A, which is too much draw for the 5 V 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 it is 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. It is very cheap, but it 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 60 Hz, 1024x768 60 Hz, 640x480 works) The adapter is based on Lontium LT8511A chip, but I was unable to get the specification for it.
The D1 diode is getting very hot though. Most likely the adapter drives more than 200 mA. The standard RS Components 1.2 A USB power supply is able to provide enough power for the Raspberry Pi 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 Raspberry Pi's RCA video output. Additionally using a splitter cable (3.5 mm 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 ==

The SD card section has been moved to a separate page. See [[RPi SD cards]]

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}
♦
nbsp;V 1nbsp;V 1000

User:TrevorGowen

2013-01-20T11:28:17Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 20.01.2013, includes a brief look at [[RPi_Distributions#RISC_OS| RISC OS Pi]]&Dagger;. USB Powered Hubs "power loading" measurements updated, including additional devices.).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, recent "Model B" with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure])

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

RPi VerifiedPeripherals

2013-01-10T14:34:41Z

TrevorGowen: /* Working power Adapters */ Corrected reference links

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

==Power Usage Notes==
{{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 Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75 V), 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.}}

'''Model B Hardware Revisions and USB Power limits'''
'''Hardware Revision 1.0'''
The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximatly 100 mA. USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA 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.

'''Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change'''
This had the polyfuses removed, removing the 100 mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012.

==Linux Driver Issues==
Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=12097&start=76] [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5249&start=44]
A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image.

== 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 the Raspberry 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 Raspberry Pi through their interconnect cable, due to the 100 mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).

===Working USB Hubs===
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''USB Version'''
| '''Number of Ports'''
| '''Power Rating*'''
| '''Powers Raspberry Pi'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|4-Port Ultra-Slim Desktop Hub
|F4U040
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U224
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|TetraHub™ USB 2.0 4-Port Hub
|F5U231
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Hub
|F5U234
|
|USB 2.0
|4-Port
|5 V - 500 mA per Port
|Verified
|No backfeed, can power the RPi. Comes with a 2.4 A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''“Per Port Current Self-Powered Mode: 500mA (max)”''. However, I've attached a HD that requires 850 mA and it worked fine.

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237
|
|USB 2.0
|7-Port
|5 V - 3.8 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|MyEssentials 7-Port High-Speed USB 2.0 Hub
|F5U259-ME
|
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 4-Port Lighted Hub
|F5U403
|
|USB 2.0
|4-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Lighted Hub
|F5U700
|
|USB 2.0
|7-Port
|
|Verified
|[http://www.amazon.com/gp/product/B000SDW84K]

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hub 2-en-1
|F5U706ea
|
|USB 2.0
|7-Port
|
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Hi-Speed USB 2.0 7-Port Hub
|F5U237v1
|
|USB 2.0
|7-Port
|5 V - 2.5 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U040v
|05e3:0608
|USB 2.0
|4-Port
|5 V - 2.6 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Belkin
|Ultra-Slim Desktop Hub
|F4U039qukAPL
|05e3:0608
|USB 2.0
|7-Port
|
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Benq
|
|E2220HD
|
|USB 2.0
|4-Port
|
|Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Biltema
|
|23-924
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|BUFFALO
|4 Port Hub
|BSH4aAE06
|05e3:0608
|USB 2.0
|4-Port
|5 V
|Verified
|No Problem using Webcam & wifi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB

|- valign="top" align="left" style="background: #F5FAFF;"
|Cyberpower
|High-speed Hub
|CP-H720P
|0409:0050
|USB 2.0
|7-Port
|3.6 A
|Verified
|May Contain dual 05e3:0608 instead of 0409:0050

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2001FP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|SP2309W
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|2407FWP
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Dell
|
|U3011
|
|USB 2.0
|4-Port
|
|Not Verified
|Monitor with built in Hub - Card Reader Works - May work with SDXC

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|
|B/N61393
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Delock
|USB 2.0 External Hub 7 Port
|B/N87467
|
|USB 2.0
|7-Port
|5 V - 3.5 A
|Verified
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.

|- valign="top" align="left" style="background: #F5FAFF;"
|Deltaco
|
|UH-715 Rev 2
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|
|
|0409:0050
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Dynex
|Dynex USB 2.0 7 Port Hub
|DX-HB7PT
|
|USB 2.0
|7-Port
|5.0 V / 2.0 A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|D-Link 7 Port USB Hub
|DUB-H7/B
|
|USB 2.0
|7-Port
|3.0 A
|Verified
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-H7 High Speed USB 2.0 7-Port Hub
|BUBH7A A5
|
|USB 2.0
|7-Port
|2.0 A
|Not Verified
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]

|- valign="top" align="left" style="background: #F5FAFF;"
|D-Link
|DUB-4 High Speed USB 2.0 4-Port Hub
|DUB-H4
|
|USB 2.0
|4-Port
|2.0 A
|Verified
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi

|- valign="top" align="left" style="background: #F5FAFF;"
|Digicom
|
|
|
|USB 2.0
|4-Port
|5 V - 2.0 A
|Not Verified
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]

|- valign="top" align="left" style="background: #F5FAFF;"
|Medi@com
|USB 2.0 4 ports Hub
|M-HX30
|
|2.0
|4-port
|
|Verified
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]

|- valign="top" align="left" style="background: #F5FAFF;"
|mbeat
|13 Port USB Hub
|USB-M13HUB
|
|USB 2.0
|13-port
|5V - 3A
|Verified
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Monoprice
|Aquagate USB Hub
|5328
|
|2.0
|7-port
|2.0 A
|Verified
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
|Plata 4 port USB 2.0 hub
|18687
|
|2.0
|4-port
|1.0 A
|Not Verified
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.

|-
|}

'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.
</div>

*'''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 it is 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 Raspberry Pi, and additionally connect GND and +5 V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.

*'''Digitus'''
** 7-port USB2.0 Powered Hub. Model DA-70226.
*'''Eminent'''
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2 A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.
* '''GearHead'''
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5 V, 1 A)
*'''Gembird'''
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.
* '''Genesys Logic (sold at Fry's)'''
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware and Belkin, same ID shows up in lsusb)
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, 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)
* '''König Electronic'''
** CMP-USB2HUB55 - 7 port USB2.0 HUB, (ID 1a40:0201 Terminus Technology Inc. Hub) 2.0 A power supply, backpowers Raspberry Pi well.
*'''Laser'''
** "7 port USB hub with AC adapter Version 2.0". 5 V 1 A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry 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, 2 A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!
*'''LogiLink'''
** UA0085 USB 2.0 Hub, 4-Port with PSU 5 V, 2 A
** UA0091 USB 3.0 Hub, 4-Port with PSU 5 V, 4 A. Connected with USB2.0 cable. 1 A 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 5 V, 3.5 A (Not suitable for powering Raspberry Pi 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 5 V, 2 A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.)
* '''Macally'''
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000 mA wall-wart (US style)
* '''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 1000 mA wall-wart (US style)
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500 mA each) + (4 USB 3.0 Ports @900 mA each) Power Switches on each port, AC Powered and Includes a 5 V 4 A wall-wart (US style)
*'''Newlink'''
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5 V 1 A
** NLUSB2-222P 4 port USB 2.0 Hub with 5 V 2 A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])
*'''Nilox'''
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5 V 1.0 A
* '''Plugable'''
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5 V 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port.
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5 V 3 A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0].

* '''Pluscom'''
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3 A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.
*'''Satechi'''
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.
*'''Staples (Business Depot) (Bureau EN GROS)'''
** Staples 4-port hub Item 607477-CA
*'''StarTech.com'''
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5 V 2 A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).
*'''SumVision'''
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5 V 1.0 A (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 Raspberry 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 (1 A). Powering Raspberry Pi via microUSB from a hub port.
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]
*'''Sweex'''
** US014 4 Port USB 2.0 Hub
*'''Targus'''
** ACH81xx 7-port powered hub. 5 V 3 A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)
** ACH63EU 4-port. Using a 5 V 2 A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.
*'''The Pi Hut'''
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
*'''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 (5 V 2 A)
*'''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 (5 V 2.5 A) Powering Raspberry Pi from the 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 5 V, 3 A. USB ID 1a40:0201.
*'''VANTEC'''
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5 V 2 A AC/DC adapter. Go 2.0 Mini hub.
*'''Z-TEK'''
** Z-TEK 7-port powered hub with PSU 5 V, 4 A. 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, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5 V pinouts)
** F4U022 7-Port powered USB hub (powered 5 V, 2.6 A), 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. (Works always without powering the Raspberry Pi, haven't tried that)

*'''Dell'''
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.

*'''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.
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root filesystem from a USB drive.

*'''Dynamode'''
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1 A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification.

*'''D-Link'''
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)

*'''E-Solution'''
** 4-Port 2 A 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 with 1 A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry 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.
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.

*'''Hama'''
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi 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).

*'''iBall'''
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power suply.

*'''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 5 V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).

*'''Targus'''
** ACH115EU 7-port powered hub. 5 V 3 A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as 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. 1 A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi 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). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.
** Generic 7-port black hub with Genesys Logic GL850A chipset
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2 A 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 there are strange USB failures when X session started. High speed devices such as hard drives had failures.

== USB Remotes ==
* 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.

* [http://www.amazon.com/gp/product/B005DKZTMG/ref=oh_details_o02_s00_i00 Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070)] - keyboard and touchpad work. Have not verified multi-touch features.

* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4 GHz wireless keyboard and touchpad.

* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.

* [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], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]. Working perfectly, just plug & play.

* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)

* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6753651&CatId=3680# Exo Ultra U12-41310 Mini Keyboard] Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work.[https://github.com/thunderbirdtr/rs-pi-exo-keyboard Exo Installer script]

== 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, 20 mA.

* '''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, 100 mA (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''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))
** [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)

* '''Banbridge'''
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)

* '''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)
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5 V/100 mA, works directly

* '''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)

* '''CD Training'''
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]

* '''Cherry'''
** CyMotion Master Linux (B)
** RS 6000 USB ON
** G84-4100PTMUS (B) (Compact keyboard. Rated 100 mA. Works directly in Raspberry Pi)
** G85-23100DE-2 (B) (Rated 40 mA, tested with RPi powered by a 1000 mA power supply unit)

* '''Compaq'''
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5 V 100 mA. Works directly connected to Raspberry Pi

* '''Das Keyboard'''
** Model S Professional Keyboard (Built in USB hub not tested) (B)
** Model S Ultimate Keyboard (Built in USB hub working) (B)

* '''Dell'''
** SK-8115 (B) (Rated 100 mA. Works directly in Raspberry Pi)
** L100 (B)
** RT7D40 (100 mA. Works directly in Raspberry Pi)
** RT7D50 (75 mA) (run "sudo dpkg-reconfigure keyboard-configuration")
** KB1421 (100 mA)
** KB2521 (100 mA)
** KB212-B (Works directly in Raspberry Pi, without powered hub)
** 1HF2Y (Works directly in Raspberry Pi)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Delux'''
** K8050

* '''Digicom'''
** WKEYPE01 Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

* '''Dynex'''
** DX_-WKBD (60 mA) (B)
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)

* '''EAPPLY'''
** EBO-013 Wireless 2.4 GHz compact keyboard with touchpad. Rated <40 mA works directly from Raspberry 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

* '''GE'''
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)

* '''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 >> also see Problem USB Keyboards
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)
** KB1500U (USB Mini Keyboard) (B)
** KB5150 (2.4 GHz wireless keyboard/mouse Combo) (B)
*** Works well with a powered hub

* '''Generic'''
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.

* '''Genius'''
** Ergomedia 700 (GK-04008/C) used without Hub
** KB-06XE (K639) (B)
** LuxeMate i200 (GK-090017; not tested with Hub)
** Slimstar 8000 wireless keyboard

* '''Gigabyte'''
** GK-KM7580 2.4 GHz Wireless Multimedia Keyboard & Mouse

* '''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.4 GHz 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.4 GHz 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 Raspberry Pi. Also works with Raspbmc with powered hub.
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub
** ACK-3700C
** ACK-340U+(DE)
** ACK-3400U (UK) mini keyboard
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi

* '''Labtec'''
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat 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.4 GHz 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.4 GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.

* '''Logik'''
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver

* '''Logitech'''
** Comfort Wave 450, labeled 100 mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine
** 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
** MK120 wired keyboard and mouse
** MK220 wireless keyboard and mouse
** MK250 wireless keyboard and mouse (no hub needed)
** MK260 wireless keyboard and mouse (no hub needed)
** 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]
** MK350 wireless keyboard (using Unifying receiver)
** MK520 wireless keyboard and mouse
** MK550 wireless keyboard and mouse (B)
** MX3200 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.
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)
** EX110 Cordless Desktop, wireless keyboard and mouse (B)
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]
** K120 Keyboard (B)
** K200 Keyboard (B)
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)
** K350 Wireless Keyboard (B)
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". +1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.
** K520 Keyboard (B)
** K700 Wireless Keyboard with Touchpad and unifying receiver
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).
** 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 Raspberry Pi.
** 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.
** V470 Bluetooth Laser Mouse

''Keyboards and mice also together with Unifying receiver''

* '''macally'''
**macally iKey slim (IKEY5V2)

* '''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)
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5 V/100 mA (Wheezy 5-Sept-2012)

* '''Mikomi'''
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the 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)

* '''ONN'''
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.

* '''Ortek'''
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.

* '''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/Raspbian Wheezy)
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.

* '''Philips'''
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)

* '''Prodige'''
**Nanox Wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]

* '''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]
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)

*'''Riitek'''
**RT-MWK03 mini wireless keyboard & trackpad
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.
**RT-MWK01 mini wireless 2.4 GHz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]

*'''Rosewill'''
** RK-200 Standard Keyboard

*'''Saitek'''
** Eclipse II Backlit Keyboard PK02AU (B)
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.
** Expression Keyboard (US)
** Cyborg V.5 (B)

*'''SelecLine'''
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (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)

*'''SolidTek'''
** Solid Tek KB-P3100BU ASK-3100U.

*'''Sony'''
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5 V 1 A 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)

*'''The Pi Hut'''
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.

* '''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.4 GHz 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 Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5 V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry 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.0 V. 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 power away from the rest of the support system devices.

* '''A4 Tech'''
** Model GL-6 USB Keyboard, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''Accuratus'''
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100 mA). Tested with 1000 mA cheap unbranded and Nokia 1200 mA power adaptors.
* '''Apple'''
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub.
*'''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 <200 mA)
* '''Dell'''
** SK-8135 (B) (Rated 1.5 A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)
** SK-8115 causes kernel panic (rated 100 mA) Debian 6-19-04-2012 (B)
** Y-U0003-DEL5 Sticky / Non-responsive keys
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V
* '''Gear Head'''
** KB2300U - Causes kernel panic (B)
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)
* '''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/]
* '''Inland'''
** Inland USB Keyboard Model #70010
* '''Jeway'''
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)
* '''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)
** MK 260 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)
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000 mA power supply unit)
* '''Novatech'''
** NOV-KEY2 - Causes kernel panic (B)<ref>http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2</ref>
* '''PC World Essentials'''
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it 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).
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5 V 500 mA. (B)
* '''SIIG'''
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.
* '''Texet'''
** MB-768B standard keyboard (Rated 5 V 1.5 A (!), 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.
* '''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.
* '''Verbatim'''
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)
* '''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

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

* '''Apple'''
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).

* '''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)
** MG-0919 (wireless)

* '''Belkin'''
** F8E882-OPT (B)

* '''Cellink'''
** OPM-602 Small wireless optical mouse

* '''Cerulian Technology'''
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA

* '''Dell'''
** M-UVDEL1 (B)
** MOC5UO (100 mA)
** M056U0A (B)
** DZL-MS111-L (B) (100 mA)
** MS-111P (100 mA)
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500 mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4

* '''Dynex'''
** DX-WMSE (100 mA) (B)

* '''Fellowes'''
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (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.4 GHz 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)

* '''Kensington'''
** Kensington Expert Mouse Trackball K64325
** Kensington Expert Mouse "Slimblade" K72327US

* '''Labtec'''
** Corded Laser Glow Mouse 1600, rated 5 V 100 mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)

* '''Lenovo'''
** Wired Optical Mouse Model: MO28UOL

* '''Logik'''
** Wired Optical Glow Mouse Model: LGGMO10. (B)

* '''Logitech'''
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)
** B105 Mouse for Laptops (OEM)
** 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)
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).
** 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 5 V 100 mA. Works fb on model B with Raspbian Wheezy

* '''Microsoft'''
** Comfort Curve Mouse 3000 for Business
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).
** 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 1000
** 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)

* '''Perixx'''
** PERIMICE-210 U Red (Part No.R1J)

* '''Razer'''
** Boomslang Collectors Edition 2007 (B)

* '''Rosewill'''
** Rosewill RM-C2U

* '''Saitek'''
** Notebook Optical Mouse (PM46)

* '''Samsung'''
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50 mA)

* '''Sun microsystems'''
** Model: FID-638 , SunPN: 371-0788-01

* '''Sweex'''
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]

* '''Swiftpoint'''
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.

* '''Targus'''
** AKM02UK (Associated keyboard not checked)
** AMU2701EUK (B)

* '''Technika'''
** TKOPTM2 (B)
**TKD-211
**TKNM110

* '''Tesco'''
** Wired optical mouse M211 (B)

*'''The Pi Hut'''
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Trust'''
** Model 15313 - large, 5-button wirless mouse
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087

* '''Verbatiam'''
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)

* '''Xenta'''
** MOW0810 (B)
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''Generic'''
** Generic 2.4 GHz 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
* '''A4Tech'''
** Model G7-630 Wireless Mouse, 20 mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.
* '''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 1000 Hz out of the box, whereas the 518 is only 125 Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.

* '''Microsoft'''
** Microsoft Touch Mouse - Does not see right clicks, Only left.

* '''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 Real Time Clocks ==
*Cymbet
** Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)
Device information at http://www.cymbet.com/pdfs/DS-72-22.pdf
Code to access the RTC from Linux: https://github.com/owendelong/Cymbet-RTC
Does not require a powered hub.

== USB Wi-Fi 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 Wi-Fi Adapters===

These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but it has not yet been tried.

'''Note:''' A Wi-Fi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if
there is a large distance from the Wi-Fi adapter to the Wi-Fi Access Point. Therefore, you may need to plug the Wi-Fi 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 Raspberry Pi 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."
** It works without additional software connected directly to a Rev 2 Raspberry Pi, but it stops working after a period of time (3 to 4 hours) with a fully updated Wheezy and all the 'USB workarounds' [http://elinux.org/Rpi_USB_check-list] in place.

* '''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). Tested on Raspbian too (drivers from aircrack-ng).
** AWUS036H (500 mW version): Tested on Raspbian (drivers from aircrack-ng).
** AWUS036H (1 W version): Tested on Raspbian (drivers from aircrack-ng). Needs USB powered HUB or Rev2 of the board / polyfuse bypass.
** AWUS036NHA: Tested on Raspbian (drivers from aircrack-ng). Works fine if connected after boot, otherwise Raspberry Pi won't boot up.

* '''AirLink101''' [[File:Airlink101.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-airlink101|100px|Airlink 101 Wireless N 150 Ultra Mini-USB Adapter]]
** 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.
** AWLL5099: Tested on Raspian Wheezy. [http://www.savagehomeautomation.com/raspi-airlink101 Step-by-step installation and configuration instructions] with screenshots can be found [http://www.savagehomeautomation.com/raspi-airlink101 here]. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.
** [http://www.airlink101.com/products/awll6075.php AWLL6075]: Tested on Raspian Wheezy 16-Dec-2012 build and distro upgrade as of 09-Jan-2013. lsusb reports: 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter. Driver installed is r8712u.

* '''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 repository (B) (not needed with latest Raspbian “Wheezy” 2012-07-15: this Asus works N10 out of the box) Does not support nl80211 APIS, so hostapd won't work.
** [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 it will not function.
** WL-167G v3 USB ID 0b05:1791, working out-of-the-box on Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17. Does not require powered hub.

* '''AusPi Technologies'''
** AusPi Wireless Adapter [Realtek RTL8188S]. Works without a powered HUB. Tested on OpenELEC (works OOB), RaspBMC (works OOB), XBian (works OOB) and 2012-08-08 Raspbian Wheezy (works OOB). Distributed in Australia by [http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/ Buy Raspberry Pi Australia].

* '''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 '''Powered hub required!'''
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Works on RaspBMC OOB (with NetworkManager plugin). Works WITHOUT powered hub on 5 V 800 mA power with 6 overvolt (nothing else connected to USB)
** 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 repository (B). Verified working with 2012-12-16-wheezy-raspbian right out of the box.
**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. Tested and working on Rasbian Wheezy (and RaspBMC), driver RTL8192CU, no powered hub needed (dongle directly attached to the onboard ports)
** Belkin Components F9L1001v1 "N150" Wireless USB Adapter. Tested and working on Rasbian Wheezy WITHOUT powered hub.
** Belkin Surf Micro WLAN USB-Adapter (Raspbian Wheezy, unpowered hub, "N150")

* '''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
** USB ID: WLI-UC-G300N - Works on Raspbmc out of the box. Tested after a factory reset of the Raspbmc.

* '''Comfast'''
** WU710N: chipset RTL8188CUS. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution.

* '''Conceptronic'''
** C300RU. Works out of the box in Raspbian. Causes reboot when plugging on a live Rev. 2 Raspberry Pi

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

* '''DealExtreme'''
** ISG-1507N Mini USB 2.4GHz 150Mbps 802.11b/g/n WiFi. Has the ralink 5370 chipset, works directly plugged into the Raspberry Pi rev.1 under OpenELEC. Note: Driver (rt2800usb) only permits B/G operation and throughput is low (10Mbit).

* '''DELL'''
** Wireless 1450 [Intersil ISL3887]. Works out of the box, but it requires a powered hub (the Raspberry Pi boots with this dongle plugged in, recognizes and configures it, works for some time, but then it crashes randomly under heavy traffic. A powered hub seems to fix the issue).

* '''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-121 (Version A1). Wireless N 150 Pico. Works out-of-the-box with Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)
** DWA-123 (Version A1). USB ID 2001:3c17, Ralink RT2800. Working out-of-the-box on Arch image from 2012-04-29. (working without UBS Hub - not yet sure if it achieves full speed though.)
** 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]
** WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.

* '''Edimax''' [[File:Edimax-ew-7811un.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-edimax-ew-7811un|100px|Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter]]
** [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]. Note: With current Raspbian (2012-09-18-Wheezy) it is recognized immediately, the default module works fine; the configuration is easy using wireless-essid and wireless-key in /etc/network/interfaces.
*** The EW-7811Un can be powered directly from the Raspberry Pi if the Raspberry Pi is powered using a well regulated power supply.
*** EW-7811Un [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un step-by-step installation and configuration instructions] for Debian & Raspian with screenshots can be found here: [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un here]
*** 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 Raspberry Pi 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.
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=261&pl1_id=1&pl2_id=44 EW-7711UAn], Ralink RT2870, works perfectly on Arch with a powered hub (not tested without yet). Simply required wireless_tools and wpa_supplicant, the drivers/firmware are included in kernel 3.0. I followed the Arch [https://wiki.archlinux.org/index.php/Wireless_Setup Wireless Setup] instructions.

* '''edup'''
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS Wi-Fi 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://dx.com/p/ultra-mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network-adapter-48166?item=1&Utm_rid=24958662&Utm_source=affiliate Ultra-Mini Nano USB 2.0 802.11n 150 Mbit/s Wi-Fi/WLAN Wireless Network Adapter] USB ID: ID 0bda:8176 Works stable when using VLC for internet radio receiver. Works stable 24/7 on two of my Raspberries used as webserver. Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian.

** [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 Raspberry Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or recieved the audio get disorted. Use script from [http://dl.dropbox.com/u/80256631/install-wheezy-beta-rtl8188cus-20120619.sh here] for Wheezy.

* '''Eminent'''
** EM4575 - rt2800usb driver.

* '''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 repository. No need to download firmware when using Debian Wheezy (B)

* '''ISY'''
** USB Wireless Micro Adapter IWL 2000, tested on Raspbian; follow [http://daniel-lnx.blogspot.nl/2013/01/raspberry-pi-and-isy-usb-wireless-micro.html these] instructions.

* '''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 it 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]
** Linksys WUSB54GC (manufactured 07/2008) No issues! needs powered hub on version 1.0 boards.

* '''LogiLink'''
** Wireless LAN USB 2.0 Nano Adapter 802.11n LogiLink [http://www.logilink.eu/showproduct/WL0084B.htm] is working even USB powered.

* '''Lutec'''
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.

* '''Micronet'''
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into Raspberry 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 Wi-Fi 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>

* '''Mvix'''
** Mvix Nubbin (MS-811N): works out of the box on Raspbian "Wheezy" and does not need a powered USB hub.

* '''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. Seems to draw a lot of power; e.g. I can't power this and a USB thumb drive simultaneously.
** WG111v3: Realtek RTL8187B chipset. Works straight out of the box using a powered USB hub.
** WNA1000M works with Raspberry Pi Model B Board v. BS1233.However when downloading torrents, when torrent pick up speed system become unresponsive.

* '''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 Wi-Fi 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.
** RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.
** [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). An image of an adapter with this chip can be found [http://i.imgur.com/wRF7L.jpg here].

* '''Rosewill'''
** RNX-N180UBE Wireless B/G/N Adapter
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172
*** Tested in Arch, works out of box. Powered USB hub required.
*** Tested in Raspbian, used wicd to configure network settings. Powered USB hub Required.
*** Tested in Raspbmc. Needs package firmware - Realtek and used wicd-curses to configure. Powered 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.
** RNX-MiniN1 (RWLD-110001) Wireless-N 2.0 Dongle (Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter)
*** Tested in Raspbian, powered from USB hub.

* '''Sabrent'''
** USB-A11N: Mini USB 2.0 Wireless-N WiFi Network Adapter: USB ID 0bda:8176, works automatically in Raspbian using rtl8192cu driver along with Logitech BT mini-receiver (keyboard/mousepad) without external hub using 5.25V 1 A psu (4.99V T1/T2) on rev 2.0 (B)

* '''Sagem'''
** Sagem Wireless USB stick XG-760N: USB ID 079b:0062, Module is not shipped in Debian image, but it 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/

* '''Sitecom'''
** Sitecom Wi-Fi USB Adapter N300: USB ID 0a5c:5800, Realtek r8712u driver + firmware Realtek. Module available in shipped Raspbian image. '''NOTE:''' although this dongle will also work without powered hub, if there is a voltage problem (either on the Raspberry or on the hub, but verified only on the hub so far) this wifi dongle will receive signal perfectly (RX), but not be capable of sending anything (TX) and the MAC address will be permanently set to FF:FF:FF:FF:FF:FF (this is indicative that there is not enough power) [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]

* '''SL'''
** SL-1507N: USB 802.11n 150M Wi-Fi Wireless LAN Network Card Adapter SL-1507N Black
*** I bought this on on eBay for $4.19 (free shipping) @ http://www.ebay.com/itm/270853614804?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649#ht_4379wt_1199
*** It worked out of the box on Raspbmc RC4, with the network manager add-on; seems to be an rt2800usb
*** dmesg output "usbcore: registered new interface driver rt2800usb"

* '''SMC'''
** SMCWUSBS-N: Hardware detected as rt2800, but it is 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.

* '''Sony'''
** Sony UWA-BR100 802.11abgn Wireless Adapter [Atheros AR7010+AR9280] (Vendor ID: 0411, Product ID: 017f) - Tested with Raspbian. Needs package firmware-atheros.(B)

* '''Tenda'''
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)
** Tenda W311MI Wireless N Pico USB Adapter (identified as Ralink RT5370 Wireless Adapter; USB-ID: 148f:5370) - Works out-of-the-box for Raspian 2012/09/18 or later. An earlier version gave me problems.
** 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]
** Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.

*'''The Pi Hut'''
** USB 802.11n Wi-Fi adapter (from [http://thepihut.com/products/usb-wifi-adapter-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])

* '''TP-Link'''
** TL-WN422G v2 (ath9k_htc) Works OOTB in Debian Wheezy Beta. Runs without powered Hub when plugged into running Raspberry Pi, but the Raspberry Pi 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) | works OOTB with Wheezy Raspbian (2012-08-16) connected directly to raspberry pi (B) and AP functionality tested with hostapd.
** 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-WN723N (RTL8188SU); works OOTB with Raspbian 2012-09-17, (B) stable with 1 A PSU and without powered USB hub on r2.0.
** TL-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub.
** TL-WN821N v3 (ath9k_htc, htc_7010.fw); works out of the box on ArchLinuxARM, Wheezy and on OpenElec (>r11211), Problems with prior OpenElec; needs powered USB Hub (B). This chipset is also compatible with hostapd (wireless AP software)
** TL-WN823N Works out of box on Raspian using powered USB Hub

* '''Trendnet'''
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-648UBM TEW-648UBM] USB ID: 20f4:648b, works OOTB with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/ Adafruit Occidentials Raspbian Wheezy variant] as it includes kernel with [http://www.wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model%3A%3ARTL8188CUS%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols%0D%0A%3FMIMO+status%0D%0A%3FOUI%0D%0A&sort_num=&order_num=ASC&eq=yes&p%5Bformat%5D=broadtable&p%5Blimit%5D=500&p%5Bsort%5D=&p%5Boffset%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Blink%5D=all&p%5Bsearchlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&eq=yes RTL8188CUS driver built-in] (B)
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-649UB TEW-649UB] Works with OpenElec 3.0, chipset Realtek RTL8191SU

* '''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)
** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package

===Problem USB Wi-Fi 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.

* '''Alfa'''
** AWUS036NHA (Vendor ID: 0cf3, Product ID: 9271) - Tested with Raspbian. Works fine if connected after boot. Kills boot process if previously attached. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=16809&p=169469#p169469 Details here.]

* '''EDIMAX'''
** EW-7811Un (Vendor ID: 7397, Product ID: 7811) - Reports as containing the Realtek RTL8188CUS chipset listed below, no lockup or kernal oops under Wheezy, but dmesg reports constant timeouts trying to initialize the module. This appears to be resolved on 2012-09-18-Wheezy-raspbian and newer versions.

* '''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.
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].

== USB Bluetooth adapters ==
===Working Bluetooth adapters===
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.
* 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 Adapter 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
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
** http://www.element14.com/community/message/58288
* IOGear GBU321 (Broadcom BCM2045 Chipset)
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
* Trust BT-2400p
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).
===Working Bluetooth/Wifi Combo adapters===
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref>
===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. Raspberry 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.
* Asus USB-BT211
** Shows up as HCI device in Raspbian, but it does not scan or pair.
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962

== USB Ethernet adapters ==
===Working Ethernet adapters===
* '''AVM'''
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.
* '''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.
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
* '''Apple'''
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.
* '''Edimax'''
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.
* '''D-Link'''
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)
* '''Sabrent'''
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)
* '''Sitecom'''
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.
* '''A-Link'''
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.

The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190 mA, so there might be stability issues if additional power is not provided.
* '''Hama'''
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.

===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. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out

== 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> . If you are not user ''pi'' you may need to add your username to the ''audio'' group thus: <code>sudo adduser yourusername audio</code> (user ''pi'' usually belongs to this group anyway).

* '''Creative'''
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]
* '''Daffodil'''
** [http://www.amazon.co.uk/gp/product/B002FI7GWK/ref=oh_details_o03_s00_i00 USB Sound Adapter US01]. Tested with low-cost headphone/microphone set via ''audacity'' (See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/DaffodilUSBSoundAdapter.html CPM-Spectre-Pi...DaffodilUSBSoundAdapter]).
* '''Edirol'''
** [http://www.roland.com/products/en/UA-1A/ UA-1A]
* '''Hercules'''
** [http://www.hercules.com/fr/Cartes-Son/bdd/p/123/gamesurround-muse-xl-pocket-lt3/ Gamesurround Muse XL (Pocket LT3)]
* '''Logilink'''
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]
* '''NuForce uDAC-2'''
** [http://www.nuforce.com/hp/products/iconudac2/index.php NuForce uDAC-2 Headphone Amplifier and USB DAC]
* '''Terratec'''
** [http://www.terratec.net/fr/produkte/Aureon_Dual_USB_12339.html Aureon Dual USB] (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers)
* '''Texas Instruments PCM2704'''
** [http://www.ti.com/product/pcm2704 PCM2704 98 dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]

==USB 3G Dongles==
* Huawei E173
* Huawei E220
* Huawei E160 (AT commands only)
* 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 Raspberry 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].
*Sundtek
**Sundtek MediaTV Digital Home
**Sundtek MediaTV Pro
**Sundtek SkyTV Ultimate
**[http://shop.sundtek.de DVB-C, DVB-T, DVB-S/S2]: digital TV works, streaming to Windows / Linux is no problem. Easy installation [http://support.sundtek.com/index.php/topic,4.0.html English]
*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.
** Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer)
** Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian)
*K-World
** K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick. IR and supplied remote work with XBMC.
*Technisat
**Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Raspberry Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Raspberry Pi itself. Tested with Astra 19.2E radio and SD-TV channels
*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 was detected, but it is not tested.

== USB Webcams ==

This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!

===USB Webcams===
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
| '''Brand'''
| '''Name'''
| '''Model Number'''
| '''Hardware ID'''
| '''Verified OS'''
| '''Verified OS version'''
| '''Verified Resolution'''
| '''Additional Information'''

|- valign="top" align="left" style="background: #F6D2CF;"
|Canyon
|
|CNR-WCAM820
|
| raspbian/wheezy
|
| 1280x1024
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Live!
| VF0470
|
| ArchLinux
|
|
| works out of the box on ArchLinux

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Socialize HD
| VF0610
|041e:4080
| raspbian/wheezy
| 2012-11-26
| 960x544
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Live! Cam Vista IM
| VF0640
|
| raspbian/wheezy
|
|
| works on Raspbian at 320x240 resolution, 15fps

|- valign="top" align="left" style="background: #F5FAFF;"
|Creative
|Webcam Notebook
| PD1170
|
|
|
|
| Detects, untested.

|- valign="top" align="left" style="background: #F6D2CF;"
|Creative
|Webcam Pro
| PD1030
|
|
|
|
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")

|- valign="top" align="left" style="background: #F5FAFF;"
|HP
|WebcamHD-2200
| HD-2200
|
|
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|HP
|Webcam HP-3100
|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

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C100
| V-U0013
|
| raspbian/wheezy
| 2012-08-16
|
| works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C200
|
| 046d:0802
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C270
|
|
|
|
|
| With external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C310
|
|
|
|
|
| Does not require a powered hub to capture snapshots

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C510
|
|
|
|
|
|

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C525
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C615
|
|
|
|
|
| Works fine without powered hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C905
|
|046d:080a
|occidentalis
|v0.2
|1600x1200
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C910
|
|
|
|
|
| With external power, is uncvideo

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|Webcam C920
|
|
| raspbian/wheezy
|
|
| With powered hub, detected out of box as Video0 V4L device

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Orbit/Sphere
|
|
|
|
|
| Works with external power

|- valign="top" align="left" style="background: #F5FAFF;"
|Logitech
|QuickCam Pro 9000
|
|
| raspbian/wheezy
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 4000
|
|
|
|
|
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.

|- valign="top" align="left" style="background: #F6D2CF;"
|Logitech
|Webcam Pro 9000
|
| 046d:0809
| Arch Linux
|
|
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).

|- valign="top" align="left" style="background: #F5FAFF;"
|Medion
|
| MD86511
|
| raspbian/wheezy
| 2012-07-15
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam Cinemap 720p USB HD Webcam
| H5D-00001
|
| raspbian/wheezy
|
|
|

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam HD-5000
|
|
|
|
|
| Picture breaks up at the bottom

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam HD-6000
|
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| VX-7000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-3000
|
| raspbian/wheezy
|
|
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|LifeCam
| NX-6000
|
| raspbian/wheezy
|
|
| Powered by USB hub

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam
| VX-800
|
| raspbian/wheezy
|
| 352x288
| Doesn't work at full resolution

|- valign="top" align="left" style="background: #F6D2CF;"
|Microsoft
|LifeCam Studio/Cinema
|
|
|
|
|
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].

|- valign="top" align="left" style="background: #F5FAFF;"
|Microsoft
|Xbox Live Vision
|
| 045e:0294
| Arch Linux
|
|
| Powered by RasPi

|- valign="top" align="left" style="background: #F6D2CF;"
|Sony
| Playstation Eye for PS3
|
|
|
|
|
| The occasional frame is corrupted/stutters when running at 640x480

|- valign="top" align="left" style="background: #F5FAFF;"
|Sony
| Playstation Eye for PS2
|
|
|
|
|
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P

|- valign="top" align="left" style="background: #F6D2CF;"
|Sony
| Playstation Eye for PS2
| SLEH 00030
|
| Arch Linux
|
|
| (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 Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012

|- valign="top" align="left" style="background: #F5FAFF;"
|Trust
| 2 MP Auto Focus Webcam
|
|
| Arch Linux
|
|
| works out of the box

|- valign="top" align="left" style="background: #F6D2CF;"
|Trust
| SPACEC@M 200
|
|
| Arch Linux
|
|
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012

|-
|}

== USB GPS devices ==

*Columbus
** Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients)
*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: It works, but it may draw too 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 Raspberry Pi. 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 and USB to Serial (RS-232) adapters ==
A 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 works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio.

** FT2232D dual RS232/FIFO works (used in various JTAG devices)

*'''Prolific'''
**PL2303 chip based adaptors works fine on latest Debian tested with ''minicom'' and ''gtkterm''

A USB to Serial (RS-232) adapter is used the other way around, ie. the USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment.

*"Best Connectivity" (Possibly also sold under the "Newlink HQ" or "Kenable HQ" labels)
**FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by ''lsusb'' as <code>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</code>. Appears as <code>/dev/ttyUSB0</code>, and requires the user to be a member of the ''dialout'' group (which ''pi'' is for ''Raspbian Wheezy''). Initially tested using an old RS Datalinker setup in "loopback" mode via ''microcom'' upto 9600 baud, and ''gtkterm'' after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently ''gtkterm'' was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

== Other, exotic USB devices ==
=== USB to Parallel Port/Printer Adapters ===
*'''Prolific'''
**PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under [[RPi_Distributions#RISC_OS| RISC OS Raspberry Pi]] with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBtoParPrntAdapter.html CPM-Spectre-Pi...USBtoParPrntAdapter] for more info. and also a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/WheezyCUPS.html CUPS/Wheezy installation guide])

=== USB to SATA ===
*'''Nippon Labs'''
** 2.5" SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi. Built-in "Y" power adapter.

=== 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 5 V at 0.5 A 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 it is 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 Raspberry Pi.
**Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168
=== USB RFID Reader ===
*Unbranded 125 kHz EM4100 RFID reader from eBay sellers (< £7), the one with a Windows logo on (easily scratches off for Linux users).
**Initially would not work when plugged in directly to Raspberry Pi. Worked when connected via an unpowered Trust hub. Worked after Raspberry Pi was modified with 10K resistors over the USB polyfuses (warranty invalidated). Probably would work fine with powered hub.
**Sends a 10 digit string to current window or console as if it was a keyboard. Can be captured independently of keyboard using Linux event interface (/dev/input), but the kernel in current distributions does not have CONFIG_INPUT_EVDEV selected so kernel rebuild is necessary.
=== JTAG ===
* FTDI2232D dual RS232/FIFO based JTAG (e.g. SheevaPlug JTAGKey USB-ID 9e88:9e8f)
** works using the Raspberry Pi as a development host
=== USB 3.0 Multi-Card Reader ===
* US Robotics All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously
** SD/MMC + MS/MS PRO or DUO/DUO PRO + CF/MD + SM + SD/MMC or MS/MS PRO. Useful for backing up cards containing other OS Distros

== 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 additional 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 it 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 5 V. 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===
* '''Adafruit'''
** 5.25 V 1 A Model 501 (Newark 44W4932) USB 110-240 VAC power supply [4.99-5.01 V @ T1/T2 with 100 mA BT and/or mini wireless-n on RPi USB ports]
* '''AlcaPower'''
** 5 V 2.5 A Model AP5A - Charger/switching with 7 connectors(also Microusb)
* '''Ansmann'''
*** Dual USB charger slim, Model-Nr. 1201-0001
* '''Apple'''
Note that apple designs its charger products to work optimally as '''chargers''', in practice this means that apple chargers drop their output voltages somewhat with output current, so that the charging circuits do not need to dissipate more heat than is strictly necessary. Because of this, and although many people have reported apple products to power their basic PI setup reliably, its still not an optimal choice for a PI system that uses power hungry USB devices. Also, because of the popularity and high price of these chargers there are many very sub standard, but almost impossible to recognize as fake copies on the market, and some of these fakes are about the worst things you can try to power your PI with! Not only do they not work, they may actually be dangerous to use!
** 5 V 2.1 A USB charger for iPad2, model A1357
** 5 V 1.0 A USB Charger for iPod
** 5 V 1.0 A USB Charger for iPhone 4
* '''Amazon'''
** 5 V 0.85 A USB charger for Kindle
** 5 V 2 A Mains to USB A adaptor, Branded "CostMad"
* '''Asus'''
** 5 V 2.0 A USB charger for Google Nexus 7
* '''Belkin'''
** 5 V 2.6 A 4 port Ultra-Slim Desktop hub (Model F4U040) (Raspberry Pi running from USB hub port)
** 5 V 2.5 A 4 port USB Hub (Model F5U404) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB 2.0 Mobile Powered Hub (Model F4U018) (Raspberry Pi running from USB hub port)
** 5 V 3.5 A 7 port USB Hub (Model F5U706) (Raspberry Pi running from USB hub port)
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)
** Universal USB Wall Charger (5 V 1 A) (Model F8Z222uk)
* '''Blackberry'''
** Charger for Pearl Flip 8220, Bold 9600 (B)
** Charger for Tour 9630
** 5 V 0.7 A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)
** 5 V 750 mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)
** 5 V 750 mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)
** 5 V 2 A Model PSAC10R-050QT, RIM Part Number HDW-34725-001
** 5 V 550 mA curve 8520 charger works with raspberry pi Model B Board v. BS1233. It does not work with Raspbmc image.Symtoms are frequent key board and external hdd disconnects.
* '''Deal Extreme'''
** [http://dx.com/p/5v-2a-regulated-switching-power-supply-110-220v-94518 S-10-5 5 V 2 A Regulated Switching Power Supply (110~220 V)] (DIY: requires additional micro-USB connector and wiring)
* '''Dell'''
** USB Hub integrated in Dell monitors (B)
* '''The FX Factory'''
** 5 V 1 A (1.2 A max) AC Travel Charger Model KJ-USB Mains. Typically provides 4.9 V at 1 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>
* '''Garmin'''
** 5 V 1 A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6 ft cable (F3U151B06) works.
* '''Globe Electric'''
** 2-Outlet Tap with Surge Protection and 2 USB Chargers ([http://globe-electric.com/product/2-outlet-tap-with-surge-protection-and-2-usb-chargers-grounded-white/ 46082]). Rated at 1000 mA. 120 V systems only.
* '''Griffin'''
** Power Block Model P2417. 5 V 2.1 A
** Power Block Model P1190R2 Two USB 5 V Outputs, 1 A each
* '''Hama'''
** 1000 mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)
* '''Hartig + Heiling GmbH & Co. KG'''
** H+H SN 6 USB
* '''HP'''
** 5.3 V 2 A Charger for HP Touchpad (B)
* '''HTC'''
** 5 V 1 A TCP-300 USB phone charger (B)
** 5 V 1 A TC B250 USB charger (HTC R/N: 79H00096-00M)
** 5 V 1 A TC E250 USB charger (HTC R/N: 79H00098-02M)
* '''i-box (Philex Electronic Ltd)'''
** 5 V 1 A 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'''
**15 W Dual USB Adapter. Model: mMini AC15. Output: 5 V, 3 A (max per port), 15 W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Specification sheet]
* '''Kodak'''
** 5 V 1 A TESA5G1-0501200
** 5 V 1.0 A K20-AM
* '''LG'''
** 4.8 V 1 A Travel Adapter
** 5.1 V 0.7 A Travel Adapter (Model: STA-U34WVI)
** 5.1 V 0.7 A Travel Adapter (Model: STA-U12ER)
* '''Logic'''
** 4 port USB Hub (Model LP4HUB10). (Raspberry Pi running from USB Hub port, red power line (+5 V) inside hub cut) (B)
*'''LogiLink'''
**5 V 2.1 A Switching power supply, model PA0040 (B)
* '''Logitech'''
** 5 V 1 A SDC115-USB Remote Control Charger and cable
* '''Maplin Electronics'''
** 5 V 1 A dual USB power supply, model number H25B-MT-K2
** Micro USB Power Supply N19HX
* '''Medion'''
** 5 V 1 A USB power supply for OYO ebook reader
* '''Microsoft'''
*** Zune Zune AC Adapter v2
* '''Motorola'''
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5 V 0.85 A SPN5504 Charger with Cable]
* '''Noname'''
** 5 V 2.1 A 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.2 V 1 A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]
** 5 V 1 A Model H-IP008 Serial No. H10T80L068
* '''Novatel Wireless'''
** 5 V 1.05 A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device
* '''Orange'''
** 5 V 0.7 A Charger for Orange San Francisco
* '''Palm'''
** 5 V 1 A Charger for Palm Pixi+ (B)
* '''Pantech'''
** 5.0 V 1 A CNR USB with LG DLC100 micro USB cable
* '''Petzl'''
** 5.0 V 1 A Charger that came with the Tikka core2 XP
* '''Phihong'''
** Switching Power Supply. Model: PSAC09R-050. Output: 5 V, 1.8 A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]
* '''PortaPow'''
** PortaPow UK Mains Wall Power Supply
* '''PowerGen'''
** PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. [http://www.amazon.com/gp/product/B0073FCPSK Amazon Link]
* '''Rayovac'''
** Universal USB Charger Model: PS69 100-240 VAC to 5 V 1 A (small cube w/folding plug) works w/wireless keyboard/mouse and mini-Wifi connected
* '''RS Components'
** HNP06UK (RS 7263069) Switching Adapter 5.0 V 1200 mA
* '''Samsung'''
** 5 V 0.7 A Charger for Galaxy S model ETA0U10EBE
** 5 V 0.7 A Charger for Galaxy SII
** 5 V 1 A Charger for Galaxy SIII
** 5 V 1 A Charger for Galaxy Nexus
** 5 V 0.7 A Charger for Galaxy S Vibrant (SGH-T959)
** 5 V 0.7 A Travel Adapter model ATADU10EBE
** 5 V 1 A? Samsung C Series TV USB-port for external HDDs. Running stable with openelec
** 5 V ?A (Unknown) Samsung Service Port (USB) on LN32A330J1DXZA 720p 32 inch HDTV
** 5 V Unknown Ampere Samsung UA22D5000 & UA32D5000 TV USB Port. Test with Raspbian Wheezy, Raspbmc, and RPITC
* '''Shun Shing'''
** 100-240 VAC to 5 VDC 1 A USB power supply, model SP5Q-AU [http://jaycar.co.nz/productView.asp?ID=MP3455 Jaycar]
* '''Sony Ericsson'''
** 5 V 0.7 A Charger CST-80
** 5 V 0.85 A Greenheart Charger EP800. Typically provides 4.8 V at 0.85 A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>.
* '''StarTech'''
** 4 Port USB 2.0 Hub Raspberry Pi can be powered just by plugging USB input into the Raspberry Pi, don't need power in micro USB port.
* '''Travel Charger'''
** 5 V 2.0 A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]
* '''Technika'''
** 5 V 1 A USB Power Adapter, model MPASS01 (B)
* '''The Pi Hut'''
** Micro USB Power Supply for the Raspberry Pi. 5 V 1000 mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])
* '''Trisonic'''
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5 V, 800 mA) $3 at Daiso U.S. stores.
* '''TruePower'''
** [http://u-socket.com/ U-Socket] 5 V 2.1 A AC Receptacle with Built-in USB ports (2.1 A 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===
* '''Nokia'''
** 5 V 1.2 A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2
** [http://accessories.nokia.com/products/nokia-fast-usb-charger-ac-16/ 5 V 1 A AC-16E Charger] Provides only 4.7V across TP1 & TP2 when at idle

* '''Masterplug'''
** Masterplug Surge Protected USB Adaptor 2 x 1 A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artefacts using HDMI.
* '''Monoprice'''
** 5 V, 2 A 3 Outlet Power Surge Protector Wall Tap with 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot. Measured to less than 4.75 V between TP1 and TP2 when used with a Monoprice cable.
* '''Sony Ericsson'''
** 5 V, 850 mA EP800. Some failures to boot, Ethernet loops at boot.

===Working external Battery packs (with 5 V regulated output)===
* '''Anker Astro3'''
** Anker Astro3 10000 mAh with dual 2 A USB output
* '''Duracell'''
** PPS2 Instant USB Charger
* '''Energizer/XPAL'''
** XP18000 18000 mAh Power Pack
* '''Generic - eBay no brand'''
** 6000T Pocket Power 5000 mAh - eBay item 271009959140
** Power Bank for iPad/iPhone 5000 mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938
* '''Mophie'''
** 38113BBR Juice Pack Powerstation 4000 mAh: output 2.1 A max: included charging cable powers RPi, 7.5 hrs light use w/keyboard and mini-Wifi on RPi ports
* '''New Trent'''
** iCurve IMP70D 7000 mAh (Approx 12 hours from full charge)
** IMP120D 12000 mAh
* '''Sinoele'''
** Movpower - Power Bank 5200 mAh (8 hours with Wi-Fi active)
* '''TeckNet'''
** iEP387 Dual-Port 7000 mAh External Power Bank (The charging lead can be used to connect the Tecknet to the Raspberry Pi. Ran the Raspberry Pi with Wi-Fi dongle and wireless keyboard receiver for over 9 hours of light use.)
** iEP392 Dual-Port 12000 mAh External Power Bank (1 A port, ~16.5 hours)
** Rayovac PS60 5 V 800 mAh
* '''VINZO'''
** Power Bank 5000 mAh Grey Output 5 V 1000 mA
* '''Kodak Power Pack KP1000'''
** 1 A USB rechargeable battery pack - see [http://blog.sheasilverman.com/2012/09/its-alive/ Shea Silverman's blog]

== 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 Raspberry Pi's primary input fuse. HDMI ports (and the raspberry PI) are designed so that they deliver a very limited amount of power (50 mA) 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 200 mA, 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 non externally powered devices. If you have bought a non externally powered HDMI to VGA adapter, and you experience problems with it (It behaves badly, D1 burns out, F3 "blows", or your PSU overloads), then not all is lost, there are cheap (a few dollars) adapters that allow you to add external power to the HDMI cable! An example can be found here: [http://dx.com/p/hdmi-male-to-hdmi-female-adapter-w-power-input-port-black-155361].

===HDMI->DVI-D cables===
HDMI to DVI-D cables, or HDMI cables with an DVI-D adapters should work, connected to a DVI-D monitor, that is because both HDMI and DVI use the same kind of digital signaling (LVDS). The only limitation being that DVI-D misses the signal channel for audio.

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.

* '''The Pi Hut'''
** HDMI to DVI Cable for the Raspberry Pi (from [http://thepihut.com/collections/video-output/products/hdmi-to-dvi-cable-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])
* '''Other Variants'''
** AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.
** [http://www.ebay.com/itm/DVI-Female-to-HDMI-Male-Adapter-Converter-Adaptor-Gold-for-HDTV-Full-HD-/320946033059?pt=US_Video_Cables_Adapters&hash=item4ab9dfd1a3 A generic HDMI-to-DVI converter from eBay]. Works well, but it's probably the cause of some power loss between the Raspberry Pi and the monitor, causing [http://elinux.org/R-Pi_Troubleshooting#Interference_visible_on_a_HDMI_or_DVI_monitor this] problem. A setting of config_hdmi_boost='''5''' in /etc/boot solved this. Note that config_hdmi_boost='''4''', as suggested in the troubleshooting guide, helped, but it did not solve the problem completely.

===HDMI->VGA Cables===
HDMI to VGA cables do not work!
They rely on logic incorporated in a videocard that isn't available in a PI.
Somehow such a videocard outputs analog signal on the otherwise purely digital HDMI connector, that seems to be the only way for it to work.
But normally HDMI cables never carry analog signals and the PI surely doesn't output analog signals either, almost no HDMI output device does, as its completely against HDMI specifications.

===HDMI->VGA converter boxes===
HDMI to VGA converters do work, they convert the digital serial data streams from HDMI and using complex logic, and digital to analog converters they convert the HDMI signal to the analog signals needed for VGA, and sometimes also convert HDMI audio to an analog stereo signal. But note that if they feed off the PI it can cause a problem, as the PI only is designed to provide about 50mA to the (HDMI or DVI-D) monitor, and these adapters use >200mA, while the absolute maximum the PI can let through is 200mA.
These adapters also thus use about half the energy that the PI (without USB devices) uses.
Therefore its much better to use an adapter that has an external power input. Alternatively there are HDMI dongles (male to female HDMI adapters) that have a barrel input connector to feed the adapter with.

Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.

[http://www.element14.com/community/groups/raspberry-pi/blog/2012/08/16/raspberry-pi-hdmi-to-vga-converter Sanoxy HDMI to VGA converter], $27 from Amazon, no changes required with official Raspbian Wheezy image (2012-Jul-15), note: had already disabled overscan previously

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 Raspberry Pi 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 1 A 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 Raspberry Pi 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 +5 V connection adapted from a USB cable, which bypasses Raspberry Pi's Micro USB cable and polyfuse F3.

* Link to a gallery with detailed images & steps of the same adapter modification: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''

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 @60 Hz:
 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 it is very pricey compared to the 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.4 A, which is too much draw for the 5 V 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 it is 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. It is very cheap, but it 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 60 Hz, 1024x768 60 Hz, 640x480 works) The adapter is based on Lontium LT8511A chip, but I was unable to get the specification for it.
The D1 diode is getting very hot though. Most likely the adapter drives more than 200 mA. The standard RS Components 1.2 A USB power supply is able to provide enough power for the Raspberry Pi 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 Raspberry Pi's RCA video output. Additionally using a splitter cable (3.5 mm 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 ==

The SD card section has been moved to a separate page. See [[RPi SD cards]]

== Foreign Language Translations ==
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]

== References ==
<references>
</references>

{{Template:Raspberry Pi}}
♦

User:TrevorGowen

2013-01-05T18:15:02Z

TrevorGowen: /* F. Trevor Gowen, MInstP */

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 05.01.2013, includes a brief look at [[RPi_Distributions#RISC_OS| RISC OS Pi]]&Dagger;. USB Power Supply/Powered Hubs measurements largely completed.).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, recent "Model B" with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure])

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)

User:TrevorGowen

2012-12-23T20:06:10Z

TrevorGowen:

== F. Trevor Gowen, MInstP ==
* Retired Principal Scientist
* Hobbies: Electronics, Computers, Photography (Film & Digital), Railway Modelling (N Gauge) and Family History Research
* Web pages: [http://www.cpmspectrepi.webspace.virginmedia.com/index.htm CPM-Spectre-Pi: Trevor Gowen's Home Page]§. These now include a link to exported pages from a [http://moinmo.in/ MoinMoin] wiki that runs on my first&dagger; Raspberry Pi, and which contains notes w.r.t. various "projects" or hardware I'm trying out - mainly various USB devices/adapters that I'd aquired some time ago. (Last import 23.12.2012, includes a brief look at [[RPi_Distributions#RISC_OS| RISC OS Pi]]&Dagger;. USB Power Supply/Powered Hubs measurements largely completed.).

§Relocated to my ISP's newer server to gain webspace!

&dagger;I now have a second, recent "Model B" with 512Mb of RAM (Which was replaced by Farnell after it suffered [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/SDcardSocketFailure.html SD card socket failure])

&Dagger;Which allowed me to resurrect the BBC Basic/NC200 version of my [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/RiscOS.html "Aid to Electronic Circuit Design Program Package"]. (IIRC the first version ran via teletype on a mainframe at Q.M.C. in the mid-1970's)