DVB-C PCI Cards

From LinuxTVWiki
Revision as of 20:48, 23 August 2007 by Euroguy (talk | contribs)
Jump to navigation Jump to search

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


Supported DVB-C PCI Cards

The following table lists the confirmed working DVB-C PCI cards 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.


Manufacturer /

Model number /

Price

Supports Tuner / Chips Connections Others Pictures
Siemens
DVB-C PCI

(PDF-Doku:
[1] engl.
[2] dt.)

ca. 80 € gebraucht (zzgl CI & analog)

yes Antenna in

Video-connector-cable
Common Interface

Hauppauge
WinTV DVB-C Rev. 2.1
[3]

ca. 200 € (plus CI & analog)

yes Antenna in

Antenna out
Video-connector-cable
Jumper2
Common Interface

Hauppauge dvb-c 2.1.jpg
Hauppauge
WinTV-Nexus-CA
German Swedish

ca. 325 €

Partial, problems with sound
Analog tuner not supported

Antenna in
Composite Video-IN
Composite Video-OUT
Audio Line-OUT
Audio Line-IN
Digital Audio OUT (S/PDIF)
Common Interface

Includes analog tuner
Identical to TechnoTrend Premium C-2300
TechnoTrend
C-1500 German

ca. 90 €

yes (from kernel 2.6.13)

QAM128 may require driver modification (included in kernel 2.6.16)

Antenna in
Common Interface

QAM128 modification:
stv0297.c (line ~395, kernel 2.6.15):

case QAM_128:
delay = 200;
sweeprate = 500;
break;

TechnoTrend
DVB-C 1.0 Budget

ca. 90 €
SAA7146AH: yes
VES1820: yes
Frontend (tuner): PHILIPS Vista VES1820-N70851.N1
Chipset (tuner to PCI bridge): PHILIPS SAA7146AH
TOP: antenna out
BOTTOM: antenna in
Fit in Asus Pundit (AB-P2600) slim barebone
Technotrend dvb-c budget 1.0.jpg
TechnoTrend
PCLine Premium DVB-C Rev. 2.1 (C2100)
[4]

ca. 200 € (C2100 discontinued, C2300 is the new model)

yes (C2100) Antenna in

Antenna out
Jumper2
Common Interface

Tt dvb-c 2.1.jpg
TechnoTrend
Premium DVB-C 2300 OT
[5]

(the newer version of C2100, adding SPDIF out and analog tuner)
ca. 100 €

partial,
C2100 much better supported
Antenna in

NO Antenna out
NO Jumper2(thus no RGB out)
Audio In
Audio Out
SPDIF Out
Video Composite Out Common Interface

Includes analog tuner - which is not supported in Linux,
128-QAM doesn't work properly in Linux

Identical to Hauppauge Nexus CA

Tt dvb-c 2.1.jpg
TerraTec
Cinergy 1200 DVB-C


ca. 80 € neu (zzgl. CI)

TDA10021: yes
TDA10023: patch exists
Philips SAA7146 + TDA1002x Antenna in

Antenna out
Common Interface

Support Desk says "NO Common Interface"!
Tt cinergy 1200 dvb-c pci.jpg
KNC1 TV-Station DVB-C English
TDA10021: yes
TDA10023: patch exists
Philips SAA7146 + TDA1002x (TDA10021 until Q4/2006, TDA10023 starting end of Q4/2006)

Tinbox CU1216L/ A I G H M (~2003 aka v.1.0): TDA10021HTB3, TAIFUN 6034 A1, LA7793 3BAE, LVC244A, EPCOS X6966D 8098 IRR2

Antenna in
Antenna Out
Common Interface

TwinHan
VisionDTV Mini Cab DVB-C


ca. 90 €
partial Philips
Conexant Fusion 878A (25878-13)
Antenna in Strong artifacts in picture


Currently Unsupported DVB-C PCI 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 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.