DVB-S USB Devices: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
Line 228: Line 228:
* [[Turbosight]] [[Turbosight USB DVB-S Q-Box|USB DVB-S Q-Box]]
* [[Turbosight]] [[Turbosight USB DVB-S Q-Box|USB DVB-S Q-Box]]
* [[VBox]] [[VBox DVB-S USB1.1|DVB-S USB1.1]] ... [http://www.vboxcomm.com/product1.htm#5 link]
* [[VBox]] [[VBox DVB-S USB1.1|DVB-S USB1.1]] ... [http://www.vboxcomm.com/product1.htm#5 link]
* [[Geniatech]] [[Geniatech Satbox|Satbox]] ... [http://www.geniatech.com/pa/satbox.asp link]


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

Revision as of 00:14, 4 September 2011

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



Note: Some of the following information is from the old deprecated DVB USB page. Eventually this page will become organized, but for now, you'll have to bear the mess....or, even better, help in cleaning it up.


Supported DVB-S USB Devices

The following table lists the confirmed working DVB-S USB devices 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).


Manufacturer
Model number
Supports Tuner / Chips Connections fw Others Pictures
DVBWorld
DVBWorld 2102 USB
kernel2.6.23 sharp0194A/CY7C68013A dvb-usb-dw2102.fw [1]
Hauppauge
DEC3000-S USB
[2]
Hauppauge
WinTV-NOVA-S USB
TechniSat
SkyStar USB / Sky2PC USB



Genpix Skywalker-1 USB

The SkyWalker-1 is a standalone USB 2.0 DVB-s card.

Resources


SIEMSSEN & CO. - Opera S1

A driver fully supporting this device is available in 2.6.22 and later kernels. It currently doesn't work on PowerPC (endianess problems).

A similar device to the DVBWorld, either identical or a modified OEM version. Seems to be sold in Germany by one of the well-known discounters. Its German distributor is Siemssen under the name Opera DVB-S1. The card contains a Cypress CY7C68013A-56PCX to manage the USB part, which seems to control a Xilinx Spartan(R) XC3850 FPGA. The tuner box reads Sharp, but I cannot find out more about it.

I'm able to upload the firmware to turn the device from cold mode to warm USB ID but programming the FPGA still fails. For my card/driver: The cold USB ID is: VID 0x04b4 (CYPRESS) PID: 0x2830 The warm USB ID is: VID 0x695C (???????) PID: 0x3829

DVB-S cards in similar cases can be found on different Asian sites: [3] [4]

Despite the fact that all those devices look quite similar and have similar hardware, Siemssen still claims that they are built completely differently and their drivers are not interchangeable.

TwinhanDTV StarBox II - DVB-S (7021A)

The following modules are necessary in order to get this device running:

 - dvb-usb.ko
 - dvb-usb-vp702x.ko

The driver is still a little work-in-progress. If you want to help the development, please consult the linux-dvb Mailing list. The front-end part of the DST driver could be rewritten to be used by the USB driver. Currently it is hard-wired to the PCI cards.

Device / Model Type Hardware Firmware URL / Pictures
Comments & quirks
DigitalRise DVB-S USB Sat Starbox USB2.0, USB1.1 DST dvb-usb-vp702x-01.fw [5]
TwinhanDTV StarBox USB2.0, USB1.1 DST dvb-usb-vp702x-01.fw [6]
Typhoon DVB-S USB 2.0 Box USB2.0, USB1.1 DST dvb-usb-vp702x-01.fw [7]

If not working with firmware dvb-usb-vp702x-01.fw try dvb-usb-vp702x-02.fw. http://www.gamesrant.com/linuxjunk_pics/dvb-usb-vp702x-02.fw

Pinnacle PCTV (e.g. 400e, 450e) - DVB-S (TDA8263 + TDA10086)

The following modules are necessary in order to get this device running:

 - dvb-usb.ko
 - ttusb2.ko

(Please update with your experiences - I have added this card because its support is listed in the source tree)

Device / Model Type Hardware Firmware URL / Pictures
Comments & quirks
Pinnacle PCTV 400e USB2.0 DST dvb-usb-pctv-400e-01.fw [8]
Pinnacle PCTV Sat Pro USB (450e) USB2.0 DST dvb-usb-pctv-400e-01.fw [9]


TechnoTrend / Satelco USB - DVB-S

The following modules are necessary in order to get these devices running:

 - dvb-usb.ko
 - ttusb2.ko
note: do not connect any other usb device to the same usb hub - this causes system freeze 
Device / Model Type Hardware Firmware URL / Pictures
Comments & quirks
Technotrend TT-connect S-2400 USB2.0 DST dvb-usb-tt-s2400-01.fw [10]
Satelco EasyWatch USB USB2.0 DST dvb-usb-tt-s2400-01.fw [11]


GENPIX 8pks/qpsk/DCII USB2.0 - DVB-S

The following modules are necessary in order to get this device running:

 - dvb-usb.ko
 - gp8psk.ko

(Please update with your experiences - I have added this card because its support is listed in the source tree)

Device / Model Type Hardware Firmware URL / Pictures
Comments & quirks
Genpix 8PSK-to-USB2 Rev.1 DVB-S receiver USB2.0 DST dvb-usb-gp8psk-01.fw [12]
Genpix 8PSK-to-USB2 Rev.2 DVB-S receiver USB2.0 DST dvb-usb-gp8psk-01.fw [13]
Genpix SkyWalker-1 DVB-S receiver USB2.0 DST dvb-usb-gp8psk-01.fw [14]
Genpix SkyWalker-CW3K DVB-S receiver USB2.0 DST dvb-usb-gp8psk-01.fw [15]


Currently Unsupported DVB-S 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