On this page you will find information regarding DVB-T2 PCIe cards.
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 PCIe Devices
The following tables list the known DVB-T2 PCIe 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:PCI_Device_Data and follow the instruction there.
If a device is unsupported, please add with which OS/kernel version you tested last.
Currently Unsupported DVB-T2 PCIe cards:
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.