RPi VerifiedPeripherals

A note about this page: For USB devices, please specify if they required a powered hub

Power Usage Notes
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. 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.

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.  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
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.


 * Acme
 * USB 2.0 hub 4 port (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
 * 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.
 * 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
 * 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
 * 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
 * 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
 * Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000 mA wall-wart (US style)
 * Manhattan
 * (#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)
 * (#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 | ModMyPi)
 * Nilox
 * Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5 V 1.0 A
 * Plugable
 * 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.
 * USB2-HUB10S 10 Port USB 2.0 Hub 2.5 A power supply. Powering Raspberry Pi via microUSB from a hub port.
 * 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. 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 | 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.
 * 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 The Pi Hut's Raspberry Pi Store)
 * Trendnet
 * TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5 V 2 A)
 * Tripp-Lite
 * 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
 * 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 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.


 * Digitus
 * 4-Port USB Hub, no special designator. Chip inside is a GL850G, lsusb identification is 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB. The hub comes with a 5V 2A PSU that is quite capable of powering the Raspberry Pi and additional peripherals. I did not test whether the hub feeds power into the uplink USB port. The problem with this hub is that USB sticks connected to it reliably disconnect after a short time of writing to them (via cat /dev/zero > /dev/ ). Sometimes they reconnect with a different device, sometimes they do not. The only error messages in the logs are plain vanilla USB device disconnects. While this may look like a power-issue, measurements with a digital oscilloscope found absolutely no problem. Another observation I have made is that sometimes (not always), the data-transfer rates to the USB sticks slow down to about 500kB/s. I suspect this is a problem with the USB driver that does not manage to work around some brokeness in the hub chip. The hub has no current-limiter at all and plugging in some peripherals will hard crash your Raspberry Pi, something I do not observe with better hubs.


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


 * nGear
 * nGear G-H508 Mini 4 Port USB2.0 Hub. Does not work when more than 1 device is plugged in even with power supply.


 * 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 TrevorGowen (talk) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at 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)
 * 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

 * The FLIRC USB dongle allows the use of any remote control with your Raspberry Pi. Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion. Available from The Pi Hut


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


 * Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070) - keyboard and touchpad work. Have not verified multi-touch features.


 * iPazzport mini 2.4 GHz wireless keyboard and touchpad.


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


 * PKB 1800 Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.


 * Riitek RT-MWK01 Rii Wireless 2.4 GHz Keyboard-mouse Combo, also known as Digicom WKEYPE01, and Prodige Nanox. Working perfectly, just plug & play.


 * Tranksung TS-Y150 USB RF Keyboard and air mouse (B)


 * 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.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
 * 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))
 * Apple Keyboard with Numeric Keypad (aluminium/wired) A1243
 * Apple Keyboard (aluminium/wired) A1242
 * 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
 * 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)
 * 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
 * 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.
 * G85-26000DE-2 wireless keyboard and mouse combo marketed as "B.Unlimited", works directly connected to Raspberry Pi. Functionality on hub and charging not tested.


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


 * Computer Gear
 * Standard Keyboard. Water resistant &amp; spill proof. Rated &lt; 50 mA. Works directly connected to Raspberry Pi. Has both USB &amp; PS/2 plugs so also good for experimenting with Arduino/Teensy etc. Very cheap - 2 keys didn't work but easy to open for repair.


 * 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 Riitek RT-MWK01 and 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
 * 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 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


 * iOne
 * Scorpius-K3NT (B)
 * (sold by Newark as an 'official' RPi accessory, miniature keyboard with integrated trackball)


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

