https://elinux.org/api.php?action=feedcontributions&user=AutoStatic&feedformat=atomeLinux.org - User contributions [en]2024-03-29T09:39:52ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=Talk:RPi_Upstream_Kernel_Compilation&diff=389761Talk:RPi Upstream Kernel Compilation2015-09-13T17:43:00Z<p>AutoStatic: Talk page autocreated when first thread was posted</p>
<hr />
<div></div>AutoStatichttps://elinux.org/index.php?title=Thread:Talk:RPi_Upstream_Kernel_Compilation/chrt_-i_0&diff=389756Thread:Talk:RPi Upstream Kernel Compilation/chrt -i 02015-09-13T17:42:59Z<p>AutoStatic: New thread: chrt -i 0</p>
<hr />
<div>Why would you want to use chrt this way together with -j 8? I assume you use -j 8 to speed up the compilation process but at the same time you give that process the least priority possible so basically any other process gets priority and thus slows down the compilation process. Seems kind of contradictory to me ;)</div>AutoStatichttps://elinux.org/index.php?title=RPi_SD_cards&diff=376941RPi SD cards2015-03-29T13:29:11Z<p>AutoStatic: Fixed typo</p>
<hr />
<div>== SD cards ==<br />
<br />
The SD card is a key part of the Raspberry Pi; it provides the initial storage for the Operating System and files. Storage can be extended through many types of USB connected peripherals.<br />
<br />
When the Raspberry Pi is 'switched on', i.e. connected to a power supply, a special piece of code called the bootloader is executed, which reads more special code from the SD card that is used to start up the Raspberry Pi. If there is no SD card inserted, it will not start. Do NOT push in or pull out an SD card while the Raspberry Pi is connected to the power, as this is likely to corrupt the SD card data (you might get away with it, but it is best not to).<br />
<br />
The SD card must be formatted, or written to, in a special way that means the Raspberry Pi can read the data it needs to start properly. If you are new to this check the instructions, or buy a pre-formatted SD card.<br />
<br />
One advantage to using an SD card like this is that you can have several SD cards, each with a different operating system, or a different purpose. Simply power off, switch cards, and reconnect the power. You have a different computer to play with.<br />
<br />
Please bear in mind that the maximum throughput of the card reader of the Raspberry Pi is 25 MB/s and that most likely read and write speed won't exceed 22 MB/s.<br />
<br />
=== Which SD card? ===<br />
<br />
[[File:SD_Card_dimensions.png|right|frameless|SD card sizes]]<br />
<br />
SD cards come in three physical sizes (see picture). The Raspberry Pi A and B use the largest one; the miniSD card and the MicroSD card can be used in those models, but you will need an adapter / holder to fit it. The Raspberry Pi B+ and Raspberry Pi 2 Model B (second generation) require the smallest one, the MicroSD.<br />
<br />
SD cards come in a range of storage sizes. You will likely need more than 2 GB.<br />
<br />
There are other properties of SD cards that are not covered here. Read the [http://en.wikipedia.org/wiki/Secure_Digital Wikipedia article] for those details.<br />
<br />
=== Other SD card content ===<br />
<br />
See the following links for other information:<br />
<br />
* [[RPi_Distributions | Select a Distribution]]<br />
<br />
* [[RPi_Easy_SD_Card_Setup | Easy SD card set up]]<br />
<br />
* [[RPi_Advanced_Setup | Advanced set up]]<br />
<br />
* [[R-Pi_Troubleshooting#SD_cards | Troubleshooting]]<br />
<br />
== Preinstalled SD cards ==<br />
<br />
You might like to consider buying a preinstalled card; a wide range of branded SD cards preinstalled with operating systems are available. If you don't buy a preinstalled card, you will have to create one yourself. Check the [[RPi_Easy_SD_Card_Setup | SD Card setup]] page to help you make this decision. That page also shows where these cards can be bought from.<br />
<br />
==Verification==<br />
<br />
Users have listed working and non-working cards here. The [https://www.sdcard.org/home SD Card Association] suggests there are more than 400 brands across dozens of product categories and more than 8,000 models. These are just a few.<br />
<br />
=== Is this reliable? ===<br />
<br />
Unfortunately there is little scope for analysis of the failures given below. There are several reasons why a card may not work. You will notice that the same card may be shown as working and not working; the model numbers on cards do seem to be confusing.<br />
<br />
* the firmware / bootloader on early Raspberry Pi boards had a problem with Class 10 high speed cards. This has been fixed.<br />
* the drivers in some Linux distributions have been improved since the initial release<br />
* the Raspberry Pi can suffer from performance problems if peripherals are drawing too much power from the power supply; one of the consequences is errors from the SD card<br />
* unless using a preinstalled card, users have to copy a distribution image to the SD card. This might be considered more technical than the user has previously experienced, resulting in a faulty SD card<br />
* there are many cheap Chinese copies of (brand name) SD-Cards on the market, in addition they are often mislabelled as having greater capacity than they really have, see [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit SanDisk counterfeit cards]<br />
<br />
... and of course, they may be faulty!<br />
<br />
=== Technical Information ===<br />
<br />
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)<br />
<br />
For this reason, please specify product numbers in the lists below, when possible.<br />
<br />
You can also attach the following fields from your card's CID:<br />
<pre><br />
cd /sys/class/mmc_host/mmc?/mmc?:*<br />
echo "man:$(cat manfid) oem:$(cat oemid) name:$(cat name) hwrev:$(cat hwrev) fwrev:$(cat fwrev)"<br />
</pre><br />
<br />
=== Working / Non-working SD cards ===<br />
<br />
The table can be sorted using the triangles in the top row. Please add entries in the correct location, so that the initial sort is by Manufacturer, Type, Size and Class. Keep separate entries for working and non-working. Put your user name and date in the final column, so people can judge if the problem is still likely to occur.<br />
<br />
{| class="wikitable sortable"<br />
! OK !! Manufacturer !! Type !! Size (GB) !! Class !! Model !! Info !! Logged by<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|7DAYSHOP.CzOM<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Ap 3 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Acumem<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|many errors on 7 Jun 2012<br />
|S0rce 8 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|SDHC<br />
|2<br />
|?<br />
|Speedy (MMAGF02GWMCA -NA)<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|2<br />
|2<br />
|Speedy 8B0947<br />
|<br />
|Stevhorn 14 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|4<br />
|4<br />
|ASDH4GCL4-R<br />
|Possibly a bit slow. Stiff to pull out of the PI.<br />
|James.C 24 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|4<br />
|4<br />
|BH1109416141G<br />
|<br />
|Blutme 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|2<br />
|MMB3F08GWMCA-GE<br />
|<br />
|Timishier 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|6<br />
|MMAGR08GUDCA-DB<br />
|sometimes boots (Dattaway)<br />
|Florz 26 May 2012, Dattaway 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|10<br />
|AUSDH8GCL10-R, P-SDH8G10-EC, ASDH8GCL10-R<br />
|<br />
|Elatllat 22 Dec 2011, Madcow42 18 Jul 2012, Thenix 14 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|16<br />
|6<br />
|<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0<br />
|Semtex 21 May 2012, Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|SDHC<br />
|16<br />
|6<br />
|SD5MY168G0<br />
|won't boot<br />
|Nijntje 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|16<br />
|10<br />
|16GSDHC10, ASDH16GUICL10-R<br />
|<br />
|Captainralf 6 Jun 2012, honza801 7 Jan 2013, CopperHead4750 28 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|32<br />
|10<br />
|AUSDH32GCL10-R<br />
|<br />
|Tom3f 13 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|MicroSD w/ adapter<br />
|0xAF 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|8<br />
|10<br />
|AUSDH8GUICL10-RA1<br />
|MicroSD w/ adapter<br />
|johnniepop 15 Apr 2013,(Elpadre 24/Nov/14)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GCL10-RA1<br />
|with adapter<br />
|Frank26080115 1 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-R<br />
|Raspberry Pi B+<br />
|zl2wrw 1 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x0 fwrev:0x2 Raspberry Pi B+ 2014-12-24-wheezy-raspbian<br />
|c 21 Jan 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi 2 B 2015-02-02-wheezy-raspbian<br />
|c 13 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi 2 B 2015-01-30-wheezy-raspbian: note: OK after running update!!<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi B 2015-01-30-wheezy-raspbian<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi B+ 2015-01-30-wheezy-raspbian<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|32<br />
|10<br />
|AUSDH32GCL10-RA1<br />
|2013-05-25-wheezy-raspbian<br />
|pAIgn10 6 Jun 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|microSDHC<br />
|64<br />
|10<br />
|<br />
|with adapter<br />
|rolgiati 2 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Agfa<br />
|microSDHC<br />
|16<br />
|6<br />
|<br />
|with adapter ENAAJK121960<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|AmazonBasics<br />
|SDHC<br />
|4<br />
|10<br />
|B004Q3R9AQ<br />
|We have had a 50% failure rate on these with file system corruption, even with write protection enabled, with Raspian<br />
|pgardella 27 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|8<br />
|10<br />
|B0058GH0LS<br />
|<br />
|Reid 7 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|16<br />
|10<br />
|B0058GH1IK<br />
|Tested 24 Jun 2012 no errors found<br />
|M3ch4 26 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|AmazonBasics<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|many errors on 7 Jun 2012<br />
|S0rce 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Lrosengreen 16 Aug 2012<br />
|-<br />
|style='background-color:#a00;'| nok<br />
|Ansonchina<br />
|microSDHC<br />
|32<br />
|10<br />
|EVO<br />
|Card from Aliexpress, Tested on RPi B+<br />
|Kimvais 2015-02-26<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Apacer<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|<br />
|Hamish 13 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Apacer<br />
|SDHC<br />
|16<br />
|10<br />
|AP16GSDHC10<br />
|Does not boot / io error from dmesg with os running from usb.<br />
|Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Apacer<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|with adapter<br />
|Jasen 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|SDHC<br />
|4<br />
|10<br />
|4GBSDHC10<br />
|<br />
|Dick Jones, 24 Sept 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|SDHC<br />
|16<br />
|4<br />
|1447<br />
|<br />
|Uberfoo 23 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|MicroSDHC<br />
|32<br />
|10<br />
|<br />
|Raspberry Pi 2 Model B<br />
|Riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CnMemory<br />
|SDHC<br />
|8<br />
|4<br />
|84209_8GB_SDHC (Silver/Black label says 'High Capacity Card') Maplins<br />
|operation is much slower than with a SanDisk 4GB Class 4 card<br />
|Ceptimus 2 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CnMemory<br />
|microSDHC<br />
|8<br />
|10<br />
|86071<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0. write 10.4 MB/s, read 20.1 MB/s<br />
|fiodschi, 19 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CoreMicro<br />
|microSDHC<br />
|8<br />
|4<br />
|CMMICROSDCL4/8GB<br />
|man:0x000082 oem:0x4a54 name:NCard hwrev:0x1 fwrev:0x0<br />
|Dick Jones, 4 Dec 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Dane-Elec<br />
|SDHC<br />
|4<br />
|4<br />
|DA-SD-4096-R<br />
|Error -110 whilst initialising sd card <br />
|captbrando, 04 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dane-Elec<br />
|SDHC<br />
|16<br />
|4<br />
|<br />
|<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dane-Elec<br />
|SDHC<br />
|16<br />
|10<br />
|Pro 200X DEMS16GB2683ENBA<br />
|<br />
|Ivazquez 15 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Delkin<br />
|SDHC<br />
|4<br />
|6<br />
|Delkin pro<br />
|works with Fedora Beefy Miracle 17<br />
|Gersh 7 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dick Smith<br />
|SDHC<br />
|4<br />
|4<br />
|XG4958<br />
|<br />
|James.C 14 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dick Smith<br />
|SDHC<br />
|8<br />
|4<br />
|XG4959<br />
|This 8GB DSE SD (S608G1137) works fine on latest Raspbian as at Dec 2013<br />
|Sauce 3 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dikom<br />
|SDHC<br />
|16<br />
|10<br />
|207H3MD016IBSD<br />
|<br />
|Churchill 1 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|16<br />
|10<br />
|Pro Photo 200x<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0 (~4.6MB/s read, ~4.4MB/s write on debian6-19-04-2012)<br />
|Bedevere 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SD<br />
|2<br />
|?<br />
|<br />
|man:0x000027 oem:0x5048 name:SD02G hwrev:0x2 fwrev:0x0<br />
|Incyi 7 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SD<br />
|16<br />
|10<br />
|EKMSD16G150XHC<br />
|less than half as fast as Sandisk 16gb Class 10<br />
|Declension 8 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|4<br />
|4<br />
|EKMSD4G60XHCN<br />
|<br />
|Korban 18 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|EKMSD8G150XHC<br />
|~17 MB/s read / ~14 MB/s write in 'dd' (man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0)<br />
|NC 10 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|180SD10MK8<br />
|MicroSD w/ adapter for Model: B+<br />
|SA 4 Oct 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|EKMSD8G150XHC<br />
|Both Raspmc and OpenElec tries to boot, but throws lots of errors<br />
|vygandas 12 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Extrememory<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0<br />
|Fjen 10 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Extrememory<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0<br />
|Mfg 3 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Extrememory<br />
|SDHC<br />
|32<br />
|10<br />
|Marked "Hyperformance"<br />
|<br />
|MathieuMD 29 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fuji<br />
|SDHC<br />
|32<br />
|10<br />
|P10NM00580A<br />
|(man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0)<br />
|Crashmeplease 28 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fujifilm<br />
|SDHC<br />
|8<br />
|4<br />
|P10N079840A<br />
|<br />
|Paul 26 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fujifilm<br />
|SDHC<br />
|8<br />
|10<br />
|A94125 1464<br />
|<br />
|sukram230799 06 Sep 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Goodram<br />
|SDHC<br />
|8<br />
|10<br />
| SDC8GHC10PGRR9<br />
|<br />
|MPastuszko 17 July 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Chmurli 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|16<br />
|4<br />
|SDU16GHCAGRR10<br />
|<br />
|Mojca 22 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|<br />
|Druss 5 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|GSkill<br />
|SDHC<br />
|16<br />
|10<br />
|FF-TSDG16GA-C10<br />
|<br />
|GKontadakis & Jim Kastrinakis (the toxic duet of IT) 31 Aug 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|GSkill<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Flatline403 12 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDHC<br />
|2<br />
|2<br />
|<br />
|<br />
|Mikerr 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDHC<br />
|8<br />
|6<br />
|High Speed Pro<br />
|<br />
|Bubblebobble 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hema (Dutch dept. store)<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Frankivo 25 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDXC<br />
|128<br />
|10<br />
|00114945<br />
|Tested with Raspbian (dd + resize) and works without issues.<br />
|SebastianB 21 Jun 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hema (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Hjongste 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HIDISC<br />
|SDHC<br />
|8<br />
|10<br />
|HDPSDH8GC10<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Nkt00125 06 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HP<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|doesn't reboot during first time startup process, but restart again and fine after that<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HP<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Harkin 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|SDHC<br />
|4<br />
|10<br />
|<br />
|<br />
|CurlyMo 1 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|image write had issues, might be my inexperience. It boots & shows Xserver<br />
|BjornW 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Wieltje 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|(20 MB/sec)<br />
|Alphons 2 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|32<br />
|10<br />
|<br />
|(20 MB/sec)<br />
|Alphons 2 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Imation<br />
|SDHC<br />
|32<br />
|10<br />
|S732G1232<br />
|mmc0: controller never released inhibit bit(s)<br />
followed by many and various <br />
mmc0: timeout errors<br />
|ChrisGreen 28 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|4<br />
|4<br />
|SD-K04G (purple label), SD-M04G<br />
|<br />
|Dmd 27 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|4<br />
|4<br />
|S404G1115<br />
|<br />
|Pluggster 16 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|4<br />
|10<br />
|Ultima Pro<br />
|<br />
|Ace 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|6<br />
|Ultima Pro<br />
|initial error -110 but boots within 5 seconds with no further errors or issues<br />
|Bubblebobble 17 May 2012mmc0: controller never released inhibit bit(s) and<br />
mmc0: timeout<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro (20 MB/s)<br />
|works: initial error -110 but boots within 5 seconds with no further errors or issues<br />
|Auldy 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro 20MB/s SD-K08G - 1238-W19718L<br />
|Works fine.<br />
|mpmc 22 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro 20MB/s SD-K08G - 1245-WJ1479L<br />
|Gets too hot and wont boot.<br />
|mpmc 22 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|16<br />
|6<br />
|Ultima Pro<br />
|<br />
|Zagblorg 26 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|16<br />
|6<br />
|Ultima Pro (SH016GAA2BB)<br />
|<br />
|Jmg123 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|16<br />
|10<br />
|Ultima Pro<br />
|20 MB/s<br />
|Tomgco 17 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|FLX 2 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|32<br />
|10<br />
|Ultima Pro (20 MB/s)<br />
|<br />
|Ab30021190 30 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|Tested with Raspbian 2013-12-20, with the included microSD adapter.<br />
|Plof 1 January 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|(Intenso)<br />
|SDHC<br />
|16<br />
|4<br />
|<br />
|<br />
|johnniepop 15 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|(Intenso)<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2 OpenELEC 3.10.20 write 8.0MB/s read 10.6MB/s<br />
|Cosbug 28 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Joyflash<br />
|SDHC<br />
|16<br />
|10<br />
|LTSD1112016GB<br />
|<br />
|Vk2amv 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingmax<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingmax<br />
|microSDHC<br />
|4<br />
|4<br />
|KM04GMCSDHC4<br />
|won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingmax<br />
|microSDHC<br />
|8<br />
|4<br />
|KM08GMCSDHC41A<br />
|won't reboot when it's hot<br />
|Slabua 2 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SD<br />
|2<br />
|<br />
|KING-SD-M02G-BULK<br />
|(0xAF 12 Jun 2012) boots the kernel, but damages the filesystem<br />
|Md84419 5 Nov 2011, 0xAF 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB<br />
|<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|<br />
|James.C 20 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|(man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0), boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|One or two worked perfectly, but most of them showed filesystem corruption after some months, usually (but not only) after power loss. Read-only filesystem didn't fix the issue. Tested on 20 SD cards on 15 different Raspberry Pi model B.<br />
25-02-2015 update: I found that all the broken SD cards were made in Taiwan. The only one made in Japan is still working (from 19/04/2012).<br />
|Gabriele Martino 23 Dec 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|Boots kernel but won't run init (times out). (works fine - Malvineous)<br />
|RoSha 10 May 2012, Malvineous 17 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|10<br />
|SD10V/4GB<br />
|<br />
|Luismreis 2 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|4<br />
|SD4/8GB<br />
|Works reliably with Raspbian 18-9-2012 and previous Debian releases (Picards)<br />
|Md84419 5 Nov 2011, Picards 28 Oct 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|4<br />
|SD4/8GB<br />
|does not work with current build of raspbmc (LastSilmaril), unreliable with raspbian (Quentinsf)<br />
|LastSilmaril 24 May 2012, Quentinsf 20 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|6<br />
|SD6/8GB<br />
|errors on boot, but ok (Debian), does not work with raspbmc rc2 or archlinux<br />
|Jamsta 5 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10G2/8GB ultimateX 100X, SD10V/8GB ultimateX 120X<br />
|<br />
|ShiftPlusOne 24 Apr 2012, Stevepdp 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10G3/8GB Elite<br />
|Works with Raspbian Wheezy 25/05/2013 <br />
|Deicide 17 July 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10V/8GB<br />
|<br />
|KingC 7 February 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|4<br />
|SD4/16GB<br />
|<br />
|Skiesare 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|4<br />
|SDC4/16GB17<br />
|Works with Raspbian wheezy.<br />
|atakanaksit 24/08/2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|6<br />
|SD6/16GB<br />
|<br />
|Malvineous 17 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10G2/16GB ultimateX 100X, SD4/16GBET<br />
|<br />
|Stevepdp 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0372-002. A00LF TAIWAN JM94450-901.A00LF)<br />
|Seems to work<br />
|Epa 20130403<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB<br />
|<br />
|Franeks 14 Feb 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10G2/16GB ultimateX 100X<br />
|mmc0: Timeout waiting for hardware interrupt<br />
|Kimmoli 27 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB<br />
|Starts boot ok but then gets stuck in mmc0 timeouts<br />
|Hh 14 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0440-001. A00LF TAIWAN JM94513-908.A00LF)<br />
|mmc0 timeouts<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0440-002. A00LF TAIWAN JM94585-902.A00LF)<br />
|not booting. no hdmi output. red leds on solid, green leds very lightly dimmed, no green flash/blink<br />
|smerz 20131230<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|32<br />
|10<br />
|SD10G2/32GB, ultimateX 100X, SD10V<br />
|<br />
|Tony 29 May 2012, Pmvarsa 17 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|32<br />
|10<br />
|SD10V/32GB <br/>(N0415-002.A00LF TAIWAN JM94450-913.AOOLF)<br />
|works<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SDX10V/64GB<br />
|<br />
|Bromont 25 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SDCX10/64GB<br />
|2015-02-16-raspbian (a bit slow)<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SD10G3/64GB UHS-I Elite<br />
|<br />
|Plnt 10 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDX<br />
|128<br />
|10<br />
|SDX10V/128GB<br />
|Must format it as FAT32. Took a very long time for Pi to install system.<br />
|H. Matis 3 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|2<br />
|<br />
|N0185-002.A00LF<br />
|Adapter (File system .img written via Transcend microSDHC "USB stick-like" adapter - P3-102510)<br />
|TrevorGowen 27 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|2<br />
|<br />
|SD-CO2G<br />
|Does not boot. Capacity (1.97 GB) seems only just enough for 2013-02-09-wheezy-raspbian.img (1.94 GB). <br />
|Pe7er 18 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Bredman 16 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC4/4GB (CO4G)<br />
|Works great with Kingston SD adapter<br />
|Horgrim 03 Mar 2015<br />
|-<br />
|style='background-color:#c00;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC4/4GB (CO4G)<br />
|Starts to boot and fails. "... Kernel panic ... unable to mount root fs on unknown block ... "<br />
|ow3n 4 Oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|8<br />
|4<br />
|SDC4/8GB<br />
|Does not work with NOOBS (do not recognize it) or applying an image of Debian or Fedora on it (Kernel panic ... cannot mount fs) <br />
|Lilt 9 May 2012 * ElPadre 15 April 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|4<br />
|SDC4/16GB<br />
|man:0x000002 oem:0x544d name:SA16G hwrev:0x1 fwrev:0x1 * Filesystem is corrupted on a daily basis (Raspbian) <br />
|Rmoser 16 June 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|4<br />
|SDC4/32GB (C32G)<br />
|<br />
|ow3n 8 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|10<br />
|SDC10/4GB<br />
|man:0x000041 oem:0x3432 name:SD4GB hwrev:0x3 fwrev:0x0 Works on Raspian 2014-12-24 with RPi Model B+<br />
|c 22 Jan 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|8<br />
|10<br />
|SDC10/8GB<br />
|Work on Raspian, '''but doesn't work with NOOB'''. [Suggestion : download full image of O.S. and put it into SD card directly.]<br />
'''Works with NOOBS'''<br />
<br>Sometimes I/O errors and: mmc0: timeout waiting for hardware interrupt<br />
<br>'''Does not work in RPi Model B+ with RaspBMC'''. Starts booting but all writes fail.<br />
<br>'''NOOBS works fine''', installed Arch and Raspbian successfully.<br />
|webserfer 03 March 2013 submarine 03 Jan 2014 diogobackup 23 Jan 2014 felon 20 July<br />
javierrgz 3 Sep 2014<br />
<br><br />
tinkergnome 24 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|10<br />
|SDCA10/16GB (SD16G)<br />
|2014-09-09-wheezy-raspbian.img, man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0<br />
|bcraun 5 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|10<br />
|SDC10/16GB<br />
|Doesn't work with N0390-002.A00LF though (tested with Raspbian “wheezy”) - mmc0 timeouts, waiting for hw int. I wouldn't recommend buying this card. N0460-002.A00LF: Does not boot / io error from dmesg with os running from usb.<br />
|Arrow 14 Jun 2012, J3rGuS 19 March 2013, Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|10<br />
|SDC10/32GB<br />
|Tested with Raspbian wheezy on RPI B+, no problem so far.<br />
|Julien Bonnier 30 Sept 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|10<br />
|SDC29/32GB<br />
|tried it with retropie raspian 7.5 so far no problems<br />
|Guido(dakiluxa) 27 Fun 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kodak<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kodak<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Britaniola 22 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kruidvat (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Boeboe 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kruidvat (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Asiklov 25 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|Boots consistently and no error messages in log after 1/2 hour use (works with Raspbmc - 321liftoff)<br />
|Russell 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|4<br />
|6<br />
|Platinum II<br />
|<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|4<br />
|Milti-Use SDHC LSD8GB ASBWMC2 rev.B, on card 31352-oc4-8gbbm-a<br />
|sold in 1 or 2 pack<br />
|Spyder Mar-2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|6<br />
|Platinum II<br />
|<br />
|Shirro 7 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|6<br />
|Premium series<br />
|<br />
|blazi 17 December 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|10<br />
|Platinum II (200X) LSD8GBBBEU200C10<br />
|Works fine on OpenElec 3.0.6<br />
|Vygandas 18 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|10<br />
|Platinum II UHS-I (LSD8GBBSBNA200C10 Rev C)<br />
|Works fine w/NOOBS v1.3.4 Raspbian<br />
|fortran87 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|16<br />
|6<br />
|Platinum II<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|32<br />
|10<br />
|Platinum II SDHC UHS-I<br />
|<br />
|Dedejacoby 11 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDXC<br />
|64<br />
|10<br />
|Premium series<br />
|UHS-I<br />
|Kuisma 17 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDXC<br />
|128<br />
|10<br />
|LSD128CTBNA400<br />
|UHS-I<br />
|AdamGreenblatt 12 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|microSDHC<br />
|16<br />
|10<br />
|(LSDMI) 16GBBEU300A<br />
|Raspberry Pi B+ Model (tested on OpenELEC,xbian, raspbmc, kali linux)<br />
|@xhark 05 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|microSDHC<br />
|32<br />
|10<br />
|HIGH-SPEED<br />
|<br />
|RogerH 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Master<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|[man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0]<br />
|Malvineous 1 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Master Optimum<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|Only 1 red LED lit, no HDMI output. Started booting one single time then crashed during boot. No errors writing card on Mac<br />
|User234891 23 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Maxell<br />
|SDHC<br />
|16<br />
|10<br />
|X-Series 83-P120001149-1<br />
|<br />
|Paul 26 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Maxell<br />
|microSDHC<br />
|8<br />
|10<br />
|X-SERIES 854716.00.TW<br />
|Tested with Raspberry PI A+ and Raspbian. No problems so far.<br />
|Unas 4 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Maxell<br />
|microSDHC<br />
|16<br />
|4<br />
|X-SERIES<br />
|MicroSD w/ adapter. Tested with latest version of Raspbian (as at date of entry).<br />
|Drummingsim 28 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Buadhach 29 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|SDHC<br />
|32<br />
|6<br />
|MD86965<br />
|works well with NOOBS 1-2-1, Raspbian and RiscOS<br />
|Joerg 19 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|microSDHC<br />
|32<br />
|6<br />
|MD86958<br />
|works well with NOOBS 1-2-1 and Raspbian<br />
|Joerg 14 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|microSDHC<br />
|32<br />
|10<br />
|MD87252<br />
|micro SD w/adapter on model B with Raspbian. man:0x000027 oem:0x5048 name:SD32G hwrev:0x3 fwrev:0x0<br />
|KMS 22 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Memorex Travel Card<br />
|SDHC<br />
|8<br />
|10<br />
|?<br />
|Works well with Raspbian 2013-09-25.<br />
|The Doctor, 25 October 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Memory2Go<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1029<br />
|I/O Errors leading to Kernel Panic on startup<br />
|Snohi 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MemoryStar<br />
|microSDHC<br />
|16<br />
|10<br />
|?<br />
|man:0x000089 oem:0x0303 name:NCard hwrev:0x1 fwrev:0x0 - works well with Raspbian 2014-12-24 and Asterisk 2014-07-31 images.<br />
|Carriba, 27 December 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Microcenter<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|hasn't worked with any of the images I've tried; appears to be completely unrecognized<br />
|Pnppl 11 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|8<br />
|4<br />
|0289508<br />
|(sold in bins at checkout)<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|8<br />
|10<br />
|0349728<br />
|(sold in bins at checkout)<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|(sold in bins at checkout)<br />
|Crayfishandy 11 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|64<br />
|10<br />
|<br />
|(sold in bins at checkout) ... Must format it as FAT32.<br />
|alex222888 27 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mushkin<br />
|SDHC<br />
|16<br />
|10<br />
|MKNSDHCU1-16GB<br />
|<br />
|Frank26080115 1 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mushkin<br />
|SDHC<br />
|32<br />
|10<br />
|MKNSDHCC10-32GB<br />
|<br />
|Openboat 30 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mustang<br />
|SDHC<br />
|8<br />
|10<br />
|SD8GHCCL10MU-R<br />
|<br />
|Xanatos 31 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|8<br />
|10<br />
|MYMESDH8G10<br />
|(latest batch not working - Bubblebobble)<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|MyMemory<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Jezmck 27 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|16<br />
|10<br />
|MYMESDH16G10<br />
|<br />
|Jblackburn 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Dale2507 10 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|OCZ<br />
|SDHC<br />
|8<br />
|6<br />
|Gold Series (08110596-8GB-6)<br />
|tested with debian6-19-04-2012<br />
|Alkarex 16 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Optima<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|Does not boot with Raspbian Wheezy 2012-07-15. Works with 2012-09-18<br />
|Penguintutor 19 Aug 2012 / 10 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Optima<br />
|SDHC<br />
|8<br />
|10<br />
|Pro-Speed<br />
|<br />
|DaWoodster 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Mikerr 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|4<br />
|RP-SDLB04GAK<br />
|Tested with Pidora (Fedora)<br />
|jwdietrich 06 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|10<br />
|UHS-I<br />
|(~11.2MB/s read, ~6.2MB/s write)<br />
|M4rcs 26 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|10<br />
|RP-SDRB04G<br />
|Tested with Rasbian Wheezy<br />
|jwdietrich 02 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|2<br />
|<br />
|(~11.1MB/s read, ~9.7MB/s write)<br />
|Malexmave 19 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|~4.8MB/s read, ~4.4MB/s write, following the Performance below<br />
|Xonx 21 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|10<br />
|RP-SDU08GD1K - London-2012-Collection<br />
|mmc0: timeout waiting for hardware interrupt<br />
|Selsinork 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|6<br />
|PSF8GSDHC10-PC<br />
|<br />
|Paradigmic 7 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|6<br />
|PS8GSDHC10-BC<br />
|repeatable corruption after 1 or 2 reboots with 2012-07-15-wheezy-raspbian<br />
|Ntrepid8 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|LX Series PSF8GSDHC10-PC1<br />
|<br />
|Nugget 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|LX Series PSF8GSDHC102PK<br />
|Twin pack<br />
|verket 8 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|PSF16GMCSDHC10<br />
|<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|PSF8GSDHC10-PC<br />
|won't even boot 2012-08-16-wheezy-raspbian (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc). Seems functional in Arch, but sometimes freezes at the beginning of boot (blinking underscore)<br />
|Dgatwood 12 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|16<br />
|10<br />
|LX Series PSF16GSDHC10-PC1 (PSF16GSDHC10)<br />
|Tested with Rasbian Wheezy<br />
|Leonardicus 25 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|16<br />
|10<br />
|LX Series (PSF16GSDHC10)<br />
|19.3MB/s read, 9.3MB/s write<br />
|Jamesnine 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|32<br />
|10<br />
|PSF32GSDHC10<br />
|<br />
|Megs 29 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|32<br />
|10<br />
|UHS-1 PEF32GSDHC10U1<br />
|20.4MB/s read, 12.1MB/s write<br />
|Bengoerz 12 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|microSDHC<br />
|8<br />
|10<br />
|PSF8GMCSDHC10<br />
|I observed behavior similar to the full size version of this card (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc).<br />
|CVBruce 25 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|microSDHC<br />
|16<br />
|10<br />
|PSF16GMCSDHC10<br />
|requires recent kernel update for boot<br />
|Wmdopple 9 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|microSDHC<br />
|16<br />
|10<br />
|PSF16GMCSDHC10<br />
|fails with 2012-12-16-wheezy-raspbian and with 1/8/13 kernel update. mmc0: controller never released inhibit bit(s) and<br />
mmc0: timeout waiting for hardware interrupt. Other cards work.<br />
|verket 8 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Peak<br />
|microSDHC<br />
|4<br />
|4<br />
|MMBTR04GUBCA-ME<br />
|tested with Arch<br />
|Selsinork 20 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Philips<br />
|SDHC<br />
|8<br />
|4<br />
|FM08SD35B<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Philips<br />
|microSDHC<br />
|8<br />
|4<br />
|FM08MD35B<br />
|(man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|<br />
|Njoyard 6 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|4<br />
|10<br />
|127660<br />
|Tested with a Raspbian Wheezy using a custom and a stock kernel. Both Ok.<br />
|cpb 15 oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|6<br />
| Fails with mmc error (7 cards in 10) on ccidentalis_v02. Fails on laptops which use mmc driver instead of SATA<br />
|(man:0x00006f oem:0x0000 name:SMI hwrev:0x1 fwrev:0x0)<br />
|Leucos 22 March 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|8<br />
|O08G840 M3100487 TW<br />
|<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|10<br />
|RTK247T5MD08G order no. 126982<br />
|<br />
|Cobalt 9 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|10<br />
|8DK52-131ME<br />
|hctosys.c: unable to open rtc device (rtc0)<br />mmc0: Timeout waiting for hardware interrupt - cmd18<br />mmc0: Timeout waiting for hardware interrupt - cmd12<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, retrying<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, retrying<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, aborting<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)<br />on Arch Linux ARM hf 2013-02-11<br />
|Cobalt 9 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|Does not boot with Raspbian Wheezy 2012-09-12<br />
|Palto 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDXC<br />
|64<br />
|10<br />
|<br />
|<br />
|Datafreak 30 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDXC<br />
|128<br />
|10<br />
|<br />
|man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2 Tested with BerryTerminal, NOOBS, OpenELEC, Raspbian and Raspbmc<br />
|Ienny 25 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|microSDHC<br />
|16<br />
|6<br />
|<br />
|<br />
|gecko16300 24 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Play.com<br />
|SDHC<br />
|4<br />
|6<br />
|S4E3CD04GEFAA 0907090121106<br />
|<br />
|JoeDaStudd 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SD<br />
|2<br />
|?<br />
|SD-M02G<br />
|<br />
|Ewindich 24 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|4<br />
|4<br />
|Optima (SD-K04G 0834TT1297Y)<br />
|<br />
|Weston 20 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Premium (Toshiba SD-K08G)<br />
| Works with 2014-01-07-wheezy-raspbian<br />
|PotOfJava 08 Feb 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Optima 120 HD SD-K08G 0928 WF3673<br />
|mmc -110 errors at init time on 12 Jun 2012<br />
|Zoward 12 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Premium<br />
|mmc - mmc0: timeout waiting for hardware interrupt<br />
|Davidgyoung 21 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|<br />
|Threedaymonk 5 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|6<br />
|P-SDHC8G6-EFS2<br />
|Raspian wheezy: mmc0 timed out; OpenELEC 3.2.4 not working<br />
|Gkoper 21 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|10<br />
|P-SDHC8G10-GE<br />
|1 - Tested with 2013-02-09-wheezy. 2 - On Mac, dd to image did not work, but SD Card Builder did. Wheezy read and write right at about 20MBps. After booting, I installed several packages - all fine. After that, I installed RetroPie. That took about 15 hours to download and compile - zero errors.<br />
|1 - Zambon 9 Mar 2013, 2 - RicM July 17 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|16<br />
|4<br />
| <br />
|Unstable results with Raspian Wheezy (Sporadic failed booting - "Timeout waiting for hardware interrupt"<br />
|DBlessing 12 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|16<br />
|10<br />
|P-SDHC16G10-GE, P-SDHC16G10-EF, Pro-Elite P-SDHC16U10-30-GE<br />
|Works with Wheezy, does not work with Squeeze (mmc0: timeout...), Arch (no boot) (Joshdev), or Fedora Remix. Works with Raspbmc (Sp00l)<br />
|Jecxjo 9 Jun 2012, Joshdev 22 Jun 2012, Sp00l 21 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|16<br />
|10<br />
|P-SDU16G10-GE<br />
|man:0x000028 oem:0x4245 name:SDU16 hwrev:0x1 fwrev:0x0 <br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/PNY-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|P-SDHC32G10-GE<br />
|Works with Arch 2012-09-18 and Raspbian 2012-12-16<br />
|Derekivey 29 Dec 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|P-SDH32U1H-GES3 Elite Performance<br />
|Happily banging away for over a month now; Raspbian Linux 3.6.11+ #456 PREEMPT armv6l system v,3.3.3<br />
|Jerasmussen 12 Aug 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|Professional (P-SDHC32G10-EF)<br />
|(mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)<br />
|Optim4l 9 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|Pro<br />
|Debian installation worked, [brand new] Card died a few minutes later with mmc0 timeouts, during apt-get upgrade. Never got it to work again on any system<br />
|Gryzor 10 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDXC<br />
|128<br />
|10<br />
|Model P-SDX128U1H-GE<br />
|No issues observed. Used dd on linux to write raspbian image, and rpi autoresized on first boot without problems<br />
|kansky 6 Mar 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDXC<br />
|128<br />
|10<br />
|P-SDX128U1H-GE<br />
|man:0x000003 oem:0x5344 name:SD064 hwrev:0x3 fwrev:0x0<br />
Fails under heavy write load with "mmc0: Controller never released inhibit bit(s)<br />
mmc0: Timeout waiting for hardware interrupt". Works perfectly in USB card adapter.<br />
|whitslack 25 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDXC<br />
|256<br />
|10<br />
|Model P-SDX256U1H-GE <br />
|man:0x000028 oem:0x4245 name:SD256 hwrev:0x0 fwrev:0x2 - Works with RaspBMC 2014-11-24 Release<br />
|mnejman 19 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with adapter<br />
|Zulucat 21 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|with adapter<br />
|Zulucat 6 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|16<br />
|10<br />
|P-SDU16GU190-GE<br />
|tested with OpenELEC Raspberry Pi 2 Model B<br />
|riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|32<br />
|4<br />
|P-SDU32G4-GE<br />
|tested with B+<br />
|krakrjak 2 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|32<br />
|10<br />
|<br />
|with AdaFruit adapter<br />
|Wibble 22 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Polaroid<br />
|SDHC<br />
|16<br />
|10<br />
|P-SDHC16GB10-EFPOL<br />
|mmc0: timeout waiting for hardware interrupt on debian6-19-04-2012<br />
|Jamesnine 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PQI<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|Works with official debian6-19-04-2012<br />
|Remick 12 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PRETEC<br />
|SDHC<br />
|8<br />
|10<br />
|8DK52-122ME<br />
|<br />
|ScorpAl 19 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PRETEC<br />
|SDHC<br />
|8<br />
|10<br />
|233x (PC10SDHC08G)<br />
|mmc0: timeout waiting for hardware interrupt, Sometimes does not boot, kernel panic<br />
|Petacz 8 Aug 2012, DarkKnightCZ 23 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|promaster.com<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Douglas W. Jones Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Reekin<br />
|SD<br />
|4<br />
|?<br />
|<br />
|doesn't boot<br />
|Nicobsa 11 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Genocho 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Genocho 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|4<br />
|MB-SS4GA MB-SS4GA/EU <br />
|works with 2014-01-07-wheezy-raspbian<br />
|Markus 24 Feb 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|4<br />
|MB-SS4G MBSS4GMBDDBA-DD<br />
|doesn't boot with 2012-07-15-wheezy-raspbian; OK light partially lit<br />
|Doctoruseful 19 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|8<br />
|6<br />
|MB-SS8GAEU<br />
|<br />
|Dakaix 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|8<br />
|10<br />
|MB-MP8GA, MB-SP8GA/EU, MB-SP8GA/AM<br />
|Works with latest firmware (3.12.25+ #701) and some older Raspbian. On Raspbian 2014-06-20 fails when " Mounting local filesystems... mmc0: Timeout waiting for hardware interrupt - cmd12 ".<br />
Solution: Download [https://github.com/raspberrypi/firmware/blob/master/boot/kernel.img latest firmware] and overwrite the original on the BOOT partition.<br />
|Garrocha 19 May 2012,<br />
Fridata 1 August 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|6<br />
|MB-SSAGAEU<br />
|<br />
|Dakaix 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|6<br />
|MB-SSAGB/EU<br />
|<br />
|leon.anavi 26 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SGAGB (UHS-I PRO)<br />
|<br />
|miljenko 30 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SPAGA / MB-SPAGAEU<br />
|<br />
|Optim4l 11 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SPAGC<br />
|<br />
|djayor 9 May 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|32<br />
|6<br />
|MB-SSBGBFFP<br />
|<br />
|Xerxes 02 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|32<br />
|10<br />
|MB-SSBGA, MBSSBGVEOBGA-SH<br />
|OK with Debian Wheezy. debian6-19-04-2012: mmc0: timeout waiting for hardware interrupt<br />
|Alkarex 11 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|4<br />
|6<br />
|MB-MS04D<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Raspberry B+ 2014-12-24-wheezy-raspbian<br />
|c 21 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|8<br />
|6<br />
|MMAGR08GUDCA-DB, MB-MS08DA<br />
|<br />
|Ewindich 24 Jul 2012 Felon 21 Jully 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MPAGC (MB-MPAGAEU)<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br />
|Olf 19 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16DA/EU<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/Samsung-Class10.html Details]<br />
|FastEddie 10 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MSBGAEU<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 - works with 2013-12-20-wheezy-raspbian.zip, Kernel 3.10<br />
|Johannes 24 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|64<br />
|10<br />
|MB-MGCGBA/AM<br />
|Comes with a SD adapter. Installed 2014-01-07 Raspbian Wheezy, works perfectly!<br />
|PatriotInAKilt 20 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16D<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Tested on B+ model with 2014-12-24-wheezy-raspbian - Runs apt-get update without a problem - Raspberry Pi 2 model B, corruption if ext3/4, no problem with f2fs for two weeks <br />
|c 22 Jan 2015 - manolonte 5 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16DA/EU<br />
|Tested on B+ model - Runs Raspbian and Xbian without a problem with over 48 hours of uptime<br />
|Jack 14 Nov 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10 UHS-1<br />
|MB-MP32DU2/EU (w/ USB2.0 adapter)<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 - works well with Raspbian 2014-12-24 and Asterisk 2014-07-31 images. Max. tested speed with SD cards adapter on PC: writing 20.3 MByte/s, reading 35.4 MByte/s.<br />
|Carriba, 29 December 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MP32D<br />
|Tested on B+ with 2015-02-16-raspbian-wheezy and FreeBSD 11 CURRENT on medium overclock settings for 3 days without problems<br />
|Herculesxe5, 4 February 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MP32DA/AM<br />
|Tested on B+ model - no adapter needed as it take microSD. Can install 2014-06-20 Raspbian image and boot OK. But afterwards, running sudo apt-get upgrade caused SD corruption. Tested with 2 cards, both exhibited the same problem.<br />
|Striders 24 Aug 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung EVO<br />
|microSDHC<br />
|8<br />
|10<br />
|MB-MP08D/EU <br />
|Tested on rpi2, First boot OK then overclock to 900Mhz, sync some files and won't able to reboot. Put a fresh raspian then and mmc errors hardware everywhere while booting. <br />
|H4h 14 feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|8<br />
|10<br />
|MB-MP08D<br />
|Tested on Raspberry Pi 2, overclocked to 900Mhz, initially stress tested for 24h (CPU with heatsink, temp recorded max at 60C), passed the [[RPiconfig#Overclock_stability_test|Overclock Stability Test]]<br />
|eNur 29 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDXC<br />
|64<br />
|10<br />
|MB-MP64D<br />
|Would not boot from standard Noobs - could not see image. Tested on B+.<br />
However, used stand alone Raspbian image file and used 'Partition Wizard' (this method - http://wiiudaily.com/2014/03/format-high-capacity-card-for-3ds/ )to force FAT32 and the Pi boots no problem into Raspbian on the 64GB card. Using df reports 56GB available free space after expanding file system. Seems to create a small FAT32 partition that enables booting. Still working after update, upgrade and Rpi update. After trial using Partition Wizard in the above method can confirm Pi will not boot after 'noobs' install so recommend using Win32 Disk Imager and a stand alone OS .img file after using partition wizard for anybody having problems. I have only tested Raspbian Wheezy and no other OS. *Note* any SD card genuinely above 32GB will be formatted exFAT using standard methods and the Pi requires a FAT32 system to read at boot or it fails. <br />
|Prod 26 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDXC<br />
|64<br />
|10<br />
|MB-MP64DA/AM<br />
|Appears that the Pi has difficulty booting a 64GiB SDXC card that's formatted for exFAT. This card will NOT work with default settings (1/23/2015, Model B+). Workaround: download a valid image file -- not NOOBS, it must be an image. Then, use a utility such as dd or Win32DiskImager to copy the image directly to your device. This forces a small enough FAT32 partition that the RasPi will be able to read and boot. Confirmed that the "Expand Filesystem" option for Raspian still works after reboot<br />
|Phaerus, 2015-01-23<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung PRO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MGAGB<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Tested on B+ model. 2014-12-24-wheezy-raspbian<br />
|c 22 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung PRO<br />
|microSDHC<br />
|32<br />
|10 UHS-I<br />
|MB-MG32DA<br />
|Works perfectly on RPi 2 Model B with RasPlex 0.5.1<br />
|biltong 12 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|<br />
|Extreme III (BE0715105083B)<br />
|Dscott 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|<br />
|SanDisk for Wii<br />
|Stevepdp 18 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|BE0916214253D<br />
|<br />
|Mate12345 9 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|Extreme III (BE0722702998D)<br />
|(man:0x000003 oem:0x5344 name:SD02G hwrev:0x8 fwrev:0x0) - tested with Raspbian (build 2012-07-15) and Raspbmc installer (build 2012-07-13)<br />
|Boandlkramer 5 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|2<br />
|BE0816113150D<br />
|writes at 3.5 Mb/s<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|4<br />
|Ultra<br />
|15 MB/s<br />
|Md84419 24 Sept 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|4<br />
|Ultra II, BE0719111366D<br />
|<br />
|Md84419 5 Nov 2011, Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|6<br />
|Extreme III (BE0804212046D)<br />
|20 MB/s<br />
|Nooitaf 20 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|2<br />
|?<br />
|Ultra II BE0828713280D (15 MB/s)<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|BH0820113475D<br />
|Tested with RPITC (Based on Raspbian Wheezy)<br />
|Rendyair 11 Sep 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt<br />
|Optim4l 10 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|8H825413279G "Limited Edition"<br />
|Error -110 whilst initialising sd card<br />
|Jezmck 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|SDSDB-004G-B35, BH1210821913G, SDSDB-004G-BT35<br />
|<br />
|Md84419 6 May 2012, Nicobsa 11 Jul 2012, Ingestre 12 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra II<br />
|<br />
|Britaniola 22 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|BH1030216016G, BH1031116016G<br />
|Doesn't boot<br />
|SquallStrife 15 May 2012, Vk2amv 9 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra (BH1028516076D)<br />
|Intermitant booting ( 1/50 power on ), random timeout messages when it does boot<br />
|Russell 26 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra (15MB/s) (SDSDH-004G-U46)<br />
|won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III (30 MB/s)<br />
|works with 2012-10-28-wheezy-raspbian<br />
|JeffS 11 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Ultra SDSDH-004G-U46 - BH1136121837G, BH1130521822D, BH1200421822D (30MB/s)<br />
|<br />
|Selsinork 20 Apr 2012 / Alex347 5 May 2012 / Jjuhl 26 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III C6 (BH0822411730D)<br />
|<br />
|Cmcr651 7 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III (30 MB/s) (BH0822712362G)<br />
|<br />
|Jezmck 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (BH10297143382G)<br />
|<br />
|Wrdx 19 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (SDSDX-004G-X46)<br />
|Works with RasPlex 0.3.1<br />
|Bellagio 15 Nov 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (SDSDX-004G-X46)<br />
|30 MB/s HD Video - Doesn't boot - Works with new kernel.img and start.elf (Paaland), not working with new kernel.img and start.elf 17-06-2012 or "wheezy"-beta (MrF)<br />
|Paaland 21 May 2012, MrF 19 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|writes at ~1.5MB/s<br />
|Ms705 30 Mar 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|Ultra BI1024716014G<br />
|labelled as 15MB/s<br />
|PhilH 3 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB-008G-B35S / SDSDB-008G-B35<br />
|Raspbian “wheezy”: used expand_rootfs option of sudo raspi-config command to make all 8GB available. <br />
|Swehner Jan 2013, Baji Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB-008GBQ35 / 80-56-12024-008G<br />
|Tested OK with Retro Pie<br />
|HBG 22 AUG 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB3-008G-A16BJ / BJ's 3-pack<br />
|Tested OK with RISC OS<br />
|Lanulos 11 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra SDSDH-008G-U46 / BI1131222083D, BI11321422083D (20 MB/s) & SDSDH-008G-T11 (30MB/s) & SDSDH2-008G-AC11<br />
|SDSDH2-008G-AC11 requires updated Squeeze or Wheezy beta (Jim Manley)<br />
|Dakaix 24 Apr 2012, Crox 23 Jun 2012, Jim Manley 27 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Extreme (BI1101116253G)<br />
|<br />
|Alex347 5 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra SDSDH-008G-U46 (BI1201421964G / BI1201221964G / BI1131222083D), SDSRH-008G-A11 & SDSDH-008G-T11 (30 MB/s)<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt) debian6-19-04-2012<br />
|Trebor27 15 Apr 2012 / Russell 26 Apr 2012 / ChuckHunky 8 May 2012/ Ryantm 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (BI11017514367G / BI1130916254G / B11209116254G / SDSDX-008G-X46/BI1218822414G)<br />
|May need updated bootcode.bin (BELzEBUB), Confirmed on Debian Squeeze 2012-04-19 and Arch Linux 2012-06-13 (Arces), works with Raspian R3 (Histvan)<br />
|Timer 16 May 2012, BELzEBUB 30 Jun 2012, Arces 9 Jul 2012, Histvan 14 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (SDSDX-008G-X46/BI1111816252D)<br />
|tested on 2013-02-09 Raspian and Rasplex 0.1.37<br />
|Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme Pro (SDSDXPA-008G-X46)<br />
|(95MB/s UHS-I) - Works with stock 2012-07-15-wheezy-raspbian<br />
|Incyi 28 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme Pro<br />
|Works with stock Arch Linux 2013-05-01<br />
|Perchrh 28 Apr 2012, Tiwipewo 27 May 2012, Perchrh 17 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-U46 (30 MB/s)<br />
|Works with debian6-19-04-2012 or raspbian images but not with OpenELEC r11212 (MrF). Works with OpenELEC r11493 (Vishnu vijay); works with 2013-09-25-wheezy-raspbian man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0 (tswaehn)<br />
|MrF 6 Jun 2012, Vishnu vijay 28 Jul 2012, tswaehn 07 dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-A11 (30 MB/s)<br />
|Works with raspbian images (blitzkrieg).<br />
|Blitzkrieg 26 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-T11 (30 MB/s)<br />
|Works with Arch Linux 20130813 (L. Snow).<br />
|L. Snow 27 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-UQ46 (30 MB/s)<br />
|Works with Raspbian (wheezy) 3.10.21+ (Read ~18.6MB/s Write ~14.5MB/s) man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|Sauce 3 Dec 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme BI1108716254G, BI110209116254G<br />
|<br />
|Dscott 23 Apr 2012, Max 31 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (BI1200916252D/SDSDX-008G-X46), BI1201416254G<br />
|Doesn't work with debian6-19-04-2012.img and with replacement kernel.img and start.elf (Weston). Doesn't work with Debian Wheezy beta (2012-06-18)(Halton). Doesn't work with Arch Linux 13/06/2012 (Madhur)<br />
|Weston 20 May 2012, Halton 8 Jun 2012, Madhur 27 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-B35<br />
|<br />
|NickstaDB 17 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-A11<br />
|Tested on OpenELEC, Arch, and NOOBS<br />
|funkeywoookey 9 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-FFP<br />
|Attempted with Ubuntu dd.<br />
|[[User:GKFX|GKFX]] ([[User talk:GKFX|talk]]) 18:46, 31 December 2014 (UTC)<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-AFFP<br />
|Attempted with Windows, Linux dd, and Fedora ARM installer. RPi would not load and Linux could not mount after image written to card.<br><br />
''Note: I fixed the Linux error on the presumably similar SDSDB-016G-FFP after [http://www.raspberrypi.org/documentation/installation/installing-images/linux.md remembering to <code>umount</code>]. [[User:GKFX|GKFX]] ([[User talk:GKFX|talk]])''<br />
|mwolfgang 19 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra (30MB/s) (BL1133921933G)<br />
|Works with OpenELEC r11324<br />
|Reckoner 17 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra (BL1202021933G)<br />
|<br />
|Dscott 23 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra I (BL1205921933G)<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt)<br />
|SnarlingFox 10 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Extreme<br />
|(man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0), boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme (45MB/s U1)(BL1203322025G), (30MB/s HD Video)(SDSDX3-016G-X46), (45MB/s U1)(BL1203322025G)<br />
|Doesn't work with debian6-19-04-2012 image, but does work with 2012-06-18-wheezy-beta.img and updated firmware (tested 2012-07-02). Danbowes: Working with latest RaspBMC image (tested 12/09/2012)<br />
|Flatline403 12 May 2012, Dkleeman 13 Jun 2012, Zbyszek 2 Jul 2012, Danbowes 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|SDSDQUIP-016G-A46<br />
|man:0x000003 oem:0x5344 name:SL16G hwrev:0x8 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/SanDisk-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Extreme PLUS SDSDXS-032G-A46 (80MB/s UHS-I)<br />
|RPi Model B+ - No issues or errors encountered, using RetroPie 2.3 (man:0x000003 oem:0x5344 name:SE32G hwrev:0x8 fwrev:0x0)<br />
|arcooke 21 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme Pro SDSDXPA-016G-A75 (95MB/s UHS-I)<br />
|Doesn't work with stock debian6-19-04-2012 image, but does work with freshly compiled kernel<br />
|AXon 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Ultra (30MB/s UHS-I) (SDSDU-016G-U46) (SDSDU-016G-U46S)<br />
|Works with debian6-19-04-2012 (Misox12). Kernel Panic with debian6-19-04-2012. Worked fine with Wheezy image (Casestudies). Works fine with Raspbian Wheezy 2013-02-09, man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0 (Fraoch). <br />
|Misox12 30 May 2012, Casestudies 30 Jun 2012, Fraoch 25 March 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|SDSDQUAN-016G-G4A<br />
|Works great with Raspbian [2015-02-16]; man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|john Pi-day 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Ultra microSDHC I UHS-I<br />
|man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0. Works again since raspberrypi-firmware 20130116 in archlinux-arm. write 6.8 MB/s, read 21.0 MB/s<br />
|fiodschi, 19 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme SDHC (45MB/s UHS-I) (SDSDX-016G-X46)<br />
|Works with Raspbian “wheezy” and works with OpenELEC<br />
|Fazdogg 08 Jan 2013; Shadyeglenn 14 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|4<br />
|<br />
|<br />
|Daviewales 30 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|6<br />
|<br />
|<br />
|Helpme1986 22 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Extreme (45MB/s UHS-I) (SDSDX-032G-X46)<br />
|works with arch-04-29-image and latest firmware (booting problems without firmware update) / works with debian wheezy kernel 3.2.27+ (jLo)<br />
|Malhelo 8 Jun 2012 / jLo 2 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Ultra (30MB/s UHS-I) (SDSDU-032G-U46)<br />
|Works with debian6-19-04-2012<br />
Works with 2014-01-07-wheezy-raspbian<br /><br />
Works with wheezy-raspbian 22 May 2014<br />
man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0<br />
|Pnppl 11 Jun 2012<br />
Sheegoth on 12 Feb 2014<br />
GrimFaker 22 May 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Elevate (30 MB/s) SDSDU-032G-T11<br />
|Works with 2012-12-16-wheezy-raspbian<br />
|bderry71 08 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Extreme(SDSDQXN-064G-G46A)<br />
|UHS-I: works with 2015-02-16-wheezy-raspbian<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Extreme (SDSDX-064G-X46)<br />
|45 MB/s UHS-I: works with 2012-07-15-wheezy-raspbian<br />
|Cracki 10 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra (SDSDQUAN-064G-G4A)<br />
|2015-02-16-wheezy-raspbian works well.<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra (SDSDU-064G-U46)<br />
|2014-03-15-wheezy-raspbian crashed every week with reading errors. Card switched to readonly after one month. The same happened with a replacement card.<br />
|hypnotoad 30 mar 14<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra SDXC UHS-I FFP (3A114807)<br />
|<br />
|Zagblorg 26 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDXC<br />
|128<br />
|10<br />
|Extreme (45MB/s UHS-I)<br />
|Don't work (Tested on Two)<br />
|OTHMAN 2014 02 10<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|miniSDHC<br />
|2<br />
|<br />
|Ultra II miniSD. BE07107FJE<br />
|Doesn't boot<br />
|Pe7er 18 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|2<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Rew 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Sleepy 1 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|6<br />
|Mobile Ultra<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt) - Jens Pedersen / (tried 15-06-2012 with kernel 19-04-2012) error -84 transferring data, kernel panic: no init found - Wieltje<br />
|Jens Pedersen 8 May 2012, Wieltje 15 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|2<br />
|<br />
|<br />
|Fjen 12 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|4<br />
|SDSDQM-008G-B35<br />
|man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|jonasbits 12 Sept 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|6<br />
|Mobile Ultra (SDSDQY-008G-U46A)<br />
|working with the latest firmware, won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Ultra (SDSDQU-008G-U46) (30MB/s UHS-I)<br />
|tested and working on Raspbian wheezy (and RaspBMC)<br />
|Pepindur 11 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Mobile Ultra (48MB/s UHS-I) (SDSDQUA-008G-U46A)<br />
|working with the latest firmware<br />
|pravin_tavagad 24 Nov 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|SDSDQUA-008G-U46<br />
|doesnt work with raspbian,arch,noob-lite man:0x000015 oem:0x0100 name:VYL00M hwrev:0x0 fwrev:0x0<br />
|Freemind 12 Sep 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|4<br />
|<br />
|(man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Mobile Ultra (30MB/s UHS-I) (SDSDQUA-016G-U46A)<br />
|working with the latest firmware; Works with OpenELEC 5.0.1 on Raspberry Pi 2 Model B.<br />
|Mengineer 25 Aug 2012, Shadyeglenn 12 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Ultra (SDSDQUAN-008G-G4A)<br />
|man:0x000003 oem:0x5344 name:SL08G hwrev:0x8 fwrev:0x0 Model B+ 2014-12-24-wheezy-raspbian<br />
|c 22 Jan 2015, Jon 3 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sandisk<br />
|microSDHC<br />
|16<br />
|?<br />
|Sandisk Extreme <br />
|man:0x000003 oem:0x5344 name:SE16G hwrev:0x8 fwrev:0x0. write 18.2 MB/s, read 18.8 MB/s Works with 2014-09-09-wheezy-raspbian on Model B+ <br />
|03 Dec 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Extreme Pro (95MB/s UHS-I) (SDSDQXP-016G-AFFP)<br />
|Installs and boots but random umounts occur and requires reboots, no work around found.<br />
|sdn3rd 15 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|4<br />
|<br />
|<br />
|Sherman 19 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQU-032G-U46A<br />
|archlinux-hf-2013-02-11<br />
|pAIgn10 6 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQUAN-032G-C4A Ultra SDHC UHS-I<br />
|RPi ModelB, raspbian wheezy 3.18.5 2015-01-30<br />
|Developer 2015-02-12<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQXN-032G-FFPA<br />
|RPi Model B+, raspbian-wheezy-2014-12-24<br />
man:0x000003 oem:0x5344 hwrev:0x8 fwrev:0x0<br />
|rico 31 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDXC<br />
|64<br />
|6<br />
|SDSDQY-064G-A11A<br />
|boots up much more consistently with latest firmware<br />
|LastSilmaril 23 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDXC<br />
|128<br />
|10<br />
|Write: 10.6 MB/s, Read: 18.6 MB/s, man:0x000003 oem:0x5344 name:SL128 hwrev:0x8 fwrev:0x0<br />
|Works with Raspbian on Model B+<br />
|Mstu 23 Nov 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SCT<br />
|SDXC<br />
|64<br />
|10<br />
|STC SM649A-130125<br />
|2013-02-09-wheezy-raspbian.img, booted cleanly, installed LibreOffice OK<br />
|Lanulos 29 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|8<br />
|10<br />
|SP008GBSDH010V10<br />
|Works fine 2012-12-16-wheezy-raspbian.img - Tested 14/01/2013<br />
|Thenix 14 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Silicon Power<br />
|SDHC<br />
|8<br />
|10<br />
|SP008GBSDH010V10<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt ) - Tested 20/11/2012, 2012-10-28-wheezy-raspbian.img with Nov 20 kernel<br />
|Xthexder 21 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|16<br />
|6<br />
|SP016GBSDH006V10<br />
|<br />
|Valery 05 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|16<br />
|10<br />
|SP016GBSDH010V10<br />
|<br />
|Xthexder 21 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Silicon Power<br />
|SDHC<br />
|32<br />
|6<br />
|LS2N732GQON03ASP<br />
|boots debian6-19-04-2012.img, but frequent slow response / system hangs<br />
|Michthom 21 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|4<br />
|6<br />
|SP004GBSTH006V10-SP<br />
|<br />
|Csgabe 19 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|8<br />
|10<br />
|S608G1202<br />
|<br />
|Blutme 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|MicroSDHC<br />
|8<br />
|10<br />
|SP008GBSTH010V10SP<br />
| Read:15.7 MB/s Write:5.5 MB/s, (man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2)<br />
|Thu 01 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|16<br />
|10<br />
|SP016GBSDH010V10<br />
|<br />
|Jamesnine 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|4<br />
|4<br />
|SF-4B4, SF-4N4<br />
|(Write 6MB/s, Read 20MB/s)<br />
|Krischaplin 7 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|4<br />
|10<br />
|UHS-1 40MB/s SF-4UY man:0x000027 oem:0x5048 name:SD04G hwrev:0x3 fwrev:0x0 <br />
|Perfect with Raspbian. With openELEC I get warnings in the logs (mmc0: DMA IRQ 6 ignored - results were reset - mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it) (Write 10,3MB/s, Read 18,8MB/s)<br />
|Knopfler19 20 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|(Write 11.8MB/s, Read 17.4MB/s)<br />
|Slabua 9 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-1 SF8UX<br />
|Write 17.2 MB/s, Read 20.8 MB/s, Raspbian works while image copied using windows<br />
|Regi24 29 Dec 2012, Hariram April 12, 2013, Hareesh G S June 6, 2013 (Openelec Image)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-1 90MB/s SF-8UX man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x0 <br />
|Perfect with Raspbian. With openELEC I get warnings in the logs (mmc0: DMA IRQ 6 ignored - results were reset - mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it) (Write 16,9 MB/s, Read 21,1 MB/s)<br />
|Knopfler19 20 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-I SF-8UY/TQ1 man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2 <br />
|Works fine with Raspbian. (Write 13.37 MB/s, Read 20.93 MB/s)<br />
|c5jirzex52xx, 18 Nov 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|16<br />
|10<br />
|UHS-1<br />
|Works well with Raspian.<br />
|Bafeigum 23 Aug 2013; DBlessing 12 Mar 2014 (Confirmed)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32NX/TQ<br />
|Max read speed of ~94 MB/s, min write speed of ~10 MB/s) - Works with archlinuxarm-29-04-2012 dd image with latest firmware update (as of 10-06-2012)<br />
|Chbg 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32UY/TQ1, SF-32UY/TQMN (40 MB/s)<br />
|Works with archlinux-hf-2013-02-11 (also after full update) - as of 04-08-2013)<br />
|Tigran 09 April 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32UY/TQ1, UHS-I (40 MB/s)<br />
|Works with Raspbmc, OpenELEC (Frodo and Gotham test builds), and NOOBS.<br />
Tested throughput:<br />
Seq Read: 87.2MB/sec<br />
Seq Write: 20.4MB/sec<br />
Random Read: 78.3MB/sec<br />
Random Write: 19.9MB/sec<br />
|JoeSchmuck 13 July 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|Micro SDHC<br />
|32<br />
|10<br />
|SR32UYA/TQMN<br />
|<br />
|Spec 8 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|Micro SDXC<br />
|64<br />
|10<br />
|SR-64UY<br />
|2015-02-16-raspbian<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Strontium<br />
|SDHC<br />
|8<br />
|10<br />
|SD-T08G 1045 US6923 G (White Shell - SKU 8 886450 703492)<br />
|<br />
|Ssb 25 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Super Talent<br />
|SDHC<br />
|32<br />
|10<br />
|SDHC32-C10 SKU: 116-557-001<br />
|works with Raspbmc RC4 and 2012-07-15-wheezy-raspbian<br />
|Drroller 14 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with TakeMS adapter<br />
|Delboy0 31 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|SDHC<br />
|16<br />
|6<br />
|<br />
|Tested on raspbmc - works with no problems<br />
|swidzi 25 October 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|SDXC<br />
|64<br />
|10<br />
|<br />
|overclock turbo model B works<br />
|select 02 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|4<br />
|4<br />
|1008WW5261B<br />
|<br />
|Pluggster 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|2 x 4<br />
|4<br />
|80-56-10275-004G<br />
|Debian works, mmc0 errors when booting Fedora<br />
|Melikescheese 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1113<br />
|Works with Debian Wheezy (2012-06-18 beta)<br />
|Dcuk 26 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|TDK<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1041, S404G1046<br />
|end May 2012, new kernel.img and start.elf, won't run init. 4 Jun 2012, debian6-19-04-2012.img, replacement kernel.img and start.elf from github. Got Error -84 and Kernel panic - not syncing: No init found<br />
|Ceptimus 2 Jun 2012, Norbini 4 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|microSDHC<br />
|4<br />
|4<br />
|with Adapter (80-56-10301-004G)<br />
|<br />
|Norbini 4 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|Works with Raspbian 2012-07-15<br />
|Backeby 20 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Team<br />
|MicroSDHC<br />
|32<br />
|10<br />
|<br />
|Raspberry Pi 2 Model B <br />
|Riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TOPRAM<br />
|SDHC<br />
|8<br />
|6<br />
|TRSD8GC6<br />
|Works with OpenELEC (Frodo and Gotham test builds), did not test on anything else yet.<br />
Tested throughput:<br />
Seq Read: 43.9MB/sec<br />
<br />
Seq Write: 18.8MB/sec<br />
Random Read: 41.8MB/sec<br />
Random Write: 17.6MB/sec<br />
|JoeSchmuck 13 July 2013<br />
|-<br />
<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|4<br />
|4<br />
|SD-K04G(1201 W12338 N) (labelled as Fujifilm SHDC 4GB class 4)<br />
|Tested with Raspbian 2013-11-18. Speed is 5MB/s write (1GB file) <br />
|captaindangeax 18 nov 2013<br />
|-<br />
<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|8<br />
|4<br />
|SD-K08G(1223 W17218 P)<br />
|Tested with Raspbian 2012-12-16. Speed is 4MB/s write<br />
|rendyair 16 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|8<br />
|10<br />
|PFS008U-1DCK (6/13)<br />
|Tested with Raspbian.<br />
|Rellermeyer 25 Sep 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|16<br />
|10<br />
|SD-T16G(1046 US7022 C)<br />
|<br />
|Yang 5 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|32<br />
|10<br />
|SD-K032GR7AR30 (30MB/s)<br />
|Works with NOOBS.<br />
|OTHMAN 2014.02.14<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC04G<br />
|with adapter - NOOBS v.1.3.4 cannot install the OS on the card but applying a OS image directly is working perfectly<br />
|elapdre 16 April 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|8<br />
|?<br />
|SD-C08GJ(BL3A)<br />
|with adapter<br />
|Jannis 15 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|8<br />
|4<br />
|PFM008U-1DAK<br />
|works with openelec<br />
|akschu 26 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|16<br />
|10<br />
|SD-C016UHS1BL5A<br />
|with adapter<br />
|wombalton 25 March 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|32<br />
|10<br />
|SD-C032UHS1BL5A<br />
|man:0x000002 oem:0x544d name:SA32G hwrev:0x1 fwrev:0x2 - Tested on A+ and B+<br />
|bpmurray 14 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|64<br />
|10<br />
|SD-C064GR7AR30<br />
|Tested 2015-02-16-raspbian on Pi2<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SD<br />
|2<br />
|?<br />
|6451AG 2G O2DS1<br />
|<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|4<br />
|TS4GSDHC4 - BH1130821915G<br />
| we've found these to work without any errors and offer reasonable performance<br />
|RasMyra 12 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|6<br />
|TS4GSDHC6<br />
|no problems (does not work with Raspbmc as of 1 Jun 2012 - 321liftoff)<br />
|LakesGeek 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|10<br />
|TS4GSDHC10<br />
|Works fine running Raspbian and OpenELEC. Tested various cards from different batches.<br />
|Kiwisol 27 Oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|10<br />
|TS4GSDHC10E, TS4GSDHC10<br />
|Corrupted when card image back up made<br />
mmc0: resetting ongoing cmd 25dma before 4096/4096 [1]/[1] complete<br />
mmc0: Timeout waiting for hardware interrupt - cmd12<br />
mmcblk0: error -110 sending stop comment, original cmd response 0x900, card status 0xe00<br />
|Mfg 3 Jun 2012, Thenix 14 Jan 2013, Fazz 04 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10E<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br />
| jmarin 22 April 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|4<br />
|TS8GSDHC4<br />
|(man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0) - works with both Debian "squeezy" and Raspbian "wheezy" distributions (Hedj)<br />
|Attila.afra 25 Apr 2012, Hedj 24 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|6<br />
|TS8GSDHC6-P2 - MMBFG08GWACA-M6<br />
|~5.8 MB/s read/write following the Performance below<br />
|Md84419 5 Nov 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10<br />
|<br />
|Selsinork 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDU1 UHC-I X300<br />
|Arch read/write 20,9/13,1 MB/s<br />
|30 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10U1 UHC-I X600<br />
|Arch read/write 21,1/15 MB/s<br />
|30 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|4<br />
|TS16GSDHC4<br />
|Tested with Raspbian 2014-12-30<br />
|Fmondada 2 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|6<br />
|TS16GSDHC6<br />
|<br />
|Bullace 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 / TS16GSDHC10E<br />
|<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 / TS16GSDHC10E<br />
| Read:18.4 MB/s Write:12.1 MB/s (man:0x000074 oem:0x4a45 name:SDC hwrev:0x0 fwrev:0x2)<br />
|Sam2 01 Feb 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDU1<br />
| Read:18.4 MB/s Write:12.1 MB/s, (man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2)<br />
|Sam2 01 Feb 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 9173BA-16G-09DS2<br />
| works<br />
|Epa 20130304. package had "83-3432 V5.1" behind it.<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10U1<br />
|Doesn't Boot, show that "kernel panic - not syncing attempted to kill init"<br />
|Khfung02 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10 UHS-1<br />
|TS16GSDHC10U1<br />
|Works with Occidentals 0.2 from Adafruit, read and write about 15 MB/s, didn't test other versions.<br />
|aevh 18 Feb 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|32<br />
|6<br />
|TS32GSDHC6-P2<br />
|Was not recognized by 1/2 rsp B, switched to read only after 1 year, man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|hypnotoad 30 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|32<br />
|10<br />
|TS32GSDHC10, TS32GSDHC10E<br />
|<br />
|Vakya 29 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDXC<br />
|64<br />
|10<br />
|TS64GSDXC10<br />
| OK<br />
NOK - After one week it switched to readonly. The same happened with a replacement card.<br />
|Country 26 Jun 2012<br />
Trochim 4 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDXC<br />
|128<br />
|10 UHS-I<br />
|TS128GSDXC10U1<br />
|Works with openSUSE<br />
|petrmatula 8 Mar 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|2<br />
|?<br />
|MMAGR02GUECA-MB<br />
|reads fine initially after image was written on a PC, gives mmc0 timeout errors reading back data after writing a large amount (in this case with 'pacman -Syu'). Still seems to work, but is *very* slow after this happens, even across reboots<br />
|Malvineous 16 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|8<br />
|10<br />
|TS8GUSDHC10<br />
|<br />
| Za Bullet 18 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|8<br />
|10<br />
|TS8GUSDU1<br />
|Works with 2014-06-20-wheezy-raspbian<br />
Works with RaspBMC in RPi Model B+<br />
|Elf98 15 Aug 2014<br />
javierrgz 3 Sep 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1<br />
|Raspberry Pi B+ Model (tested on OpenELEC,xbian, raspbmc, kali linux)<br />
|@xhark 05 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1<br />
|Works with 2014-06-20-wheezy-raspbian<br />
|Elf98 15 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1E<br />
|man:0x000003 oem:0x5344 name:SL16G hwrev:0x8 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/Transcend-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|10<br />
|TS32GUSDU1<br />
|Works with 2013-02-09-wheezy-raspbian<br />
|Neurolit 15 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|?<br />
|TS32GUSDHC4<br />
|Doesn't boot<br />
|Piponazo 7 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|10<br />
|TS32GUSDHC10<br />
|(man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDXC<br />
|64<br />
|10<br />
|TS64GUSDU1E<br />
|Raspberry Pi B+ Model (tested with ARM Arch Linux)<br />
|fluxon 28 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Traveller<br />
|SDHC<br />
|4<br />
|?<br />
|High Speed<br />
|Works with raspbian<br />
|Sega dude 28 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|UNIREX<br />
|microSDHC<br />
|32<br />
|UHS-I C10<br />
|UMW-325M<br />
|mmcblk0: read problems during boot [including "mmc0: controller never released inhibit bit(s)" ], corruption ensues. this with Raspbian 2015-02-16 on Raspberry Pi2 Model B<br />
|mmhere 18 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|V-Gen<br />
|microSDHC<br />
|8<br />
|?<br />
|<br />
|No problems.(man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0). Tested with Raspbian Wheezy & Raspbmc<br />
|Rendyair 11 Sep 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Veho<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|<br />
|Spaaa 5 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Veho<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra fast<br />
|(man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0) 7.8Mb/s. Slow but tested with Arch Linux<br />
|Johnlane 28 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|6<br />
|Go<br />
|tested with NOOBS 1.3.2 and Raspbian Wheezy 2013-09-25; mmc0: timeout waiting for hardware interrupt<br />
|marcel.kolaja 12 Dec, 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|43961<br />
|<br />
|Petacz 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|Premium<br />
|Tested with 2013-02-09 release of Raspbian Wheezy and Rasplex 0.1.37 - blue plastic version<br />
|Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|Premium PSF8GSDHC10-PC<br />
|Tested with September release of Raspbian and Debian Wheezy - both fail to boot with mmc errors, confirmed fail with this black plastic version (may 2013)<br />
|XQx 31 Oct 2012 , confirmed Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|43961<br />
|Raspbian - installs it but doesn't boot, repeatedly prints: 'timeout waiting for hardware interrupt'<br />
|Gkontadakis 31 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|4<br />
|44020<br />
|<br />
|Adelahunty 22 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|6<br />
|47178<br />
|Raspbian Pisces RC3 - boots, but after login: mmc timeout waiting for interrupt<br />
|Razzda 15 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|10<br />
|43962<br />
|<br />
|Klass 24 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|10<br />
|13762<br />
|mmc timeout<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|32<br />
|6<br />
|44032<br />
|<br />
|Jarip 14 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|microSDHC<br />
|8<br />
|10<br />
|44012<br />
|ArchLinux - boots, but after system update develops segmentation faults<br />
|John.glasson 29 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|microSDHC<br />
|16<br />
|4<br />
|<br />
|Tested with 2013-02-09-wheezy-raspbian - works without any problem<br />
|J3rGuS 19 March 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|SD<br />
|1<br />
|?<br />
|<br />
|Works with raspbmc, have not tested others<br />
|Sp00l 21 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|SD<br />
|2<br />
|?<br />
|<br />
|Works with raspbian, have not tested others<br />
|Sega dude 27 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|…testing on B+…<br />
|[[User:DisneyWizard|DisneyWizard]] ([[User talk:DisneyWizard|talk]]) 18:00, 10 January 2015 (UTC)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|microSDXC<br />
|64<br />
|10<br />
|SR-64UYA<br />
|Works with Raspy 2 and Snappy Ubuntu<br />
|[[User:Ileo|Ileo]] ([[User talk:Ileo|talk]]) 20:10, 15 March 2015 (UTC)<br />
|}<br />
<br />
== Performance ==<br />
<br />
The following results have been reported by Users.<br />
<br />
=== Terminal Commands ===<br />
<br />
To obtain the results in the table, type the following lines at a command prompt. If you are running the GUI windows, open the Terminal application.<br />
<br />
The '''dd''' command is the Linux block copy command. It reads from the '''if=''' file, in the first case a block of zeros, and writes to the '''of=''' file, in the first case the file named test.tmp in your HOME directory (the ~/ means your HOME directory). The '''bs=''' gives the size of the data, and the '''count=''' gives the number of times this is repeated. '''sync''' ensures that the filesystem cache is flushed to have more realistic data. Please run it multiple times, one sample is not scientific enough.<br />
<br />
'''Write speed'''<br />
<br />
sync; dd if=/dev/zero of=~/test.tmp bs=500K count=1024<br />
<br />
'''Read speed'''<br />
<br />
sync; echo 3 | sudo tee /proc/sys/vm/drop_caches<br />
sync; time dd if=~/test.tmp of=/dev/null bs=500K count=1024<br />
<br />
'''Delete the temporary file'''<br />
<br />
rm ~/test.tmp<br />
<br />
'''Kernel version'''<br />
<br />
uname -a<br />
<br />
=== External Benchmarks ===<br />
<br />
* http://www2.sakoman.com/OMAP/microsd-card-perfomance-test-results.html<br />
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076<br />
<br />
=== Is this reliable? ===<br />
<br />
SD cards are given a rating (Class) by the manufacturers; the higher the rating the quicker the card. SD cards are usually used in a camera. The camera usually writes a block of data (a picture), then writes another. The SD card is tuned for this type of use. When used in the Raspberry Pi the data is written and read a lot more frequently, and from differing locations on the card. This difference in use means the<br />
manufacturers rating may not be as applicable for the Raspberry Pi.<br />
<br />
=== SD card performance ===<br />
<br />
The table can be sorted using the triangles in the top row. Please add entries in the correct location, so that the initial sort is by Manufacturer, Size, Type and Class<br />
<br />
{| border="1" class="sortable"<br />
! SD Card !! Read (MB/s) !! Write (MB/s) !! class="unsortable" | Distro !! class="unsortable" | Kernel !! class="unsortable" | Notes<br />
|-<br />
|ADATA 8GB SDHC Class 10 (ASDH8GCL10-R) || 19.6 || 18.8 || 2012-08-04 Debian Wheezy "Raspbian" || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|ADATA 8GB SDHC Class 10 (ASDH8GCL10-R) || 18.2 || 12.4 || 2012-12-16 Debian Wheezy "Raspbian" || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux || <br />
|-<br />
|ADATA 16GB SDHC Class 10 || 19.5 || 16.9 || 2012-06-13 Arch Linux ARM || Linux alarmpi 3.2.27+ #60 PREEMPT Thu Aug 23 15:33:51 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|ADATA 16GB SDHC Class 10 || 17.8 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.10.24+ #610 PREEMPT Thu Dec 12 13:12:09 GMT 2013 armv6l GNU/Linux || man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0<br />
|-<br />
| ADATA 16GB SDHC Class 10 (ASDH16GUICL10-R) || 18.5 || 9.9 || archlinux-hf-2013-11-14 || Linux alarmpi 3.10.25-1-ARCH #1 PREEMPT Mon Dec 23 16:07:25 MST 2013 armv6l GNU/Linux ||<br />
|-<br />
| ADATA 16GB SDHC Class 10 (ASDH16GUICL10-R) || 18.4 || 16.06 || 2014-01-07-wheezy-raspbian || Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux || Fresh install<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-R) || 18.6 || 12.3 || 2014-07-08-wheezy-raspbian || Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux || Fresh NOOBS install + apt-get upgrade<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-RA1) || 13.8 || 7.1 || 2014-12-24-wheezy-raspbian || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Fresh Raspbian install<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-RA1) || 18.8 || 9.3 || 2014-12-24-wheezy-raspbian || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Fresh Raspbian install + apt-get upgrade + reboot<br />
|-<br />
|ADATA 32GB SDHC Class 10 (ASDH32GCL10-R) || 20.1 || 6.4 || 2012-06-18-wheezy-beta || Linux raspberrypi 3.1.9+ #152 PREEMPT Fri Jul 6 18:47:16 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|AmazonBasics SDHC Class 10 8GB || 19.3 || 8.6 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|AmazonBasics SDHC Class 10 8GB || 17 || 9.4 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || Same board and card as above, slightly newer kernel.<br />
|-<br />
|Emtec SDHC 8GB class 10 (EKMSD8G150XHC) || 20.3 || 14.6 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux || Turbo mode = High (950/250/450MHz)<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 4.7 || 4.5 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #52 ||<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 11.3 || 5.4 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #101 || init_emmc_clock=200000000 in config.txt<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 18.2 || 6.3 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ custom || kernel and firmware as of 17.06.2012, no extra option in config.txt<br />
|-<br />
|Extrememory SDHC 16GB class 10 <br/>(man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0) || 16.9 || 10.7 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||<br />
|-<br />
|Extrememory SDHC 32GB class 10 <br/>(man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0) || 18.7 || 16.5 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||<br />
|-<br />
|Farnell Branded (Samsung) SDHC 4GB Class 4 (MMBTF04GWBCA-ME) || 20.1 || 6.9 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 || Pi overclocked to 900 Mhz arm_freq and 500 Mhz sdram_freq<br />
|-<br />
|Fugi SDHC 32GB class 10 (P10NM00580A) || 12.7 || 19.8 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 || man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0<br />
|-<br />
|GoodRAM SDHC 16GB Pro class 10 (SDC16GHC10PGRR9) || 19.4 || 18.0 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #272 ||<br />
|-<br />
|Integral SDHC 16GB class 10 ||17.7 || 19.6 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 ||<br />
|-<br />
|Kingmax 8GB microSDHC Class 4 (KM08GMCSDHC41A) || 13.6 || 3.7 || Debian Wheezy Raspbian || Linux 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 ||<br />
|-<br />
|Kingston SDHC 4GB class 4 ||4.5 ||4.1 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #52 Tue May 8 23:49:32 BST 2012 ||<br />
|-<br />
|Kingston SDHC 4GB class 4 ||4.2 ||2.5 ||archlinuxarm-19-04-2012 ||Linux alarmpi 3.1.9-13+ #6 Thu May 10 00:48:37 UTC 2012 ||Identical card to one above. One to look into, as I was expecting Arch to be faster...<br />
|-<br />
|Kingston uSDHC 4GB class 4 ||4.0 ||3.8 ||Debian Squeeze ||Linux 3.1.9+ #90 ||<br />
|-<br />
|Kingston uSDHC 8GB class 4 (SDC4/8GB) ||4.7 ||3.7 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_uSD_8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)] This is my only card that can be counted on to boot up on each plug-in.<br />
|-<br />
|Kingston microSDHC 4GB Class 10 (SDC10/4GB) || 13.4 || 10.6 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || c 22 Jan 2015<br />
|-<br />
|Kingston microSDHC 8GB Class 10 || 14.5 || 8.1 || Debian Wheezy "Raspbian" || Linux Rpi 3.12.24+ #694 PREEMPT Tue Jul 15 17:34:35 BST 2014 armv6l GNU/Linux || Felon 07 July 2014<br />
|-<br />
|Kingston microSDHC 16GB class 4 ||17.1 ||5.1 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Kingston microSDHC 16GB class 10 ||20.1 ||13.4 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Kingston microSDHC 32GB class 10 ||17.9 ||10.9 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Kingston SDHC 8GB Class 4 (SD4/8GB) || 16.2 || 5.2 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Kingston SDHC 8GB class 4 (SD4/8GB) ||4.6 ||3.0 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_SD4-8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)]<br />
|-<br />
|Kingston SDHC 8GB class 4 (SD4/8GB) ||13.2 ||3.4 || Hexxeh Raspbian r3 ||Linux raspbian 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || man:0x000002 oem:0x544d name:SA08G hwrev:0x1 fwrev:0x0<br />
|-<br />
|Kingston SDHC 8GB Class 10 (SD10V/8GB) || 16.2 || 9.9 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Kingston SDHC 32GB class 10 ||10.8 ||8.1 ||Fedora 17 ARM snapshot 07 May 2012 ||Linux fedora-arm 3.1.9 #1 ||mmc0: note - long write sync 1453000ns - 14608 its. - kernel/module problems?<br />
|-<br />
|Kingston SDHC 32GB class 10 ||4.7 ||4.1 ||Fedora 17 ARM nightly snapshot ||Linux fedora-arm 3.1.9+ #101 PREEMPT Mon Jun 4 17:19:44 BST 2012 ||custom kernel from raspberrypi github - no more mmc0 sync problems<br />
|-<br />
|Kingston SDHC 32GB class 10 ||4.6 ||3.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 ||<br />
|-<br />
|Kingston SDXC 64GB class 10 (SDCX10/64GB) ||13.9 ||10.1 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Lexar Platinum II SDHC 8GB Class 10 UHS-I || 18.5 || 9.1 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Noname uSDHC 16GB class 4 ||18.5 ||2.6 ||Raspmc ||Linux raspbmc 3.2.27 #1 PREEMPT Mon Nov 5 20:50:02 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|Panasonic SDHC 8GB class 6 ||4.8 ||4.4 || || ||<br />
|-<br />
|Panasonic SDHC 8GB class 4 ||11.1 || 9.7 || Debian Wheezy "Rasbpian" || Linux rpi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Platinum SDHC 8GB class 10||14.9|| 13.9 || Arch Linux ARM "hf-2013-02-11"|| Linux alarmpi 3.6.11-9-ARCH+ #1 PREEMPT Sat Mar 30 02:38:20 UTC 2013 armv6l GNU/Linux ||<br />
|-<br />
|Patriot microSDHC 16GB Class 10 (PSF16GMSHC10) ||9.5 ||5.2 ||Fedora 14 ||Linux raspi 3.1.9+ #101 ||init_emmc_clock=200000000 in config.txt<br />
|-<br />
|Patriot SDHC 16GB Class 10 (PSF16GSDHC10) ||19.3 ||9.3 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Patriot SDHC 32GB Class 10 UHS-1 (PEF32GSDHC10U1) ||20.4 ||12.1 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|PNY microSDHC 16GB Class 10 (P-SDU16G10-GE) ||17.31 ||11.0 ||Raspbian OS from NOOBS v1.4.0 ||Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux ||Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/PNY-Class10.html Details]<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MP16DA/AM) ||17.33 ||13.1 ||Raspbian OS from NOOBS v1.4.0 ||Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux ||Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/Samsung-Class10.html Details]<br />
|-<br />
<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||10.7 ||8.8 ||Fedora 17 ARM snapshot 07 May 2012 - GUI release ||Linux fedora-arm 3.1.9 #1 ||Had "long write sync" errors, slow boot times and then system instability using USB port on Macbook, switched to iPhone charger (5V 1A) and warning disappeared<br />
|-<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||19.6 ||18.7 || Debian Wheezy "Raspbian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armvl GNU/Linux ||(Same user / card as above, definitely notable that Raspbian is superior)<br />
|-<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGC) ||18.5 ||12.2 || Debian XFCE pipplware ||Linux raspberrypi 3.10.33+ #356 PREEMPT Tue Mar 18 17:35:55 GMT 2014 armv6l GNU/Linux || djayor 9 May 2014<br />
|-<br />
|Samsung SDHC 4GB Class 4 (MB-SS4GA/EU) ||17.7 ||8.1 || Debian Wheezy "Raspbian" ||Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l<br />
||Markus 2014/02/24<br />
|-<br />
|Samsung microSDHC 4GB Class 6 ( MB-MS04D) || 18.9 || 8.1 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || c 21 Jan 2015<br />
|-<br />
|Samsung microSDHC 8GB Class 6 ( MB-MS08DA/EU) || 17.8 || 6.3 || Debian Wheezy "Raspbian" || Linux Rpi 3.12.24+ #694 PREEMPT Tue Jul 15 17:34:35 BST 2014 armv6l GNU/Linux || Felon 07 July 2014<br />
|-<br />
|Samsung SDHC 32GB Class 6 || 21.6 || 17.4 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux || -<br />
|-<br />
|Samsung EVO microSDHC 16GB Class 10 (MB-MP16D) || 17.2 || 8.9 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || B+ model<br>c 22 Jan 2015<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MPAGA/US) || 19.8 || 15.8 || Debian Wheezy "Raspbian" || Linux pisces 3.1.9+ #155 PREEMPT Mon Jul 9 12:49:19 BST 2012 armv6l GNU/Linux || -<br />
|-<br />
|Samsung microSDHC 16GB Class 4 (MB-MS4GA/US) || 19.2 || 5.5 || Debian Wheezy "Raspbian" || ? || -<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MPAGAEU) || 21.7 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux || man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 <br> 512Mb version of Raspberry Pi<br />
|-<br />
|Samsung PRO microSDHC 16GB Class 10 (MB-MGAGB) || 17.5 || 11.3 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Model B+<br />
|-<br />
|SanDisk Extreme III 2GB Class 10 (BE07054050838) || 23.3 || 21.5 || Raspbmc || Linux raspbmc 3.2.27 #1 PREEMPT Mon Nov 5 20:50:02 UTC arm61 GNU/Linux || 512Mb version of Raspberry Pi<br />
|-<br />
|SanDisk microSD 2GB ||4.7 ||4.2 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_2GB_uSD_CDM_Bench.zip CrystalDiskMark results (FAT32)] Card has no serial/is likely a fake.<br />
|-<br />
|SanDisk Ultra SDHC 4GB class 4 ||4.7 ||4.4 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SD04G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra II SDHC 4GB class 4 (15 MB/s)||20.9 ||14.6 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ ||<br />
|-<br />
|SanDisk SDHC 8GB class 4 ||11.1 ||5.6 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. <br />man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 4GB class 4 ||11.15 ||5.15 ||Raspbian Wheezy || Linux raspberrypi 3.6.11+ #456 PREEMPT || man:0x000003 oem:0x5344 name:SD04G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 8GB class 4 ||4.7 ||3.2 ||Debian Squeeze || ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 6 "30MB/s*" ||19.5 || 7.6 ||archlinuxarm || 3.1.9-22-ARCH+ #1 PREEMPT Sun Jun 17 13:54:30 UTC 2012 || "mmc0: error -84 whilst initialising SD card" at bootup, but works fine<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" ||19.3 || 3.2 ||Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s* (SDSDU-008G-UQ46)" || 18.6 || 14.5 ||Raspbian GNU/Linux 7 (wheezy) || Linux raspberrypi 3.10.21+ #604 PREEMPT Mon Dec 2 20:17:09 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" || 13.6 || 14.5 || raspbmc rc3 || Linux raspbmc 3.1.9-test-12-06 #1 PREEMPT Mon Jun 18 20:07:45 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC II 16GB class 2 "15MB/s*" ||16.7 || 16.2 || Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 || man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 UHS-1 "30Mb/s" (SDSDU-016G-U46) ||20.9 ||18.1 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. <br />man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 "30Mb/s" (SDSDU-016G-U46) ||20.9 ||10.9 ||Raspbian Wheezy || Linux raspberrypi 3.6.11+ #371 PREEMPT || <br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 (SDSDQUAN-016G-G4A) ||18.8 ||13.4 || 2015-02-16-wheezy-raspbian || Linux rpi 3.18.9-v7+ #767 SMP PREEMPT || read test is done with dropped cache, write test is done with sync; man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0 <br />
|-<br />
|SanDisk microSDHC 16GB class 4 (SDSDQ-016G) || 18.3 || 7.5 || 2015-02-16-wheezy-raspbian || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk microSDHC 16GB class 10 (SDSDQUIP-016G-A46) ||18.01 ||17.9 || Raspbian OS from NOOBS v1.4.0 || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/SanDisk-Class10.html Details] <br />
|-<br />
|SanDisk Ultra SDHC 32GB class 10 "30Mb/s" (SDSDU-032G-U46) ||18.3 ||8.8 ||Raspbian Wheezy || Linux raspberrypi 3.12.19+ #684 PREEMPT || man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0 <br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 "30MB/s" (SDSDU-016G-U46S) ||21.6 ||15.2 || 2013-02-09-wheezy-raspbian || Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme SDHC I 4GB class 10 "30MB/s" || 19.7 || 21.0 || 2012-07-15-wheezy-raspbian || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux || Only boots with images with new firmware, didn't boot with previous images.<br />
|-<br />
|SanDisk Extreme SDHC I 8GB class 10 "30MB/s" || 17.7 || 19.7 || Archlinuxarm 2012-06-13 || Linux raspi 3.1.9-28-ARCH+ #1 PREEMPT Fri Jul 6 23:07:26 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme SDHC I 8GB class 10 "30MB/s" || 17.2 || 10.6 || RISC OS 5.21 (04-Jun-2014) || RC12a ||<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 32GB class 10 "30MB/s" || 21.4 / 18.4 || 19.5 / 22.2 || 2012-10-28-wheezy-raspbian || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk microSDHC UHS-I 32GB class 10 "30MB/s" || 21.1 || 10.9 || 2013-02-09 Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra microSDHC 32GB class 10 "48MB/s" (SDSDQUN-032G-FFP-A)|| 18.5 || 10.8 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux || Raspberry Pi B+, 2014-12-20<br />
|-<br />
|SanDisk Ultra microSDHC 32GB class 10 "48MB/s" (SDSDQUAN-032G-C4A)|| 18.9 || 16.73 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux || Raspberry Pi B, 2015-02-12<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 16GB class 10 "45MB/s" (SDSDX-016G-X46) || 21.1 || 20.8 || 2012-09-18-wheezy-raspbian || Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Sandisk Extreme microSDHC UHS-I 16GB || 18.8 || 18.2 || 2014-09-09-wheezy-raspbian on Model B+ || Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SE16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 32GB class 10 "45MB/s" (SDSDX-032G-X46) || 20.96 || 17.9 || 2013-05-20-wheezy-raspabian || Linux raspberrypi 3.6.11+ #456 PREEMPT || man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme PLUS SDHC UHS-I 32GB class 10 "80MB/s" (SDSDXS-032G-A46) || 18.7 || 16.5 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SE32G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 32GB class 6 ||4.6 ||4.8 || || ||<br />
|-<br />
|SanDisk uSDXC 64GB class 6 ||4.9 ||3.8 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_64GB_uSDXC_CDM_Bench.zip CrystalDiskMark results (FAT32)]<br />
|-<br />
|SanDisk Ultra SDXC 64GB class 10 (SDSDQUAN-064G-G4A) ||17.9 ||14.5 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|SanDisk Extreme SDXC 64GB class 10 (SDSDQXN-064G-G46A) ||17.4 ||20.9 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Silicon Power 8GB class 10 (SP008GBSDH010V10) || 15.6 || 11.7 || Debian Wheezy "Raspbian" (2012-12-16) || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Sony 8GB class 10 (SF-8UY/TQ1) || 20.9 || 13.4 || Debian Wheezy "Raspbian" (2013-09-25) || Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux ||man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2<br />
|-<br />
|Sony 64GB class 10 (SR-64UY) || 15.8 || 17.5 || Debian Wheezy "Raspbian" (2015-02-16) || Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|TakeMS SDXC 64GB, Class 10 ||16.9 ||8.2 ||Debian Wheezy "Raspbian" (2013-06-02) ||Linux pisys 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux || Pi B overclocked arm_freq=1000 core_freq=500 sdram_freq=600 over_voltage=6<br />
|-<br />
|TDK microSDHC 4GB, Class 4 (80-56-10301-004G) ||11.2 ||4.7 ||Debian Wheezy "Raspbian" (2012-07-15) ||3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 || <br />
|-<br />
|Toshiba microSDHC 4GB Class 4 ||17.8 ||10.4 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Toshiba SD-T16G SDHC 16GB, Class 10 (1046 US7022 C) ||20.6 ||13.5 ||Debian Wheezy "Raspbian" ||3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Toshiba microSDXC 64GB (SD-C064GR7AR30) ||14.7 ||10.5 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Transcend microSDHC 16GB Class 10 (16GBBEU300A) || 17.7 || 9 || Debian Wheezey 7.6 "Raspbian" || Linux raspbian 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 UTC 2014 armv6l GNU/Linux || 2014-10-05 by @xhark <br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10E) || 22.2 || 17.1 || 2013-04-22 Raspbmc || Linux raspbmc 3.6.11 #2 PREEMPT Wed Mar 13 17:12:47 UTC 2013 armv6l GNU/Linux || Pi overclocked toarm_freq=840, core_freq=350, gpu_freq=253<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10E) ||15.9||17.5||Debian Wheezy "Raspbian"||Linux RaspberryPi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux||stock clock speed||<br />
|-<br />
|Transcend microSDHC 8GB Class 10 (TS8GUSDHC10) || 20.2 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux || <br />
|-<br />
|Transcend SDHC 8GB class 6 ||5.8 ||5.8 || || ||<br />
|-<br />
|Transcend SDHC 8GB Class 6 (TS8GSDHC6) ||4.6 ||4.0 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 Wed Apr 18 18:23:05 BST 2012 armv61 GNU/Linux ||Tested with dd. Card doesn't maintain the promised minimum class speed.<br />
|-<br />
|Transcend SDHC 8GB Class 4 (TS8GSDHC4) ||11.1 ||8.1 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Transcend microSDHC 8GB Kit, Class 4 (TS8GUSDHC4)||4.7 ||3.7 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10) ||4.6 ||4.6 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ armv61 GNU/Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10) ||19.5 ||18.5 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDU1) UHC-I X300 ||20.9 ||13.1 ||Linux alarmpi 3.6.11-14-ARCH+ #1 PREEMPT Sun Jul 21 17:39:58 CDT 2013 armv6l GNU/Linux ||Arch Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10U1) UHC-I X600 ||21.1 ||15 ||Linux alarmpi 3.6.11-14-ARCH+ #1 PREEMPT Sun Jul 21 17:39:58 CDT 2013 armv6l GNU/Linux ||Arch Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10U1) UHC-I X600 ||18.5 ||12.4 ||Debian Wheezy (Raspbian 2014-01-07) ||Linux raspi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux ||man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2<br />
|-<br />
|Transcend SDHC 4GB Class 6 ||9.8 ||8.8 ||Fedora Remix FC14 ||Linux raspi 3.1.9 #1 PREEMPT Sat Mar 3 21:58:00 UTC 2012 armv6l armv6l armv6l GNU/Linux ||Not sure why this setup is faster than others, test results repeatable.<br />
|-<br />
|Transcend SDHC 4GB Class 10 (TS4GSDHC10) || 17.6 || 12.1 ||Debian Wheezy "Rasbpian" (2012-10-28) || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Transcend SDHC 16GB Class 10 ||20.3 ||11.9 ||Debian Wheezy "Rasbpian" || Linux raspberry-pi 3.1.9-cutdown+ #173 ||<br />
|-<br />
|Transcend SDHC 16GB Class 10 ||17.4 ||12.0 ||Debian Wheezy (2012-08-08-wheezy-armel)|| Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux || man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|-<br />
|Transcend microSDHC 16GB Class 10 || 17.96 || 16.4 ||Raspbian OS from NOOBS v1.4.0 || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/Transcend-Class10.html Details]<br />
|-<br />
|Transcend SDHC 16GB Class 10 || 18.6 || 11.2 ||Raspbian Wheezy || Linux raspberrypi 3.12.20+ #687 PREEMPT Fri May 30 16:39:11 BST 2014 armv6l GNU/Linux || hwrev:0x0 fwrev:0x2 man:0x000074 oem:0x4a45 <br />
After 2 months of use as a home server<br />
|-<br />
|Transcend SDHC 16GB Class 10 UHS-I Premium 300x ||21.4 ||9.6 ||Debian Rasbpian Wheezy (2013-09-25)|| Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l || <br />
|-<br />
|Transcend SDHC 32GB Class 10 (TS32GSDHC10E) || 20.3 || 15.3 || Debian Wheezy "Rasbpian" || Linux raspberrypi 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 armv6l GNU/Linux || man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|-<br />
|Transcend MicroSDHC 32GB Class 10 UHS-I (Premium 300x)||18.5 ||10.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Transcend MicroSDXC 64GB Class 10 UHS-I (Premium 300x)||18.5 ||15.7 ||ARM Arch Linux||Linux alarmpi 3.12.28-2-ARCH #1 PREEMPT Mon Sep 22 02:02:11 MDT 2014 armv6l GNU/Linux ||<br />
|-<br />
|Sandisk Extreme Pro SDHC 8GB Class 10 UHS-I || 21.6 || 21.7 || Arch Linux || Linux alarmpi 3.6.11-11-ARCH+ #1 PREEMPT Tue May 14 16:12:58 UTC 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Sandisk Extreme Pro SDHC 16GB Class 10 UHS-I (SDSDXPA-016G-A75) ||21.6 ||21.7 || Debian Wheezy "Rasbpian" || Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme Pro SDHC 16GB Class 10||20.8||18.6||Debian Wheezy "Raspbian"||Linux raspberrypi 3.1.9+ #125 PREEMPT Sun Jun 17 16:09:36 BST 2012 armv6l GNU/Linux||<br />
|-<br />
|Sandisk Ultra SDHC I Class 6 ("30MB/s") ||4.7 ||4.8 ||Debian Wheezy "Raspbian" ||3.2.18+ #3 PREEMPT ||Feels faster than my Kingston 4GB Class 4 card.<br />
|-<br />
|Sony 8GB SDHC Class 4 || 17.4 || 11.8 || Debian Wheezy Raspbian || Linux 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 ||<br />
|-<br />
|WINTEC FileMate Professional SDHC 16GB Class 10 (3FMSD16GBC10-R) ||4.6 ||4.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #95 PREEMPT Thu May 31 13:21:40 BST 2012 armv6l GNU/Linux ||After installing new kernel with rpi-update on 2012-06-01<br />
|-<br />
|Lexar SDHC 8GB Class 4 "Multi-use" ||18.9 ||6.8 ||Debian Wheezy "Raspbian" ||3.1.9+ #110 PREEMPT ||<br />
|-<br />
|Lexar SDHC 8GB Class 6 "PLATINUM II" ||19.7 ||10.1 ||Debian Wheezy "Raspbian" || 3.1.9+ #168 PREEMPT ||<br />
|-<br />
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||5.3 ||4.8 ||Debian Wheezy/sid || Linux raspberrypi 3.2.19-rpi1+ #3 ||<br />
|-<br />
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||18.9 ||9.0 ||Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #168 PREEMPT || Same card as 'Lexar SDHC 16GB Class 10 "PLATINUM II"' above - imaged with Raspbian<br />
|-<br />
|Lexar SDXC 64GB UHS-I Class 10 Premium series ||20.7 ||15.8 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Lexar SDHC 8GB UHS-I Class 10 Premium series ||19.4 ||8.8 ||raspbmc-rls-1.0-hardfp-b20131223-u20131223 ||Linux raspbmc 3.10.24 #2 PREEMPT Mon Dec 23 05:18:12 UTC 2013 armv6l GNU/Linux ||man:0x000028 oem:0x4245 name: hwrev:0x0 fwrev:0x2<br />
|-<br />
|Mushkin SDHC 16GB Class 10 MKNSDHCC10-16GB ||19.7 ||10.9 ||2012-07-15-wheezy-raspbian ||3.1.9+ #168 PREEMPT ||<br />
|-<br />
|PNY SDHC 8GB Class 6 Limited Edition ||7.4 ||13.2 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|PNY SDHC 32GB Class 10 Elite Performance ||20.4 ||15.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.6.11+ #456 PREEMPT armv6l sys v.3.3.3 ||avoid_pwm_pll=1 arm_freq=1000 gpu_freq=675 sdram_freq=500 core_freq=275 over_voltage=6<br />
|-<br />
|SanDisk MicroSDHC 4GB ||5.1 ||11.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk UHS-I C10 Ultra SDHC 8GB (SDSDU-008G-U46)||19.1 ||20.8 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC 8GB class 10 (30 MB/s) ||21.7 ||15.7 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #434 PREEMPT Wed May 1 21:13:52 BST 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0 (some read time trials with drop caches: 21.0/21.7/21.8/21.8/21.8/21.8/(write#2:)21.7; two write trials: 15.7/15.8; timings (dd;sync): 33.761;5.799)<br />
|-<br />
|Panasonic SDHC 4GB Class 10 UHS-I ||11.2 ||6.2 ||Debian Wheezy "Raspbian" ||3.1.9+ #144 PREEMPT || Panasonic RP-SDU04GE1K<br />
|-<br />
|Sony SDHC 8GB Class 10 UHS-1 ||20.8 ||17.2 ||Debian Wheezy "Raspbian" ||3.2.27+ #250 PREEMPT ||<br />
|-<br />
|Sony SDHC 4Gb Class 10 UHS-I "40MB/s" (SF-4UY) ||18.8 ||10.3 ||openELEC 3.0.6 ||Linux openelecPi 3.6.11 #1 PREEMPT Thu Jun 13 21:32:37 CEST 2013 armv6l GNU/Linux ||man:0x000027 oem:0x5048 name:SD04G hwrev:0x3 fwrev:0x0<br />
|-<br />
|Sony SDHC 8Gb Class 10 UHS-I "90MB/s" (SF-8UX) ||21.1 ||16.9 ||Raspbian 2013-05-25-wheezy ||Linux raspberrypi 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux ||man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x0<br />
|-<br />
|Sony SDHC 16Gb Class 10 UHS-I "40MB/s" ||21.8 ||13.5 ||Raspbian 2013-07-26-wheezy ||Linux raspberrypi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra 16GB MicroSDHC Class 10 UHS-1 + Adapter "30MB/s" (SDSDQUA-016G-U46A) ||18.5 ||7.3 ||Raspbian 2014-01-07 wheezy ||Linux mmmpie 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra 8GB MicroSDHC Class 10 UHS-1 + Adapter "48MB/s" (SDSDQUAN-008G-G4A) ||18.8 ||14.5 ||Raspbian 2014-12-24 wheezy ||Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme 16GB UHS-I/U3 Micro SDHC Memory Card Up to 60MB/s Read with Adapter- SDSDQXN-016G-G46A ||20.3 ||18.2 ||OpenELEC 5.0.1 ||Linux OptimusPi 3.18.5 #1 SMP PREEMPT Sun Feb 1 14:59:37 CET 2015 armv7l GNU/Linux ||Raspberry Pi 2 ||<br />
|-<br />
|SanDisk Extreme 16GB UHS-I/U3 Micro SDHC Memory Card Up to 60MB/s Read with Adapter- SDSDQXN-016G-G46A ||19.8 ||24.7 ||OSMC Alpha 4 ||Linux osmc 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l GNU/Linux ||Raspberry Pi 2 ||<br />
|}<br />
<br />
=== SD(DC|DX] Card Class 6 & 10 Hints with OverClockings === <br />
[http://elinux.org/index.php?title=RPiconfig&section=14 | SD card usage Hints with OverClocking]<br />
{{Template:BackToRPiHub}}<br />
[[Category:RPi SD card]]<br />
<br />
== References ==<br />
<references></references><br />
{{Template:Raspberry Pi}}</div>AutoStatichttps://elinux.org/index.php?title=RPi_SD_cards&diff=376936RPi SD cards2015-03-29T13:26:58Z<p>AutoStatic: Added info about max. throughput and updated write and read speed dd commandos</p>
<hr />
<div>== SD cards ==<br />
<br />
The SD card is a key part of the Raspberry Pi; it provides the initial storage for the Operating System and files. Storage can be extended through many types of USB connected peripherals.<br />
<br />
When the Raspberry Pi is 'switched on', i.e. connected to a power supply, a special piece of code called the bootloader is executed, which reads more special code from the SD card that is used to start up the Raspberry Pi. If there is no SD card inserted, it will not start. Do NOT push in or pull out an SD card while the Raspberry Pi is connected to the power, as this is likely to corrupt the SD card data (you might get away with it, but it is best not to).<br />
<br />
The SD card must be formatted, or written to, in a special way that means the Raspberry Pi can read the data it needs to start properly. If you are new to this check the instructions, or buy a pre-formatted SD card.<br />
<br />
One advantage to using an SD card like this is that you can have several SD cards, each with a different operating system, or a different purpose. Simply power off, switch cards, and reconnect the power. You have a different computer to play with.<br />
<br />
Please bear in mind that the maximum throughput of the card reader of the Raspberry Pi is 25 MB/s and that most likely read and write speed won't exceed 22 MB/s.<br />
<br />
=== Which SD card? ===<br />
<br />
[[File:SD_Card_dimensions.png|right|frameless|SD card sizes]]<br />
<br />
SD cards come in three physical sizes (see picture). The Raspberry Pi A and B use the largest one; the miniSD card and the MicroSD card can be used in those models, but you will need an adapter / holder to fit it. The Raspberry Pi B+ and Raspberry Pi 2 Model B (second generation) require the smallest one, the MicroSD.<br />
<br />
SD cards come in a range of storage sizes. You will likely need more than 2 GB.<br />
<br />
There are other properties of SD cards that are not covered here. Read the [http://en.wikipedia.org/wiki/Secure_Digital Wikipedia article] for those details.<br />
<br />
=== Other SD card content ===<br />
<br />
See the following links for other information:<br />
<br />
* [[RPi_Distributions | Select a Distribution]]<br />
<br />
* [[RPi_Easy_SD_Card_Setup | Easy SD card set up]]<br />
<br />
* [[RPi_Advanced_Setup | Advanced set up]]<br />
<br />
* [[R-Pi_Troubleshooting#SD_cards | Troubleshooting]]<br />
<br />
== Preinstalled SD cards ==<br />
<br />
You might like to consider buying a preinstalled card; a wide range of branded SD cards preinstalled with operating systems are available. If you don't buy a preinstalled card, you will have to create one yourself. Check the [[RPi_Easy_SD_Card_Setup | SD Card setup]] page to help you make this decision. That page also shows where these cards can be bought from.<br />
<br />
==Verification==<br />
<br />
Users have listed working and non-working cards here. The [https://www.sdcard.org/home SD Card Association] suggests there are more than 400 brands across dozens of product categories and more than 8,000 models. These are just a few.<br />
<br />
=== Is this reliable? ===<br />
<br />
Unfortunately there is little scope for analysis of the failures given below. There are several reasons why a card may not work. You will notice that the same card may be shown as working and not working; the model numbers on cards do seem to be confusing.<br />
<br />
* the firmware / bootloader on early Raspberry Pi boards had a problem with Class 10 high speed cards. This has been fixed.<br />
* the drivers in some Linux distributions have been improved since the initial release<br />
* the Raspberry Pi can suffer from performance problems if peripherals are drawing too much power from the power supply; one of the consequences is errors from the SD card<br />
* unless using a preinstalled card, users have to copy a distribution image to the SD card. This might be considered more technical than the user has previously experienced, resulting in a faulty SD card<br />
* there are many cheap Chinese copies of (brand name) SD-Cards on the market, in addition they are often mislabelled as having greater capacity than they really have, see [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit SanDisk counterfeit cards]<br />
<br />
... and of course, they may be faulty!<br />
<br />
=== Technical Information ===<br />
<br />
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)<br />
<br />
For this reason, please specify product numbers in the lists below, when possible.<br />
<br />
You can also attach the following fields from your card's CID:<br />
<pre><br />
cd /sys/class/mmc_host/mmc?/mmc?:*<br />
echo "man:$(cat manfid) oem:$(cat oemid) name:$(cat name) hwrev:$(cat hwrev) fwrev:$(cat fwrev)"<br />
</pre><br />
<br />
=== Working / Non-working SD cards ===<br />
<br />
The table can be sorted using the triangles in the top row. Please add entries in the correct location, so that the initial sort is by Manufacturer, Type, Size and Class. Keep separate entries for working and non-working. Put your user name and date in the final column, so people can judge if the problem is still likely to occur.<br />
<br />
{| class="wikitable sortable"<br />
! OK !! Manufacturer !! Type !! Size (GB) !! Class !! Model !! Info !! Logged by<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|7DAYSHOP.CzOM<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Ap 3 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Acumem<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|many errors on 7 Jun 2012<br />
|S0rce 8 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|SDHC<br />
|2<br />
|?<br />
|Speedy (MMAGF02GWMCA -NA)<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|2<br />
|2<br />
|Speedy 8B0947<br />
|<br />
|Stevhorn 14 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|4<br />
|4<br />
|ASDH4GCL4-R<br />
|Possibly a bit slow. Stiff to pull out of the PI.<br />
|James.C 24 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|4<br />
|4<br />
|BH1109416141G<br />
|<br />
|Blutme 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|2<br />
|MMB3F08GWMCA-GE<br />
|<br />
|Timishier 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|6<br />
|MMAGR08GUDCA-DB<br />
|sometimes boots (Dattaway)<br />
|Florz 26 May 2012, Dattaway 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|8<br />
|10<br />
|AUSDH8GCL10-R, P-SDH8G10-EC, ASDH8GCL10-R<br />
|<br />
|Elatllat 22 Dec 2011, Madcow42 18 Jul 2012, Thenix 14 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|16<br />
|6<br />
|<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0<br />
|Semtex 21 May 2012, Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|SDHC<br />
|16<br />
|6<br />
|SD5MY168G0<br />
|won't boot<br />
|Nijntje 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|16<br />
|10<br />
|16GSDHC10, ASDH16GUICL10-R<br />
|<br />
|Captainralf 6 Jun 2012, honza801 7 Jan 2013, CopperHead4750 28 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|SDHC<br />
|32<br />
|10<br />
|AUSDH32GCL10-R<br />
|<br />
|Tom3f 13 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|MicroSD w/ adapter<br />
|0xAF 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|8<br />
|10<br />
|AUSDH8GUICL10-RA1<br />
|MicroSD w/ adapter<br />
|johnniepop 15 Apr 2013,(Elpadre 24/Nov/14)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GCL10-RA1<br />
|with adapter<br />
|Frank26080115 1 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-R<br />
|Raspberry Pi B+<br />
|zl2wrw 1 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x0 fwrev:0x2 Raspberry Pi B+ 2014-12-24-wheezy-raspbian<br />
|c 21 Jan 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi 2 B 2015-02-02-wheezy-raspbian<br />
|c 13 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi 2 B 2015-01-30-wheezy-raspbian: note: OK after running update!!<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi B 2015-01-30-wheezy-raspbian<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|16<br />
|10<br />
|AUSDH16GUICL10-RA1<br />
|Raspberry Pi B+ 2015-01-30-wheezy-raspbian<br />
|johnty 2 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Adata<br />
|microSDHC<br />
|32<br />
|10<br />
|AUSDH32GCL10-RA1<br />
|2013-05-25-wheezy-raspbian<br />
|pAIgn10 6 Jun 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Adata<br />
|microSDHC<br />
|64<br />
|10<br />
|<br />
|with adapter<br />
|rolgiati 2 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Agfa<br />
|microSDHC<br />
|16<br />
|6<br />
|<br />
|with adapter ENAAJK121960<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|AmazonBasics<br />
|SDHC<br />
|4<br />
|10<br />
|B004Q3R9AQ<br />
|We have had a 50% failure rate on these with file system corruption, even with write protection enabled, with Raspian<br />
|pgardella 27 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|8<br />
|10<br />
|B0058GH0LS<br />
|<br />
|Reid 7 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|16<br />
|10<br />
|B0058GH1IK<br />
|Tested 24 Jun 2012 no errors found<br />
|M3ch4 26 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|AmazonBasics<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|many errors on 7 Jun 2012<br />
|S0rce 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|AmazonBasics<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Lrosengreen 16 Aug 2012<br />
|-<br />
|style='background-color:#a00;'| nok<br />
|Ansonchina<br />
|microSDHC<br />
|32<br />
|10<br />
|EVO<br />
|Card from Aliexpress, Tested on RPi B+<br />
|Kimvais 2015-02-26<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Apacer<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|<br />
|Hamish 13 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Apacer<br />
|SDHC<br />
|16<br />
|10<br />
|AP16GSDHC10<br />
|Does not boot / io error from dmesg with os running from usb.<br />
|Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Apacer<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|with adapter<br />
|Jasen 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|SDHC<br />
|4<br />
|10<br />
|4GBSDHC10<br />
|<br />
|Dick Jones, 24 Sept 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|SDHC<br />
|16<br />
|4<br />
|1447<br />
|<br />
|Uberfoo 23 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Centon<br />
|MicroSDHC<br />
|32<br />
|10<br />
|<br />
|Raspberry Pi 2 Model B<br />
|Riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CnMemory<br />
|SDHC<br />
|8<br />
|4<br />
|84209_8GB_SDHC (Silver/Black label says 'High Capacity Card') Maplins<br />
|operation is much slower than with a SanDisk 4GB Class 4 card<br />
|Ceptimus 2 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CnMemory<br />
|microSDHC<br />
|8<br />
|10<br />
|86071<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0. write 10.4 MB/s, read 20.1 MB/s<br />
|fiodschi, 19 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|CoreMicro<br />
|microSDHC<br />
|8<br />
|4<br />
|CMMICROSDCL4/8GB<br />
|man:0x000082 oem:0x4a54 name:NCard hwrev:0x1 fwrev:0x0<br />
|Dick Jones, 4 Dec 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Dane-Elec<br />
|SDHC<br />
|4<br />
|4<br />
|DA-SD-4096-R<br />
|Error -110 whilst initialising sd card <br />
|captbrando, 04 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dane-Elec<br />
|SDHC<br />
|16<br />
|4<br />
|<br />
|<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dane-Elec<br />
|SDHC<br />
|16<br />
|10<br />
|Pro 200X DEMS16GB2683ENBA<br />
|<br />
|Ivazquez 15 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Delkin<br />
|SDHC<br />
|4<br />
|6<br />
|Delkin pro<br />
|works with Fedora Beefy Miracle 17<br />
|Gersh 7 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dick Smith<br />
|SDHC<br />
|4<br />
|4<br />
|XG4958<br />
|<br />
|James.C 14 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dick Smith<br />
|SDHC<br />
|8<br />
|4<br />
|XG4959<br />
|This 8GB DSE SD (S608G1137) works fine on latest Raspbian as at Dec 2013<br />
|Sauce 3 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Dikom<br />
|SDHC<br />
|16<br />
|10<br />
|207H3MD016IBSD<br />
|<br />
|Churchill 1 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|16<br />
|10<br />
|Pro Photo 200x<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Duracell<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0 (~4.6MB/s read, ~4.4MB/s write on debian6-19-04-2012)<br />
|Bedevere 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SD<br />
|2<br />
|?<br />
|<br />
|man:0x000027 oem:0x5048 name:SD02G hwrev:0x2 fwrev:0x0<br />
|Incyi 7 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SD<br />
|16<br />
|10<br />
|EKMSD16G150XHC<br />
|less than half as fast as Sandisk 16gb Class 10<br />
|Declension 8 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|4<br />
|4<br />
|EKMSD4G60XHCN<br />
|<br />
|Korban 18 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|EKMSD8G150XHC<br />
|~17 MB/s read / ~14 MB/s write in 'dd' (man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0)<br />
|NC 10 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|180SD10MK8<br />
|MicroSD w/ adapter for Model: B+<br />
|SA 4 Oct 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Emtec<br />
|SDHC<br />
|8<br />
|10<br />
|EKMSD8G150XHC<br />
|Both Raspmc and OpenElec tries to boot, but throws lots of errors<br />
|vygandas 12 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Extrememory<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0<br />
|Fjen 10 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Extrememory<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0<br />
|Mfg 3 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Extrememory<br />
|SDHC<br />
|32<br />
|10<br />
|Marked "Hyperformance"<br />
|<br />
|MathieuMD 29 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fuji<br />
|SDHC<br />
|32<br />
|10<br />
|P10NM00580A<br />
|(man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0)<br />
|Crashmeplease 28 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fujifilm<br />
|SDHC<br />
|8<br />
|4<br />
|P10N079840A<br />
|<br />
|Paul 26 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Fujifilm<br />
|SDHC<br />
|8<br />
|10<br />
|A94125 1464<br />
|<br />
|sukram230799 06 Sep 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Goodram<br />
|SDHC<br />
|8<br />
|10<br />
| SDC8GHC10PGRR9<br />
|<br />
|MPastuszko 17 July 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Chmurli 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|16<br />
|4<br />
|SDU16GHCAGRR10<br />
|<br />
|Mojca 22 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Goodram<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|<br />
|Druss 5 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|GSkill<br />
|SDHC<br />
|16<br />
|10<br />
|FF-TSDG16GA-C10<br />
|<br />
|GKontadakis & Jim Kastrinakis (the toxic duet of IT) 31 Aug 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|GSkill<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Flatline403 12 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDHC<br />
|2<br />
|2<br />
|<br />
|<br />
|Mikerr 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDHC<br />
|8<br />
|6<br />
|High Speed Pro<br />
|<br />
|Bubblebobble 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hema (Dutch dept. store)<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Frankivo 25 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hama<br />
|SDXC<br />
|128<br />
|10<br />
|00114945<br />
|Tested with Raspbian (dd + resize) and works without issues.<br />
|SebastianB 21 Jun 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Hema (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Hjongste 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HIDISC<br />
|SDHC<br />
|8<br />
|10<br />
|HDPSDH8GC10<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Nkt00125 06 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HP<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|doesn't reboot during first time startup process, but restart again and fine after that<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|HP<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Harkin 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|SDHC<br />
|4<br />
|10<br />
|<br />
|<br />
|CurlyMo 1 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|image write had issues, might be my inexperience. It boots & shows Xserver<br />
|BjornW 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Wieltje 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|(20 MB/sec)<br />
|Alphons 2 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|ICIDU<br />
|microSDHC<br />
|32<br />
|10<br />
|<br />
|(20 MB/sec)<br />
|Alphons 2 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Imation<br />
|SDHC<br />
|32<br />
|10<br />
|S732G1232<br />
|mmc0: controller never released inhibit bit(s)<br />
followed by many and various <br />
mmc0: timeout errors<br />
|ChrisGreen 28 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|4<br />
|4<br />
|SD-K04G (purple label), SD-M04G<br />
|<br />
|Dmd 27 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|4<br />
|4<br />
|S404G1115<br />
|<br />
|Pluggster 16 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|4<br />
|10<br />
|Ultima Pro<br />
|<br />
|Ace 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|6<br />
|Ultima Pro<br />
|initial error -110 but boots within 5 seconds with no further errors or issues<br />
|Bubblebobble 17 May 2012mmc0: controller never released inhibit bit(s) and<br />
mmc0: timeout<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro (20 MB/s)<br />
|works: initial error -110 but boots within 5 seconds with no further errors or issues<br />
|Auldy 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro 20MB/s SD-K08G - 1238-W19718L<br />
|Works fine.<br />
|mpmc 22 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|8<br />
|10<br />
|Ultima Pro 20MB/s SD-K08G - 1245-WJ1479L<br />
|Gets too hot and wont boot.<br />
|mpmc 22 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|16<br />
|6<br />
|Ultima Pro<br />
|<br />
|Zagblorg 26 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Integral<br />
|SDHC<br />
|16<br />
|6<br />
|Ultima Pro (SH016GAA2BB)<br />
|<br />
|Jmg123 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|16<br />
|10<br />
|Ultima Pro<br />
|20 MB/s<br />
|Tomgco 17 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|FLX 2 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|SDHC<br />
|32<br />
|10<br />
|Ultima Pro (20 MB/s)<br />
|<br />
|Ab30021190 30 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Integral<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|Tested with Raspbian 2013-12-20, with the included microSD adapter.<br />
|Plof 1 January 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|(Intenso)<br />
|SDHC<br />
|16<br />
|4<br />
|<br />
|<br />
|johnniepop 15 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|(Intenso)<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2 OpenELEC 3.10.20 write 8.0MB/s read 10.6MB/s<br />
|Cosbug 28 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Joyflash<br />
|SDHC<br />
|16<br />
|10<br />
|LTSD1112016GB<br />
|<br />
|Vk2amv 8 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingmax<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingmax<br />
|microSDHC<br />
|4<br />
|4<br />
|KM04GMCSDHC4<br />
|won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingmax<br />
|microSDHC<br />
|8<br />
|4<br />
|KM08GMCSDHC41A<br />
|won't reboot when it's hot<br />
|Slabua 2 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SD<br />
|2<br />
|<br />
|KING-SD-M02G-BULK<br />
|(0xAF 12 Jun 2012) boots the kernel, but damages the filesystem<br />
|Md84419 5 Nov 2011, 0xAF 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB<br />
|<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|<br />
|James.C 20 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|(man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0), boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|4<br />
|SD4/4GB SD-K04G<br />
|One or two worked perfectly, but most of them showed filesystem corruption after some months, usually (but not only) after power loss. Read-only filesystem didn't fix the issue. Tested on 20 SD cards on 15 different Raspberry Pi model B.<br />
25-02-2015 update: I found that all the broken SD cards were made in Taiwan. The only one made in Japan is still working (from 19/04/2012).<br />
|Gabriele Martino 23 Dec 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|Boots kernel but won't run init (times out). (works fine - Malvineous)<br />
|RoSha 10 May 2012, Malvineous 17 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|4<br />
|10<br />
|SD10V/4GB<br />
|<br />
|Luismreis 2 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|4<br />
|SD4/8GB<br />
|Works reliably with Raspbian 18-9-2012 and previous Debian releases (Picards)<br />
|Md84419 5 Nov 2011, Picards 28 Oct 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|4<br />
|SD4/8GB<br />
|does not work with current build of raspbmc (LastSilmaril), unreliable with raspbian (Quentinsf)<br />
|LastSilmaril 24 May 2012, Quentinsf 20 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|6<br />
|SD6/8GB<br />
|errors on boot, but ok (Debian), does not work with raspbmc rc2 or archlinux<br />
|Jamsta 5 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10G2/8GB ultimateX 100X, SD10V/8GB ultimateX 120X<br />
|<br />
|ShiftPlusOne 24 Apr 2012, Stevepdp 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10G3/8GB Elite<br />
|Works with Raspbian Wheezy 25/05/2013 <br />
|Deicide 17 July 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|8<br />
|10<br />
|SD10V/8GB<br />
|<br />
|KingC 7 February 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|4<br />
|SD4/16GB<br />
|<br />
|Skiesare 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|4<br />
|SDC4/16GB17<br />
|Works with Raspbian wheezy.<br />
|atakanaksit 24/08/2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|6<br />
|SD6/16GB<br />
|<br />
|Malvineous 17 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10G2/16GB ultimateX 100X, SD4/16GBET<br />
|<br />
|Stevepdp 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0372-002. A00LF TAIWAN JM94450-901.A00LF)<br />
|Seems to work<br />
|Epa 20130403<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB<br />
|<br />
|Franeks 14 Feb 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10G2/16GB ultimateX 100X<br />
|mmc0: Timeout waiting for hardware interrupt<br />
|Kimmoli 27 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB<br />
|Starts boot ok but then gets stuck in mmc0 timeouts<br />
|Hh 14 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0440-001. A00LF TAIWAN JM94513-908.A00LF)<br />
|mmc0 timeouts<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|SDHC<br />
|16<br />
|10<br />
|SD10V/16GB <br/>(N0440-002. A00LF TAIWAN JM94585-902.A00LF)<br />
|not booting. no hdmi output. red leds on solid, green leds very lightly dimmed, no green flash/blink<br />
|smerz 20131230<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|32<br />
|10<br />
|SD10G2/32GB, ultimateX 100X, SD10V<br />
|<br />
|Tony 29 May 2012, Pmvarsa 17 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDHC<br />
|32<br />
|10<br />
|SD10V/32GB <br/>(N0415-002.A00LF TAIWAN JM94450-913.AOOLF)<br />
|works<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SDX10V/64GB<br />
|<br />
|Bromont 25 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SDCX10/64GB<br />
|2015-02-16-raspbian (a bit slow)<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDXC<br />
|64<br />
|10<br />
|SD10G3/64GB UHS-I Elite<br />
|<br />
|Plnt 10 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|SDX<br />
|128<br />
|10<br />
|SDX10V/128GB<br />
|Must format it as FAT32. Took a very long time for Pi to install system.<br />
|H. Matis 3 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|2<br />
|<br />
|N0185-002.A00LF<br />
|Adapter (File system .img written via Transcend microSDHC "USB stick-like" adapter - P3-102510)<br />
|TrevorGowen 27 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|2<br />
|<br />
|SD-CO2G<br />
|Does not boot. Capacity (1.97 GB) seems only just enough for 2013-02-09-wheezy-raspbian.img (1.94 GB). <br />
|Pe7er 18 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Bredman 16 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC4/4GB (CO4G)<br />
|Works great with Kingston SD adapter<br />
|Horgrim 03 Mar 2015<br />
|-<br />
|style='background-color:#c00;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC4/4GB (CO4G)<br />
|Starts to boot and fails. "... Kernel panic ... unable to mount root fs on unknown block ... "<br />
|ow3n 4 Oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|8<br />
|4<br />
|SDC4/8GB<br />
|Does not work with NOOBS (do not recognize it) or applying an image of Debian or Fedora on it (Kernel panic ... cannot mount fs) <br />
|Lilt 9 May 2012 * ElPadre 15 April 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|4<br />
|SDC4/16GB<br />
|man:0x000002 oem:0x544d name:SA16G hwrev:0x1 fwrev:0x1 * Filesystem is corrupted on a daily basis (Raspbian) <br />
|Rmoser 16 June 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|4<br />
|SDC4/32GB (C32G)<br />
|<br />
|ow3n 8 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|4<br />
|10<br />
|SDC10/4GB<br />
|man:0x000041 oem:0x3432 name:SD4GB hwrev:0x3 fwrev:0x0 Works on Raspian 2014-12-24 with RPi Model B+<br />
|c 22 Jan 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Kingston<br />
|microSDHC<br />
|8<br />
|10<br />
|SDC10/8GB<br />
|Work on Raspian, '''but doesn't work with NOOB'''. [Suggestion : download full image of O.S. and put it into SD card directly.]<br />
'''Works with NOOBS'''<br />
<br>Sometimes I/O errors and: mmc0: timeout waiting for hardware interrupt<br />
<br>'''Does not work in RPi Model B+ with RaspBMC'''. Starts booting but all writes fail.<br />
<br>'''NOOBS works fine''', installed Arch and Raspbian successfully.<br />
|webserfer 03 March 2013 submarine 03 Jan 2014 diogobackup 23 Jan 2014 felon 20 July<br />
javierrgz 3 Sep 2014<br />
<br><br />
tinkergnome 24 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|10<br />
|SDCA10/16GB (SD16G)<br />
|2014-09-09-wheezy-raspbian.img, man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0<br />
|bcraun 5 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|16<br />
|10<br />
|SDC10/16GB<br />
|Doesn't work with N0390-002.A00LF though (tested with Raspbian “wheezy”) - mmc0 timeouts, waiting for hw int. I wouldn't recommend buying this card. N0460-002.A00LF: Does not boot / io error from dmesg with os running from usb.<br />
|Arrow 14 Jun 2012, J3rGuS 19 March 2013, Jettis 5 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|10<br />
|SDC10/32GB<br />
|Tested with Raspbian wheezy on RPI B+, no problem so far.<br />
|Julien Bonnier 30 Sept 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kingston<br />
|microSDHC<br />
|32<br />
|10<br />
|SDC29/32GB<br />
|tried it with retropie raspian 7.5 so far no problems<br />
|Guido(dakiluxa) 27 Fun 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kodak<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kodak<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Britaniola 22 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kruidvat (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Boeboe 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Kruidvat (Dutch dept. store)<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Asiklov 25 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|Boots consistently and no error messages in log after 1/2 hour use (works with Raspbmc - 321liftoff)<br />
|Russell 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|4<br />
|6<br />
|Platinum II<br />
|<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|4<br />
|Milti-Use SDHC LSD8GB ASBWMC2 rev.B, on card 31352-oc4-8gbbm-a<br />
|sold in 1 or 2 pack<br />
|Spyder Mar-2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|6<br />
|Platinum II<br />
|<br />
|Shirro 7 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|6<br />
|Premium series<br />
|<br />
|blazi 17 December 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|10<br />
|Platinum II (200X) LSD8GBBBEU200C10<br />
|Works fine on OpenElec 3.0.6<br />
|Vygandas 18 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|8<br />
|10<br />
|Platinum II UHS-I (LSD8GBBSBNA200C10 Rev C)<br />
|Works fine w/NOOBS v1.3.4 Raspbian<br />
|fortran87 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|16<br />
|6<br />
|Platinum II<br />
|<br />
|Semtex 21 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDHC<br />
|32<br />
|10<br />
|Platinum II SDHC UHS-I<br />
|<br />
|Dedejacoby 11 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDXC<br />
|64<br />
|10<br />
|Premium series<br />
|UHS-I<br />
|Kuisma 17 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|SDXC<br />
|128<br />
|10<br />
|LSD128CTBNA400<br />
|UHS-I<br />
|AdamGreenblatt 12 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|microSDHC<br />
|16<br />
|10<br />
|(LSDMI) 16GBBEU300A<br />
|Raspberry Pi B+ Model (tested on OpenELEC,xbian, raspbmc, kali linux)<br />
|@xhark 05 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Lexar<br />
|microSDHC<br />
|32<br />
|10<br />
|HIGH-SPEED<br />
|<br />
|RogerH 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Master<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|[man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0]<br />
|Malvineous 1 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Master Optimum<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|Only 1 red LED lit, no HDMI output. Started booting one single time then crashed during boot. No errors writing card on Mac<br />
|User234891 23 May 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Maxell<br />
|SDHC<br />
|16<br />
|10<br />
|X-Series 83-P120001149-1<br />
|<br />
|Paul 26 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Maxell<br />
|microSDHC<br />
|8<br />
|10<br />
|X-SERIES 854716.00.TW<br />
|Tested with Raspberry PI A+ and Raspbian. No problems so far.<br />
|Unas 4 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Maxell<br />
|microSDHC<br />
|16<br />
|4<br />
|X-SERIES<br />
|MicroSD w/ adapter. Tested with latest version of Raspbian (as at date of entry).<br />
|Drummingsim 28 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|<br />
|Buadhach 29 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|SDHC<br />
|32<br />
|6<br />
|MD86965<br />
|works well with NOOBS 1-2-1, Raspbian and RiscOS<br />
|Joerg 19 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|microSDHC<br />
|32<br />
|6<br />
|MD86958<br />
|works well with NOOBS 1-2-1 and Raspbian<br />
|Joerg 14 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Medion<br />
|microSDHC<br />
|32<br />
|10<br />
|MD87252<br />
|micro SD w/adapter on model B with Raspbian. man:0x000027 oem:0x5048 name:SD32G hwrev:0x3 fwrev:0x0<br />
|KMS 22 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Memorex Travel Card<br />
|SDHC<br />
|8<br />
|10<br />
|?<br />
|Works well with Raspbian 2013-09-25.<br />
|The Doctor, 25 October 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Memory2Go<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1029<br />
|I/O Errors leading to Kernel Panic on startup<br />
|Snohi 12 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MemoryStar<br />
|microSDHC<br />
|16<br />
|10<br />
|?<br />
|man:0x000089 oem:0x0303 name:NCard hwrev:0x1 fwrev:0x0 - works well with Raspbian 2014-12-24 and Asterisk 2014-07-31 images.<br />
|Carriba, 27 December 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Microcenter<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|hasn't worked with any of the images I've tried; appears to be completely unrecognized<br />
|Pnppl 11 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|8<br />
|4<br />
|0289508<br />
|(sold in bins at checkout)<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|8<br />
|10<br />
|0349728<br />
|(sold in bins at checkout)<br />
|Pdp7 25 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|(sold in bins at checkout)<br />
|Crayfishandy 11 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Microcenter<br />
|SDHC<br />
|64<br />
|10<br />
|<br />
|(sold in bins at checkout) ... Must format it as FAT32.<br />
|alex222888 27 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mushkin<br />
|SDHC<br />
|16<br />
|10<br />
|MKNSDHCU1-16GB<br />
|<br />
|Frank26080115 1 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mushkin<br />
|SDHC<br />
|32<br />
|10<br />
|MKNSDHCC10-32GB<br />
|<br />
|Openboat 30 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Mustang<br />
|SDHC<br />
|8<br />
|10<br />
|SD8GHCCL10MU-R<br />
|<br />
|Xanatos 31 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|8<br />
|10<br />
|MYMESDH8G10<br />
|(latest batch not working - Bubblebobble)<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|MyMemory<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|<br />
|Jezmck 27 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|16<br />
|10<br />
|MYMESDH16G10<br />
|<br />
|Jblackburn 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|MyMemory<br />
|SDHC<br />
|32<br />
|10<br />
|<br />
|<br />
|Dale2507 10 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|OCZ<br />
|SDHC<br />
|8<br />
|6<br />
|Gold Series (08110596-8GB-6)<br />
|tested with debian6-19-04-2012<br />
|Alkarex 16 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Optima<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|Does not boot with Raspbian Wheezy 2012-07-15. Works with 2012-09-18<br />
|Penguintutor 19 Aug 2012 / 10 Oct 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Optima<br />
|SDHC<br />
|8<br />
|10<br />
|Pro-Speed<br />
|<br />
|DaWoodster 13 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Mikerr 5 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|4<br />
|RP-SDLB04GAK<br />
|Tested with Pidora (Fedora)<br />
|jwdietrich 06 Jul 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|10<br />
|UHS-I<br />
|(~11.2MB/s read, ~6.2MB/s write)<br />
|M4rcs 26 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|4<br />
|10<br />
|RP-SDRB04G<br />
|Tested with Rasbian Wheezy<br />
|jwdietrich 02 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|2<br />
|<br />
|(~11.1MB/s read, ~9.7MB/s write)<br />
|Malexmave 19 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|~4.8MB/s read, ~4.4MB/s write, following the Performance below<br />
|Xonx 21 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Panasonic<br />
|SDHC<br />
|8<br />
|10<br />
|RP-SDU08GD1K - London-2012-Collection<br />
|mmc0: timeout waiting for hardware interrupt<br />
|Selsinork 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|6<br />
|PSF8GSDHC10-PC<br />
|<br />
|Paradigmic 7 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|6<br />
|PS8GSDHC10-BC<br />
|repeatable corruption after 1 or 2 reboots with 2012-07-15-wheezy-raspbian<br />
|Ntrepid8 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|LX Series PSF8GSDHC10-PC1<br />
|<br />
|Nugget 9 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|LX Series PSF8GSDHC102PK<br />
|Twin pack<br />
|verket 8 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|PSF16GMCSDHC10<br />
|<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|SDHC<br />
|8<br />
|10<br />
|PSF8GSDHC10-PC<br />
|won't even boot 2012-08-16-wheezy-raspbian (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc). Seems functional in Arch, but sometimes freezes at the beginning of boot (blinking underscore)<br />
|Dgatwood 12 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|16<br />
|10<br />
|LX Series PSF16GSDHC10-PC1 (PSF16GSDHC10)<br />
|Tested with Rasbian Wheezy<br />
|Leonardicus 25 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|16<br />
|10<br />
|LX Series (PSF16GSDHC10)<br />
|19.3MB/s read, 9.3MB/s write<br />
|Jamesnine 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|32<br />
|10<br />
|PSF32GSDHC10<br />
|<br />
|Megs 29 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|SDHC<br />
|32<br />
|10<br />
|UHS-1 PEF32GSDHC10U1<br />
|20.4MB/s read, 12.1MB/s write<br />
|Bengoerz 12 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|microSDHC<br />
|8<br />
|10<br />
|PSF8GMCSDHC10<br />
|I observed behavior similar to the full size version of this card (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc).<br />
|CVBruce 25 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Patriot<br />
|microSDHC<br />
|16<br />
|10<br />
|PSF16GMCSDHC10<br />
|requires recent kernel update for boot<br />
|Wmdopple 9 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Patriot<br />
|microSDHC<br />
|16<br />
|10<br />
|PSF16GMCSDHC10<br />
|fails with 2012-12-16-wheezy-raspbian and with 1/8/13 kernel update. mmc0: controller never released inhibit bit(s) and<br />
mmc0: timeout waiting for hardware interrupt. Other cards work.<br />
|verket 8 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Peak<br />
|microSDHC<br />
|4<br />
|4<br />
|MMBTR04GUBCA-ME<br />
|tested with Arch<br />
|Selsinork 20 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Philips<br />
|SDHC<br />
|8<br />
|4<br />
|FM08SD35B<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Philips<br />
|microSDHC<br />
|8<br />
|4<br />
|FM08MD35B<br />
|(man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|<br />
|Njoyard 6 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|4<br />
|10<br />
|127660<br />
|Tested with a Raspbian Wheezy using a custom and a stock kernel. Both Ok.<br />
|cpb 15 oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|6<br />
| Fails with mmc error (7 cards in 10) on ccidentalis_v02. Fails on laptops which use mmc driver instead of SATA<br />
|(man:0x00006f oem:0x0000 name:SMI hwrev:0x1 fwrev:0x0)<br />
|Leucos 22 March 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|8<br />
|O08G840 M3100487 TW<br />
|<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|10<br />
|RTK247T5MD08G order no. 126982<br />
|<br />
|Cobalt 9 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|8<br />
|10<br />
|8DK52-131ME<br />
|hctosys.c: unable to open rtc device (rtc0)<br />mmc0: Timeout waiting for hardware interrupt - cmd18<br />mmc0: Timeout waiting for hardware interrupt - cmd12<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, retrying<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, retrying<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmcblk0: error -110 sending status command, aborting<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />mmc0: Timeout waiting for hardware interrupt - cmd13<br />Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)<br />on Arch Linux ARM hf 2013-02-11<br />
|Cobalt 9 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Platinum<br />
|SDHC<br />
|16<br />
|10<br />
|<br />
|Does not boot with Raspbian Wheezy 2012-09-12<br />
|Palto 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDXC<br />
|64<br />
|10<br />
|<br />
|<br />
|Datafreak 30 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|SDXC<br />
|128<br />
|10<br />
|<br />
|man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2 Tested with BerryTerminal, NOOBS, OpenELEC, Raspbian and Raspbmc<br />
|Ienny 25 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Platinum<br />
|microSDHC<br />
|16<br />
|6<br />
|<br />
|<br />
|gecko16300 24 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Play.com<br />
|SDHC<br />
|4<br />
|6<br />
|S4E3CD04GEFAA 0907090121106<br />
|<br />
|JoeDaStudd 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SD<br />
|2<br />
|?<br />
|SD-M02G<br />
|<br />
|Ewindich 24 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|4<br />
|4<br />
|<br />
|<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|4<br />
|4<br />
|Optima (SD-K04G 0834TT1297Y)<br />
|<br />
|Weston 20 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Premium (Toshiba SD-K08G)<br />
| Works with 2014-01-07-wheezy-raspbian<br />
|PotOfJava 08 Feb 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Optima 120 HD SD-K08G 0928 WF3673<br />
|mmc -110 errors at init time on 12 Jun 2012<br />
|Zoward 12 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|4<br />
|Premium<br />
|mmc - mmc0: timeout waiting for hardware interrupt<br />
|Davidgyoung 21 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|<br />
|Threedaymonk 5 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|8<br />
|6<br />
|P-SDHC8G6-EFS2<br />
|Raspian wheezy: mmc0 timed out; OpenELEC 3.2.4 not working<br />
|Gkoper 21 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|8<br />
|10<br />
|P-SDHC8G10-GE<br />
|1 - Tested with 2013-02-09-wheezy. 2 - On Mac, dd to image did not work, but SD Card Builder did. Wheezy read and write right at about 20MBps. After booting, I installed several packages - all fine. After that, I installed RetroPie. That took about 15 hours to download and compile - zero errors.<br />
|1 - Zambon 9 Mar 2013, 2 - RicM July 17 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|16<br />
|4<br />
| <br />
|Unstable results with Raspian Wheezy (Sporadic failed booting - "Timeout waiting for hardware interrupt"<br />
|DBlessing 12 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|16<br />
|10<br />
|P-SDHC16G10-GE, P-SDHC16G10-EF, Pro-Elite P-SDHC16U10-30-GE<br />
|Works with Wheezy, does not work with Squeeze (mmc0: timeout...), Arch (no boot) (Joshdev), or Fedora Remix. Works with Raspbmc (Sp00l)<br />
|Jecxjo 9 Jun 2012, Joshdev 22 Jun 2012, Sp00l 21 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|16<br />
|10<br />
|P-SDU16G10-GE<br />
|man:0x000028 oem:0x4245 name:SDU16 hwrev:0x1 fwrev:0x0 <br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/PNY-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|P-SDHC32G10-GE<br />
|Works with Arch 2012-09-18 and Raspbian 2012-12-16<br />
|Derekivey 29 Dec 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|P-SDH32U1H-GES3 Elite Performance<br />
|Happily banging away for over a month now; Raspbian Linux 3.6.11+ #456 PREEMPT armv6l system v,3.3.3<br />
|Jerasmussen 12 Aug 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|Professional (P-SDHC32G10-EF)<br />
|(mmc0 timeout with Debian, error -84 whilst initialising sd card with Fedora and QtonPi. Arch seems to work, gets to the login prompt)<br />
|Optim4l 9 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDHC<br />
|32<br />
|10<br />
|Pro<br />
|Debian installation worked, [brand new] Card died a few minutes later with mmc0 timeouts, during apt-get upgrade. Never got it to work again on any system<br />
|Gryzor 10 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDXC<br />
|128<br />
|10<br />
|Model P-SDX128U1H-GE<br />
|No issues observed. Used dd on linux to write raspbian image, and rpi autoresized on first boot without problems<br />
|kansky 6 Mar 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PNY<br />
|SDXC<br />
|128<br />
|10<br />
|P-SDX128U1H-GE<br />
|man:0x000003 oem:0x5344 name:SD064 hwrev:0x3 fwrev:0x0<br />
Fails under heavy write load with "mmc0: Controller never released inhibit bit(s)<br />
mmc0: Timeout waiting for hardware interrupt". Works perfectly in USB card adapter.<br />
|whitslack 25 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|SDXC<br />
|256<br />
|10<br />
|Model P-SDX256U1H-GE <br />
|man:0x000028 oem:0x4245 name:SD256 hwrev:0x0 fwrev:0x2 - Works with RaspBMC 2014-11-24 Release<br />
|mnejman 19 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with adapter<br />
|Zulucat 21 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|with adapter<br />
|Zulucat 6 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|16<br />
|10<br />
|P-SDU16GU190-GE<br />
|tested with OpenELEC Raspberry Pi 2 Model B<br />
|riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|32<br />
|4<br />
|P-SDU32G4-GE<br />
|tested with B+<br />
|krakrjak 2 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PNY<br />
|microSDHC<br />
|32<br />
|10<br />
|<br />
|with AdaFruit adapter<br />
|Wibble 22 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Polaroid<br />
|SDHC<br />
|16<br />
|10<br />
|P-SDHC16GB10-EFPOL<br />
|mmc0: timeout waiting for hardware interrupt on debian6-19-04-2012<br />
|Jamesnine 28 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PQI<br />
|SDHC<br />
|8<br />
|6<br />
|<br />
|Works with official debian6-19-04-2012<br />
|Remick 12 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|PRETEC<br />
|SDHC<br />
|8<br />
|10<br />
|8DK52-122ME<br />
|<br />
|ScorpAl 19 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|PRETEC<br />
|SDHC<br />
|8<br />
|10<br />
|233x (PC10SDHC08G)<br />
|mmc0: timeout waiting for hardware interrupt, Sometimes does not boot, kernel panic<br />
|Petacz 8 Aug 2012, DarkKnightCZ 23 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|promaster.com<br />
|SDHC<br />
|8<br />
|10<br />
|<br />
|man:0x000027 oem:0x5048 name:SD08G hwrev:0x3 fwrev:0x0<br />
|Douglas W. Jones Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Reekin<br />
|SD<br />
|4<br />
|?<br />
|<br />
|doesn't boot<br />
|Nicobsa 11 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Genocho 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|?<br />
|<br />
|<br />
|Genocho 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|4<br />
|MB-SS4GA MB-SS4GA/EU <br />
|works with 2014-01-07-wheezy-raspbian<br />
|Markus 24 Feb 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung<br />
|SDHC<br />
|4<br />
|4<br />
|MB-SS4G MBSS4GMBDDBA-DD<br />
|doesn't boot with 2012-07-15-wheezy-raspbian; OK light partially lit<br />
|Doctoruseful 19 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|8<br />
|6<br />
|MB-SS8GAEU<br />
|<br />
|Dakaix 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|8<br />
|10<br />
|MB-MP8GA, MB-SP8GA/EU, MB-SP8GA/AM<br />
|Works with latest firmware (3.12.25+ #701) and some older Raspbian. On Raspbian 2014-06-20 fails when " Mounting local filesystems... mmc0: Timeout waiting for hardware interrupt - cmd12 ".<br />
Solution: Download [https://github.com/raspberrypi/firmware/blob/master/boot/kernel.img latest firmware] and overwrite the original on the BOOT partition.<br />
|Garrocha 19 May 2012,<br />
Fridata 1 August 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|6<br />
|MB-SSAGAEU<br />
|<br />
|Dakaix 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|6<br />
|MB-SSAGB/EU<br />
|<br />
|leon.anavi 26 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SGAGB (UHS-I PRO)<br />
|<br />
|miljenko 30 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SPAGA / MB-SPAGAEU<br />
|<br />
|Optim4l 11 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|16<br />
|10<br />
|MB-SPAGC<br />
|<br />
|djayor 9 May 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|32<br />
|6<br />
|MB-SSBGBFFP<br />
|<br />
|Xerxes 02 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|SDHC<br />
|32<br />
|10<br />
|MB-SSBGA, MBSSBGVEOBGA-SH<br />
|OK with Debian Wheezy. debian6-19-04-2012: mmc0: timeout waiting for hardware interrupt<br />
|Alkarex 11 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|4<br />
|6<br />
|MB-MS04D<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Raspberry B+ 2014-12-24-wheezy-raspbian<br />
|c 21 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|8<br />
|6<br />
|MMAGR08GUDCA-DB, MB-MS08DA<br />
|<br />
|Ewindich 24 Jul 2012 Felon 21 Jully 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MPAGC (MB-MPAGAEU)<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br />
|Olf 19 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16DA/EU<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/Samsung-Class10.html Details]<br />
|FastEddie 10 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MSBGAEU<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 - works with 2013-12-20-wheezy-raspbian.zip, Kernel 3.10<br />
|Johannes 24 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung<br />
|microSDHC<br />
|64<br />
|10<br />
|MB-MGCGBA/AM<br />
|Comes with a SD adapter. Installed 2014-01-07 Raspbian Wheezy, works perfectly!<br />
|PatriotInAKilt 20 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16D<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Tested on B+ model with 2014-12-24-wheezy-raspbian - Runs apt-get update without a problem - Raspberry Pi 2 model B, corruption if ext3/4, no problem with f2fs for two weeks <br />
|c 22 Jan 2015 - manolonte 5 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MP16DA/EU<br />
|Tested on B+ model - Runs Raspbian and Xbian without a problem with over 48 hours of uptime<br />
|Jack 14 Nov 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10 UHS-1<br />
|MB-MP32DU2/EU (w/ USB2.0 adapter)<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 - works well with Raspbian 2014-12-24 and Asterisk 2014-07-31 images. Max. tested speed with SD cards adapter on PC: writing 20.3 MByte/s, reading 35.4 MByte/s.<br />
|Carriba, 29 December 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MP32D<br />
|Tested on B+ with 2015-02-16-raspbian-wheezy and FreeBSD 11 CURRENT on medium overclock settings for 3 days without problems<br />
|Herculesxe5, 4 February 2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung EVO<br />
|microSDHC<br />
|32<br />
|10<br />
|MB-MP32DA/AM<br />
|Tested on B+ model - no adapter needed as it take microSD. Can install 2014-06-20 Raspbian image and boot OK. But afterwards, running sudo apt-get upgrade caused SD corruption. Tested with 2 cards, both exhibited the same problem.<br />
|Striders 24 Aug 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Samsung EVO<br />
|microSDHC<br />
|8<br />
|10<br />
|MB-MP08D/EU <br />
|Tested on rpi2, First boot OK then overclock to 900Mhz, sync some files and won't able to reboot. Put a fresh raspian then and mmc errors hardware everywhere while booting. <br />
|H4h 14 feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDHC<br />
|8<br />
|10<br />
|MB-MP08D<br />
|Tested on Raspberry Pi 2, overclocked to 900Mhz, initially stress tested for 24h (CPU with heatsink, temp recorded max at 60C), passed the [[RPiconfig#Overclock_stability_test|Overclock Stability Test]]<br />
|eNur 29 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDXC<br />
|64<br />
|10<br />
|MB-MP64D<br />
|Would not boot from standard Noobs - could not see image. Tested on B+.<br />
However, used stand alone Raspbian image file and used 'Partition Wizard' (this method - http://wiiudaily.com/2014/03/format-high-capacity-card-for-3ds/ )to force FAT32 and the Pi boots no problem into Raspbian on the 64GB card. Using df reports 56GB available free space after expanding file system. Seems to create a small FAT32 partition that enables booting. Still working after update, upgrade and Rpi update. After trial using Partition Wizard in the above method can confirm Pi will not boot after 'noobs' install so recommend using Win32 Disk Imager and a stand alone OS .img file after using partition wizard for anybody having problems. I have only tested Raspbian Wheezy and no other OS. *Note* any SD card genuinely above 32GB will be formatted exFAT using standard methods and the Pi requires a FAT32 system to read at boot or it fails. <br />
|Prod 26 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung EVO<br />
|microSDXC<br />
|64<br />
|10<br />
|MB-MP64DA/AM<br />
|Appears that the Pi has difficulty booting a 64GiB SDXC card that's formatted for exFAT. This card will NOT work with default settings (1/23/2015, Model B+). Workaround: download a valid image file -- not NOOBS, it must be an image. Then, use a utility such as dd or Win32DiskImager to copy the image directly to your device. This forces a small enough FAT32 partition that the RasPi will be able to read and boot. Confirmed that the "Expand Filesystem" option for Raspian still works after reboot<br />
|Phaerus, 2015-01-23<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung PRO<br />
|microSDHC<br />
|16<br />
|10<br />
|MB-MGAGB<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 Tested on B+ model. 2014-12-24-wheezy-raspbian<br />
|c 22 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Samsung PRO<br />
|microSDHC<br />
|32<br />
|10 UHS-I<br />
|MB-MG32DA<br />
|Works perfectly on RPi 2 Model B with RasPlex 0.5.1<br />
|biltong 12 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|<br />
|Extreme III (BE0715105083B)<br />
|Dscott 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|<br />
|SanDisk for Wii<br />
|Stevepdp 18 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|BE0916214253D<br />
|<br />
|Mate12345 9 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SD<br />
|2<br />
|?<br />
|Extreme III (BE0722702998D)<br />
|(man:0x000003 oem:0x5344 name:SD02G hwrev:0x8 fwrev:0x0) - tested with Raspbian (build 2012-07-15) and Raspbmc installer (build 2012-07-13)<br />
|Boandlkramer 5 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|2<br />
|BE0816113150D<br />
|writes at 3.5 Mb/s<br />
|Elatllat 22 Dec 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|4<br />
|Ultra<br />
|15 MB/s<br />
|Md84419 24 Sept 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|4<br />
|Ultra II, BE0719111366D<br />
|<br />
|Md84419 5 Nov 2011, Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SD<br />
|2<br />
|6<br />
|Extreme III (BE0804212046D)<br />
|20 MB/s<br />
|Nooitaf 20 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|2<br />
|?<br />
|Ultra II BE0828713280D (15 MB/s)<br />
|<br />
|Oostenvr 4 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|BH0820113475D<br />
|Tested with RPITC (Based on Raspbian Wheezy)<br />
|Rendyair 11 Sep 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|<br />
|Debian and xbmc boot, but fedora gets a lot of mmc0 note long write sync errors and then hc_xfer_timeout errors at the login prompt<br />
|Optim4l 10 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|2<br />
|8H825413279G "Limited Edition"<br />
|Error -110 whilst initialising sd card<br />
|Jezmck 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|SDSDB-004G-B35, BH1210821913G, SDSDB-004G-BT35<br />
|<br />
|Md84419 6 May 2012, Nicobsa 11 Jul 2012, Ingestre 12 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra II<br />
|<br />
|Britaniola 22 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|BH1030216016G, BH1031116016G<br />
|Doesn't boot<br />
|SquallStrife 15 May 2012, Vk2amv 9 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra (BH1028516076D)<br />
|Intermitant booting ( 1/50 power on ), random timeout messages when it does boot<br />
|Russell 26 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|4<br />
|Ultra (15MB/s) (SDSDH-004G-U46)<br />
|won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III (30 MB/s)<br />
|works with 2012-10-28-wheezy-raspbian<br />
|JeffS 11 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Ultra SDSDH-004G-U46 - BH1136121837G, BH1130521822D, BH1200421822D (30MB/s)<br />
|<br />
|Selsinork 20 Apr 2012 / Alex347 5 May 2012 / Jjuhl 26 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III C6 (BH0822411730D)<br />
|<br />
|Cmcr651 7 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|6<br />
|Extreme III (30 MB/s) (BH0822712362G)<br />
|<br />
|Jezmck 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (BH10297143382G)<br />
|<br />
|Wrdx 19 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (SDSDX-004G-X46)<br />
|Works with RasPlex 0.3.1<br />
|Bellagio 15 Nov 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|4<br />
|10<br />
|Extreme (SDSDX-004G-X46)<br />
|30 MB/s HD Video - Doesn't boot - Works with new kernel.img and start.elf (Paaland), not working with new kernel.img and start.elf 17-06-2012 or "wheezy"-beta (MrF)<br />
|Paaland 21 May 2012, MrF 19 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|writes at ~1.5MB/s<br />
|Ms705 30 Mar 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|Ultra BI1024716014G<br />
|labelled as 15MB/s<br />
|PhilH 3 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB-008G-B35S / SDSDB-008G-B35<br />
|Raspbian “wheezy”: used expand_rootfs option of sudo raspi-config command to make all 8GB available. <br />
|Swehner Jan 2013, Baji Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB-008GBQ35 / 80-56-12024-008G<br />
|Tested OK with Retro Pie<br />
|HBG 22 AUG 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|4<br />
|SDSDB3-008G-A16BJ / BJ's 3-pack<br />
|Tested OK with RISC OS<br />
|Lanulos 11 Sep 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra SDSDH-008G-U46 / BI1131222083D, BI11321422083D (20 MB/s) & SDSDH-008G-T11 (30MB/s) & SDSDH2-008G-AC11<br />
|SDSDH2-008G-AC11 requires updated Squeeze or Wheezy beta (Jim Manley)<br />
|Dakaix 24 Apr 2012, Crox 23 Jun 2012, Jim Manley 27 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Extreme (BI1101116253G)<br />
|<br />
|Alex347 5 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra SDSDH-008G-U46 (BI1201421964G / BI1201221964G / BI1131222083D), SDSRH-008G-A11 & SDSDH-008G-T11 (30 MB/s)<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt) debian6-19-04-2012<br />
|Trebor27 15 Apr 2012 / Russell 26 Apr 2012 / ChuckHunky 8 May 2012/ Ryantm 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (BI11017514367G / BI1130916254G / B11209116254G / SDSDX-008G-X46/BI1218822414G)<br />
|May need updated bootcode.bin (BELzEBUB), Confirmed on Debian Squeeze 2012-04-19 and Arch Linux 2012-06-13 (Arces), works with Raspian R3 (Histvan)<br />
|Timer 16 May 2012, BELzEBUB 30 Jun 2012, Arces 9 Jul 2012, Histvan 14 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (SDSDX-008G-X46/BI1111816252D)<br />
|tested on 2013-02-09 Raspian and Rasplex 0.1.37<br />
|Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme Pro (SDSDXPA-008G-X46)<br />
|(95MB/s UHS-I) - Works with stock 2012-07-15-wheezy-raspbian<br />
|Incyi 28 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme Pro<br />
|Works with stock Arch Linux 2013-05-01<br />
|Perchrh 28 Apr 2012, Tiwipewo 27 May 2012, Perchrh 17 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-U46 (30 MB/s)<br />
|Works with debian6-19-04-2012 or raspbian images but not with OpenELEC r11212 (MrF). Works with OpenELEC r11493 (Vishnu vijay); works with 2013-09-25-wheezy-raspbian man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0 (tswaehn)<br />
|MrF 6 Jun 2012, Vishnu vijay 28 Jul 2012, tswaehn 07 dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-A11 (30 MB/s)<br />
|Works with raspbian images (blitzkrieg).<br />
|Blitzkrieg 26 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-T11 (30 MB/s)<br />
|Works with Arch Linux 20130813 (L. Snow).<br />
|L. Snow 27 Dec 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Ultra SDSDU-008G-UQ46 (30 MB/s)<br />
|Works with Raspbian (wheezy) 3.10.21+ (Read ~18.6MB/s Write ~14.5MB/s) man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|Sauce 3 Dec 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme BI1108716254G, BI110209116254G<br />
|<br />
|Dscott 23 Apr 2012, Max 31 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|8<br />
|10<br />
|Extreme (BI1200916252D/SDSDX-008G-X46), BI1201416254G<br />
|Doesn't work with debian6-19-04-2012.img and with replacement kernel.img and start.elf (Weston). Doesn't work with Debian Wheezy beta (2012-06-18)(Halton). Doesn't work with Arch Linux 13/06/2012 (Madhur)<br />
|Weston 20 May 2012, Halton 8 Jun 2012, Madhur 27 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-B35<br />
|<br />
|NickstaDB 17 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-A11<br />
|Tested on OpenELEC, Arch, and NOOBS<br />
|funkeywoookey 9 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-FFP<br />
|Attempted with Ubuntu dd.<br />
|[[User:GKFX|GKFX]] ([[User talk:GKFX|talk]]) 18:46, 31 December 2014 (UTC)<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|4<br />
|SDSDB-016G-AFFP<br />
|Attempted with Windows, Linux dd, and Fedora ARM installer. RPi would not load and Linux could not mount after image written to card.<br><br />
''Note: I fixed the Linux error on the presumably similar SDSDB-016G-FFP after [http://www.raspberrypi.org/documentation/installation/installing-images/linux.md remembering to <code>umount</code>]. [[User:GKFX|GKFX]] ([[User talk:GKFX|talk]])''<br />
|mwolfgang 19 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra (30MB/s) (BL1133921933G)<br />
|Works with OpenELEC r11324<br />
|Reckoner 17 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra (BL1202021933G)<br />
|<br />
|Dscott 23 Apr 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Ultra I (BL1205921933G)<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt)<br />
|SnarlingFox 10 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|6<br />
|Extreme<br />
|(man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0), boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme (45MB/s U1)(BL1203322025G), (30MB/s HD Video)(SDSDX3-016G-X46), (45MB/s U1)(BL1203322025G)<br />
|Doesn't work with debian6-19-04-2012 image, but does work with 2012-06-18-wheezy-beta.img and updated firmware (tested 2012-07-02). Danbowes: Working with latest RaspBMC image (tested 12/09/2012)<br />
|Flatline403 12 May 2012, Dkleeman 13 Jun 2012, Zbyszek 2 Jul 2012, Danbowes 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|SDSDQUIP-016G-A46<br />
|man:0x000003 oem:0x5344 name:SL16G hwrev:0x8 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/SanDisk-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Extreme PLUS SDSDXS-032G-A46 (80MB/s UHS-I)<br />
|RPi Model B+ - No issues or errors encountered, using RetroPie 2.3 (man:0x000003 oem:0x5344 name:SE32G hwrev:0x8 fwrev:0x0)<br />
|arcooke 21 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme Pro SDSDXPA-016G-A75 (95MB/s UHS-I)<br />
|Doesn't work with stock debian6-19-04-2012 image, but does work with freshly compiled kernel<br />
|AXon 26 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Ultra (30MB/s UHS-I) (SDSDU-016G-U46) (SDSDU-016G-U46S)<br />
|Works with debian6-19-04-2012 (Misox12). Kernel Panic with debian6-19-04-2012. Worked fine with Wheezy image (Casestudies). Works fine with Raspbian Wheezy 2013-02-09, man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0 (Fraoch). <br />
|Misox12 30 May 2012, Casestudies 30 Jun 2012, Fraoch 25 March 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|SDSDQUAN-016G-G4A<br />
|Works great with Raspbian [2015-02-16]; man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|john Pi-day 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Ultra microSDHC I UHS-I<br />
|man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0. Works again since raspberrypi-firmware 20130116 in archlinux-arm. write 6.8 MB/s, read 21.0 MB/s<br />
|fiodschi, 19 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|16<br />
|10<br />
|Extreme SDHC (45MB/s UHS-I) (SDSDX-016G-X46)<br />
|Works with Raspbian “wheezy” and works with OpenELEC<br />
|Fazdogg 08 Jan 2013; Shadyeglenn 14 Feb 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|4<br />
|<br />
|<br />
|Daviewales 30 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|6<br />
|<br />
|<br />
|Helpme1986 22 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Extreme (45MB/s UHS-I) (SDSDX-032G-X46)<br />
|works with arch-04-29-image and latest firmware (booting problems without firmware update) / works with debian wheezy kernel 3.2.27+ (jLo)<br />
|Malhelo 8 Jun 2012 / jLo 2 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Ultra (30MB/s UHS-I) (SDSDU-032G-U46)<br />
|Works with debian6-19-04-2012<br />
Works with 2014-01-07-wheezy-raspbian<br /><br />
Works with wheezy-raspbian 22 May 2014<br />
man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0<br />
|Pnppl 11 Jun 2012<br />
Sheegoth on 12 Feb 2014<br />
GrimFaker 22 May 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDHC<br />
|32<br />
|10<br />
|Elevate (30 MB/s) SDSDU-032G-T11<br />
|Works with 2012-12-16-wheezy-raspbian<br />
|bderry71 08 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Extreme(SDSDQXN-064G-G46A)<br />
|UHS-I: works with 2015-02-16-wheezy-raspbian<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Extreme (SDSDX-064G-X46)<br />
|45 MB/s UHS-I: works with 2012-07-15-wheezy-raspbian<br />
|Cracki 10 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra (SDSDQUAN-064G-G4A)<br />
|2015-02-16-wheezy-raspbian works well.<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra (SDSDU-064G-U46)<br />
|2014-03-15-wheezy-raspbian crashed every week with reading errors. Card switched to readonly after one month. The same happened with a replacement card.<br />
|hypnotoad 30 mar 14<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|SDXC<br />
|64<br />
|10<br />
|Ultra SDXC UHS-I FFP (3A114807)<br />
|<br />
|Zagblorg 26 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|SDXC<br />
|128<br />
|10<br />
|Extreme (45MB/s UHS-I)<br />
|Don't work (Tested on Two)<br />
|OTHMAN 2014 02 10<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|miniSDHC<br />
|2<br />
|<br />
|Ultra II miniSD. BE07107FJE<br />
|Doesn't boot<br />
|Pe7er 18 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|2<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Rew 24 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Sleepy 1 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|4<br />
|6<br />
|Mobile Ultra<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt) - Jens Pedersen / (tried 15-06-2012 with kernel 19-04-2012) error -84 transferring data, kernel panic: no init found - Wieltje<br />
|Jens Pedersen 8 May 2012, Wieltje 15 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|2<br />
|<br />
|<br />
|Fjen 12 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|4<br />
|<br />
|with SanDisk microSD to SD adapter<br />
|Md84419 21 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|4<br />
|SDSDQM-008G-B35<br />
|man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|jonasbits 12 Sept 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|6<br />
|Mobile Ultra (SDSDQY-008G-U46A)<br />
|working with the latest firmware, won`t reboot when it`s hot<br />
|Sorinm 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Ultra (SDSDQU-008G-U46) (30MB/s UHS-I)<br />
|tested and working on Raspbian wheezy (and RaspBMC)<br />
|Pepindur 11 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Mobile Ultra (48MB/s UHS-I) (SDSDQUA-008G-U46A)<br />
|working with the latest firmware<br />
|pravin_tavagad 24 Nov 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|SDSDQUA-008G-U46<br />
|doesnt work with raspbian,arch,noob-lite man:0x000015 oem:0x0100 name:VYL00M hwrev:0x0 fwrev:0x0<br />
|Freemind 12 Sep 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|4<br />
|<br />
|(man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Mobile Ultra (30MB/s UHS-I) (SDSDQUA-016G-U46A)<br />
|working with the latest firmware; Works with OpenELEC 5.0.1 on Raspberry Pi 2 Model B.<br />
|Mengineer 25 Aug 2012, Shadyeglenn 12 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|8<br />
|10<br />
|Ultra (SDSDQUAN-008G-G4A)<br />
|man:0x000003 oem:0x5344 name:SL08G hwrev:0x8 fwrev:0x0 Model B+ 2014-12-24-wheezy-raspbian<br />
|c 22 Jan 2015, Jon 3 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sandisk<br />
|microSDHC<br />
|16<br />
|?<br />
|Sandisk Extreme <br />
|man:0x000003 oem:0x5344 name:SE16G hwrev:0x8 fwrev:0x0. write 18.2 MB/s, read 18.8 MB/s Works with 2014-09-09-wheezy-raspbian on Model B+ <br />
|03 Dec 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|SanDisk<br />
|microSDHC<br />
|16<br />
|10<br />
|Extreme Pro (95MB/s UHS-I) (SDSDQXP-016G-AFFP)<br />
|Installs and boots but random umounts occur and requires reboots, no work around found.<br />
|sdn3rd 15 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|4<br />
|<br />
|<br />
|Sherman 19 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQU-032G-U46A<br />
|archlinux-hf-2013-02-11<br />
|pAIgn10 6 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQUAN-032G-C4A Ultra SDHC UHS-I<br />
|RPi ModelB, raspbian wheezy 3.18.5 2015-01-30<br />
|Developer 2015-02-12<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDHC<br />
|32<br />
|10<br />
|SDSDQXN-032G-FFPA<br />
|RPi Model B+, raspbian-wheezy-2014-12-24<br />
man:0x000003 oem:0x5344 hwrev:0x8 fwrev:0x0<br />
|rico 31 Dec 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDXC<br />
|64<br />
|6<br />
|SDSDQY-064G-A11A<br />
|boots up much more consistently with latest firmware<br />
|LastSilmaril 23 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SanDisk<br />
|microSDXC<br />
|128<br />
|10<br />
|Write: 10.6 MB/s, Read: 18.6 MB/s, man:0x000003 oem:0x5344 name:SL128 hwrev:0x8 fwrev:0x0<br />
|Works with Raspbian on Model B+<br />
|Mstu 23 Nov 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|SCT<br />
|SDXC<br />
|64<br />
|10<br />
|STC SM649A-130125<br />
|2013-02-09-wheezy-raspbian.img, booted cleanly, installed LibreOffice OK<br />
|Lanulos 29 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|8<br />
|10<br />
|SP008GBSDH010V10<br />
|Works fine 2012-12-16-wheezy-raspbian.img - Tested 14/01/2013<br />
|Thenix 14 Jan 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Silicon Power<br />
|SDHC<br />
|8<br />
|10<br />
|SP008GBSDH010V10<br />
|Boots kernel but won't run init (mmc timeout waiting for interrupt ) - Tested 20/11/2012, 2012-10-28-wheezy-raspbian.img with Nov 20 kernel<br />
|Xthexder 21 Nov 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|16<br />
|6<br />
|SP016GBSDH006V10<br />
|<br />
|Valery 05 Apr 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|SDHC<br />
|16<br />
|10<br />
|SP016GBSDH010V10<br />
|<br />
|Xthexder 21 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Silicon Power<br />
|SDHC<br />
|32<br />
|6<br />
|LS2N732GQON03ASP<br />
|boots debian6-19-04-2012.img, but frequent slow response / system hangs<br />
|Michthom 21 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|4<br />
|6<br />
|SP004GBSTH006V10-SP<br />
|<br />
|Csgabe 19 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|8<br />
|10<br />
|S608G1202<br />
|<br />
|Blutme 17 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|MicroSDHC<br />
|8<br />
|10<br />
|SP008GBSTH010V10SP<br />
| Read:15.7 MB/s Write:5.5 MB/s, (man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2)<br />
|Thu 01 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Silicon Power<br />
|microSDHC<br />
|16<br />
|10<br />
|SP016GBSDH010V10<br />
|<br />
|Jamesnine 10 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|4<br />
|4<br />
|SF-4B4, SF-4N4<br />
|(Write 6MB/s, Read 20MB/s)<br />
|Krischaplin 7 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|4<br />
|10<br />
|UHS-1 40MB/s SF-4UY man:0x000027 oem:0x5048 name:SD04G hwrev:0x3 fwrev:0x0 <br />
|Perfect with Raspbian. With openELEC I get warnings in the logs (mmc0: DMA IRQ 6 ignored - results were reset - mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it) (Write 10,3MB/s, Read 18,8MB/s)<br />
|Knopfler19 20 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|4<br />
|<br />
|(Write 11.8MB/s, Read 17.4MB/s)<br />
|Slabua 9 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-1 SF8UX<br />
|Write 17.2 MB/s, Read 20.8 MB/s, Raspbian works while image copied using windows<br />
|Regi24 29 Dec 2012, Hariram April 12, 2013, Hareesh G S June 6, 2013 (Openelec Image)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-1 90MB/s SF-8UX man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x0 <br />
|Perfect with Raspbian. With openELEC I get warnings in the logs (mmc0: DMA IRQ 6 ignored - results were reset - mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it) (Write 16,9 MB/s, Read 21,1 MB/s)<br />
|Knopfler19 20 Jun 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|8<br />
|10<br />
|UHS-I SF-8UY/TQ1 man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2 <br />
|Works fine with Raspbian. (Write 13.37 MB/s, Read 20.93 MB/s)<br />
|c5jirzex52xx, 18 Nov 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|16<br />
|10<br />
|UHS-1<br />
|Works well with Raspian.<br />
|Bafeigum 23 Aug 2013; DBlessing 12 Mar 2014 (Confirmed)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32NX/TQ<br />
|Max read speed of ~94 MB/s, min write speed of ~10 MB/s) - Works with archlinuxarm-29-04-2012 dd image with latest firmware update (as of 10-06-2012)<br />
|Chbg 13 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32UY/TQ1, SF-32UY/TQMN (40 MB/s)<br />
|Works with archlinux-hf-2013-02-11 (also after full update) - as of 04-08-2013)<br />
|Tigran 09 April 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|SDHC<br />
|32<br />
|10<br />
|SF-32UY/TQ1, UHS-I (40 MB/s)<br />
|Works with Raspbmc, OpenELEC (Frodo and Gotham test builds), and NOOBS.<br />
Tested throughput:<br />
Seq Read: 87.2MB/sec<br />
Seq Write: 20.4MB/sec<br />
Random Read: 78.3MB/sec<br />
Random Write: 19.9MB/sec<br />
|JoeSchmuck 13 July 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|Micro SDHC<br />
|32<br />
|10<br />
|SR32UYA/TQMN<br />
|<br />
|Spec 8 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|Micro SDXC<br />
|64<br />
|10<br />
|SR-64UY<br />
|2015-02-16-raspbian<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Strontium<br />
|SDHC<br />
|8<br />
|10<br />
|SD-T08G 1045 US6923 G (White Shell - SKU 8 886450 703492)<br />
|<br />
|Ssb 25 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Super Talent<br />
|SDHC<br />
|32<br />
|10<br />
|SDHC32-C10 SKU: 116-557-001<br />
|works with Raspbmc RC4 and 2012-07-15-wheezy-raspbian<br />
|Drroller 14 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|microSDHC<br />
|4<br />
|4<br />
|<br />
|with TakeMS adapter<br />
|Delboy0 31 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|SDHC<br />
|16<br />
|6<br />
|<br />
|Tested on raspbmc - works with no problems<br />
|swidzi 25 October 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TakeMS<br />
|SDXC<br />
|64<br />
|10<br />
|<br />
|overclock turbo model B works<br />
|select 02 June 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|4<br />
|4<br />
|1008WW5261B<br />
|<br />
|Pluggster 17 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|2 x 4<br />
|4<br />
|80-56-10275-004G<br />
|Debian works, mmc0 errors when booting Fedora<br />
|Melikescheese 27 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1113<br />
|Works with Debian Wheezy (2012-06-18 beta)<br />
|Dcuk 26 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|TDK<br />
|SDHC<br />
|4<br />
|6<br />
|S404G1041, S404G1046<br />
|end May 2012, new kernel.img and start.elf, won't run init. 4 Jun 2012, debian6-19-04-2012.img, replacement kernel.img and start.elf from github. Got Error -84 and Kernel panic - not syncing: No init found<br />
|Ceptimus 2 Jun 2012, Norbini 4 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|microSDHC<br />
|4<br />
|4<br />
|with Adapter (80-56-10301-004G)<br />
|<br />
|Norbini 4 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TDK<br />
|microSDHC<br />
|8<br />
|10<br />
|<br />
|Works with Raspbian 2012-07-15<br />
|Backeby 20 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Team<br />
|MicroSDHC<br />
|32<br />
|10<br />
|<br />
|Raspberry Pi 2 Model B <br />
|Riverstyxxx 7 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|TOPRAM<br />
|SDHC<br />
|8<br />
|6<br />
|TRSD8GC6<br />
|Works with OpenELEC (Frodo and Gotham test builds), did not test on anything else yet.<br />
Tested throughput:<br />
Seq Read: 43.9MB/sec<br />
<br />
Seq Write: 18.8MB/sec<br />
Random Read: 41.8MB/sec<br />
Random Write: 17.6MB/sec<br />
|JoeSchmuck 13 July 2013<br />
|-<br />
<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|4<br />
|4<br />
|SD-K04G(1201 W12338 N) (labelled as Fujifilm SHDC 4GB class 4)<br />
|Tested with Raspbian 2013-11-18. Speed is 5MB/s write (1GB file) <br />
|captaindangeax 18 nov 2013<br />
|-<br />
<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|8<br />
|4<br />
|SD-K08G(1223 W17218 P)<br />
|Tested with Raspbian 2012-12-16. Speed is 4MB/s write<br />
|rendyair 16 Jan 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|8<br />
|10<br />
|PFS008U-1DCK (6/13)<br />
|Tested with Raspbian.<br />
|Rellermeyer 25 Sep 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|16<br />
|10<br />
|SD-T16G(1046 US7022 C)<br />
|<br />
|Yang 5 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|SDHC<br />
|32<br />
|10<br />
|SD-K032GR7AR30 (30MB/s)<br />
|Works with NOOBS.<br />
|OTHMAN 2014.02.14<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|4<br />
|4<br />
|SDC04G<br />
|with adapter - NOOBS v.1.3.4 cannot install the OS on the card but applying a OS image directly is working perfectly<br />
|elapdre 16 April 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|8<br />
|?<br />
|SD-C08GJ(BL3A)<br />
|with adapter<br />
|Jannis 15 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|8<br />
|4<br />
|PFM008U-1DAK<br />
|works with openelec<br />
|akschu 26 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|16<br />
|10<br />
|SD-C016UHS1BL5A<br />
|with adapter<br />
|wombalton 25 March 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|32<br />
|10<br />
|SD-C032UHS1BL5A<br />
|man:0x000002 oem:0x544d name:SA32G hwrev:0x1 fwrev:0x2 - Tested on A+ and B+<br />
|bpmurray 14 Jan 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Toshiba<br />
|microSDHC<br />
|64<br />
|10<br />
|SD-C064GR7AR30<br />
|Tested 2015-02-16-raspbian on Pi2<br />
|map7 02/03/2015<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SD<br />
|2<br />
|?<br />
|6451AG 2G O2DS1<br />
|<br />
|MaWe 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|4<br />
|TS4GSDHC4 - BH1130821915G<br />
| we've found these to work without any errors and offer reasonable performance<br />
|RasMyra 12 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|6<br />
|TS4GSDHC6<br />
|no problems (does not work with Raspbmc as of 1 Jun 2012 - 321liftoff)<br />
|LakesGeek 23 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|10<br />
|TS4GSDHC10<br />
|Works fine running Raspbian and OpenELEC. Tested various cards from different batches.<br />
|Kiwisol 27 Oct 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|4<br />
|10<br />
|TS4GSDHC10E, TS4GSDHC10<br />
|Corrupted when card image back up made<br />
mmc0: resetting ongoing cmd 25dma before 4096/4096 [1]/[1] complete<br />
mmc0: Timeout waiting for hardware interrupt - cmd12<br />
mmcblk0: error -110 sending stop comment, original cmd response 0x900, card status 0xe00<br />
|Mfg 3 Jun 2012, Thenix 14 Jan 2013, Fazz 04 Oct 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10E<br />
|man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0<br />
| jmarin 22 April 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|4<br />
|TS8GSDHC4<br />
|(man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0) - works with both Debian "squeezy" and Raspbian "wheezy" distributions (Hedj)<br />
|Attila.afra 25 Apr 2012, Hedj 24 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|6<br />
|TS8GSDHC6-P2 - MMBFG08GWACA-M6<br />
|~5.8 MB/s read/write following the Performance below<br />
|Md84419 5 Nov 2011<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10<br />
|<br />
|Selsinork 26 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDU1 UHC-I X300<br />
|Arch read/write 20,9/13,1 MB/s<br />
|30 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|8<br />
|10<br />
|TS8GSDHC10U1 UHC-I X600<br />
|Arch read/write 21,1/15 MB/s<br />
|30 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|4<br />
|TS16GSDHC4<br />
|Tested with Raspbian 2014-12-30<br />
|Fmondada 2 Jan 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|6<br />
|TS16GSDHC6<br />
|<br />
|Bullace 18 May 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 / TS16GSDHC10E<br />
|<br />
|Rew 18 Apr 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 / TS16GSDHC10E<br />
| Read:18.4 MB/s Write:12.1 MB/s (man:0x000074 oem:0x4a45 name:SDC hwrev:0x0 fwrev:0x2)<br />
|Sam2 01 Feb 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDU1<br />
| Read:18.4 MB/s Write:12.1 MB/s, (man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2)<br />
|Sam2 01 Feb 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10 9173BA-16G-09DS2<br />
| works<br />
|Epa 20130304. package had "83-3432 V5.1" behind it.<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10<br />
|TS16GSDHC10U1<br />
|Doesn't Boot, show that "kernel panic - not syncing attempted to kill init"<br />
|Khfung02 13 Sep 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|16<br />
|10 UHS-1<br />
|TS16GSDHC10U1<br />
|Works with Occidentals 0.2 from Adafruit, read and write about 15 MB/s, didn't test other versions.<br />
|aevh 18 Feb 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDHC<br />
|32<br />
|6<br />
|TS32GSDHC6-P2<br />
|Was not recognized by 1/2 rsp B, switched to read only after 1 year, man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|hypnotoad 30 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDHC<br />
|32<br />
|10<br />
|TS32GSDHC10, TS32GSDHC10E<br />
|<br />
|Vakya 29 May 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|SDXC<br />
|64<br />
|10<br />
|TS64GSDXC10<br />
| OK<br />
NOK - After one week it switched to readonly. The same happened with a replacement card.<br />
|Country 26 Jun 2012<br />
Trochim 4 Mar 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|SDXC<br />
|128<br />
|10 UHS-I<br />
|TS128GSDXC10U1<br />
|Works with openSUSE<br />
|petrmatula 8 Mar 2014<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|2<br />
|?<br />
|MMAGR02GUECA-MB<br />
|reads fine initially after image was written on a PC, gives mmc0 timeout errors reading back data after writing a large amount (in this case with 'pacman -Syu'). Still seems to work, but is *very* slow after this happens, even across reboots<br />
|Malvineous 16 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|8<br />
|10<br />
|TS8GUSDHC10<br />
|<br />
| Za Bullet 18 May 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|8<br />
|10<br />
|TS8GUSDU1<br />
|Works with 2014-06-20-wheezy-raspbian<br />
Works with RaspBMC in RPi Model B+<br />
|Elf98 15 Aug 2014<br />
javierrgz 3 Sep 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1<br />
|Raspberry Pi B+ Model (tested on OpenELEC,xbian, raspbmc, kali linux)<br />
|@xhark 05 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1<br />
|Works with 2014-06-20-wheezy-raspbian<br />
|Elf98 15 Aug 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|16<br />
|10<br />
|TS16GUSDU1E<br />
|man:0x000003 oem:0x5344 name:SL16G hwrev:0x8 fwrev:0x0<br /><br />
Tested on Pi 2 Model B with Raspbian via NOOBS 1.4; More [http://skippingpebbles.com/Pi/Transcend-Class10.html Details]<br />
|FastEddie 19 Mar 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|10<br />
|TS32GUSDU1<br />
|Works with 2013-02-09-wheezy-raspbian<br />
|Neurolit 15 Apr 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|?<br />
|TS32GUSDHC4<br />
|Doesn't boot<br />
|Piponazo 7 Aug 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Transcend<br />
|microSDHC<br />
|32<br />
|10<br />
|TS32GUSDHC10<br />
|(man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0), with microSD to SD adapter, boots, (mmc0: timeout waiting for hardware interrupt, followed by continuous I/O errors, timeouts, etc), 2013-02-09-wheezy-raspbian<br />
|Bernard Ladenthin 12 Mar 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Transcend<br />
|microSDXC<br />
|64<br />
|10<br />
|TS64GUSDU1E<br />
|Raspberry Pi B+ Model (tested with ARM Arch Linux)<br />
|fluxon 28 Oct 2014<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Traveller<br />
|SDHC<br />
|4<br />
|?<br />
|High Speed<br />
|Works with raspbian<br />
|Sega dude 28 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|UNIREX<br />
|microSDHC<br />
|32<br />
|UHS-I C10<br />
|UMW-325M<br />
|mmcblk0: read problems during boot [including "mmc0: controller never released inhibit bit(s)" ], corruption ensues. this with Raspbian 2015-02-16 on Raspberry Pi2 Model B<br />
|mmhere 18 Feb 2015<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|V-Gen<br />
|microSDHC<br />
|8<br />
|?<br />
|<br />
|No problems.(man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0). Tested with Raspbian Wheezy & Raspbmc<br />
|Rendyair 11 Sep 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Veho<br />
|SDHC<br />
|4<br />
|6<br />
|<br />
|<br />
|Spaaa 5 Jun 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Veho<br />
|SDHC<br />
|8<br />
|6<br />
|Ultra fast<br />
|(man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0) 7.8Mb/s. Slow but tested with Arch Linux<br />
|Johnlane 28 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|6<br />
|Go<br />
|tested with NOOBS 1.3.2 and Raspbian Wheezy 2013-09-25; mmc0: timeout waiting for hardware interrupt<br />
|marcel.kolaja 12 Dec, 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|43961<br />
|<br />
|Petacz 13 Aug 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|Premium<br />
|Tested with 2013-02-09 release of Raspbian Wheezy and Rasplex 0.1.37 - blue plastic version<br />
|Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|Premium PSF8GSDHC10-PC<br />
|Tested with September release of Raspbian and Debian Wheezy - both fail to boot with mmc errors, confirmed fail with this black plastic version (may 2013)<br />
|XQx 31 Oct 2012 , confirmed Jahislove 11 may 2013<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|8<br />
|10<br />
|43961<br />
|Raspbian - installs it but doesn't boot, repeatedly prints: 'timeout waiting for hardware interrupt'<br />
|Gkontadakis 31 Aug 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|4<br />
|44020<br />
|<br />
|Adelahunty 22 Nov 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|6<br />
|47178<br />
|Raspbian Pisces RC3 - boots, but after login: mmc timeout waiting for interrupt<br />
|Razzda 15 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|10<br />
|43962<br />
|<br />
|Klass 24 Jun 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|SDHC<br />
|16<br />
|10<br />
|13762<br />
|mmc timeout<br />
|Epa 20130304<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|SDHC<br />
|32<br />
|6<br />
|44032<br />
|<br />
|Jarip 14 Jul 2012<br />
|-<br />
|style='background-color:#c00;'| nok<br />
|Verbatim<br />
|microSDHC<br />
|8<br />
|10<br />
|44012<br />
|ArchLinux - boots, but after system update develops segmentation faults<br />
|John.glasson 29 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Verbatim<br />
|microSDHC<br />
|16<br />
|4<br />
|<br />
|Tested with 2013-02-09-wheezy-raspbian - works without any problem<br />
|J3rGuS 19 March 2013<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|SD<br />
|1<br />
|?<br />
|<br />
|Works with raspbmc, have not tested others<br />
|Sp00l 21 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|SD<br />
|2<br />
|?<br />
|<br />
|Works with raspbian, have not tested others<br />
|Sega dude 27 Jul 2012<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Walgreens Photo<br />
|microSDHC<br />
|16<br />
|10<br />
|<br />
|…testing on B+…<br />
|[[User:DisneyWizard|DisneyWizard]] ([[User talk:DisneyWizard|talk]]) 18:00, 10 January 2015 (UTC)<br />
|-<br />
|style='background-color:#0a0;'| ok<br />
|Sony<br />
|microSDXC<br />
|64<br />
|10<br />
|SR-64UYA<br />
|Works with Raspy 2 and Snappy Ubuntu<br />
|[[User:Ileo|Ileo]] ([[User talk:Ileo|talk]]) 20:10, 15 March 2015 (UTC)<br />
|}<br />
<br />
== Performance ==<br />
<br />
The following results have been reported by Users.<br />
<br />
=== Terminal Commands ===<br />
<br />
To obtain the results in the table, type the following lines at a command prompt. If you are running the GUI windows, open the Terminal application.<br />
<br />
The '''dd''' command is the Linux block copy command. It reads from the '''if=''' file, in the first case a block of zeros, and writes to the '''of=''' file, in the first case the file named test.tmp in your HOME directory (the ~/ means your HOME directory). The '''bs=''' gives the size of the data, and the '''count=''' gives the number of times this is repeated. '''sync''' ensures that the filesystem cache is flushed to have more realistic data. Please run it multiple times, one sample is not scientific enough.<br />
<br />
'''Write speed'''<br />
<br />
sync; dd if=/dev/zero of=~/test.tmp bs=500K count=1024<br />
<br />
'''Read speed'''<br />
<br />
sync; echo 3 | sudo tee /proc/sys/vm/drop_caches<br />
sync; time dd if=~/test.tmp of=/dev/null bs=500K count=1024<br />
<br />
'''Delete the temporary file'''<br />
<br />
rm ~/test.tmp<br />
<br />
'''Kernel version'''<br />
<br />
uname -a<br />
<br />
=== External Benchmarks ===<br />
<br />
* http://www2.sakoman.com/OMAP/microsd-card-perfomance-test-results.html<br />
* http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4076<br />
<br />
=== Is this reliable? ===<br />
<br />
SD cards are given a rating (Class) by the manufacturers; the higher the rating the quicker the card. SD cards are usually used in a camera. The camera usually writes a block of data (a picture), then writes another. The SD card is tuned for this type of use. When used in the Raspberry Pi the data is written and read a lot more frequently, and from differing locations on the card. This difference in use means the<br />
manufacturers rating may not be as applicable for the Raspberry Pi.<br />
<br />
=== SD card performance ===<br />
<br />
The table can be sorted using the triangles in the top row. Please add entries in the correct location, so that the initial sort is by Manufacturer, Size, Type and Class<br />
<br />
{| border="1" class="sortable"<br />
! SD Card !! Read (MB/s) !! Write (MB/s) !! class="unsortable" | Distro !! class="unsortable" | Kernel !! class="unsortable" | Notes<br />
|-<br />
|ADATA 8GB SDHC Class 10 (ASDH8GCL10-R) || 19.6 || 18.8 || 2012-08-04 Debian Wheezy "Raspbian" || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|ADATA 8GB SDHC Class 10 (ASDH8GCL10-R) || 18.2 || 12.4 || 2012-12-16 Debian Wheezy "Raspbian" || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux || <br />
|-<br />
|ADATA 16GB SDHC Class 10 || 19.5 || 16.9 || 2012-06-13 Arch Linux ARM || Linux alarmpi 3.2.27+ #60 PREEMPT Thu Aug 23 15:33:51 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|ADATA 16GB SDHC Class 10 || 17.8 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.10.24+ #610 PREEMPT Thu Dec 12 13:12:09 GMT 2013 armv6l GNU/Linux || man:0x00001d oem:0x4144 name:SD hwrev:0x1 fwrev:0x0<br />
|-<br />
| ADATA 16GB SDHC Class 10 (ASDH16GUICL10-R) || 18.5 || 9.9 || archlinux-hf-2013-11-14 || Linux alarmpi 3.10.25-1-ARCH #1 PREEMPT Mon Dec 23 16:07:25 MST 2013 armv6l GNU/Linux ||<br />
|-<br />
| ADATA 16GB SDHC Class 10 (ASDH16GUICL10-R) || 18.4 || 16.06 || 2014-01-07-wheezy-raspbian || Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux || Fresh install<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-R) || 18.6 || 12.3 || 2014-07-08-wheezy-raspbian || Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux || Fresh NOOBS install + apt-get upgrade<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-RA1) || 13.8 || 7.1 || 2014-12-24-wheezy-raspbian || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Fresh Raspbian install<br />
|-<br />
| ADATA 16GB SDHC Class 10 (AUSDH16GUICL10-RA1) || 18.8 || 9.3 || 2014-12-24-wheezy-raspbian || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Fresh Raspbian install + apt-get upgrade + reboot<br />
|-<br />
|ADATA 32GB SDHC Class 10 (ASDH32GCL10-R) || 20.1 || 6.4 || 2012-06-18-wheezy-beta || Linux raspberrypi 3.1.9+ #152 PREEMPT Fri Jul 6 18:47:16 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|AmazonBasics SDHC Class 10 8GB || 19.3 || 8.6 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|AmazonBasics SDHC Class 10 8GB || 17 || 9.4 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || Same board and card as above, slightly newer kernel.<br />
|-<br />
|Emtec SDHC 8GB class 10 (EKMSD8G150XHC) || 20.3 || 14.6 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux || Turbo mode = High (950/250/450MHz)<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 4.7 || 4.5 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #52 ||<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 11.3 || 5.4 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #101 || init_emmc_clock=200000000 in config.txt<br />
|-<br />
|Extrememory SDHC 16GB class 10 || 18.2 || 6.3 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ custom || kernel and firmware as of 17.06.2012, no extra option in config.txt<br />
|-<br />
|Extrememory SDHC 16GB class 10 <br/>(man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0) || 16.9 || 10.7 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||<br />
|-<br />
|Extrememory SDHC 32GB class 10 <br/>(man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0) || 18.7 || 16.5 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||<br />
|-<br />
|Farnell Branded (Samsung) SDHC 4GB Class 4 (MMBTF04GWBCA-ME) || 20.1 || 6.9 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 || Pi overclocked to 900 Mhz arm_freq and 500 Mhz sdram_freq<br />
|-<br />
|Fugi SDHC 32GB class 10 (P10NM00580A) || 12.7 || 19.8 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 || man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0<br />
|-<br />
|GoodRAM SDHC 16GB Pro class 10 (SDC16GHC10PGRR9) || 19.4 || 18.0 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #272 ||<br />
|-<br />
|Integral SDHC 16GB class 10 ||17.7 || 19.6 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 ||<br />
|-<br />
|Kingmax 8GB microSDHC Class 4 (KM08GMCSDHC41A) || 13.6 || 3.7 || Debian Wheezy Raspbian || Linux 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 ||<br />
|-<br />
|Kingston SDHC 4GB class 4 ||4.5 ||4.1 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #52 Tue May 8 23:49:32 BST 2012 ||<br />
|-<br />
|Kingston SDHC 4GB class 4 ||4.2 ||2.5 ||archlinuxarm-19-04-2012 ||Linux alarmpi 3.1.9-13+ #6 Thu May 10 00:48:37 UTC 2012 ||Identical card to one above. One to look into, as I was expecting Arch to be faster...<br />
|-<br />
|Kingston uSDHC 4GB class 4 ||4.0 ||3.8 ||Debian Squeeze ||Linux 3.1.9+ #90 ||<br />
|-<br />
|Kingston uSDHC 8GB class 4 (SDC4/8GB) ||4.7 ||3.7 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_uSD_8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)] This is my only card that can be counted on to boot up on each plug-in.<br />
|-<br />
|Kingston microSDHC 4GB Class 10 (SDC10/4GB) || 13.4 || 10.6 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || c 22 Jan 2015<br />
|-<br />
|Kingston microSDHC 8GB Class 10 || 14.5 || 8.1 || Debian Wheezy "Raspbian" || Linux Rpi 3.12.24+ #694 PREEMPT Tue Jul 15 17:34:35 BST 2014 armv6l GNU/Linux || Felon 07 July 2014<br />
|-<br />
|Kingston microSDHC 16GB class 4 ||17.1 ||5.1 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Kingston microSDHC 16GB class 10 ||20.1 ||13.4 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Kingston microSDHC 32GB class 10 ||17.9 ||10.9 ||2013-02-09 Debian Wheezy "Raspbian" ||Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Kingston SDHC 8GB Class 4 (SD4/8GB) || 16.2 || 5.2 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Kingston SDHC 8GB class 4 (SD4/8GB) ||4.6 ||3.0 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_SD4-8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)]<br />
|-<br />
|Kingston SDHC 8GB class 4 (SD4/8GB) ||13.2 ||3.4 || Hexxeh Raspbian r3 ||Linux raspbian 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || man:0x000002 oem:0x544d name:SA08G hwrev:0x1 fwrev:0x0<br />
|-<br />
|Kingston SDHC 8GB Class 10 (SD10V/8GB) || 16.2 || 9.9 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Kingston SDHC 32GB class 10 ||10.8 ||8.1 ||Fedora 17 ARM snapshot 07 May 2012 ||Linux fedora-arm 3.1.9 #1 ||mmc0: note - long write sync 1453000ns - 14608 its. - kernel/module problems?<br />
|-<br />
|Kingston SDHC 32GB class 10 ||4.7 ||4.1 ||Fedora 17 ARM nightly snapshot ||Linux fedora-arm 3.1.9+ #101 PREEMPT Mon Jun 4 17:19:44 BST 2012 ||custom kernel from raspberrypi github - no more mmc0 sync problems<br />
|-<br />
|Kingston SDHC 32GB class 10 ||4.6 ||3.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 ||<br />
|-<br />
|Kingston SDXC 64GB class 10 (SDCX10/64GB) ||13.9 ||10.1 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Lexar Platinum II SDHC 8GB Class 10 UHS-I || 18.5 || 9.1 ||2013-12-20 Debian Wheezy "Raspbian" ||Linux RaspberryPi 3.10.24+ #614 PREEMPT Dec 19 20:38 GMT 2013 armv6L GNU/Linux ||<br />
|-<br />
|Noname uSDHC 16GB class 4 ||18.5 ||2.6 ||Raspmc ||Linux raspbmc 3.2.27 #1 PREEMPT Mon Nov 5 20:50:02 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|Panasonic SDHC 8GB class 6 ||4.8 ||4.4 || || ||<br />
|-<br />
|Panasonic SDHC 8GB class 4 ||11.1 || 9.7 || Debian Wheezy "Rasbpian" || Linux rpi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Platinum SDHC 8GB class 10||14.9|| 13.9 || Arch Linux ARM "hf-2013-02-11"|| Linux alarmpi 3.6.11-9-ARCH+ #1 PREEMPT Sat Mar 30 02:38:20 UTC 2013 armv6l GNU/Linux ||<br />
|-<br />
|Patriot microSDHC 16GB Class 10 (PSF16GMSHC10) ||9.5 ||5.2 ||Fedora 14 ||Linux raspi 3.1.9+ #101 ||init_emmc_clock=200000000 in config.txt<br />
|-<br />
|Patriot SDHC 16GB Class 10 (PSF16GSDHC10) ||19.3 ||9.3 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Patriot SDHC 32GB Class 10 UHS-1 (PEF32GSDHC10U1) ||20.4 ||12.1 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|PNY microSDHC 16GB Class 10 (P-SDU16G10-GE) ||17.31 ||11.0 ||Raspbian OS from NOOBS v1.4.0 ||Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux ||Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/PNY-Class10.html Details]<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MP16DA/AM) ||17.33 ||13.1 ||Raspbian OS from NOOBS v1.4.0 ||Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux ||Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/Samsung-Class10.html Details]<br />
|-<br />
<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||10.7 ||8.8 ||Fedora 17 ARM snapshot 07 May 2012 - GUI release ||Linux fedora-arm 3.1.9 #1 ||Had "long write sync" errors, slow boot times and then system instability using USB port on Macbook, switched to iPhone charger (5V 1A) and warning disappeared<br />
|-<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||19.6 ||18.7 || Debian Wheezy "Raspbian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armvl GNU/Linux ||(Same user / card as above, definitely notable that Raspbian is superior)<br />
|-<br />
|Samsung SDHC 16GB Class 10 (MB-SPAGC) ||18.5 ||12.2 || Debian XFCE pipplware ||Linux raspberrypi 3.10.33+ #356 PREEMPT Tue Mar 18 17:35:55 GMT 2014 armv6l GNU/Linux || djayor 9 May 2014<br />
|-<br />
|Samsung SDHC 4GB Class 4 (MB-SS4GA/EU) ||17.7 ||8.1 || Debian Wheezy "Raspbian" ||Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l<br />
||Markus 2014/02/24<br />
|-<br />
|Samsung microSDHC 4GB Class 6 ( MB-MS04D) || 18.9 || 8.1 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || c 21 Jan 2015<br />
|-<br />
|Samsung microSDHC 8GB Class 6 ( MB-MS08DA/EU) || 17.8 || 6.3 || Debian Wheezy "Raspbian" || Linux Rpi 3.12.24+ #694 PREEMPT Tue Jul 15 17:34:35 BST 2014 armv6l GNU/Linux || Felon 07 July 2014<br />
|-<br />
|Samsung SDHC 32GB Class 6 || 21.6 || 17.4 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux || -<br />
|-<br />
|Samsung EVO microSDHC 16GB Class 10 (MB-MP16D) || 17.2 || 8.9 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || B+ model<br>c 22 Jan 2015<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MPAGA/US) || 19.8 || 15.8 || Debian Wheezy "Raspbian" || Linux pisces 3.1.9+ #155 PREEMPT Mon Jul 9 12:49:19 BST 2012 armv6l GNU/Linux || -<br />
|-<br />
|Samsung microSDHC 16GB Class 4 (MB-MS4GA/US) || 19.2 || 5.5 || Debian Wheezy "Raspbian" || ? || -<br />
|-<br />
|Samsung microSDHC 16GB Class 10 (MB-MPAGAEU) || 21.7 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux || man:0x00001b oem:0x534d name:00000 hwrev:0x1 fwrev:0x0 <br> 512Mb version of Raspberry Pi<br />
|-<br />
|Samsung PRO microSDHC 16GB Class 10 (MB-MGAGB) || 17.5 || 11.3 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux || Model B+<br />
|-<br />
|SanDisk Extreme III 2GB Class 10 (BE07054050838) || 23.3 || 21.5 || Raspbmc || Linux raspbmc 3.2.27 #1 PREEMPT Mon Nov 5 20:50:02 UTC arm61 GNU/Linux || 512Mb version of Raspberry Pi<br />
|-<br />
|SanDisk microSD 2GB ||4.7 ||4.2 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_2GB_uSD_CDM_Bench.zip CrystalDiskMark results (FAT32)] Card has no serial/is likely a fake.<br />
|-<br />
|SanDisk Ultra SDHC 4GB class 4 ||4.7 ||4.4 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SD04G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra II SDHC 4GB class 4 (15 MB/s)||20.9 ||14.6 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ ||<br />
|-<br />
|SanDisk SDHC 8GB class 4 ||11.1 ||5.6 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. <br />man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 4GB class 4 ||11.15 ||5.15 ||Raspbian Wheezy || Linux raspberrypi 3.6.11+ #456 PREEMPT || man:0x000003 oem:0x5344 name:SD04G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 8GB class 4 ||4.7 ||3.2 ||Debian Squeeze || ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 6 "30MB/s*" ||19.5 || 7.6 ||archlinuxarm || 3.1.9-22-ARCH+ #1 PREEMPT Sun Jun 17 13:54:30 UTC 2012 || "mmc0: error -84 whilst initialising SD card" at bootup, but works fine<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" ||19.3 || 3.2 ||Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s* (SDSDU-008G-UQ46)" || 18.6 || 14.5 ||Raspbian GNU/Linux 7 (wheezy) || Linux raspberrypi 3.10.21+ #604 PREEMPT Mon Dec 2 20:17:09 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" || 13.6 || 14.5 || raspbmc rc3 || Linux raspbmc 3.1.9-test-12-06 #1 PREEMPT Mon Jun 18 20:07:45 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC II 16GB class 2 "15MB/s*" ||16.7 || 16.2 || Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 || man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 UHS-1 "30Mb/s" (SDSDU-016G-U46) ||20.9 ||18.1 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. <br />man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 "30Mb/s" (SDSDU-016G-U46) ||20.9 ||10.9 ||Raspbian Wheezy || Linux raspberrypi 3.6.11+ #371 PREEMPT || <br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 (SDSDQUAN-016G-G4A) ||18.8 ||13.4 || 2015-02-16-wheezy-raspbian || Linux rpi 3.18.9-v7+ #767 SMP PREEMPT || read test is done with dropped cache, write test is done with sync; man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0 <br />
|-<br />
|SanDisk microSDHC 16GB class 4 (SDSDQ-016G) || 18.3 || 7.5 || 2015-02-16-wheezy-raspbian || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk microSDHC 16GB class 10 (SDSDQUIP-016G-A46) ||18.01 ||17.9 || Raspbian OS from NOOBS v1.4.0 || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/SanDisk-Class10.html Details] <br />
|-<br />
|SanDisk Ultra SDHC 32GB class 10 "30Mb/s" (SDSDU-032G-U46) ||18.3 ||8.8 ||Raspbian Wheezy || Linux raspberrypi 3.12.19+ #684 PREEMPT || man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0 <br />
|-<br />
|SanDisk Ultra SDHC 16GB class 10 "30MB/s" (SDSDU-016G-U46S) ||21.6 ||15.2 || 2013-02-09-wheezy-raspbian || Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme SDHC I 4GB class 10 "30MB/s" || 19.7 || 21.0 || 2012-07-15-wheezy-raspbian || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux || Only boots with images with new firmware, didn't boot with previous images.<br />
|-<br />
|SanDisk Extreme SDHC I 8GB class 10 "30MB/s" || 17.7 || 19.7 || Archlinuxarm 2012-06-13 || Linux raspi 3.1.9-28-ARCH+ #1 PREEMPT Fri Jul 6 23:07:26 UTC 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme SDHC I 8GB class 10 "30MB/s" || 17.2 || 10.6 || RISC OS 5.21 (04-Jun-2014) || RC12a ||<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 32GB class 10 "30MB/s" || 21.4 / 18.4 || 19.5 / 22.2 || 2012-10-28-wheezy-raspbian || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk microSDHC UHS-I 32GB class 10 "30MB/s" || 21.1 || 10.9 || 2013-02-09 Debian Wheezy "Raspbian" || Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra microSDHC 32GB class 10 "48MB/s" (SDSDQUN-032G-FFP-A)|| 18.5 || 10.8 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux || Raspberry Pi B+, 2014-12-20<br />
|-<br />
|SanDisk Ultra microSDHC 32GB class 10 "48MB/s" (SDSDQUAN-032G-C4A)|| 18.9 || 16.73 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux || Raspberry Pi B, 2015-02-12<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 16GB class 10 "45MB/s" (SDSDX-016G-X46) || 21.1 || 20.8 || 2012-09-18-wheezy-raspbian || Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Sandisk Extreme microSDHC UHS-I 16GB || 18.8 || 18.2 || 2014-09-09-wheezy-raspbian on Model B+ || Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SE16G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme SDHC UHS-I 32GB class 10 "45MB/s" (SDSDX-032G-X46) || 20.96 || 17.9 || 2013-05-20-wheezy-raspabian || Linux raspberrypi 3.6.11+ #456 PREEMPT || man:0x000003 oem:0x5344 name:SU32G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk Extreme PLUS SDHC UHS-I 32GB class 10 "80MB/s" (SDSDXS-032G-A46) || 18.7 || 16.5 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SE32G hwrev:0x8 fwrev:0x0<br />
|-<br />
|SanDisk SDHC 32GB class 6 ||4.6 ||4.8 || || ||<br />
|-<br />
|SanDisk uSDXC 64GB class 6 ||4.9 ||3.8 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_64GB_uSDXC_CDM_Bench.zip CrystalDiskMark results (FAT32)]<br />
|-<br />
|SanDisk Ultra SDXC 64GB class 10 (SDSDQUAN-064G-G4A) ||17.9 ||14.5 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|SanDisk Extreme SDXC 64GB class 10 (SDSDQXN-064G-G46A) ||17.4 ||20.9 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Silicon Power 8GB class 10 (SP008GBSDH010V10) || 15.6 || 11.7 || Debian Wheezy "Raspbian" (2012-12-16) || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Sony 8GB class 10 (SF-8UY/TQ1) || 20.9 || 13.4 || Debian Wheezy "Raspbian" (2013-09-25) || Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux ||man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x2<br />
|-<br />
|Sony 64GB class 10 (SR-64UY) || 15.8 || 17.5 || Debian Wheezy "Raspbian" (2015-02-16) || Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|TakeMS SDXC 64GB, Class 10 ||16.9 ||8.2 ||Debian Wheezy "Raspbian" (2013-06-02) ||Linux pisys 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux || Pi B overclocked arm_freq=1000 core_freq=500 sdram_freq=600 over_voltage=6<br />
|-<br />
|TDK microSDHC 4GB, Class 4 (80-56-10301-004G) ||11.2 ||4.7 ||Debian Wheezy "Raspbian" (2012-07-15) ||3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 || <br />
|-<br />
|Toshiba microSDHC 4GB Class 4 ||17.8 ||10.4 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Toshiba SD-T16G SDHC 16GB, Class 10 (1046 US7022 C) ||20.6 ||13.5 ||Debian Wheezy "Raspbian" ||3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Toshiba microSDXC 64GB (SD-C064GR7AR30) ||14.7 ||10.5 ||Raspbian 2015-02-16 ||Linux raspberrypi 3.18.8-v7+ ||<br />
|-<br />
|Transcend microSDHC 16GB Class 10 (16GBBEU300A) || 17.7 || 9 || Debian Wheezey 7.6 "Raspbian" || Linux raspbian 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 UTC 2014 armv6l GNU/Linux || 2014-10-05 by @xhark <br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10E) || 22.2 || 17.1 || 2013-04-22 Raspbmc || Linux raspbmc 3.6.11 #2 PREEMPT Wed Mar 13 17:12:47 UTC 2013 armv6l GNU/Linux || Pi overclocked toarm_freq=840, core_freq=350, gpu_freq=253<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10E) ||15.9||17.5||Debian Wheezy "Raspbian"||Linux RaspberryPi 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux||stock clock speed||<br />
|-<br />
|Transcend microSDHC 8GB Class 10 (TS8GUSDHC10) || 20.2 || 11.2 || Debian Wheezy "Raspbian" || Linux raspberrypi 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux || <br />
|-<br />
|Transcend SDHC 8GB class 6 ||5.8 ||5.8 || || ||<br />
|-<br />
|Transcend SDHC 8GB Class 6 (TS8GSDHC6) ||4.6 ||4.0 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 Wed Apr 18 18:23:05 BST 2012 armv61 GNU/Linux ||Tested with dd. Card doesn't maintain the promised minimum class speed.<br />
|-<br />
|Transcend SDHC 8GB Class 4 (TS8GSDHC4) ||11.1 ||8.1 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Transcend microSDHC 8GB Kit, Class 4 (TS8GUSDHC4)||4.7 ||3.7 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10) ||4.6 ||4.6 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ armv61 GNU/Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10) ||19.5 ||18.5 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDU1) UHC-I X300 ||20.9 ||13.1 ||Linux alarmpi 3.6.11-14-ARCH+ #1 PREEMPT Sun Jul 21 17:39:58 CDT 2013 armv6l GNU/Linux ||Arch Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10U1) UHC-I X600 ||21.1 ||15 ||Linux alarmpi 3.6.11-14-ARCH+ #1 PREEMPT Sun Jul 21 17:39:58 CDT 2013 armv6l GNU/Linux ||Arch Linux ||<br />
|-<br />
|Transcend SDHC 8GB Class 10 (TS8GSDHC10U1) UHC-I X600 ||18.5 ||12.4 ||Debian Wheezy (Raspbian 2014-01-07) ||Linux raspi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux ||man:0x000074 oem:0x4a45 name:SDU1 hwrev:0x0 fwrev:0x2<br />
|-<br />
|Transcend SDHC 4GB Class 6 ||9.8 ||8.8 ||Fedora Remix FC14 ||Linux raspi 3.1.9 #1 PREEMPT Sat Mar 3 21:58:00 UTC 2012 armv6l armv6l armv6l GNU/Linux ||Not sure why this setup is faster than others, test results repeatable.<br />
|-<br />
|Transcend SDHC 4GB Class 10 (TS4GSDHC10) || 17.6 || 12.1 ||Debian Wheezy "Rasbpian" (2012-10-28) || Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|Transcend SDHC 16GB Class 10 ||20.3 ||11.9 ||Debian Wheezy "Rasbpian" || Linux raspberry-pi 3.1.9-cutdown+ #173 ||<br />
|-<br />
|Transcend SDHC 16GB Class 10 ||17.4 ||12.0 ||Debian Wheezy (2012-08-08-wheezy-armel)|| Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux || man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|-<br />
|Transcend microSDHC 16GB Class 10 || 17.96 || 16.4 ||Raspbian OS from NOOBS v1.4.0 || Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux || Tested on Pi 2 Model B by FastEddie 19 Mar 2015; More [http://skippingpebbles.com/Pi/Transcend-Class10.html Details]<br />
|-<br />
|Transcend SDHC 16GB Class 10 || 18.6 || 11.2 ||Raspbian Wheezy || Linux raspberrypi 3.12.20+ #687 PREEMPT Fri May 30 16:39:11 BST 2014 armv6l GNU/Linux || hwrev:0x0 fwrev:0x2 man:0x000074 oem:0x4a45 <br />
After 2 months of use as a home server<br />
|-<br />
|Transcend SDHC 16GB Class 10 UHS-I Premium 300x ||21.4 ||9.6 ||Debian Rasbpian Wheezy (2013-09-25)|| Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l || <br />
|-<br />
|Transcend SDHC 32GB Class 10 (TS32GSDHC10E) || 20.3 || 15.3 || Debian Wheezy "Rasbpian" || Linux raspberrypi 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 armv6l GNU/Linux || man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0<br />
|-<br />
|Transcend MicroSDHC 32GB Class 10 UHS-I (Premium 300x)||18.5 ||10.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux ||<br />
|-<br />
|Transcend MicroSDXC 64GB Class 10 UHS-I (Premium 300x)||18.5 ||15.7 ||ARM Arch Linux||Linux alarmpi 3.12.28-2-ARCH #1 PREEMPT Mon Sep 22 02:02:11 MDT 2014 armv6l GNU/Linux ||<br />
|-<br />
|Sandisk Extreme Pro SDHC 8GB Class 10 UHS-I || 21.6 || 21.7 || Arch Linux || Linux alarmpi 3.6.11-11-ARCH+ #1 PREEMPT Tue May 14 16:12:58 UTC 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0<br />
|-<br />
|Sandisk Extreme Pro SDHC 16GB Class 10 UHS-I (SDSDXPA-016G-A75) ||21.6 ||21.7 || Debian Wheezy "Rasbpian" || Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme Pro SDHC 16GB Class 10||20.8||18.6||Debian Wheezy "Raspbian"||Linux raspberrypi 3.1.9+ #125 PREEMPT Sun Jun 17 16:09:36 BST 2012 armv6l GNU/Linux||<br />
|-<br />
|Sandisk Ultra SDHC I Class 6 ("30MB/s") ||4.7 ||4.8 ||Debian Wheezy "Raspbian" ||3.2.18+ #3 PREEMPT ||Feels faster than my Kingston 4GB Class 4 card.<br />
|-<br />
|Sony 8GB SDHC Class 4 || 17.4 || 11.8 || Debian Wheezy Raspbian || Linux 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 ||<br />
|-<br />
|WINTEC FileMate Professional SDHC 16GB Class 10 (3FMSD16GBC10-R) ||4.6 ||4.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #95 PREEMPT Thu May 31 13:21:40 BST 2012 armv6l GNU/Linux ||After installing new kernel with rpi-update on 2012-06-01<br />
|-<br />
|Lexar SDHC 8GB Class 4 "Multi-use" ||18.9 ||6.8 ||Debian Wheezy "Raspbian" ||3.1.9+ #110 PREEMPT ||<br />
|-<br />
|Lexar SDHC 8GB Class 6 "PLATINUM II" ||19.7 ||10.1 ||Debian Wheezy "Raspbian" || 3.1.9+ #168 PREEMPT ||<br />
|-<br />
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||5.3 ||4.8 ||Debian Wheezy/sid || Linux raspberrypi 3.2.19-rpi1+ #3 ||<br />
|-<br />
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||18.9 ||9.0 ||Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #168 PREEMPT || Same card as 'Lexar SDHC 16GB Class 10 "PLATINUM II"' above - imaged with Raspbian<br />
|-<br />
|Lexar SDXC 64GB UHS-I Class 10 Premium series ||20.7 ||15.8 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux ||<br />
|-<br />
|Lexar SDHC 8GB UHS-I Class 10 Premium series ||19.4 ||8.8 ||raspbmc-rls-1.0-hardfp-b20131223-u20131223 ||Linux raspbmc 3.10.24 #2 PREEMPT Mon Dec 23 05:18:12 UTC 2013 armv6l GNU/Linux ||man:0x000028 oem:0x4245 name: hwrev:0x0 fwrev:0x2<br />
|-<br />
|Mushkin SDHC 16GB Class 10 MKNSDHCC10-16GB ||19.7 ||10.9 ||2012-07-15-wheezy-raspbian ||3.1.9+ #168 PREEMPT ||<br />
|-<br />
|PNY SDHC 8GB Class 6 Limited Edition ||7.4 ||13.2 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|PNY SDHC 32GB Class 10 Elite Performance ||20.4 ||15.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.6.11+ #456 PREEMPT armv6l sys v.3.3.3 ||avoid_pwm_pll=1 arm_freq=1000 gpu_freq=675 sdram_freq=500 core_freq=275 over_voltage=6<br />
|-<br />
|SanDisk MicroSDHC 4GB ||5.1 ||11.4 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk UHS-I C10 Ultra SDHC 8GB (SDSDU-008G-U46)||19.1 ||20.8 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra SDHC 8GB class 10 (30 MB/s) ||21.7 ||15.7 ||Debian Wheezy "Raspbian" ||Linux raspberrypi 3.6.11+ #434 PREEMPT Wed May 1 21:13:52 BST 2013 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0 (some read time trials with drop caches: 21.0/21.7/21.8/21.8/21.8/21.8/(write#2:)21.7; two write trials: 15.7/15.8; timings (dd;sync): 33.761;5.799)<br />
|-<br />
|Panasonic SDHC 4GB Class 10 UHS-I ||11.2 ||6.2 ||Debian Wheezy "Raspbian" ||3.1.9+ #144 PREEMPT || Panasonic RP-SDU04GE1K<br />
|-<br />
|Sony SDHC 8GB Class 10 UHS-1 ||20.8 ||17.2 ||Debian Wheezy "Raspbian" ||3.2.27+ #250 PREEMPT ||<br />
|-<br />
|Sony SDHC 4Gb Class 10 UHS-I "40MB/s" (SF-4UY) ||18.8 ||10.3 ||openELEC 3.0.6 ||Linux openelecPi 3.6.11 #1 PREEMPT Thu Jun 13 21:32:37 CEST 2013 armv6l GNU/Linux ||man:0x000027 oem:0x5048 name:SD04G hwrev:0x3 fwrev:0x0<br />
|-<br />
|Sony SDHC 8Gb Class 10 UHS-I "90MB/s" (SF-8UX) ||21.1 ||16.9 ||Raspbian 2013-05-25-wheezy ||Linux raspberrypi 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux ||man:0x000082 oem:0x4a54 name:NCard hwrev:0x0 fwrev:0x0<br />
|-<br />
|Sony SDHC 16Gb Class 10 UHS-I "40MB/s" ||21.8 ||13.5 ||Raspbian 2013-07-26-wheezy ||Linux raspberrypi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra 16GB MicroSDHC Class 10 UHS-1 + Adapter "30MB/s" (SDSDQUA-016G-U46A) ||18.5 ||7.3 ||Raspbian 2014-01-07 wheezy ||Linux mmmpie 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Ultra 8GB MicroSDHC Class 10 UHS-1 + Adapter "48MB/s" (SDSDQUAN-008G-G4A) ||18.8 ||14.5 ||Raspbian 2014-12-24 wheezy ||Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux ||<br />
|-<br />
|SanDisk Extreme 16GB UHS-I/U3 Micro SDHC Memory Card Up to 60MB/s Read with Adapter- SDSDQXN-016G-G46A ||20.3 ||18.2 ||OpenELEC 5.0.1 ||Linux OptimusPi 3.18.5 #1 SMP PREEMPT Sun Feb 1 14:59:37 CET 2015 armv7l GNU/Linux ||Raspberry Pi 2 ||<br />
|-<br />
|SanDisk Extreme 16GB UHS-I/U3 Micro SDHC Memory Card Up to 60MB/s Read with Adapter- SDSDQXN-016G-G46A ||19.8 ||24.7 ||OSMC Alpha 4 ||Linux osmc 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l GNU/Linux ||Raspberry Pi 2 ||<br />
|}<br />
<br />
=== SD(DC|DX] Card Class 6 & 10 Hints with OverClockings === <br />
[http://elinux.org/index.php?title=RPiconfig&section=14 | SD card usage Hints with OverClocking]<br />
{{Template:BackToRPiHub}}<br />
[[Category:RPi SD card]]<br />
<br />
== References ==<br />
<references></references><br />
{{Template:Raspberry Pi}}</div>AutoStatichttps://elinux.org/index.php?title=RPi_Text_to_Speech_(Speech_Synthesis)&diff=316682RPi Text to Speech (Speech Synthesis)2014-02-10T20:33:16Z<p>AutoStatic: /* Pico Text To Speech */</p>
<hr />
<div>This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.<br />
<br />
== Why use Text to Speech? ==<br />
<br />
It’s very easy add to your program - just output a string to the speech function instead of the screen.<br />
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.<br />
<br />
You could use speech output for:<br />
(i) status messages - e.g. internet connection made or IP address on a headless RPi;<br />
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;<br />
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.<br />
<br />
== Install supporting packages ==<br />
<br />
Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).<br />
<br />
Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:<br />
<br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
<br />
If you do not already have sound on your RPi then you will need the alsa sound utilities:<br />
sudo apt-get install alsa-utils<br />
and edit the file /etc/modules using:<br />
sudo nano /etc/modules<br />
to have line:<br />
snd_bcm2835 <br />
If this line is already there then leave the file as is!<br />
<br />
Install the mplayer audio/movie player with:<br />
sudo apt-get install mplayer<br />
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:<br />
sudo nano /etc/mplayer/mplayer.conf<br />
to add line<br />
nolirc=yes<br />
<br />
== Cepstral Text to Speech ==<br />
<br />
Cepstral is a commercial Text to Speech engine that is installed on the Pi and does not require an Internet connection. The voices are higher quality than open source solutions and pricing is dependent on the use case. More information is available is their website:<br />
<br />
https://www.cepstral.com/raspberrypi<br />
<br />
== Festival Text to Speech ==<br />
<br />
The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.<br />
<br />
Install Festival with:<br />
sudo apt-get install festival<br />
<br />
Try out Festival with:<br />
echo “Just what do you think you're doing, Dave?” | festival --tts<br />
or to speak RPi’s IP address:<br />
hostname -I | festival --tts<br />
<br />
== Espeak Text to Speech ==<br />
<br />
Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.<br />
<br />
Install Espeak with:<br />
sudo apt-get install espeak<br />
<br />
Test Espeak with:<br />
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-<br />
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"<br />
<br />
== Google Text to Speech ==<br />
<br />
Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.<br />
<br />
I used used ax206geek’s bash script to access the Google Text to Speech engine:<br />
<br />
Create a file speech.sh with:<br />
nano speech.sh<br />
<br />
Add these lines to the file and save it (in nano editor use CTRL-O writeOut)<br />
#!/bin/bash<br />
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }<br />
say $*<br />
Alternatively save from here: [[File:speech.sh]]<br />
<br />
Add execute permissions to your script with:<br />
chmod u+x speech.sh<br />
<br />
Test it using: <br />
./speech.sh Look Dave, I can see you're really upset about this.<br />
<br />
EXTRA: <br />
Dan Fountain improved on the above script to speak any length of text (Google limits you to 100 bytes normally). His excellent easy-to-read webpage describes this at http://danfountain.com/2013/03/raspberry-pi-text-to-speech/<br />
<br />
== Pico Text to Speech ==<br />
<br />
Google Android TTS engine.<br />
<br />
sudo apt-get install libttspico-utils<br />
pico2wave -w lookdave.wav "Look Dave, I can see you're really upset about this." && aplay lookdave.wav<br />
<br />
== Recommendations ==<br />
<br />
I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?<br />
<br />
All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.</div>AutoStatichttps://elinux.org/index.php?title=RPi_Text_to_Speech_(Speech_Synthesis)&diff=316676RPi Text to Speech (Speech Synthesis)2014-02-10T20:32:59Z<p>AutoStatic: /* Pico TTS */</p>
<hr />
<div>This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.<br />
<br />
== Why use Text to Speech? ==<br />
<br />
It’s very easy add to your program - just output a string to the speech function instead of the screen.<br />
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.<br />
<br />
You could use speech output for:<br />
(i) status messages - e.g. internet connection made or IP address on a headless RPi;<br />
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;<br />
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.<br />
<br />
== Install supporting packages ==<br />
<br />
Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).<br />
<br />
Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:<br />
<br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
<br />
If you do not already have sound on your RPi then you will need the alsa sound utilities:<br />
sudo apt-get install alsa-utils<br />
and edit the file /etc/modules using:<br />
sudo nano /etc/modules<br />
to have line:<br />
snd_bcm2835 <br />
If this line is already there then leave the file as is!<br />
<br />
Install the mplayer audio/movie player with:<br />
sudo apt-get install mplayer<br />
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:<br />
sudo nano /etc/mplayer/mplayer.conf<br />
to add line<br />
nolirc=yes<br />
<br />
== Cepstral Text to Speech ==<br />
<br />
Cepstral is a commercial Text to Speech engine that is installed on the Pi and does not require an Internet connection. The voices are higher quality than open source solutions and pricing is dependent on the use case. More information is available is their website:<br />
<br />
https://www.cepstral.com/raspberrypi<br />
<br />
== Festival Text to Speech ==<br />
<br />
The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.<br />
<br />
Install Festival with:<br />
sudo apt-get install festival<br />
<br />
Try out Festival with:<br />
echo “Just what do you think you're doing, Dave?” | festival --tts<br />
or to speak RPi’s IP address:<br />
hostname -I | festival --tts<br />
<br />
== Espeak Text to Speech ==<br />
<br />
Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.<br />
<br />
Install Espeak with:<br />
sudo apt-get install espeak<br />
<br />
Test Espeak with:<br />
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-<br />
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"<br />
<br />
== Google Text to Speech ==<br />
<br />
Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.<br />
<br />
I used used ax206geek’s bash script to access the Google Text to Speech engine:<br />
<br />
Create a file speech.sh with:<br />
nano speech.sh<br />
<br />
Add these lines to the file and save it (in nano editor use CTRL-O writeOut)<br />
#!/bin/bash<br />
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }<br />
say $*<br />
Alternatively save from here: [[File:speech.sh]]<br />
<br />
Add execute permissions to your script with:<br />
chmod u+x speech.sh<br />
<br />
Test it using: <br />
./speech.sh Look Dave, I can see you're really upset about this.<br />
<br />
EXTRA: <br />
Dan Fountain improved on the above script to speak any length of text (Google limits you to 100 bytes normally). His excellent easy-to-read webpage describes this at http://danfountain.com/2013/03/raspberry-pi-text-to-speech/<br />
<br />
== Pico Text To Speech ==<br />
<br />
Google Android TTS engine.<br />
<br />
sudo apt-get install libttspico-utils<br />
pico2wave -w lookdave.wav "Look Dave, I can see you're really upset about this." && aplay lookdave.wav<br />
<br />
== Recommendations ==<br />
<br />
I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?<br />
<br />
All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.</div>AutoStatichttps://elinux.org/index.php?title=RPi_Text_to_Speech_(Speech_Synthesis)&diff=316670RPi Text to Speech (Speech Synthesis)2014-02-10T20:32:31Z<p>AutoStatic: </p>
<hr />
<div>This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.<br />
<br />
== Why use Text to Speech? ==<br />
<br />
It’s very easy add to your program - just output a string to the speech function instead of the screen.<br />
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.<br />
<br />
You could use speech output for:<br />
(i) status messages - e.g. internet connection made or IP address on a headless RPi;<br />
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;<br />
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.<br />
<br />
== Install supporting packages ==<br />
<br />
Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).<br />
<br />
Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:<br />
<br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
<br />
If you do not already have sound on your RPi then you will need the alsa sound utilities:<br />
sudo apt-get install alsa-utils<br />
and edit the file /etc/modules using:<br />
sudo nano /etc/modules<br />
to have line:<br />
snd_bcm2835 <br />
If this line is already there then leave the file as is!<br />
<br />
Install the mplayer audio/movie player with:<br />
sudo apt-get install mplayer<br />
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:<br />
sudo nano /etc/mplayer/mplayer.conf<br />
to add line<br />
nolirc=yes<br />
<br />
== Cepstral Text to Speech ==<br />
<br />
Cepstral is a commercial Text to Speech engine that is installed on the Pi and does not require an Internet connection. The voices are higher quality than open source solutions and pricing is dependent on the use case. More information is available is their website:<br />
<br />
https://www.cepstral.com/raspberrypi<br />
<br />
== Festival Text to Speech ==<br />
<br />
The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.<br />
<br />
Install Festival with:<br />
sudo apt-get install festival<br />
<br />
Try out Festival with:<br />
echo “Just what do you think you're doing, Dave?” | festival --tts<br />
or to speak RPi’s IP address:<br />
hostname -I | festival --tts<br />
<br />
== Espeak Text to Speech ==<br />
<br />
Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.<br />
<br />
Install Espeak with:<br />
sudo apt-get install espeak<br />
<br />
Test Espeak with:<br />
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-<br />
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"<br />
<br />
== Google Text to Speech ==<br />
<br />
Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.<br />
<br />
I used used ax206geek’s bash script to access the Google Text to Speech engine:<br />
<br />
Create a file speech.sh with:<br />
nano speech.sh<br />
<br />
Add these lines to the file and save it (in nano editor use CTRL-O writeOut)<br />
#!/bin/bash<br />
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }<br />
say $*<br />
Alternatively save from here: [[File:speech.sh]]<br />
<br />
Add execute permissions to your script with:<br />
chmod u+x speech.sh<br />
<br />
Test it using: <br />
./speech.sh Look Dave, I can see you're really upset about this.<br />
<br />
EXTRA: <br />
Dan Fountain improved on the above script to speak any length of text (Google limits you to 100 bytes normally). His excellent easy-to-read webpage describes this at http://danfountain.com/2013/03/raspberry-pi-text-to-speech/<br />
<br />
== Pico TTS ==<br />
<br />
Google Android TTS engine.<br />
<br />
sudo apt-get install libttspico-utils<br />
pico2wave -w lookdave.wav "Look Dave, I can see you're really upset about this." && aplay lookdave.wav<br />
<br />
== Recommendations ==<br />
<br />
I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?<br />
<br />
All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.</div>AutoStatichttps://elinux.org/index.php?title=RPi_applications&diff=255266RPi applications2013-05-20T20:22:38Z<p>AutoStatic: </p>
<hr />
<div>[[Category:RaspberryPi]]<br />
<br />
=== Additional apt Sources ===<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=30&t=19349 Open Monitoring Distribution] (Nagios, Shinken, NagVis, PNP, Thruk, DokuWiki, check_mk, mod_gearman)<br />
*[[RPi_XBMC#3rd_party_apt_source | XBMC]]<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=56&t=15793 open media vault]<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6096 webmin]<br />
*[http://maniactwister.de/b/aazlvr/en Dionaea]<br />
*[http://rpi.autostatic.com/ Raspbian audio software repository]<br />
<br />
=== Raspberry Pi Software Application Notes ===<br />
Here you will find notes on installing specific applications on the Raspberry Pi<br />
<br />
* [[Rpi_Asterisk|Asterisk]]. Notes on installing the Asterisk VoIP Server.<br />
* [[Rpi_Music_Player_Daemon|Music Player Daemon]]<br />
* [[RPi_XBMC]]<br />
* [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=238000#p238000 RetroShare]<br />
* No Flash or accelerated HTML5 video support yet. (XBMC will play youtube or you can download then play in omxplayer )<br />
* [[RPi_emulators]]</div>AutoStatichttps://elinux.org/index.php?title=RPi_applications&diff=255260RPi applications2013-05-20T20:22:00Z<p>AutoStatic: Changed URL and description of my repository</p>
<hr />
<div>[[Category:RaspberryPi]]<br />
<br />
=== Additional apt Sources ===<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=30&t=19349 Open Monitoring Distribution] (Nagios, Shinken, NagVis, PNP, Thruk, DokuWiki, check_mk, mod_gearman)<br />
*[[RPi_XBMC#3rd_party_apt_source | XBMC]]<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=56&t=15793 open media vault]<br />
*[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6096 webmin]<br />
*[http://maniactwister.de/b/aazlvr/en Dionaea]<br />
*[http://rpi.autostatic.com/ audio software repository]<br />
<br />
=== Raspberry Pi Software Application Notes ===<br />
Here you will find notes on installing specific applications on the Raspberry Pi<br />
<br />
* [[Rpi_Asterisk|Asterisk]]. Notes on installing the Asterisk VoIP Server.<br />
* [[Rpi_Music_Player_Daemon|Music Player Daemon]]<br />
* [[RPi_XBMC]]<br />
* [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=238000#p238000 RetroShare]<br />
* No Flash or accelerated HTML5 video support yet. (XBMC will play youtube or you can download then play in omxplayer )<br />
* [[RPi_emulators]]</div>AutoStatichttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=237710RPi VerifiedPeripherals2013-04-03T18:11:33Z<p>AutoStatic: /* Working USB to Serial Adapters */</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 />
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.<br />
<br />
If you use a powered hub and the Raspberry Pi PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100&nbsp;mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).<br />
<br />
===Working USB Hubs===<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''USB Version'''<br />
| '''Number of Ports'''<br />
| '''Power Rating*'''<br />
| '''Powers Raspberry Pi'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Atlantis<br />
|HUB USB2.0 7P<br />
|P014-GH902-B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2&nbsp;A<br />
|Verified<br />
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|4-Port Ultra-Slim Desktop Hub<br />
|F4U040<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.6&nbsp;A<br />
|Verified<br />
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|8-Port ExpressBus for iMac<br />
|F5U010<br />
|<br />
|USB 2.0<br />
|8-Port 7x"A" 1x"B"<br />
|<br />
|Verified<br />
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U224<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|TetraHub™ USB 2.0 4-Port Hub<br />
|F5U231<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U234<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|No backfeed, can power the RPi. Comes with a 2.4&nbsp;A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''&ldquo;Per Port Current Self-Powered Mode: 500mA (max)&rdquo;''. However, I've attached a HD that requires 850&nbsp;mA and it worked fine.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.8&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|MyEssentials 7-Port High-Speed USB 2.0 Hub<br />
|F5U259-ME<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Lighted Hub<br />
|F5U403<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Lighted Hub<br />
|F5U700<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hub 2-en-1<br />
|F5U706ea<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237v1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2.5&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U040v<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5 V - 2.6 A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U039qukAPL<br />
|05e3:0608<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Benq<br />
|<br />
|E2220HD<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|BUFFALO<br />
|4 Port Hub<br />
|BSH4aAE06<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V <br />
|Verified<br />
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Cyberpower<br />
|High-speed Hub<br />
|CP-H720P<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|3.6&nbsp;A<br />
|Verified<br />
|May Contain dual 05e3:0608 instead of 0409:0050<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2001FP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|SP2309W<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2407FWP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|U3011<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub - Card Reader Works - May work with SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|<br />
|B/N61393<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|USB 2.0 External Hub 7 Port<br />
|B/N87467<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.5&nbsp;A<br />
|Verified<br />
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Deltaco<br />
|<br />
|UH-715 Rev 2<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|<br />
|<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|Dynex USB 2.0 7 Port Hub<br />
|DX-HB7PT<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5.0&nbsp;V / 2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|D-Link 7 Port USB Hub<br />
|DUB-H7/B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7 High Speed USB 2.0 7-Port Hub<br />
|BUBH7A A5<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7<br />
|EUBH7EB H/W Ver:B1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI<br />
<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-4 High Speed USB 2.0 4-Port Hub<br />
|DUB-H4<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Digicom<br />
|<br />
|<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|ednet<br />
|USB 2.0 7 port Hub<br />
|85014<br />
|<br />
|2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|Works with keyboard, mouse, audio devices<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GigaWare<br />
|USB 2.0 4 port Hub<br />
|Model 26-160<br />
|<br />
|2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|König Electronic<br />
|7 port USB2.0 HUB<br />
|CMP-USB2HUB55<br />
|1a40:0201<br />
|2.0<br />
|7-Port<br />
|2.0A<br />
|Verified<br />
|Backpowers Raspberry Pi well.<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medi@com<br />
|USB 2.0 4 ports Hub<br />
|M-HX30<br />
|<br />
|2.0<br />
|4-port<br />
|<br />
|Verified<br />
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.<br />
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|mbeat<br />
|13 Port USB Hub<br />
|USB-M13HUB<br />
|<br />
|USB 2.0<br />
|13-port<br />
|5V - 3A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Monoprice<br />
|Aquagate USB Hub<br />
|5328<br />
|<br />
|2.0<br />
|7-port<br />
|2.0&nbsp;A<br />
|Verified<br />
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable <br />
|7 Port High Speed USB Hub<br />
|USB2-HUB-AG7<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 3A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable<br />
|4 Port Hub with Battery Charging 1.1 Support<br />
|USB2-HUB4BC<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5V - 2.5A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|10 Port USB 2.0 Hub<br />
|USB2-HUB10S<br />
|<br />
|USB 2.0<br />
|10-Port<br />
|5V - 2.5A<br />
|Not Verified<br />
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|4 Port USB 3.0 Hub<br />
|USB2-HUB-81X4<br />
|<br />
|USB 3.0<br />
|4-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|7 Port USB 3.0 Hub<br />
|USB2-HUB7-81X<br />
|<br />
|USB 3.0<br />
|7-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
|Plata 4 port USB 2.0 hub<br />
|18687<br />
|<br />
|2.0<br />
|4-port<br />
|1.0&nbsp;A<br />
|Not Verified<br />
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Zipp<br />
|USB 7-Port HUB<br />
|N294<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 2.0A<br />
|Verified<br />
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)<br />
<br />
|-<br />
|}<br />
<br />
<br />
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.<br />
</div><br />
<br />
<br />
*'''Acme'''<br />
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but it is very cheap and small and works after a small modding: on USB-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the Raspberry Pi, and additionally connect GND and +5&nbsp;V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.<br />
<br />
<br />
*'''Digitus'''<br />
** 7-port USB2.0 Powered Hub. Model DA-70226.<br />
*'''Eminent'''<br />
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
* '''GearHead'''<br />
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5&nbsp;V, 1&nbsp;A)<br />
*'''Gembird'''<br />
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.<br />
* '''Genesys Logic (sold at Fry's)'''<br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref><br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)<br />
* '''Hama'''<br />
** Hama 4-way USB 2.0 Hub<br />
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)<br />
*'''HP'''<br />
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)<br />
<br />
*'''Laser'''<br />
** "7 port USB hub with AC adapter Version 2.0". 5&nbsp;V 1&nbsp;A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry Pi USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.<br />
*'''Logik'''<br />
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''<br />
** Logik L4THUB10 4 Port powered hub works fine under Raspbian/Wheezy/model B. Captive USB cable, 2&nbsp;A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!<br />
*'''LogiLink'''<br />
** UA0085 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0090 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0091 USB 3.0 Hub, 4-Port with PSU 5&nbsp;V, 4&nbsp;A. Connected with USB2.0 cable. 1&nbsp;A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy. <br />
** UA0096 USB 2.0 Hub, 10-Port with PSU 5&nbsp;V, 3.5&nbsp;A (Not suitable for powering Raspberry Pi because it doesn't work unless there is working USB input present even with PSU plugged in.)<br />
** UA0160 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.<br />
* '''Macally'''<br />
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000&nbsp;mA wall-wart (US style)<br />
* '''Manhattan'''<br />
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000&nbsp;mA wall-wart (US style)<br />
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500&nbsp;mA each) + (4 USB 3.0 Ports @900&nbsp;mA each) Power Switches on each port, AC Powered and Includes a 5&nbsp;V 4&nbsp;A wall-wart (US style)<br />
*'''Newlink'''<br />
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5&nbsp;V 1&nbsp;A<br />
** NLUSB2-222P 4 port USB 2.0 Hub with 5&nbsp;V 2&nbsp;A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])<br />
*'''Nilox'''<br />
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5&nbsp;V 1.0&nbsp;A<br />
* '''Plugable'''<br />
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5&nbsp;V 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.<br />
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port.<br />
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5&nbsp;V 3&nbsp;A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)<br />
<br />
* '''Pluscom'''<br />
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3&nbsp;A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.<br />
*'''Satechi'''<br />
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.<br />
*'''Staples (Business Depot) (Bureau EN GROS)'''<br />
** Staples 4-port hub Item 607477-CA<br />
*'''StarTech.com'''<br />
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5&nbsp;V 2&nbsp;A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).<br />
*'''SumVision'''<br />
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5&nbsp;V 1.0&nbsp;A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])<br />
*'''Sitecom'''<br />
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Raspberry Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500&nbsp;mA Voltcraft <br />
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1&nbsp;A). Powering Raspberry Pi via microUSB from a hub port.<br />
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
*'''Sweex'''<br />
** US014 4 Port USB 2.0 Hub<br />
*'''Targus'''<br />
** ACH81xx 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)<br />
** ACH63EU 4-port. Using a 5&nbsp;V 2&nbsp;A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.<br />
*'''The Pi Hut'''<br />
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
*'''Trendnet'''<br />
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2&nbsp;A)<br />
*'''Tripp-Lite'''<br />
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2.5&nbsp;A) Powering Raspberry Pi from the hub works.<br />
*'''Ultron'''<br />
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5&nbsp;V, 3&nbsp;A. USB ID 1a40:0201.<br />
*'''VANTEC'''<br />
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5&nbsp;V 2&nbsp;A AC/DC adapter. Go 2.0 Mini hub.<br />
*'''Z-TEK'''<br />
** Z-TEK 7-port powered hub with PSU 5&nbsp;V, 4&nbsp;A. USB ID 1a40:0201.<br />
*"Unknown"<br />
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works<br />
<br />
===Problem USB Hubs===<br />
<br />
Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list<br />
<br />
*'''Addon'''<br />
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.<br />
*'''Belkin'''<br />
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5&nbsp;V pinouts)<br />
** F4U022 7-Port powered USB hub (powered 5&nbsp;V, 2.6&nbsp;A), same as F4U018<br />
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired Ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.<br />
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.<br />
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes. (Works always without powering the Raspberry Pi, haven't tried that)<br />
<br />
*'''Dell'''<br />
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.<br />
<br />
*'''DELTACO'''<br />
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills Ethernet when X11 is started.<br />
<br />
*'''Dynex'''<br />
** 7-Port USB Hub - Does not work in Debian 19-04 image.<br />
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.<br />
<br />
*'''Dynamode'''<br />
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).<br />
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1&nbsp;A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification. <br />
<br />
*'''D-Link'''<br />
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)<br />
<br />
*'''E-Solution'''<br />
** 4-Port 2&nbsp;A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]<br />
<br />
*'''Fosmon'''<br />
** 7-Port USB 2.0 Hub with 1&nbsp;A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry Pi with it's Micro USB cable unplugged).<br />
<br />
*'''Gear Head'''<br />
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.<br />
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.<br />
<br />
*'''Hama'''<br />
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608<br />
<br />
*'''Kensington'''<br />
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).<br />
<br />
*'''iBall'''<br />
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.<br />
<br />
*'''Inland'''<br />
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)<br />
<br />
*'''Logik'''<br />
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)<br />
<br />
*'''LogiLink'''<br />
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.<br />
<br />
*'''Soniq'''<br />
** 4-Port 5&nbsp;V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).<br />
<br />
*'''Targus'''<br />
** ACH115EU 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.<br />
<br />
*'''TCM'''<br />
** Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1&nbsp;A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi no connects. (insufficient power?)<br />
<br />
*'''Trust'''<br />
** 10-port USB 2.0 Hub (powered). Prevents Ethernet from being recognised.<br />
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents Ethernet from being recognised. Keyboard sends multiple characters. <br />
<br />
*'''Unbranded / Multiple Brands'''<br />
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.<br />
** Generic 7-port black hub with Genesys Logic GL850A chipset<br />
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2&nbsp;A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref><br />
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but there are strange USB failures when X session started. High speed devices such as hard drives had failures.<br />
<br />
== USB Remotes ==<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 />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''<br />
=== Working USB Keyboards ===<br />
The following is a list of specific keyboards known to work and which appear to work fault-free.<br />
<br />
* '''A4 Tech'''<br />
** Model KL-5 USB Keyboard, 20&nbsp;mA.<br />
<br />
* '''ABS'''<br />
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)<br />
<br />
* '''Action Star'''<br />
** ACK-5010U Mini Keyboard And Mouse<br />
<br />
* '''Accuratus'''<br />
** KYB-Toughball-HI<br />
<br />
* '''Acer'''<br />
** KG-0917 Wireless Keyboard And Mouse Bundle (B)<br />
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)<br />
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)<br />
<br />
* '''Adesso'''<br />
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100&nbsp;mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.<br />
** Model AKB-410UB. Keyboard with Touchpad.<br />
<br />
* '''Apple''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))<br />
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]<br />
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]<br />
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]<br />
<br />
* '''Asda'''<br />
** Basic Wired Keyboard HK2026 (B)<br />
** Basic Wired Keyboard HK3014<br />
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)<br />
** Premium Wireless Keyboard (white keys, silver back) HK8028<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''Asus'''<br />
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)<br />
<br />
* '''Banbridge'''<br />
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)<br />
<br />
* '''BTC - Behavior Tech Computer Corp.'''<br />
** Wired Portable Keyboard Model 6100 US (86+9 keys)<br />
*** Works with or without a powered hub<br />
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)<br />
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5&nbsp;V/100&nbsp;mA, works directly<br />
<br />
* '''Bush'''<br />
** Wired Slimline Keyboard KU-0833<br />
*** This does not require a USB hub in order to work with the Raspberry Pi<br />
*** In the UK, it is available from Argos for £9.99<br />
<br />
* '''Cerulian''' <br />
** Mini wireless keyboard and mouse deskset (B)<br />
<br />
* '''CD Training''' <br />
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]<br />
<br />
* '''Cherry'''<br />
** CyMotion Master Linux (B)<br />
** RS 6000 USB ON<br />
** G84-4100PTMUS (B) (Compact keyboard. Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** G85-23100DE-2 (B) (Rated 40&nbsp;mA, tested with RPi powered by a 1000&nbsp;mA power supply unit)<br />
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.<br />
<br />
* '''Compaq'''<br />
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5&nbsp;V 100&nbsp;mA. Works directly connected to Raspberry Pi<br />
<br />
* '''Das Keyboard'''<br />
** Model S Professional Keyboard (Built in USB hub not tested) (B)<br />
** Model S Ultimate Keyboard (Built in USB hub working) (B)<br />
<br />
* '''Dell'''<br />
** SK-8115 (B) (Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** L100 (B)<br />
** RT7D40 (100&nbsp;mA. Works directly in Raspberry Pi)<br />
** RT7D50 (75&nbsp;mA) (run "sudo dpkg-reconfigure keyboard-configuration")<br />
** KB1421 (100&nbsp;mA)<br />
** KB2521 (100&nbsp;mA)<br />
** KB212-B (Works directly in Raspberry Pi, without powered hub)<br />
** 1HF2Y (Works directly in Raspberry Pi)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** USB Keyboard 413c:2107 - Works with and without USB hub<br />
<br />
* '''Delux'''<br />
** K8050<br />
<br />
* '''Digicom'''<br />
** WKEYPE01 Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]<br />
<br />
* '''Dynex'''<br />
** DX_-WKBD (60&nbsp;mA) (B)<br />
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)<br />
<br />
* '''EAPPLY'''<br />
** EBO-013 Wireless 2.4&nbsp;GHz compact keyboard with touchpad. Rated <40&nbsp;mA works directly from Raspberry Pi. eBay ref 260962010276 from Shenzen, China.<br />
<br />
* '''Emprex'''<br />
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)<br />
<br />
* '''Fujitsu Siemens''' <br />
** KB SC USB UK (!)<br />
** KB910 USB, with led light on the highest level (B)<br />
** KB400 USB US<br />
<br />
* '''GE''' <br />
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)<br />
<br />
* '''Gear Head''' <br />
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)<br />
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)<br />
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)<br />
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported >> also see Problem USB Keyboards<br />
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)<br />
** KB1500U (USB Mini Keyboard) (B)<br />
** KB5150 (2.4&nbsp;GHz wireless keyboard/mouse Combo) (B)<br />
*** Works well with a powered hub<br />
<br />
* '''Generic'''<br />
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.<br />
<br />
* '''Genius'''<br />
** Ergomedia 700 (GK-04008/C) used without Hub<br />
** KB-06XE (K639) (B)<br />
** LuxeMate i200 (GK-090017; not tested with Hub)<br />
** Slimstar 8000 wireless keyboard<br />
<br />
* '''Gigabyte'''<br />
** GK-KM7580 2.4&nbsp;GHz Wireless Multimedia Keyboard & Mouse<br />
<br />
* '''HP'''<br />
** KG-1061<br />
** KG-0851 Wireless Keyboard and Mouse<br />
** KU-0316 (B)<br />
** LV290AA#ABA Wireless Keyboard and Mouse<br />
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)<br />
** SK-2880<br />
<br />
* '''Hyundai'''<br />
** HY-K201<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Imation''' <br />
** KBD-702 Multi-media Wired Keyboard<br />
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)<br />
<br />
* '''IOGEAR'''<br />
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball<br />
** IOGEAR GKM681R 2.4&nbsp;GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel<br />
<br />
* '''iOne'''<br />
** Scorpius-K3NT (B)<br />
*** (sold by Newark as an 'official' RPi accessory, miniature keyboard with integrated trackball)<br />
<br />
* '''iPazzPort'''<br />
<br />
* '''i.t.works'''<br />
** KC04 (direct and by USB hub)<br />
** KC Silicone (only tested directly)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''KeySonic'''<br />
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Raspberry Pi. Also works with Raspbmc with powered hub.<br />
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub<br />
** ACK-3700C<br />
** ACK-340U+(DE)<br />
** ACK-3400U (UK) mini keyboard<br />
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi<br />
<br />
* '''Labtec'''<br />
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat Keyboard]<br />
<br />
* '''Laptopmate'''<br />
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad<br />
<br />
* '''LC-Power<br />
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4&nbsp;GHz Trackball Keyboard) tested with Debian 6.0.4<br />
<br />
* '''Lenovo'''<br />
** SK-8825 UK (B)<br />
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)<br />
** Lenovo Mini Wireless Keyboard N5901 (US)<br />
<br />
* '''Lindy'''<br />
** 21840 (Wireless RF 2.4&nbsp;GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.<br />
<br />
* '''Logik'''<br />
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''<br />
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver<br />
<br />
* '''Logitech'''<br />
** Comfort Wave 450, labeled 100&nbsp;mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)<br />
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)<br />
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)<br />
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)<br />
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine<br />
** Wii wireless keyboard KG-0802 (!)<br />
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)<br />
** Deluxe 250 Keyboard<br />
** Internet 350 (M/N 967740-0403)<br />
** Internet Navigator Keyboard<br />
** MK120 wired keyboard and mouse<br />
** MK220 wireless keyboard and mouse<br />
** MK250 wireless keyboard and mouse (no hub needed)<br />
** MK260 wireless keyboard and mouse (no hub needed)<br />
** MK300 wireless keyboard and mouse<br />
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]<br />
** MK350 wireless keyboard (using Unifying receiver)<br />
** MK520 wireless keyboard and mouse<br />
** MK550 wireless keyboard and mouse (B)<br />
** MX3200 wireless keyboard and mouse (B)<br />
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.<br />
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)<br />
** EX110 Cordless Desktop, wireless keyboard and mouse (B)<br />
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]<br />
** K120 Keyboard (B)<br />
** K200 Keyboard (B)<br />
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)<br />
** K310 Washable Keyboard<br />
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K350 Wireless Keyboard (B)<br />
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". <br />+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.<br />
** K520 Keyboard (B)<br />
** K700 Wireless Keyboard with Touchpad and unifying receiver<br />
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )<br />
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).<br />
** S510 wireless keyboard and mouse (B)<br />
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100&nbsp;mA. OK direct into Model B Raspberry Pi.<br />
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub in back of keyboard works too.<br />
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.<br />
** V470 Bluetooth Laser Mouse<br />
<br />
''Keyboards and mice also together with Unifying receiver'' <br />
<br />
* '''macally'''<br />
**macally iKey slim (IKEY5V2)<br />
<br />
* '''Medion'''<br />
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
**Microsoft Comfort Curve Keyboard 2000<br />
**Microsoft Comfort Curve Keyboard 3000 for Business<br />
**Microsoft Digital Media Pro Keyboard Model: 1031 (Debian 13-Apr-2012)<br />
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)<br />
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)<br />
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)<br />
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub<br />
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)<br />
**Microsoft Windows 2000 Keyboard (KB-USBK110610)<br />
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5&nbsp;V/100&nbsp;mA (Wheezy 5-Sept-2012)<br />
<br />
* '''Mikomi''' <br />
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the range is terrible less than a metre) (B)<br />
<br />
* '''Monoprice'''<br />
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.<br />
<br />
* '''Motorola'''<br />
<br />
** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)<br />
<br />
* '''ONN'''<br />
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.<br />
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.<br />
<br />
* '''Ortek'''<br />
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.<br />
<br />
* '''Perixx''' <br />
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)<br />
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.<br />
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)<br />
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.<br />
<br />
* '''Philips''' <br />
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)<br />
<br />
* '''Prodige'''<br />
**Nanox Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]<br />
<br />
* '''Rapoo'''<br />
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad<br />
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]<br />
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)<br />
<br />
*'''Riitek'''<br />
**RT-MWK03 mini wireless keyboard & trackpad<br />
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.<br />
**RT-MWK01 mini 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]<br />
<br />
*'''Rosewill'''<br />
** RK-200 Standard Keyboard<br />
<br />
*'''Saitek'''<br />
** Eclipse II Backlit Keyboard PK02AU (B)<br />
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.<br />
** Expression Keyboard (US) <br />
** Cyborg V.5 (B)<br />
<br />
*'''SelecLine'''<br />
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (B)<br />
<br />
*'''SIIG'''<br />
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)<br />
<br />
*'''Silvercrest'''<br />
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B) <br />
<br />
*'''SolidTek'''<br />
** Solid Tek KB-P3100BU ASK-3100U. <br />
<br />
*'''Sony'''<br />
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5&nbsp;V 1&nbsp;A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.<br />
<br />
* '''SteelSeries'''<br />
** Merc keyboard (B)<br />
<br />
* '''Sun Microsystems'''<br />
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)<br />
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard<br />
<br />
* '''Technika'''<br />
** WKEY03 (B)<br />
** TKD-211<br />
<br />
* '''Tesco'''<br />
** Value Keyboard VK109 (B)<br />
** Multimedia K211 Wired Keyboard (B)<br />
<br />
*'''The Pi Hut'''<br />
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.<br />
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)<br />
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard <br />
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087<br />
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.<br />
<br />
* '''Unbranded'''<br />
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller<br />
<br />
* '''Unicomp'''<br />
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub<br />
<br />
* '''Q-Connect'''<br />
** AK-808 (B)<br />
<br />
* '''Xenta'''<br />
** 2.4&nbsp;GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)<br />
** Mini Multimedia Keyboard (Model no.: 808M) (B)<br />
<br />
===Problem USB Keyboards===<br />
<br />
Note that generally PS/2 keyboards with an USB adapter will not work directly on a Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5&nbsp;V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry Pi may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0&nbsp;V. Some of these keyboards work when running the latest Raspbian, but not when using the overclocked XBMC version of Raspbmc, probably due to the overclocking drawing more power away from the rest of the support system devices.<br />
<br />
* '''A4 Tech'''<br />
** Model GL-6 USB Keyboard, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''Accuratus'''<br />
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100&nbsp;mA). Tested with 1000&nbsp;mA cheap unbranded and Nokia 1200&nbsp;mA power adaptors.<br />
* '''Apple'''<br />
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub. <br />
*'''Argos'''<br />
** Argos Value Wired Keyboard causes kernel panic<br />
* '''Choidy'''<br />
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic<br />
* '''Cit''' <br />
** KB-1807UB Causes kernel panic (rated <200&nbsp;mA)<br />
* '''Dell'''<br />
** SK-8135 (B) (Rated 1.5&nbsp;A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)<br />
** SK-8115 causes kernel panic (rated 100&nbsp;mA) Debian 6-19-04-2012 (B)<br />
** Y-U0003-DEL5 Sticky / Non-responsive keys<br />
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V<br />
* '''Gear Head'''<br />
** KB2300U - Causes kernel panic (B)<br />
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)<br />
* '''GMYLE'''<br />
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]<br />
* '''Inland''' <br />
** Inland USB Keyboard Model #70010<br />
* '''Jeway'''<br />
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)<br />
* '''Labtec'''<br />
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
* '''Logik'''<br />
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)<br />
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''<br />
* '''Logitech'''<br />
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)<br />
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)<br />
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)<br />
** K360 Wireless Keyboard - Occasional sticky keys. (B)<br />
** MK 260 Wireless Keyboard - Occasional sticky keys. (B)<br />
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)<br />
** G510 Gaming Keyboard - lagging or unresponsive keys.<br />
** MX5500 wireless keyboard and mouse with USB Bluetooth receiver - Unstable, looses connection without prior notice<br />
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).<br />
* '''Microsoft''' <br />
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)<br />
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)<br />
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.<br />
** Arc wireless - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)<br />
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)<br />
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000&nbsp;mA power supply unit)<br />
* '''Novatech'''<br />
** NOV-KEY2 - Causes kernel panic (B)<br />
* '''PC World Essentials'''<br />
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it caused a kernel panic -- tested on powered hub and direct.<br />
* '''Razer'''<br />
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.<br />
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED).<br />
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5&nbsp;V 500&nbsp;mA. (B)<br />
* '''SIIG'''<br />
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.<br />
* '''Texet'''<br />
** MB-768B standard keyboard (Rated 5&nbsp;V 1.5&nbsp;A (!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)<br />
* '''Trust''' <br />
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.<br />
* '''Unbranded'''<br />
** Compuparts<br />
** model no. HK-6106 (B)<br />
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.<br />
* '''Verbatim'''<br />
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)<br />
* '''Wilkinsons / TEXET'''<br />
** Model MB-768B causes kernel panic on debian6-19-04-2012.<br />
* '''Xenta'''<br />
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)<br />
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems. <br />
<br />
===Working USB Mouse Devices===<br />
The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* '''A4Tech'''<br />
** OP-530NU Padless Wired Mouse<br />
<br />
* '''Apple'''<br />
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).<br />
<br />
* '''Asda'''<br />
** HM5058 (Smart Price) Wired Mouse<br />
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> mouse)<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''ASUS'''<br />
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)<br />
** MG-0919 (wireless)<br />
<br />
* '''Belkin'''<br />
** F8E882-OPT (B)<br />
<br />
* '''Cellink'''<br />
** OPM-602 Small wireless optical mouse<br />
<br />
* '''Cerulian Technology'''<br />
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA<br />
<br />
* '''Dell'''<br />
** M-UVDEL1 (B)<br />
** MOC5UO (100&nbsp;mA)<br />
** M056U0A (B)<br />
** DZL-MS111-L (B) (100&nbsp;mA)<br />
** MS-111P (100&nbsp;mA)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.<br />
<br />
* '''Dynex'''<br />
** DX-WMSE (100&nbsp;mA) (B)<br />
<br />
* '''Fellowes'''<br />
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (B)<br />
<br />
* '''Filand'''<br />
** OP-102i Mini Optical Mouse<br />
<br />
* '''Genius'''<br />
** GM-04003A (B)<br />
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)<br />
** Traveler 515 Laser<br />
<br />
* '''HP'''<br />
** MN-UAE96 (The basic stock HP wired mouse)(B)<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''Kensington'''<br />
** Kensington Expert Mouse Trackball K64325<br />
** Kensington Expert Mouse "Slimblade" K72327US<br />
<br />
* '''Labtec'''<br />
** Corded Laser Glow Mouse 1600, rated 5&nbsp;V 100&nbsp;mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)<br />
<br />
* '''Lenovo'''<br />
** Wired Optical Mouse Model: MO28UOL<br />
<br />
* '''Logik'''<br />
** Wired Optical Glow Mouse Model: LGGMO10. (B)<br />
<br />
* '''Logitech'''<br />
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)<br />
** B105 Mouse for Laptops (OEM)<br />
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE<br />
** G5 Logitech Gaming Mouse (B)<br />
** G5v2 Logitech Gaming Mouse (B)<br />
** G500 Logitech Gaming Mouse (B)<br />
** G700 Logitech Wireless Gaming Mouse (B)<br />
** LX-700 Cordless Desktop Receiver (B)<br />
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).<br />
** M90 optical mouse<br />
** M185 Wireless Mouse (B)<br />
** M210 (part of the MK260 set) (B)<br />
** M305 Wireless Mouse<br />
** M310 Cordless Mouse<br />
** M325 Wireless Mouse<br />
** M505 USB wireless laser, model no: 910-001324 (B)<br />
** M510 Wireless Mouse (B)<br />
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)<br />
** M-BD58 Wheel Mouse (B)<br />
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)<br />
** M-BJ79 (B)<br />
** M-BT96a Optical Mouse<br />
** MX320/MX400 laser mouse (B)<br />
** MX518 Optical wheel mouse (B)<br />
** Optical USB Mouse (M/N 931643-0403)<br />
** Performance Mouse MX (B)<br />
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)<br />
** VX Nano Cordless Laser Mouse for Notebooks<br />
** Wheel Mouse (M/N BJ58)<br />
<br />
* '''Medion'''<br />
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5&nbsp;V 100&nbsp;mA. Works fb on model B with Raspbian Wheezy<br />
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
** Comfort Curve Mouse 3000 for Business<br />
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).<br />
** Compact optical mouse 500 V2.0 (B)<br />
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)<br />
** Microsoft Intellimouse Optical Mouse<br />
** Microsoft Wireless Laser Mouse 8000<br />
** Microsoft Wireless Mobile Mouse 1000<br />
** Microsoft Wireless Mobile Mouse 3500<br />
** Microsoft Wireless Mobile Mouse 4000<br />
** Microsoft Wireless Mouse 700 v2.0<br />
** Microsoft Comfort Mouse 4500<br />
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)<br />
<br />
* '''Perixx'''<br />
** PERIMICE-210 U Red (Part No.R1J) <br />
<br />
* '''Razer'''<br />
** Boomslang Collectors Edition 2007 (B)<br />
<br />
* '''Rosewill'''<br />
** Rosewill RM-C2U<br />
<br />
* '''Saitek'''<br />
** Notebook Optical Mouse (PM46)<br />
<br />
* '''Samsung'''<br />
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50&nbsp;mA) <br />
<br />
* '''Sun microsystems'''<br />
** Model: FID-638 , SunPN: 371-0788-01<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]<br />
<br />
* '''Swiftpoint'''<br />
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.<br />
<br />
* '''Targus'''<br />
** AKM02UK (Associated keyboard not checked)<br />
** AMU2701EUK (B)<br />
<br />
* '''Technika'''<br />
** TKOPTM2 (B)<br />
**TKD-211<br />
**TKNM110<br />
<br />
* '''Tesco'''<br />
** Wired optical mouse M211 (B)<br />
<br />
*'''The Pi Hut'''<br />
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Model 15313 - large, 5-button wireless mouse<br />
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base<br />
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)<br />
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087<br />
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.<br />
<br />
* '''Verbatiam'''<br />
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)<br />
<br />
* '''Xenta'''<br />
** MOW0810 (B)<br />
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Generic'''<br />
** Generic 2.4&nbsp;GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)<br />
<br />
===Problem USB Mouse Devices===<br />
The following is a list of specific mouse devices that have problems working with the Raspberry Pi<br />
* '''A4Tech'''<br />
** Model G7-630 Wireless Mouse, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''HP'''<br />
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors. <br />
<br />
* '''Logik'''<br />
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)<br />
<br />
* '''Logitech'''<br />
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000&nbsp;Hz out of the box, whereas the 518 is only 125&nbsp;Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.<br />
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot<br />
<br />
* '''Microsoft'''<br />
** Microsoft Touch Mouse - Does not see right clicks, Only left.<br />
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.<br />
<br />
* '''Razer'''<br />
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works, but the cursor doesn't move.<br />
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus<br />
<br />
* '''Roccat'''<br />
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)<br />
<br />
* '''Trust'''<br />
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)<br />
<br />
* '''Xenta'''<br />
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle<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 />
== USB Wi-Fi Adapters ==<br />
<br />
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. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.<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.<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 />
* '''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. <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.<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 />
<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 />
* '''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 Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)<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-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. Important : revision A1 works, revision B1 does not. Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<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-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.<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 />
*** 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 />
** [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 />
<br />
* '''Hawking'''<br />
** HWU54G rev. Z2 (802.11g) (B). Requires "zd1211-firmware" package.<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 />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<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 />
<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].<br />
<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 />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.<br />
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module<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 supports Access Point and it be used for hostapd <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)<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: 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 />
* '''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 (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-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.<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-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 />
<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 />
** [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)<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 />
* '''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 />
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].<br />
<br />
== USB Bluetooth adapters ==<br />
===Working Bluetooth adapters===<br />
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote<br />
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.<br />
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)<br />
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)<br />
** Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.<br />
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.<br />
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288<br />
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.<br />
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.<br />
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian<br />
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian<br />
** Azio BTD-V400. CSR BC8 radio, bluetooth 4.0. Tested with Raspbian using powered USB hub<br />
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip<br />
** http://www.element14.com/community/message/58288<br />
* IOGear GBU321 (Broadcom BCM2045 Chipset)<br />
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.<br />
* Trust BT-2400p<br />
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).<br />
<br />
===Working Bluetooth/Wifi Combo adapters===<br />
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)<ref>http://www.lindy.co.uk/shop/showProductDetail.do?orderNumber=52213</ref><br />
<br />
===Problem Bluetooth adapters===<br />
* '''Belkin'''<br />
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.<br />
* '''Generic'''<br />
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.<br />
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.<br />
* Asus USB-BT211<br />
** Shows up as HCI device in Raspbian, but it does not scan or pair.<br />
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962<br />
<br />
== USB Ethernet adapters ==<br />
===Working Ethernet adapters===<br />
* '''AVM'''<br />
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.<br />
* '''Wintech'''<br />
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100&nbsp;mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]<br />
* '''LogiLink'''<br />
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.<br />
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed<br />
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter <br />
* '''Apple'''<br />
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.<br />
* '''Edimax'''<br />
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.<br />
* '''D-Link'''<br />
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)<br />
* '''LinkSys'''<br />
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.<br />
* '''Sabrent'''<br />
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)<br />
* '''Sitecom'''<br />
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.<br />
* '''A-Link'''<br />
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter<br />
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.<br />
<br />
The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190&nbsp;mA, so there might be stability issues if additional power is not provided.<br />
* '''Hama'''<br />
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.<br />
* '''Newlink'''<br />
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.<br />
<br />
===Problem Ethernet adapters===<br />
* Axago<br />
** Axago ADE-X1 10/100 Ethernet Adapter (USB: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out<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 />
* '''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://www.ti.com/product/pcm2704 PCM2704 98&nbsp;dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]<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 />
==USB 3G Dongles==<br />
* Huawei E1750<br />
* Huawei E173<br />
* Huawei E1820 Works on Raspbian with Sakis3G<br />
* Huawei E220<br />
* Huawei E353 HiLink Works on Raspbian<br />
* Huawei E160 (AT commands only)<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 />
<br />
== USB IR Receivers==<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, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.<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)<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 />
*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 Webcams ==<br />
<br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
|PD1030<br />
|<br />
|<br />
|<br />
|<br />
|ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Hercules<br />
|Webcam Deluxe<br />
|<br />
|05a9:4519<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|ov519 driver "Corrupt JPEG data: premature end of data segment" gives corrupt image in motion and fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|WebcamHD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C270<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| With external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|046d:0826<br />
|<br />
| <br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| With powered hub, detected out of box as Video0 V4L device<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Messenger<br />
|V-UM14<br />
|046d:08f0<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|Not working, STV06xx driver "ioctl (VIDIOCGCAP): Inappropriate ioctl for device", Supported palettes: GRBG, gives corrupt image in fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Picture breaks up at the bottom<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
| <br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Up to 352x288. Higher resolutions do not work. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|Xbox Live Vision<br />
| <br />
| 045e:0294<br />
| Arch Linux <br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| toucam<br />
| Philips 720K/40 webcam<br />
| 0471:0313<br />
| Raspbian Wheezy<br />
| 2013-04-03<br />
| 320x240<br />
| Recognised as lsusb ID 0471:0329 Philips (or NXP). Works with $> guvcview -s 320x240 -f yv12 -t 5 -n rec5sec.mkv --exit_on_close --no_display, but not with command $> fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| The occasional frame is corrupted/stutters when running at 640x480<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| works out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| Spotlight<br />
| <br />
| 0c45:62c0<br />
| Raspbian/Wheezy<br />
| <br />
| 640x480 <br />
| Works out of the box. Tested with power direct from the Raspberry Pi, not tested on a hub. <br />
<br />
<br />
|-<br />
|}<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. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually<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 />
<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 />
== 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 />
=== 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 />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<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 SATA ===<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 />
<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 />
<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 />
=== 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 (Lazerus), 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 />
== 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 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 adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.<br />
<br />
===Working power Adapters===<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 />
** 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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''The Pi Hut'''<br />
** Micro USB Power Supply for the Raspberry Pi. 5&nbsp;V 1000&nbsp;mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])<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 />
* '''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 />
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 />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.<br />
<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 />
http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the Raspberry Pi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1&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 "Burning Raspberry!" 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 />
<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 />
http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=4<br />
<br>config_hdmi_boost=4<br />
<br>overscan_top=-30<br />
<br>overscan_bottom=-30<br />
<br>overscan_left=-30<br />
<br>overscan_right=-30<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 />
According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
<br />
According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but it is very pricey compared to the alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4&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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"<br />
<br />
Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=16<br />
<br>hdmi_force_hotplug=1<br />
<br>disable_overscan=0<br />
<br />
<br />
And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. It is very cheap, but it works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC). <br />
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.<br />
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 />
Marcin.<br />
<br />
<br />
Newark/element14 sells the "Pi-View" HDMI-VGA converter specifically for use with the Raspberry Pi. It does work although the small box gets warm and the video output isn't great (slightly fuzzy text, smaller screen area even with overscan enabled):<br />
<br />
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 />
== 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>AutoStatichttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=237692RPi VerifiedPeripherals2013-04-03T18:09:10Z<p>AutoStatic: /* Working USB to Serial Adapters */</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 />
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.<br />
<br />
If you use a powered hub and the Raspberry Pi PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100&nbsp;mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).<br />
<br />
===Working USB Hubs===<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''USB Version'''<br />
| '''Number of Ports'''<br />
| '''Power Rating*'''<br />
| '''Powers Raspberry Pi'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Atlantis<br />
|HUB USB2.0 7P<br />
|P014-GH902-B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2&nbsp;A<br />
|Verified<br />
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|4-Port Ultra-Slim Desktop Hub<br />
|F4U040<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.6&nbsp;A<br />
|Verified<br />
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|8-Port ExpressBus for iMac<br />
|F5U010<br />
|<br />
|USB 2.0<br />
|8-Port 7x"A" 1x"B"<br />
|<br />
|Verified<br />
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U224<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|TetraHub™ USB 2.0 4-Port Hub<br />
|F5U231<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U234<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|No backfeed, can power the RPi. Comes with a 2.4&nbsp;A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''&ldquo;Per Port Current Self-Powered Mode: 500mA (max)&rdquo;''. However, I've attached a HD that requires 850&nbsp;mA and it worked fine.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.8&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|MyEssentials 7-Port High-Speed USB 2.0 Hub<br />
|F5U259-ME<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Lighted Hub<br />
|F5U403<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Lighted Hub<br />
|F5U700<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hub 2-en-1<br />
|F5U706ea<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237v1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2.5&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U040v<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5 V - 2.6 A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U039qukAPL<br />
|05e3:0608<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Benq<br />
|<br />
|E2220HD<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|BUFFALO<br />
|4 Port Hub<br />
|BSH4aAE06<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V <br />
|Verified<br />
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Cyberpower<br />
|High-speed Hub<br />
|CP-H720P<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|3.6&nbsp;A<br />
|Verified<br />
|May Contain dual 05e3:0608 instead of 0409:0050<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2001FP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|SP2309W<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2407FWP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|U3011<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub - Card Reader Works - May work with SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|<br />
|B/N61393<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|USB 2.0 External Hub 7 Port<br />
|B/N87467<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.5&nbsp;A<br />
|Verified<br />
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Deltaco<br />
|<br />
|UH-715 Rev 2<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|<br />
|<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|Dynex USB 2.0 7 Port Hub<br />
|DX-HB7PT<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5.0&nbsp;V / 2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|D-Link 7 Port USB Hub<br />
|DUB-H7/B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7 High Speed USB 2.0 7-Port Hub<br />
|BUBH7A A5<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7<br />
|EUBH7EB H/W Ver:B1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI<br />
<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-4 High Speed USB 2.0 4-Port Hub<br />
|DUB-H4<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Digicom<br />
|<br />
|<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|ednet<br />
|USB 2.0 7 port Hub<br />
|85014<br />
|<br />
|2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|Works with keyboard, mouse, audio devices<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GigaWare<br />
|USB 2.0 4 port Hub<br />
|Model 26-160<br />
|<br />
|2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|König Electronic<br />
|7 port USB2.0 HUB<br />
|CMP-USB2HUB55<br />
|1a40:0201<br />
|2.0<br />
|7-Port<br />
|2.0A<br />
|Verified<br />
|Backpowers Raspberry Pi well.<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medi@com<br />
|USB 2.0 4 ports Hub<br />
|M-HX30<br />
|<br />
|2.0<br />
|4-port<br />
|<br />
|Verified<br />
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.<br />
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|mbeat<br />
|13 Port USB Hub<br />
|USB-M13HUB<br />
|<br />
|USB 2.0<br />
|13-port<br />
|5V - 3A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Monoprice<br />
|Aquagate USB Hub<br />
|5328<br />
|<br />
|2.0<br />
|7-port<br />
|2.0&nbsp;A<br />
|Verified<br />
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable <br />
|7 Port High Speed USB Hub<br />
|USB2-HUB-AG7<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 3A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable<br />
|4 Port Hub with Battery Charging 1.1 Support<br />
|USB2-HUB4BC<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5V - 2.5A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|10 Port USB 2.0 Hub<br />
|USB2-HUB10S<br />
|<br />
|USB 2.0<br />
|10-Port<br />
|5V - 2.5A<br />
|Not Verified<br />
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|4 Port USB 3.0 Hub<br />
|USB2-HUB-81X4<br />
|<br />
|USB 3.0<br />
|4-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|7 Port USB 3.0 Hub<br />
|USB2-HUB7-81X<br />
|<br />
|USB 3.0<br />
|7-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
|Plata 4 port USB 2.0 hub<br />
|18687<br />
|<br />
|2.0<br />
|4-port<br />
|1.0&nbsp;A<br />
|Not Verified<br />
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Zipp<br />
|USB 7-Port HUB<br />
|N294<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 2.0A<br />
|Verified<br />
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)<br />
<br />
|-<br />
|}<br />
<br />
<br />
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.<br />
</div><br />
<br />
<br />
*'''Acme'''<br />
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but it is very cheap and small and works after a small modding: on USB-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the Raspberry Pi, and additionally connect GND and +5&nbsp;V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.<br />
<br />
<br />
*'''Digitus'''<br />
** 7-port USB2.0 Powered Hub. Model DA-70226.<br />
*'''Eminent'''<br />
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
* '''GearHead'''<br />
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5&nbsp;V, 1&nbsp;A)<br />
*'''Gembird'''<br />
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.<br />
* '''Genesys Logic (sold at Fry's)'''<br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref><br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)<br />
* '''Hama'''<br />
** Hama 4-way USB 2.0 Hub<br />
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)<br />
*'''HP'''<br />
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)<br />
<br />
*'''Laser'''<br />
** "7 port USB hub with AC adapter Version 2.0". 5&nbsp;V 1&nbsp;A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry Pi USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.<br />
*'''Logik'''<br />
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''<br />
** Logik L4THUB10 4 Port powered hub works fine under Raspbian/Wheezy/model B. Captive USB cable, 2&nbsp;A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!<br />
*'''LogiLink'''<br />
** UA0085 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0090 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0091 USB 3.0 Hub, 4-Port with PSU 5&nbsp;V, 4&nbsp;A. Connected with USB2.0 cable. 1&nbsp;A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy. <br />
** UA0096 USB 2.0 Hub, 10-Port with PSU 5&nbsp;V, 3.5&nbsp;A (Not suitable for powering Raspberry Pi because it doesn't work unless there is working USB input present even with PSU plugged in.)<br />
** UA0160 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.<br />
* '''Macally'''<br />
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000&nbsp;mA wall-wart (US style)<br />
* '''Manhattan'''<br />
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000&nbsp;mA wall-wart (US style)<br />
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500&nbsp;mA each) + (4 USB 3.0 Ports @900&nbsp;mA each) Power Switches on each port, AC Powered and Includes a 5&nbsp;V 4&nbsp;A wall-wart (US style)<br />
*'''Newlink'''<br />
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5&nbsp;V 1&nbsp;A<br />
** NLUSB2-222P 4 port USB 2.0 Hub with 5&nbsp;V 2&nbsp;A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])<br />
*'''Nilox'''<br />
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5&nbsp;V 1.0&nbsp;A<br />
* '''Plugable'''<br />
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5&nbsp;V 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.<br />
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port.<br />
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5&nbsp;V 3&nbsp;A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)<br />
<br />
* '''Pluscom'''<br />
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3&nbsp;A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.<br />
*'''Satechi'''<br />
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.<br />
*'''Staples (Business Depot) (Bureau EN GROS)'''<br />
** Staples 4-port hub Item 607477-CA<br />
*'''StarTech.com'''<br />
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5&nbsp;V 2&nbsp;A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).<br />
*'''SumVision'''<br />
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5&nbsp;V 1.0&nbsp;A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])<br />
*'''Sitecom'''<br />
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Raspberry Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500&nbsp;mA Voltcraft <br />
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1&nbsp;A). Powering Raspberry Pi via microUSB from a hub port.<br />
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
*'''Sweex'''<br />
** US014 4 Port USB 2.0 Hub<br />
*'''Targus'''<br />
** ACH81xx 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)<br />
** ACH63EU 4-port. Using a 5&nbsp;V 2&nbsp;A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.<br />
*'''The Pi Hut'''<br />
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
*'''Trendnet'''<br />
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2&nbsp;A)<br />
*'''Tripp-Lite'''<br />
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2.5&nbsp;A) Powering Raspberry Pi from the hub works.<br />
*'''Ultron'''<br />
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5&nbsp;V, 3&nbsp;A. USB ID 1a40:0201.<br />
*'''VANTEC'''<br />
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5&nbsp;V 2&nbsp;A AC/DC adapter. Go 2.0 Mini hub.<br />
*'''Z-TEK'''<br />
** Z-TEK 7-port powered hub with PSU 5&nbsp;V, 4&nbsp;A. USB ID 1a40:0201.<br />
*"Unknown"<br />
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works<br />
<br />
===Problem USB Hubs===<br />
<br />
Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list<br />
<br />
*'''Addon'''<br />
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.<br />
*'''Belkin'''<br />
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5&nbsp;V pinouts)<br />
** F4U022 7-Port powered USB hub (powered 5&nbsp;V, 2.6&nbsp;A), same as F4U018<br />
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired Ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.<br />
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.<br />
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes. (Works always without powering the Raspberry Pi, haven't tried that)<br />
<br />
*'''Dell'''<br />
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.<br />
<br />
*'''DELTACO'''<br />
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills Ethernet when X11 is started.<br />
<br />
*'''Dynex'''<br />
** 7-Port USB Hub - Does not work in Debian 19-04 image.<br />
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.<br />
<br />
*'''Dynamode'''<br />
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).<br />
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1&nbsp;A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification. <br />
<br />
*'''D-Link'''<br />
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)<br />
<br />
*'''E-Solution'''<br />
** 4-Port 2&nbsp;A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]<br />
<br />
*'''Fosmon'''<br />
** 7-Port USB 2.0 Hub with 1&nbsp;A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry Pi with it's Micro USB cable unplugged).<br />
<br />
*'''Gear Head'''<br />
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.<br />
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.<br />
<br />
*'''Hama'''<br />
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608<br />
<br />
*'''Kensington'''<br />
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).<br />
<br />
*'''iBall'''<br />
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.<br />
<br />
*'''Inland'''<br />
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)<br />
<br />
*'''Logik'''<br />
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)<br />
<br />
*'''LogiLink'''<br />
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.<br />
<br />
*'''Soniq'''<br />
** 4-Port 5&nbsp;V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).<br />
<br />
*'''Targus'''<br />
** ACH115EU 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.<br />
<br />
*'''TCM'''<br />
** Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1&nbsp;A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi no connects. (insufficient power?)<br />
<br />
*'''Trust'''<br />
** 10-port USB 2.0 Hub (powered). Prevents Ethernet from being recognised.<br />
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents Ethernet from being recognised. Keyboard sends multiple characters. <br />
<br />
*'''Unbranded / Multiple Brands'''<br />
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.<br />
** Generic 7-port black hub with Genesys Logic GL850A chipset<br />
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2&nbsp;A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref><br />
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but there are strange USB failures when X session started. High speed devices such as hard drives had failures.<br />
<br />
== USB Remotes ==<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 />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''<br />
=== Working USB Keyboards ===<br />
The following is a list of specific keyboards known to work and which appear to work fault-free.<br />
<br />
* '''A4 Tech'''<br />
** Model KL-5 USB Keyboard, 20&nbsp;mA.<br />
<br />
* '''ABS'''<br />
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)<br />
<br />
* '''Action Star'''<br />
** ACK-5010U Mini Keyboard And Mouse<br />
<br />
* '''Accuratus'''<br />
** KYB-Toughball-HI<br />
<br />
* '''Acer'''<br />
** KG-0917 Wireless Keyboard And Mouse Bundle (B)<br />
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)<br />
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)<br />
<br />
* '''Adesso'''<br />
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100&nbsp;mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.<br />
** Model AKB-410UB. Keyboard with Touchpad.<br />
<br />
* '''Apple''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))<br />
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]<br />
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]<br />
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]<br />
<br />
* '''Asda'''<br />
** Basic Wired Keyboard HK2026 (B)<br />
** Basic Wired Keyboard HK3014<br />
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)<br />
** Premium Wireless Keyboard (white keys, silver back) HK8028<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''Asus'''<br />
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)<br />
<br />
* '''Banbridge'''<br />
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)<br />
<br />
* '''BTC - Behavior Tech Computer Corp.'''<br />
** Wired Portable Keyboard Model 6100 US (86+9 keys)<br />
*** Works with or without a powered hub<br />
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)<br />
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5&nbsp;V/100&nbsp;mA, works directly<br />
<br />
* '''Bush'''<br />
** Wired Slimline Keyboard KU-0833<br />
*** This does not require a USB hub in order to work with the Raspberry Pi<br />
*** In the UK, it is available from Argos for £9.99<br />
<br />
* '''Cerulian''' <br />
** Mini wireless keyboard and mouse deskset (B)<br />
<br />
* '''CD Training''' <br />
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]<br />
<br />
* '''Cherry'''<br />
** CyMotion Master Linux (B)<br />
** RS 6000 USB ON<br />
** G84-4100PTMUS (B) (Compact keyboard. Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** G85-23100DE-2 (B) (Rated 40&nbsp;mA, tested with RPi powered by a 1000&nbsp;mA power supply unit)<br />
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.<br />
<br />
* '''Compaq'''<br />
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5&nbsp;V 100&nbsp;mA. Works directly connected to Raspberry Pi<br />
<br />
* '''Das Keyboard'''<br />
** Model S Professional Keyboard (Built in USB hub not tested) (B)<br />
** Model S Ultimate Keyboard (Built in USB hub working) (B)<br />
<br />
* '''Dell'''<br />
** SK-8115 (B) (Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** L100 (B)<br />
** RT7D40 (100&nbsp;mA. Works directly in Raspberry Pi)<br />
** RT7D50 (75&nbsp;mA) (run "sudo dpkg-reconfigure keyboard-configuration")<br />
** KB1421 (100&nbsp;mA)<br />
** KB2521 (100&nbsp;mA)<br />
** KB212-B (Works directly in Raspberry Pi, without powered hub)<br />
** 1HF2Y (Works directly in Raspberry Pi)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** USB Keyboard 413c:2107 - Works with and without USB hub<br />
<br />
* '''Delux'''<br />
** K8050<br />
<br />
* '''Digicom'''<br />
** WKEYPE01 Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]<br />
<br />
* '''Dynex'''<br />
** DX_-WKBD (60&nbsp;mA) (B)<br />
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)<br />
<br />
* '''EAPPLY'''<br />
** EBO-013 Wireless 2.4&nbsp;GHz compact keyboard with touchpad. Rated <40&nbsp;mA works directly from Raspberry Pi. eBay ref 260962010276 from Shenzen, China.<br />
<br />
* '''Emprex'''<br />
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)<br />
<br />
* '''Fujitsu Siemens''' <br />
** KB SC USB UK (!)<br />
** KB910 USB, with led light on the highest level (B)<br />
** KB400 USB US<br />
<br />
* '''GE''' <br />
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)<br />
<br />
* '''Gear Head''' <br />
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)<br />
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)<br />
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)<br />
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported >> also see Problem USB Keyboards<br />
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)<br />
** KB1500U (USB Mini Keyboard) (B)<br />
** KB5150 (2.4&nbsp;GHz wireless keyboard/mouse Combo) (B)<br />
*** Works well with a powered hub<br />
<br />
* '''Generic'''<br />
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.<br />
<br />
* '''Genius'''<br />
** Ergomedia 700 (GK-04008/C) used without Hub<br />
** KB-06XE (K639) (B)<br />
** LuxeMate i200 (GK-090017; not tested with Hub)<br />
** Slimstar 8000 wireless keyboard<br />
<br />
* '''Gigabyte'''<br />
** GK-KM7580 2.4&nbsp;GHz Wireless Multimedia Keyboard & Mouse<br />
<br />
* '''HP'''<br />
** KG-1061<br />
** KG-0851 Wireless Keyboard and Mouse<br />
** KU-0316 (B)<br />
** LV290AA#ABA Wireless Keyboard and Mouse<br />
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)<br />
** SK-2880<br />
<br />
* '''Hyundai'''<br />
** HY-K201<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Imation''' <br />
** KBD-702 Multi-media Wired Keyboard<br />
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)<br />
<br />
* '''IOGEAR'''<br />
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball<br />
** IOGEAR GKM681R 2.4&nbsp;GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel<br />
<br />
* '''iOne'''<br />
** Scorpius-K3NT (B)<br />
*** (sold by Newark as an 'official' RPi accessory, miniature keyboard with integrated trackball)<br />
<br />
* '''iPazzPort'''<br />
<br />
* '''i.t.works'''<br />
** KC04 (direct and by USB hub)<br />
** KC Silicone (only tested directly)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''KeySonic'''<br />
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Raspberry Pi. Also works with Raspbmc with powered hub.<br />
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub<br />
** ACK-3700C<br />
** ACK-340U+(DE)<br />
** ACK-3400U (UK) mini keyboard<br />
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi<br />
<br />
* '''Labtec'''<br />
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat Keyboard]<br />
<br />
* '''Laptopmate'''<br />
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad<br />
<br />
* '''LC-Power<br />
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4&nbsp;GHz Trackball Keyboard) tested with Debian 6.0.4<br />
<br />
* '''Lenovo'''<br />
** SK-8825 UK (B)<br />
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)<br />
** Lenovo Mini Wireless Keyboard N5901 (US)<br />
<br />
* '''Lindy'''<br />
** 21840 (Wireless RF 2.4&nbsp;GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.<br />
<br />
* '''Logik'''<br />
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''<br />
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver<br />
<br />
* '''Logitech'''<br />
** Comfort Wave 450, labeled 100&nbsp;mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)<br />
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)<br />
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)<br />
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)<br />
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine<br />
** Wii wireless keyboard KG-0802 (!)<br />
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)<br />
** Deluxe 250 Keyboard<br />
** Internet 350 (M/N 967740-0403)<br />
** Internet Navigator Keyboard<br />
** MK120 wired keyboard and mouse<br />
** MK220 wireless keyboard and mouse<br />
** MK250 wireless keyboard and mouse (no hub needed)<br />
** MK260 wireless keyboard and mouse (no hub needed)<br />
** MK300 wireless keyboard and mouse<br />
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]<br />
** MK350 wireless keyboard (using Unifying receiver)<br />
** MK520 wireless keyboard and mouse<br />
** MK550 wireless keyboard and mouse (B)<br />
** MX3200 wireless keyboard and mouse (B)<br />
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.<br />
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)<br />
** EX110 Cordless Desktop, wireless keyboard and mouse (B)<br />
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]<br />
** K120 Keyboard (B)<br />
** K200 Keyboard (B)<br />
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)<br />
** K310 Washable Keyboard<br />
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K350 Wireless Keyboard (B)<br />
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". <br />+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.<br />
** K520 Keyboard (B)<br />
** K700 Wireless Keyboard with Touchpad and unifying receiver<br />
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )<br />
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).<br />
** S510 wireless keyboard and mouse (B)<br />
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100&nbsp;mA. OK direct into Model B Raspberry Pi.<br />
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub in back of keyboard works too.<br />
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.<br />
** V470 Bluetooth Laser Mouse<br />
<br />
''Keyboards and mice also together with Unifying receiver'' <br />
<br />
* '''macally'''<br />
**macally iKey slim (IKEY5V2)<br />
<br />
* '''Medion'''<br />
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
**Microsoft Comfort Curve Keyboard 2000<br />
**Microsoft Comfort Curve Keyboard 3000 for Business<br />
**Microsoft Digital Media Pro Keyboard Model: 1031 (Debian 13-Apr-2012)<br />
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)<br />
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)<br />
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)<br />
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub<br />
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)<br />
**Microsoft Windows 2000 Keyboard (KB-USBK110610)<br />
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5&nbsp;V/100&nbsp;mA (Wheezy 5-Sept-2012)<br />
<br />
* '''Mikomi''' <br />
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the range is terrible less than a metre) (B)<br />
<br />
* '''Monoprice'''<br />
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.<br />
<br />
* '''Motorola'''<br />
<br />
** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)<br />
<br />
* '''ONN'''<br />
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.<br />
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.<br />
<br />
* '''Ortek'''<br />
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.<br />
<br />
* '''Perixx''' <br />
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)<br />
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.<br />
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)<br />
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.<br />
<br />
* '''Philips''' <br />
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)<br />
<br />
* '''Prodige'''<br />
**Nanox Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]<br />
<br />
* '''Rapoo'''<br />
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad<br />
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]<br />
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)<br />
<br />
*'''Riitek'''<br />
**RT-MWK03 mini wireless keyboard & trackpad<br />
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.<br />
**RT-MWK01 mini 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]<br />
<br />
*'''Rosewill'''<br />
** RK-200 Standard Keyboard<br />
<br />
*'''Saitek'''<br />
** Eclipse II Backlit Keyboard PK02AU (B)<br />
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.<br />
** Expression Keyboard (US) <br />
** Cyborg V.5 (B)<br />
<br />
*'''SelecLine'''<br />
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (B)<br />
<br />
*'''SIIG'''<br />
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)<br />
<br />
*'''Silvercrest'''<br />
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B) <br />
<br />
*'''SolidTek'''<br />
** Solid Tek KB-P3100BU ASK-3100U. <br />
<br />
*'''Sony'''<br />
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5&nbsp;V 1&nbsp;A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.<br />
<br />
* '''SteelSeries'''<br />
** Merc keyboard (B)<br />
<br />
* '''Sun Microsystems'''<br />
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)<br />
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard<br />
<br />
* '''Technika'''<br />
** WKEY03 (B)<br />
** TKD-211<br />
<br />
* '''Tesco'''<br />
** Value Keyboard VK109 (B)<br />
** Multimedia K211 Wired Keyboard (B)<br />
<br />
*'''The Pi Hut'''<br />
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.<br />
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)<br />
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard <br />
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087<br />
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.<br />
<br />
* '''Unbranded'''<br />
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller<br />
<br />
* '''Unicomp'''<br />
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub<br />
<br />
* '''Q-Connect'''<br />
** AK-808 (B)<br />
<br />
* '''Xenta'''<br />
** 2.4&nbsp;GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)<br />
** Mini Multimedia Keyboard (Model no.: 808M) (B)<br />
<br />
===Problem USB Keyboards===<br />
<br />
Note that generally PS/2 keyboards with an USB adapter will not work directly on a Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5&nbsp;V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry Pi may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0&nbsp;V. Some of these keyboards work when running the latest Raspbian, but not when using the overclocked XBMC version of Raspbmc, probably due to the overclocking drawing more power away from the rest of the support system devices.<br />
<br />
* '''A4 Tech'''<br />
** Model GL-6 USB Keyboard, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''Accuratus'''<br />
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100&nbsp;mA). Tested with 1000&nbsp;mA cheap unbranded and Nokia 1200&nbsp;mA power adaptors.<br />
* '''Apple'''<br />
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub. <br />
*'''Argos'''<br />
** Argos Value Wired Keyboard causes kernel panic<br />
* '''Choidy'''<br />
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic<br />
* '''Cit''' <br />
** KB-1807UB Causes kernel panic (rated <200&nbsp;mA)<br />
* '''Dell'''<br />
** SK-8135 (B) (Rated 1.5&nbsp;A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)<br />
** SK-8115 causes kernel panic (rated 100&nbsp;mA) Debian 6-19-04-2012 (B)<br />
** Y-U0003-DEL5 Sticky / Non-responsive keys<br />
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V<br />
* '''Gear Head'''<br />
** KB2300U - Causes kernel panic (B)<br />
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)<br />
* '''GMYLE'''<br />
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]<br />
* '''Inland''' <br />
** Inland USB Keyboard Model #70010<br />
* '''Jeway'''<br />
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)<br />
* '''Labtec'''<br />
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
* '''Logik'''<br />
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)<br />
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''<br />
* '''Logitech'''<br />
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)<br />
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)<br />
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)<br />
** K360 Wireless Keyboard - Occasional sticky keys. (B)<br />
** MK 260 Wireless Keyboard - Occasional sticky keys. (B)<br />
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)<br />
** G510 Gaming Keyboard - lagging or unresponsive keys.<br />
** MX5500 wireless keyboard and mouse with USB Bluetooth receiver - Unstable, looses connection without prior notice<br />
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).<br />
* '''Microsoft''' <br />
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)<br />
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)<br />
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.<br />
** Arc wireless - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)<br />
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)<br />
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000&nbsp;mA power supply unit)<br />
* '''Novatech'''<br />
** NOV-KEY2 - Causes kernel panic (B)<br />
* '''PC World Essentials'''<br />
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it caused a kernel panic -- tested on powered hub and direct.<br />
* '''Razer'''<br />
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.<br />
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED).<br />
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5&nbsp;V 500&nbsp;mA. (B)<br />
* '''SIIG'''<br />
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.<br />
* '''Texet'''<br />
** MB-768B standard keyboard (Rated 5&nbsp;V 1.5&nbsp;A (!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)<br />
* '''Trust''' <br />
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.<br />
* '''Unbranded'''<br />
** Compuparts<br />
** model no. HK-6106 (B)<br />
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.<br />
* '''Verbatim'''<br />
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)<br />
* '''Wilkinsons / TEXET'''<br />
** Model MB-768B causes kernel panic on debian6-19-04-2012.<br />
* '''Xenta'''<br />
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)<br />
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems. <br />
<br />
===Working USB Mouse Devices===<br />
The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* '''A4Tech'''<br />
** OP-530NU Padless Wired Mouse<br />
<br />
* '''Apple'''<br />
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).<br />
<br />
* '''Asda'''<br />
** HM5058 (Smart Price) Wired Mouse<br />
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> mouse)<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''ASUS'''<br />
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)<br />
** MG-0919 (wireless)<br />
<br />
* '''Belkin'''<br />
** F8E882-OPT (B)<br />
<br />
* '''Cellink'''<br />
** OPM-602 Small wireless optical mouse<br />
<br />
* '''Cerulian Technology'''<br />
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA<br />
<br />
* '''Dell'''<br />
** M-UVDEL1 (B)<br />
** MOC5UO (100&nbsp;mA)<br />
** M056U0A (B)<br />
** DZL-MS111-L (B) (100&nbsp;mA)<br />
** MS-111P (100&nbsp;mA)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.<br />
<br />
* '''Dynex'''<br />
** DX-WMSE (100&nbsp;mA) (B)<br />
<br />
* '''Fellowes'''<br />
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (B)<br />
<br />
* '''Filand'''<br />
** OP-102i Mini Optical Mouse<br />
<br />
* '''Genius'''<br />
** GM-04003A (B)<br />
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)<br />
** Traveler 515 Laser<br />
<br />
* '''HP'''<br />
** MN-UAE96 (The basic stock HP wired mouse)(B)<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''Kensington'''<br />
** Kensington Expert Mouse Trackball K64325<br />
** Kensington Expert Mouse "Slimblade" K72327US<br />
<br />
* '''Labtec'''<br />
** Corded Laser Glow Mouse 1600, rated 5&nbsp;V 100&nbsp;mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)<br />
<br />
* '''Lenovo'''<br />
** Wired Optical Mouse Model: MO28UOL<br />
<br />
* '''Logik'''<br />
** Wired Optical Glow Mouse Model: LGGMO10. (B)<br />
<br />
* '''Logitech'''<br />
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)<br />
** B105 Mouse for Laptops (OEM)<br />
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE<br />
** G5 Logitech Gaming Mouse (B)<br />
** G5v2 Logitech Gaming Mouse (B)<br />
** G500 Logitech Gaming Mouse (B)<br />
** G700 Logitech Wireless Gaming Mouse (B)<br />
** LX-700 Cordless Desktop Receiver (B)<br />
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).<br />
** M90 optical mouse<br />
** M185 Wireless Mouse (B)<br />
** M210 (part of the MK260 set) (B)<br />
** M305 Wireless Mouse<br />
** M310 Cordless Mouse<br />
** M325 Wireless Mouse<br />
** M505 USB wireless laser, model no: 910-001324 (B)<br />
** M510 Wireless Mouse (B)<br />
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)<br />
** M-BD58 Wheel Mouse (B)<br />
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)<br />
** M-BJ79 (B)<br />
** M-BT96a Optical Mouse<br />
** MX320/MX400 laser mouse (B)<br />
** MX518 Optical wheel mouse (B)<br />
** Optical USB Mouse (M/N 931643-0403)<br />
** Performance Mouse MX (B)<br />
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)<br />
** VX Nano Cordless Laser Mouse for Notebooks<br />
** Wheel Mouse (M/N BJ58)<br />
<br />
* '''Medion'''<br />
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5&nbsp;V 100&nbsp;mA. Works fb on model B with Raspbian Wheezy<br />
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
** Comfort Curve Mouse 3000 for Business<br />
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).<br />
** Compact optical mouse 500 V2.0 (B)<br />
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)<br />
** Microsoft Intellimouse Optical Mouse<br />
** Microsoft Wireless Laser Mouse 8000<br />
** Microsoft Wireless Mobile Mouse 1000<br />
** Microsoft Wireless Mobile Mouse 3500<br />
** Microsoft Wireless Mobile Mouse 4000<br />
** Microsoft Wireless Mouse 700 v2.0<br />
** Microsoft Comfort Mouse 4500<br />
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)<br />
<br />
* '''Perixx'''<br />
** PERIMICE-210 U Red (Part No.R1J) <br />
<br />
* '''Razer'''<br />
** Boomslang Collectors Edition 2007 (B)<br />
<br />
* '''Rosewill'''<br />
** Rosewill RM-C2U<br />
<br />
* '''Saitek'''<br />
** Notebook Optical Mouse (PM46)<br />
<br />
* '''Samsung'''<br />
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50&nbsp;mA) <br />
<br />
* '''Sun microsystems'''<br />
** Model: FID-638 , SunPN: 371-0788-01<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]<br />
<br />
* '''Swiftpoint'''<br />
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.<br />
<br />
* '''Targus'''<br />
** AKM02UK (Associated keyboard not checked)<br />
** AMU2701EUK (B)<br />
<br />
* '''Technika'''<br />
** TKOPTM2 (B)<br />
**TKD-211<br />
**TKNM110<br />
<br />
* '''Tesco'''<br />
** Wired optical mouse M211 (B)<br />
<br />
*'''The Pi Hut'''<br />
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Model 15313 - large, 5-button wireless mouse<br />
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base<br />
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)<br />
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087<br />
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.<br />
<br />
* '''Verbatiam'''<br />
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)<br />
<br />
* '''Xenta'''<br />
** MOW0810 (B)<br />
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Generic'''<br />
** Generic 2.4&nbsp;GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)<br />
<br />
===Problem USB Mouse Devices===<br />
The following is a list of specific mouse devices that have problems working with the Raspberry Pi<br />
* '''A4Tech'''<br />
** Model G7-630 Wireless Mouse, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''HP'''<br />
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors. <br />
<br />
* '''Logik'''<br />
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)<br />
<br />
* '''Logitech'''<br />
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000&nbsp;Hz out of the box, whereas the 518 is only 125&nbsp;Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.<br />
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot<br />
<br />
* '''Microsoft'''<br />
** Microsoft Touch Mouse - Does not see right clicks, Only left.<br />
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.<br />
<br />
* '''Razer'''<br />
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works, but the cursor doesn't move.<br />
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus<br />
<br />
* '''Roccat'''<br />
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)<br />
<br />
* '''Trust'''<br />
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)<br />
<br />
* '''Xenta'''<br />
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle<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 />
== USB Wi-Fi Adapters ==<br />
<br />
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. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.<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.<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 />
* '''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. <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.<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 />
<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 />
* '''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 Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)<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-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. Important : revision A1 works, revision B1 does not. Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<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-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.<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 />
*** 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 />
** [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 />
<br />
* '''Hawking'''<br />
** HWU54G rev. Z2 (802.11g) (B). Requires "zd1211-firmware" package.<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 />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<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 />
<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].<br />
<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 />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.<br />
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module<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 supports Access Point and it be used for hostapd <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)<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: 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 />
* '''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 (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-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.<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-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 />
<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 />
** [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)<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 />
* '''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 />
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].<br />
<br />
== USB Bluetooth adapters ==<br />
===Working Bluetooth adapters===<br />
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote<br />
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.<br />
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)<br />
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)<br />
** Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.<br />
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.<br />
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288<br />
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.<br />
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.<br />
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian<br />
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian<br />
** Azio BTD-V400. CSR BC8 radio, bluetooth 4.0. Tested with Raspbian using powered USB hub<br />
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip<br />
** http://www.element14.com/community/message/58288<br />
* IOGear GBU321 (Broadcom BCM2045 Chipset)<br />
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.<br />
* Trust BT-2400p<br />
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).<br />
<br />
===Working Bluetooth/Wifi Combo adapters===<br />
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)<ref>http://www.lindy.co.uk/shop/showProductDetail.do?orderNumber=52213</ref><br />
<br />
===Problem Bluetooth adapters===<br />
* '''Belkin'''<br />
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.<br />
* '''Generic'''<br />
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.<br />
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.<br />
* Asus USB-BT211<br />
** Shows up as HCI device in Raspbian, but it does not scan or pair.<br />
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962<br />
<br />
== USB Ethernet adapters ==<br />
===Working Ethernet adapters===<br />
* '''AVM'''<br />
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.<br />
* '''Wintech'''<br />
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100&nbsp;mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]<br />
* '''LogiLink'''<br />
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.<br />
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed<br />
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter <br />
* '''Apple'''<br />
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.<br />
* '''Edimax'''<br />
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.<br />
* '''D-Link'''<br />
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)<br />
* '''LinkSys'''<br />
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.<br />
* '''Sabrent'''<br />
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)<br />
* '''Sitecom'''<br />
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.<br />
* '''A-Link'''<br />
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter<br />
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.<br />
<br />
The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190&nbsp;mA, so there might be stability issues if additional power is not provided.<br />
* '''Hama'''<br />
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.<br />
* '''Newlink'''<br />
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.<br />
<br />
===Problem Ethernet adapters===<br />
* Axago<br />
** Axago ADE-X1 10/100 Ethernet Adapter (USB: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out<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 />
* '''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://www.ti.com/product/pcm2704 PCM2704 98&nbsp;dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]<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 />
==USB 3G Dongles==<br />
* Huawei E1750<br />
* Huawei E173<br />
* Huawei E1820 Works on Raspbian with Sakis3G<br />
* Huawei E220<br />
* Huawei E353 HiLink Works on Raspbian<br />
* Huawei E160 (AT commands only)<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 />
<br />
== USB IR Receivers==<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, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.<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)<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 />
*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 Webcams ==<br />
<br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
|PD1030<br />
|<br />
|<br />
|<br />
|<br />
|ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Hercules<br />
|Webcam Deluxe<br />
|<br />
|05a9:4519<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|ov519 driver "Corrupt JPEG data: premature end of data segment" gives corrupt image in motion and fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|WebcamHD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C270<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| With external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|046d:0826<br />
|<br />
| <br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| With powered hub, detected out of box as Video0 V4L device<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Messenger<br />
|V-UM14<br />
|046d:08f0<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|Not working, STV06xx driver "ioctl (VIDIOCGCAP): Inappropriate ioctl for device", Supported palettes: GRBG, gives corrupt image in fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Picture breaks up at the bottom<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
| <br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Up to 352x288. Higher resolutions do not work. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|Xbox Live Vision<br />
| <br />
| 045e:0294<br />
| Arch Linux <br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| toucam<br />
| Philips 720K/40 webcam<br />
| 0471:0313<br />
| Raspbian Wheezy<br />
| 2013-04-03<br />
| 320x240<br />
| Recognised as lsusb ID 0471:0329 Philips (or NXP). Works with $> guvcview -s 320x240 -f yv12 -t 5 -n rec5sec.mkv --exit_on_close --no_display, but not with command $> fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| The occasional frame is corrupted/stutters when running at 640x480<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| works out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| Spotlight<br />
| <br />
| 0c45:62c0<br />
| Raspbian/Wheezy<br />
| <br />
| 640x480 <br />
| Works out of the box. Tested with power direct from the Raspberry Pi, not tested on a hub. <br />
<br />
<br />
|-<br />
|}<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. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually<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 />
<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 />
== 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 ''ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port''. Appears as ''/dev/ttyUSBX'' with GUID ''dialout'' so your user has to be in that group. If not, ''sudo usermod -a -G dialout yourusername'' will add your user to the ''dialout'' group. Works great with ''screen /dev/ttyUSBX 115200''.<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 />
=== 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 />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<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 SATA ===<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 />
<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 />
<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 />
=== 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 (Lazerus), 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 />
== 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 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 adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.<br />
<br />
===Working power Adapters===<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 />
** 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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''The Pi Hut'''<br />
** Micro USB Power Supply for the Raspberry Pi. 5&nbsp;V 1000&nbsp;mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])<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 />
* '''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 />
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 />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.<br />
<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 />
http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the Raspberry Pi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1&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 "Burning Raspberry!" 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 />
<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 />
http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=4<br />
<br>config_hdmi_boost=4<br />
<br>overscan_top=-30<br />
<br>overscan_bottom=-30<br />
<br>overscan_left=-30<br />
<br>overscan_right=-30<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 />
According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
<br />
According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but it is very pricey compared to the alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4&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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"<br />
<br />
Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=16<br />
<br>hdmi_force_hotplug=1<br />
<br>disable_overscan=0<br />
<br />
<br />
And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. It is very cheap, but it works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC). <br />
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.<br />
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 />
Marcin.<br />
<br />
<br />
Newark/element14 sells the "Pi-View" HDMI-VGA converter specifically for use with the Raspberry Pi. It does work although the small box gets warm and the video output isn't great (slightly fuzzy text, smaller screen area even with overscan enabled):<br />
<br />
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 />
== 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>AutoStatichttps://elinux.org/index.php?title=RPi_Guides&diff=233978RPi Guides2013-03-24T20:06:24Z<p>AutoStatic: /* System Tasks */</p>
<hr />
<div>{{Template:RPi_Learning}}<br />
<br />
<br />
==Introduction==<br />
<br />
This page contains a set of guides to show readers how to do common or useful tasks on the system. These guides focus on system-related items such as how to install a linux option or configure an on-board device. Items listed here should achieve a goal as simply as possible, with the aim to build the confidence of the reader. For anything more complex, the item should be listed on the projects page.<br />
<br />
The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.<br />
<br />
Please add links to your guides (and ones you find interesting).<br />
<br />
Fill in each section:<br />
* Guide Title (as a link to the project webpage or connected wiki page)<br />
* Guide Description (including any additional links or information<br />
* Tags (key words related to the item, i.e. LCD Screen, Teaching, Python)<br />
* Author(s) or group who have produced it (also if it is an Open/Community Project for anyone to contribute)<br />
* Guide Status (Not Started/In-Progress/Available).<br />
<br />
==System Tasks==<br />
This section describes tasks that involve software installation, setup or configuration of your Raspberry Pi. <br />
{| border="1" style="background:transparent;"<br />
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Title and Link'''<br />
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Description'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Tags'''<br />
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Author'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Status'''<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Debian Auto Login | Debian Auto Login/Startx]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
How to launch LXDE without the need of a username/Password in Debian.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
LXDE, Boot, Login, Auto<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Ian Hartwell (helpme1986)<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Early draft.<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Defining Default Terminal Size | Defining default LXTerminal size on the Raspberry Pi]]===<br />
|The LXTerminal application starts with a default size of 24 rows and 80 columns. The window can be resized, but this setting is not remembered for the next time you create a window. This guide shows how to make the setting persistent.<br />
| LXTerminal size<br />
| HBrydon<br />
|Complete<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Chromium | Installing Chromium web browser]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing the Chromium web browser on Debian.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Chromium<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
bredman<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Ready for testing<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Java JDK Installation | Installing The Java JDK on the Raspberry Pi (Debian systems only)]]===<br />
|This page describes how to to install the Java 7 JDK on Debian Wheezy. [As of Q1 2013, the Java JDK will only run on soft-float implementations of Debian Wheezy.]<br />
| Java JDK<br />
| HBrydon<br />
|Complete<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi IceWeasel | Installing Mozilla IceWeasel Web Browser]]===<br />
|On the Raspberry Pi, the Mozilla Firefox browser is implemented under the name "IceWeasel". This page lists how to install IceWeasel on Raspian and Debian.<br />
| Mozilla IceWeasel<br />
| HBrydon<br />
|Debian: Complete Raspian: Needs testing<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://wiki.linuxaudio.org/wiki/raspberrypi Raspberry Pi and real-time, low-latency audio]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
The Raspberry Pi can be set up to handle real-time, low-latency audio but it requires quite some tweaking. Hence this Wiki article in which some common bottlenecks as well as some possible optimizations will be described. Last but not least this article will explain how to get JACK aka jackd running on your RPi. <br />
| vertical-align:top; border:1px solid #aaa;" |<br />
realtime real-time jackd low-latency audio midi<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Jeremy Jongepier (AutoStatic)<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Almost complete Raspbian: tested<br />
|-<br />
|}<br />
<br />
==Easy==<br />
Suitable for beginners who are confident typing commands into Linux but need a lot of guidance.<br />
{| border="1" style="background:transparent;"<br />
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Title and Link'''<br />
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Description'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Tags'''<br />
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Author'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Status'''<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
===[[R-Pi NAS | Network Attached Storage]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Network Attached Storage - Basic concept: A place to save copies of all your important files<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Samba<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
[[User:bredman | bredman]] - Open Project<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Tested on Debian, some help needed with Fedora chapter<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
===[[Autoinstall Samba | Connect your RPi to your MS Windows machines]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
The guide above is a full NAS setup - This guide/script just configures and installs a very simple setup to allow you to read/write to your RPi files<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Samba<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
[[User:SimpleSi | Simon Walters]] - Open Project<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Tested on Raspbian<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
<br />
===[[RPi Debian Python3 | Python 3 on Debian]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing the latest Python 3 and common modules on Debian.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Python<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
croston<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Tested. Needs more modules adding<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
===[[RPi Java | Installing Java 8]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing Java 8 on Raspberry Pi.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Java 8<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Happy-Neko<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Tested on Raspbian.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPiForked-Daapd]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
How to install Forked-Daapd, an itunes media server<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Debian, streaming, <br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Greg (pr1sm)<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Early draft.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Setting up a static IP in Debian | Setting up a static IP in Debian]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
How to set-up a static IP in Debian<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Debian, Static IP<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
sleepy<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Text to Speech (Speech Synthesis) | Text to Speech (Speech Synthesis)]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Three easy methods of getting your Raspberry Pi to talk<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Raspbian<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
StevenP<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Works fine<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
===[http://robotblogging.blogspot.co.uk/2013/01/pi-vision-10.html Installing a Web Cam]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Basic installation and testing of a usb web cam on Raspberry Pi<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
web cam, ps eye, ffmpeg<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Chris Cummings<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Works<br />
|-<br />
<br />
|}<br />
<br />
==Medium==<br />
Suitable for beginners who are willing to experiment and only need a little guidance.<br />
{| border="1" style="background:transparent;"<br />
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Title and Link'''<br />
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Description'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Tags'''<br />
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Author'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Status'''<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[R-Pi PXE Server | Classroom Boot Server]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Classroom boot server - Basic concept: A PXE server to allow cheap computers without hard disks to boot into Windows or Linux.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
PXE, netboot<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
[[User:bredman | bredman]] - Open Project<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Lots of random text, needs organisation and testing<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Ruby on Rails | Installing Ruby on Rails]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing Ruby on Rails and common modules on Debian.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Ruby, Rails<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Erik<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Partially tested. Still early draft.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi VNC Screen Sharing | Share your screen with VNC]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing Vino to allow remote control of the screen from another computer.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Vino, VNC<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Jaix Bly<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Draft.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi VNC Server | Remote Control of a Raspberry with VNC]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing VNC to allow remote control a X11 session (not the console) from another computer.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
VNC<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Simon H<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Early draft.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi XRDP Server | Remote Destop Server for Raspberry]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Installing XRDP to allow Remote Desktop / Terminal Server on Raspberry Pi.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
rdp, xrdp<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Jaix Bly<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Draft.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi iSCSI Initiator | iSCSI support and boot]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Adding iSCSI initiator/target support, setting up iSCSI initiator, and configuring booting from an iSCSI volume.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
iSCSI, netboot<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Alex (nidO)<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Early draft, tested<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi_Email_IP_On_Boot_Debian | Send email containing Pi ip address on boot]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Send email containing the ip of your Pi so you can access via SSH or other network protocol when your ip changes (moving networks) and you are working headless<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
SSH, email, python<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
--[[User:Geraldcor|Geraldcor]] 03:36, 18 June 2012 (UTC)<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Early draft, tested<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://www.penguintutor.com/linux/tightvnc Connecting securely to TightVNC over the Internet]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Guide to installing Tightvnc server on the Raspberry Pi and securing it using ssh to allow connecting over the Internet.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
VNC, ssh<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Stewart Watkiss<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://www.penguintutor.com/linux/raspberrypi-webserver Configuring a LAMP webserver]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Guide to configuring the Raspberry Pi as a LAMP (Linux, Apache, Mysql, PHP) webserver.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
apache, mysql, php<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Stewart Watkiss<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[https://github.com/ewindisch/chefiler Storage Filer/NAS via Chef]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Turn-key package to turn a machine into a storage filer / NAS. Developed and tested on a RaspberryPi. Still in early development. Deploys with Chef.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
samba, nfs, chef<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Eric Windisch<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Alpha/early-stage<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://elinux.org/RPI-Wireless-Hotspot Raspberry Pi WiFi Hotspot]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Turn your Raspberry Pi into a WiFi hotspot!<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
wifi, hotspot, hostapd<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Isaac Smith<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Works like a charm.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://robotblogging.blogspot.co.uk/2013/01/raspberry-pi-chats-to-arduino.html Raspberry Pi / Arduino Serial Communication]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Raspberry Pi talking to Arduino over serial uart<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
arduino, serial, uart<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Chris Cummings<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Works perfectly!<br />
|-<br />
<br />
|}<br />
<br />
==Advanced==<br />
Suitable for confident users who want to try something more advanced.<br />
{| border="1" style="background:transparent;"<br />
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Title and Link'''<br />
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Guide Description'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Tags'''<br />
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Author'''<br />
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |<br />
'''Status'''<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi building and installing OpenELEC | building and installing OpenELEC]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
How to build and install OpenELEC,a embedded Multimedia Distro. You can learn (cross)compiling, building packages from source, how buildsystems are working and what is needed to install a OS on a SD-card for Raspberry Pi.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
XBMC, HTPC, Multimedia, Distro, compiling<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Stephan Raue<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[[RPi Using Skypekit | Using Skypekit]]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
How to get started using Skypekit to make calls & chat. This is currently only useful for advanced users & developers. <br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Skype, Skypekit<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Henry Cooke<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Alpha.<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
<br />
===[http://www.penguintutor.com/linux/raspberrypi-headless Pre-configuring SD card with a static IP address]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Guide to pre-configuring a SD image so that it boots with a static IP address. Useful for running headless without needing to know what DHCP address will be allocated.<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
networking, tcpip<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Stewart Watkiss<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
===[http://rpipython.blogspot.com.es/2012/12/sending-remote-commands-to-our-pi.html Sending remote commands to our Pi thanks to Pastebin]===<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
A guide to send remote commands to our Pi just by editing a pastebin!<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
remote commands, notsureifuseful<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Itxaka Serrano Garcia<br />
| vertical-align:top; border:1px solid #aaa;" |<br />
Available<br />
|-<br />
|}<br />
<br />
=References= <br />
<references/><br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=231926RPi VerifiedPeripherals2013-03-18T19:21:12Z<p>AutoStatic: /* Databases of sound cards that are known to work with Linux */</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 />
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.<br />
<br />
If you use a powered hub and the Raspberry Pi PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100&nbsp;mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).<br />
<br />
===Working USB Hubs===<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''USB Version'''<br />
| '''Number of Ports'''<br />
| '''Power Rating*'''<br />
| '''Powers Raspberry Pi'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Atlantis<br />
|HUB USB2.0 7P<br />
|P014-GH902-B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2&nbsp;A<br />
|Verified<br />
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|4-Port Ultra-Slim Desktop Hub<br />
|F4U040<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.6&nbsp;A<br />
|Verified<br />
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|8-Port ExpressBus for iMac<br />
|F5U010<br />
|<br />
|USB 2.0<br />
|8-Port 7x"A" 1x"B"<br />
|<br />
|Verified<br />
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U224<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|TetraHub™ USB 2.0 4-Port Hub<br />
|F5U231<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U234<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|No backfeed, can power the RPi. Comes with a 2.4&nbsp;A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''&ldquo;Per Port Current Self-Powered Mode: 500mA (max)&rdquo;''. However, I've attached a HD that requires 850&nbsp;mA and it worked fine.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.8&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|MyEssentials 7-Port High-Speed USB 2.0 Hub<br />
|F5U259-ME<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Lighted Hub<br />
|F5U403<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Lighted Hub<br />
|F5U700<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hub 2-en-1<br />
|F5U706ea<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237v1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2.5&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U040v<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5 V - 2.6 A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U039qukAPL<br />
|05e3:0608<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Benq<br />
|<br />
|E2220HD<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|BUFFALO<br />
|4 Port Hub<br />
|BSH4aAE06<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V <br />
|Verified<br />
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Cyberpower<br />
|High-speed Hub<br />
|CP-H720P<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|3.6&nbsp;A<br />
|Verified<br />
|May Contain dual 05e3:0608 instead of 0409:0050<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2001FP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|SP2309W<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2407FWP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|U3011<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub - Card Reader Works - May work with SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|<br />
|B/N61393<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|USB 2.0 External Hub 7 Port<br />
|B/N87467<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.5&nbsp;A<br />
|Verified<br />
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Deltaco<br />
|<br />
|UH-715 Rev 2<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|<br />
|<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|Dynex USB 2.0 7 Port Hub<br />
|DX-HB7PT<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5.0&nbsp;V / 2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|D-Link 7 Port USB Hub<br />
|DUB-H7/B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7 High Speed USB 2.0 7-Port Hub<br />
|BUBH7A A5<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7<br />
|EUBH7EB H/W Ver:B1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI<br />
<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-4 High Speed USB 2.0 4-Port Hub<br />
|DUB-H4<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Digicom<br />
|<br />
|<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|ednet<br />
|USB 2.0 7 port Hub<br />
|85014<br />
|<br />
|2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|Works with keyboard, mouse, audio devices<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GigaWare<br />
|USB 2.0 4 port Hub<br />
|Model 26-160<br />
|<br />
|2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|König Electronic<br />
|7 port USB2.0 HUB<br />
|CMP-USB2HUB55<br />
|1a40:0201<br />
|2.0<br />
|7-Port<br />
|2.0A<br />
|Verified<br />
|Backpowers Raspberry Pi well.<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medi@com<br />
|USB 2.0 4 ports Hub<br />
|M-HX30<br />
|<br />
|2.0<br />
|4-port<br />
|<br />
|Verified<br />
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.<br />
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|mbeat<br />
|13 Port USB Hub<br />
|USB-M13HUB<br />
|<br />
|USB 2.0<br />
|13-port<br />
|5V - 3A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Monoprice<br />
|Aquagate USB Hub<br />
|5328<br />
|<br />
|2.0<br />
|7-port<br />
|2.0&nbsp;A<br />
|Verified<br />
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable <br />
|7 Port High Speed USB Hub<br />
|USB2-HUB-AG7<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 3A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable<br />
|4 Port Hub with Battery Charging 1.1 Support<br />
|USB2-HUB4BC<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5V - 2.5A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|10 Port USB 2.0 Hub<br />
|USB2-HUB10S<br />
|<br />
|USB 2.0<br />
|10-Port<br />
|5V - 2.5A<br />
|Not Verified<br />
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|4 Port USB 3.0 Hub<br />
|USB2-HUB-81X4<br />
|<br />
|USB 3.0<br />
|4-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|7 Port USB 3.0 Hub<br />
|USB2-HUB7-81X<br />
|<br />
|USB 3.0<br />
|7-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
|Plata 4 port USB 2.0 hub<br />
|18687<br />
|<br />
|2.0<br />
|4-port<br />
|1.0&nbsp;A<br />
|Not Verified<br />
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Zipp<br />
|USB 7-Port HUB<br />
|N294<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 2.0A<br />
|Verified<br />
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)<br />
<br />
|-<br />
|}<br />
<br />
<br />
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.<br />
</div><br />
<br />
<br />
*'''Acme'''<br />
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but it is very cheap and small and works after a small modding: on USB-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the Raspberry Pi, and additionally connect GND and +5&nbsp;V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.<br />
<br />
<br />
*'''Digitus'''<br />
** 7-port USB2.0 Powered Hub. Model DA-70226.<br />
*'''Eminent'''<br />
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
* '''GearHead'''<br />
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5&nbsp;V, 1&nbsp;A)<br />
*'''Gembird'''<br />
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.<br />
* '''Genesys Logic (sold at Fry's)'''<br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref><br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)<br />
* '''Hama'''<br />
** Hama 4-way USB 2.0 Hub<br />
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)<br />
*'''HP'''<br />
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)<br />
<br />
*'''Laser'''<br />
** "7 port USB hub with AC adapter Version 2.0". 5&nbsp;V 1&nbsp;A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry Pi USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.<br />
*'''Logik'''<br />
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''<br />
** Logik L4THUB10 4 Port powered hub works fine under Raspbian/Wheezy/model B. Captive USB cable, 2&nbsp;A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!<br />
*'''LogiLink'''<br />
** UA0085 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0090 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0091 USB 3.0 Hub, 4-Port with PSU 5&nbsp;V, 4&nbsp;A. Connected with USB2.0 cable. 1&nbsp;A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy. <br />
** UA0096 USB 2.0 Hub, 10-Port with PSU 5&nbsp;V, 3.5&nbsp;A (Not suitable for powering Raspberry Pi because it doesn't work unless there is working USB input present even with PSU plugged in.)<br />
** UA0160 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.<br />
* '''Macally'''<br />
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000&nbsp;mA wall-wart (US style)<br />
* '''Manhattan'''<br />
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000&nbsp;mA wall-wart (US style)<br />
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500&nbsp;mA each) + (4 USB 3.0 Ports @900&nbsp;mA each) Power Switches on each port, AC Powered and Includes a 5&nbsp;V 4&nbsp;A wall-wart (US style)<br />
*'''Newlink'''<br />
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5&nbsp;V 1&nbsp;A<br />
** NLUSB2-222P 4 port USB 2.0 Hub with 5&nbsp;V 2&nbsp;A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])<br />
*'''Nilox'''<br />
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5&nbsp;V 1.0&nbsp;A<br />
* '''Plugable'''<br />
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5&nbsp;V 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.<br />
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port.<br />
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5&nbsp;V 3&nbsp;A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)<br />
<br />
* '''Pluscom'''<br />
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3&nbsp;A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.<br />
*'''Satechi'''<br />
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.<br />
*'''Staples (Business Depot) (Bureau EN GROS)'''<br />
** Staples 4-port hub Item 607477-CA<br />
*'''StarTech.com'''<br />
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5&nbsp;V 2&nbsp;A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).<br />
*'''SumVision'''<br />
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5&nbsp;V 1.0&nbsp;A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])<br />
*'''Sitecom'''<br />
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Raspberry Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500&nbsp;mA Voltcraft <br />
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1&nbsp;A). Powering Raspberry Pi via microUSB from a hub port.<br />
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
*'''Sweex'''<br />
** US014 4 Port USB 2.0 Hub<br />
*'''Targus'''<br />
** ACH81xx 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)<br />
** ACH63EU 4-port. Using a 5&nbsp;V 2&nbsp;A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.<br />
*'''The Pi Hut'''<br />
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
*'''Trendnet'''<br />
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2&nbsp;A)<br />
*'''Tripp-Lite'''<br />
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2.5&nbsp;A) Powering Raspberry Pi from the hub works.<br />
*'''Ultron'''<br />
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5&nbsp;V, 3&nbsp;A. USB ID 1a40:0201.<br />
*'''VANTEC'''<br />
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5&nbsp;V 2&nbsp;A AC/DC adapter. Go 2.0 Mini hub.<br />
*'''Z-TEK'''<br />
** Z-TEK 7-port powered hub with PSU 5&nbsp;V, 4&nbsp;A. USB ID 1a40:0201.<br />
*"Unknown"<br />
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works<br />
<br />
===Problem USB Hubs===<br />
<br />
Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list<br />
<br />
*'''Addon'''<br />
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.<br />
*'''Belkin'''<br />
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5&nbsp;V pinouts)<br />
** F4U022 7-Port powered USB hub (powered 5&nbsp;V, 2.6&nbsp;A), same as F4U018<br />
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired Ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.<br />
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.<br />
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes. (Works always without powering the Raspberry Pi, haven't tried that)<br />
<br />
*'''Dell'''<br />
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.<br />
<br />
*'''DELTACO'''<br />
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills Ethernet when X11 is started.<br />
<br />
*'''Dynex'''<br />
** 7-Port USB Hub - Does not work in Debian 19-04 image.<br />
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.<br />
<br />
*'''Dynamode'''<br />
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).<br />
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1&nbsp;A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification. <br />
<br />
*'''D-Link'''<br />
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)<br />
<br />
*'''E-Solution'''<br />
** 4-Port 2&nbsp;A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]<br />
<br />
*'''Fosmon'''<br />
** 7-Port USB 2.0 Hub with 1&nbsp;A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry Pi with it's Micro USB cable unplugged).<br />
<br />
*'''Gear Head'''<br />
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.<br />
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.<br />
<br />
*'''Hama'''<br />
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608<br />
<br />
*'''Kensington'''<br />
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).<br />
<br />
*'''iBall'''<br />
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.<br />
<br />
*'''Inland'''<br />
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)<br />
<br />
*'''Logik'''<br />
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)<br />
<br />
*'''LogiLink'''<br />
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.<br />
<br />
*'''Soniq'''<br />
** 4-Port 5&nbsp;V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).<br />
<br />
*'''Targus'''<br />
** ACH115EU 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.<br />
<br />
*'''TCM'''<br />
** Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1&nbsp;A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi no connects. (insufficient power?)<br />
<br />
*'''Trust'''<br />
** 10-port USB 2.0 Hub (powered). Prevents Ethernet from being recognised.<br />
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents Ethernet from being recognised. Keyboard sends multiple characters. <br />
<br />
*'''Unbranded / Multiple Brands'''<br />
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.<br />
** Generic 7-port black hub with Genesys Logic GL850A chipset<br />
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2&nbsp;A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref><br />
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but there are strange USB failures when X session started. High speed devices such as hard drives had failures.<br />
<br />
== USB Remotes ==<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 />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''<br />
=== Working USB Keyboards ===<br />
The following is a list of specific keyboards known to work and which appear to work fault-free.<br />
<br />
* '''A4 Tech'''<br />
** Model KL-5 USB Keyboard, 20&nbsp;mA.<br />
<br />
* '''ABS'''<br />
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)<br />
<br />
* '''Action Star'''<br />
** ACK-5010U Mini Keyboard And Mouse<br />
<br />
* '''Accuratus'''<br />
** KYB-Toughball-HI<br />
<br />
* '''Acer'''<br />
** KG-0917 Wireless Keyboard And Mouse Bundle (B)<br />
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)<br />
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)<br />
<br />
* '''Adesso'''<br />
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100&nbsp;mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.<br />
** Model AKB-410UB. Keyboard with Touchpad.<br />
<br />
* '''Apple''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))<br />
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]<br />
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]<br />
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]<br />
<br />
* '''Asda'''<br />
** Basic Wired Keyboard HK2026 (B)<br />
** Basic Wired Keyboard HK3014<br />
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)<br />
** Premium Wireless Keyboard (white keys, silver back) HK8028<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''Asus'''<br />
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)<br />
<br />
* '''Banbridge'''<br />
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)<br />
<br />
* '''BTC - Behavior Tech Computer Corp.'''<br />
** Wired Portable Keyboard Model 6100 US (86+9 keys)<br />
*** Works with or without a powered hub<br />
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)<br />
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5&nbsp;V/100&nbsp;mA, works directly<br />
<br />
* '''Bush'''<br />
** Wired Slimline Keyboard KU-0833<br />
*** This does not require a USB hub in order to work with the Raspberry Pi<br />
*** In the UK, it is available from Argos for £9.99<br />
<br />
* '''Cerulian''' <br />
** Mini wireless keyboard and mouse deskset (B)<br />
<br />
* '''CD Training''' <br />
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]<br />
<br />
* '''Cherry'''<br />
** CyMotion Master Linux (B)<br />
** RS 6000 USB ON<br />
** G84-4100PTMUS (B) (Compact keyboard. Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** G85-23100DE-2 (B) (Rated 40&nbsp;mA, tested with RPi powered by a 1000&nbsp;mA power supply unit)<br />
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.<br />
<br />
* '''Compaq'''<br />
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5&nbsp;V 100&nbsp;mA. Works directly connected to Raspberry Pi<br />
<br />
* '''Das Keyboard'''<br />
** Model S Professional Keyboard (Built in USB hub not tested) (B)<br />
** Model S Ultimate Keyboard (Built in USB hub working) (B)<br />
<br />
* '''Dell'''<br />
** SK-8115 (B) (Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** L100 (B)<br />
** RT7D40 (100&nbsp;mA. Works directly in Raspberry Pi)<br />
** RT7D50 (75&nbsp;mA) (run "sudo dpkg-reconfigure keyboard-configuration")<br />
** KB1421 (100&nbsp;mA)<br />
** KB2521 (100&nbsp;mA)<br />
** KB212-B (Works directly in Raspberry Pi, without powered hub)<br />
** 1HF2Y (Works directly in Raspberry Pi)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** USB Keyboard 413c:2107 - Works with and without USB hub<br />
<br />
* '''Delux'''<br />
** K8050<br />
<br />
* '''Digicom'''<br />
** WKEYPE01 Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]<br />
<br />
* '''Dynex'''<br />
** DX_-WKBD (60&nbsp;mA) (B)<br />
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)<br />
<br />
* '''EAPPLY'''<br />
** EBO-013 Wireless 2.4&nbsp;GHz compact keyboard with touchpad. Rated <40&nbsp;mA works directly from Raspberry Pi. eBay ref 260962010276 from Shenzen, China.<br />
<br />
* '''Emprex'''<br />
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)<br />
<br />
* '''Fujitsu Siemens''' <br />
** KB SC USB UK (!)<br />
** KB910 USB, with led light on the highest level (B)<br />
** KB400 USB US<br />
<br />
* '''GE''' <br />
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)<br />
<br />
* '''Gear Head''' <br />
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)<br />
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)<br />
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)<br />
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported >> also see Problem USB Keyboards<br />
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)<br />
** KB1500U (USB Mini Keyboard) (B)<br />
** KB5150 (2.4&nbsp;GHz wireless keyboard/mouse Combo) (B)<br />
*** Works well with a powered hub<br />
<br />
* '''Generic'''<br />
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.<br />
<br />
* '''Genius'''<br />
** Ergomedia 700 (GK-04008/C) used without Hub<br />
** KB-06XE (K639) (B)<br />
** LuxeMate i200 (GK-090017; not tested with Hub)<br />
** Slimstar 8000 wireless keyboard<br />
<br />
* '''Gigabyte'''<br />
** GK-KM7580 2.4&nbsp;GHz Wireless Multimedia Keyboard & Mouse<br />
<br />
* '''HP'''<br />
** KG-1061<br />
** KG-0851 Wireless Keyboard and Mouse<br />
** KU-0316 (B)<br />
** LV290AA#ABA Wireless Keyboard and Mouse<br />
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)<br />
** SK-2880<br />
<br />
* '''Hyundai'''<br />
** HY-K201<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Imation''' <br />
** KBD-702 Multi-media Wired Keyboard<br />
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)<br />
<br />
* '''IOGEAR'''<br />
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball<br />
** IOGEAR GKM681R 2.4&nbsp;GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel<br />
<br />
* '''iPazzPort'''<br />
<br />
* '''i.t.works'''<br />
** KC04 (direct and by USB hub)<br />
** KC Silicone (only tested directly)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''KeySonic'''<br />
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Raspberry Pi. Also works with Raspbmc with powered hub.<br />
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub<br />
** ACK-3700C<br />
** ACK-340U+(DE)<br />
** ACK-3400U (UK) mini keyboard<br />
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi<br />
<br />
* '''Labtec'''<br />
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat Keyboard]<br />
<br />
* '''Laptopmate'''<br />
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad<br />
<br />
* '''LC-Power<br />
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4&nbsp;GHz Trackball Keyboard) tested with Debian 6.0.4<br />
<br />
* '''Lenovo'''<br />
** SK-8825 UK (B)<br />
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)<br />
** Lenovo Mini Wireless Keyboard N5901 (US)<br />
<br />
* '''Lindy'''<br />
** 21840 (Wireless RF 2.4&nbsp;GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.<br />
<br />
* '''Logik'''<br />
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''<br />
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver<br />
<br />
* '''Logitech'''<br />
** Comfort Wave 450, labeled 100&nbsp;mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)<br />
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)<br />
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)<br />
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)<br />
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine<br />
** Wii wireless keyboard KG-0802 (!)<br />
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)<br />
** Deluxe 250 Keyboard<br />
** Internet 350 (M/N 967740-0403)<br />
** Internet Navigator Keyboard<br />
** MK120 wired keyboard and mouse<br />
** MK220 wireless keyboard and mouse<br />
** MK250 wireless keyboard and mouse (no hub needed)<br />
** MK260 wireless keyboard and mouse (no hub needed)<br />
** MK300 wireless keyboard and mouse<br />
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]<br />
** MK350 wireless keyboard (using Unifying receiver)<br />
** MK520 wireless keyboard and mouse<br />
** MK550 wireless keyboard and mouse (B)<br />
** MX3200 wireless keyboard and mouse (B)<br />
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.<br />
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)<br />
** EX110 Cordless Desktop, wireless keyboard and mouse (B)<br />
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]<br />
** K120 Keyboard (B)<br />
** K200 Keyboard (B)<br />
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)<br />
** K310 Washable Keyboard<br />
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K350 Wireless Keyboard (B)<br />
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". <br />+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.<br />
** K520 Keyboard (B)<br />
** K700 Wireless Keyboard with Touchpad and unifying receiver<br />
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )<br />
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).<br />
** S510 wireless keyboard and mouse (B)<br />
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100&nbsp;mA. OK direct into Model B Raspberry Pi.<br />
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub in back of keyboard works too.<br />
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.<br />
** V470 Bluetooth Laser Mouse<br />
<br />
''Keyboards and mice also together with Unifying receiver'' <br />
<br />
* '''macally'''<br />
**macally iKey slim (IKEY5V2)<br />
<br />
* '''Medion'''<br />
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
**Microsoft Comfort Curve Keyboard 2000<br />
**Microsoft Comfort Curve Keyboard 3000 for Business<br />
**Microsoft Digital Media Pro Keyboard Model: 1031 (Debian 13-Apr-2012)<br />
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)<br />
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)<br />
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)<br />
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub<br />
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)<br />
**Microsoft Windows 2000 Keyboard (KB-USBK110610)<br />
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5&nbsp;V/100&nbsp;mA (Wheezy 5-Sept-2012)<br />
<br />
* '''Mikomi''' <br />
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the range is terrible less than a metre) (B)<br />
<br />
* '''Monoprice'''<br />
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.<br />
<br />
* '''Motorola'''<br />
<br />
** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)<br />
<br />
* '''ONN'''<br />
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.<br />
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.<br />
<br />
* '''Ortek'''<br />
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.<br />
<br />
* '''Perixx''' <br />
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)<br />
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.<br />
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)<br />
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.<br />
<br />
* '''Philips''' <br />
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)<br />
<br />
* '''Prodige'''<br />
**Nanox Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]<br />
<br />
* '''Rapoo'''<br />
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad<br />
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]<br />
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)<br />
<br />
*'''Riitek'''<br />
**RT-MWK03 mini wireless keyboard & trackpad<br />
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.<br />
**RT-MWK01 mini 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]<br />
<br />
*'''Rosewill'''<br />
** RK-200 Standard Keyboard<br />
<br />
*'''Saitek'''<br />
** Eclipse II Backlit Keyboard PK02AU (B)<br />
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.<br />
** Expression Keyboard (US) <br />
** Cyborg V.5 (B)<br />
<br />
*'''SelecLine'''<br />
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (B)<br />
<br />
*'''SIIG'''<br />
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)<br />
<br />
*'''Silvercrest'''<br />
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B) <br />
<br />
*'''SolidTek'''<br />
** Solid Tek KB-P3100BU ASK-3100U. <br />
<br />
*'''Sony'''<br />
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5&nbsp;V 1&nbsp;A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.<br />
<br />
* '''SteelSeries'''<br />
** Merc keyboard (B)<br />
<br />
* '''Sun Microsystems'''<br />
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)<br />
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard<br />
<br />
* '''Technika'''<br />
** WKEY03 (B)<br />
** TKD-211<br />
<br />
* '''Tesco'''<br />
** Value Keyboard VK109 (B)<br />
** Multimedia K211 Wired Keyboard (B)<br />
<br />
*'''The Pi Hut'''<br />
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.<br />
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)<br />
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard <br />
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087<br />
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.<br />
<br />
* '''Unbranded'''<br />
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller<br />
<br />
* '''Unicomp'''<br />
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub<br />
<br />
* '''Q-Connect'''<br />
** AK-808 (B)<br />
<br />
* '''Xenta'''<br />
** 2.4&nbsp;GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)<br />
** Mini Multimedia Keyboard (Model no.: 808M) (B)<br />
<br />
===Problem USB Keyboards===<br />
<br />
Note that generally PS/2 keyboards with an USB adapter will not work directly on a Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5&nbsp;V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry Pi may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0&nbsp;V. Some of these keyboards work when running the latest Raspbian, but not when using the overclocked XBMC version of Raspbmc, probably due to the overclocking drawing more power away from the rest of the support system devices.<br />
<br />
* '''A4 Tech'''<br />
** Model GL-6 USB Keyboard, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''Accuratus'''<br />
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100&nbsp;mA). Tested with 1000&nbsp;mA cheap unbranded and Nokia 1200&nbsp;mA power adaptors.<br />
* '''Apple'''<br />
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub. <br />
*'''Argos'''<br />
** Argos Value Wired Keyboard causes kernel panic<br />
* '''Choidy'''<br />
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic<br />
* '''Cit''' <br />
** KB-1807UB Causes kernel panic (rated <200&nbsp;mA)<br />
* '''Dell'''<br />
** SK-8135 (B) (Rated 1.5&nbsp;A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)<br />
** SK-8115 causes kernel panic (rated 100&nbsp;mA) Debian 6-19-04-2012 (B)<br />
** Y-U0003-DEL5 Sticky / Non-responsive keys<br />
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V<br />
* '''Gear Head'''<br />
** KB2300U - Causes kernel panic (B)<br />
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)<br />
* '''GMYLE'''<br />
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]<br />
* '''Inland''' <br />
** Inland USB Keyboard Model #70010<br />
* '''Jeway'''<br />
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)<br />
* '''Labtec'''<br />
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
* '''Logik'''<br />
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)<br />
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''<br />
* '''Logitech'''<br />
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)<br />
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)<br />
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)<br />
** K360 Wireless Keyboard - Occasional sticky keys. (B)<br />
** MK 260 Wireless Keyboard - Occasional sticky keys. (B)<br />
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)<br />
** G510 Gaming Keyboard - lagging or unresponsive keys.<br />
** MX5500 wireless keyboard and mouse with USB Bluetooth receiver - Unstable, looses connection without prior notice<br />
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).<br />
* '''Microsoft''' <br />
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)<br />
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)<br />
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.<br />
** Arc wireless - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)<br />
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)<br />
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000&nbsp;mA power supply unit)<br />
* '''Novatech'''<br />
** NOV-KEY2 - Causes kernel panic (B)<br />
* '''PC World Essentials'''<br />
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it caused a kernel panic -- tested on powered hub and direct.<br />
* '''Razer'''<br />
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.<br />
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED).<br />
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5&nbsp;V 500&nbsp;mA. (B)<br />
* '''SIIG'''<br />
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.<br />
* '''Texet'''<br />
** MB-768B standard keyboard (Rated 5&nbsp;V 1.5&nbsp;A (!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)<br />
* '''Trust''' <br />
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.<br />
* '''Unbranded'''<br />
** Compuparts<br />
** model no. HK-6106 (B)<br />
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.<br />
* '''Verbatim'''<br />
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)<br />
* '''Wilkinsons / TEXET'''<br />
** Model MB-768B causes kernel panic on debian6-19-04-2012.<br />
* '''Xenta'''<br />
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)<br />
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems. <br />
<br />
===Working USB Mouse Devices===<br />
The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* '''A4Tech'''<br />
** OP-530NU Padless Wired Mouse<br />
<br />
* '''Apple'''<br />
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).<br />
<br />
* '''Asda'''<br />
** HM5058 (Smart Price) Wired Mouse<br />
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> mouse)<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''ASUS'''<br />
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)<br />
** MG-0919 (wireless)<br />
<br />
* '''Belkin'''<br />
** F8E882-OPT (B)<br />
<br />
* '''Cellink'''<br />
** OPM-602 Small wireless optical mouse<br />
<br />
* '''Cerulian Technology'''<br />
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA<br />
<br />
* '''Dell'''<br />
** M-UVDEL1 (B)<br />
** MOC5UO (100&nbsp;mA)<br />
** M056U0A (B)<br />
** DZL-MS111-L (B) (100&nbsp;mA)<br />
** MS-111P (100&nbsp;mA)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.<br />
<br />
* '''Dynex'''<br />
** DX-WMSE (100&nbsp;mA) (B)<br />
<br />
* '''Fellowes'''<br />
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (B)<br />
<br />
* '''Filand'''<br />
** OP-102i Mini Optical Mouse<br />
<br />
* '''Genius'''<br />
** GM-04003A (B)<br />
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)<br />
** Traveler 515 Laser<br />
<br />
* '''HP'''<br />
** MN-UAE96 (The basic stock HP wired mouse)(B)<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''Kensington'''<br />
** Kensington Expert Mouse Trackball K64325<br />
** Kensington Expert Mouse "Slimblade" K72327US<br />
<br />
* '''Labtec'''<br />
** Corded Laser Glow Mouse 1600, rated 5&nbsp;V 100&nbsp;mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)<br />
<br />
* '''Lenovo'''<br />
** Wired Optical Mouse Model: MO28UOL<br />
<br />
* '''Logik'''<br />
** Wired Optical Glow Mouse Model: LGGMO10. (B)<br />
<br />
* '''Logitech'''<br />
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)<br />
** B105 Mouse for Laptops (OEM)<br />
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE<br />
** G5 Logitech Gaming Mouse (B)<br />
** G5v2 Logitech Gaming Mouse (B)<br />
** G500 Logitech Gaming Mouse (B)<br />
** G700 Logitech Wireless Gaming Mouse (B)<br />
** LX-700 Cordless Desktop Receiver (B)<br />
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).<br />
** M90 optical mouse<br />
** M185 Wireless Mouse (B)<br />
** M210 (part of the MK260 set) (B)<br />
** M305 Wireless Mouse<br />
** M310 Cordless Mouse<br />
** M325 Wireless Mouse<br />
** M505 USB wireless laser, model no: 910-001324 (B)<br />
** M510 Wireless Mouse (B)<br />
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)<br />
** M-BD58 Wheel Mouse (B)<br />
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)<br />
** M-BJ79 (B)<br />
** M-BT96a Optical Mouse<br />
** MX320/MX400 laser mouse (B)<br />
** MX518 Optical wheel mouse (B)<br />
** Optical USB Mouse (M/N 931643-0403)<br />
** Performance Mouse MX (B)<br />
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)<br />
** VX Nano Cordless Laser Mouse for Notebooks<br />
** Wheel Mouse (M/N BJ58)<br />
<br />
* '''Medion'''<br />
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5&nbsp;V 100&nbsp;mA. Works fb on model B with Raspbian Wheezy<br />
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
** Comfort Curve Mouse 3000 for Business<br />
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).<br />
** Compact optical mouse 500 V2.0 (B)<br />
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)<br />
** Microsoft Intellimouse Optical Mouse<br />
** Microsoft Wireless Laser Mouse 8000<br />
** Microsoft Wireless Mobile Mouse 1000<br />
** Microsoft Wireless Mobile Mouse 3500<br />
** Microsoft Wireless Mobile Mouse 4000<br />
** Microsoft Wireless Mouse 700 v2.0<br />
** Microsoft Comfort Mouse 4500<br />
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)<br />
<br />
* '''Perixx'''<br />
** PERIMICE-210 U Red (Part No.R1J) <br />
<br />
* '''Razer'''<br />
** Boomslang Collectors Edition 2007 (B)<br />
<br />
* '''Rosewill'''<br />
** Rosewill RM-C2U<br />
<br />
* '''Saitek'''<br />
** Notebook Optical Mouse (PM46)<br />
<br />
* '''Samsung'''<br />
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50&nbsp;mA) <br />
<br />
* '''Sun microsystems'''<br />
** Model: FID-638 , SunPN: 371-0788-01<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]<br />
<br />
* '''Swiftpoint'''<br />
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.<br />
<br />
* '''Targus'''<br />
** AKM02UK (Associated keyboard not checked)<br />
** AMU2701EUK (B)<br />
<br />
* '''Technika'''<br />
** TKOPTM2 (B)<br />
**TKD-211<br />
**TKNM110<br />
<br />
* '''Tesco'''<br />
** Wired optical mouse M211 (B)<br />
<br />
*'''The Pi Hut'''<br />
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Model 15313 - large, 5-button wireless mouse<br />
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base<br />
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)<br />
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087<br />
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.<br />
<br />
* '''Verbatiam'''<br />
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)<br />
<br />
* '''Xenta'''<br />
** MOW0810 (B)<br />
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Generic'''<br />
** Generic 2.4&nbsp;GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)<br />
<br />
===Problem USB Mouse Devices===<br />
The following is a list of specific mouse devices that have problems working with the Raspberry Pi<br />
* '''A4Tech'''<br />
** Model G7-630 Wireless Mouse, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''HP'''<br />
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors. <br />
<br />
* '''Logik'''<br />
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)<br />
<br />
* '''Logitech'''<br />
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000&nbsp;Hz out of the box, whereas the 518 is only 125&nbsp;Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.<br />
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot<br />
<br />
* '''Microsoft'''<br />
** Microsoft Touch Mouse - Does not see right clicks, Only left.<br />
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.<br />
<br />
* '''Razer'''<br />
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works, but the cursor doesn't move.<br />
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus<br />
<br />
* '''Roccat'''<br />
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)<br />
<br />
* '''Trust'''<br />
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)<br />
<br />
* '''Xenta'''<br />
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle<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 />
== USB Wi-Fi Adapters ==<br />
<br />
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. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.<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.<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 />
* '''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. <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.<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 />
<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 />
* '''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 Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)<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-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. Important : revision A1 works, revision B1 does not. Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<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-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.<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 />
*** 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 />
(B)<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 />
<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 />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<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 />
<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 />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.<br />
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module<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 supports Access Point and it be used for hostapd <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)<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: 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 />
* '''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]<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 (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-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.<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-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 />
<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 />
** [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)<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 />
* '''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 />
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].<br />
<br />
== USB Bluetooth adapters ==<br />
===Working Bluetooth adapters===<br />
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote<br />
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.<br />
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)<br />
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)<br />
** Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.<br />
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.<br />
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288<br />
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.<br />
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.<br />
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian<br />
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian<br />
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip<br />
** http://www.element14.com/community/message/58288<br />
* IOGear GBU321 (Broadcom BCM2045 Chipset)<br />
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.<br />
* Trust BT-2400p<br />
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).<br />
<br />
===Working Bluetooth/Wifi Combo adapters===<br />
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)<ref>http://www.lindy.co.uk/shop/showProductDetail.do?orderNumber=52213</ref><br />
<br />
===Problem Bluetooth adapters===<br />
* '''Belkin'''<br />
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.<br />
* '''Generic'''<br />
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.<br />
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.<br />
* Asus USB-BT211<br />
** Shows up as HCI device in Raspbian, but it does not scan or pair.<br />
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962<br />
<br />
== USB Ethernet adapters ==<br />
===Working Ethernet adapters===<br />
* '''AVM'''<br />
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.<br />
* '''Wintech'''<br />
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100&nbsp;mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]<br />
* '''LogiLink'''<br />
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.<br />
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed<br />
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter <br />
* '''Apple'''<br />
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.<br />
* '''Edimax'''<br />
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.<br />
* '''D-Link'''<br />
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)<br />
* '''LinkSys'''<br />
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.<br />
* '''Sabrent'''<br />
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)<br />
* '''Sitecom'''<br />
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.<br />
* '''A-Link'''<br />
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter<br />
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.<br />
<br />
The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190&nbsp;mA, so there might be stability issues if additional power is not provided.<br />
* '''Hama'''<br />
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.<br />
* '''Newlink'''<br />
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.<br />
<br />
===Problem Ethernet adapters===<br />
* Axago<br />
** Axago ADE-X1 10/100 Ethernet Adapter (USB: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out<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 />
* '''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://www.ti.com/product/pcm2704 PCM2704 98&nbsp;dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]<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 />
==USB 3G Dongles==<br />
* Huawei E1750<br />
* Huawei E173<br />
* Huawei E220<br />
* Huawei E160 (AT commands only)<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 />
<br />
== USB IR Receivers==<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, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.<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)<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 />
*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 Webcams ==<br />
<br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
| PD1030<br />
|<br />
| <br />
| <br />
|<br />
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|WebcamHD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| Works fine without external power.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C270<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| With external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| With powered hub, detected out of box as Video0 V4L device<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Picture breaks up at the bottom<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
| <br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Up to 352x288. Higher resolutions do not work. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|Xbox Live Vision<br />
| <br />
| 045e:0294<br />
| Arch Linux <br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #A4B2CF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| The occasional frame is corrupted/stutters when running at 640x480<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| works out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
<br />
|-<br />
|}<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. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually<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 />
<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 />
== 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 />
<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'' and ''gtkterm''<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 />
<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 />
== 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 />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<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 SATA ===<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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== USB 3.0 Multi-Card Reader ===<br />
* US Robotics 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 />
=== 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 (Lazerus), 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 />
== 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 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 adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.<br />
<br />
===Working power Adapters===<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 />
** 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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''The Pi Hut'''<br />
** Micro USB Power Supply for the Raspberry Pi. 5&nbsp;V 1000&nbsp;mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])<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 />
* '''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 />
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 />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.<br />
<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 />
http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the Raspberry Pi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1&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 "Burning Raspberry!" 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 />
<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 />
http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=4<br />
<br>config_hdmi_boost=4<br />
<br>overscan_top=-30<br />
<br>overscan_bottom=-30<br />
<br>overscan_left=-30<br />
<br>overscan_right=-30<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 />
According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
<br />
According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but it is very pricey compared to the alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4&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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"<br />
<br />
Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=16<br />
<br>hdmi_force_hotplug=1<br />
<br>disable_overscan=0<br />
<br />
<br />
And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. It is very cheap, but it works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC). <br />
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.<br />
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 />
Marcin.<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 />
== 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>AutoStatichttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=231920RPi VerifiedPeripherals2013-03-18T19:18:58Z<p>AutoStatic: /* USB Sound Cards */</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 />
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.<br />
<br />
If you use a powered hub and the Raspberry Pi PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100&nbsp;mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).<br />
<br />
===Working USB Hubs===<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''USB Version'''<br />
| '''Number of Ports'''<br />
| '''Power Rating*'''<br />
| '''Powers Raspberry Pi'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Atlantis<br />
|HUB USB2.0 7P<br />
|P014-GH902-B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2&nbsp;A<br />
|Verified<br />
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|4-Port Ultra-Slim Desktop Hub<br />
|F4U040<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.6&nbsp;A<br />
|Verified<br />
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|8-Port ExpressBus for iMac<br />
|F5U010<br />
|<br />
|USB 2.0<br />
|8-Port 7x"A" 1x"B"<br />
|<br />
|Verified<br />
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U224<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|TetraHub™ USB 2.0 4-Port Hub<br />
|F5U231<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U234<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|No backfeed, can power the RPi. Comes with a 2.4&nbsp;A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''&ldquo;Per Port Current Self-Powered Mode: 500mA (max)&rdquo;''. However, I've attached a HD that requires 850&nbsp;mA and it worked fine.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.8&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|MyEssentials 7-Port High-Speed USB 2.0 Hub<br />
|F5U259-ME<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Lighted Hub<br />
|F5U403<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Lighted Hub<br />
|F5U700<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hub 2-en-1<br />
|F5U706ea<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237v1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2.5&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U040v<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5 V - 2.6 A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U039qukAPL<br />
|05e3:0608<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Benq<br />
|<br />
|E2220HD<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|BUFFALO<br />
|4 Port Hub<br />
|BSH4aAE06<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V <br />
|Verified<br />
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Cyberpower<br />
|High-speed Hub<br />
|CP-H720P<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|3.6&nbsp;A<br />
|Verified<br />
|May Contain dual 05e3:0608 instead of 0409:0050<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2001FP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|SP2309W<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2407FWP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|U3011<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub - Card Reader Works - May work with SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|<br />
|B/N61393<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|USB 2.0 External Hub 7 Port<br />
|B/N87467<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.5&nbsp;A<br />
|Verified<br />
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Deltaco<br />
|<br />
|UH-715 Rev 2<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|<br />
|<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|Dynex USB 2.0 7 Port Hub<br />
|DX-HB7PT<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5.0&nbsp;V / 2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|D-Link 7 Port USB Hub<br />
|DUB-H7/B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7 High Speed USB 2.0 7-Port Hub<br />
|BUBH7A A5<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7<br />
|EUBH7EB H/W Ver:B1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI<br />
<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-4 High Speed USB 2.0 4-Port Hub<br />
|DUB-H4<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Digicom<br />
|<br />
|<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|ednet<br />
|USB 2.0 7 port Hub<br />
|85014<br />
|<br />
|2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|Works with keyboard, mouse, audio devices<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GigaWare<br />
|USB 2.0 4 port Hub<br />
|Model 26-160<br />
|<br />
|2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|König Electronic<br />
|7 port USB2.0 HUB<br />
|CMP-USB2HUB55<br />
|1a40:0201<br />
|2.0<br />
|7-Port<br />
|2.0A<br />
|Verified<br />
|Backpowers Raspberry Pi well.<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medi@com<br />
|USB 2.0 4 ports Hub<br />
|M-HX30<br />
|<br />
|2.0<br />
|4-port<br />
|<br />
|Verified<br />
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.<br />
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|mbeat<br />
|13 Port USB Hub<br />
|USB-M13HUB<br />
|<br />
|USB 2.0<br />
|13-port<br />
|5V - 3A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Monoprice<br />
|Aquagate USB Hub<br />
|5328<br />
|<br />
|2.0<br />
|7-port<br />
|2.0&nbsp;A<br />
|Verified<br />
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable <br />
|7 Port High Speed USB Hub<br />
|USB2-HUB-AG7<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 3A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable<br />
|4 Port Hub with Battery Charging 1.1 Support<br />
|USB2-HUB4BC<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5V - 2.5A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|10 Port USB 2.0 Hub<br />
|USB2-HUB10S<br />
|<br />
|USB 2.0<br />
|10-Port<br />
|5V - 2.5A<br />
|Not Verified<br />
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|4 Port USB 3.0 Hub<br />
|USB2-HUB-81X4<br />
|<br />
|USB 3.0<br />
|4-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|7 Port USB 3.0 Hub<br />
|USB2-HUB7-81X<br />
|<br />
|USB 3.0<br />
|7-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
|Plata 4 port USB 2.0 hub<br />
|18687<br />
|<br />
|2.0<br />
|4-port<br />
|1.0&nbsp;A<br />
|Not Verified<br />
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Zipp<br />
|USB 7-Port HUB<br />
|N294<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 2.0A<br />
|Verified<br />
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)<br />
<br />
|-<br />
|}<br />
<br />
<br />
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.<br />
</div><br />
<br />
<br />
*'''Acme'''<br />
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but it is very cheap and small and works after a small modding: on USB-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the Raspberry Pi, and additionally connect GND and +5&nbsp;V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.<br />
<br />
<br />
*'''Digitus'''<br />
** 7-port USB2.0 Powered Hub. Model DA-70226.<br />
*'''Eminent'''<br />
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
* '''GearHead'''<br />
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5&nbsp;V, 1&nbsp;A)<br />
*'''Gembird'''<br />
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.<br />
* '''Genesys Logic (sold at Fry's)'''<br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref><br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)<br />
* '''Hama'''<br />
** Hama 4-way USB 2.0 Hub<br />
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)<br />
*'''HP'''<br />
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)<br />
<br />
*'''Laser'''<br />
** "7 port USB hub with AC adapter Version 2.0". 5&nbsp;V 1&nbsp;A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry Pi USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.<br />
*'''Logik'''<br />
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''<br />
** Logik L4THUB10 4 Port powered hub works fine under Raspbian/Wheezy/model B. Captive USB cable, 2&nbsp;A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!<br />
*'''LogiLink'''<br />
** UA0085 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0090 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0091 USB 3.0 Hub, 4-Port with PSU 5&nbsp;V, 4&nbsp;A. Connected with USB2.0 cable. 1&nbsp;A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy. <br />
** UA0096 USB 2.0 Hub, 10-Port with PSU 5&nbsp;V, 3.5&nbsp;A (Not suitable for powering Raspberry Pi because it doesn't work unless there is working USB input present even with PSU plugged in.)<br />
** UA0160 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.<br />
* '''Macally'''<br />
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000&nbsp;mA wall-wart (US style)<br />
* '''Manhattan'''<br />
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000&nbsp;mA wall-wart (US style)<br />
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500&nbsp;mA each) + (4 USB 3.0 Ports @900&nbsp;mA each) Power Switches on each port, AC Powered and Includes a 5&nbsp;V 4&nbsp;A wall-wart (US style)<br />
*'''Newlink'''<br />
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5&nbsp;V 1&nbsp;A<br />
** NLUSB2-222P 4 port USB 2.0 Hub with 5&nbsp;V 2&nbsp;A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])<br />
*'''Nilox'''<br />
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5&nbsp;V 1.0&nbsp;A<br />
* '''Plugable'''<br />
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5&nbsp;V 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.<br />
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port.<br />
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5&nbsp;V 3&nbsp;A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)<br />
<br />
* '''Pluscom'''<br />
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3&nbsp;A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.<br />
*'''Satechi'''<br />
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.<br />
*'''Staples (Business Depot) (Bureau EN GROS)'''<br />
** Staples 4-port hub Item 607477-CA<br />
*'''StarTech.com'''<br />
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5&nbsp;V 2&nbsp;A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).<br />
*'''SumVision'''<br />
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5&nbsp;V 1.0&nbsp;A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])<br />
*'''Sitecom'''<br />
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Raspberry Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500&nbsp;mA Voltcraft <br />
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1&nbsp;A). Powering Raspberry Pi via microUSB from a hub port.<br />
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
*'''Sweex'''<br />
** US014 4 Port USB 2.0 Hub<br />
*'''Targus'''<br />
** ACH81xx 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)<br />
** ACH63EU 4-port. Using a 5&nbsp;V 2&nbsp;A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.<br />
*'''The Pi Hut'''<br />
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
*'''Trendnet'''<br />
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2&nbsp;A)<br />
*'''Tripp-Lite'''<br />
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2.5&nbsp;A) Powering Raspberry Pi from the hub works.<br />
*'''Ultron'''<br />
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5&nbsp;V, 3&nbsp;A. USB ID 1a40:0201.<br />
*'''VANTEC'''<br />
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5&nbsp;V 2&nbsp;A AC/DC adapter. Go 2.0 Mini hub.<br />
*'''Z-TEK'''<br />
** Z-TEK 7-port powered hub with PSU 5&nbsp;V, 4&nbsp;A. USB ID 1a40:0201.<br />
*"Unknown"<br />
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works<br />
<br />
===Problem USB Hubs===<br />
<br />
Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list<br />
<br />
*'''Addon'''<br />
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.<br />
*'''Belkin'''<br />
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5&nbsp;V pinouts)<br />
** F4U022 7-Port powered USB hub (powered 5&nbsp;V, 2.6&nbsp;A), same as F4U018<br />
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired Ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.<br />
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.<br />
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes. (Works always without powering the Raspberry Pi, haven't tried that)<br />
<br />
*'''Dell'''<br />
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.<br />
<br />
*'''DELTACO'''<br />
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills Ethernet when X11 is started.<br />
<br />
*'''Dynex'''<br />
** 7-Port USB Hub - Does not work in Debian 19-04 image.<br />
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.<br />
<br />
*'''Dynamode'''<br />
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).<br />
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1&nbsp;A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification. <br />
<br />
*'''D-Link'''<br />
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)<br />
<br />
*'''E-Solution'''<br />
** 4-Port 2&nbsp;A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]<br />
<br />
*'''Fosmon'''<br />
** 7-Port USB 2.0 Hub with 1&nbsp;A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry Pi with it's Micro USB cable unplugged).<br />
<br />
*'''Gear Head'''<br />
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.<br />
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.<br />
<br />
*'''Hama'''<br />
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608<br />
<br />
*'''Kensington'''<br />
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).<br />
<br />
*'''iBall'''<br />
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.<br />
<br />
*'''Inland'''<br />
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)<br />
<br />
*'''Logik'''<br />
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)<br />
<br />
*'''LogiLink'''<br />
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.<br />
<br />
*'''Soniq'''<br />
** 4-Port 5&nbsp;V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).<br />
<br />
*'''Targus'''<br />
** ACH115EU 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.<br />
<br />
*'''TCM'''<br />
** Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1&nbsp;A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi no connects. (insufficient power?)<br />
<br />
*'''Trust'''<br />
** 10-port USB 2.0 Hub (powered). Prevents Ethernet from being recognised.<br />
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents Ethernet from being recognised. Keyboard sends multiple characters. <br />
<br />
*'''Unbranded / Multiple Brands'''<br />
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.<br />
** Generic 7-port black hub with Genesys Logic GL850A chipset<br />
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2&nbsp;A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref><br />
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but there are strange USB failures when X session started. High speed devices such as hard drives had failures.<br />
<br />
== USB Remotes ==<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 />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''<br />
=== Working USB Keyboards ===<br />
The following is a list of specific keyboards known to work and which appear to work fault-free.<br />
<br />
* '''A4 Tech'''<br />
** Model KL-5 USB Keyboard, 20&nbsp;mA.<br />
<br />
* '''ABS'''<br />
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)<br />
<br />
* '''Action Star'''<br />
** ACK-5010U Mini Keyboard And Mouse<br />
<br />
* '''Accuratus'''<br />
** KYB-Toughball-HI<br />
<br />
* '''Acer'''<br />
** KG-0917 Wireless Keyboard And Mouse Bundle (B)<br />
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)<br />
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)<br />
<br />
* '''Adesso'''<br />
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100&nbsp;mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.<br />
** Model AKB-410UB. Keyboard with Touchpad.<br />
<br />
* '''Apple''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))<br />
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]<br />
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]<br />
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]<br />
<br />
* '''Asda'''<br />
** Basic Wired Keyboard HK2026 (B)<br />
** Basic Wired Keyboard HK3014<br />
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)<br />
** Premium Wireless Keyboard (white keys, silver back) HK8028<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''Asus'''<br />
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)<br />
<br />
* '''Banbridge'''<br />
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)<br />
<br />
* '''BTC - Behavior Tech Computer Corp.'''<br />
** Wired Portable Keyboard Model 6100 US (86+9 keys)<br />
*** Works with or without a powered hub<br />
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)<br />
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5&nbsp;V/100&nbsp;mA, works directly<br />
<br />
* '''Bush'''<br />
** Wired Slimline Keyboard KU-0833<br />
*** This does not require a USB hub in order to work with the Raspberry Pi<br />
*** In the UK, it is available from Argos for £9.99<br />
<br />
* '''Cerulian''' <br />
** Mini wireless keyboard and mouse deskset (B)<br />
<br />
* '''CD Training''' <br />
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]<br />
<br />
* '''Cherry'''<br />
** CyMotion Master Linux (B)<br />
** RS 6000 USB ON<br />
** G84-4100PTMUS (B) (Compact keyboard. Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** G85-23100DE-2 (B) (Rated 40&nbsp;mA, tested with RPi powered by a 1000&nbsp;mA power supply unit)<br />
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.<br />
<br />
* '''Compaq'''<br />
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5&nbsp;V 100&nbsp;mA. Works directly connected to Raspberry Pi<br />
<br />
* '''Das Keyboard'''<br />
** Model S Professional Keyboard (Built in USB hub not tested) (B)<br />
** Model S Ultimate Keyboard (Built in USB hub working) (B)<br />
<br />
* '''Dell'''<br />
** SK-8115 (B) (Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** L100 (B)<br />
** RT7D40 (100&nbsp;mA. Works directly in Raspberry Pi)<br />
** RT7D50 (75&nbsp;mA) (run "sudo dpkg-reconfigure keyboard-configuration")<br />
** KB1421 (100&nbsp;mA)<br />
** KB2521 (100&nbsp;mA)<br />
** KB212-B (Works directly in Raspberry Pi, without powered hub)<br />
** 1HF2Y (Works directly in Raspberry Pi)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** USB Keyboard 413c:2107 - Works with and without USB hub<br />
<br />
* '''Delux'''<br />
** K8050<br />
<br />
* '''Digicom'''<br />
** WKEYPE01 Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]<br />
<br />
* '''Dynex'''<br />
** DX_-WKBD (60&nbsp;mA) (B)<br />
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)<br />
<br />
* '''EAPPLY'''<br />
** EBO-013 Wireless 2.4&nbsp;GHz compact keyboard with touchpad. Rated <40&nbsp;mA works directly from Raspberry Pi. eBay ref 260962010276 from Shenzen, China.<br />
<br />
* '''Emprex'''<br />
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)<br />
<br />
* '''Fujitsu Siemens''' <br />
** KB SC USB UK (!)<br />
** KB910 USB, with led light on the highest level (B)<br />
** KB400 USB US<br />
<br />
* '''GE''' <br />
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)<br />
<br />
* '''Gear Head''' <br />
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)<br />
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)<br />
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)<br />
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported >> also see Problem USB Keyboards<br />
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)<br />
** KB1500U (USB Mini Keyboard) (B)<br />
** KB5150 (2.4&nbsp;GHz wireless keyboard/mouse Combo) (B)<br />
*** Works well with a powered hub<br />
<br />
* '''Generic'''<br />
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.<br />
<br />
* '''Genius'''<br />
** Ergomedia 700 (GK-04008/C) used without Hub<br />
** KB-06XE (K639) (B)<br />
** LuxeMate i200 (GK-090017; not tested with Hub)<br />
** Slimstar 8000 wireless keyboard<br />
<br />
* '''Gigabyte'''<br />
** GK-KM7580 2.4&nbsp;GHz Wireless Multimedia Keyboard & Mouse<br />
<br />
* '''HP'''<br />
** KG-1061<br />
** KG-0851 Wireless Keyboard and Mouse<br />
** KU-0316 (B)<br />
** LV290AA#ABA Wireless Keyboard and Mouse<br />
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)<br />
** SK-2880<br />
<br />
* '''Hyundai'''<br />
** HY-K201<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Imation''' <br />
** KBD-702 Multi-media Wired Keyboard<br />
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)<br />
<br />
* '''IOGEAR'''<br />
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball<br />
** IOGEAR GKM681R 2.4&nbsp;GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel<br />
<br />
* '''iPazzPort'''<br />
<br />
* '''i.t.works'''<br />
** KC04 (direct and by USB hub)<br />
** KC Silicone (only tested directly)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''KeySonic'''<br />
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Raspberry Pi. Also works with Raspbmc with powered hub.<br />
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub<br />
** ACK-3700C<br />
** ACK-340U+(DE)<br />
** ACK-3400U (UK) mini keyboard<br />
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi<br />
<br />
* '''Labtec'''<br />
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat Keyboard]<br />
<br />
* '''Laptopmate'''<br />
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad<br />
<br />
* '''LC-Power<br />
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4&nbsp;GHz Trackball Keyboard) tested with Debian 6.0.4<br />
<br />
* '''Lenovo'''<br />
** SK-8825 UK (B)<br />
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)<br />
** Lenovo Mini Wireless Keyboard N5901 (US)<br />
<br />
* '''Lindy'''<br />
** 21840 (Wireless RF 2.4&nbsp;GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.<br />
<br />
* '''Logik'''<br />
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''<br />
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver<br />
<br />
* '''Logitech'''<br />
** Comfort Wave 450, labeled 100&nbsp;mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)<br />
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)<br />
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)<br />
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)<br />
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine<br />
** Wii wireless keyboard KG-0802 (!)<br />
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)<br />
** Deluxe 250 Keyboard<br />
** Internet 350 (M/N 967740-0403)<br />
** Internet Navigator Keyboard<br />
** MK120 wired keyboard and mouse<br />
** MK220 wireless keyboard and mouse<br />
** MK250 wireless keyboard and mouse (no hub needed)<br />
** MK260 wireless keyboard and mouse (no hub needed)<br />
** MK300 wireless keyboard and mouse<br />
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]<br />
** MK350 wireless keyboard (using Unifying receiver)<br />
** MK520 wireless keyboard and mouse<br />
** MK550 wireless keyboard and mouse (B)<br />
** MX3200 wireless keyboard and mouse (B)<br />
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.<br />
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)<br />
** EX110 Cordless Desktop, wireless keyboard and mouse (B)<br />
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]<br />
** K120 Keyboard (B)<br />
** K200 Keyboard (B)<br />
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)<br />
** K310 Washable Keyboard<br />
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K350 Wireless Keyboard (B)<br />
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". <br />+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.<br />
** K520 Keyboard (B)<br />
** K700 Wireless Keyboard with Touchpad and unifying receiver<br />
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )<br />
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).<br />
** S510 wireless keyboard and mouse (B)<br />
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100&nbsp;mA. OK direct into Model B Raspberry Pi.<br />
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub in back of keyboard works too.<br />
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.<br />
** V470 Bluetooth Laser Mouse<br />
<br />
''Keyboards and mice also together with Unifying receiver'' <br />
<br />
* '''macally'''<br />
**macally iKey slim (IKEY5V2)<br />
<br />
* '''Medion'''<br />
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
**Microsoft Comfort Curve Keyboard 2000<br />
**Microsoft Comfort Curve Keyboard 3000 for Business<br />
**Microsoft Digital Media Pro Keyboard Model: 1031 (Debian 13-Apr-2012)<br />
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)<br />
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)<br />
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)<br />
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub<br />
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)<br />
**Microsoft Windows 2000 Keyboard (KB-USBK110610)<br />
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5&nbsp;V/100&nbsp;mA (Wheezy 5-Sept-2012)<br />
<br />
* '''Mikomi''' <br />
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the range is terrible less than a metre) (B)<br />
<br />
* '''Monoprice'''<br />
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.<br />
<br />
* '''Motorola'''<br />
<br />
** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)<br />
<br />
* '''ONN'''<br />
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.<br />
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.<br />
<br />
* '''Ortek'''<br />
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.<br />
<br />
* '''Perixx''' <br />
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)<br />
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.<br />
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)<br />
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.<br />
<br />
* '''Philips''' <br />
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)<br />
<br />
* '''Prodige'''<br />
**Nanox Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]<br />
<br />
* '''Rapoo'''<br />
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad<br />
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]<br />
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)<br />
<br />
*'''Riitek'''<br />
**RT-MWK03 mini wireless keyboard & trackpad<br />
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.<br />
**RT-MWK01 mini 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]<br />
<br />
*'''Rosewill'''<br />
** RK-200 Standard Keyboard<br />
<br />
*'''Saitek'''<br />
** Eclipse II Backlit Keyboard PK02AU (B)<br />
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.<br />
** Expression Keyboard (US) <br />
** Cyborg V.5 (B)<br />
<br />
*'''SelecLine'''<br />
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (B)<br />
<br />
*'''SIIG'''<br />
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)<br />
<br />
*'''Silvercrest'''<br />
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B) <br />
<br />
*'''SolidTek'''<br />
** Solid Tek KB-P3100BU ASK-3100U. <br />
<br />
*'''Sony'''<br />
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5&nbsp;V 1&nbsp;A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.<br />
<br />
* '''SteelSeries'''<br />
** Merc keyboard (B)<br />
<br />
* '''Sun Microsystems'''<br />
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)<br />
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard<br />
<br />
* '''Technika'''<br />
** WKEY03 (B)<br />
** TKD-211<br />
<br />
* '''Tesco'''<br />
** Value Keyboard VK109 (B)<br />
** Multimedia K211 Wired Keyboard (B)<br />
<br />
*'''The Pi Hut'''<br />
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.<br />
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)<br />
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard <br />
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087<br />
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.<br />
<br />
* '''Unbranded'''<br />
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller<br />
<br />
* '''Unicomp'''<br />
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub<br />
<br />
* '''Q-Connect'''<br />
** AK-808 (B)<br />
<br />
* '''Xenta'''<br />
** 2.4&nbsp;GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)<br />
** Mini Multimedia Keyboard (Model no.: 808M) (B)<br />
<br />
===Problem USB Keyboards===<br />
<br />
Note that generally PS/2 keyboards with an USB adapter will not work directly on a Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5&nbsp;V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry Pi may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0&nbsp;V. Some of these keyboards work when running the latest Raspbian, but not when using the overclocked XBMC version of Raspbmc, probably due to the overclocking drawing more power away from the rest of the support system devices.<br />
<br />
* '''A4 Tech'''<br />
** Model GL-6 USB Keyboard, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''Accuratus'''<br />
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100&nbsp;mA). Tested with 1000&nbsp;mA cheap unbranded and Nokia 1200&nbsp;mA power adaptors.<br />
* '''Apple'''<br />
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub. <br />
*'''Argos'''<br />
** Argos Value Wired Keyboard causes kernel panic<br />
* '''Choidy'''<br />
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic<br />
* '''Cit''' <br />
** KB-1807UB Causes kernel panic (rated <200&nbsp;mA)<br />
* '''Dell'''<br />
** SK-8135 (B) (Rated 1.5&nbsp;A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)<br />
** SK-8115 causes kernel panic (rated 100&nbsp;mA) Debian 6-19-04-2012 (B)<br />
** Y-U0003-DEL5 Sticky / Non-responsive keys<br />
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V<br />
* '''Gear Head'''<br />
** KB2300U - Causes kernel panic (B)<br />
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)<br />
* '''GMYLE'''<br />
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]<br />
* '''Inland''' <br />
** Inland USB Keyboard Model #70010<br />
* '''Jeway'''<br />
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)<br />
* '''Labtec'''<br />
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
* '''Logik'''<br />
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)<br />
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''<br />
* '''Logitech'''<br />
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)<br />
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)<br />
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)<br />
** K360 Wireless Keyboard - Occasional sticky keys. (B)<br />
** MK 260 Wireless Keyboard - Occasional sticky keys. (B)<br />
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)<br />
** G510 Gaming Keyboard - lagging or unresponsive keys.<br />
** MX5500 wireless keyboard and mouse with USB Bluetooth receiver - Unstable, looses connection without prior notice<br />
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).<br />
* '''Microsoft''' <br />
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)<br />
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)<br />
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.<br />
** Arc wireless - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)<br />
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)<br />
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000&nbsp;mA power supply unit)<br />
* '''Novatech'''<br />
** NOV-KEY2 - Causes kernel panic (B)<br />
* '''PC World Essentials'''<br />
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it caused a kernel panic -- tested on powered hub and direct.<br />
* '''Razer'''<br />
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.<br />
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED).<br />
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5&nbsp;V 500&nbsp;mA. (B)<br />
* '''SIIG'''<br />
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.<br />
* '''Texet'''<br />
** MB-768B standard keyboard (Rated 5&nbsp;V 1.5&nbsp;A (!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)<br />
* '''Trust''' <br />
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.<br />
* '''Unbranded'''<br />
** Compuparts<br />
** model no. HK-6106 (B)<br />
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.<br />
* '''Verbatim'''<br />
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)<br />
* '''Wilkinsons / TEXET'''<br />
** Model MB-768B causes kernel panic on debian6-19-04-2012.<br />
* '''Xenta'''<br />
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)<br />
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems. <br />
<br />
===Working USB Mouse Devices===<br />
The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* '''A4Tech'''<br />
** OP-530NU Padless Wired Mouse<br />
<br />
* '''Apple'''<br />
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).<br />
<br />
* '''Asda'''<br />
** HM5058 (Smart Price) Wired Mouse<br />
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> mouse)<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''ASUS'''<br />
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)<br />
** MG-0919 (wireless)<br />
<br />
* '''Belkin'''<br />
** F8E882-OPT (B)<br />
<br />
* '''Cellink'''<br />
** OPM-602 Small wireless optical mouse<br />
<br />
* '''Cerulian Technology'''<br />
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA<br />
<br />
* '''Dell'''<br />
** M-UVDEL1 (B)<br />
** MOC5UO (100&nbsp;mA)<br />
** M056U0A (B)<br />
** DZL-MS111-L (B) (100&nbsp;mA)<br />
** MS-111P (100&nbsp;mA)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.<br />
<br />
* '''Dynex'''<br />
** DX-WMSE (100&nbsp;mA) (B)<br />
<br />
* '''Fellowes'''<br />
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (B)<br />
<br />
* '''Filand'''<br />
** OP-102i Mini Optical Mouse<br />
<br />
* '''Genius'''<br />
** GM-04003A (B)<br />
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)<br />
** Traveler 515 Laser<br />
<br />
* '''HP'''<br />
** MN-UAE96 (The basic stock HP wired mouse)(B)<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''Kensington'''<br />
** Kensington Expert Mouse Trackball K64325<br />
** Kensington Expert Mouse "Slimblade" K72327US<br />
<br />
* '''Labtec'''<br />
** Corded Laser Glow Mouse 1600, rated 5&nbsp;V 100&nbsp;mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)<br />
<br />
* '''Lenovo'''<br />
** Wired Optical Mouse Model: MO28UOL<br />
<br />
* '''Logik'''<br />
** Wired Optical Glow Mouse Model: LGGMO10. (B)<br />
<br />
* '''Logitech'''<br />
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)<br />
** B105 Mouse for Laptops (OEM)<br />
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE<br />
** G5 Logitech Gaming Mouse (B)<br />
** G5v2 Logitech Gaming Mouse (B)<br />
** G500 Logitech Gaming Mouse (B)<br />
** G700 Logitech Wireless Gaming Mouse (B)<br />
** LX-700 Cordless Desktop Receiver (B)<br />
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).<br />
** M90 optical mouse<br />
** M185 Wireless Mouse (B)<br />
** M210 (part of the MK260 set) (B)<br />
** M305 Wireless Mouse<br />
** M310 Cordless Mouse<br />
** M325 Wireless Mouse<br />
** M505 USB wireless laser, model no: 910-001324 (B)<br />
** M510 Wireless Mouse (B)<br />
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)<br />
** M-BD58 Wheel Mouse (B)<br />
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)<br />
** M-BJ79 (B)<br />
** M-BT96a Optical Mouse<br />
** MX320/MX400 laser mouse (B)<br />
** MX518 Optical wheel mouse (B)<br />
** Optical USB Mouse (M/N 931643-0403)<br />
** Performance Mouse MX (B)<br />
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)<br />
** VX Nano Cordless Laser Mouse for Notebooks<br />
** Wheel Mouse (M/N BJ58)<br />
<br />
* '''Medion'''<br />
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5&nbsp;V 100&nbsp;mA. Works fb on model B with Raspbian Wheezy<br />
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
** Comfort Curve Mouse 3000 for Business<br />
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).<br />
** Compact optical mouse 500 V2.0 (B)<br />
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)<br />
** Microsoft Intellimouse Optical Mouse<br />
** Microsoft Wireless Laser Mouse 8000<br />
** Microsoft Wireless Mobile Mouse 1000<br />
** Microsoft Wireless Mobile Mouse 3500<br />
** Microsoft Wireless Mobile Mouse 4000<br />
** Microsoft Wireless Mouse 700 v2.0<br />
** Microsoft Comfort Mouse 4500<br />
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)<br />
<br />
* '''Perixx'''<br />
** PERIMICE-210 U Red (Part No.R1J) <br />
<br />
* '''Razer'''<br />
** Boomslang Collectors Edition 2007 (B)<br />
<br />
* '''Rosewill'''<br />
** Rosewill RM-C2U<br />
<br />
* '''Saitek'''<br />
** Notebook Optical Mouse (PM46)<br />
<br />
* '''Samsung'''<br />
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50&nbsp;mA) <br />
<br />
* '''Sun microsystems'''<br />
** Model: FID-638 , SunPN: 371-0788-01<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]<br />
<br />
* '''Swiftpoint'''<br />
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.<br />
<br />
* '''Targus'''<br />
** AKM02UK (Associated keyboard not checked)<br />
** AMU2701EUK (B)<br />
<br />
* '''Technika'''<br />
** TKOPTM2 (B)<br />
**TKD-211<br />
**TKNM110<br />
<br />
* '''Tesco'''<br />
** Wired optical mouse M211 (B)<br />
<br />
*'''The Pi Hut'''<br />
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Model 15313 - large, 5-button wireless mouse<br />
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base<br />
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)<br />
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087<br />
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.<br />
<br />
* '''Verbatiam'''<br />
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)<br />
<br />
* '''Xenta'''<br />
** MOW0810 (B)<br />
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Generic'''<br />
** Generic 2.4&nbsp;GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)<br />
<br />
===Problem USB Mouse Devices===<br />
The following is a list of specific mouse devices that have problems working with the Raspberry Pi<br />
* '''A4Tech'''<br />
** Model G7-630 Wireless Mouse, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''HP'''<br />
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors. <br />
<br />
* '''Logik'''<br />
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)<br />
<br />
* '''Logitech'''<br />
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000&nbsp;Hz out of the box, whereas the 518 is only 125&nbsp;Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.<br />
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot<br />
<br />
* '''Microsoft'''<br />
** Microsoft Touch Mouse - Does not see right clicks, Only left.<br />
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.<br />
<br />
* '''Razer'''<br />
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works, but the cursor doesn't move.<br />
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus<br />
<br />
* '''Roccat'''<br />
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)<br />
<br />
* '''Trust'''<br />
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)<br />
<br />
* '''Xenta'''<br />
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle<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 />
== USB Wi-Fi Adapters ==<br />
<br />
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. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.<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.<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 />
* '''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. <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.<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 />
<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 />
* '''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 Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)<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-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. Important : revision A1 works, revision B1 does not. Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<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-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.<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 />
*** 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 />
(B)<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 />
<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 />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<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 />
<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 />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.<br />
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module<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 supports Access Point and it be used for hostapd <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)<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: 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 />
* '''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]<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 (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-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.<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-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 />
<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 />
** [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)<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 />
* '''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 />
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].<br />
<br />
== USB Bluetooth adapters ==<br />
===Working Bluetooth adapters===<br />
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote<br />
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.<br />
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)<br />
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)<br />
** Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.<br />
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.<br />
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288<br />
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.<br />
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.<br />
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian<br />
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian<br />
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip<br />
** http://www.element14.com/community/message/58288<br />
* IOGear GBU321 (Broadcom BCM2045 Chipset)<br />
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.<br />
* Trust BT-2400p<br />
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).<br />
<br />
===Working Bluetooth/Wifi Combo adapters===<br />
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)<ref>http://www.lindy.co.uk/shop/showProductDetail.do?orderNumber=52213</ref><br />
<br />
===Problem Bluetooth adapters===<br />
* '''Belkin'''<br />
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.<br />
* '''Generic'''<br />
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.<br />
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.<br />
* Asus USB-BT211<br />
** Shows up as HCI device in Raspbian, but it does not scan or pair.<br />
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962<br />
<br />
== USB Ethernet adapters ==<br />
===Working Ethernet adapters===<br />
* '''AVM'''<br />
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.<br />
* '''Wintech'''<br />
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100&nbsp;mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]<br />
* '''LogiLink'''<br />
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.<br />
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed<br />
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter <br />
* '''Apple'''<br />
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.<br />
* '''Edimax'''<br />
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.<br />
* '''D-Link'''<br />
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)<br />
* '''LinkSys'''<br />
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.<br />
* '''Sabrent'''<br />
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)<br />
* '''Sitecom'''<br />
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.<br />
* '''A-Link'''<br />
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter<br />
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.<br />
<br />
The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190&nbsp;mA, so there might be stability issues if additional power is not provided.<br />
* '''Hama'''<br />
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.<br />
* '''Newlink'''<br />
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.<br />
<br />
===Problem Ethernet adapters===<br />
* Axago<br />
** Axago ADE-X1 10/100 Ethernet Adapter (USB: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out<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 />
* '''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://www.ti.com/product/pcm2704 PCM2704 98&nbsp;dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]<br />
<br />
=== Databases of sound cards that are known to work with Linux ===<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 />
==USB 3G Dongles==<br />
* Huawei E1750<br />
* Huawei E173<br />
* Huawei E220<br />
* Huawei E160 (AT commands only)<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 />
<br />
== USB IR Receivers==<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, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.<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)<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 />
*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 Webcams ==<br />
<br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
| PD1030<br />
|<br />
| <br />
| <br />
|<br />
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|WebcamHD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| Works fine without external power.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C270<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| With external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| With powered hub, detected out of box as Video0 V4L device<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Picture breaks up at the bottom<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
| <br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Up to 352x288. Higher resolutions do not work. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|Xbox Live Vision<br />
| <br />
| 045e:0294<br />
| Arch Linux <br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #A4B2CF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| The occasional frame is corrupted/stutters when running at 640x480<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| works out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
<br />
|-<br />
|}<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. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually<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 />
<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 />
== 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 />
<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'' and ''gtkterm''<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 />
<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 />
== 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 />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<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 SATA ===<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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== USB 3.0 Multi-Card Reader ===<br />
* US Robotics 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 />
=== 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 (Lazerus), 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 />
== 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 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 adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.<br />
<br />
===Working power Adapters===<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 />
** 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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''The Pi Hut'''<br />
** Micro USB Power Supply for the Raspberry Pi. 5&nbsp;V 1000&nbsp;mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])<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 />
* '''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 />
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 />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.<br />
<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 />
http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the Raspberry Pi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1&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 "Burning Raspberry!" 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 />
<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 />
http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=4<br />
<br>config_hdmi_boost=4<br />
<br>overscan_top=-30<br />
<br>overscan_bottom=-30<br />
<br>overscan_left=-30<br />
<br>overscan_right=-30<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 />
According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
<br />
According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but it is very pricey compared to the alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4&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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"<br />
<br />
Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=16<br />
<br>hdmi_force_hotplug=1<br />
<br>disable_overscan=0<br />
<br />
<br />
And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. It is very cheap, but it works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC). <br />
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.<br />
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 />
Marcin.<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 />
== 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>AutoStatichttps://elinux.org/index.php?title=RPi_VerifiedPeripherals&diff=231914RPi VerifiedPeripherals2013-03-18T19:16:37Z<p>AutoStatic: /* USB Sound Cards */</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 />
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.<br />
<br />
If you use a powered hub and the Raspberry Pi PSU together consider powering them from the same power bar with switch, so you can turn them on simultaneously., especially if the HUB tries to feed the Raspberry Pi through their interconnect cable, due to the 100&nbsp;mA limiting fuse in the Raspberry Pi, the Raspberry Pi will be partially powered which may cause problems (unwanted writes to the SD card).<br />
<br />
===Working USB Hubs===<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''USB Version'''<br />
| '''Number of Ports'''<br />
| '''Power Rating*'''<br />
| '''Powers Raspberry Pi'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Atlantis<br />
|HUB USB2.0 7P<br />
|P014-GH902-B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2&nbsp;A<br />
|Verified<br />
|Powers the pi. Seems very good, tested with: a keyboard, a mouse, a numpad and an Xbox joypad<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|4-Port Ultra-Slim Desktop Hub<br />
|F4U040<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.6&nbsp;A<br />
|Verified<br />
| Powers the pi quite well, 4.85V across TP1&2 during idle and load. The PSU for the hub is a 2.5A 5v made in china. Seems solid. Does backfeed the mini USB port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|8-Port ExpressBus for iMac<br />
|F5U010<br />
|<br />
|USB 2.0<br />
|8-Port 7x"A" 1x"B"<br />
|<br />
|Verified<br />
|PSU 6v 4A Powering a 256 "A" RPi with the hub. With the USB output of the RPi connected to the one "B" port<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U224<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|TetraHub™ USB 2.0 4-Port Hub<br />
|F5U231<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Hub<br />
|F5U234<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 500&nbsp;mA per Port<br />
|Verified<br />
|No backfeed, can power the RPi. Comes with a 2.4&nbsp;A power supply. The user manual [http://www.belkin.com/pyramid/documents/external/P75268ea_F5U234ea.pdf] says ''&ldquo;Per Port Current Self-Powered Mode: 500mA (max)&rdquo;''. However, I've attached a HD that requires 850&nbsp;mA and it worked fine.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.8&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|MyEssentials 7-Port High-Speed USB 2.0 Hub<br />
|F5U259-ME<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 4-Port Lighted Hub<br />
|F5U403<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Lighted Hub<br />
|F5U700<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|Cascaded hub, only 3 ports work [http://forum.stmlabs.com/showthread.php?tid=5396&pid=60068#pid60068] [http://www.amazon.com/gp/product/B000SDW84K]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hub 2-en-1<br />
|F5U706ea<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Hi-Speed USB 2.0 7-Port Hub <br />
|F5U237v1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 2.5&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U040v<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5 V - 2.6 A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Belkin<br />
|Ultra-Slim Desktop Hub<br />
|F4U039qukAPL<br />
|05e3:0608<br />
|USB 2.0<br />
|7-Port<br />
|<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Benq<br />
|<br />
|E2220HD<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Biltema<br />
|<br />
|23-924<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|BUFFALO<br />
|4 Port Hub<br />
|BSH4aAE06<br />
|05e3:0608<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V <br />
|Verified<br />
|No Problem using Webcam & Wi-Fi Dongle. seen As Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Cyberpower<br />
|High-speed Hub<br />
|CP-H720P<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|3.6&nbsp;A<br />
|Verified<br />
|May Contain dual 05e3:0608 instead of 0409:0050<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2001FP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|SP2309W<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|2407FWP<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built-in hub - 6-in-1 card reader Works, but it cannot read SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dell<br />
|<br />
|U3011<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|<br />
|Not Verified<br />
|Monitor with built in Hub - Card Reader Works - May work with SDXC<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|<br />
|B/N61393<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Delock<br />
|USB 2.0 External Hub 7 Port<br />
|B/N87467<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5&nbsp;V - 3.5&nbsp;A<br />
|Verified<br />
|You can Power Raspberry Pi using one USB Port of the Hub there is no backfeeding, measured 4,88V on Idle and 4,82V on load on TP1-TP2.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Deltaco<br />
|<br />
|UH-715 Rev 2<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|<br />
|<br />
|0409:0050<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Dynex<br />
|Dynex USB 2.0 7 Port Hub<br />
|DX-HB7PT<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5.0&nbsp;V / 2.0&nbsp;A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|D-Link 7 Port USB Hub<br />
|DUB-H7/B<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.misco.co.uk/product/94282/D-Link-7-Port-USB-Hub] Power USB slots can be used to power Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7 High Speed USB 2.0 7-Port Hub<br />
|BUBH7A A5<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF]<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-H7<br />
|EUBH7EB H/W Ver:B1<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|3.0&nbsp;A<br />
|Verified<br />
|[http://www.amazon.fr/gp/product/B0000B0DL7/] 7 ports including 2 ports 1.2 A sucessfully power RPI<br />
<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|D-Link<br />
|DUB-4 High Speed USB 2.0 4-Port Hub<br />
|DUB-H4<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|2.0&nbsp;A<br />
|Verified<br />
|[http://www.newegg.com/Product/Product.aspx?Item=N82E16817111131] Charging port doesn't power Raspberry Pi<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Digicom<br />
|<br />
|<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5&nbsp;V - 2.0&nbsp;A<br />
|Not Verified<br />
|[http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/MiniHubUsb204P#]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|ednet<br />
|USB 2.0 7 port Hub<br />
|85014<br />
|<br />
|2.0<br />
|7-Port<br />
|<br />
|Not Verified<br />
|Works with keyboard, mouse, audio devices<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GigaWare<br />
|USB 2.0 4 port Hub<br />
|Model 26-160<br />
|<br />
|2.0<br />
|4-Port<br />
|<br />
|Verified<br />
|Works with Raspbian for powering webcams. This is the only powered hub on shelves at Radioshack as of early 2013.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|König Electronic<br />
|7 port USB2.0 HUB<br />
|CMP-USB2HUB55<br />
|1a40:0201<br />
|2.0<br />
|7-Port<br />
|2.0A<br />
|Verified<br />
|Backpowers Raspberry Pi well.<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medi@com<br />
|USB 2.0 4 ports Hub<br />
|M-HX30<br />
|<br />
|2.0<br />
|4-port<br />
|<br />
|Verified<br />
|Very small USB Hub. Powers the Rapsberry Pi and an 2.5" external HDD (LaCie Rikiki 500Gb) without problems. I already tried to connect another HDD without problems even if is not yet been mounted on linux.<br />
[http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1988]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|mbeat<br />
|13 Port USB Hub<br />
|USB-M13HUB<br />
|<br />
|USB 2.0<br />
|13-port<br />
|5V - 3A<br />
|Verified<br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Monoprice<br />
|Aquagate USB Hub<br />
|5328<br />
|<br />
|2.0<br />
|7-port<br />
|2.0&nbsp;A<br />
|Verified<br />
|Has separate USB In port, in theory should prevent backfeeding (but that is not verified). get about 4.9V across TP1/TP2 when idling with Raspbian. [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030702&p_id=5328&seq=1&format=4]<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable <br />
|7 Port High Speed USB Hub<br />
|USB2-HUB-AG7<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 3A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB-AG7/] Better than usual power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Plugable<br />
|4 Port Hub with Battery Charging 1.1 Support<br />
|USB2-HUB4BC<br />
|<br />
|USB 2.0<br />
|4-Port<br />
|5V - 2.5A<br />
|Verified<br />
| [http://plugable.com/products/USB2-HUB4BC/] High quality power supply for a 4 port hub (to support BC 1.1 current). US plugs version only. Can Power Raspberry Pi via microUSB from a hub port, plus three more devices. USB Audio peripheral tested and working. No back-voltage on upstream connection. Widely used with success on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|10 Port USB 2.0 Hub<br />
|USB2-HUB10S<br />
|<br />
|USB 2.0<br />
|10-Port<br />
|5V - 2.5A<br />
|Not Verified<br />
| Possibly because 10 ports hubs combine 7 + 4 cascaded controllers, seems to have corner cases where it won't power the Pi at boot. Not recommended. Get their USB 2.0 7 port version<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|4 Port USB 3.0 Hub<br />
|USB2-HUB-81X4<br />
|<br />
|USB 3.0<br />
|4-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #FFFDFD;"<br />
|Plugable<br />
|7 Port USB 3.0 Hub<br />
|USB2-HUB7-81X<br />
|<br />
|USB 3.0<br />
|7-Port<br />
|5V - 4A<br />
|Not Verified<br />
| The high-power 4 A power adapter makes this a tempting purchase, but some users report problems connecting devices with a USB 3.0 hub. Since Pi can't benefit from USB 3.0, better off to use one of the Plugable USB 2.0 7 or 4 port hubs like USB2-HUB-AG7 to both power the Pi and attached USB devices.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
|Plata 4 port USB 2.0 hub<br />
|18687<br />
|<br />
|2.0<br />
|4-port<br />
|1.0&nbsp;A<br />
|Not Verified<br />
|Probably not suited to power the Rapsberry Pi but works well as a hub on the Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Zipp<br />
|USB 7-Port HUB<br />
|N294<br />
|<br />
|USB 2.0<br />
|7-Port<br />
|5V - 2.0A<br />
|Verified<br />
|Powers both the RPi and a WD Portable 1TB Drive without problems - $14.99 at Big W (Australia)<br />
<br />
|-<br />
|}<br />
<br />
<br />
'*' Power Ratings may not be completely accurate, use as rough guideline rather than fact.<br />
</div><br />
<br />
<br />
*'''Acme'''<br />
** USB 2.0 hub 4 port ([http://www.acme.eu/en-us/product/019188 ACME]) Based on NEC μPD720114 USB2.0 Hub Controller USB ID 0409:005a '''NOTE!''' It is bus-powered hub, but it is very cheap and small and works after a small modding: on USB-hub board you have 4 holes: V, D+, D- and GND. Connect GND, D+ and D- to the Raspberry Pi, and additionally connect GND and +5&nbsp;V from power supply to the same holes on USB-hub GND and V. Now there is common contacts: GND, D+ and D- between Raspberry Pi and hub needed to work, and additional power for USB devices, connected to the hub. Tested on my Raspberry Pi.<br />
<br />
<br />
*'''Digitus'''<br />
** 7-port USB2.0 Powered Hub. Model DA-70226.<br />
*'''Eminent'''<br />
** [http://www.eminent-online.com/en/product/22/em1102-4-port-usb-hub---black.html] EM1102 4 Port USB 2.0 Hub with 1&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
** [http://www.eminent-online.com/en/product/27/7-port-usb-2-0-hub.html] EM1107 7 Port USB 2.0 Hub with 2&nbsp;A power adapter. It's able to power the Raspberry Pi, external HDD and other peripherals.<br />
* '''GearHead'''<br />
** [http://www.amazon.com/gp/product/B004OBZ088/] GearHead 4 Port Hub with Energy Saving Power Switch (5&nbsp;V, 1&nbsp;A)<br />
*'''Gembird'''<br />
** Gembird UHS 242 4-port USB 2.0 Hub (5V DC, 1A). '''NB:''' This is a 4-port switching hub that enables the "sharing" of up to four USB devices between two computers. Whilst it may be powered externally, it does take power from both connected computers. If one of them is, say, a netbook or laptop, that may provide sufficient extra power to enable the use of USB devices that the Pi alone cannot handle.<br />
* '''Genesys Logic (sold at Fry's)'''<br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0608) (Other brands include Gigaware, Hama and Belkin, same ID shows up in lsusb) - works, but increases packet loss problems<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=297664#p297664</ref><br />
** Genesys Logic 4-Port USB 2.0 Hub (ID 05e3:0606) (Other brands include i-Rocks, same ID shows up in lsusb)<br />
* '''Hama'''<br />
** Hama 4-way USB 2.0 Hub<br />
** Hama 7-way USB 2.0 Hub (identified as two "05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB" but Pi boots OK only with 1.2A power, not with 1A..)<br />
*'''HP'''<br />
** HP ZR2240w 21.5" Monitor with built in 2-Port USB Hub (B)<br />
<br />
*'''Laser'''<br />
** "7 port USB hub with AC adapter Version 2.0". 5&nbsp;V 1&nbsp;A (found at Harvey Norman Australia for $24.95 and Australia Post Shops for $9.95). You can power the Raspberry Pi by connecting both the main USB connector to the Raspberry Pi USB port, '''and''' from a spare USB port back to the power micro USB socket. If you don't do both, boot-loops are likely to occur.<br />
*'''Logik'''<br />
** [http://www.currys.co.uk/gbuk/logik-lp4hub10-4-port-powered-usb-hub-04979038-pdt.html] LP4HUB10 4-Port USB Hub. '''Throws errors when used with Fedora remix 14'''<br />
** Logik L4THUB10 4 Port powered hub works fine under Raspbian/Wheezy/model B. Captive USB cable, 2&nbsp;A power supply, convenient single top mounted USB socket. Unlike my last hub, will power Wi-Fi!<br />
*'''LogiLink'''<br />
** UA0085 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0090 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A<br />
** UA0091 USB 3.0 Hub, 4-Port with PSU 5&nbsp;V, 4&nbsp;A. Connected with USB2.0 cable. 1&nbsp;A per port, able to support USB HDD drives and other power hungry devices. Tested with kernel 3.1.9-cutdown, Wheezy. <br />
** UA0096 USB 2.0 Hub, 10-Port with PSU 5&nbsp;V, 3.5&nbsp;A (Not suitable for powering Raspberry Pi because it doesn't work unless there is working USB input present even with PSU plugged in.)<br />
** UA0160 USB 2.0 Hub, 4-Port with PSU 5&nbsp;V, 2&nbsp;A. Able to power the Raspberry Pi, keyboard, mouse and LogiLink UA0144 USB Ethernet adapter. (More testing to come.) Was not able to record audio properly via a Soundblaster Play! device.<br />
* '''Macally'''<br />
** [http://www.macally.com/EN/?page_id=2312] Hi-Speed 7-Port USB 2.0 Powered Micro HUB, AC Powered. Includes a 2000&nbsp;mA wall-wart (US style)<br />
* '''Manhattan'''<br />
** [http://manhattan-products.com/en-US/products/6500-hi-speed-usb-2-0-micro-hub] (#160612) Hi-Speed USB 2.0 Micro HUB, AC Powered (identifies as ID 05e3:0608 Genesys Logic) Includes a 1000&nbsp;mA wall-wart (US style)<br />
** [http://manhattan-products.com/en-US/products/9583-mondohub] (#161718) MondoHub 28 Port USB 3.0 & USB 2.0 HUB (24 USB 2 ports @500&nbsp;mA each) + (4 USB 3.0 Ports @900&nbsp;mA each) Power Switches on each port, AC Powered and Includes a 5&nbsp;V 4&nbsp;A wall-wart (US style)<br />
*'''Newlink'''<br />
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5&nbsp;V 1&nbsp;A<br />
** NLUSB2-222P 4 port USB 2.0 Hub with 5&nbsp;V 2&nbsp;A PSU (Available From [https://www.modmypi.com/shop/raspberry-pi-accessories/New-Link-4-Port-USB-Hub-(USB-2.0-with-Mains-Adaptor) | ModMyPi])<br />
*'''Nilox'''<br />
** Nilox USB 2.0 4port HUB model HUB4USB2AC with PSU 5&nbsp;V 1.0&nbsp;A<br />
* '''Plugable'''<br />
** [http://plugable.com/products/USB2-HUB4BC/] USB2-HUB4BC 4 Port USB 2.0 Hub with BC 1.1 Fast Charging. 5&nbsp;V 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port. USB Audio peripheral tested and working.<br />
** [http://plugable.com/products/USB2-HUB10S] USB2-HUB10S 10 Port USB 2.0 Hub 2.5&nbsp;A power supply. Powering Raspberry Pi via microUSB from a hub port.<br />
** [http://plugable.com/products/USB2-HUB-AG7/] USB2-HUB-AG7 7 Port USB 2.0 Hub with 5&nbsp;V 3&nbsp;A power supply. There are US and UK power supply versions and it can be ordered in US and (for the UK version) many countries in Europe. There is a video showing this hub powering both the Raspberry Pi several peripherals at once[http://www.youtube.com/watch?v=pDA7MxFtoS0]. Confirmed to work with Element14 WiPi Wi-Fi dongle and Seagate external hard drive (simultaneously)<br />
<br />
* '''Pluscom'''<br />
** Pluscom 7 Port USB 2.0 Hub Model U7PH-3A with 3&nbsp;A PSU. USB ID 1a40:0101. Powering Raspberry Pi via microUSB from a hub port. Internally two 4 Port switches linked. Leaks power back up USB data cable to Raspberry Pi, but it is not really a problem when powering Raspberry Pi at the same time.<br />
*'''Satechi'''<br />
** ST-UH12P 12 port powered hub with 2 Control Switches. Also works while powering the Raspberry Pi.<br />
*'''Staples (Business Depot) (Bureau EN GROS)'''<br />
** Staples 4-port hub Item 607477-CA<br />
*'''StarTech.com'''<br />
** StarTech.com 7-port Compact USB 2.0 Hub (ST7202USB). Comes with 5&nbsp;V 2&nbsp;A supply. Shows in lsusb as two Genesys Logic, Inc. USB-2.0 4-Port HUBs (05e3:0608). Back powers Raspberry Pi (just, voltage across TP1 & TP2 is a little low when powered from this hub).<br />
*'''SumVision'''<br />
** Sumvision Slim 4 Port High Speed USB 2.0 HUB with PSU 5&nbsp;V 1.0&nbsp;A (from [http://www.7dayshop.com/catalog/account_history_info.php?page=1&order_id=5130107 | 7dayshop ])<br />
*'''Sitecom'''<br />
** CN-032 4 Port USB 2.0 Pocket Hub. Works for powering the Raspberry Pi, an USB WLAN Adapter, wireless Kbd+Mouse. Using an 2500&nbsp;mA Voltcraft <br />
** CN-060 4 Port USB 2.0 Hub powered with AC Adapter (1&nbsp;A). Powering Raspberry Pi via microUSB from a hub port.<br />
** CN-061 7 Port USB 2.0 Hub powered with AC Adapter. There is a voltage problem on the left half of the hub (4 ports) that do not deliver enough current to feed a wifi dongle (tested with an RTL8191S); you should not use these ports for anything important (keyboard keys will stick, self-powered USB hard disk will reset continuously). The remaining 3 ports on the right half are instead working as expected. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=24247]<br />
*'''Sweex'''<br />
** US014 4 Port USB 2.0 Hub<br />
*'''Targus'''<br />
** ACH81xx 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wi-Fi Dongles)<br />
** ACH63EU 4-port. Using a 5&nbsp;V 2&nbsp;A power supply, which isn't supplied with the hub, it is able to power the Raspberry Pi as well.<br />
*'''The Pi Hut'''<br />
** 7 Port USB Hub (from [http://thepihut.com/products/7-port-usb-hub-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
*'''Trendnet'''<br />
** [http://www.trendnet.com/products/proddetail.asp?prod=130_TU2-700&cat=49] TU2-700 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2&nbsp;A)<br />
*'''Tripp-Lite'''<br />
** [http://www.tripplite.com/en/products/model.cfm?txtModelID=3167] U222-007-R 7 Port Powered USB 2.0 Hub with AC Adapter (5&nbsp;V 2.5&nbsp;A) Powering Raspberry Pi from the hub works.<br />
*'''Ultron'''<br />
** [http://www.ultron.de/v1/produktansicht.php?artnr=67072&kid=bfa8340c4e245...&l=en&WGType=Neue+USB-HUBS] UHN-710 7-port powered hub with PSU 5&nbsp;V, 3&nbsp;A. USB ID 1a40:0201.<br />
*'''VANTEC'''<br />
** 4 Port USB 2.0 Powered Hub Model: UGT-MH304. 5&nbsp;V 2&nbsp;A AC/DC adapter. Go 2.0 Mini hub.<br />
*'''Z-TEK'''<br />
** Z-TEK 7-port powered hub with PSU 5&nbsp;V, 4&nbsp;A. USB ID 1a40:0201.<br />
*"Unknown"<br />
** 10(7-4) port hub idVendor=1a40, idProduct=0201 / idVendor=1a40, idProduct=0101 works<br />
<br />
===Problem USB Hubs===<br />
<br />
Please check known workarounds [http://elinux.org/Rpi_USB_check-list here] before adding to the list<br />
<br />
*'''Addon'''<br />
** 7-Port Powered Hub - labelled ADDUH070P - Gives constant Eth0 errors on boot.<br />
*'''Belkin'''<br />
** 7-Port Powered Mobile Hub - device labelled F4U018, packaging labelled F5U701. lsusb reveals it to be two Genesys Logic 4-port hubs based on the GL850G chipset (vendor: 0x05e3 product: 0x0608) ganged together. Yields a lot of "handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" errors and device resets in /var/log/messages. Low speed devices such as keyboards work OK, Wi-Fi/mass storage is unreliable or broken. -- No error messages with the latest kernel, but it is still unstable with mass storage devices. Also, leaks current back to the Raspberry Pi (can be fixed by overtaping GND and +5&nbsp;V pinouts)<br />
** F4U022 7-Port powered USB hub (powered 5&nbsp;V, 2.6&nbsp;A), same as F4U018<br />
** 7-Port Powered Hub - device labled F5U237 Rev.3 - ID 050d:0237 Wired Ethernet fails to connect; gives "DWC OTG HCD URB enqueue failed adding QTD. Error status -4008" Result is same as DUB-H7 below.<br />
** F5U404 Hi-Speed USB 2.0 4-Port Mobile Hub. Faulty/bad design; Leaks current back up the cable to the Raspberry Pi.<br />
** F5U307 Hi-Speed USB 2.0 7-Port Hub (Powered, able to apply power to Raspberry Pi via micro USB from this hub at same time) It work's sometimes. (Works always without powering the Raspberry Pi, haven't tried that)<br />
<br />
*'''Dell'''<br />
** Dell U2410 Monitor Built-in 4 Port Hub - Shows up as a pair with 0424:2514 and 0424:2640. Standard Microsystems Corp. USB 2.0 Hub. When connecting some devices it kills the Ethernet with "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x0000011X" errors. It did work for a keyboard and webcam. Bluetooth that works connected directly to the Raspberry Pi triggers the error.<br />
<br />
*'''DELTACO'''<br />
** 7-Port USB Hub UH-713 Rev 3. This one consists also of two 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUBs connected together. The power supply is rated at 5 V 2 A. It kills Ethernet when X11 is started.<br />
<br />
*'''Dynex'''<br />
** 7-Port USB Hub - Does not work in Debian 19-04 image.<br />
** DX-HB7PT 7-Port USB Hub - As per the Gear Head below, it's 2 daisy-chained Genesys Logic 05e3:0608 devices. Appears to result in significant slow downs when the USB is under load, such as running the root file system from a USB drive.<br />
<br />
*'''Dynamode'''<br />
** 7-Port USB 2.0 Hub (Silver and black). Feeds power back up the interconnect to the Raspberry Pi causing the power LED to light on the Raspberry Pi if the hub is powered on, but the Raspberry Pi is not. The Raspberry Pi also fails to boot when powered off this hub, with or without the interconnect plugged in. Stops the network from working when connected to the Raspberry Pi after booting the Raspberry Pi - cannot ssh to the Raspberry Pi. Best avoided. :-( Shows up in ''lsusb'' as a pair of ''ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB'' which is interesting. - Confirmed. This hub also appears unable to power an external USB drive using a y-cable as it gives the error -71 message in dmesg (when providing external power to the Raspberry Pi).<br />
** 4-Port High-Speed USB 2.0 Hub (USB-H40-A2.0), came with with a 1&nbsp;A power supply. Leaks power to the Raspberry Pi through the uplink. Doesn't work with Raspberry Pi, unless the Raspberry Pi is powered by a second power source. This hub is completely generic and I've seen it being sold under different brand names as well. Therefore, a picture is [http://i.imgur.com/BPZ3j.jpg included] for easy identification. <br />
<br />
*'''D-Link'''<br />
** 7-Port USB Hub DUB-H7 (Crashes USB stack, including Ethernet, when plugging / using some peripherals). (See note above, it works with some distros and/or with latest firmware)<br />
<br />
*'''E-Solution'''<br />
** 4-Port 2&nbsp;A Supply (Does not detect at all during boot or after boot- no messages) [IC = Alcor Micro Corp (AU6254)]<br />
<br />
*'''Fosmon'''<br />
** 7-Port USB 2.0 Hub with 1&nbsp;A Power Supply (Causes interference with other USB devices and sends enough power to light up the Raspberry Pi with it's Micro USB cable unplugged).<br />
<br />
*'''Gear Head'''<br />
** UH7250MAC 7-port powered hub. Internally, two daisy-chained Genesys Logic 05e3:0608 devices. Causes Ethernet instability when used under very specific circumstances, in X11.<br />
** <strike>UH5200T 4-port powered hub. As of 2012-08-16 Wheezy, if any USB 1.x device (a keyboard, for example) is plugged into this hub, Ethernet stops, and USB interrupts for other devices get dropped (keys repeating forever), etc. Occurs even if power is not attached (not a power leakage problem).</strike> Appears working after a bootloader and/or firmware update on 9/12. Also, turned out to be somewhat more specific to the combination of two particular low-speed devices.<br />
<br />
*'''Hama'''<br />
** 4-Port USB 2.0 "bus hub", model 78496 (?). Only works for low power devices (card readers?), but it does not work for power hungry devices (HDD and WLAN). It doesn't boot when hub connected to Raspberry Pi. The funniest thing is that Raspberry Pi powers on when I plug in this hub to normal size USB port (not that small dedicated port). idVendor=05e3, idProduct=0608<br />
<br />
*'''Kensington'''<br />
** 7-Port Dome Hub model no 1500129 (Possible problems with malfunctioning keyboard, kills mouse when GUI started).<br />
<br />
*'''iBall'''<br />
** Piano 423 4-Port USB hub. Listed in lsusb as Genesys Logic. Fails to deliver enough power to connected devices even when using AC power supply.<br />
<br />
*'''Inland'''<br />
** 4-Port USB 2.0 Cable Hub model no 480426 (Some devices work, some don't, cheap unshielded untwisted wire design)<br />
<br />
*'''Logik'''<br />
** LP7HUB11 7-Port USB Hub. (Ethernet failed, slow response, in LXDE. Happened whether or not the hub's independent power supply was connected to the hub.)<br />
<br />
*'''LogiLink'''<br />
** 7-Port powered USB-Hub with switch UA0124. Does not work even with a x86 Linux box. Does work with Windows and comes with a beefy 3,5 A power supply that works with a Belkin 7-port mobile USB-Hub to power a cluster of 4 Raspberries.<br />
<br />
*'''Soniq'''<br />
** 4-Port 5&nbsp;V supply. Model number CUH100. (B). Appears to draw power away from the Raspberry Pi, even when the Raspberry Pi has an isolated power line. Netgear WNA1100 Wi-Fi Adapter (which is known to work in other setups is recognized, but it is unresponsive).<br />
<br />
*'''Targus'''<br />
** ACH115EU 7-port powered hub. 5&nbsp;V 3&nbsp;A power supply. Arduino communicates with Raspberry Pi when connected directly to Raspberry Pi's USB port, but it hangs as soon as if connected via ACH115. Also sometimes smsc95xx eth0 Failed to read register index 0x00000114 etc. errors in syslog when used.<br />
<br />
*'''TCM'''<br />
** Model 234298 s/n T634007737 powered hub. 4 ports plus card reader. 1&nbsp;A power supply. Model B, Wheezy Raspbian works OK with keyboard/mouse, but there are problems with Wi-Fi no connects. (insufficient power?)<br />
<br />
*'''Trust'''<br />
** 10-port USB 2.0 Hub (powered). Prevents Ethernet from being recognised.<br />
** SliZe 7 port USB 2.0 Hub (powered) - Item number 17080 (Barcode 8 713439 170801). Prevents Ethernet from being recognised. Keyboard sends multiple characters. <br />
<br />
*'''Unbranded / Multiple Brands'''<br />
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably'' due to an inadequate power supply. -- I replaced the terrible power supply with a very good one, kept getting "DEBUG: handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK" in dmesg, with no devices plugged in to the hub (with or without the power supply in). Measurements by [[User:TrevorGowen|TrevorGowen]] ([[User talk:TrevorGowen|talk]]) of the power loading behaviour of an example of this type of hub and its supplied PSU are logged at [http://www.cpmspectrepi.webspace.virginmedia.com/raspberry_pi/MoinMoinExport/PoweredUSBHubs.html CPM-Spectre-Pi...PoweredUSBHubs], together with similar measurements of other devices.<br />
** Generic 7-port black hub with Genesys Logic GL850A chipset<br />
** Cerulian 10 Port USB 2.0 Top Loading Hub with 2&nbsp;A supply (kills mouse and network port)<ref>http://www.raspberrypi.org/forum/absolute-beginners/cheap-powered-usb-hub-uk/#p76452</ref><br />
** [http://www.monoprice.com/products/product.asp?c_id=103&cp_id=10307&cs_id=1030701&p_id=226 USB 2.0 4 PORT INT/EXT DUAL HUB BAY] -- Genesys Chipset -- idVendor=05e3, idProduct=0607 -- low speed devices worked, but there are strange USB failures when X session started. High speed devices such as hard drives had failures.<br />
<br />
== USB Remotes ==<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 />
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work. '''Please be aware that some of these keyboards were probably used with a powered hub'''<br />
=== Working USB Keyboards ===<br />
The following is a list of specific keyboards known to work and which appear to work fault-free.<br />
<br />
* '''A4 Tech'''<br />
** Model KL-5 USB Keyboard, 20&nbsp;mA.<br />
<br />
* '''ABS'''<br />
** M1 Heavy Duty Professional Gaming Mechanical Keyboard (B)<br />
<br />
* '''Action Star'''<br />
** ACK-5010U Mini Keyboard And Mouse<br />
<br />
* '''Accuratus'''<br />
** KYB-Toughball-HI<br />
<br />
* '''Acer'''<br />
** KG-0917 Wireless Keyboard And Mouse Bundle (B)<br />
** KU-0906 Compact Keyboard (B) (Also known as Genius LuxeMate i200 Keyboard)<br />
** SK-9625 Multimedia Keyboard (B) (multimedia functions not tested)<br />
<br />
* '''Adesso'''<br />
** [http://ergoprise.com/product_images/j/699/ADP-PU21_big__14173_zoom.jpg PS/2 to USB Adapter] ADP-PU21, 100&nbsp;mA (tested only with keyboards) Any PS/2 keyboard will work only if it will work with a reduced operating voltage.<br />
** Model AKB-410UB. Keyboard with Touchpad.<br />
<br />
* '''Apple''' (Apple keyboards that have USB ports require an external powered hub to work, and do not work on the Raspberry Pi directly! Note: Apple keyboard works fine using the latest Raspberry Pi, even when connected directly (and with mouse connected))<br />
** [http://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Apple_iMac_Keyboard_A1243.png/800px-Apple_iMac_Keyboard_A1243.png Apple Keyboard with Numeric Keypad (aluminium/wired) A1243]<br />
** [http://upload.wikimedia.org/wikipedia/commons/8/81/Apple_Keyboard_A1242.jpg Apple Keyboard (aluminium/wired) A1242]<br />
** [http://upload.wikimedia.org/wikipedia/commons/c/c5/Apple_Pro_Keyboard_black.jpg Apple Pro Keyboard M7803]<br />
<br />
* '''Asda'''<br />
** Basic Wired Keyboard HK2026 (B)<br />
** Basic Wired Keyboard HK3014<br />
*** (Please note when I put this keyboard through Newlink USB hub, it didn't work as expected)<br />
** Premium Wireless Keyboard (white keys, silver back) HK8028<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''Asus'''<br />
** KS-631U (comes with Asus Vento KM-63 keyboard/mouse set, not using powered hub) (B)<br />
<br />
* '''Banbridge'''<br />
** [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter] (B) (Tested with Logitech C-SF17 Cordless Desktop Express)<br />
<br />
* '''BTC - Behavior Tech Computer Corp.'''<br />
** Wired Portable Keyboard Model 6100 US (86+9 keys)<br />
*** Works with or without a powered hub<br />
** Wireless Multimedia Keyboard with build in pointer/mouse Model 9029URF III (86+17 keys) (B)<br />
** [http://www.btc.com.tw/english/2-7-07keyboard.htm Wired Multimedia keyboard 6311U/6310U] - rated at 5&nbsp;V/100&nbsp;mA, works directly<br />
<br />
* '''Bush'''<br />
** Wired Slimline Keyboard KU-0833<br />
*** This does not require a USB hub in order to work with the Raspberry Pi<br />
*** In the UK, it is available from Argos for £9.99<br />
<br />
* '''Cerulian''' <br />
** Mini wireless keyboard and mouse deskset (B)<br />
<br />
* '''CD Training''' <br />
** [http://www.cd-training.fr/?&feed=product&product_id=308 Wireless Combo Keyboard and Mouse (SolClavGlos)]<br />
<br />
* '''Cherry'''<br />
** CyMotion Master Linux (B)<br />
** RS 6000 USB ON<br />
** G84-4100PTMUS (B) (Compact keyboard. Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** G85-23100DE-2 (B) (Rated 40&nbsp;mA, tested with RPi powered by a 1000&nbsp;mA power supply unit)<br />
** G82-24800DE wireless keyboard and mouse combo marketed overwhelmingly as "Cordless Desktop eVolution Sirius XT Wireless", works without hub.<br />
<br />
* '''Compaq'''<br />
** Compaq Internet Keyboard KU-9978 (049f:000e). Rated 5&nbsp;V 100&nbsp;mA. Works directly connected to Raspberry Pi<br />
<br />
* '''Das Keyboard'''<br />
** Model S Professional Keyboard (Built in USB hub not tested) (B)<br />
** Model S Ultimate Keyboard (Built in USB hub working) (B)<br />
<br />
* '''Dell'''<br />
** SK-8115 (B) (Rated 100&nbsp;mA. Works directly in Raspberry Pi)<br />
** L100 (B)<br />
** RT7D40 (100&nbsp;mA. Works directly in Raspberry Pi)<br />
** RT7D50 (75&nbsp;mA) (run "sudo dpkg-reconfigure keyboard-configuration")<br />
** KB1421 (100&nbsp;mA)<br />
** KB2521 (100&nbsp;mA)<br />
** KB212-B (Works directly in Raspberry Pi, without powered hub)<br />
** 1HF2Y (Works directly in Raspberry Pi)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** USB Keyboard 413c:2107 - Works with and without USB hub<br />
<br />
* '''Delux'''<br />
** K8050<br />
<br />
* '''Digicom'''<br />
** WKEYPE01 Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.verkkokauppa.com/fi/product/52783 Prodige Nanox]<br />
<br />
* '''Dynex'''<br />
** DX_-WKBD (60&nbsp;mA) (B)<br />
** DX_-WKBDSL (Hot keys not yet tested with Debian) (tested through non-powered 3 dongle USB hub) (B)<br />
<br />
* '''EAPPLY'''<br />
** EBO-013 Wireless 2.4&nbsp;GHz compact keyboard with touchpad. Rated <40&nbsp;mA works directly from Raspberry Pi. eBay ref 260962010276 from Shenzen, China.<br />
<br />
* '''Emprex'''<br />
** Wireless Media Control Keyboard With Trackball 9039ARF III (Media functions untested)<br />
<br />
* '''Fujitsu Siemens''' <br />
** KB SC USB UK (!)<br />
** KB910 USB, with led light on the highest level (B)<br />
** KB400 USB US<br />
<br />
* '''GE''' <br />
** 98139 Rev.K1 (Power Keyboard) (lsusb shows it as "0b38:0010 Gear Head 107-Key Keyboard") - works without a hub (i.e. directly connected) (B)<br />
<br />
* '''Gear Head''' <br />
** KB3700TP (USB Mini Smart Touch Touchpad Keyboard) (B)<br />
** KB3800TP (Wireless Touch Mini Touchpad Keyboard with Smart Touch) (B)<br />
*** Works when plugged directly into Raspberry Pi, did not work with powered hub (could be a hub issue)<br />
** KB3800TPW (Windows Smart Touch Wireless Keyboard with Touchpad) (B)RASPBMC supported >> also see Problem USB Keyboards<br />
** KB4950TPW (Wireless Touch II Touchpad Keyboard) (B)<br />
** KB1500U (USB Mini Keyboard) (B)<br />
** KB5150 (2.4&nbsp;GHz wireless keyboard/mouse Combo) (B)<br />
*** Works well with a powered hub<br />
<br />
* '''Generic'''<br />
** [http://www.amazon.co.uk/gp/product/B00A8D9ZPA/ref=oh_details_o06_s00_i00 AK-601] Wireless Mini-keyboard and Trackball. Works well as a handheld device, the wireless dongle does not appear to draw excessive current. However, since its USB charging port requires 5V 300mA it does need to be recharged from a netbook/laptop USB port or via a (spare) USB charger.<br />
<br />
* '''Genius'''<br />
** Ergomedia 700 (GK-04008/C) used without Hub<br />
** KB-06XE (K639) (B)<br />
** LuxeMate i200 (GK-090017; not tested with Hub)<br />
** Slimstar 8000 wireless keyboard<br />
<br />
* '''Gigabyte'''<br />
** GK-KM7580 2.4&nbsp;GHz Wireless Multimedia Keyboard & Mouse<br />
<br />
* '''HP'''<br />
** KG-1061<br />
** KG-0851 Wireless Keyboard and Mouse<br />
** KU-0316 (B)<br />
** LV290AA#ABA Wireless Keyboard and Mouse<br />
** PR1101U (available from Sainsbury's in the UK, £8, July 2012)<br />
** SK-2880<br />
<br />
* '''Hyundai'''<br />
** HY-K201<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Imation''' <br />
** KBD-702 Multi-media Wired Keyboard<br />
*** (works after the firmware update via [https://github.com/Hexxeh/rpi-update rpi-update] as of 06/27/2012)<br />
<br />
* '''IOGEAR'''<br />
** IOGEAR GKM561R Wireless HTPC Multimedia Keyboard with Trackball<br />
** IOGEAR GKM681R 2.4&nbsp;GHz Wireless Compact Keyboard with Optical Trackball and Scroll Wheel<br />
<br />
* '''iPazzPort'''<br />
<br />
* '''i.t.works'''<br />
** KC04 (direct and by USB hub)<br />
** KC Silicone (only tested directly)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''KeySonic'''<br />
** ACK-540RF (Wireless USB keyboard with built-in trackpad); works fine on Debian Squeeze plugged directly into Raspberry Pi. Also works with Raspbmc with powered hub.<br />
** ACK-540RF+ (UK) Wi-Fi keyboard incl. touchpad with USB Wi-Fi dongle works fb with on model B/Raspbian/Wheezy via powered hub<br />
** ACK-3700C<br />
** ACK-340U+(DE)<br />
** ACK-3400U (UK) mini keyboard<br />
** ACK-612RF (GER) Wireless Mini-Keyboard; works fine with its wireless adpater plugged directly into Raspberry Pi<br />
<br />
* '''Labtec'''<br />
** [http://www.labtec.com/index.cfm/gear/details/EUR/EN,crid=28,contentid=692| Ultra-flat Keyboard]<br />
<br />
* '''Laptopmate'''<br />
** AK-98UNTN7-UBRII Laptopmate RII Touch N7 Mini Wireless Keyboard with touchpad<br />
<br />
* '''LC-Power<br />
** K1000BMW (lsusb: ID 1241:f767 Belkin; dmesg: HOLTEK Wireless 2.4&nbsp;GHz Trackball Keyboard) tested with Debian 6.0.4<br />
<br />
* '''Lenovo'''<br />
** SK-8825 UK (B)<br />
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)<br />
** Lenovo Mini Wireless Keyboard N5901 (US)<br />
<br />
* '''Lindy'''<br />
** 21840 (Wireless RF 2.4&nbsp;GHz Micro Keyboard with built-in optical touchpad/trackpad, USB); works fine on model B/Raspbian/Wheezy - the supplied Lindy USB nano dongle transceiver plugged directly into Raspberry Pi USB port.<br />
<br />
* '''Logik'''<br />
** Ultra slim keyboard LKBWSL11 (B) >> '''This is also listed under Problem USB Keyboards?'''<br />
** LK212(R, B, P, V, O at the end represents the colour ) Wireless Keyboard paired with wireless receiver<br />
<br />
* '''Logitech'''<br />
** Comfort Wave 450, labeled 100&nbsp;mA (M/N Y-U0001, P/N 820-001725, PID SC951C40001)<br />
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)<br />
** diNovo Edge Keyboard, Windows edition, built-in TouchDisc track-pad, Bluetooth with USB mini-receiver 967685-0403 (B)<br />
*** older model 867777-0403 may need '''dwc_otg.speed=1''' added to cmdline.txt to avoid dropped/repeated keys and dropped mousepad taps/clicks (B)<br />
**** after Raspbian dist-upgrade about 12/12/12, if '''/lib/udev/rules.d/97-bluetooth-hid2hci.rules''' exists and di Novo Edge fails to respond, edit tail of line after "# Logitech devices" in that file from '''c71['''34'''bc]''' to '''c71[bc]''' to ignore c713 and c714 (do not wordwrap long line), then it works fine<br />
** Wii wireless keyboard KG-0802 (!)<br />
** C-BG17-Dual Wireless keyboard and mouse with wired USB receiver (B)<br />
** Deluxe 250 Keyboard<br />
** Internet 350 (M/N 967740-0403)<br />
** Internet Navigator Keyboard<br />
** MK120 wired keyboard and mouse<br />
** MK220 wireless keyboard and mouse<br />
** MK250 wireless keyboard and mouse (no hub needed)<br />
** MK260 wireless keyboard and mouse (no hub needed)<br />
** MK300 wireless keyboard and mouse<br />
** MK320 wireless keyboard and mouse [http://www.amazon.co.uk/Logitech-920-002885-MK320-Wireless-Desktop/dp/B003STDQYW/ref=sr_1_3?ie=UTF8&qid=1339166178&sr=8-3]<br />
** MK350 wireless keyboard (using Unifying receiver)<br />
** MK520 wireless keyboard and mouse<br />
** MK550 wireless keyboard and mouse (B)<br />
** MX3200 wireless keyboard and mouse (B)<br />
** MX5000 Bluetooth keyboard and mouse (B) The Logitech Bluetooth dongle also does proprietary wireless so it works without Bluetooth drivers.<br />
** EX100 Cordless Desktop, Wireless Keyboard and Mouse (B)<br />
** EX110 Cordless Desktop, wireless keyboard and mouse (B)<br />
** C-SF17 Cordless Desktop Express, Wireless Keyboard and Mouse (B) PS/2 Interface. Tested using [http://www.kurpirkti.lt/imagesi/infodb/org_d69dbd9707af8df77eae6e005f681a9a/BANDRIDGE-USB-2X-PS-2-ADAPTER.jpg PS/2 to USB Banbridge CPA4002 Adapter]<br />
** K120 Keyboard (B)<br />
** K200 Keyboard (B)<br />
** K230 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K260 Wireless Keyboard & Mouse (Unifying receiver, no powered hub) (B)<br />
** K310 Washable Keyboard<br />
** K340 Wireless Keyboard (Unifying receiver, no powered hub) (B)<br />
** K350 Wireless Keyboard (B)<br />
** K400 wireless keyboard with touchpad - also listed under "problematic". Works for weeks with openelec and Raspbian without any problems. Worked out of the box - the on/off switch needs to be "on" for it to function correctly. Highly recommended if you are "working from the sofa". <br />+1 on this, works out of the box with 2012-10-28-wheezy, no powered hub.<br />
** K520 Keyboard (B)<br />
** K700 Wireless Keyboard with Touchpad and unifying receiver<br />
** K750 Wireless Solar Keyboard (B) (Mac version works too. (B) )<br />
** LX 710 - works fine with receiver plugged directly into the Raspberry Pi (accompanying mouse works fine too).<br />
** S510 wireless keyboard and mouse (B)<br />
** Ultra-Flat Keyboard (M/N Y-BP62A P/N 820-000245 PID SY126UK)labelled 100&nbsp;mA. OK direct into Model B Raspberry Pi.<br />
** G19 Gaming Keyboard, works fine with no external power. Illumination with external power. Powered hub in back of keyboard works too.<br />
** G15 Gaming keyboard, as long as you press the backlight button twice to turn off the backlight (it says below it dosen't work with backlight on.<br />
** V470 Bluetooth Laser Mouse<br />
<br />
''Keyboards and mice also together with Unifying receiver'' <br />
<br />
* '''macally'''<br />
**macally iKey slim (IKEY5V2)<br />
<br />
* '''Medion'''<br />
** Medion K28 (by Sysgration) works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
**Microsoft Comfort Curve Keyboard 2000<br />
**Microsoft Comfort Curve Keyboard 3000 for Business<br />
**Microsoft Digital Media Pro Keyboard Model: 1031 (Debian 13-Apr-2012)<br />
**Microsoft Natural Ergonomic Keyboard 4000 (B) (Debian "Wheezy" beta 18-June-2012)<br />
**Microsoft Wired Keyboard 600 Model 1366 (Debian 28-May-2012 on Production Model B)<br />
**Microsoft Wireless Desktop 700 Keyboard v2.0 (Raspbian Pisces image 08-June-2012 on Production Model B)<br />
**Microsoft Wireless Photo Keyboard (Model 1027) Unifying receiver, no hub<br />
**Microsoft Wireless Natural Multimedia Keyboard (Raspbian Pisces 08-July-2012) (B)<br />
**Microsoft Windows 2000 Keyboard (KB-USBK110610)<br />
**[https://www.microsoft.com/hardware/en-us/p/wired-keyboard-600/ANB-00001 Microsoft Wired Keyboard 600]. The keyboard is rated at 5&nbsp;V/100&nbsp;mA (Wheezy 5-Sept-2012)<br />
<br />
* '''Mikomi''' <br />
** Wireless Deskset KM80545 Keyboard and mouse (it works, but the range is terrible less than a metre) (B)<br />
<br />
* '''Monoprice'''<br />
** [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10404&cs_id=1040401&p_id=6854&seq=1&format=2|Monoprice PS/2 To USB Adapter] Directly and through an unpowered hub with a USB mouse plugged in.<br />
<br />
* '''Motorola'''<br />
<br />
** Bluetooth wireless ultra slim keyboard and mouse combo (sold as for the "Atrix" phone) work in combination with the Technika Bluetooth adaptor listed below<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/desktopkits/nov-wcombo.html|Novatech Wireless Combo - Keyboard & Mouse, Nano adapter] (B)<br />
<br />
* '''ONN'''<br />
**ONN Keyboard Stock No: ONA11HO089 (from Walmart). Seems to work fine, even without a hub.<br />
**ONN Keyboard Stock No: ONA11HO087 (from Walmart). Combination keyboard and mouse package with nano receiver. Be sure to configure keyboard layout.<br />
<br />
* '''Ortek'''<br />
** Ortek Technology, Inc. [http://www.ortek.com/html/pdt_view.asp?area=46&cat=150&sn=79 WKB-2000S] Wireless Keyboard with Touchpad works fine on Raspbian Wheezy and Raspbmc. Wireless USB receiver (device ID 05a4:2000) is recognised automatically. Connected directly to Raspberry Pi USB port, no powered hub used.<br />
<br />
* '''Perixx''' <br />
**Periboard 716 Wireless Ultra-Slim Keyboard with Touchpad (Debian 07-Jun-2012 on Production Model B)<br />
***(Raspbian Wheezy, 2012-12-16, Prod. Model B, Rev 2) Has the "sticky key" issue as reported by other users with other keyboards. Seems to be somewhat related to power when directly connected to the Pi. Using a 2A PS makes it MUCH better, but not completely fixed. When/if it happens again, unplugging and reinserting the USB dongle brings it back to normal. Did not try with powered USB hub.<br />
** PERIBOARD-502 wired keyboard inc built in touchpad (model B/Raspbian Wheezy)<br />
** Periduo-707 Plus (Wireless Keyboard and Mouse) works fine ''most'' of the time. Does suffer from dropouts and glitches though. Usual "drawing too much power from USB" problems show up as well - dropped key presses or constant autorepeats. These can be cured by pulling out and reinserting the dongle in the USB socket. The keyboard sometimes hangs after power on when used with my laptop - it seems to need 30 seconds of non-use before it works fine. Again, remove and insert the dongle cures it. Works fine vi my Benq monitor's USB Hub.<br />
<br />
* '''Philips''' <br />
**Wired Multimedia Keyboard SPK3700BC/97 (Debian 19-Apr-2012 on Production Model B)<br />
<br />
* '''Prodige'''<br />
**Nanox Wireless 2.4&nbsp;GHz Keyboard-mouse Combo, also known as [http://www.riitek.com/product_Info.asp?id=56 Riitek RT-MWK01] and [http://www.digicom.it/digisit/prodotti.nsf/itprodottiidx/WKEYPE01 Digicom WKEYPE01]<br />
<br />
* '''Rapoo'''<br />
**Rapoo E9080 Wireless Ultra-Slim Keyboard with Touchpad<br />
**Rapoo Wireless Multi-media Touchpad Keyboard E2700 [http://www.rapoo.com/showdetails.aspx?P_No=E2700]<br />
**Rapoo Ultra-Slim Wireless Multimedia Keyboard and Mouse E9060 (works proper on powered USB Hub)<br />
<br />
*'''Riitek'''<br />
**RT-MWK03 mini wireless keyboard & trackpad<br />
**RT-MWK02+ mini Bluetooth keyboard & trackpad. Followed instructions from this page: [http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/] and it worked, connection persists across reboots, no problem with either builtin USB or powered USB hub.<br />
**RT-MWK01 mini 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]<br />
<br />
*'''Rosewill'''<br />
** RK-200 Standard Keyboard<br />
<br />
*'''Saitek'''<br />
** Eclipse II Backlit Keyboard PK02AU (B)<br />
** Eclipse Backlit Keyboard PZ30AV (B) - works fine when connected directly to Raspberry Pi rev.1 and 2 USB port. No powered hub used.<br />
** Expression Keyboard (US) <br />
** Cyborg V.5 (B)<br />
<br />
*'''SelecLine'''<br />
** WK11P & WM11P-SP-PP. Keyboard and mouse set. (B)<br />
<br />
*'''SIIG'''<br />
** SIIG Wireless Multi-Touchpad Mini Keyboard 02-1286A v1.0 (B)<br />
<br />
*'''Silvercrest'''<br />
** MTS2219 Wireless Keyboard and mouse set. Powered hub NOT used. (B) <br />
<br />
*'''SolidTek'''<br />
** Solid Tek KB-P3100BU ASK-3100U. <br />
<br />
*'''Sony'''<br />
** Keyboard for PlayStation 2 (PS2) Linux. Works without powered hub with 5&nbsp;V 1&nbsp;A supply, requires manual keyboard remapping with Debian Squeeze to USA 101-key layout.<br />
<br />
* '''SteelSeries'''<br />
** Merc keyboard (B)<br />
<br />
* '''Sun Microsystems'''<br />
** Model: Type 7, SUN PN: 320-1348-02 (Danish key layout)<br />
** Model: Type 6, SUN PN: 320-1279-01 (Danish key layout)<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/keyboards/KB060UK/ KB060UK] Wired Multimedia Keyboard<br />
<br />
* '''Technika'''<br />
** WKEY03 (B)<br />
** TKD-211<br />
<br />
* '''Tesco'''<br />
** Value Keyboard VK109 (B)<br />
** Multimedia K211 Wired Keyboard (B)<br />
<br />
*'''The Pi Hut'''<br />
** Super Slim Apple Style Keyboard (from [http://thepihut.com/products/usb-keyboard-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Apple Style Keyboard Set (Keyboard & Mouse) (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Trust [http://trust.com/17585 17585] Wireless Deskset (mouse and keyboard) (17585-02) No hub needed.<br />
** Trust [http://trust.com/17916 17916] Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)<br />
** Trust [http://trust.com/17184 17184] ClassicLine Keyboard <br />
** Trust [http://trust.com/16087 16087] Camiva MultiMedia Keyboard http://trust.com/products/product.aspx?artnr=16087<br />
** Trust [http://trust.com/17603 17603] Convex Keyboard http://trust.com/products/product.aspx?artnr=17603 tested Debian 6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
** Trust [http://trust.com/18007 18007] Tocamy Wireless Entertainment Keyboard. Tested with raspbian and powered USB HUB.<br />
<br />
* '''Unbranded'''<br />
** AK-601 Wireless Mini Keyboard and Trackball (with laser pointer) - sourced from eBay Chinese seller<br />
<br />
* '''Unicomp'''<br />
** USB Endurapro - keyboard and trackpoint work perfectly from powered hub<br />
<br />
* '''Q-Connect'''<br />
** AK-808 (B)<br />
<br />
* '''Xenta'''<br />
** 2.4&nbsp;GHz Wireless Multimedia Entertainment Keyboard with Touchpad (B)<br />
** Mini Multimedia Keyboard (Model no.: 808M) (B)<br />
<br />
===Problem USB Keyboards===<br />
<br />
Note that generally PS/2 keyboards with an USB adapter will not work directly on a Raspberry Pi port, due to the fact that PS/2 keyboards are designed for normal 5&nbsp;V +-5% range, while USB keyboards must be designed to work with 4.4 Volt, and generally USB devices on the Raspberry Pi may receive less than 4.75 Volt. PS/2 + USB adapter keyboards might work behind a powered hub, which does provide the full 5.0&nbsp;V. Some of these keyboards work when running the latest Raspbian, but not when using the overclocked XBMC version of Raspbmc, probably due to the overclocking drawing more power away from the rest of the support system devices.<br />
<br />
* '''A4 Tech'''<br />
** Model GL-6 USB Keyboard, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''Accuratus'''<br />
** Accuratus KYBAC100-101USBBLK causes kernel panic (rated 100&nbsp;mA). Tested with 1000&nbsp;mA cheap unbranded and Nokia 1200&nbsp;mA power adaptors.<br />
* '''Apple'''<br />
** [http://www.powerbookmedic.com/xcart1/images/D/apple-keyboard.jpg Apple Keyboard (109 keys) A1048]. Draws too much power and does not seem to work properly when plugged into a powered hub. <br />
*'''Argos'''<br />
** Argos Value Wired Keyboard causes kernel panic<br />
* '''Choidy'''<br />
** Identifiers from usb-devices: Vendor=1a2c ProdID=0002 Rev=01.10 Product=USB Keykoard (yes, 'Keykoard') causes kernel panic<br />
* '''Cit''' <br />
** KB-1807UB Causes kernel panic (rated <200&nbsp;mA)<br />
* '''Dell'''<br />
** SK-8135 (B) (Rated 1.5&nbsp;A. Takes too much power from Raspberry Pi even when not used as USB hub. Symptom = repeated keystrokes)<br />
** SK-8115 causes kernel panic (rated 100&nbsp;mA) Debian 6-19-04-2012 (B)<br />
** Y-U0003-DEL5 Sticky / Non-responsive keys<br />
** Wireless Trackball Keyboard with trackball - problem sticky keys definitely not power issue as the dongle works even at 3V<br />
* '''Gear Head'''<br />
** KB2300U - Causes kernel panic (B)<br />
** KB3800TPW - Wireless Touch Touchpad Keyboard - Wireless dongle disrupts USB and ethernet whether direct or on powered hub, no keyboard/mousepad response in Raspbian (logged in syslog) or Raspbmc (no logs written)(B)<br />
* '''GMYLE'''<br />
** Wired USB Slim Chocolate Multimedia Media Typing Keyboard With 3 USB Port hub (B) - Kernel Panic on startup if plugged in. If plugged in at login prompt then freeze. [http://www.amazon.co.uk/gp/product/B0067EC3GW/]<br />
* '''Inland''' <br />
** Inland USB Keyboard Model #70010<br />
* '''Jeway'''<br />
** JK-8170 "The Hunter" - causes kernel oops (Debian6-19-04-2012) (B)<br />
* '''Labtec'''<br />
** ultra-flat wireless desktop USB - Keyboard has 'sticky' keys. Tested both debian6-19-04-2012 and archlinuxarm-13-06-2012 (B)<br />
* '''Logik'''<br />
** Wired Multimedia Keyboard Model: LKBWMM11 - causes kernel panic (on Debian 190412 distro) (B)<br />
** Wired Ultra Slim Keyboard Model: LKBWSL11 - causes USB power issues. Not reliable. Causes other USB devices to fail (B) >> '''This is also listed under Working USB Keyboards??'''<br />
* '''Logitech'''<br />
** Logitech Illuminated Keyboard (unstable; not working with led light on; tested both US and NO layouts with both Apple iPad 2 and Asus TF-101 USB chargers)<br />
** G110 Gaming Keyboard - only works with illumination off, otherwise unresponsive. Once failed it needs reconnecting before another attempt. (B)<br />
** G15 Gaming Keyboard - LCD and key backlights flicker, 95% unresponsive to typing. I don't know of a way to turn the illumination off. (B)<br />
** K360 Wireless Keyboard - Occasional sticky keys. (B)<br />
** MK 260 Wireless Keyboard - Occasional sticky keys. (B)<br />
** K400 wireless keyboard with touchpad (completely non-functional on debian6-19-04-2012)<br />
** G510 Gaming Keyboard - lagging or unresponsive keys.<br />
** MX5500 wireless keyboard and mouse with USB Bluetooth receiver - Unstable, looses connection without prior notice<br />
** EX100 Cordless Desktop, wireless keyboard and mouse. Mouse and keyboard hangs every few minutes (with or without hub).<br />
* '''Microsoft''' <br />
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Entertainment Keyboard - No key input recognized (possibly connectivity issue as pairing devices does not seem to work)<br />
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)<br />
** Wireless Keyboard 2000 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Desktop 3000 - Keyboard has 'sticky' keys.<br />
** Arc wireless - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X4 - Keyboard has 'sticky' keys. (B)<br />
** Sidewinder X6 - Keyboard has 'sticky' keys. (B)<br />
** Wireless Comfort Keyboard 5000 - Keyboard has 'sticky' keys. (B)<br />
** Razer Reclusa - Keyboard has 'sticky' keys. (B rev 2.0)<br />
** Wired Keyboard 600 Model 1366 (B) (no power to keyboard, RPi powered by a 1000&nbsp;mA power supply unit)<br />
* '''Novatech'''<br />
** NOV-KEY2 - Causes kernel panic (B)<br />
* '''PC World Essentials'''<br />
** PKBW11 Wired Keyboard - no power to keyboard, no error messages on both Arch 29-04-2012 and Debian6-19-04-2012, the same Raspberry Pi works with Asda keyboard. Me too, but it caused a kernel panic -- tested on powered hub and direct.<br />
* '''Razer'''<br />
** Razer Tarantula gaming keyboard - sticky keys, could be power issue as is programmable with host powered USB hub and audio jacks.<br />
** Razer BlackWidow - Sticky keys, could be a power related issue due to illuminated logo (Blue LED).<br />
** Razer Arctosa - Sticky keys, most probably power related issue since it states it's rated at 5&nbsp;V 500&nbsp;mA. (B)<br />
* '''SIIG'''<br />
** Wireless Ultra Slim Multimedia Mini Keyboard JK-WR0612-S1 - Unresponsive and sticky keys.<br />
* '''Texet'''<br />
** MB-768B standard keyboard (Rated 5&nbsp;V 1.5&nbsp;A (!), so probably too much power drain. Kernel panic, Debian6-19-04-2012)<br />
* '''Trust''' <br />
** TRUST GXT 18 Gaming Keyboard - No power to keyboard, could be a driver issue - no error messages.<br />
* '''Unbranded'''<br />
** Compuparts<br />
** model no. HK-6106 (B)<br />
** LK-890 (Multimedia keyboard & Optical Mouse) - kernel panic on Debian Squeeze, ArchLinux and Qtonpi.<br />
* '''Verbatim'''<br />
** [http://www.amazon.com/gp/product/B004LB5AKY/ref=oh_details_o00_s00_i02|Verbatim 97472 Mini Wireless Slim Keyboard and Mouse] - Keyboard has lagging, unresponsive and sticky keys issues. (Tested with and without powered USB hub.)<br />
* '''Wilkinsons / TEXET'''<br />
** Model MB-768B causes kernel panic on debian6-19-04-2012.<br />
* '''Xenta'''<br />
** HK-6106 - causes kernel panic (on Debian 190412 distro)(B)<br />
** Multimedia Wireless Keyboard and Mouse Set (Keyboard Model: HK3518B + Mouse Model HM3301) (B) - occasional sticky keys, and occasional complete lock-up<br />
<br />
== USB Mouse devices ==<br />
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems. <br />
<br />
===Working USB Mouse Devices===<br />
The following is a list of specific mouse devices known to work and which appear to be fault-free.<br />
<br />
* '''A4Tech'''<br />
** OP-530NU Padless Wired Mouse<br />
<br />
* '''Apple'''<br />
** Apple Mighty Mouse (Model No. A1152): Works well with the exception of the scroll ball only transmitting vertical scrolling (This seems to be an issue of driver that was designed to support scroll wheels).<br />
<br />
* '''Asda'''<br />
** HM5058 (Smart Price) Wired Mouse<br />
** Traveler 8000, 5-button wireless wheelmouse (reported by ''lsusb'' as a <code> ID 0458:00e7 KYE Systems Corp. (Mouse Systems) </code> mouse)<br />
** Wireless Multimedia Deskset (keyboard, mouse and USB dongle) Model: HKM8016B (Note: Shown on Asda Website as HK8016B) (B)<br />
<br />
* '''ASUS'''<br />
** MS-511U (comes with Asus Vento KM-63 keyboard/mouse combo) (B)<br />
** MG-0919 (wireless)<br />
<br />
* '''Belkin'''<br />
** F8E882-OPT (B)<br />
<br />
* '''Cellink'''<br />
** OPM-602 Small wireless optical mouse<br />
<br />
* '''Cerulian Technology'''<br />
** 3 Button Mini Mobile Blue Trace Mice - Model:N96JA<br />
<br />
* '''Dell'''<br />
** M-UVDEL1 (B)<br />
** MOC5UO (100&nbsp;mA)<br />
** M056U0A (B)<br />
** DZL-MS111-L (B) (100&nbsp;mA)<br />
** MS-111P (100&nbsp;mA)<br />
** Bluetooth Wireless Keyboard and Mouse Bundle (B), Bluetooth USB dongle C-UV35 (Rated 500&nbsp;mA, but it works great), Keyboard Y-RAQ-DEL2, Mouse M-RBB-DEL4<br />
** 8K89 I.T.E. Wireless Mouse/Receiver (Associated keyboard model RT7D40) - reported by ''lsusb'' as <code> ID 046d:c509 Logitech, Inc. Cordless Keyboard & Mouse </code>. A little sluggish but this is an old, well-used device from a Dell desktop package circa 2005! Keyboard appears to work O.K.<br />
<br />
* '''Dynex'''<br />
** DX-WMSE (100&nbsp;mA) (B)<br />
<br />
* '''Fellowes'''<br />
** 99928 USB Micro Track Ball (works without a hub, directly plugged in) (B)<br />
<br />
* '''Filand'''<br />
** OP-102i Mini Optical Mouse<br />
<br />
* '''Genius'''<br />
** GM-04003A (B)<br />
** Slimstar 8000 wireless mouse (Can be intermitent. Mouse pointer sometimes is irratic.)<br />
** Traveler 515 Laser<br />
<br />
* '''HP'''<br />
** MN-UAE96 (The basic stock HP wired mouse)(B)<br />
<br />
* '''iConcepts'''<br />
** 2.4&nbsp;GHz Wireless Keyboard and Optical Mouse Model 62550<br />
*** (saves a USB port since keyboard and mouse share one transceiver, $14.99 at Fry's Electronics)<br />
<br />
* '''Jenkins'''<br />
** Jenkins Wireless Desktop Set Blue (B)<br />
<br />
* '''Kensington'''<br />
** Kensington Expert Mouse Trackball K64325<br />
** Kensington Expert Mouse "Slimblade" K72327US<br />
<br />
* '''Labtec'''<br />
** Corded Laser Glow Mouse 1600, rated 5&nbsp;V 100&nbsp;mA (P/N 810-000819, M/N M-UAZ149, PID GT83401)<br />
<br />
* '''Lenovo'''<br />
** Wired Optical Mouse Model: MO28UOL<br />
<br />
* '''Logik'''<br />
** Wired Optical Glow Mouse Model: LGGMO10. (B)<br />
<br />
* '''Logitech'''<br />
** Anywhere MX Wireless Mouse - works fine with same unifying receiver as K400 keyboard/mousepad (quake3 is easier w/mouse than mousepad)<br />
** B105 Mouse for Laptops (OEM)<br />
** Cordless Pilot Optical Mouse M/N M-RR95 with Cordless Mouse Receiver M/N C-BA4-MSE<br />
** G5 Logitech Gaming Mouse (B)<br />
** G5v2 Logitech Gaming Mouse (B)<br />
** G500 Logitech Gaming Mouse (B)<br />
** G700 Logitech Wireless Gaming Mouse (B)<br />
** LX-700 Cordless Desktop Receiver (B)<br />
** LX 710 Wireless Mouse - works fine with receiver plugged directly into Raspberry Pi (accompanying keyboard works fine too).<br />
** M90 optical mouse<br />
** M185 Wireless Mouse (B)<br />
** M210 (part of the MK260 set) (B)<br />
** M305 Wireless Mouse<br />
** M310 Cordless Mouse<br />
** M325 Wireless Mouse<br />
** M505 USB wireless laser, model no: 910-001324 (B)<br />
** M510 Wireless Mouse (B)<br />
** M705 Marathon Mouse (Unifying receiver, no powered hub) (B)<br />
** M-BD58 Wheel Mouse (B)<br />
** M-BJ58/M-BJ69 Optical Wheel Mouse (B)<br />
** M-BJ79 (B)<br />
** M-BT96a Optical Mouse<br />
** MX320/MX400 laser mouse (B)<br />
** MX518 Optical wheel mouse (B)<br />
** Optical USB Mouse (M/N 931643-0403)<br />
** Performance Mouse MX (B)<br />
** MX Revolution (B) (Debian "Wheezy" beta 18-June-2012)<br />
** VX Nano Cordless Laser Mouse for Notebooks<br />
** Wheel Mouse (M/N BJ58)<br />
<br />
* '''Medion'''<br />
** Mini mouse Model M101-CBJ P/N 40016632 S/N 7BFSA00003445 rated 5&nbsp;V 100&nbsp;mA. Works fb on model B with Raspbian Wheezy<br />
** Medion AGM-946 (by Sysgration) USB optical mouse works, but not with dwc_otg.speed=1<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=292149#p292149</ref><br />
<br />
* '''Microsoft''' <br />
** Comfort Curve Mouse 3000 for Business<br />
** Comfort Mouse 6000 (works when directly connected to Raspberry Pi (B). Does not work when connected through USB Hub (mouse pointer intermittent).<br />
** Compact optical mouse 500 V2.0 (B)<br />
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)<br />
** Microsoft Intellimouse Optical Mouse<br />
** Microsoft Wireless Laser Mouse 8000<br />
** Microsoft Wireless Mobile Mouse 1000<br />
** Microsoft Wireless Mobile Mouse 3500<br />
** Microsoft Wireless Mobile Mouse 4000<br />
** Microsoft Wireless Mouse 700 v2.0<br />
** Microsoft Comfort Mouse 4500<br />
** Wireless IntelliMouse Explorer 2.0 (unifying receiver, no hub)<br />
<br />
* '''Novatech'''<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-mouser.html|Novatech M1 USB Mouse - Wired](B)<br />
** [http://www.novatech.co.uk/products/peripherals/miceandtrackballs/nov-dl10.html|Novatech DL10 Wireless Mouse] (B)<br />
<br />
* '''Perixx'''<br />
** PERIMICE-210 U Red (Part No.R1J) <br />
<br />
* '''Razer'''<br />
** Boomslang Collectors Edition 2007 (B)<br />
<br />
* '''Rosewill'''<br />
** Rosewill RM-C2U<br />
<br />
* '''Saitek'''<br />
** Notebook Optical Mouse (PM46)<br />
<br />
* '''Samsung'''<br />
** Samsung model:AA-SM3PCPB USB Optical Mouse (draws 50&nbsp;mA) <br />
<br />
* '''Sun microsystems'''<br />
** Model: FID-638 , SunPN: 371-0788-01<br />
<br />
* '''Sweex'''<br />
** [http://www.sweex.com/en/assortiment/input/optical-mice/MI015/ MI015]<br />
<br />
* '''Swiftpoint'''<br />
** [http://http://www.americas.futuremouse.com/] Swiftpoint Mini Wireless Optical Mouse. Does not require any special drivers. Haven't confirmed if charging the mouse requires a powered USB hub or not.<br />
<br />
* '''Targus'''<br />
** AKM02UK (Associated keyboard not checked)<br />
** AMU2701EUK (B)<br />
<br />
* '''Technika'''<br />
** TKOPTM2 (B)<br />
**TKD-211<br />
**TKNM110<br />
<br />
* '''Tesco'''<br />
** Wired optical mouse M211 (B)<br />
<br />
*'''The Pi Hut'''<br />
** USB Mouse for Raspberry Pi (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
** Super Slim Keyboard & Mouse Set (from [http://thepihut.com/products/usb-keyboard-mouse-bundle-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Trust'''<br />
** Model 15313 - large, 5-button wireless mouse<br />
** Model 15349 - small, wireless notebook mouse - wireless dongle turns mouse off when "parked" in its base<br />
** Model 16591-04 - large, wired 3-button wheelmouse (reported by ''lsusb'' as a <code> ID 192f:0916 Avago Technologies, Pte.</code> mouse)<br />
** Trust Nanou Wireless Micro Mouse http://trust.com/products/product.aspx?artnr=17087<br />
** Fachi, tech air, and a generic "Car" Mouse. All three are wired mice, and reported by ''lsusb'' as <code> ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse</code> devices.<br />
<br />
* '''Verbatiam'''<br />
**Mini Nano Optical Mouse 97470 (wireless on non-powered three USB dongle hub) (B)<br />
<br />
* '''Xenta'''<br />
** MOW0810 (B)<br />
** Wired Optical Mouse (from [http://thepihut.com/products/usb-mouse-for-the-raspberry-pi The Pi Hut's Raspberry Pi Store])<br />
<br />
* '''Generic'''<br />
** Generic 2.4&nbsp;GHz Wireless Mouse (ID 040b:2013 Weltrend Semiconductor) (B)<br />
<br />
===Problem USB Mouse Devices===<br />
The following is a list of specific mouse devices that have problems working with the Raspberry Pi<br />
* '''A4Tech'''<br />
** Model G7-630 Wireless Mouse, 20&nbsp;mA. Part of wireless keyboard/mouse bundle GL-6630 (GL-6 + G7-630 + RN-10B) - suffers from USB flakeyness. Even on a powered hub. No problems on other computers I have tested it with.<br />
* '''HP'''<br />
** HP Retractable Mobile Mouse (Optical) HP Product Number XP472AA - errors / boot loop RASPBMC (B)removed mouse, started with no further errors. <br />
<br />
* '''Logik'''<br />
** Logik IMF Blue Trace Wired USB mouse (Model LMWBLU11) - disconnects from the USB port every 20 seconds when using the Raspian distro. Always reconnects to the USB port successfully (B)<br />
<br />
* '''Logitech'''<br />
** Logitech G400 Gaming Mouse - 100% CPU load and laggy mouse cursor when the mouse is moved. MX518 works fine on the same setup, so I suspect it's a polling rate issue. [http://tech2.in.com/reviews/mice/logitech-g400-is-it-a-worthy-successor/231012 this] says the mouse is 1000&nbsp;Hz out of the box, whereas the 518 is only 125&nbsp;Hz. Solution found: add usbhid.mousepoll=8 to the kernel commandline.<br />
** Logitech G5 is working, high CPU Load, solution add: usbhid.mousepoll=8 to kernel cmdline.txt in /boot<br />
<br />
* '''Microsoft'''<br />
** Microsoft Touch Mouse - Does not see right clicks, Only left.<br />
** Microsoft Sidewinder X8 - Uses far too much power, if it works then only for a short time!.<br />
<br />
* '''Razer'''<br />
** Naga Wired USB mouse - the mouse seems to present itself as a keyboard because the numpad on the left-hand side of the device works, but the cursor doesn't move.<br />
** Mamba (wired) and Imperator - slow and unreliable reaction to mouse clicks, loosing focus<br />
<br />
* '''Roccat'''<br />
** Kone[+] Wired USB mouse - Nothing happens when moving the mouse, haven't looked further into the issue (B)<br />
<br />
* '''Trust'''<br />
** Optical USB Mouse MI-2250 - Nothing happens when moving the mouse (B)<br />
<br />
* '''Xenta'''<br />
** Multimedia Wireless Keyboard and Mouse Set (Mouse Model: HM-3301) (B) - frequent lost connection giving stuttering mouse cursor indicating USB current not enough for dongle<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 />
== USB Wi-Fi Adapters ==<br />
<br />
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. Therefore, you may need to plug the Wi-Fi adapter into a powered USB hub.<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.<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 />
* '''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. <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.<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 />
<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 />
* '''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 Raspian Wheezy (2012-09-18) and Raspbmc (2012-11-06) using Network-Manager addon (see Program - Addons)<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-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. Important : revision A1 works, revision B1 does not. Works out of the box on Raspbian “Wheezy”. Verified with direct USB: no powered USB hub needed. Also verified when Nano used in powered USB hub. Someone had trouble configuring SSID/Passphrase in etc/network/interfaces file. But no problem & very easy to configure using wicd: wicd is a gui interface on LXDE for network configuration. Install it using command-line: <code>apt-get install wicd</code>. Once configured ith wicd to auto-run on boot, no need to turn back to LXDE. Recommended.<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-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.<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 />
*** 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 />
(B)<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 />
<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 />
<br />
* '''Lutec'''<br />
** Lutec WLA-54L (old version with ZD1211b chipset) is working even USB powered.<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 />
<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 />
<br />
* '''OvisLink'''<br />
** Evo-W300USB: USB ID 148f:2270 Ralink Technology RT2770. apt-get install firmware-ralink<br />
<br />
* '''Patriot Memory'''<br />
** [http://patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=1198&type=20 PCUSBW1150] Wireless 11N USB adapter (uses Realtek RTL8188CUS) Install using Micronet script. Works only through powered USB hub.<br />
** [http://www.patriotmemory.com/products/detailp.jsp?prodline=6&catid=69&prodgroupid=163&id=973&type=20 PCBOWAU2-N] Wireless 11N USB adapter (uses Realtek RTL8191SU chip) Installed using r8712u Kernel module<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 supports Access Point and it be used for hostapd <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)<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: 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 />
* '''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]<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 (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-WN725N Works out of the box on Raspbian 2012-12-16 without a powered USB hub. This adapter is based on the Realtek RTL8188CUS chipset.<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-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 />
<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 />
** [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)<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 />
* '''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 />
** TL-WDN3200 USB ID: 148f:5572, no native driver available under Raspbian, OpenELEC, raspbmc (neither under x86 Linux) for the ralink 5572 chipset. Might work if driver is compiled from [http://www.ralinktech.com/en/04_support/support.php?sn=501 source].<br />
<br />
== USB Bluetooth adapters ==<br />
===Working Bluetooth adapters===<br />
* Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote<br />
** Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.<br />
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)<br />
** Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)<br />
** Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.<br />
** Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.<br />
** Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288<br />
** RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.<br />
** ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.<br />
** Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian<br />
** Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian<br />
* D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip<br />
** http://www.element14.com/community/message/58288<br />
* IOGear GBU321 (Broadcom BCM2045 Chipset)<br />
** Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.<br />
* Trust BT-2400p<br />
** Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).<br />
<br />
===Working Bluetooth/Wifi Combo adapters===<br />
* PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=27678</ref><br />
* Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)<ref>http://www.lindy.co.uk/shop/showProductDetail.do?orderNumber=52213</ref><br />
<br />
===Problem Bluetooth adapters===<br />
* '''Belkin'''<br />
** Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.<br />
* '''Generic'''<br />
** [http://dx.com/p/mini-bluetooth-v3-0-usb-2-0-dongle-71248 Bluetooth "3.0" Dongle]. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.<br />
** [http://dx.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866 Super Mini Bluetooth 2.0 Dongle]. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.<br />
* Asus USB-BT211<br />
** Shows up as HCI device in Raspbian, but it does not scan or pair.<br />
** http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9962<br />
<br />
== USB Ethernet adapters ==<br />
===Working Ethernet adapters===<br />
* '''AVM'''<br />
** FRITZ!Box WLAN 3030 USB Ethernet Adapter: Works out of the box. No external power source needed.<br />
* '''Wintech'''<br />
** USB 2.0 LanCard Model: LAU-15 (CK0049C) using the mcs7830 driver. Probably needs more than 100&nbsp;mA current. [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=46&t=8708#p106136]<br />
* '''LogiLink'''<br />
** USB 2.0 UA0144: AX88772 chipset using the asix kernel driver. Tested only on powered USB hub so far.<br />
** LogiLink Fast EN USB 2.0 to RJ45 Adapter: Test on Wheezy-Raspian (2012-08-16) without USB Hub will be confirmed<br />
lsusb output: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter <br />
* '''Apple'''<br />
** Apple USB Ethernet Adapter using asix kernel driver. Works out of the box on Raspbian, haven't tested on any other OS.<br />
* '''Edimax'''<br />
** Edimax EU-4230 USB2.0 Fast Ethernet Adapter with 3 port USB hub. Works out of the box. Needs its own power source.<br />
* '''D-Link'''<br />
** D-Link DUB-E100 Fast Ethernet USB 2.0 Adapter - works out of the box, requires own power supply (from powered USB hub)<br />
* '''LinkSys'''<br />
** Linksys - USB200M - Compact USB 2.0 10/100 Network Adapter - raspian recognized it automatically and so far I have only pinged a few addresses with and it worked. I had it plugged into a powered hub so I cannot say if it works connected directly to the pi.<br />
* '''Sabrent'''<br />
** Sabrent USB 2.0 10/100 Ethernet Adapter - works out of the box (asix), but USB 2.0 '''only''' (does not work if using dwc_otg.speed=1 in cmdline.txt to force USB 1.1 for other problem hardware)<br />
* '''Sitecom'''<br />
** Sitecom LN-030 V2 detected as ASIX AX88772 USB 2.0 Ethernet Adapter works out of the box. Doesn't seem to require any extra power supply.<br />
* '''A-Link'''<br />
** A-Link NA1GU Gigabit USB 2.0 Ethernet adapter<br />
This adapter works, but it (probably) requires a bit of work. The driver for the chipset (Asix AX88178) included with the Raspbian kernel (v 3.1.9+ Aug 7 2012) does '''not''' work. With that driver the device is detected, but it does not seem to be possible to actually put any traffic through it. :-( In order to make it work you need to download the latest driver from [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 the chipset manufacturer]. The version I used was "Linux kernel 3.x/2.6.x Driver" v4.4.0, released 2012-05-18. Fortunately this is GNU GPLv2 -licenced source code and not a binary blob, so compiling it for the Raspberry Pi is perfectly doable. The hardest part was in fact getting the Linux source code required, because the repositores contained the source for the wrong kernel version. >:-( Fortunately there is [https://www.grendelman.net/wp/compiling-kernel-modules-for-raspbian-raspberry-pi a very useful guide] for how to get the sources from github, and preparing that source so that you can compile modules. Unfortunately you will have to compile the kernel (even if you don't actually install it) - which will take the better part of the day on the Raspberry, but once that's done you can unpack the driver source and just run "make && sudo make install". Reboot and you should have a fully working Ethernet adapter.<br />
<br />
The adapter seems to work without a powered USB hub, but according to the specifications it can draw up to 190&nbsp;mA, so there might be stability issues if additional power is not provided.<br />
* '''Hama'''<br />
** Hama 00049244 Fast Ethernet USB 2.0-Adapter detected as MOSCHIP 7830/7832/7730 usb-NET adapter. Works out of the box on Debian Wheezy/sid (2012-08-08-wheezy-armel)(not tested yet on other OS). No external power source or USB hub needed.<br />
* '''Newlink'''<br />
** Newlink NLUSB2-ETH USB 2.0 Ethernet Adapter. Works out of the box on Raspbian. Detected as ASIX AX88772. Works without a powereed hub.<br />
<br />
===Problem Ethernet adapters===<br />
* Axago<br />
** Axago ADE-X1 10/100 Ethernet Adapter (USB: 9710:7830 driver:mcs7830). Adapter working about 10 minutes without problem, but after that kernel write error message to dmesg and no packet is received. Needed to unplug and plug USB again. Tested with and without powered USB hub. dmesg error: NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out<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 />
* '''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://www.ti.com/product/pcm2704 PCM2704 98&nbsp;dB SNR Stereo USB2.0 FS DAC with line-out and S/PDIF output, Bus/Self-powered]<br />
<br />
Databases of sound cards that are known to work with Linux:<br />
* http://wiki.linuxaudio.org/wiki/current_audio_gear<br />
* http://wiki.linuxmusicians.com/doku.php?id=hardware_matrix<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 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 when in doubt or 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 />
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 />
==USB 3G Dongles==<br />
* Huawei E1750<br />
* Huawei E173<br />
* Huawei E220<br />
* Huawei E160 (AT commands only)<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 />
<br />
== USB IR Receivers==<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, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD & SD.<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)<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 />
*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 Webcams ==<br />
<br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
| PD1030<br />
|<br />
| <br />
| <br />
|<br />
| ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|WebcamHD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| Works fine without external power.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C270<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| With external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, she is uncvideo and detected out of box as Video0 V4L device. 1600x1200 is slow rate but he tested with motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| With powered hub, detected out of box as Video0 V4L device<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other usb port.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Picture breaks up at the bottom<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
| <br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Up to 352x288. Higher resolutions do not work. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|Xbox Live Vision<br />
| <br />
| 045e:0294<br />
| Arch Linux <br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #A4B2CF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| The occasional frame is corrupted/stutters when running at 640x480<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| works out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
<br />
|-<br />
|}<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. That uses a Profilic pl2303-chip so you'll need to compile the module or the kernel manually<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 />
<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 />
== 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 />
<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'' and ''gtkterm''<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 />
<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 />
== 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 />
=== Numpads ===<br />
*'''Conceptronic / Holtek'''<br />
**USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub<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 SATA ===<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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== 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 />
=== USB 3.0 Multi-Card Reader ===<br />
* US Robotics 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 />
=== 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 (Lazerus), 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 />
== 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 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 adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.<br />
<br />
===Working power Adapters===<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 />
** 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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''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 />
* '''The Pi Hut'''<br />
** Micro USB Power Supply for the Raspberry Pi. 5&nbsp;V 1000&nbsp;mA (from [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store]) (also from [http://www.ebay.co.uk/itm/330844162509 eBay ])<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 />
* '''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 />
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 />
Most will require use [[RPi_config.txt]]. Start off with hdmi_safe=1.<br />
<br />
At under ten pound [currently listed at £29.80, there are white ones for £11 linked down the page but it's not clear if these are identical] this one [http://www.amazon.co.uk/gp/product/B0088K7QUQ/ref=s9_simh_gw_p147_d0_i1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-3&pf_rd_r=1Y006WNZC47TTNRJFH1D&pf_rd_t=101&pf_rd_p=317828027&pf_rd_i=468294] is one of the cheapest, but perhaps due to a more advanced design is seems power frugal enough to most often work well with a PI, it has many comments saying it works well with the PI, and gives tips on how to edit config.txt.<br />
<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 />
http://www.amazon.co.uk/gp/product/B007KEIRNG -- "Neewer" HDMI to VGA -- some issues discussed below:<br />
However, according to user "Tom1989" the same Neewer HDMI to VGA adapter burned out BAT54 Schottky diode D1 on the Raspberry Pi and broke its HDMI output: [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9819 Serious HDMI Problems. What's that smell? Burning Raspberry!]. On that thread, "mahjongg" suggested the NXP (or equivalent) PMEG2010AET as a high-current replacement for D1. The PMEG2010AET has 1&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 "Burning Raspberry!" 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 />
<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 />
http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- "Kanaan" HDMI-VGA<br />
<br />
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=130699741793 -- eBay is swarming with $16 converters all like this one.<br />
<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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=4<br />
<br>config_hdmi_boost=4<br />
<br>overscan_top=-30<br />
<br>overscan_bottom=-30<br />
<br>overscan_left=-30<br />
<br>overscan_right=-30<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 />
According to user "Mortimer" -- HDFuryPro HDMI to YPbBr/VGA Converter found on Amazon -- http://www.amazon.co.uk/Inputs-Component-Video-YPbPr-Converter/dp/B00797ZZ4S/ -- Works with Raspberry Pi. Tested against a Philips 170B 1280x1024 LCD monitor, producing a full native resolution image. Not tested against a Component Video TV yet, and audio has yet to be got working.<br />
The [[RPi_config.txt|config.txt]] settings used are:<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
<br />
According to user "Mortimer" -- HDFury1 1080p HDMI to VGA Converter from HDFury.com. I'm not sure the HDFury1 can be got a hold of easily nowadays, I happened to have access to one to try out. HDFury2, 3 and 4 are available as far as I can tell, but it is very pricey compared to the alternatives. HDFury1 was around £80 when we bought one for a project at work. HDFury2 seems to be around £130, 3 and 4 are getting on towards £200 or more. So not to be recommended as a solution unless you happen to have one lying around. I don't believe there is any relationship between the company that produces these and the HDFuryPro I bought for myself (See above). I didn't alter any config settings, just plugged it in. It doesn't work without having its external power supply connected, as it requires 0.4&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 />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=36<br />
<br>disable_overscan=1<br />
<br />
http://www.amazon.co.uk/gp/product/B007SM7O2U/ref=oh_details_o02_s00_i00 - "Cable Matters"<br />
<br />
Here It is another option: http://www.dealextreme.com/p/hdmi-v1-4-male-to-vga-female-converter-adapter-cable-white-15cm-130458, is cheap (it's free shipping from china) and works perfectly, I tested it with an Acer VGA monitor (AL1511), without no change in my XBMC distribution.<br />
The config.txt for Raspbian (Flatron VGA monitor 1024 * 768):<br />
<br>hdmi_drive=2<br />
<br>hdmi_group=2<br />
<br>hdmi_mode=16<br />
<br>hdmi_force_hotplug=1<br />
<br>disable_overscan=0<br />
<br />
<br />
And another one: http://cgi.ebay.pl/ws/eBayISAPI.dll?ViewItem&item=251086464644. It is very cheap, but it works perfectly. No config.txt changes was needed at all. I've booted Raspbian and OpenELEC. Monitor is detected correctly and the optimal resolution is set (Raspbian) or you can change the res in the menu (OpenELEC). <br />
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.<br />
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 />
Marcin.<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 />
== 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>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215540Raspberry Pi Kernel Compilation2013-01-31T20:47:31Z<p>AutoStatic: /* Transfer the build */</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, set an environment variable <tt>CCPREFIX</tt> that points to the prefix of your compiler binary as each compiler will be named slightly differently.<br />
<pre><br />
export CCPREFIX=/path/to/your/compiler/binary/prefix-of-binary-<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=${CCPREFIX}</tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX}<br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215450Raspberry Pi Kernel Compilation2013-01-31T13:36:33Z<p>AutoStatic: /* Perform the compilation */</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, set an environment variable <tt>CCPREFIX</tt> that points to the prefix of your compiler binary as each compiler will be named slightly differently.<br />
<pre><br />
export CCPREFIX=/path/to/your/compiler/binary/prefix-of-binary-<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=${CCPREFIX}</tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX}<br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215444Raspberry Pi Kernel Compilation2013-01-31T13:33:16Z<p>AutoStatic: /* Perform the compilation */</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, set an environment variable CCPREFIX that points to the prefix of your compiler binary as each compiler will be named slightly differently.<br />
<pre><br />
export CCPREFIX=/path/to/your/compiler/binary/prefix-of-binary-<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=${CCPREFIX}</tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX}<br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215438Raspberry Pi Kernel Compilation2013-01-31T13:28:52Z<p>AutoStatic: /* Perform the compilation */</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, please substitute <tt><your_compiler></tt> with your compiler binary prefix (e.g. <tt>/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-</tt>) as each compiler will be named slightly differently. Even better would be to export this prefix because you will need it later:<br />
<pre><br />
export CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=<your_compiler></tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX} menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=${CCPREFIX}<br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215432Raspberry Pi Kernel Compilation2013-01-31T13:26:14Z<p>AutoStatic: /* Perform the compilation */</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, please substitute <tt><your_compiler></tt> with your compiler binary prefix (e.g. <tt>/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-</tt>) as each compiler will be named slightly differently. You can also export this prefix because you will need it later:<br />
<pre><br />
export CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=<your_compiler></tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler><br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215426Raspberry Pi Kernel Compilation2013-01-31T13:15:23Z<p>AutoStatic: Added info about PATH variable.</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, please substitute <tt><your_compiler></tt> with your compiler binary prefix (e.g. <tt>arm-bcm2708hardfp-linux-gnueabi-</tt>) as each compiler will be named slightly differently. Also make sure that the path to your compiler binary can be found:<br />
<pre><br />
export PATH=/path/to/your/compiler/binary:${PATH}<br />
</pre><br />
<br />
If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=<your_compiler></tt> from each command and do not export any additional PATH values.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler><br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatichttps://elinux.org/index.php?title=Raspberry_Pi_Kernel_Compilation&diff=215420Raspberry Pi Kernel Compilation2013-01-31T13:10:39Z<p>AutoStatic: Updated 3.2 branch instructions</p>
<hr />
<div>{{Template:RPi_Software}}<br />
<br />
= Overview =<br />
This page explains how to rebuild the kernel image for the RPi. There are two possible routes available: <br />
# Compile on the Raspberry Pi itself<br />
# Cross compile on another Linux system<br />
<br />
Both of these routes are covered below, however, you are strongly recommended to follow the cross compilation route. The low processing power of the RPi means that a local compile will take many hours.<br />
<br />
== Example Checklist/Roadmap ==<br />
This section serves to hold a new user's hand just a bit more than some of the other more generic information below in the document. To get more information on the steps in the roadmap, search this page for additional details. It assumes you can navigate filesystems, move files across systems, and have a general understanding of compiling linux kernels, filesystems, partitions, and block devices.<br />
<br />
This series of steps yielded a successful custom/updated hardfp kernel to a stock Raspbian installation, cross compiled from an amd64 Debian system without regression on any kernel configuration options or requiring modified boot parameters. Be aware that in the worst case, you may need to overlay a stock set of kernel/modules/firmware on the Raspberry Pi if something fails. If you do not know how to do this, then a reimage of the SD card may be necessary. Assuming this is not an issue for your configuration, continue onward:<br />
# Get the latest raspberrypi kernel source (git://github.com/raspberrypi/linux.git)<br />
# Set an environment variable KERNEL_SRC to point to the location of the source (e.g. KERNEL_SRC=/home/me/linux/)<br />
# Get the latest raspberrypi compiler (git clone git://github.com/raspberrypi/tools.git)<br />
# Set an environment variable CCPREFIX to point to the location of tools (e.g. CCPREFIX=/home/me/tools/arm-bcm2708/arm-bcm2708-linux-gnueabi/bin/arm-bcm2708-linux-gnueabi-)<br />
# From the kernel clone location, clean the kernel source with "make mrproper"<br />
# Pull the /proc/config.gz from the running Raspbian installation<br />
# Prime kernel with the old config by running "ARCH=arm CROSS_COMPILE=${CCPREFIX} make oldconfig"<br />
# Modify the kernel config by either modifying the .config file or using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make menuconfig"<br />
# Build the new kernel by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} make"<br />
# Set an environment variable MODULES_TEMP to point to the location of the source (e.g. MODULES_TEMP=/home/me/modules/)<br />
# Set aside the new kernel modules by using "ARCH=arm CROSS_COMPILE=${CCPREFIX} modules_install INSTALL_MOD_PATH=${MODULES_TEMP} make"<br />
# From the tools clone location, in the mkimage directory, run "./imagetool-uncompressed.py ${KERNEL_SRC}/arch/arm/boot/zImage"<br />
# Move the resulting kernel.img to the Raspberry Pi's /boot/ directory<br />
# Package up the modules into an archive such that at the top level, the structure looks like this:<br />
#* ./firmware<br />
#* ./firmware/brcm<br />
#* ./firmware/edgeport<br />
#* ./firmware/emi26<br />
#* ...<br />
#* ./modules<br />
#* ./modules/3.6.11+<br />
#* ./modules/3.6.11+/kernel<br />
#* ./modules/3.6.11+/kernel/lib<br />
#* ./modules/3.6.11+/kernel/fs<br />
#* ...<br />
# Move the modules archive to the Raspberry Pi and extract them such that the aforementioned firmware and modules directories overwrite /lib/firmware and /lib/modules<br />
# Get the latest raspberrypi firmware (git://github.com/raspberrypi/firmware.git)<br />
# Transfer the following files from the firmware/boot directory to the Raspberry pi /boot directory:<br />
#* bootcode.bin<br />
#* fixup.dat<br />
#* start.elf<br />
# Transfer the firmware/hardfp/opt directory to the Raspberry pi /opt directory<br />
# Reboot the Raspberry Pi<br />
The Raspberry Pi should now boot with the newly configured/recompiled kernel.<br />
<br />
= Get the kernel source =<br />
The kernel source should be downloaded from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]. Although you could just compile the vanilla kernel from [http://www.kernel.org/ Kernel.org], it will not have the necessary drivers and modules for the Broadcom SoC on the RPi. You can however apply patches from the vanilla kernel to the RPi one - be prepared for potential compiler grumbles though!<br />
<br />
At the time of writing, two branches of interest are available:<br />
* '''rpi-3.2.27''' - This is the version of the kernel currently used in Raspbian, but not exactly the same - Raspbian stock kernel image (the one available from the foundation's website) has a 3.2.27+ version marking. Please see [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=26616 this post] for more details.<br />
* '''rpi-3.6-y''' - This is a development branch based on the current vanilla kernel. It will eventually replace the 3.2 branch. At the time of writing, the exact version is 3.6.11.<br />
<br />
You can download the source directly using git. For the 3.2 branch:<br />
<pre><br />
git clone --depth 1 git://github.com/raspberrypi/linux.git<br />
git checkout rpi-3.2.27<br />
</pre><br />
and for the 3.6 branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/linux.git rpi-3.6.y:refs/remotes/origin/rpi-3.6.y<br />
git checkout rpi-3.6.y<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/linux/archive/rpi-3.2.27.tar.gz rpi-3.2.27] [https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz rpi-3.6.y]<br />
<br />
= Get a compiler =<br />
Next, you will need to get a version of GCC in order to build the kernel.<br />
<br />
== On the RPi ==<br />
<br />
=== Raspbian ===<br />
<pre><br />
apt-get update<br />
apt-get -y dist-upgrade<br />
apt-get -y install gcc make<br />
</pre><br />
<br />
=== Arch Linux ===<br />
<pre><br />
pacman -Syu<br />
pacman -S gcc make<br />
</pre><br />
<br />
== Cross compiling from Linux ==<br />
Please note that when cross-compiling, your compiler may not target the correct ARM processor by default. This will at best reduce performance, or worse, compile for a much newer processor resulting in illegal instructions in your code. The pre-built compiler or a custom-built compiler are recommended because of this. (For example, the latest GCC Linaro binary targets armv7-a by default, whereas the RPi requires armv6kz). It is possible to add extra compiler options to the <tt>HOSTCFLAGS</tt> line in <tt>Makefile</tt>. The correct flags are shown on the [[RPi_Software#Compiler|software page]] - note that you may also need to add <tt>-marm</tt> if your compiler produces Thumb code by default.<br />
<br />
=== Use the provided compiler ===<br />
Download the pre-built bmc2708 compiler from the [https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi RPI tools section on GitHub].<br />
<pre><br />
git clone git://github.com/raspberrypi/tools.git<br />
</pre><br />
or you can download a tarball from the website using [https://github.com/raspberrypi/tools/archive/master.tar.gz this link].<br />
<br />
=== Custom-built Linaro GCC ===<br />
See [[RPi_Linaro_GCC_Compilation|Linaro GCC Compilation]].<br />
<br />
=== Ubuntu ===<br />
<pre><br />
apt-get install gcc-arm-linux-gnueabi make ncurses-dev<br />
</pre><br />
<br />
=== Gentoo Linux ===<br />
<pre><br />
crossdev -S -v -t arm-unknown-linux-gnueabi<br />
</pre><br />
<br />
Crossdev should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. On 2012-05-06, <tt>cross -S -v -A gnueabi arm</tt> works just fine.<br />
<br />
=== Arch Linux ===<br />
<pre><br />
yaourt -S arm-linux-gnueabi-gcc<br />
</pre><br />
<br />
== Cross compiling from OSX ==<br />
=== Macports ===<br />
The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format.<br />
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection]<br />
Install [http://guide.macports.org/#installing macports]<br />
<pre><br />
port install arm-none-eabi-gcc<br />
port install arm-none-eabi-binutils<br />
</pre><br />
<br />
'''If you get an error message that elf.h is missing'''<br />
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf<br />
From opensource.apple.com, download and copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include<br />
<br />
Edit elf.h and add<br />
#define R_386_NONE 0<br />
#define R_386_32 1<br />
#define R_386_PC32 2<br />
#define R_ARM_NONE 0<br />
#define R_ARM_PC24 1<br />
#define R_ARM_ABS32 2<br />
#define R_MIPS_NONE 0<br />
#define R_MIPS_16 1<br />
#define R_MIPS_32 2<br />
#define R_MIPS_REL32 3<br />
#define R_MIPS_26 4<br />
#define R_MIPS_HI16 5<br />
#define R_MIPS_LO16 6<br />
'''If you get a "SEGMENT_SIZE is undeclared" error'''<br />
open the Makefile and change the line:<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)<br />
to<br />
NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux<br />
<br />
=== Yagarto ===<br />
Download and install from [http://www.yagarto.de/#downloadmac here].<br />
<br />
= Perform the compilation =<br />
Firstly, ensure your build directory is clean:<br />
<pre><br />
make mrproper<br />
</pre><br />
<br />
Next, in all cases, you will want to get a working kernel configuration to start from. You can get the one running on the RPi by typing the following (on the RPi):<br />
<pre><br />
zcat /proc/config.gz > .config<br />
</pre><br />
then copy <tt>.config</tt> into your build directory.<br />
<br />
Alternatively, the default configuration is available in the downloaded kernel source in <tt>arch/arm/configs/bcmrpi_defconfig</tt>. Just copy this to <tt>.config</tt> in the build directory.<br />
<br />
From this point on, if you are cross-compiling, please substitute <tt><your_compiler></tt> with your compiler binary prefix (e.g. <tt>arm-bcm2708hardfp-linux-gnueabi-</tt>) as each compiler will be named slightly differently. If you are building on the RPi, remove <tt>ARCH=arm CROSS_COMPILE=<your_compiler></tt> from each command.<br />
<br />
Ensure that your configuration file is up-to-date:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> oldconfig<br />
</pre><br />
If any configuration options have been added, you will be asked what set each option to. If you don't know the answer, just press enter to accept the default.<br />
<br />
Optionally, if you want to make changes to the configuration, run this next:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> menuconfig<br />
</pre><br />
<br />
Now you are ready to build:<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler><br />
</pre><br />
If you are on a multi-core system, you can make the build faster by appending <tt>-j<N></tt> where <tt>N</tt> is the number of cores on your system plus one.<br />
<br />
Find something else to get on with while the compilation takes place. On an average PC with the default configuration, this should take about 15 minutes.<br />
<br />
= Transfer the build =<br />
Copy your new <tt>kernel.img</tt> file into the RPi boot partition, though preferably as a new file (such as <tt>kernel_new.img</tt>) just in case it doesn't work. If you're building on the RPi, just copy the file to <tt>/boot</tt>. If you use a different filename, edit <tt>config.txt</tt> change the kernel line:<br />
<pre><br />
kernel=kernel_new.img<br />
#kernel=kernel.img<br />
</pre><br />
<br />
Now you need to transfer the modules. In the build directory, run the following (substituting <tt><modules_path></tt> for a folder somewhere (e.g. <tt>~/modules</tt>):<br />
<pre><br />
make ARCH=arm CROSS_COMPILE=<your_compiler> INSTALL_MOD_PATH=<modules_path> modules_install<br />
</pre><br />
<br />
The contents of this directory should then be copied into the RPi root directory. NOTE: If you have rebuilt the new kernel with exactly the same version as the one that's running, you'll need to remove the old modules first. Ideally this should be done offline by mounting the SD card on another system.<br />
<br />
Your RPi should now be ready to boot the new kernel. However, at this point it's recommended that you update your GPU firmware and libraries. '''This is required if you've just moved from 3.2 to 3.6 as the firmware interface has changed'''.<br />
<br />
= Get the firmware =<br />
The firmware and boot files should be updated at the same time to ensure that your new kernel works properly. Again, two branches are available:<br />
* '''master''' - This is the version of firmware currently used in Raspbian (i.e. it works with the 3.2 kernel).<br />
* '''next''' - This is a development branch which provides a newer GPU firmware to work with the updated drivers in the 3.6 kernel.<br />
<br />
You can either download the source directly using git:<br />
You can download the firmware directly using git. For the master branch:<br />
<pre><br />
git clone git://github.com/raspberrypi/firmware.git<br />
</pre><br />
and for the next branch:<br />
<pre><br />
git fetch git://github.com/raspberrypi/firmware.git next:refs/remotes/origin/next<br />
</pre><br />
Or you can download a tarball from the website using these links: [https://github.com/raspberrypi/firmware/archive/master.tar.gz master] [https://github.com/raspberrypi/firmware/archive/next.tar.gz next]<br />
<br />
= Transfer the firmware =<br />
Firstly, update the required boot files in the RPi <tt>boot</tt> directory with those you've downloaded. These are:<br />
* bootcode.bin<br />
* fixup.dat<br />
* start.elf<br />
<br />
Next, you need to copy the VC libraries over. There are two copies of this: one for hard float and one for soft float. To find the correct one, run the following command (substituting the program name for your compiler binary as required):<br />
<pre><br />
arm-none-linux-gnueabi-gcc -v 2>&1 | grep hard<br />
</pre><br />
<br />
If something prints out, and you can see <tt>--with-float=hard</tt>, you need the hard float ones. NOTE: The current version of Raspbian uses hard float.<br />
<br />
Remove the <tt>/opt/vc</tt> directory from the RPi root, then:<br />
* For hard float, copy <tt>vc</tt> from the <tt>hardfp/opt</tt> directory into <tt>/opt</tt> in the RPi root directory<br />
* Otherwise copy <tt>vc</tt> from the top-level <tt>opt</tt> directory into <tt>/opt</tt> in the RPi root directory.<br />
<br />
= Test your build =<br />
Power cycle your RPi and check the following:<br />
* If you have the serial port on the GPIO expander wired up, you should see the kernel booting.<br />
* The screen works - the kernel boots and you get a login prompt.<br />
* The VC interface is working - if the 'OK' LED flashes regularly eight or so times every few seconds once the OS has booted, it's not. You can also test this by running <tt>vcgencmd measure_temp</tt>. If it prints "VCHI initialization failed", you have the a mismatch between the firmware, the VC libraries, and the kernel driver.<br />
* Run <tt>uname -a</tt> and check that your new kernel is the one that's running.<br />
* Make sure you don't have any odd error messages during boot that may indicate a module isn't working properly. If you see <tt>missed completion of cmd 18</tt> regarding DMA transfers to the SD card, you can safely ignore it.<br />
<br />
{{Template:Raspberry Pi}}<br />
[[Category:RaspberryPi]]</div>AutoStatic