Leadtek WinFast DTV2000DS: Difference between revisions
mNo edit summary |
(This is to make the record straight for this card.) |
||
Line 113: | Line 113: | ||
==Making it work== |
==Making it work== |
||
Mythbuntu 10.04 plus latest V4L-DVB drivers as per [http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers] |
Mythbuntu 10.04 plus latest V4L-DVB drivers as per [http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers] |
||
NOTE: This card has not been working in 10.10, in fact it is not working in 10.04 either. |
|||
There are some reports of people making it work by switching to different kernels, different driver, different firmware, etc, |
|||
but as far as working is concerned this does not constitute a stable state. |
|||
There are no consistent reports of this card working under any kernel, so unless an accurate HOWTO with detailed and exact versions are performed, this card can be regarded as "unstable". |
|||
===Remote Control Support=== |
===Remote Control Support=== |
Revision as of 10:47, 14 November 2010
A dual tuner DVB-T PCI card from Leadtek.
Currently supported by recent V4L-DVB (as at Sep 2010).
Overview/Features
Formats:
- DVB-T
Inputs:
- RF
- Infrared
Components Used
Contains
- NXP TDA18211
Identification
Output of lsusb -v:
Bus 002 Device 002: ID 0413:6a04 Leadtek Research, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6a04 bcdDevice 2.00 iManufacturer 1 Afatech iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered)
Making it work
Mythbuntu 10.04 plus latest V4L-DVB drivers as per [1]
NOTE: This card has not been working in 10.10, in fact it is not working in 10.04 either. There are some reports of people making it work by switching to different kernels, different driver, different firmware, etc, but as far as working is concerned this does not constitute a stable state.
There are no consistent reports of this card working under any kernel, so unless an accurate HOWTO with detailed and exact versions are performed, this card can be regarded as "unstable".
Remote Control Support
I (Gregoryo) have had no success with the remote, but there is hope from dmesg:
[ 22.263721] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0e.0/0000:02:0a.2/usb2/2-1/input/input5
user@host:~$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=0413 Product=6a04 Version=0200
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:02:0a.2-1/ir0
S: Sysfs=/devices/pci0000:00/0000:00:0e.0/0000:02:0a.2/usb2/2-1/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=108fc310 2802891 0 0 0 0 118000 200180 4803 e1680 0 100000 ffe
So I've been using /dev/input/event5 in my tests. I have tried using evtest, mode2, and irw to no avail. I get no indication of any signal coming from the remote. Am I missing a kernel driver module?