+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.
 * 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[34bc] 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
 * 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 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".
 * 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


 * 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)
 * 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
 * |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
 * |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. 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 Riitek RT-MWK01 and Digicom WKEYPE01


 * Rapoo
 * Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad
 * Rapoo Wireless Multi-media Touchpad Keyboard 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: 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 Digicom WKEYPE01, and 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
 * SolidTek KB-P3100BU ASK-3100U.
 * SolidTek KB-3910 — compact combined keyboard/trackpad with a single USB cable. Does not need a powered hub.


 * 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
 * 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 The Pi Hut's Raspberry Pi Store)
 * Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from The Pi Hut's Raspberry Pi Store)


 * Trust
 * Trust 17585 Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.
 * Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)
 * Trust 17184 ClassicLine Keyboard
 * Trust 16087 Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087
 * Trust 17603 Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)
 * Trust 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


 * Unisen
 * 2.4GHz 2.8" Mini Wireless Handheld QWERTY Keyboard and Mouse Touchpad


 * 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.
 * A4Tech 2.4G VTrack USB Mouse and Wireless Keyboard (7300N)- Keyboard suffers from missed keystrokes and "stuck" keys with and without USB hub.
 * Accuratus
 * Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100 mA). Tested with 1000 mA cheap unbranded and Nokia 1200 mA power adaptors.
 * Apple
 * 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.
 * 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, works perfectly on a B model (with and without a hub) on raspbian and raspbmc after setting dwc_otg.speed=1)
 * 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
 * |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  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 . 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)
 * M187 Wireless Mini Mouse (B) OK directly into the Pi
 * 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


 * 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
 * |Novatech M1 USB Mouse - Wired(B)
 * |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
 * MI015


 * Swiftpoint
 * 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 The Pi Hut's Raspberry Pi Store)
 * Super Slim Keyboard & Mouse Set (from 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  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  devices.


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


 * Xenta
 * MOW0810 (B)
 * Wired Optical Mouse (from 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. 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
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.
 * Cymbet
 * Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)

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 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, or it is transferring large amounts of data. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.

Note: Some WiFi adaptors, including Ralink brand, may not work reliably unless 'wireless-power off' is included in /etc/network/interfaces. For more details see: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=40474#p330868

Note: Devices with RTL8188CUS work great as wifi access point - see tutorial and configuration script.If you plan to use your raspberry pi in ad hoc mode, you must verify that your adapter is using the nl80211 driver. Wifi adaptors using RTL8188CUS driver will not work in ad hoc mode.

Note: To the owner of this page, this page would benefit of being rewritten as a matrix with - does it need external power - does it support ad hoc, ap - link to how to.


 * 3COM
 * 3CRUSB10075: ZyDAS zd1211rw chipset (!)


 * 7DayShop
 * W-3S01BLK, W-3S01BLKTWIN: Unbranded product available from 7DayShop, in a single or twin pack., . 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' 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 Airlink101.jpg
 * 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. Step-by-step installation and configuration instructions with screenshots can be found here. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution. Wifi access point configuration - see tutorial and configuration script
 * 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
 * USB-N10 USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must 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.
 * USB-N13 USB ID 0b05:17ab, works with Adafruit Occidentalis v0.1 image as it includes kernel 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) and 2012-08-08 Raspbian Wheezy (works OOB). Free shipping worldwide from 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 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 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 this guide.
 * Belkin Components F6D4050 V1/V2 [Realtek RT3070] USB ID: 050d:935a / 935b Driver: RT3572STA. Tested with Raspbian - See 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
 * 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. Wifi access point configuration - see tutorial and configuration script
 * 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, 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. Wifi access point configuration - see tutorial and configuration 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] . [] Works out of the box in OpenELEC. With Raspbian or Debian squeezy/Wheezy works with zd1211-firmware.
 * USBWAVE300C [chipset Ralink 2870] . [] 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  package from the   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). Wifi access point configuration - see tutorial and configuration script
 * 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 works now with Raspbian's kernel 3.6.11+ ! Otherwise get the last Linux firmware on DLink Website : http://tsd.dlink.com.tw/.
 * 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: . 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  package from the   non-free repository.
 * DWA-140 (Version B2). USB ID 07d1:3c0a, Ralink RT3072. Workaround for faulty firmware binary: Place file rt2870.bin from linux-firmware_1.53.tar.gz in /lib/firmware. Explanation.
 * DWA-160 (Version B1). USB ID 07d1:3c11, Ralink RT2870. On Debian requires the  package from the   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
 * WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.


 * Edimax Edimax-ew-7811un.jpg
 * EW-7811Un USB ID 7392:7811, RTL8192CU, driver blob download via Element14, works with WPA2-AES-CCMP (howto) (B) - 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. Wifi access point configuration - see tutorial and configuration script
 * EW-7811Un step-by-step installation and configuration instructions for Debian & Raspian with screenshots can be found here: here
 * A script-based installation for the EW-7811Un by MrEngman can be found on the Raspberry Pi forums. Tested with Debian Squeeze and Raspbian. An installation guide can be found here.
 * Instructions for getting the EW-7811Un working in Raspbmc (tested RC3) can be found here.
 * Simple step-by-step instructions for 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.
 * EW-7318USg USB ID 148f:2573, rt73usb. RT2573 chipset. Works with powered usb-hub or shorted polyfuses.
 * 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 Wireless Setup instructions.


 * edup
 * [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.(requires firmware-ralink from Wheezy) (B)
 * 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 here for Debian.  Seems to be the same as EW-7811Un using the RTL8188CUS chipset.


 * edup nano EP-N8508 Use method shown 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 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.
 * Micro Mini USB Wireless B/N/G 802.11n RTL8192CU WiFi LAN Adapter. As noted elsewhere, RTL8192 driver is in current Raspbian distribution. Wifi access point configuration - see tutorial and configuration script
 * Hawking
 * HWU54G rev. Z2 (802.11g) (B). Requires "zd1211-firmware" package.


 * IOGear
 * GWU625 USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must 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 these instructions.


 * Linksys
 * Linksys (Cisco) WUSB100 ver.2 1737:0078, tested on Raspbian; follow Brucalipto.org instructions; not stress tested, but it works without issues for light network load.
 * Linksys (Cisco) WUSB600N, test on Raspbian, details 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 is working even USB powered.
 * Micro Wireless LAN USB Adapter is working good.


 * 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) Debian installation instructions IMPORTANT: read the instructions first to avoid problems, and Auto-install script. The script has been used to install other adapters using the RTL8188CUS chip. Updated driver that handles the latest rpi-updates that kill the original driver, download for manual installation, automatically installed by the Auto-install script.
 * Wifi access point configuration - see tutorial and configuration script


 * ModMyPi
 * Wireless USB 11N Nano Adaptor 802.11N (Realtek RTL8188CUS) works plugged directly into Raspberry Pi USB without the need for a USB hub. No drivers need installing on Raspian - plug and play! Available from the ModMyPi Raspberry Pi Shop. Wifi access point configuration - see tutorial and configuration script
 * MSI
 * 0db0:6861 MSI-6861 802.11g Wi-Fi adapter (US54G): works with external powered USB hub, requires firmware from here, power management must be disabled:


 * 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  package from the   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
 * PCUSBW1150 Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub. Wifi access point configuration - see tutorial and configuration script
 * PCBOWAU2-N Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Worked immedietly, plug and play in 2013-02-09 Raspbian via powered USB hub.


 * Ralink
 * inner 02 joggler Wi-Fi USB RT2770F USB-ID 148f:2770 (firmware-ralink required) (only got dhcp on powered hub)
 * RT2070 USB-ID 148f:2070 firmware is already loaded into Raspbian. For Debian, the firmware must be installed (instructions). Needs a powered USB hub.
 * RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.
 * RT2501/RT2573 USB-ID 148f:2573 (firmware-ralink required) (B)
 * RT5370 USB-ID 148f:5370 (requires firmware-ralink from Wheezy) RPi_Ralink_WLAN_devices(B). An image of an adapter with this chip can be found 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)


 * 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 (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. Debian installation instructions Available from the ModMyPi Raspberry Pi Shop
 * Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.


 * The Pi Hut
 * USB 802.11n Wi-Fi adapter (from 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, TL-WN722NC (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-WN723N v2 (USB ID: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter, FCC ID: TE7WN723NV2) Works from a box with Raspbian 2013-02-09. Used 2.1A adapter, without powered hub.
 * TL-WN725N v1. Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset. Works great as AP - instructions and config script
 * TL-WN725N v2. Needs manual driver installation. This USB adapter is based on the Realtek RTL8188EUS 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
 * TL-WN7200ND works. Can be made as a WiFi AP using hostapd. Need a powered USB hub.


 * Trendnet
 * TEW-648UBM USB ID: 20f4:648b, works OOTB with Adafruit Occidentials Raspbian Wheezy variant as it includes kernel with RTL8188CUS driver built-in (B)
 * TEW-649UB Works with OpenElec 3.0, chipset Realtek RTL8191SU


 * Widemac
 * RT5370 Wireless Adapter from Ebay runs without powered hub. Follow these instructions, but go to ftp.de.debian.org/debian/pool/non-free/f/firmware-nonfree/ and pick the latest firmware-ralink_0.xx_all.deb


 * ZyXEL
 * NWD2105 USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)
 * NWD2205 USDB ID: 0586:341f RTL8192CU chipset, works out-of-the-box
 * 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 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. Details here.


 * D-Link
 * ( DWA-131 (rev. B1) ) - Works now on Raspbian's kernel 3.6.11+ or with DLink firmware: http://tsd.dlink.com.tw/
 * 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.
 * Possible fix: try the new 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).


 * Realtek
 * RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)


 * Trendnet
 * TEW-424UB USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)


 * TP-Link
 * TL-WN821N USB ID: 0cf3:7015; tested on Debian; requires 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 source.

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
 * Azio BTD-V400. CSR BC8 radio, bluetooth 4.0. Tested with Raspbian using powered USB hub
 * D-Link DBT-120, works OK in Raspian. Tested with Sony PS3 keypad.
 * 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.
 * Note that some Raspberry Pi users are reporting problems with this device; see section below.
 * 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
 * Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)
 * Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)

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
 * 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.
 * 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
 * Broadcom chipset Based Devices, e.g. BCM92045B3
 * This is includes the IOGear GBU321 (listed above as working) among others. The device will show up via hciconfig, but reports as "down".  The device will timeout after attempting to mount via hciconfig hci0 up".  Workarounds linked below have worked for some, but are spotty at best, and may cause side effects:
 * Bluetooth with Broadcom chip a no go?,
 * Bluetooth TX Timeout Issue,
 * Bluetooth dongle only works on usb 1.0 ....
 * The best solution for these devices seems to be to return them or throw them away, and go with the ones with a genuine Cambridge Silicon Radio chipset.

