https://elinux.org/api.php?action=feedcontributions&user=ACc&feedformat=atomeLinux.org - User contributions [en]2024-03-19T07:44:29ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=319478RPi VerifiedPeripherals2014-03-18T14:11:16Z<p>ACc: </p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: ARM Development Boards]]<br />
[[Category: Broadcom]]<br />
[[Category: Development Boards]]<br />
[[Category: RaspberryPi]]<br />
[[Category: Education]]<br />
{{Template: RPi_Hardware}}<br />
<br />
<br />
'''A note about this page: For USB devices, please specify if they required a powered hub'''<br />
==Notes==<br />
<br />
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the [http://www.raspberrypi.org/downloads default Debian distribution] unless stated otherwise. A suggested suffix markup scheme is as follows:<br />
<br />
* (A) - Relates to model A production board<br />
* (B) - Relates to model B production board<br />
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different<br />
* No markup - relates to all production boards<br />
<br />
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=247]''<br />
<br />
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.<br />
<br />
==Power Usage Notes==<br />
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75&nbsp;V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}<br />
<br />
'''Model B Hardware Revisions and USB Power limits'''<br />
'''Hardware Revision 1.0'''<br />
The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximately 100&nbsp;mA. USB devices using more than 100&nbsp;mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700&nbsp;mA of which 200&nbsp;mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100&nbsp;mA, and typical 140&nbsp;mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100&nbsp;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.<br />
<br />
'''Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change'''<br />
This had the polyfuses removed, removing the 100&nbsp;mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012. {{Warning|}}Because the polyfuses have been removed, back feeding of the PI, by applying power via its normal USB output, can damage D 17 if triggered by an over-voltage, and so lead to consequential over-heating. This can be discovered by melts, scorching, smoke or worse.[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=34149]<br />
<br />
==Linux Driver Issues==<br />
Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=12097&start=76] [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5249&start=44]<br />
A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image.<br />
<br />
== Powered USB Hubs ==<br />
<br />
This section has been moved to a separate page. See [[RPi Powered USB Hubs]]<br />
<br />
== USB Remotes ==<br />
* The [http://www.pi-supply.com/product/flirc-usb-ir-remote-dongle-for-raspberry-pi/ 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 [http://www.pi-supply.com/ Pi Supply] and [http://thepihut.com/ The Pi Hut]<br />
<br />
* 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)<br />
<br />
* 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.<br />
<br />
* [http://www.amazon.com/gp/product/B005DKZTMG/ref=oh_details_o02_s00_i00 Logitech Wireless Touch Keyboard K400 with Built-In Multi-Touch Touchpad (920-003070)] - keyboard and touchpad work. Have not verified multi-touch features.<br />
<br />
* [http://www.ipazzport.com/02A.html iPazzport] mini 2.4&nbsp;GHz wireless keyboard and touchpad. <br />
<br />
* Pan.Code D1000 - 2.4GHz Wireless keyboard and touchpad.<br />
<br />
* [http://www.ortek.com/html/pdt_view.asp?area=46&cat=152&sn=76 PKB 1800] Wireless Smart Pad ad Mini Keyboard. The pad works as a mouse, but not multi touch features. The keyboard works.<br />
<br />
* [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] '''Rii''' Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01], and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]. Working perfectly, just plug & play.<br />
<br />
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)<br />
<br />
* [http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=6753651&CatId=3680# Exo Ultra U12-41310 Mini Keyboard] Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work.[https://github.com/thunderbirdtr/rs-pi-exo-keyboard Exo Installer script]<br />
<br />
== USB Keyboards ==<br />
<br />
This section has been moved to a separate page. See [[RPi USB Keyboards]]<br />
<br />
== USB Mouse devices ==<br />
<br />
This section has been moved to a separate page. See [[RPi USB Mouse devices]]<br />
<br />
== USB Real Time Clocks ==<br />
*Cymbet<br />
** Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123)<br />
Device information at http://www.cymbet.com/pdfs/DS-72-22.pdf<br />
Code to access the RTC from Linux: https://github.com/owendelong/Cymbet-RTC<br />
Does not require a powered hub.<br />
<br />
==Internet==<br />
=== USB Wi-Fi Adapters ===<br />
This section has been moved to a separate page. See [[RPi USB Wi-Fi Adapters]]<br />
<br />
=== USB Bluetooth adapters ===<br />
This section has been moved to a separate page. See [[RPi USB Bluetooth adapters]]<br />
<br />
=== USB Ethernet adapters ===<br />
This section has been moved to a separate page. See [[RPi USB Ethernet adapters]]<br />
<br />
=== USB 3G Dongles ===<br />
==== Huawei ====<br />
* E1750<br />
* E173<br />
* E1820 Works on Raspbian with Sakis3G<br />
* E220 [http://raspberry-at-home.com/installing-3g-modem/ installation instructions]<br />
* E353 HiLink Works on Raspbian<br />
* E160 (AT commands only)<br />
* E169, E620, E800, (12d1:1001) - works on Raspbian Wheezy, [https://github.com/sk-vpohybe/stopa-monitor/wiki/3G-modem-Huawei-E169-E620-E800 details here]<br />
==== Sierra Wireless ====<br />
* AirCard 250u works with wvdial/network manager<br />
* AirCard 320u (0f3d:68aa) works in WWAN mode, driver provided by the kernel. Tested on Arch.<br />
** Kernel version 3.10 has a bug that causes the WWAN interface to never be in ''RUNNING'' state (no carrier). Use 3.6 kernel instead.<br />
** AT command guide can be found [http://mycusthelpadmin.net/SIERRAWIRELESS/_cs/AnswerDetail.aspx?aid=44 here]<br />
** for GPS to work you have to enable it. First, setup the modem (guide [http://whirlpool.net.au/wiki/hw_model_1210 here]) and after that enable NMEA output by passing ''nmea=1'' parameter to the ''sierra'' kernel module. '''Warning! Enabling NMEA output may cause the modem to drop connections / restart itself'''. This is probably related to higher power drain. This may not be the issue when a powered hub is used.<br />
* 307 Works fine with Sakis3G script. The connection LED does not change its state after establishing a connection but the same behaviour on a normal linux system.<br />
<br />
==== ZTE ====<br />
* ZTE MF190S<br />
* ZTE MF626 <br>Works fine with Sakis3G script. You can use force it to ALWAYS be in modem mode (See here: http://forums.whirlpool.net.au/archive/1205127 ), or use usb-modeswitch ( as described here http://blog.christophersmart.com/2009/05/21/telstra-nextg-working-with-mf626-usb-modem/ )<br />
* ZTE MF628 Tested with Sakis3g using --noprobegsm, use usb_modeswitch to get ID 19d2:0031.<br />
==== Others ====<br />
* Franklin U600 from Sprint / VirginMobile<br />
** Use usb_modeswitch and vendor 0x1fac and product 0x0150/0x0151<br />
* Digicom Internet Key 7.2 HSUPA '''MU372-L01''' [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MU372L01]<br />
Tested on Raspbian and Archlinux. Detected as 230d:0001. Works with cdc_acm driver. Install usb_modeswitch.<br />
There are 2 "com ports"( /dev/ttyACM0 and /dev/ttyACM1 ) . Tested with Network Manager.Works also perfectly with SAKYS3G [http://www.sakis3g.org/] tools (!! led is always off !!) and wvdial. A working wvdial.conf: http://ubuntuforums.org/showpost.php?p=10361881&postcount=28 . (for example for Vodafone IT , replace Init3 with this: Init3 = AT+CGDCONT=1,"IP","web.omnitel.it" and replace line Modem = /dev/ttyUSB0 with Modem = /dev/ttyACM1 ) and run with wvdial voda .<br />
* Vodafone MD950 (1dbc:0005) - is working on RPi (Raspbian Wheezy) but not out of the box, [https://github.com/sk-vpohybe/stopa-monitor/wiki/3G-modem-Vodafone-MD950 more details here].<br />
<br />
== USB Sound Cards ==<br />
You will usually want the <code>alsa</code> package for sound. In the Debian image for Raspberry Pi (and possibly other distributions) USB sound cards are prevented from loading as the first sound card, which can be an annoyance if it's the only device you have. To disable this behaviour edit <code>/etc/modprobe.d/alsa-base.conf</code> and comment out the last line; <code>options snd-usb-audio index=-2</code> . If you are not user ''pi'' you may need to add your username to the ''audio'' group thus: <code>sudo adduser yourusername audio</code> (user ''pi'' usually belongs to this group anyway).<br />
<br />
* '''Creative'''<br />
** [http://asia.creative.com/products/product.asp?category=1&subcategory=207&product=17892 Sound Blaster Play!]<br />
* '''Daffodil'''<br />
** [http://www.amazon.co.uk/gp/product/B002FI7GWK/ref=oh_details_o03_s00_i00 USB Sound Adapter US01]. Tested with low-cost headphone/microphone set via ''audacity'' (See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/DaffodilUSBSoundAdapter.html CPM-Spectre-Pi...DaffodilUSBSoundAdapter]).<br />
* '''Edirol'''<br />
** [http://www.roland.com/products/en/UA-1A/ UA-1A]<br />
* '''GWCtech'''<br />
** [http://www.gwctech.com/product3.asp?listid=3&id=4&subid=10&pid=788&typeid=96 AA1570 USB 7.1 Sound Card] (aka [http://www.conrad.com/ce/en/product/872990/USB-SoundBox-71 Conrad AA 1570 7.1 SoundBox]) - playback works fine, Recording stutters unless dwc_otg.speed=1 is set<br />
* '''Hercules'''<br />
** [http://www.hercules.com/fr/Cartes-Son/bdd/p/123/gamesurround-muse-xl-pocket-lt3/ Gamesurround Muse XL (Pocket LT3)]<br />
* '''Logilink'''<br />
** [http://www.logilink.de/showproduct/UA0053.htm?seticlanguage=en UA0053 USB Soundcard with Virtual 3D Soundeffects LogiLink]<br />
* '''Logitech'''<br />
** [http://www.amazon.com/Logitech-Wireless-Gaming-Headset-Surround/dp/B003VANOFY/ref=sr_1_1?ie=UTF8&qid=1358114107&sr=8-1&keywords=g930 Logitech G930 Wireless Gaming Headset with 7.1 Surround Sound] (stereo works with ALSA, have not tried 7.1 Surround Sound)<br />
* '''NuForce uDAC-2'''<br />
** [http://www.nuforce.com/hp/products/iconudac2/index.php NuForce uDAC-2 Headphone Amplifier and USB DAC]<br />
* '''Plantronics'''<br />
** [http://www.ebay.com/itm/Genuine-New-Plantronics-External-USB-Audio-Soundcard-New-Sealed-/300845395889?pt=US_Sound_Card_External&hash=item460bc86fb1 Plantronics Stereo USB Adapter -01] (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter)<br />
* '''SpeedLink'''<br />
** [http://www.speedlink.com/?p=2&cat=17&pid=23371&paus=1&act_lang=en VIGO USB Soundcard, black] - Device ID: 0d8c:000e ("C-Media Electronics, Inc. Audio Adapter"). Working, but on Raspbian 3.6.11 it fills up kern.log with "cm109_urb_irq_callback: urb status -71" messages. To prevent this, you can insert `:msg, contains, "cm109_urb_irq_callback" ~´ as first rule into /etc/rsyslog.conf.<br />
* '''Terratec'''<br />
** [http://www.terratec.net/fr/produkte/Aureon_Dual_USB_12339.html Aureon Dual USB] (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers)<br />
* '''Texas Instruments PCM2704'''<br />
** [http://dx.com/p/usb-dac-pcm2704-decoder-red-172991?Utm_rid=24958662&Utm_source=affiliate USB DAC PCM2704 Decoder]<br />
<br />
=== Databases of supported sound cards ===<br />
* http://wiki.linuxaudio.org/wiki/current_audio_gear<br />
* http://wiki.linuxmusicians.com/doku.php?id=hardware_matrix<br />
<br />
=== Class compliant USB sound cards ===<br />
<br />
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.<br />
<br />
=== Troubleshooting ===<br />
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<br />
<br />
* Bulleted list item<br />
<br />
== USB IR Receivers==<br />
* The [http://www.pi-supply.com/product/flirc-usb-ir-remote-dongle-for-raspberry-pi/ 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 [http://www.pi-supply.com/ Pi Supply], [http://thepihut.com/ The Pi Hut] and [http://www.buyraspberrypi.com.au Buy Raspberry Pi Australia]<br />
<br />
* SMK Manufacturing, Inc. eHome Infrared Receiver (Works out of the box with OpenELEC)<br />
<br />
== USB Radio devices==<br />
*FM Radio<br />
** ADS InstantFM Music - FM radio tuner works fine under Debian.<br />
<br />
== USB TV Tuners and DVB devices==<br />
*August<br />
**DVB-T205, based on rtl2832u chipset, worked with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver] on older 3.2 kernel. Couldn't get same device working reliably on current kernel. (On the older 3.2 kernel it worked with Saorview (Irish DTT service), both HD & SD.)<br />
*DVBSky<br />
**[http://dvbsky.eu/Products_S860.html Mystique SaTiX-S2 Sky USB]: Scanning/watching SD and HD works via vdr and streamdev plugin, watching on the Raspberry Pi directly is laggy as hell. DVB-USB and I2C support must be enabled in the kernel. Needs drivers/firmware from [http://dvbsky.eu/Support.html here].<br />
*Sundtek<br />
**Sundtek MediaTV Digital Home<br />
**Sundtek MediaTV Pro<br />
**Sundtek SkyTV Ultimate<br />
**[http://shop.sundtek.de DVB-C, DVB-T, DVB-S/S2]: digital TV works, streaming to Windows / Linux is no problem. Easy installation [http://support.sundtek.com/index.php/topic,4.0.html English]<br />
*Hauppauge<br />
** Hauppauge NOVA-T Stick (Revision 70xxx) DiBcom DiB0700 chipset, requires powered hub.<br />
** Hauppauge NOVA-TD Stick (Revision 52xxx) DiBcom DiB0700 chipset, requires powered hub.<br />
** Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer, tested Digital OTA with MythTV)<br />
** Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian)<br />
*K-World<br />
** 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.<br />
*Technisat<br />
**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<br />
* Terratec<br />
** Terratec H7. Tested DVB-C with [http://git.linuxtv.org/v4l-utils.git dvbv5 tools, part of v4l-utils], under [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix Fedora 18 Remix] and latest (April, 14 2013) [http://git.linuxtv.org/media_build.git DVB Kernel stack/drivers].<br />
*Generic<br />
** [http://www.onsources.com/product_images/a/757/watch_and_record_digital_tv_dongle__44323_zoom.jpg DVB-T USB Dongle (Silver casing)], based on AF9015 chipset.<br />
** [http://www.electrodepot.fr/media/catalog/product/cache/1/image/500x/9df78eab33525d08d6e5fb8d27136e95/P926993.jpg DVB-T USB Dongle], based on RTL2832 FC12 (HD/SD), IR was detected, but it is not tested.<br />
** [http://obrazki.elektroda.pl/8081115000_1317678968.jpg HDTV USB DVB-T] dongle, based on IT9135. This tuner comes in two revisions. Revision is printed on PCB.<br />
*** rev. 1.0; should work with 3.2+ kernel, need confirmation.<br />
*** rev. 2.0; works with kernel 3.6.11, without a powered hub. This tuner also requires a firmware (dvb-usb-it9135-02.fw) which can be downloaded from [http://logout.hu/bejegyzes/azbest/usb_dvb-t_tuner_it9135_rev2/hsz_1-50.html this page]. It's in Hungarian, so google translate or equivalent is recommended. The remote also works.<br>According to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=29141 this post], there may be issues on some software configurations when using ''omxplayer''.<br />
<br />
== USB Video / Frame grabbers==<br />
<br />
* EasyCAP DC60 (STK1160 chip) - works out of the box for older versions of Raspbian. If you're getting grey stripes see this [http://raspberry-at-home.com/video-grabber-for-raspberry-pi/ tutorial]<br />
* EasyCAP (UTV007 Fushicai chip) - works after driver compilation - see instructions at [http://raspberry-at-home.com/video-grabber-for-raspberry-pi/ this link]. remember to use older Raspbian version. <br />
* Hauppage HVR 1900<br />
<br />
== USB Webcams ==<br />
<br />
This section has been moved to a separate page. See [[RPi USB Webcams]]<br />
<br />
== USB GPS devices ==<br />
<br />
*Columbus<br />
** Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients)<br />
*Royaltek<br />
**Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter (Prolific pl2303-chip)<br />
*Garmin<br />
**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<br />
*GlobalSat<br />
**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:<br /><pre>sudo killall gpsd; sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock</pre><br />
**GlobalSat BU-353-S4 supports two protocols: NMEA, and SiRF v4. NMEA works fine, but SiRF v4 isn't compatible with "gpsd"'s SiRF v3 interpreter, resulting in a greatly reduced data rate (as low as four location fixes per hour). To keep "gpsd"'s autoconfiguration from putting the receiver in SiRF mode, you'll need to pass the "-b" flag when starting "gpsd".<br />
<br />
*Wintec<br />
**WBT-200: No problem on Debian<br />
*Holux<br />
**Holux M-215: Works fine on Arch, uses Silicon Labs CP210x RS232 serial adaptor driver<br />
*Bluenext<br />
**Bluenext BN903S: No problem on Debian image (19-04-2012).<br />
<br />
* U blox NEO 6 - works well, connects via GPIO (serial console). Info [http://diydrones.com/profiles/blogs/how-to-connect-3dr-gps-ublox-to-raspberry-pi here] and [https://github.com/petervojtek/diy/wiki/GPS-U-blox-NEO-6-with-Raspberry-Pi here].<br />
<br />
== USB UART and USB to Serial (RS-232) adapters ==<br />
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.<br />
<br />
===Working USB to Serial Adapters===<br />
*'''FTDI'''<br />
**FT232 chip based adapters works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio.<br />
**FT2232D dual RS232/FIFO works (used in various JTAG devices)<br />
<br />
*'''Prolific'''<br />
**PL2303 chip based adaptors works fine on latest Debian tested with ''minicom'', ''gtkterm'' and ''screen''.<br />
<br />
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.<br />
<br />
*"Best Connectivity" (Possibly also sold under the "Newlink HQ" or "Kenable HQ" labels)<br />
**FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by ''lsusb'' as <code>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</code>. Appears as <code>/dev/ttyUSB0</code>, and requires the user to be a member of the ''dialout'' group (which ''pi'' is for ''Raspbian Wheezy''). Initially tested using an old RS Datalinker setup in "loopback" mode via ''microcom'' upto 9600 baud, and ''gtkterm'' after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently ''gtkterm'' was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.<br />
* "PL2303HX USB to RS232 TTL Converter Adapter Module" on dx.com: http://dx.com/p/pl2303hx-usb-to-rs232-ttl-converter-adapter-module-164590<br />
** Based on the Prolific PL-2303HX chipset. Listed by ''lsusb'' as <tt>ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port</tt>. Appears as <tt>/dev/ttyUSBX</tt> with GUID <tt>dialout</tt> so your user has to be in that group. If not, <tt>sudo usermod -a -G dialout yourusername</tt> will add your user to the <tt>dialout</tt> group. Works great with <tt>screen /dev/ttyUSBX 115200</tt> to connect from your workstation to your RPi.<br />
<br />
===Problem USB to Serial Adapters===<br />
'''HL-340'''<br />
*CH340 Chipset - '''Currently not supported by RPi''' but there is a patch of kernel code [http://tiagovaz.wordpress.com/2008/01/04/using-a-hl-340-usb-serial-adapter-against-2623-linux-kernel/ here], but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work.<br />
<br />
== USB Multi-Card Readers ==<br />
<br />
=== Working USB Multi-Card Readers ===<br />
* US Robotics USB 3.0 All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously<br />
** 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<br />
<br />
*'''Generic''' (Nintendo branded)<br />
**identified as "14cd:8123 Super Top SD MMC Reader" (B)<br />
<br />
=== Problem USB Multi-Card Readers ===<br />
<br />
*'''Generic'''<br />
**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)<br />
<br />
== Other, exotic USB devices ==<br />
=== Joysticks / Joypads ===<br />
*'''Microsoft'''<br />
**Xbox360 Controller (045e:028e): works. Tested with archlinux, connected to an USB Hub, used as "mouse" in X, package xf86-input-joystick<br />
<br />
*'''Logitech'''<br />
** Dual Action: works, connected directly to the Pi.<br />
<br />
*'''Ion'''<br />
** Go Pad: works. Tested on Raspbian Wheezy (release 2014-01-07), connected to on-board USB port (Model B rev. 2).<br />
<br />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<br />
*'''Speedlink SL-7430-SGY'''<br />
**USB numpad (04d9:1603, HT82M99E Holtek chip inside): works. Tested with Raspbian “wheezy”<br />
*'''GreenAsia Inc. ([http://img.dxcdn.com/productimages/sku_26083_1.jpg USB 18-Key Silicone Numeric Keypad])'''<br />
**USB numpad (0e8f:0022): works. Tested with Raspbian “wheezy”<br />
<br />
=== USB to Parallel Port/Printer Adapters ===<br />
*'''Prolific'''<br />
**PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under [[RPi_Distributions#RISC_OS| RISC OS Raspberry Pi]] with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBtoParPrntAdapter.html CPM-Spectre-Pi...USBtoParPrntAdapter] for more info. and also a [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/WheezyCUPS.html CUPS/Wheezy installation guide])<br />
<br />
=== USB to IDE/SATA ===<br />
*'''JMicron Technology'''<br />
** JM20337 USB to SATA/PATA Combo Bridge (152d:2338) - works on Raspbian and Arch. The hard drive requires an external power supply.<br />
*'''Nippon Labs'''<br />
** 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<br />
<br />
=== CAN Bus ===<br />
*PEAK-System (www.peak-system.com)<br />
**PCAN-USB using the driver (kernel module) from http://www.peak-system.com/fileadmin/media/linux/index.htm<br />
<br />
=== Home automation ===<br />
*Tellstick (www.telldus.com), installation [[R-Pi_Tellstick_core|instructions]]<br />
**Depends on libftdi1<br />
<br />
=== Weather station ===<br />
*Oregon Scientific WMRS-200 : Work out of the box (tested with Raspbian & wview)<br />
<br />
=== One-Wire ===<br />
*'''PCsensor'''<br />
**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.<br />
<br />
=== Touch Screen ===<br />
*ACER T230H touch screen [http://support.acer.com/acerpanam/monitor/2009/acer/t230h/t230hnv.shtml]<br />
**USB TS identifies as "Quanta Computer, Inc. Optical dual-touch panel", module hid_quanta<br />
**Seems to draw over 200&nbsp;mA from USB!<br />
*SainSmart 3.2 touch screen [http://www.sainsmart.com/sainsmart-3-2-tft-lcd-display-touch-panel-pcb-adapter-sd-slot-for-arduino-2560.html]<br />
**320*240<br />
**3.2 inch<br />
**SSD1289:240 RGB x 320 TFT Drive<br />
**Video: Raspberry Pi with a 3.2" TFT with Touch control [http://www.youtube.com/watch?feature=player_embedded&v=QKxmPdUoNQU]<br />
**Tutorial: Raspberry Pi with a 3.2″ TFT with Touch control [http://marks-space.com/2013/05/23/raspberry-pi-with-a-3-2-tft-with-touch-control/]<br />
<br />
=== Floppy Disk Drive ===<br />
*Samsung USB Floppy Drive SFD-321U/HP<br />
**I suppose a floppy drive might be considered exotic nowadays!<br />
**LSUSB lists it as Samsung Electro-Mechanics Co. Floppy Disk Drive<br />
**Only tried connected to a powered USB hub, as the drive is labelled 5&nbsp;V at 0.5&nbsp;A on a Raspberry Pi running Debian Wheezy.<br />
**tail -f /var/log/syslog looking for mount device when plugged in, came up as SDA in testing.<br />
**sudo mkdir /media/floppy<br />
**sudo mount /dev/sda /media/floppy<br />
**Contents of floppy now available in /media/floppy<br />
**To remove drive, ensure no sessions have the floppy directory as the current working directory.<br />
**sudo umount /media/floppy<br />
*Y-E Data model HU-35EF<br />
**Requires a powered hub and manual mounting/unmounting like the Samsung drive above.<br />
<br />
=== USB Missile Launcher ===<br />
*USB Missile Launcher / Rocket Launcher sold in UK by Marks and Spencer, but it is also sold under a range of other names.<br />
**USB ID 1130:0202 Tenx Technology, Inc. Use apt-get install pymissile (python code) and there is C code at [http://sourceforge.net/projects/usbmissile/ usbmissile from Source Forge]<br />
<br />
=== USB Docking Stations ===<br />
*StarTech USB 3.0 to Dual 2.5"/3.5" SATA HDD Dock (SATDOCK2U3GB)<br />
**This is an externally powered dual sata HDD docking station, which has USB2.0 compatibility with the Raspberry Pi. <br />
**Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168<br />
<br />
*Icy Box USB 3.0 to Dual 2.5"/3.5" SATA HDD Dock (IB-120StU3)<br />
**Externally powered dual HDD dock, USB 2 compatible.<br />
**Tested with Slackware ARM 14.0 and drives in both slots, just show up as separate SCSI disks.<br />
<br />
=== USB RFID Reader ===<br />
*Unbranded 125&nbsp;kHz EM4100 RFID reader from eBay sellers (< £7), the one with a Windows logo on (easily scratches off for Linux users).<br />
**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.<br />
**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.<br />
<br />
=== JTAG ===<br />
* FTDI2232D dual RS232/FIFO based JTAG (e.g. SheevaPlug JTAGKey USB-ID 9e88:9e8f)<br />
** works using the Raspberry Pi as a development host<br />
<br />
=== Tinkerforge Bricks and Bricklets (http://www.tinkerforge.com) ===<br />
* Read out sensors and control motors over USB with open source hardware.<br />
* Tested with the brickd_armhf.deb from [[http://www.tinkerforge.com/doc/Downloads.html#tools: here]] with:<br />
** sudo apt-get install libusb-1.0-0 libudev0<br />
** wget http://download.tinkerforge.com/tools/brickd/linux/brickd_linux_latest_armhf.deb<br />
** sudo dpkg -i brickd_linux_latest_armhf.deb<br />
* Tested languages: C/C++, C# (mono), [[Free Pascal]] ([[Lazarus]]), Java, PHP, Python, Ruby (see [[http://www.tinkerforge.com/doc/Software/API_Bindings.html: here]] for installation).<br />
* If a big amount of Bricks is used, a powered USB Hub may be required.<br />
<br />
=== Thermometers ===<br />
<br />
* TEMPer1 (id: 0c45:7401)<br />
** works out of the box on raspbian/wheezy with [https://github.com/petervojtek/usb-thermometer pcsensors library]<br />
<br />
=== Fingerprint Scanners ===<br />
==== Futronic ====<br />
<br />
Single finger scanners Futronic FS80 and FS88 tested - they work well with Raspbian. Example of captured fingerprint here: [[Media:Futronic_fingerprint_example.png]]<br />
<br />
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 ]]<br />
<br />
== PS2 / AT to USB Converters ==<br />
<br />
* 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.<br />
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. <br />
<br />
'''Tested PS2/AT keyboards'''<br />
<br />
All above tested with the famous "blue cube" on a powered USB hub.<br />
<br />
*IBM Model F (please note requires an additional AT to PS2 converter)<br />
*Dell AT101w<br />
*Northgate Ominikey Ultra T (please note requires an additional AT to PS2 converter)<br />
<br />
* 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller<br />
** Working: Ipex RT215KTW PS/2 keyboard<br />
** 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.)<br />
<br />
== Power Switches ==<br />
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.<br />
<br />
* The [http://www.pi-supply.com/product/pi-supply-raspberry-pi-power-switch/ Pi Supply Switch] 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.<br />
* '''RemotePi Board'''<br />
** The [http://msl-digital-solutions.myshopify.com/products/remotepi-board RemotePi Board] is an intelligent infrared remote controlled power switch add-on board for the Raspberry Pi. It allows to switch power on and off using any button (configurable in learning mode) of an existing standard IR remote. Power is only cut after notifying the OS and giving it time to shut-down. It is mainly intended to remote control (using LIRC) and power off/on a mediacenter system. i.e OpenELEC, Raspbmc, XBian.<br />
<br />
== Power adapters ==<br />
The Raspberry Pi uses a standard Micro USB (type B) power connector, which runs at 5&nbsp;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.<br />
<br />
<br />
===Working power Adapters===<br />
There is now a 5.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. <br> Available in UK, EU, USA and AU varieties from [http://thepihut.com/collections/raspberry-pi-power-supplies Pi Hut] and [http://www.pi-supply.com/product-category/raspberry-pi-power-supplies/ Pi Supply]<br />
<br />
<br />
* '''Adafruit'''<br />
** 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]<br />
* '''AlcaPower'''<br />
** 5&nbsp;V 2.5&nbsp;A Model AP5A - Charger/switching with 7 connectors(also Microusb)<br />
* '''Ansmann'''<br />
** Dual USB charger slim, Model-Nr. 1201-0001<br />
* '''Apple'''<br>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!<br />
** 5&nbsp;V 2.1&nbsp;A USB charger for iPad2, model A1357<br />
** 5&nbsp;V 1.0&nbsp;A USB Charger for iPod<br />
** 5&nbsp;V 1.0&nbsp;A USB Charger for iPhone 4<br />
* '''Amazon'''<br />
** 5&nbsp;V 0.85&nbsp;A USB charger for Kindle<br />
** 5&nbsp;V 2&nbsp;A Mains to USB A adaptor, Branded "CostMad" <br />
* '''Asus'''<br />
** 5&nbsp;V 2.0&nbsp;A USB charger for Google Nexus 7<br />
* '''Bandridge'''<br />
** 5&nbsp;V 1.0&nbsp;A Mobile Phone Charger (Model: BPC3102EC)<br />
* '''Belkin'''<br />
** 5&nbsp;V 2.6&nbsp;A 4 port Ultra-Slim Desktop hub (Model F4U040) (Raspberry Pi running from USB hub port)<br />
** 5&nbsp;V 2.5&nbsp;A 4 port USB Hub (Model F5U404) (Raspberry Pi running from USB hub port)<br />
** 5&nbsp;V 3.5&nbsp;A 7 port USB 2.0 Mobile Powered Hub (Model F4U018) (Raspberry Pi running from USB hub port)<br />
** 5&nbsp;V 3.5&nbsp;A 7 port USB Hub (Model F5U706) (Raspberry Pi running from USB hub port)<br />
** Mini Surge Protector Dual USB Charger (Model BZ103050-TVL)<br />
** Universal USB Wall Charger (5&nbsp;V 1&nbsp;A) (Model F8Z222uk)<br />
* '''Blackberry'''<br />
** Charger for Pearl Flip 8220, Bold 9600 (B)<br />
** Charger for Tour 9630<br />
** 5V 1.8A "Folding Blade" Micro USB Tablet charger Part #: HDW-34724-001 Model #: AD8213HF (works with model A w/ camera + Wifi)<br />
** 5&nbsp;V 0.7&nbsp;A Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003 (B)<br />
** 5&nbsp;V 750&nbsp;mA Model RIM-C-0004aDUUUC-001, RIM Part Number HWD-24481-001 (comes with Blackberry 9300)<br />
** 5&nbsp;V 750&nbsp;mA Model RIM-C-0004ADUUS-001 035D, Single port plug. (Tested with USB B to Micro USB cable from Logitech H760 Headset)<br />
** 5&nbsp;V 2&nbsp;A Model PSAC10R-050QT, RIM Part Number HDW-34725-001<br />
** 5&nbsp;V 550&nbsp;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.<br />
* '''Deal Extreme'''<br />
** [http://dx.com/p/5v-2a-regulated-switching-power-supply-110-220v-94518 S-10-5 5&nbsp;V 2&nbsp;A Regulated Switching Power Supply (110~220&nbsp;V)] (DIY: requires additional micro-USB connector and wiring)<br />
* '''Dell'''<br />
** USB Hub integrated in Dell monitors (B)<br />
* '''DLO'''<br />
** 5 V 1.0 A PowerBug (Model: SP05001000-A) Powers Pi, Wifi dongle and Webcam<br />
* '''The FX Factory'''<br />
** 5&nbsp;V 1&nbsp;A (1.2&nbsp;A max) AC Travel Charger Model KJ-USB Mains. Typically provides 4.9&nbsp;V at 1&nbsp;A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref><br />
** 5&nbsp;V 2x1&nbsp;A Dual Charger Model TR9202-MICRO. Typically provides 4.8&nbsp;V at 1&nbsp;A per output. Can be used to power a Pi and, via a separate cable, a USB 4-port hub <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/OtherTestedPSUs.html#FX_Factory_Dual_Charger_TR9202-MICRO http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/OtherTestedPSUs.html#FX_Factory_Dual_Charger_TR9202-MICRO]</ref><br />
* '''Garmin'''<br />
** 5&nbsp;V 1&nbsp;A charger (Model: PSA105R-050Q) supplied with Garmin Edge 800 GPS. Requires a USB-A to MicroUSB-B cable. Belkin 6&nbsp;ft cable (F3U151B06) works.<br />
* '''Gembird'''<br />
** 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).<br />
* '''Globe Electric'''<br />
** 2-Outlet Tap with Surge Protection and 2 USB Chargers ([http://globe-electric.com/product/2-outlet-tap-with-surge-protection-and-2-usb-chargers-grounded-white/ 46082]). Rated at 1000&nbsp;mA. 120&nbsp;V systems only.<br />
* '''Griffin'''<br />
** Power Block Model P2417. 5&nbsp;V 2.1&nbsp;A<br />
** Power Block Model P1190R2 Two USB 5&nbsp;V Outputs, 1&nbsp;A each<br />
* '''Hama'''<br />
** 1000&nbsp;mA Travel Charger for Micro USB universal (barcode nr: 4 007249 935854)<br />
* '''Hartig + Heiling GmbH & Co. KG'''<br />
** H+H SN 6 USB<br />
* '''HP'''<br />
** 5.3&nbsp;V 2&nbsp;A Charger for HP Touchpad (B)<br />
* '''HTC'''<br />
** 5&nbsp;V 1&nbsp;A TCP-300 USB phone charger (B)<br />
** 5&nbsp;V 1&nbsp;A TC B250 USB charger (HTC R/N: 79H00096-00M)<br />
** 5&nbsp;V 1&nbsp;A TC E250 USB charger (HTC R/N: 79H00098-02M)<br />
* '''i-box (Philex Electronic Ltd)'''<br />
** 5&nbsp;V 1&nbsp;A USB charger, 1 USB socket, no USB lead supplied, Model: 76971HS/02 (available from ASDA and others in the UK) (B).<br />
* '''IDAPT'''<br />
** [http://www.idaptweb.com/universal_chargers/i4/ i4 multi device charger] - 3 interchangeable device tips + USB A socket ([https://twitter.com/andrewmk/status/226057302879375361 see it in use])<br />
* '''Innergie'''<br />
**15&nbsp;W Dual USB Adapter. Model: mMini AC15. Output: 5&nbsp;V, 3&nbsp;A (max per port), 15&nbsp;W max. [http://www.myinnergie.com/DuoPowerKit/specification.aspx Specification sheet]<br />
* '''ICIDU'''<br />
** PI-707730 charger 5V 2.1A, sometimes drops current to ~1.3A during heavy use, but still enough to power the Pi.<br />
* '''Kodak'''<br />
** 5&nbsp;V 1&nbsp;A TESA5G1-0501200<br />
** 5&nbsp;V 1.0&nbsp;A K20-AM<br />
* '''König'''<br />
** 5&nbsp;V 1&nbsp;A PSUP-GSM01<br />
* '''Kuanten'''<br />
** Model SSA051F050100USU, 1A output<br />
* '''LG'''<br />
** 4.8&nbsp;V 1&nbsp;A Travel Adapter<br />
** 5.1&nbsp;V 0.7&nbsp;A Travel Adapter (Model: STA-U34WVI)<br />
** 5.1&nbsp;V 0.7&nbsp;A Travel Adapter (Model: STA-U12ER)<br />
* '''Logic'''<br />
** 4 port USB Hub (Model LP4HUB10). (Raspberry Pi running from USB Hub port, red power line (+5&nbsp;V) inside hub cut) (B)<br />
*'''LogiLink'''<br />
**5&nbsp;V 2.1&nbsp;A Switching power supply, model PA0040 (B)<br />
* '''Logitech'''<br />
** 5&nbsp;V 1&nbsp;A SDC115-USB Remote Control Charger and cable<br />
* '''Maplin Electronics'''<br />
** 5&nbsp;V 1&nbsp;A dual USB power supply, model number H25B-MT-K2<br />
** Micro USB Power Supply N19HX<br />
* '''Medion'''<br />
** 5&nbsp;V 1&nbsp;A USB power supply for OYO ebook reader<br />
* '''Microsoft'''<br />
*** Zune Zune AC Adapter v2<br />
* '''ModMyPi'''<br />
** [https://www.modmypi.com/shop/5v-2A-modmypi-raspberry-pi-power-supply 5.25V 2A HQ Raspberry Pi USB Power Supply] (Detachable USB) [5.01 - 5.07V @ T1/T2 with Wifi dongle and Wireless Mouse/Keyboard on RPi USB ports]<br />
* '''Motorola'''<br />
** [http://www.amazon.com/Motorola-Micro-USB-Home-Travel-Charger/dp/B004EYSKM8/ 5&nbsp;V 0.85&nbsp;A SPN5504 Charger with Cable]<br />
* '''Noname'''<br />
** 5&nbsp;V 2.1&nbsp;A KMS-AC09 4 port USB charger (B) [http://www.miniinthebox.com/kms-ac09-universal-ac-adapter-for-ipad-ipad-2-iphone-white_p208568.html]<br />
** 5.2&nbsp;V 1&nbsp;A MW-3NU10GT - no cable, but this one works well (1m): [http://www.amazon.de/gp/product/B005L8VELA]<br />
** 5&nbsp;V 1&nbsp;A Model H-IP008 Serial No. H10T80L068<br />
** 5&nbsp;V 1&nbsp;A Travel charger Model MSH-TR-018A [http://www.akizz.com/catalog/product/chargeur-secteur-rapide-de-voyage-70/galaxy-duos-s7562 reseller1], [http://www.sepdistribution.fr/produit-2496.html reseller2]<br />
* '''Novatel Wireless'''<br />
** 5&nbsp;V 1.05&nbsp;A Charger, model number SSW-1811, packaged with Verizon Wireless MiFi device<br />
* '''Orange'''<br />
** 5&nbsp;V 0.7&nbsp;A Charger for Orange San Francisco<br />
* '''Palm'''<br />
** 5&nbsp;V 1&nbsp;A Charger for Palm Pixi+ (B)<br />
* '''Pantech'''<br />
** 5.0&nbsp;V 1&nbsp;A CNR USB with LG DLC100 micro USB cable<br />
* '''Petzl'''<br />
** 5.0&nbsp;V 1&nbsp;A Charger that came with the Tikka core2 XP<br />
* '''Phihong'''<br />
** Switching Power Supply. Model: PSAC09R-050. Output: 5&nbsp;V, 1.8&nbsp;A, microUSB. [http://www.digikey.com/product-detail/en/PSAC09R-050/993-1109-ND/2635771 Digi-key Link]<br />
* '''Pi Supply'''<br />
** [http://www.pi-supply.com/product/uk-micro-usb-raspberry-pi-power-supply-5v-1500ma/ 5.25V 1.5A Raspberry Pi USB Power Supply] Specially designed for the Pi. Comes in 4 varieties for worldwide compatibility - UK, European (EU), American (USA) and Australian (AUS). <br />
* '''PortaPow'''<br />
** PortaPow UK Mains Wall Power Supply<br />
* '''PowerGen'''<br />
** PowerGen Dual Port USB 2.1A 10W AC Travel Wall Charger. [http://www.amazon.com/gp/product/B0073FCPSK Amazon Link]<br />
* '''Rayovac'''<br />
** 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<br />
* '''RhoTech'''<br />
** [http://www.rhotech.eu/index.php?id_product=10&controller=product RH-PS001] 5V/2A, dedicated for Raspberry Pi, integrated MicroUSB cable. Stable with Raspbmc and WiFi card.<br />
** [http://www.rhotech.eu/index.php?id_product=11&controller=product RH-PS002] 5V/2.1A dual USB Power Supply.<br />
* '''RS Components'<br />
** HNP06UK (RS 7263069) Switching Adapter 5.0&nbsp;V 1200&nbsp;mA<br />
* '''Samsung'''<br />
** 5&nbsp;V 0.7&nbsp;A Charger for Galaxy S model ETA0U10EBE<br />
** 5&nbsp;V 0.7&nbsp;A Charger for Galaxy SII<br />
** 5&nbsp;V 1&nbsp;A Charger for Galaxy SIII<br />
** 5&nbsp;V 1&nbsp;A Charger for Galaxy Nexus<br />
** 5&nbsp;V 0.7&nbsp;A Charger for Galaxy S Vibrant (SGH-T959)<br />
** 5&nbsp;V 0.7&nbsp;A Travel Adapter model ATADU10EBE<br />
** 5&nbsp;V 1&nbsp;A? Samsung C Series TV USB-port for external HDDs. Running stable with openelec<br />
** 5&nbsp;V ?A (Unknown) Samsung Service Port (USB) on LN32A330J1DXZA 720p 32 inch HDTV <br />
** 5&nbsp;V Unknown Ampere Samsung UA22D5000 & UA32D5000 TV USB Port. Test with Raspbian Wheezy, Raspbmc, and RPITC<br />
* '''Shun Shing'''<br />
** 100-240&nbsp;VAC to 5&nbsp;VDC 1&nbsp;A USB power supply, model SP5Q-AU [http://jaycar.co.nz/productView.asp?ID=MP3455 Jaycar]<br />
* '''Sony Ericsson'''<br />
** 5&nbsp;V 0.7&nbsp;A Charger CST-80<br />
** 5&nbsp;V 0.85&nbsp;A Greenheart&#153; Charger EP800. Typically provides 4.8&nbsp;V at 0.85&nbsp;A <ref>[http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/USBPowerSupplies.html]</ref>.<br />
* '''StarTech'''<br />
** 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.<br />
* '''Travel Charger'''<br />
** 5&nbsp;V 2.0&nbsp;A USB Power Adapter, [http://www.amazon.co.uk/gp/product/B0065JCIPU/ Amazon Link]<br />
* '''Technika'''<br />
** 5&nbsp;V 1&nbsp;A USB Power Adapter, model MPASS01 (B)<br />
* '''Trisonic'''<br />
** TS-CP600T - MICRO USB HOME & TRAVEL CHARGER (5&nbsp;V, 800&nbsp;mA) $3 at Daiso U.S. stores.<br />
* '''TruePower'''<br />
** [http://u-socket.com/ U-Socket] 5&nbsp;V 2.1&nbsp;A AC Receptacle with Built-in USB ports (2.1&nbsp;A per USB port) model ACE-7169<br />
* '''Voltcraft'''<br />
** SPS5-12W, 2500&nbsp;mA, requires additional USB <-> miniUSB adapter/cable, works perfectly (bought from [http://www.conrad.de/ce/de/product/512660/VOLTCRAFT-SPS5-12W-Steckernetzteil-Steckernetzgeraet-5-VDC-2500-mA-12-Watt Conrad Shop])<br />
* '''ZTE'''<br />
** ZTE Blade charger STC-A22O501700USBA-A 5&nbsp;V 700&nbsp;mA<br />
<br />
===Problem power Adapters===<br />
* '''Nokia'''<br />
** 5&nbsp;V 1.2&nbsp;A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2<br />
** [http://accessories.nokia.com/products/nokia-fast-usb-charger-ac-16/ 5&nbsp;V 1&nbsp;A AC-16E Charger] Provides only 4.7V across TP1 & TP2 when at idle<br />
<br />
* '''Masterplug'''<br />
** Masterplug Surge Protected USB Adaptor 2 x 1&nbsp;A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artifacts using HDMI.<br />
* '''Monoprice'''<br />
** 5&nbsp;V, 2&nbsp;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&nbsp;V between TP1 and TP2 when used with a Monoprice cable.<br />
* '''Sony Ericsson'''<br />
** 5&nbsp;V, 850&nbsp;mA EP800. Some failures to boot, Ethernet loops at boot.<br />
<br />
===Working external Battery packs (with 5&nbsp;V regulated output)===<br />
* '''Anker Astro3'''<br />
** Anker Astro3 10000&nbsp;mAh with dual 2&nbsp;A USB output<br />
* '''Duracell'''<br />
** PPS2 Instant USB Charger<br />
* '''EasyAcc'''<br />
** PB12000A 12000&nbsp;mAh battery with 2.1&nbsp;A USB output<br />
* '''Energizer/XPAL'''<br />
** XP18000 18000&nbsp;mAh Power Pack<br />
* '''Generic - eBay no brand'''<br />
** 6000T Pocket Power 5000&nbsp;mAh - eBay item 271009959140<br />
** Power Bank for iPad/iPhone 5000&nbsp;mAh (looks the same as a New Trent IMP50D or TeckNet iEP380) - eBay item 280914455938<br />
* '''Mophie'''<br />
** 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<br />
* '''New Trent'''<br />
** iCurve IMP70D 7000&nbsp;mAh (Approx 12&nbsp;hours from full charge)<br />
** IMP120D 12000&nbsp;mAh<br />
* '''Sinoele'''<br />
** Movpower - Power Bank 5200&nbsp;mAh (8&nbsp;hours with Wi-Fi active)<br />
* '''TeckNet'''<br />
** iEP387 Dual-Port 7000&nbsp;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.)<br />
** iEP392 Dual-Port 12000&nbsp;mAh External Power Bank (1&nbsp;A port, ~16.5 hours)<br />
** Rayovac PS60 5&nbsp;V 800&nbsp;mAh<br />
* '''VINZO'''<br />
** Power Bank 5000&nbsp;mAh Grey Output 5&nbsp;V 1000&nbsp;mA<br />
* '''Kodak Power Pack KP1000'''<br />
** 1&nbsp;A USB rechargeable battery pack - see [http://blog.sheasilverman.com/2012/09/its-alive/ Shea Silverman's blog]<br />
<br />
== Display adapters ==<br />
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&nbsp;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&nbsp;mA, if the adapter tries to draw much more than that the diode might fail. Therefore only externally powered adapters are to be recommended. Despite this, many people report success with non externally powered devices. If you have bought a non externally powered HDMI to VGA adapter, and you experience problems with it (It behaves badly, D1 burns out, F3 "blows", or your PSU overloads), then not all is lost, there are cheap (a few dollars) adapters that allow you to add external power to the HDMI cable! An example can be found here: [http://dx.com/p/hdmi-male-to-hdmi-female-adapter-w-power-input-port-black-155361].<br />
<br />
===HDMI->DVI-D cables===<br />
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.<br />
<br />
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 [[RPi_config.txt|config.txt]] hdmi_force_hotplug=0 to =1 if your display does not receive DVI signal (the analog output is likely active).<br />
<br />
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.<br />
<br />
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.<br />
<br />
* '''The Pi Hut'''<br />
** HDMI to DVI Cable for the Raspberry Pi (from [http://thepihut.com/collections/video-output/products/hdmi-to-dvi-cable-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
* '''Other Variants'''<br />
** AmazonBasics HDMI to DVI Adapter Cable (model SK231) works and is inexpensive.<br />
** [http://www.ebay.com/itm/DVI-Female-to-HDMI-Male-Adapter-Converter-Adaptor-Gold-for-HDTV-Full-HD-/320946033059?pt=US_Video_Cables_Adapters&hash=item4ab9dfd1a3 A generic HDMI-to-DVI converter from eBay]. Works well, but it's probably the cause of some power loss between the Raspberry Pi and the monitor, causing [http://elinux.org/R-Pi_Troubleshooting#Interference_visible_on_a_HDMI_or_DVI_monitor this] problem. A setting of config_hdmi_boost='''5''' in /etc/boot solved this. Note that config_hdmi_boost='''4''', as suggested in the troubleshooting guide, helped, but it did not solve the problem completely.<br />
<br />
===HDMI->VGA Cables===<br />
HDMI to VGA cables <strong>do not work!</strong> <br />
They rely on logic incorporated in a video card that isn't available in a PI.<br />
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.<br />
But normally HDMI cables <strong>never</strong> 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.<br />
<br />
===HDMI->VGA converter boxes===<br />
<br />
HDMI to VGA <strong>converters</strong> 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.<br />
These adapters also thus use about half the energy that the PI (without USB devices) uses.<br />
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.<br />
<br />
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.<br />
<br />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
'''HDMI to VGA + audio adapter from DHgate'''<br />
* Under six pounds with free international shipping [http://www.dhgate.com/product/hdmi-to-vga-output-projector-monitors-adapter/170509392.html] makes this worth the delivery time of just under 3 weeks. Works out of the box at 1024x768 without editing config.txt (I'll try editing for full HD later). Spec. says upto UXGA and 1080p with 10-bit DAC at 165MHz/1.65Gbps. Raspberry "tvservice -a" reports that it supports audio up to 192k at 24-bit. Sounded fine on my tiny speaker. Comes with 3.5mm stereo plug-to-plug cable and USB to mini barrel jack power cable which it doesn't need on the Pi. Ran mine for ages without the external power and the Pi's HDMI regulator never got more than 34 degrees C. Adapter weighs only 14.8g and can plug directly into the Pi or even via a 90-degree 'elbow' which I prefer to use. VGA signal is good enough to run 2 displays at once using a cheap splitter cable. After brief testing with good headphones, it seems there's some definite noise on a signal of 17,500Hz and 18,500Hz is distorted. In contrast, the RPi's own analogue sounds clean at 17,500Hz. So you couldn't consider this an alternative to a good USB DAC.<br />
<br />
'''HDMI to VGA Cable adaptor from amazon'''<br />
* At under ten pounds this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ] 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.<br />
<br />
'''Sanoxy HDMI to VGA converter'''<br />
* [http://www.element14.com/community/groups/raspberry-pi/blog/2012/08/16/raspberry-pi-hdmi-to-vga-converter Sanoxy HDMI to VGA converter]'', $27 from Amazon, no changes required with official Raspbian Wheezy image (2012-Jul-15), note: had already disabled overscan previously<br />
<br />
'''"Neewer" HDMI to VGA '''<br />
* http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
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&nbsp;A max forward current, much greater than the BAT54's 200&nbsp;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 same" thread, user "pwinwood" reported the Neewer's current to be 400&nbsp;mA, which is twice the limit of BAT54 diode D1. "pwinwood" also took the Neewer apart and added its own +5&nbsp;V connection adapted from a USB cable, which bypasses Raspberry Pi's Micro USB cable and polyfuse F3.<br />
Link to a gallery with detailed images & steps of the same adapter modification: [http://imgur.com/a/sLogs/all HERE] --''by [[User:Pinoccio|Pinoccio]]''<br />
<br />
'''"Kanaan" HDMI-VGA'''<br />
* http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
'''HDMI Male to VGA RGB Female HDMI to VGA Video Converter adapter'''<br />
* http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<br />
'''HDMI to VGA 3.5mm Audio HDTV HD Video Converter'''<br />
* This adapter -- http://www.ebay.co.uk/itm/300692770623 -- works from 640x480 up to 1920x1080, audio over HDMI works too.<br />
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.<br />
Requires HDMI boost and overscan, [[RPi_config.txt|config.txt]] settings for 640x480 @60&nbsp;Hz:<br />
<pre>hdmi_drive=2<br />
hdmi_group=2<br />
hdmi_mode=4<br />
config_hdmi_boost=4<br />
overscan_top=-30<br />
overscan_bottom=-30<br />
overscan_left=-30<br />
overscan_right=-30<br />
</pre><br />
<br />
'''HDFuryPro HDMI to YPbBr/VGA Converter'''<br />
* 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.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<pre>hdmi_drive=2<br />
hdmi_group=2<br />
hdmi_mode=36<br />
disable_overscan=1<br />
</pre><br />
<br />
'''HDFury1 1080p HDMI to VGA Converter'''<br />
* 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&nbsp;A, which is too much draw for the 5&nbsp;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.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<pre>hdmi_drive=2<br />
hdmi_group=2<br />
hdmi_mode=36<br />
disable_overscan=1<br />
</pre><br />
<br />
'''Cable Matters Gold Plated Premium HDMI to VGA'''<br />
* http://www.amazon.co.uk/gp/product/B007SM7O2U/ - "Cable Matters"<br />
<br />
'''HDMI V1.4 Male to VGA Female Converter Adapter'''<br />
* 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.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<pre>hdmi_drive=2<br />
hdmi_group=2<br />
hdmi_mode=16<br />
hdmi_force_hotplug=1<br />
disable_overscan=0<br />
</pre><br />
<br />
''' HDMI - VGA [lontium chip]'''<br />
* 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&nbsp;Hz, 1024x768 60&nbsp;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&nbsp;mA. The standard RS Components 1.2&nbsp;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.<br />
<br />
'''Pi-View HDMI-VGA converter'''<br />
* The "Pi-View" was designed 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]<br />
<br />
===DVI-D -> VGA active adapters===<br />
None are currently listed<br />
<br />
===Composite->SCART===<br />
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&nbsp;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.<br />
<br />
* Generic - works<br />
<br />
===Composite->VGA converter boxes===<br />
* [http://www.extron.com/product/product.aspx?id=dvs204 Extron DVS-204] - works no problem!<br />
<br />
== Boblight hardware ==<br />
'''Lightberry'''<br />
* http://lightberry.eu it's the first (I think), dedicated hardware for Raspberry Pi that can produce colorful effects behind your TV, when you watch movies or even pictures. It uses GPIO pins (not USB). It is easy to configure - you can even download configured system image from the producer website. Works perfectly :)<br />
<br />
== SD cards ==<br />
<br />
The SD card section has been moved to a separate page. See [[RPi SD cards]]<br />
<br />
== Foreign Language Translations ==<br />
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]<br />
<br />
== References ==<br />
<references><br />
</references><br />
<br />
{{Template:Raspberry Pi}}<br />
♦<br />
nbsp;V 1nbsp;V 1000</div>ACchttps://elinux.org/index.php?title=RPi_USB_Wi-Fi_Adapters&diff=319472RPi USB Wi-Fi Adapters2014-03-18T13:57:58Z<p>ACc: </p>
<hr />
<div>See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing<br />
<br />
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.<br />
<br />
==Working USB Wi-Fi Adapters==<br />
<br />
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.<br />
<br />
'''Note:''' A Wi-Fi adapter will probably need more power than the Raspberry Pi USB port can provide, especially if<br />
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.<br />
<br />
'''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:<br />
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=40474#p330868<br />
<br />
'''Note:''' Devices with RTL8188CUS work great as wifi access point - [http://raspberry-at-home.com/hotspot-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. <br />
<br />
'''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.<br />
<br />
* '''3COM'''<br />
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)<br />
<br />
* '''7DayShop'''<br />
** W-3S01BLK, W-3S01BLKTWIN: Unbranded product available from 7DayShop, in a single or twin pack. [http://www.7dayshop.com/catalog/product_info.php?cPath=777_9&products_id=112046], [http://www.7dayshop.com/catalog/product_info.php?&products_id=112527]. Tested on Debian Wheezy, with the dongle attached directly to the Raspberry Pi along with the wireless keyboard receiver. Shows up as a Ralink RT5370 device, and no drivers or additional software downloads required. Created wpa.conf, edited 'interfaces' file and restarted the networking. The manufacturer portion of the MAC address (7cdd90) is assigned to "Shenzhen Ogemray Technology Co., Ltd."<br />
** It works without additional software connected directly to a Rev 2 Raspberry Pi, but it stops working after a period of time (3 to 4 hours) with a fully updated Wheezy and all the 'USB workarounds' [http://elinux.org/Rpi_USB_check-list] in place. <br />
<br />
* '''Alfa'''<br />
** AWUS036NEH: Tested on Debian Squeeze (with Ralink firmware package)<br />
** AWUS036NH: Tested on Arch Linux ARM using the rt2800usb module.<br />
** AWUS036NH: Tested on Debian Wheezy (with Ralink firmware package). Tested on Raspbian too (drivers from aircrack-ng).<br />
** AWUS036H (500&nbsp;mW version): Tested on Raspbian (drivers from aircrack-ng).<br />
** AWUS036H (1&nbsp;W version): Tested on Raspbian (drivers from aircrack-ng). Needs USB powered HUB or Rev2 of the board / polyfuse bypass.<br />
** AWUS036NHA: Tested on Raspbian (drivers from aircrack-ng). Works fine if connected after boot, otherwise Raspberry Pi won't boot up.<br />
<br />
* '''AirLink101''' [[File:Airlink101.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-airlink101|100px|Airlink 101 Wireless N 150 Ultra Mini-USB Adapter]]<br />
** 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.<br />
** AWLL5099: Tested on Raspian Wheezy. [http://www.savagehomeautomation.com/raspi-airlink101 Step-by-step installation and configuration instructions] with screenshots can be found [http://www.savagehomeautomation.com/raspi-airlink101 here]. This adapter is based on the Realtek RTL8188CUS chipset. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution. Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
** [http://www.airlink101.com/products/awll6075.php AWLL6075]: Tested on Raspian Wheezy 16-Dec-2012 build and distro upgrade as of 09-Jan-2013. lsusb reports: 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter. Driver installed is r8712u. Powers OK from Model B Pi (Rev 000f) USB port (1200mA supply tested). Dongle does get hot under use when directly connected to USB port (slightly reduced when USB extender cable used).<br />
<br />
* '''Asus'''<br />
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware - Realtek from non-free Squeeze repository (B) (not needed with latest Raspbian “Wheezy” 2012-07-15: this Asus works N10 out of the box) Does not support nl80211 APIS, so hostapd won't work.<br />
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, works with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1 Adafruit Occidentalis v0.1 image] as it includes kernel [http://www.element14.com/community/message/57635#57660 with 8192u driver built-in] (B)<br />
** 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.<br />
** 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.<br />
[[File:AusPiWiFi.png|thumb|right|link=http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/|100px|AusPi Technologies 802.11n WiFi Adapter]]<br />
* '''AusPi Technologies'''<br />
** AusPi Wireless Adapter [Realtek RTL8188S]. Works without a powered HUB. Tested on OpenELEC (works OOB), RaspBMC (works OOB) and 2012-08-08 Raspbian Wheezy (works OOB). Free shipping worldwide from [http://www.buyraspberrypi.com.au/raspberry-pi-802-11bgn-usb-wireless-dongle/ Buy Raspberry Pi Australia].<br />
<br />
* '''Belkin'''<br />
** Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]. On Debian requires the firmware-ralink package from the non-free repository. The usbcore module needs to be added to /etc/modules [http://www.penguintutor.com/blog/viewblog.php?blog=6281 install instructions].<br />
** 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!'''<br />
** Belkin Components F5D8053 ver.6001 Wireless N Adapter [Realtek RTL8188SU]. Works on RaspBMC OOB (with NetworkManager plugin). Works WITHOUT powered hub on 5&nbsp;V 800&nbsp;mA power with 6 overvolt (nothing else connected to USB)<br />
** Belkin Components F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU] USB ID 050d:945a, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian and install firmware - Realtek from non-free Squeeze repository (B). Verified working with 2012-12-16-wheezy-raspbian right out of the box.<br />
**Belkin Components F6D4050 V1 [Realtek RT3070] USB ID: 050d:935a Driver: RT3572STA(recommended),RT2800USB,RT2870STA. Tested under Arch using [https://wiki.archlinux.org/index.php/Setting_Up_Belkin_F6D4050_Wireless_USB_Dongles this] guide.<br />
**Belkin Components F6D4050 V1/V2 [Realtek RT3070] USB ID: 050d:935a / 935b Driver: RT3572STA. Tested with Raspbian - See [http://iggy82.blogspot.co.uk/2012/08/wireless-n-raspberry-pi-belkin-f6d4050.html installation instructions] - Powered hub not required!<br />
** 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)<br />
** Belkin Components F9L1001v1 "N150" Wireless USB Adapter. Tested and working on Rasbian Wheezy WITHOUT powered hub. <br />
** Belkin Surf Micro WLAN USB-Adapter (Raspbian Wheezy, unpowered hub, "N150")<br />
<br />
* '''Blitzz'''<br />
** [http://wikidevi.com/wiki/Blitzz_BWU613B Blitzz BWU613B ]Tested on Raspbian 5-25-13, must install atmel-firmware from apt-get.<br />
<br />
* '''BlueProton'''<br />
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora & Arch; rtl8187 driver (B)<br />
<br />
* '''Buffalo'''<br />
** USB ID: 0411:01A2 WLI-UC-GNM - Tested on Raspbmc; rt2800usb driver <br />
** USB ID: WLI-UC-G300N - Works on Raspbmc out of the box. Tested after a factory reset of the Raspbmc.<br />
<br />
* '''Comfast'''<br />
** WU710N: chipset RTL8188CUS. The rtl8192cu kernel driver is loaded automatically in the latest Raspian distribution. Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script] <br />
** WU810N (150M): Works out of the box on wheezy raspbian of version 2012-12-16. <br />
<br />
* '''Conceptronic'''<br />
** C300RU. Works out of the box in Raspbian. Causes reboot when plugging on a live Rev. 2 Raspberry Pi<br />
<br />
* '''Conrad'''<br />
** WLAN Stick N150 mini. Works out of the box in OpenELEC, [http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/ requires firmware - Realtek and r8712u kernel module on Debian].<br />
** WLAN Stick N150 Nano [Realtek RTL8188CUS]. Requires a powered USB hub. See Micronet SP907NS for installation instructions and script. Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
<br />
* '''DealExtreme'''<br />
** 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).<br />
** DX Original Mini Nano USB 2.0 IEEE802.11n/b/g 150Mbps Wi-Fi / WLAN Wireless Network Adapter, SKU 256382. Has Ralink RT2870 chipset. Works out of the box in latest Raspbian Wheezy (7.2). I ([[User:-df-|-df-]] ([[User talk:-df-|talk]])) have been using it in powered USB hub with Raspberry Pi model B and also directly in model A's single USB slot.<br />
<br />
* '''DELL'''<br />
** 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).<br />
<br />
* '''DIGICOM'''<br />
** USBWAVE54 [chipset Zydas ZD1211] . [[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/UsbWave54]] Works out of the box in OpenELEC. With Raspbian or Debian squeezy/Wheezy works with zd1211-firmware . <br />
** USBWAVE300C [chipset Ralink 2870] . [[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/UsbWave300c]] Works out of the box in OpenELEC. With Raspbian or Debian squeezy/Wheezy works with firmware-ralink . <br />
<br />
* '''Digitus'''<br />
** [http://www.digitus.info/en/products/network/150mbps-wireless-lan-series/wireless-150n-usb-adapter-dn-7042-1/ Wireless 150N DN-7042-1], USB ID 0bda:8176, RTL8188CUS. Works out of the box with Raspbian Wheezy. Works even after uninstalling firmware-realtek from the raspbian non-free repository. No powered USB hub needed. GNU GPLv3 printed on paper and included in the package.<br />
<br />
* '''D-Link'''<br />
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>Squeeze-firmware</code> non-free repository. (However I experience total crashes on Raspbian 2012-07-15 after a few minutes of load on the WLAN. Will have to investigate via serial console.)<br />
** AirPlus G DWL-G122 (rev. C). USB ID 07d1:3c03, Ralink RT2571. Working out-of-the-box on Arch image from 2012-04-29.<br />
** AirPlus G DWL-G122 (rev. B1). USB ID 2001:3c00, Ralink RT2571. Working out-of-the-box on Arch image from 2012-06-13.<br />
** DWA-110 (Version A1). Requires the ralink package from the non-free repository on Debian.<br />
** DWA-121 (Version A1). Wireless N 150 Pico. Works out-of-the-box with Arch Linux (3.12.1), Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons). Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
** 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.)<br />
** DWA-125 (Version A2). Works out of the box on Raspian Wheezy (2013) and Raspbmc (2013)<br />
** 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. <br />
** DWA-131 (rev. A1) USB ID 07d1:3303,Realtek RTL8192SU, 802.11n Wireless N Nano.<br />
*** 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/.<br />
*** Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<br />
** DWA-140 (Version B1). USB ID 07d1:3c09, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>Squeeze-firmware</code> non-free repository.<br />
** DWA-140 (Version B2). USB ID 07d1:3c0a, Ralink RT3072. Workaround for faulty firmware binary: Place file rt2870.bin from [https://launchpad.net/ubuntu/oneiric/+source/linux-firmware/1.53/+files/linux-firmware_1.53.tar.gz linux-firmware_1.53.tar.gz] in /lib/firmware. [https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/770232 Explanation].<br />
** DWA-140 (Version B3). USB ID 2001:3c15, Works out of the box with Raspbmc (only tested with powered hub).<br />
** DWA-160 (Version B1). USB ID 07d1:3c11, Ralink RT2870. On Debian requires the <code>firmware-ralink</code> package from the <code>Squeeze-firmware</code> non-free repository.<br />
** DWA-160 (Version A2). USB ID 07d1:3a09, Atheros AR9170. (NOTE: I can only get it to work through powered USB hub) requires carl9170-fw firmware [http://http://aur.archlinux.org/packages.php/packages.php?ID=44102]<br />
** WUA-1340 (Version A1). Works with Raspbian Wheezy after installing the firmware-ralink package from the non-free repository on Debian.<br />
<br />
* '''Edimax''' [[File:Edimax-ew-7811un.jpg|thumb|right|link=http://www.savagehomeautomation.com/raspi-edimax-ew-7811un|100px|Edimax EW-7811Un 150 Mbps Wireless 11n Nano Size USB Adapter]]<br />
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP ([http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html howto]) (B) - [http://dl.dropbox.com/u/80256631/8192cu-latest.tar.gz Alternative driver download link that works with Raspian]. <b>Note:</b> 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.<br />
*** 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 - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
*** EW-7811Un [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un step-by-step installation and configuration instructions] for Debian & Raspian with screenshots can be found here: [http://www.savagehomeautomation.com/raspi-edimax-ew-7811un here] <br />
*** A script-based installation for the [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] by MrEngman can be found [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6256&hilit=edimax on the Raspberry Pi forums]. Tested with Debian Squeeze and Raspbian. [http://dl.dropbox.com/u/80256631/install-rtl8188cus.txt An installation guide can be found here.]<br />
*** Instructions for getting the [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] working in Raspbmc (tested RC3) can be found [http://forum.stmlabs.com/showthread.php?tid=780 here].<br />
*** Simple step-by-step instructions for [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] which uses the RTL8192 chipset [[RPi_edimax_EW-7811Un]]<br />
*** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&pl1_id=1&pl2_id=44 EW-7811Un] with the RTL8188UCS chipset works out of the box as a client with Raspbian (as of August 2013), requires a special version of hostapd to work as Wi-Fi access point - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
*** 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.<br />
*** Doesn't work in monitor mode with default drivers in latest Raspbian (2013-09-25-wheezy-raspbian) due to lack of support of nl80211 in driver.<br />
** [http://www.edimax.com/en/produce_detail.php?pd_id=8&pl1_id=1&pl2_id=44 EW-7318USg] USB ID 148f:2573, rt73usb. RT2573 chipset. Works with powered usb-hub or shorted polyfuses.<br />
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=261&pl1_id=1&pl2_id=44 EW-7711UAn], Ralink RT2870, works perfectly on Arch with a powered hub (not tested without yet). Simply required wireless_tools and wpa_supplicant, the drivers/firmware are included in kernel 3.0. I followed the Arch [https://wiki.archlinux.org/index.php/Wireless_Setup Wireless Setup] instructions.<br />
<br />
* '''edup'''<br />
** [[http://www2.buyincoins.com/details/usb-150m-wifi-wireless-lan-network-card-adapter-antenna-product-1916.html Edup 150MBPS Wi-Fi adapter]] USB ID: 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter. Driver is the RT2800USB module, I had to install the firmware as rt2870.bin in /lib/firmware.([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from Wheezy]) (B)<br />
** [http://dx.com/p/ultra-mini-nano-usb-2-0-802-11n-150mbps-wifi-wlan-wireless-network-adapter-48166?item=1&Utm_rid=24958662&Utm_source=affiliate Ultra-Mini Nano USB 2.0 802.11n 150&nbsp;Mbit/s Wi-Fi/WLAN Wireless Network Adapter] USB ID: ID 0bda:8176 Works stable when using VLC for internet radio receiver. Works stable 24/7 on two of my Raspberries used as webserver. Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian. Seems to be the same as EW-7811Un using the RTL8188CUS chipset.<br />
<br />
** [http://www.szedup.com/show.aspx?id=1681 edup nano EP-N8508] Use method shown [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7471&p=91736 here] for Debian. Requires powered USB hub for adequate power. When directly powered by Raspberry Pi, it fails after a few minutes. (B) Unusable with analog audio because when data is being send or received the audio get distorted. Use script from [http://dl.dropbox.com/u/80256631/install-wheezy-beta-rtl8188cus-20120619.sh here] for Wheezy.<br />
<br />
* '''Eminent'''<br />
** EM4575 - rt2800usb driver.<br />
<br />
* '''EnGenius'''<br />
** EUB9603 EXT - Realtek r8712u driver <br />
<br />
* '''Gigabyte'''<br />
** Gigabyte GN-WB32L 802.11n USB WLAN Card. Works with the rt2800usb driver.<br />
<br />
* '''GMYLE'''<br />
** Wireless 11n USB Adapter. Uses RTL8188CUS chipset - cheap on eBay. Installs and works using the install-rtl8188cus-latest.sh script.<br />
** 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 - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
* '''Hawking'''<br />
** HWU54G rev. Z2 (802.11g) (B). Requires "zd1211-firmware" package.<br />
<br />
* '''Hercules'''<br />
** Hercules Wireless N LB USB / HWNU-LB-150 (802.11n/g/b). Identified by USB ID 06f8:e034 Guillemot Corp. and driver is in current Raspbian. No external power needed but warning when hot plug because RPi is rebooting.<br />
<br />
* '''IOGear'''<br />
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix & Arch, must [http://www.element14.com/community/servlet/JiveServlet/download/44948-8-97488/r8712u_ko.zip download] for Debian Squeeze and install firmware - Realtek from non-free Squeeze repository. No need to download firmware when using Debian Wheezy (B)<br />
<br />
* '''ISY'''<br />
** USB Wireless Micro Adapter IWL 2000, tested on Raspbian; follow [http://daniel-lnx.blogspot.nl/2013/01/raspberry-pi-and-isy-usb-wireless-micro.html these] instructions.<br />
<br />
* '''Linksys'''<br />
** Linksys (Cisco) WUSB100 ver.2 1737:0078, tested on Raspbian; follow [http://www.brucalipto.org/linux/the-raspberry-diary-wusb100-wireless-n/ Brucalipto.org] instructions; not stress tested, but it works without issues for light network load.<br />
** Linksys (Cisco) WUSB600N, test on Raspbian, details [http://elibtronic.ca/content/20120731/raspberry-pi-part-1-wifi-support here]<br />
** Linksys WUSB54GC (manufactured 07/2008) No issues! needs powered hub on version 1.0 boards - 13b1:0020<br />
** 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.<br />
<br />
* '''LogiLink'''<br />
** Wireless LAN USB 2.0 Nano Adapter 802.11n LogiLink [http://www.logilink.eu/showproduct/WL0084B.htm] is working even USB powered.<br />
** Micro Wireless LAN USB Adapter [http://www.logilink.eu/showproduct/WL0085.htm] is working good.<br />
** [http://www.logilink.eu/showproduct/WL0145.htm WL0145], USB ID 148f:5370 works, via a powered USB hub, used as access point, 150MBit 2,4MHz<br />
** [http://www.logilink.eu/showproduct/WL0150.htm WL0150], USB ID 148f:5372 works, directly, used as AP or Bridge possible (hostapd nl80211) 300MBit 2,4 GHz 180mA<br />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<br />
<br />
* '''Manhattan'''<br />
** Micro 150N (uses Realtek RTL8188CUS) Works out of the box in Rasbian Wheezy, no hub, no drivers - http://manhattan-products.com/en-US/products/9687<br />
<br />
* '''Micronet'''<br />
** Micronet SP907NS, 11N Wireless LAN USB Adapter (uses Realtek RTL8188CUS) works plugged directly into Raspberry Pi USB (B) [http://dl.dropbox.com/u/80256631/install-rtl8188cus.txt Debian installation instructions] IMPORTANT: read the instructions first to avoid problems, and [http://dl.dropbox.com/u/80256631/install-rtl8188cus-latest.sh Auto-install script]. The script has been used to install other adapters using the RTL8188CUS chip. [http://dl.dropbox.com/u/80256631/8192cu-latest.tar.gz Updated driver] that handles the latest rpi-updates that kill the original driver, download for manual installation, automatically installed by the Auto-install script.<br />
** Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
<br />
* '''ModMyPi'''<br />
** 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 [https://www.modmypi.com/raspberry-pi-accessories/wireless-USB%20-1N-nano-adaptor-802.11N-(WiFi-dongle) ModMyPi Raspberry Pi Shop]. Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
* '''MSI'''<br />
** 0db0:6861 MSI-6861 802.11g Wi-Fi adapter (US54G): works with external powered USB hub, requires firmware from [http://sourceforge.net/projects/zd1211/files/zd1211-firmware/ here], power management must be disabled: <code>iwconfig wlan0 power off</code><br />
<br />
* '''Mvix'''<br />
** Mvix Nubbin (MS-811N): works out of the box on Raspbian "Wheezy" and does not need a powered USB hub.<br />
<br />
* '''Netgear''' <br />
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the <code>firmware-atheros</code> package from the <code>Squeeze-backports</code> non-free repository (!)<br />
** 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.<br />
** WG111v1: Prism54 chipset. Needs powered hub. Follow info for Prism54 chipset on Debian wiki.<br />
** WG111v2: Realtek rtl8187 chipset. Seems to draw a lot of power; e.g. I can't power this and a USB thumb drive simultaneously.<br />
** WG111v3: Realtek RTL8187B chipset. Works straight out of the box using a powered USB hub.<br />
** WNA1000M works with Raspberry Pi Model B Board v. BS1233. However, when downloading torrents and when they pick up speed, the system becomes unresponsive. <br />
** WMA3100M works when connected to on-board USB. Also works in an un-powered hub. But like the WNA1000M during use the CPU can go to 100% at which point the system is VERY slow to respond. <br />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://www.patriotmemory.com/product/detail.jsp?prodline=6&catid=97&prodgroupid=163&id=1198&type=24 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub. Wifi access point configuration - [http://raspberry-at-home.com/hotspot-wifi-access-point/ see tutorial and configuration script]<br />
** [http://www.patriotmemory.com/product/detail.jsp?prodline=6&catid=97&prodgroupid=163&id=973&type=24 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Worked immedietly, plug and play in 2013-02-09 Raspbian via powered USB hub.<br />
<br />
* '''Ralink'''<br />
** inner 02 joggler Wi-Fi USB RT2770F USB-ID 148f:2770 (firmware-ralink required) (only got dhcp on powered hub)<br />
** [http://www.dx.com/p/24688 RT2070] USB-ID 148f:2070 firmware is already loaded into Raspbian. For Debian, the firmware must be installed ([http://wiki.debian.org/rt2870sta instructions]). Needs a powered USB hub.<br />
** RT3070 USB-ID 148f:3070 firmware is already loaded into Raspbian.<br />
** [http://www.element14.com/community/docs/DOC-44703 RT2501/RT2573] USB-ID 148f:2573 (firmware-ralink required) (B)<br />
** RT5370 USB-ID 148f:5370 ([http://raspberry-pi-notes.blogspot.com/2012/05/rt5370-cheap-micro-usb-wireless-dongle.html requires firmware-ralink from Wheezy]) [[RPi_Ralink_WLAN_devices]](B). An image of an adapter with this chip can be found [http://i.imgur.com/wRF7L.jpg here].<br />
** RT5370 USB-ID 148f:7601 Advertised on eBay as RT5370 chipset but has Mediatek 7601T chip instead. [http://i.imgur.com/deqDOWp.jpg] DOES NOT WORK out of the box; requires compiling a driver downloadable from mediatek.com<br />
** RT5370 supports Access Point and it be used for hostapd <br />
** RT5572 USB ID 148f:5572 no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the Ralink 5572 chipset but works using Ralink drivers (requiring compilation - [http://www.ctheroux.com/2012/09/ralink-rt5572-based-wifi-usb-dongle-setup-on-ubuntu-12-04/ guidance], requires source for the running kernel) including with wpa_supplicant. Supports dual band 2.4GHz/5GHz. No need for firmware installation. Needs a powered hub.<br />
<br />
* '''RhoTech'''<br />
** [http://www.rhotech.eu/index.php?id_product=9&controller=product RH-WL01B] Miniature Wireless USB adapter B/G/N, Ralink RT5370 chipset, works out of the box with Raspbian nad Raspbmc<br />
<br />
* '''Rosewill'''<br />
** RNX-N180UBE Wireless B/G/N Adapter<br />
*** Realtek RTL8191SU chipset, USB-ID 0bda:8172<br />
*** Tested in Arch, works out of box. Powered USB hub required.<br />
*** Tested in Raspbian, used wicd to configure network settings. Powered USB hub Required.<br />
*** Tested in Raspbmc. Needs package firmware - Realtek and used wicd-curses to configure. Powered USB hub required<br />
** RNX-G1 Wireless B/G Adapter<br />
*** Realtek RTL8187 chipset, USB-ID 0bda:8187<br />
*** Tested in Arch, works out of box. USB hub required.<br />
** RNX-MiniN1 (RWLD-110001) Wireless-N 2.0 Dongle (Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter)<br />
*** Tested in Raspbian, powered from USB hub.<br />
<br />
* '''Sabrent'''<br />
** 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). RTL8188CUS chipset. To get access point to work required compilation of vendor-supplied hostapd (Part of [http://sabrent.com/drivers/USB-A11N/Wlan_11n_USB_linux.zip Linux driver package] available from [http://www.sabrent.com/downloads.php vendor site].) (Path to hostapd in driver package: ~/Wlan_11n_USB_linux/wpa_supplicant_hostapd/wpa_supplicant_hostapd-0.8/hostapd)<br />
<br />
* '''Sagem'''<br />
** 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"<br />
<br />
* '''Sempre'''<br />
** 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/<br />
<br />
* '''Sitecom'''<br />
** Sitecom Wi-Fi USB Adapter N300: USB ID 0a5c:5800, Realtek r8712u driver + firmware Realtek. Module available in shipped Raspbian image. '''NOTE:''' although this dongle will also work without powered hub, if there is a voltage problem (either on the Raspberry or on the hub, but verified only on the hub so far) this wifi dongle will receive signal perfectly (RX), but not be capable of sending anything (TX) and the MAC address will be permanently set to FF:FF:FF:FF:FF:FF (this is indicative that there is not enough power) [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
<br />
* '''SL'''<br />
** SL-1507N: USB 802.11n 150M Wi-Fi Wireless LAN Network Card Adapter SL-1507N Black<br />
*** 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<br />
*** It worked out of the box on Raspbmc RC4, with the network manager add-on; seems to be an rt2800usb<br />
*** dmesg output "usbcore: registered new interface driver rt2800usb"<br />
<br />
* '''SMC'''<br />
** SMCWUSBS-N: Hardware detected as rt2800, but it is missing firmware; "sudo apt-get install firmware-ralink" fixed it<br />
** SMCWUSB-G (also sold as the "SMC EZ Connect g"): Gives "couldn't load firmware" error. "sudo apt-get install zd1211-firmware" fixes it.<br />
<br />
* '''Sony'''<br />
** Sony UWA-BR100 802.11abgn Wireless Adapter [Atheros AR7010+AR9280] (Vendor ID: 0411, Product ID: 017f) - Tested with Raspbian. Needs package firmware-atheros.(B)<br />
<br />
* '''Tecknet'''<br />
** TK-WD688N5 Ralink RT5572-based, see RT5572 notes<br />
<br />
* '''Tenda''' <br />
** USB 11n adapter on a G network: Ralink 2870/3070 driver (!)<br />
** Tenda W311M Wireless N150 Nano USB Adapter ([http://www.tenda.cn/tendacn/Product/show.aspx?productid=375 product page]) - Works out-of-the-box with Raspbian as of 2012-12. Tested in WPA-Personal network. Runs without Powered Hub when plugged into Raspberry Pi.<br />
** 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.<br />
** Tenda W311U Mini 11N Wireless USB Adapter (USB-ID 148f:3070): Ralink 2870/3070 driver; needs powered hub. [http://blog.modmypi.com/2012/06/installing-tenda-w311u-mini-wireless.html Debian installation instructions] Available from the [https://www.modmypi.com/raspberry-pi-accessories/tenda-wireless-n150-usb-network-adapter ModMyPi Raspberry Pi Shop] <br />
** Tenda W311U+ Wireless USB Adapter - Tested with Raspbian.<br />
<br />
*'''The Pi Hut'''<br />
** USB 802.11n Wi-Fi adapter (from [http://thepihut.com/products/usb-wifi-adapter-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''TP-Link'''<br />
** 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<br />
** 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<br />
** 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.<br />
** 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.<br />
** 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)<br />
** TL-WN723N (RTL8188SU); works OOTB with Raspbian 2012-09-17, (B) stable with 1&nbsp;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)<br />
** 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.<br />
** [http://wikidevi.com/wiki/TP-LINK_TL-WN725N_v1 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 - [http://raspberry-at-home.com/hotspot-wifi-access-point/ instructions and config script]<br />
** [http://wikidevi.com/wiki/TP-LINK_TL-WN725N_v2 TL-WN725N v2]. Needs [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=29752 manual driver installation]. This USB adapter is based on the Realtek RTL8188EUS chipset.<br />
** TL-WN727N v3 (rt2800usb, install package firmware-ralink). Works with Raspbian, supports hostapd. Does NOT require powered hub, works directly plugged into Raspberry with proper power supply (850mA, 1A worked). 40Mhz doesn't work.<br />
** 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)<br />
** TL-WN821N v4 (RLT8192CU), works out of the box on Arch, complains but works. Needs powered USB hub.<br />
** TL-WN822N v2 (ath9k_htc) works on ArchLinuxARM, with powered USB Hub. Successfully tested hostapd/dnsmasq.<br />
** TL-WN823N Works out of box on Raspian using powered USB Hub<br />
** TL-WN7200ND works. Can be made as a WiFi AP using hostapd. Need a powered USB hub.<br />
** TL-WDN3200 See Ralink RT5572 notes.<br />
<br />
* '''Trendnet'''<br />
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-648UBM TEW-648UBM] USB ID: 20f4:648b, works OOTB with [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/ Adafruit Occidentials Raspbian Wheezy variant] as it includes kernel with [http://www.wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model%3A%3ARTL8188CUS%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols%0D%0A%3FMIMO+status%0D%0A%3FOUI%0D%0A&sort_num=&order_num=ASC&eq=yes&p%5Bformat%5D=broadtable&p%5Blimit%5D=500&p%5Bsort%5D=&p%5Boffset%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Blink%5D=all&p%5Bsearchlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&eq=yes RTL8188CUS driver built-in] (B)<br />
** [http://www.wikidevi.com/wiki/TRENDnet_TEW-649UB TEW-649UB] Works with OpenElec 3.0, chipset Realtek RTL8191SU<br />
<br />
* '''Widemac'''<br />
** RT5370 Wireless Adapter from [http://www.ebay.co.uk/itm/180887771838?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649 Ebay] runs without powered hub. Follow these [http://elinux.org/RPi_Ralink_WLAN_devices instructions], but go to [http://ftp.de.debian.org/debian/pool/non-free/f/firmware-nonfree/ ftp.de.debian.org/debian/pool/non-free/f/firmware-nonfree/] and pick the latest firmware-ralink_0.xx_all.deb<br />
<br />
* '''ZyXEL'''<br />
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)<br />
** NWD2205 USDB ID: 0586:341f RTL8192CU chipset, works out-of-the-box<br />
** [http://www.zyxel.com/products_services/g_202.shtml G-202] model 0586:3410 ZyXEL Communications Corp. ZyAIR G-202 802.11bg using zd1211rw kernel module and zd1211-firmware package<br />
<br />
==Problem USB Wi-Fi Adapters==<br />
<br />
These adapters were tested and found to have issues the Raspberry Pi. Note [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6928] as a possible solution/explanation for errors while running LXDE.<br />
<br />
* '''Alfa'''<br />
** AWUS036NHA (Vendor ID: 0cf3, Product ID: 9271) - Tested with Raspbian. Works fine if connected after boot. Kills boot process if previously attached. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=16809&p=169469#p169469 Details here.]<br />
<br />
* '''D-Link'''<br />
** ( DWA-131 (rev. B1) ) - Works now on Raspbian's kernel 3.6.11+ or with DLink firmware: http://tsd.dlink.com.tw/<br />
** 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<br />
<br />
* '''Edimax'''<br />
** 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)<br />
** 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.<br />
** EW-7811Un It doesn't support Access Point and you can't use it for hostapd.<br />
<br />
* '''Linksys'''<br />
** WUSB300N (Vendor ID: 13B1, Product ID: 0029) - Tested with Raspbian, OpenELEC, among others. No Linux chipset support for Marvell 88W8362 at all.<br />
<br />
* '''LogiLink'''<br />
** WL0085 tested under Debian (Squeeze, Wheezy, Raspbian); no stable connection can be established. This gets even worse when X is running.<br />
<br />
* '''MicroNEXT'''<br />
** MN-WD152B (Debian image) modprobe hangs when plugged in, lsusb hangs. udevd errors in the logs. [http://www.element14.com/community/thread/17632] [http://www.raspberrypi.org/phpBB3/viewtopic.php?t=6737]<br />
*** Possible fix: try the new [http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1 Adafruit Occidentalis v0.1] image (based on Raspbian Wheezy) as it includes the needed 8192cu driver builtin to the kernel<br />
<br />
* '''Netgear'''<br />
** WNDA3100v2 tested with Debian (Wheezy); no driver for broadcom chipset (see [http://www.wikidevi.com/wiki/Netgear_WNDA3100v2 http://www.wikidevi.com/wiki/Netgear_WNDA3100v2]).<br />
<br />
* '''Pandigital 802.11g'''<br />
** Shows up in output of lsusb as: ID 0ace:1215 ZyDAS ZD1211B 802.11g<br />
** Kernel driver automatically loaded: zd1211rw<br />
** Circumstances tested:<br />
*** Directly plugged into RasPi's USB port<br />
*** Plugged into powered USB hub<br />
*** Plugged into unpowered USB hub<br />
** Will associate with access points that do not use encryption and which use WPA-PSK.<br />
** Periodically deconfigures itself (layers 1-3) and become unresponsive.<br />
** Can be put into ad-hoc mode for an hour or two at a time but will eventually glitch out and become unresponsive.<br />
<br />
* '''Realtek'''<br />
** RTL8188CUS USB-ID 0bda:8176, kernel oops in dmesg and freeze when pulled from USB. (B)<br />
<br />
* '''Trendnet'''<br />
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora & Arch; rtl8187 driver; errors with LXDE running (B)<br />
<br />
* '''TP-Link'''<br />
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; errors with LXDE running (B)<br />
** TL-WN723N USB ID: 0bda:8176; tested on Arch without a powered hub; it seems to draw too much current.<br />
** [http://wikidevi.com/wiki/TP-LINK_TL-WN723N_v3 TL-WN723N V3] USB ID: 0bda:8179; Needs custom driver on Raspbian wheezy.<br />
<br />
== References ==<br />
<references><br />
</references><br />
<br />
{{Template:Raspberry Pi}}</div>ACc