Here is an (non-exhaustive) overview of DVB/ATSC USB devices sorted by their required LinuxTV driver (if supported - and yes - most of them are). Generally, when it comes to support for USB devices, it is a good idea to try the [http://linuxtv.org/repo/ current Hg sources] because some device drivers can be very new and thus may have not made their way into the mainstream kernel.

+

For information about supported USB devices, see the appropriate device category: <BR>

−

+

* [[ATSC USB Devices]]

−

Please help to keep this list up-to-date so that it is useful for everyone!

+

* [[DVB-C USB Devices]]

+

* [[DVB-S USB Devices]]

+

* [[DVB-S2 USB Devices]]

+

* [[DVB-T USB Devices]]

+

* [[DVB-T2 USB Devices]]

+

<BR>

__TOC__

__TOC__

+

==Introduction==

+

'''For all DVB USB devices you will need to load (if not compiled into the kernel):'''

+

* i2c-core

+

* crc32

+

* firmware_class

+

* dvb-core.ko

+

* dvb-pll.ko

+

and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.

−

==Introduction==

+

The ''Type'' field specifies the USB standard(s) supported by the device.

−

'''For all devices shown below you need to load (if not compiled into the kernel):'''

+

−

- i2c-core

+

−

- crc32

+

−

- firmware_class

+

−

- dvb-core.ko

+

−

- dvb-pll.ko

+

−

and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol"-message. Then take a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.

+

−

'''Legend:''' the field type specifies the real USB-standard of the device

+

; USB1.1

−

- '''USB1.1''': the device can be run on the USB1.1 and on the USB2.0 bus but only with USB1.1-speed.

+

: The device supports USB 1.1 only, and will work at 1.1 speeds when attached to a USB 2.0 port.

−

- '''USB2.0''': the device can only be connected to a real USB2.0 port and runs with USB2.0-speed.

+

; USB2.0

−

(delivering the complete [[TS|Transport Stream]] to the software demuxer.)

+

: The device supports USB 2.0 only, and will not work when attached to a USB 1.1-only port. Such devices are normally capable of delivering the complete [[TS|Transport Stream]] to the software demuxer.

−

- '''USB2.0/USB1.1''': the device is actually USB2.0, but can also be driven on a USB1.1 port. (if not

+

; USB2.0, USB1.1

−

mentioned elsewhere, these boxes can deliver the complete [[TS|Transport Stream]] when running in USB2.0 mode)

+

: The device supports USB 1.1 and USB 2.0, and will work at any speed supported by 1.1 or 2.0. When running in USB 2.0 mode, such devices can deliver the complete [[TS|Transport Stream]] (unless specified otherwise).

== Firmware ==

== Firmware ==

−

Most of the USB devices need a firmware to run. Some of the firmware files can be downloaded here: [http://www.linuxtv.org/downloads/firmware/] or here: [http://www.thadathil.net/dvb/fw/].

+

Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from [http://www.linuxtv.org/downloads/firmware/ here].

−

You need to copy the firmware to the correct place on your system. This will be /lib/firmware or a folder below it. Here is an example:

+

You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:

Remember that on some system the firmware is loaded by udev, so if for some reason the firmware is not loaded you may check that

+

udev is acutally running.

+

To check you could for example issue the command:

+

- $ ps -e | grep udev

+

+

If the output is empty, then you have to restart the udev daemon. For example in a Debian based system you may try with:

+

- $ sudo /etc/init.d/udev restart

+

+

then try again, removing and inserting the module again with modprobe.

+

+

== Additional Technical Information ==

This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.

This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.

−

=== DVB-USB devices host-controlled ===

+

=== Host Controlled DVB USB Devices ===

When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.

When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.

Line 56:

Line 72:

As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.

As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.

−

Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was [[I2C]]. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.

+

Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was [[I²C Protocol|I²C]]. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.

Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the [[BOM]]. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.

Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the [[BOM]]. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.

|comment=The tuner sensitivity is less than impressive. The driver has trouble scanning channel lists with Kaffeine. If you use a channel list made with another DVB-T device, watching the channels isn't really a big problem (a few blocks are shown though). This could be a timeout problem.

| comment=There are several clones of this device: some have the AN2235 USB controller instead of the AN2135; some use a Panasonic tuner instead of the default Thomson Cable tuner. Most of the Boxes have standard Cypress USB IDs which makes it very hard to identify them. A HOWTO for this devices can be found [[Artec T1 USB TV Box|here]].

+

−

| pic=[http://www.ultima-elec.nl/]

+

−

}}

+

−

{{DvbDevice

+

−

| device=VideoWalker DVB-T USB

+

−

| type=USB1.1

+

−

| fw=dvb-usb-dibusb-5.0.0.11.fw

+

−

| hw=[[DiB3000M-B|DiBcom 3000M-B]]

+

−

| pic=[http://www.geniusnet.com.tw/product/product-1.asp?pdtno=541]

+

−

}}

+

−

}}

+

−

+

−

==== [[DiB3000M-C/P]] USB2.0 DVB-T devices ====

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

- dib3000-common.ko

+

−

- dib3000mc.ko

+

−

- mt2060.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-dibusb-common.ko

+

−

- dvb-usb-dibusb-mc.ko

+

−

+

−

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:

+

−

- [[DiB3000M-C|DiBcom 3000M-C]]

+

−

- [[DiB3000P|DiBcom 3000P]]

+

−

+

−

&#91;FIXME: which for which devices?&#93;

+

−

+

−

These devices are clones of DVB-T USB2.0 reference designs made by [[DiBcom]]. MOD3000P1 (FX2), MOD3000P1.2 (FX2-LP) and STK3000P.

{{Note| Currently, at least two dib0700-based devices are known to have problems. The Nova-T 500 suffers from random disconnects after a few hours or days, and the Nova-T Stick, and possibly others using the same hardware, suffer from I2C errors. Updating to [http://linuxtv.org/hg/v4l-dvb current Hg drivers] and using [http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-03-pre1.fw new firmware] should cure these.}}

+

−

+

−

All devices below will be fully supported by the LinuxTV drivers very soon. The following modules are needed for these devices:

+

−

- dib7000m.ko

+

−

- dib7000p.ko

+

−

- dib3000mc.ko

+

−

- mt2060.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-dib0700.ko

+

−

+

−

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:

+

−

- DiBcom DiB7000P, DiBcom DiB7000PC

+

−

+

−

'''Comment:''' In case someone is opening the device, one can find the DiB7700-chips (B/C/D), which is demodulator and USB in one silicon. The USB firmware used is the same for all devices.

+

−

+

−

The dvb-usb-dib0700 module has a parameter which forces the activation of LNAs (Low Noise Amplifier). If you have reception problems you can try to load the module with force_lna_activation=1 and see if it works better. Normally the LNA is controlled automatically by software so, in general, there should be no need to force activation. If a device has an LNA, it is shown in the table below; for those which have no LNA, this parameter has no meaning.

| comment=There exists another device with the same design and name but different internals. Both are supported by linuxtv.org.

+

−

}}

+

−

}}

