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

+

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

−

- dvb-usb.ko

+

dvb_usb_lmedm04 , depends: <br>

−

- dvb-usb-lmedm04.ko

+

usbcore,dvb-core,dvb_usb_v2,rc-core <br>

+

+tuners ( ts2020 + m88rs2000 / ...)

Usually sold on online auction sites from china as either DM04, latest on market's PCB/case stamps and retail package pictures indicate Manufacturer is Shenzhen Forward Video Co., Ltd., or QQBOX(not to be confused with QBOX).

Usually sold on online auction sites from china as either DM04, latest on market's PCB/case stamps and retail package pictures indicate Manufacturer is Shenzhen Forward Video Co., Ltd., or QQBOX(not to be confused with QBOX).

but zapping on the 2nd test host (ICH8 behind TTI hub) trigger'd the stalling issue, continuous debug messages of "m88rs2000_set_symbolrate" and the LOCK LED keeps stale ON after driver reset indicates the firmware/tuner has crashed due to tuner misprogramming on channel switching, needs USB replugging.

Revision as of 14:07, 24 August 2013

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!

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

Genpix Skywalker-1 USB

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.

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.

LME2510 DM04/QQBOX DVB-S USB 2.0

The following modules are necessary in order to get this device running:
dvb_usb_lmedm04 , depends:
usbcore,dvb-core,dvb_usb_v2,rc-core
+tuners ( ts2020 + m88rs2000 / ...)

Usually sold on online auction sites from china as either DM04, latest on market's PCB/case stamps and retail package pictures indicate Manufacturer is Shenzhen Forward Video Co., Ltd., or QQBOX(not to be confused with QBOX).
It contains a;
LME2510 or LME2510C usb bridge powered by the USB power.
DVB-S Tuner powered by the supplied external PSU.

The latest device will not work or be detected without the external PSU on and may crash Your kernel on unplug without USB unplug before.

M88RS2000 beta driver is now in media_build for kernel >= 3.2.48
Go to the How to Obtain, Build and Install V4L-DVB Device Drivers page and download and build the lastest media_build.
Firmware
We need to modify id of rs2000 firmware or it will warm boot id 3344:1120.
Date: 29 Jun 2010

Got a 30min full transponder recording of RTL (6 channels) without any USB (Intel ICH6 EHCI host behind TTI hub) halts/disconnect or tuner PLL or stream issues
but zapping on the 2nd test host (ICH8 behind TTI hub) trigger'd the stalling issue, continuous debug messages of "m88rs2000_set_symbolrate" and the LOCK LED keeps stale ON after driver reset indicates the firmware/tuner has crashed due to tuner misprogramming on channel switching, needs USB replugging.

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