Working Ethernet adapters
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 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 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 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.
 * 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.
 * 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
 * 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.
 * Pluscom
 * Pluscom U1EC - Davicom DM9000E chipset, DM9601 driver, Max current 144mA. Unlike later, USB 1.1 devices using the same driver, this one works fine (see http://www.raspberrypi.org/phpBB3/viewtopic.php?t=45718)
 * Pluscom U2E-ADM8515 - ADMtek, Inc. AN8515 Ethernet chipset, pegasus driver, Max current 224 mA. Works with a Model "A" Pi if plugged into an external (maybe unpowered) 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

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


 * Davicom / Kontron
 * Kontron DM9601 (USB: 0fe6:9700) Cost $5 on Ebay, works OK with Dell laptop under WinXP & Debian. While it is advertised as USB 2.0, actually it is a USB 1.1 device, thus, its throughput is limited to 12 Mbps. Check with lsusb -v, field bcdUSB. Adaptor works on boot on R-Pi model A well enough for ping and NTP, but then crashes with "Kernel Bug at net/core/skbuff.c:127" immediately when file transfer begins.  TP1-TP2 voltage measured solid at 4.92 V. See also http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=39567&p=325003#p325003  The Linux DM9601 Driver is reported to be the problem here: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=34557  so until driver is updated, do not bother with this device.

USB Sound Cards
You will usually want the  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  and comment out the last line;. If you are not user pi you may need to add your username to the audio group thus:  (user pi usually belongs to this group anyway).


 * Creative
 * Sound Blaster Play!
 * Daffodil
 * USB Sound Adapter US01. Tested with low-cost headphone/microphone set via audacity (See notes at CPM-Spectre-Pi...DaffodilUSBSoundAdapter).
 * Edirol
 * UA-1A
 * GWCtech
 * AA1570 USB 7.1 Sound Card (aka Conrad AA 1570 7.1 SoundBox) - playback works fine, Recording stutters unless dwc_otg.speed=1 is set
 * Hercules
 * Gamesurround Muse XL (Pocket LT3)
 * Logilink
 * UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink
 * Logitech
 * Logitech G930 Wireless Gaming Headset with 7.1 Surround Sound (stereo works with ALSA, have not tried 7.1 Surround Sound)
 * NuForce uDAC-2
 * NuForce uDAC-2 Headphone Amplifier and USB DAC
 * Plantronics
 * Plantronics Stereo USB Adapter -01 (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter)
 * Terratec
 * 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
 * USB DAC PCM2704 Decoder

Databases of supported sound cards

 * http://wiki.linuxaudio.org/wiki/current_audio_gear
 * http://wiki.linuxmusicians.com/doku.php?id=hardware_matrix

Class compliant USB sound cards
Any USB1.1 audio interface that is class compliant should work with Linux, same goes for USB2.0 interfaces that adhere to the current USB audio standards. There are some interfaces that are supported in Linux while they do not comply to the standards because specific quirks have been added to the USB Linux drivers. To verify if your interface is supported search for a manual of your interface and check if it needs drivers to run under Windows/Mac. If the manual explicitely mentions no drivers are needed the interface is almost surely a class compliant device. When in doubt check the aforementioned databases.

Troubleshooting
If you encounter problems setting up your USB soundcard check the RPi Wiki article in the linuxaudio.org Wiki: http://wiki.linuxaudio.org/wiki/raspberrypi


 * Bulleted list item

USB 3G Dongles
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 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.
 * Huawei E1750
 * Huawei E173
 * Huawei E1820 Works on Raspbian with Sakis3G
 * Huawei E220 installation instructions
 * Huawei E353 HiLink Works on Raspbian
 * Huawei E160 (AT commands only)
 * Huawei E169 E620 E800 (12d1:1001) - works on Raspbian Wheezy, details here
 * Franklin U600 from Sprint / VirginMobile
 * Use usb_modeswitch and vendor 0x1fac and product 0x0150/0x0151
 * Digicom Internet Key 7.2 HSUPA MU372-L01
 * Vodafone MD950 (1dbc:0005) - is working on RPi (Raspbian Wheezy) but not out of the box, more details here.
 * Sierra Wireless 307 Works fine with Sakis3G script. The connection LED does not change its state after establishing a connection but the same behavior on a normal linux system.

USB IR Receivers

 * The FLIRC USB dongle allows the use of any remote control with your Raspberry Pi. Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion. Available from The Pi Hut and Buy Raspberry Pi Australia

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 this driver. Tested with Saorview (Irish DTT service), both HD & SD.
 * DVBSky
 * 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 here.
 * Sundtek
 * Sundtek MediaTV Digital Home
 * Sundtek MediaTV Pro
 * Sundtek SkyTV Ultimate
 * DVB-C, DVB-T, DVB-S/S2: digital TV works, streaming to Windows / Linux is no problem. Easy installation 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
 * Terratec
 * Terratec H7. Tested DVB-C with dvbv5 tools, part of v4l-utils, under Fedora 18 Remix and latest (April, 14 2013) DVB Kernel stack/drivers.
 * Generic
 * DVB-T USB Dongle (Silver casing), based on AF9015 chipset.
 * DVB-T USB Dongle, based on RTL2832 FC12 (HD/SD), IR was detected, but it is not tested.
 * 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 this page. It's in Hungarian, so google translate or equivalent is recommended. The remote also works. According to 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!

USB GPS devices
sudo killall gpsd; sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
 * 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:


 * 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, gtkterm and screen.

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 . Appears as , 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.
 * "PL2303HX USB to RS232 TTL Converter Adapter Module" on dx.com: http://dx.com/p/pl2303hx-usb-to-rs232-ttl-converter-adapter-module-164590
 * Based on the Prolific PL-2303HX chipset. Listed by lsusb as ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port. Appears as /dev/ttyUSBX with GUID dialout so your user has to be in that group. If not, sudo usermod -a -G dialout yourusername will add your user to the dialout group. Works great with screen /dev/ttyUSBX 115200 to connect from your workstation to your RPi.

Problem USB to Serial Adapters
HL-340
 * CH340 Chipset - Currently not supported by RPi but there is a patch of kernel code 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.

Working USB Multi-Card Readers

 * US Robotics USB 3.0 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


 * Generic (Nintendo branded)
 * identified as "14cd:8123 Super Top SD MMC Reader" (B)

Problem USB Multi-Card Readers

 * Generic
 * Card reader based on NEODIO ND3260-LD chip, identified as "0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader", fails after a few seconds with all access lights blinking. (B)

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 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 CPM-Spectre-Pi...USBtoParPrntAdapter for more info. and also a 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 instructions
 * Depends on libftdi1

Weather station

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

One-Wire

 * PCsensor
 * USB9097 (1a86:7523): works out of the box but issue with LAN after a few hours, no problem after a firmware update. Identify's as "QinHeng Electronics HL-340 USB-Serial adapter" Tested with raspbian/wheezy + domotiga & digitemp directly to USB port & 4 sensors connected via a '1-wire hub'. Claims to be 'fully replace DS9097, DS9490 of MAXIM'. Simple and cheap solution to measure temperature.

Touch Screen

 * ACER T230H touch screen
 * 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 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


 * Icy Box USB 3.0 to Dual 2.5"/3.5" SATA HDD Dock (IB-120StU3)
 * Externally powered dual HDD dock, USB 2 compatible.
 * Tested with Slackware ARM 14.0 and drives in both slots, just show up as separate SCSI disks.

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

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 [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 (Lazarus), Java, PHP, Python, Ruby (see [here] for installation).
 * If a big amount of Bricks is used, a powered USB Hub may be required.

Thermometers

 * TEMPer1 (id: 0c45:7401)
 * works out of the box on raspbian/wheezy with pcsensors library

Futronic
Single finger scanners Futronic FS80 and FS88 tested - they work well with Raspbian. Example of captured fingerprint here: [[Media:Futronic_fingerprint_example.png]]

To make it working deploy the Futronic libScanAPI on your Raspberry Pi (example code and instructions included): [[Media:ScanApi_armlinux_RPi_gnueabihf_gcc472_update1.zip ‎]]

PS2 / AT to USB Converters
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.
 * 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.

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 Switches
The Raspberry Pi does not have a power on/off switch as standard (it does have a reset switch), however some add on boards have been developed to cater for this need.
 * Pi Supply
 * The Pi Supply Switch v1.1 is an on/off power switch for the Raspberry Pi which includes a hard on and off switch and a soft shutdown switch for the Pi, making it easy to manage power on your Pi. They were recently successfully funded on Kickstarter.

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 adapter. 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 adapters known to work.

Pi Supply offers a 5.25V (+-0.25v) 1500mA power supply, manufactured specially for the Raspberry Pi to account for voltage drop due to the high current draw of the Raspberry Pi when compared to typical (phone charging etc.) duties. This is available in four varieties :
 * UK Raspberry Pi Power Supply
 * EU Raspberry Pi Power Supply
 * USA Raspberry Pi Power Supply
 * AUS Raspberry Pi Power Supply

The Pi Hut offers a 5V 1500mA power supply, manufactured specially for the Raspberry Pi. This is available in three varieties :
 * UK
 * EU
 * USA

Working power Adapters
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!
 * 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
 * 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
 * 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
 * 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 (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
 * i4 multi device charger - 3 interchangeable device tips + USB A socket (see it in use)
 * Innergie
 * 15 W Dual USB Adapter. Model: mMini AC15. Output: 5 V, 3 A (max per port), 15 W max. Specification sheet
 * ICIDU
 * PI-707730 charger 5V 2.1A, sometimes drops current to ~1.3A during heavy use, but still enough to power the Pi.
 * Kodak
 * 5 V 1 A TESA5G1-0501200
 * 5 V 1.0 A K20-AM
 * König
 * 5 V 1 A PSUP-GSM01
 * Kuanten
 * Model SSA051F050100USU, 1A output
 * 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
 * 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
 * 5 V 0.85 A SPN5504 Charger with Cable
 * Noname
 * 5 V 2.1 A KMS-AC09 4 port USB charger (B)
 * 5.2 V 1 A MW-3NU10GT - no cable, but this one works well (1m):
 * 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. Digi-key Link
 * Pi Supply
 * 5.25V 1.5A Raspberry Pi USB Power Supply Comes in 4 varieties for worldwide compatibility - UK, European (EU), American (USA) and Australian (AUS). Is of the detachable USB type so can double up as iPhone/Smartphone charger.
 * PortaPow
 * PortaPow UK Mains Wall Power Supply
 * PowerGen
 * PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. 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 Jaycar
 * Sony Ericsson
 * 5 V 0.7 A Charger CST-80
 * 5 V 0.85 A Greenheart&#153; Charger EP800. Typically provides 4.8 V at 0.85 A.
 * 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, 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 The Pi Hut's Raspberry Pi Store) (also from eBay)
 * Trisonic
 * TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5 V, 800 mA) $3 at Daiso U.S. stores.
 * TruePower
 * 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 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
 * 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 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:.

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! In any case, you may need to change config.txt hdmi_force_hotplug=0 to =1 if your display does not receive DVI signal (the analog output is likely active).

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 The Pi Hut's Raspberry Pi Store)
 * Other Variants
 * AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.
 * 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 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
The HDMI to VGA adapter for the Raspberry Piis now available at The Pi Hut.

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

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: HERE --by 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, 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 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 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.

Newark/element14 sells the "Pi-View" HDMI-VGA converter specifically for use with the Raspberry Pi. It does work although the small box gets warm and the video output isn't great (slightly fuzzy text, smaller screen area even with overscan enabled):

http://canada.newark.com/element14/piview/cable-assembly-hdmi-to-vga-adapter/dp/07W8937

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

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

 * RaspberryPiBoardVerifiedPeripherals