+

−

+

−

=== HanfTek UMT-010 ===

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

- mt352.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-dibusb-common.ko

+

−

- dvb-usb-umt-010.ko

+

−

+

−

The USB protocol which is used by this device is equal to the one used in DiBcom USB2.0 reference design. Thanks to Hanftek who especially wrote a firmware for easy Linux-Support.

+

−

+

−

{{DvbDeviceList

+

−

| content=

+

−

{{DvbDeviceCommented

+

−

| device=Hanftek UMT-010

+

−

| type=USB2.0

+

−

| fw=dvb-usb-umt-010-02.fw

+

−

| hw=[[Zarlink MT352]]

+

−

| comment=Stick-sized. Different colours (blue, grey, red).

+

−

| pic=[http://www.hanftek.com/]

+

−

}}

+

−

}}

+

−

+

−

=== Hauppauge WinTV-NOVA-T usb2 ===

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

- dib3000-common.ko

+

−

- dib3000mc.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-dibusb-common.ko

+

−

- dvb-usb-nova-t-usb2.ko

+

−

+

−

These devices are clones of a DVB-T USB2.0 reference design made by [[DiBcom]].

+

−

+

−

{{DvbDeviceList

+

−

| content=

+

−

{{DvbDeviceCommented

+

−

| device=Hauppauge WinTV NOVA-T USB2

+

−

| type=USB2.0, USB1.1

+

−

| fw=dvb-usb-nova-t-usb2-01.fw

+

−

| hw=[[DiB3000P|DiBcom 3000P]]

+

−

| comment=It has a MAC address.

+

−

| pic=[http://www.hauppauge.de/pages/products/data_novatusb2.html]

+

−

}}

+

−

}}

+

−

+

−

=== LifeView ===

+

−

+

−

Devices are starting to be supported.

+

−

+

−

See http://linuxtv.org/v4lwiki/index.php/LifeView

+

−

+

−

==== LifeView TV Walker Twin ====

+

−

+

−

Works well (two tuners).

+

−

+

−

The TV Walker twin contains a ULi M9206, which is, according to the website, a "versatile digital audio/video controller for various digital TV standards such as DVB and ATSC. M9206 supports Microsoft's latest Broadcast Driver Architecture (BDA), which offer customers design flexibility and broad market coverage to both DVB and ATSC standards." A pair of TDA10046A OFDM channel demodulators and TDA8275A Silicon Tuners provide the DVB-T functionality. There is also an IR receiver which is presumably controlled by the M9206. Note: this device's USB cable comes with 2 USB plugs. This is not one plug per tuner; plug in both of them together to supply adequate power to the device.

+

−

+

−

=== Nebula DigiTV USB version - DVB-T ===

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

- mt352.ko

+

−

- nxt6000.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-digitv.ko

+

−

+

−

{{DvbDeviceList

+

−

| content=

+

−

{{DvbDeviceCommented

+

−

| device=Nebula DigiTV USB

+

−

| type=USB2.0

+

−

| fw=dvb-usb-digitv-01.fw

+

−

| hw=[[Zarlink MT352]] or [[NXT6000|NxtWave Nxt6000]]

+

−

| comment=There is an SDK for download on the Nebula WebSite, which was used to improve the driver's quality. Was the first USB2.0 box on the market (late 2003/early 2004).

| comment='''It seems that some TwinhanDTV Alphas need newer firmware.''' The symptoms are that they can not find any channels. Consequently, they are unusable at the moment. See these posts for more details: [http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html][http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014226.html][http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015145.html][http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015222.html]

+

−

| pic=[http://www.twinhan.com/product_terrestrial_7.asp]

+

−

}}

+

−

{{DvbDevice

+

−

| device=TwinhanDTV MagicBoxII

+

−

| type=USB2.0

+

−

| fw=dvb-usb-vp7045-01.fw

+

−

| hw=[[Zarlink MT352]]

+

−

| pic=[http://www.twinhan.com/product_terrestrial_6.asp]

+

−

}}

+

−

}}

+

−

+

−

The programming of the MT352 is hidden behind the USB protocol defined within the firmware.

+

−

+

−

=== WideView/Yakumo/Hama/Typhoon/Yuan Boxes and Pens ===

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

- dvb-usb.ko

+

−

- dvb-usb-dtt200u.ko

+

−

+

−

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:

+

−

- [[Zarlink MT352]]

+

−

- The new units use the Zarlink ZL10353 instead of MT352

+

−

- for pentype design it is unknown (but it doesn't matter at all)

+

−

+

−

The programming of the MT352 is hidden behind the USB protocol defined within the firmware. These boxes can only deliver part of the [[TS|Transport Stream]] (using a hardware PID filter); it is not known how to deactivate this. (The driver was completely [[reverse-engineering|reverse-engineered]] without the help of its real vendor (assuming WideView is the manufacturer). '''UPDATE:''' the vendor was so kind to provide information about unknown commands, hence the driver is complete.

+

−

+

−

There is apparently another Yakumo model not covered:

+

−

+

−

<blockquote>Hi, I've purchased a "Yakumo Quickstick TV easy" and it doesn't work after compiling and installing the modules. Its vendor and product id ara 0x14aa and 0x620, and it does not appear in modules.usbmap. So I think it's not defined... ßingen.</blockquote>

+

−

+

−

'''Firmware:''' The firmware for the new rev Freecom sticks (dvb-usb-wt220u-fc03.fw) can be obtained from here [http://home.arcor.de/efocht/dvb-usb-wt220u-fc03.fw]

+

−

+

−

'''Warning:''' When checking the table below, check the USB ID to see if you have an old or new revision of the firmware.

Possibly has some frame-dropping issues? (See [http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015799.html], though works somehow despite the warning in [http://www.mail-archive.com/linux-dvb@linuxtv.org/msg23180.html] so maybe the first is just missing firmware file or something else.)

+

−

+

−

As a side note, the Techno-trend USB IR works [http://www.google.com/search?&q=technotrend+usb+ir+patch with patches] (support for ttusbir included in lirc 0.8.2pre3).

+

−

+

−

== DVB-S ==

+

−

+

−

=== SIEMSSEN & CO. - Opera S1 ===

+

−

+

−

A similar device to the DVBWorld. Seems to be sold in Germany by one of the well-known discounters. Its German distributor is [http://www.siemssen.de/ 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:

+

−

[http://www.dvb-device.com/ace42sc.htm]

+

−

[http://www.szforwardvideo.com/en/manager/product_read.asp?ID=96]

+

−

+

−

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.

+

−

+

−

A driver fully supporting this device is available in 2.6.22 and later kernels.

+

−

+

−

=== 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-ml|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.

+

−

+

−

{{DvbDeviceList

+

−

| content=

+

−

{{DvbDevice

+

−

| device=DigitalRise DVB-S USB Sat Starbox

+

−

| type=USB2.0, USB1.1

+

−

| fw=dvb-usb-vp702x-01.fw

+

−

| hw=[[DST]]

+

−

| pic=[http://www.digitalrise.biz/products/dtv-s7021/]

+

−

}}

+

−

{{DvbDevice

+

−

| device=TwinhanDTV StarBox

+

−

| type=USB2.0, USB1.1

+

−

| fw=dvb-usb-vp702x-01.fw

+

−

| hw=[[DST]]

+

−

| pic=[http://www.twinhan.com/product_satellite_5.asp]

+

−

}}

+

−

{{DvbDevice

+

−

| device=Typhoon DVB-S USB 2.0 Box

+

−

| type=USB2.0, USB1.1

+

−

| fw=dvb-usb-vp702x-01.fw

+

−

| hw=[[DST]]

+

−

| pic=[http://www.typhoon.de/de/art.php?p=822&c=]

+

−

}}

+

−

}}

+

−

+

−

=== Pinnacle PCTV 400e USB2.0 DVB-S ===

+

−

+

−

This driver is pre-Work-In-Progress. The following drivers are needed for these devices:

W3ird_N3rd says that "it is detected perfectly but it is not capable of locking onto any channel, 0 channels are found. My antenna is fine and the device does work on Windows, so somehow support for this device is broken. Don't buy it till it's fixed."

Hybrid devices have a DVB-demodulator and a analogue capturing chip. Normally they share a tuner.

+

−

+

−

=== Medion MD95700 (DVB-T) ===

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

+

−

- cx22702.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-cxusb.ko

+

−

+

−

The analogue part (handled by a Conexant CX25842) is not supported yet. The cx25840 driver from ivtv can be used to implement support.

+

−

+

−

{{DvbDeviceList

+

−

| content=

+

−

{{DvbDeviceCommented

+

−

| device=Medion MD 95700 4in1

+

−

| type=USB2.0

+

−

| hw=[[CX22702|Conexant CX22702]]

+

−

| comment=The box also has a X10 remote control. This is radio, not IR, and is supported by the atiremote driver. It also has a USB2.0 hub (Tetrahub) with one additional USB port. Both of them are working without mains power.

+

−

}}

+

−

}}

+

−

+

−

There is a new firmware, version 1.0.2.14, for the MD 95700 from Medion.

+

−

You can download it directly: [http://www1.medion.de/downloads/index.pl?op=detail&id=2804&type=treiber&lang=de] (in German). '''Please read the Readme''' before you flash the box.

+

−

+

−

This update fixes some video problems, but it is incompatible with the old dvb-usb drivers (i.e. kernels from 2005). If you use your box under Windows, don't forget to ensure that the Windows drivers are up to date too.

+

−

+

−

Suse 10.1 users might also want to see the distro-specific notes in the [[Medion MD95700 (DVB-T)]] article.

+

−

+

−

=== DViCO FusionHDTV USB ===

+

−

+

−

This class of usb devices is codenamed, Bluebird.

+

−

+

−

All devices below are fully supported by the LinuxTV driver. The following drivers are needed for these devices:

+

−

+

−

- lgdt330x.ko

+

−

- mt352.ko

+

−

- zl10353.ko

+

−

- dvb-usb.ko

+

−

- dvb-usb-cxusb.ko

+

−

+

−

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:

+

−

- [[LGDT3303|LG Electronics DT3303]]

+

−

- [[Zarlink MT352]]

+

−

- [[ZL10353|Zarlink ZL10353]]

+

−

+

−

+

−

{| width="900" border=1 cellpadding=2 cellspacing=0 valign="top"

+

−

|- bgcolor=#efefef valign="top"

+

−

! '''device/model'''

+

−

! '''type'''

+

−

! '''firmware name'''

+

−

! '''comments/quirks'''

+

−

! '''URL/pictures'''

+

−

|- align="left"

+

−

! DViCO FusionHDTV 5 USB Gold

+

−

! USB2.0

+

−

! dvb-usb-bluebird-01.fw

+

−

!

+

−

! [http://www.fusionhdtv.co.kr/eng/Products/HDTV5usb.aspx]

+

−

|- align="left"

+

−

! DViCO FusionHDTV USB DVB-T

+

−

! USB2.0

+

−

! dvb-usb-bluebird-01.fw

+

−

! There is a working Mac driver written by John Dalgliesh. http://www.defyne.org

+

−

! [http://www.fusionhdtv.co.kr/eng/Products/DVBTUSB.aspx]

+

−

|- align="left"

+

−

! DViCO FusionHDTV DVB-T Dual USB

+

−

! USB2.0

+

−

! dvb-usb-bluebird-01.fw

+

−

!

+

−

! [http://www.fusionhdtv.co.kr/ENG/Products/DualDigital.aspx]

+

−

|-

+

−

|}

+

−

+

−

== Work-In-Progress ==

+

−

+

−

=== [[Pinnacle PCTV 200e | Pinnacle PCTV 200e USB - DVB-T]] ===

+

−

+

−

This driver in beta stage, soon available for testing. Search this wiki for Pinnacle 200e. The following drivers are needed for these devices:

+

−

- dvb-usb.ko

+

−

- pctv200e.ko

+

−

+

−

These [[frontend|frontend(s)]]/[[demodulator|demodulator(s)]] can be found in various revisions of this device:

+

−

- [[Zarlink MT352]]

+

−

+

−

'''Comment:''' The driver is almost written. There is a version that has started to work, which we hope to release for testing soon. If you want to help to test the driver, or you want to help to develop the driver, please consult the [[linux-dvb-ml|linux-dvb Mailing list]].

The design of DVB-T E30 seems to be similar to the Twinhan Alpha Stick (same Tuner and Demod), but it doesn't work with the alpha-driver (vp7045) and firmware. Possibly some help from the new Opera DVB-S1 support, which also uses a Cypress CY7C68013 chip for USB microcontroller ([http://bttv-gallery.de/]) (just an idea)? dvb-usb-vp7045 reported to load at [http://www.linuxtv.org/pipermail/linux-dvb/2005-September/004592.html] (an old message).

+

−

+

−

Note: It has been reported that [http://anysee.com/ Anysee] has not been willing to help open source developers to write a Linux driver by handing out specifications. Any further information on communication with Anysee would be welcome.

+

−

+

−

=== Anysee E30 Plus DVB-C USB2 ===

+

−

+

−

Looks like support for DVB-C version should be added to cxusb, since from the photos it looks like Conexant USB 2.0 reference design (source: IRC logs). Has two firmware files, anyseeAUDB.ROM and anyseeAUDC.ROM, which are needed for analog video (cx2584x/MAKO) only.

+

−

+

−

The device hardware might be similar to those supported by dvb-usb-cxusb, but the firmware API is different.

* Now it doesn't exist in the Lifeview's page, not in discontinued products and not in External TV solutions, only a P Plus but i supuose that is different like the Q (now unsupported) and the Q PLus in External TV solutions. ¿Somebody can confirm this and also put info about the new product of lifeview if they're different?

There is a DVB-T-only box: [http://www.lifeview.com.tw/html/products/external_tv/tv_walker_dvbt.htm] I'm not able to find it in the discontinued products and correct the url to a new working one.

+

−

+

−

There is a DVB-T/Analogue box (with external power): [http://www.lifeview.com.tw/html/products/discontinued_products/tv_walker_studio_hybrid.htm]

+

−

+

−

Other dvb-t usb cards same as lifeview ones but different brand:

+

−

+

−

*Zaapa USB DVB-T Model: LR523 - (I can't find the lr523 in their web page) This one seems to be exactly the same LifeView TV Walker DVB-T Q LR506, lsusb also reveals (idVendor 0x10fd Anubis Electronics, Ltd) and the idProduct is 0x0513 I don't know if is the same id product that the LifeViews Q stick but is the same that the [[DVB_USB#LifeView_TV_Walker_Twin|Lifeview TV Walker Twin]] (this make an issue triying to make it work because the Walker Twin is different, the last two paragrafhs of this point explain this issue), anyone can post here the idProduct of lifeview's (if it's the same the issue of this stick will also apply to the Lifeview Q stick). I say this based on http://www.bandaancha.st/foros.php?temid=592815#633106 the post #44 says that in spanish, and also tell windows users with problems in channels reception, to use the driver and also the aplication from lifeview for the lr506, and seems that most of the users have their problems solved.

+

−

+

−

: In a kernel-2.6.22-gentoo-r1 with the firmware supplied by the ebuild linuxtv-dvb-firmware and DVB_CARD="tda10046lifeview" only, the usb is detected as a TV Walker Twin insted of a TV Walker DVB-T Q LR506 and the result is to fail triying to load the wrong firmware. This was with a similar to Q LR506 zaapa LR523 and also with the tda1004x module also in use by a saa7134_dvb, don't know if this can cause problems when i could load the correct firmware.

+

−

+

−

: Somebody can make mechanism to detect this card as is and not as a TV Walker Twin? This is caused by a similar vendor and product ids.

+

−

+

−

*In the zaapa web page I found one the ZT- LR 506Q http://www.zaapa.co.uk/Public/ficha_producto.asp?CPRO=636 this one have also the same name that the lifeview ones, the image of this tunner is the same that the zaapa LR523 except that the 523 have the anthena connector oposite to the usb side.

+

−

+

−

=== Pinnacle PCTV HD Pro Stick===

+

−

* USB2 stick. USB ID: 2304:0227.

+

−

* Device identifies itself as a "PCTV 800e".

+

−

* The USB stick consists of two boards: one with the USB and A/V connectors, the other with the RF connector. The two boards are joined(soldered) together with two 7 pin headers, one on each side of the board. I( [[User:Emeitner]] )am unwilling to unsolder the pins and risk damaging the

A [[hybrid]] USB2.0 box based on the [http://www.uli.com.tw/product_dm/m9207dm_web.pdf ULI M9207] chipset. Also based on this chipset is the Pinnacle [http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Analog_Digital+PVR/PCTV+310e PCTV 310e] and [http://www.nurido.at/news/computer/testgericomtvtunerusb20beihofer.html Gericom USB 2.0 Hybrid Box] sold by Aldi (Germany) and Hofer (Austria).

+

−

+

−

=== VBox DVB-S USB1.1 ===

+

−

+

−

Search the archive of the linux-dvb-mailing. A developer of VBox once mentioned that they have a Linux-driver. Maybe they are willing to provide information for a OpenSource-driver.

+

−

[http://www.vboxcomm.com/product1.htm#5]

−

=== WideView DVB-T/CATV USB2.0 Hybrid ===

+

== lsusb -t ==

−

[http://www.wv.com.tw/]

+

=== Wrong ===

+

With this setup you will have bandwidth problems with no appropriate warning whatsoever on any log file. Except that video will look horrible.

Contents

Introduction

For all DVB USB devices you will need to load (if not compiled into the kernel):

i2c-core

crc32

firmware_class

dvb-core.ko

dvb-pll.ko

and maybe others too. If the loading fails for any particular module you'll get a "unknown symbol" message. Then have a look at dmesg to find out, which symbols (functions) are missing. After you've found out which module was absent, please come back here and add it to the list/device-entry.

The Type field specifies the USB standard(s) supported by the device.

USB1.1

The device supports USB 1.1 only, and will work at 1.1 speeds when attached to a USB 2.0 port.

USB2.0

The device supports USB 2.0 only, and will not work when attached to a USB 1.1-only port. Such devices are normally capable of delivering the complete Transport Stream to the software demuxer.

USB2.0, USB1.1

The device supports USB 1.1 and USB 2.0, and will work at any speed supported by 1.1 or 2.0. When running in USB 2.0 mode, such devices can deliver the complete Transport Stream (unless specified otherwise).

Firmware

Most of the USB devices need firmware to run. Some of the firmware files can be downloaded from here.

You need to copy the firmware to the correct place on your system. This will normally be /lib/firmware or a folder below it. Here is an example:

Remember that on some system the firmware is loaded by udev, so if for some reason the firmware is not loaded you may check that
udev is acutally running.
To check you could for example issue the command:

- $ ps -e | grep udev

If the output is empty, then you have to restart the udev daemon. For example in a Debian based system you may try with:

- $ sudo /etc/init.d/udev restart

then try again, removing and inserting the module again with modprobe.

Additional Technical Information

This section starts describing devices which hit the market beginning of spring 2004. It does not cover TTUSB-based devices.

Host Controlled DVB USB Devices

When first AC-Adapter-free USB devices (with the capability of receiving DVB Signals) hit the market, every vendor was using the generic USB-device-controller from Cypress (FX1 (AN2135/AN2235), FX2) as an interface between the DVB-hardware and the host.

As those controllers are very generic, one has to create (and download) an (small or not so small) embedded software to those controller to give vendor-specific and the wanted functionality. After downloading the so-called firmware vendors used the reboot-feature of the controller to re-enumerate with new USB Vendor/Product-IDs and a new USB-layout. On the host this looks like a normal disconnect and connect of an USB device.

Because the memory for storing the firmware was limited, vendors decided not to put any DVB-demodulator and RF-tuner specific code into the firmware, but only to implement interface functionality. At that time, the common way to control other components was I²C. The other necessary feature was data-streaming. With such a firmware, every functionality is done from the host - mainly the driving of the demodulator and the tuner.

Firmware Controlled DVB USB Devices

Another approach was coming later: When it started, that putting more memory on a board/into an IC with almost no increase of the BOM. Vendors started to put the demodulator and tuner-driver into the firmware. This was simplifying the host-part dramatically, because if you have a new hardware, you just need to modify the (platform-independent) firmware part and, as long as the firmware-interface is not changing, the host-driver stays the same.