DVB-C USB Devices: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(DigiVox Trio)
 
(31 intermediate revisions by 8 users not shown)
Line 4: Line 4:
<br>
<br>
__TOC__
__TOC__

<br>
==Firmwares==
==Supported DVB-C USB Devices==
Many of the devices on this page need a firmware, the best source for firmwares is [https://github.com/OpenELEC/dvb-firmware 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-C USB Devices==
The following tables list the known DVB-C 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 [[DVB-C USB Devices/Full|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).


{{Device_List_Medium_Detail/Header
| content =
{{USB_Device_Data
|renderwith=Device_List_Medium_Detail/Row
|selatt1=hostinterface
|selval1=USB
|selatt2=standard
|selval2=DVB-C
}}
}}


==Supported DVB-C USB Devices (old data)==
The following table lists the confirmed working DVB-C USB device and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.
The following table lists the confirmed working DVB-C USB device and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.
<br>
<br>


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).
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). Otherwise a single USB2.0 port may not sustain two HD recordings; check with `lsusb -t` that two devices do not share the same Bus.
<br>
<br>


Line 31: Line 68:
* dvb-usb-anysee.ko
* dvb-usb-anysee.ko
* Note: the newest version not yet supported by the driver, but the earlier three versions are. Would need help from someone with the newest device. At least in kernel 2.6.27 the card reader is not supported (empirical evidence and notes in the driver).
* Note: the newest version not yet supported by the driver, but the earlier three versions are. Would need help from someone with the newest device. At least in kernel 2.6.27 the card reader is not supported (empirical evidence and notes in the driver).
|


|-
|[[Delock]]<br> [[Delock_61959|Delock_61959]]
|
|NO Card reader
|
* Note: there are two versions. Version 1 is supported, version2 is unsupported.
|
|


