On this page you will find information regarding DVB-T2 USB devices.
Please be aware that
- The information contained here is likely non-exhaustive and, despite best efforts to do otherwise, may contain errors. (Please help to keep these lists up-to-date so that they are useful for everyone!)
- If your device is not listed, try:
- searching the existing mailing list archives:
- Linux-Media Mailing List (LMML) archives (via vger or .... )
- or from the older mailing lists (now largely deprecated in favour of the LMML):
- dvb mailing list archives (via spinics or MARC ... )
- v4l mailing list archives (via .... )
- searching for information with Google or other internet search engine
- by posting a question about the device directly to the LMML (but please do conduct a search first, as it may already have been discussed!)
- Note: when it comes to support, it is generally a good idea to try the current V4L-DVB sources because some device drivers can be very new and thus may have not made their way into the mainstream kernel.
- In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.
- Because the component constitution on many devices are often similar or identical, there may be devices that are unlisted but may actually work with the existing driver framework for previously supported devices. In such a case, your non-listed but working device will likely be reported in your system messages as being one of those previously supported devices. If you encounter such an occurrence, please do report your success on the LMML so that proper detection/identification of your device can be added within the drivers.
- Lastly, it bears worth repeating the request: Please help to keep these lists up-to-date so that they are useful for everyone!
Many of the devices on this page need a firmware, the best source for firmwares is OpenELEC dvb-firmware repository.
The firmwares on OpenELEC's repository are already extracted, just download the proper .fw file and copy to your firmware folder (usually /usr/lib/firmware).
DVB-T2 USB Devices
The following tables list the known DVB-T2 USB devices and provides a brief summary of their features and components. (or at least it should)
If you need more technical information on a device, have a look at its device specific wiki article if there is one.
The device specific article is linked via the device's name but not all are linked yet.
If you find an article (e.g. via the search feature on the left) then please edit the device entry here add that link.
Just click on the edit icon in the last column of the device's row.
If you are unsure about how to do it, click on the edit icon for a device that already has a link to see how it is done.
Please feel free to create a device specific page if there is enough worthwhile information that doesn't fit in the comments field.
There is also a full detail table.
If you'd like to add a new device (supported or unsupported), please go to Template:USB_Device_Data and follow the instruction there.
If a device is unsupported, please add with which OS/kernel version you tested last.
If you are experiencing problems with USB devices, it may not be the fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset (e.g. VIA 6212L, NEC).
|| ID on |
|| Comment / Pictures
| Anysee E7
|| ✘ No
|| 1c73:861f USB2.0
|| This is a generic entry for the Anysee E7 line. If you have details for a particular device, please feel free to clone this entry and add the details.
| Geniatech T220
|| ✔ Yes, in kernel since 3.14
|| 1f4d:d220 USB2.0
|| Sony CXD2820R / NXP TDA18271HD/C2 / Cypress CY7C68013A
|| Looks like August DVB-T210 is a rebranded device with the same usbids.
| PCTV Systems nanoStick T2 290e
|| ✔ Yes, in kernel since 3.0
|| 2013:024f USB2.0
|| Empia em28xx / Sony CXD2820R / NXP TDA18271HD/C2
|| First DVB-T2 capable receiver with Linux support. Kernel 3.2+ or latest media-build may be needed for multiple Empia-based devices to work together. Details on development history.
| Astrometa DVB-T2
|| ✔ Yes, in kernel since 3.13, only DVB-T
|| 15f4:0131 USB2.0
|| RealTek RTL2832P, Panasonic MN88472, Rafael Micro R828D
|| Popular generic DVB-T2 USB tuner from different Chinese suppliers
Currently Unsupported DVB-T2 USB Devices
If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List
(LMML). Note that if your device is similar to or contains components for which driver development is currently being undertaken, then it is possible that you will pique the(se) developer's interest and can obtain some assistance that, possibly, leads to full support for your device.
However, please note that inquiries to the mailing list:
- should NOT be treated as an order drop-off line/queue. You're soliciting help from volunteer developers who work on V4L-DVB matters in their spare time, and such work can be non-trivial (i.e. requiring even _thousands_ of hours work). So being demanding is one sure route to being ignored. (Honestly, this point really shouldn't even need to be written, but you'd be surprised at the number of irrational individuals who write into the mailing list demanding this or that).
- may pass without even garnering a response -- that's a distinct by-product of the fact that there are only a limited number of developers, whom might be able to help, that are associated with the project. Often times, even if they wished to help, their energies are entirely tied up with other projects. In such cases, the best path might be to try to spearhead the driver development for your device yourself, or arrange to hire someone who can.
Please don't add your device here, instead add it to the table above.
Supported by 3rd Party Drivers
Sometimes a manufacturer forks v4l-dvb all on their own and writes a driver for their device so they can claim Linux support.
1. You might get well support for your device
2. If the manufacturer provides open source drivers, volunteers are able to provide long term support and submit it to the Linux Kernel.
1. If the manufacturer provides binary modules, or object files you might have to recompile the 3rd party driver every time you update your local kernel version. Compiling might require some additional dependencies (eg. linux source tree, specific toolchain for particular architectures etc. so it might not be so easy to install them everywhere
2. If the manufacturer stops updating the drivers you might loose support for those drivers on newer Linux systems
In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist Linux-Media Mailing List (LMML)
1. Generic over nearly all Linux versions starting from 2.6.15 on
2. No recompilation needed if you update your kernel version
3. Manufacturer might provide well support for the device you bought
4. Drivers can be profiled easily and more accurately than in kernelspace
5. If the driver crashes your system won't be affected
6. If the manufacturer would stop to support the drivers, the application driver will still continue to work with newer Linux systems since the Kernelspace <-> Userspace interfaces are fixed and are not meant to be changed
1. this is only meant for hackers that they won't have insight about what the manufacturer is doing, regular endusers usually won't cope with device driver sources anyway