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>

+

+

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 18:

Line 21:

|'''Pictures'''

|'''Pictures'''

−

|-

−

|[[DVBWorld]]<br> [[DVBWorld DVB-C USB|DW3101]]

−

|

−

* Philips CU1216 tuner

−

* NXP/Philips TDA10023HT demodulator

−

|NO Card reader

−

|http://liplianin.at.tut.by/ds110en.html

−

|[http://www.worlddvb.com/product/htm/usbc.htm]

|-

|-

Line 31:

Line 26:

|

|

* Samsung DTOS403IH102A tuner

* Samsung DTOS403IH102A tuner

−

* NXP/Philips TDA10023HT demodulator

+

* [[NXP TDA1002x|NXP/Philips TDA10023HT]] demodulator

|Card reader

|Card reader

|

|

Line 39:

Line 34:

|-

|-

−

|[[Anysee]]<br> [[Anysee E30 Combo Plus|E30 Combo Plus]]

+

|[[Anysee]]<br> [[Anysee_E30|Anysee E30 Combo Plus]]

|

|

+

Version 1

* ?

* ?

+

Version 2

+

* DNOD44CDV086A tuner

+

* TDA18212 demodultator

|Card reader - not tested

|Card reader - not tested

|

|

Line 47:

Line 46:

* USB device ID: 1c73:861f

* 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.

* 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 - not tested.

+

* 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.

*Driver support seems to be available in kernel as of 2012/03/19 ([http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=c247d7b107c6654bb73d539485df649db5c0796f] [http://patchwork.linuxtv.org/patch/10404/] [http://www.mail-archive.com/linux-media@vger.kernel.org/msg38055.html])

+

*"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 [[http://www11.zippyshare.com/v/17827014/file.html|dvb-demod-drxk-pctv.fw]]

+

|[[File:Pctv_quatrostick_nano_520e.jpg|thumb|520e]]

+

|-

+

|[[Sundtek]]<br> Sundtek MediaTV Pro

+

|

+

* ?

+

|

+

* ?

+

|

+

* 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)

Revision as of 13:20, 3 December 2012

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!)

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!

Contents

Supported DVB-C USB Devices

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.

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).

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.

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)

Proprietary drivers replace the DVB drivers for other non-TBS devices with old ones

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(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.