Line 50: Line 96:
|
|
|-
|-
|[[DVBWorld]]<br> [[DVBWorld DVB-C USB|DW3101]]
|[[Hauppauge]]<br>[[Hauppauge_WinTV-HVR-930C|WinTV HVR-930C]]
|
|
* Philips CU1216 tuner
* [[NXP TDA1002x|NXP/Philips TDA10023HT]] demodulator
|NO Card reader
|NO Card reader
|BE AWARE! The WinTV HVR-930C'''-HD''' with device ID 2040:b130 is ''not'' supported! Only the non-HD variant with device ID 2040:1605 will work. Firmware dvb-usb-hauppauge-hvr930c-drxk.fw (same as TerraTec HTC stick: https://linuxtv.org/patch/11683/)
|http://liplianin.at.tut.by/ds110en.html
|
|[http://www.worlddvb.com/product/htm/usbc.htm]
|-
|[[MaxMedia]]<br>[[MaxMedia UB425-TC|UB425-TC]]
|
|NO Card reader
|
|
|-
|[[MSI]]<br>[[MSI DigiVox Trio|DigiVox Trio]]
|
|NO Card reader
|Firmware dvb-usb-terratec-h5-drxk.fw
|
|-
|[[Pinnacle|PCTV]]<br>[[PCTVSystems_QuatroStick-_510e|QuatroStick (510e)]]
|
|NO Card reader
|Appears in Documentation_video4linux_CARDLIST.em28xx, so presumably supported.
|
|-
|-
|[[Pinnacle|PCTV]]<br>[[PCTVSystems_QuatroStick-nano_520e|QuatroStick nano (520e)]]
|[[Pinnacle|PCTV]]<br>[[PCTVSystems_QuatroStick-nano_520e|QuatroStick nano (520e)]]
Line 71: Line 133:
|[[File:Pctv_quatrostick_nano_520e.jpg|thumb|520e]]
|[[File:Pctv_quatrostick_nano_520e.jpg|thumb|520e]]
|-
|-
|[[Sundtek]]<br> Sundtek MediaTV Pro
|[[TerraTec]]<br>[[TerraTec_H5|H5]]
|
|
|NO Card reader
* ?
|Firmware dvb-usb-terratec-h5-drxk.fw
|
|
|-
* ?
|[[TerraTec]]<br>[[TerraTec_Cinergy_HTC_Stick_HD|Cinergy HTC Stick HD]]
|
|
|NO Card reader
* Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
|
* Manufacturer provides [http://support.sundtek.de/index.php?topic=4.0 Driver] for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)
*ID 0ccd:00b2. Firmware dvb-usb-terratec-htc-stick-drxk.fw
*Ubuntu 12.10 and higher supported
*Allwinner ARM A10 custom kernel 3.4 supported (w_scan cannot found any channel but tvheadend can)
*Works well with Tvheadend
*http://linux.terratec.de/images/CinergyHTCStick.png
|[[Image:CinergyHTCStick.png|link=http://linux.terratec.de/images/|Cinergy HTC Stick HD]]
|-
|[[TerraTec]]<br>[[TerraTec_Cinergy_HTC_USB_XS|Cinergy HTC USB XS]]
|
|NO Card reader
|ID 0ccd:008e,0ccd:00ac. Firmware unknown? Maybe same as H5? (https://linuxtv.org/patch/7685/)
|
|


|-
|-
|[[TechniSat]]<br> [[TechniSat CableStar USB / Cable4PC USB|CableStar USB / Cable4PC USB]]
|[[TechniSat]]<br> [[TechniSat CableStar USB / Cable4PC USB|CableStar USB / Cable4PC USB]]
Line 127: Line 200:
|
|
* DVB-C and DVB-T supported ([[http://www.spinics.net/lists/linux-media/msg18971.html]] [[http://www.spinics.net/lists/linux-media/msg36404.html]])
* DVB-C and DVB-T supported ([[http://www.spinics.net/lists/linux-media/msg18971.html]] [[http://www.spinics.net/lists/linux-media/msg36404.html]])
* CI supported from kernel 3.2 ([[http://www.spinics.net/lists/linux-media/msg37983.html]] [[https://lkml.org/lkml/2011/10/31/95]])
* CI supported from kernel 3.2 ([http://www.tbsdtv.com/download/]])
* Module dvb_usb_ttusb2 is needed.
* Module dvb_usb_ttusb2 is needed.
* Works well with [https://www.lonelycoder.com/tvheadend/ Tvheadend]
* Works well with [https://www.lonelycoder.com/tvheadend/ Tvheadend]
|[[File:TT-connect CT-3650 CI.jpg|thumb|CT-3650 CI]]
|[[File:TT-connect CT-3650 CI.jpg|thumb|CT-3650 CI]]


|-
|[[TechnoTrend]]<br> [[TechnoTrend TT-connect CT2-4650 CI|TT-connect CT2-4650 CI]]
|
* vendorId 0b48
* productId 3012
| Common Interface (CI) - Not yet tested
|
* DVB-C and DVB-T supported
* Modules dvb_usb_ttv2, dvb_usb_v2
* it seems part of the driver (sit2.o in vendor-provided [http://www.tt-downloads.de/Linux/media_build-tt-130819.tar.gz]) is only available in binary form?!
|
|}

== Supported by 3rd Party Drivers ==
{{3rd_party_drivers}}

=== Kernel Space Drivers ===
{| border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
|'''Manufacturer<BR>Model'''
|'''Components'''
|'''Connectors'''
|'''Comments'''
|'''Pictures'''

|-
|[[DVBSKY]]<br> [[DVBSKY_T680C|T680C]]
|?
|Common Interface
|Needs v4l-dvb fork from dvbsky
|[http://www.dvbsky.net/Products_T680C.html]
|-
|[[DVBWorld]]<br> [[DVBWorld DVB-C USB|DW3101]]
|
* Philips CU1216 tuner
* [[NXP TDA1002x|NXP/Philips TDA10023HT]] demodulator
|NO Card reader
|http://liplianin.at.tut.by/ds110en.html
|[http://www.worlddvb.com/product/htm/usbc.htm]
|-
|[[TBS]]<br> [[TBS5680 DVB-C TV Tuner CI USB|TBS5680 DVB-C TV Tuner CI USB]]
|
* CY7C68013
* TDA10024 DVB-C demodulator
* TDA18252

| Common Interface (CI) - Tested successfully with latest kernel and Viaccess/Conax/Irdeto CAM.

|
* DVB-C supported ([[http://www.tbsdtv.com/products/tbs5680-dvb-c-tv-tuner-ci-usb.html]])
* CI supported from latest kernel ([http://www.tbsdtv.com/download/]])
* Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones

|

|-
|[[TBS]]<br> [[TBS5880_USB_DVB-T2/T/C_CI_hybrid_TV_Box|5880 DVB-T2/T/C CI hybrid TV Box]]
|
* DNOT44QCH266A
* CY7C68013

| Common Interface (CI)

|
* DVB-C, DVB-T, DVB-T2 supported
* CI supported from latest kernel ([http://www.tbsdtv.com/download/]])
* Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones
|
|}


=== Userspace Drivers ===
{| border=1 cellpadding=2 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
|'''Manufacturer<BR>Model'''
|'''Components'''
|'''Connectors'''
|'''Comments'''
|'''Pictures'''
|-
|[[Sundtek]] MediaTV Pro III
|
* ?
|
* ?
|
* DVB-C
* DVB-T
* DVB-T2
* AnalogTV (PAL/NTSC/SECAM + VBI/ClosedCaption)
* FM Radio / RDS
* S-Video
* Composite
* Supports Linux 2.6.15+ ARM/MIPS/PPC/SH4/X86/X86-32<br>
* Product: [http://sundtek.com/shop/Digital-TV-Sticks/Sundtek-MediaTV-Pro-III-DVB-C/T/T2-FM-Radio-AnalogTV.html Sundtek MediaTV Pro III]
* Drivers: [http://support.sundtek.de/index.php?topic=4.0 Driver]
* Manufactured in Germany/Berlin
|
|-
|[[Sundtek]] MediaTV Pro
|
* ?
|
* ?
|
* Device is EOL (but still supported)
* Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
* Manufacturer provides [http://support.sundtek.de/index.php?topic=4.0 Driver] for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)
|}
|}


Line 139: Line 320:
* Tongshi DVB-C USB [http://www.tongshi.com/cp_dvb_e.htm] ... ''is this just a reference design?''
* Tongshi DVB-C USB [http://www.tongshi.com/cp_dvb_e.htm] ... ''is this just a reference design?''
* [[TechniSat CableStar Combo HD CI]]
* [[TechniSat CableStar Combo HD CI]]
* [[Hauppauge_WinTV-HVR-930C-HD|WinTV HVR-930C-HD]]


==Also See==
==Also See==

Latest revision as of 15:37, 11 January 2015

On this page you will find information regarding DVB-C 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!


Firmwares

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-C USB Devices

The following tables list the known DVB-C 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).


Vendor
Device/Model
Supported ID on
Interface
Hardware Firmware Comment / Pictures URL E
Anysee E7 No 1c73:861f USB2.0 N/A 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. Anysee E7 T2C [1] Jump to the place where you can edit this entry
Anysee E30 Combo Plus Yes, in kernel since 2.6.28 1c73:861f or 04b4:861f USB2.0 zl10353 or tda10023 demodulator Does DVB-T and DVB-C depending on anysee.ko module parameter delsys= (0=DVB-C, 1=DVB-T). [2] Jump to the place where you can edit this entry
Microsoft Xbox One Digital TV Tuner Yes 045e:02d5 USB2.0 DiBcom DiB7000 / Panasonic MN88472 / TDA 18250B dvb-usb-dib0700-1.20.fw Jump to the place where you can edit this entry
TechnoTrend TT-connect CT-3650 CI Yes, in kernel since 3.2 0b48:300d USB2.0 Philips TDA10023 DVB-C, NXP TDA10048HN DVB-T N/A Combined DVB-T/DVB-C with integrated CI, which is fully supported from kernel 3.2. TT-connect CT-3650 CI.jpg [3] Jump to the place where you can edit this entry
Geniatech T220 Yes, in kernel since 3.14, Users reporting errors with DVB-T2 1f4d:d220 USB2.0 Sony CXD2820R / NXP TDA18271HD/C2 / Cypress CY7C68013A N/A Looks like August DVB-T210 is a rebranded device with the same usbids. [4] Jump to the place where you can edit this entry
PCTV Systems nanoStick T2 290e Yes, in kernel since 3.0 2013:024f USB2.0 eMPIA em28xx, Sony CXD2820R, NXP TDA18271HD/C2 N/A 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. PCTV nanoStick T2 290e PCB em28xx demod.jpg [5] Jump to the place where you can edit this entry
Astrometa DVB-T2 DVB-T Yes, in kernel since 3.13, DVB-T2 Yes, in kernel since 4.6 15f4:0131 USB2.0 RealTek RTL2832P, Panasonic MN88472 or MN88473, Rafael Micro R828D Popular generic DVB-T2 USB tuner from different Chinese suppliers Astometa HD-901T2 [6] Jump to the place where you can edit this entry
Geniatech T230
MyGica T230
August T210v2
Geniatech PT360 (USB-OTG)
MyGica PT360 (USB-OTG)
D202 (USB-OTG, OEM)
Yes 0572:c688 USB2.0 Silicon Labs Si2148-A20 or Si2158-A20, Silicon Labs Si2168-B40, Cypress EZ-USB FX2 CY7C68013A dvb-demod-si2168-b40-01.fw, dvb-tuner-si2158-a20-01.fw kernel >= 3.19, remote control supported. Geniatech-t230.jpg [7] Jump to the place where you can edit this entry
Geniatech T230C
MyGica T230C
eyeTV T2
eyeTV T2 Hybrid
eyeTV T2 Lite
~ Partial You may have to build the drivers yourself 0572:c689 USB 2.0 Silicon Labs Si2141-A10, Silicon Labs Si2168-D60, Cypress EZ-USB FX2 CY7C68013A dvb-demod-si2168-d60-01.fw dvb-tuner-si2141-a10-01.fw Fully works if the correct drivers are used Geniatech-t230.jpg Jump to the place where you can edit this entry
Geniatech T230C2
MyGica T230C2
August DVB-T210 v2.0
August DVB-T230
Yes, in kernel since 5.4 0572:c68a USB2.0 Silicon Labs Si2141-A10, Silicon Labs Si2168-D60, Cypress EZ-USB FX2 CY7C68013A, Evolveo Sigma T2 [dvb-demod-si2168-d60-01.fw, dvb-tuner-si2141-a10-01.fw] Drivers can be built with media_build for older kernels. Evidence of August DVB-T210 v2.0 using Geniatech T230 in the past, ones bought today are likely to be T230C2 instead. Geniatech-t230.jpg Evolveo Sigma T2.jpeg August.jpg [8] Jump to the place where you can edit this entry
TerraTec Cinergy T2 Stick HD Yes eb1a:8179 USB2.0 Silicon Labs Si2146, Silicon Labs si2168, Empia EM28178 dvb-demod-si2168-a30-01.fw kernel >= 3.19, remote control supported. TerraTec Cinergy T2 Stick HD.jpg [9] Jump to the place where you can edit this entry
PCTV Systems tripleStick 292e Yes 2013:025f USB2.0 Silicon Labs Si2157, Silicon Labs Si2168, eMPIA em28174 dvb-demod-si2168-b40-01.fw First version of the driver has been released, look here [10] Jump to the place where you can edit this entry
TechnoTrend TVStick CT2-4400 Yes 0b48:3014 USB2.0 Silicon Labs Si2158, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-a30-01.fw [11] Jump to the place where you can edit this entry
TechnoTrend TT-connect CT2-4650 CI Yes 0b48:3012 USB2.0 Silicon Labs Si2158, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-a20-01.fw, dvb-tuner-si2158-a20-01.fw [12] Jump to the place where you can edit this entry
TechnoTrend TT-connect CT2-4650 CI v1.1 Yes 0b48:3015 USB2.0 Silicon Labs Si2157, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-b40-01.fw, dvb-demod-si2168-02.fw, dvb-tuner-si2158-a20-01.fw Patch for v1.1 (2016) [13] Jump to the place where you can edit this entry
Hauppauge Hauppauge_WinTV-soloHD Yes 2040:0264 USB2.0 Silicon Labs Si2157, Silicon Labs Si2168, eMPIA em28174 dvb-demod-si2168-b40-01.fw First version of the driver has been released, look here [14] Jump to the place where you can edit this entry
Hauppauge Hauppauge_WinTV-dualHD Model 01590 Yes, in kernel since 4.17 2040:0265 USB2.0 Silicon Labs Si2157, Silicon Labs Si2168,Empia EM28274 dvb-demod-si2168-b40-01.fw Kernel >=4.7 first tuner only, kernel patch for both tuners. Kernel >=4.17 both tuners suported. [15] Jump to the place where you can edit this entry


Supported DVB-C USB Devices (old data)

The following table lists the confirmed working DVB-C USB device and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.

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). Otherwise a single USB2.0 port may not sustain two HD recordings; check with `lsusb -t` that two devices do not share the same Bus.


Manufacturer
Model
Components Connectors Comments Pictures


Anysee
E30C Plus
Card reader
  • dvb-usb-anysee.ko
  • Note: the newest version not yet supported by the driver, but the earlier three versions are. Would need help from someone with the newest device. At least in kernel 2.6.27 the card reader is not supported (empirical evidence and notes in the driver).


Delock
Delock_61959
NO Card reader
  • Note: there are two versions. Version 1 is supported, version2 is unsupported.
Anysee
Anysee E30 Combo Plus

Version 1

  • ?

Version 2

  • DNOD44CDV086A tuner
  • TDA18212 demodultator
Card reader - not tested
  • dvb-usb-anysee.ko
  • USB device ID: 1c73:861f
  • This is a combined (Combo) DVB-T and DVB-C -device. The default mode is DVB-C. DVB-T -mode can be selected with a command "sudo modprobe dvb-usb-anysee delsys=1". Both modes seem to work.
  • Includes a remote control - only number and volume buttons work, so you still need another input method.
  • Note: The device comes in two versions, version 1 is supported from Linux kernel version 2.6.28 and version 2 is supported in Linux kernel version 3.0.0 (possibly earlier). Version 2 can be distinguished from version 1 by the loop antenna output which is absent on version 1.
Hauppauge
WinTV HVR-930C
NO Card reader BE AWARE! The WinTV HVR-930C-HD with device ID 2040:b130 is not supported! Only the non-HD variant with device ID 2040:1605 will work. Firmware dvb-usb-hauppauge-hvr930c-drxk.fw (same as TerraTec HTC stick: https://linuxtv.org/patch/11683/)
MaxMedia
UB425-TC
NO Card reader
MSI
DigiVox Trio
NO Card reader Firmware dvb-usb-terratec-h5-drxk.fw
PCTV
QuatroStick (510e)
NO Card reader Appears in Documentation_video4linux_CARDLIST.em28xx, so presumably supported.
PCTV
QuatroStick nano (520e)
NO Card reader
  • Driver support seems to be available in kernel as of 2012/03/19 ([16] [17] [18])
  • "Analog is not supported currently. Only DVB-T and DVB-C."
  • "There seems to be still problems for locking DVB-C channels which have strong signal. Attenuator helps. I think it is demodulator IF/RF AGC issue. Lets fix it later. Patches are welcome."

Will not work out of the box yet (as of 2012/04/16). You will need to build the latest media drivers, and download the firmware file [[19]]

520e
TerraTec
H5
NO Card reader Firmware dvb-usb-terratec-h5-drxk.fw
TerraTec
Cinergy HTC Stick HD
NO Card reader
  • ID 0ccd:00b2. Firmware dvb-usb-terratec-htc-stick-drxk.fw
  • Ubuntu 12.10 and higher supported
  • Allwinner ARM A10 custom kernel 3.4 supported (w_scan cannot found any channel but tvheadend can)
  • Works well with Tvheadend
  • http://linux.terratec.de/images/CinergyHTCStick.png
Cinergy HTC Stick HD
TerraTec
Cinergy HTC USB XS
NO Card reader ID 0ccd:008e,0ccd:00ac. Firmware unknown? Maybe same as H5? (https://linuxtv.org/patch/7685/)
TechniSat
CableStar USB / Cable4PC USB
TechnoTrend
PCLine DVB-C USB
TechnoTrend
TT-Connect C-1100 USB
  • dvb-ttusb-budget.ko
TechnoTrend
TT-Connect C-1200 USB
  • TechnoTrend USB IR also works
  • Support in lirc 0.8.2.
TechnoTrend
TT-connect CT-3650 CI
  • Philips TDA8274 tuner
  • TDA10023 DVB-C demodulator
  • TDA10048 DVB-T demodulator
  • Cypress FX2
Common Interface (CI) - Tested successfully with kernel 3.2 and a Viaccess 4.0 DVB-T CAM.
  • DVB-C and DVB-T supported ([[20]] [[21]])
  • CI supported from kernel 3.2 ([22]])
  • Module dvb_usb_ttusb2 is needed.
  • Works well with Tvheadend
CT-3650 CI
TechnoTrend
TT-connect CT2-4650 CI
  • vendorId 0b48
  • productId 3012
Common Interface (CI) - Not yet tested
  • DVB-C and DVB-T supported
  • Modules dvb_usb_ttv2, dvb_usb_v2
  • it seems part of the driver (sit2.o in vendor-provided [23]) is only available in binary form?!

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.

In-Kernel 3rd party Drivers

Advantages:

  1. It's possible your device will work.. for the moment.
  2. If the manufacturer provides open source drivers with an acceptable license, volunteers could technically implement this code in the Linux kernel for true support. However.. :

Disadvantages:

  1. The quality of the code (if open, there are also cases where you just get a binary blob) too often just isn't good enough and there's still too much work to be done to make the device work. There was probably a reason the manufacturer didn't just send their patches to the linux-media mailinglist.
  2. Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.
  3. When the manufacturer stops updating the drivers, the drivers will quickly refuse to install as newer kernels are released.

In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist Linux-Media Mailing List (LMML). Keep in mind however that if the license isn't compatible with the Linux kernel or the quality of the code isn't good enough, these will not become a part of the Linux kernel.

NOTE: As linux media drivers are character based, drivers can be also written using libfuse's character device in userspace example. If written that way, an out-of-kernel driver can be written, which fully integrates to udev without the disadvantage of closed source or incompatibility to other drivers. Such driver would rely on kernel fuse and character device in user space support as well as libfuse.

Closed source userspace drivers (Sundtek)

Advantages:

  1. Same driver works with different Linux versions
  2. No need to reinstall drivers when your kernel is updated.
  3. Drivers can be profiled easily and more accurately than in kernelspace.
  4. If the driver crashes, it won't crash the system or kernel, only the driver and applications using the driver will be affected. Userspace drivers can also be used when debugging drivers for USB host controllers, as the userspace driver can't crash the system, making debugging easier.
  5. If the manufacturer would stop to support the drivers, the userspace driver will still continue to work with newer Linux systems

Userspace drivers use a modern device infrastructure, Kernelspace drivers were available at a time when Linux did not support userspace drivers, Sundtek spent a substantial amount of work to make userspace drivers happen.

As a track record, most Linux distributions and many Settopboxes which were released since 2006 are supported, even open source drivers don't have such a high backward compatibility.

Disadvantages:

  1. You can't look into the sources. While this may be not a problem for end-users, in case of issues Sundtek provides a support forum.

Kernel Space Drivers

Manufacturer
Model
Components Connectors Comments Pictures
DVBSKY
T680C
? Common Interface Needs v4l-dvb fork from dvbsky [24]
DVBWorld
DW3101
NO Card reader http://liplianin.at.tut.by/ds110en.html [25]
TBS
TBS5680 DVB-C TV Tuner CI USB
  • CY7C68013
  • TDA10024 DVB-C demodulator
  • TDA18252
Common Interface (CI) - Tested successfully with latest kernel and Viaccess/Conax/Irdeto CAM.
  • DVB-C supported ([[26]])
  • CI supported from latest kernel ([27]])
  • Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones
TBS
5880 DVB-T2/T/C CI hybrid TV Box
  • DNOT44QCH266A
  • CY7C68013
Common Interface (CI)
  • DVB-C, DVB-T, DVB-T2 supported
  • CI supported from latest kernel ([28]])
  • Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones


Userspace Drivers

Manufacturer
Model
Components Connectors Comments Pictures
Sundtek MediaTV Pro III
  • ?
  • ?
  • DVB-C
  • DVB-T
  • DVB-T2
  • AnalogTV (PAL/NTSC/SECAM + VBI/ClosedCaption)
  • FM Radio / RDS
  • S-Video
  • Composite
  • Supports Linux 2.6.15+ ARM/MIPS/PPC/SH4/X86/X86-32
  • Product: Sundtek MediaTV Pro III
  • Drivers: Driver
  • Manufactured in Germany/Berlin
Sundtek MediaTV Pro
  • ?
  • ?
  • Device is EOL (but still supported)
  • Opensource Kernelspace driver available for improving the datatransfer, but usually works without it and entirely in userspace (devicesetup is entirely done in Userspace). Drivers are proprietary but well supported. (since mid 2009)
  • Manufacturer provides Driver for Intel 32-bit, 64-bit, ARM (eabi4) and PowerPC(PlayStation 3 first Rev.), MIPS as far as website info goes (further architectures are available upon request). Driver claims support for AnalogTV, Composite, S-Video, VBI/Closed Caption, FM-Radio, DVB-T, DVB-C, Remote Control (keyboard emulation and lirc support)

Currently Unsupported DVB-C 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 developers' 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 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 garnering a response—a distinct byproduct of the fact that there are 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 hire someone who can.

Also See