Hi, yesterday I got this thing and now I'm trying to make it work somehow. http://www.pcstore.de/storeshop/artikeldet.php?proid=5518 It has a red and a green LED inside and an infrared remote control receiver, I haven't opened it yet. lsusb says: Bus 005 Device 002: ID 15f4:0001 HanfTek HanfTek UMT-010 USB2.0 DVB-T (cold) after loading the Hanftek firmware: Bus 005 Device 004: ID 15f4:0015 HanfTek Jul 10 19:29:59 piccolo kernel: dvb_usb_umt_010 5-1:1.0: usb_probe_interface - got id Jul 10 19:29:59 piccolo kernel: dvb-usb: found a 'Hanftek UMT-010 DVB- T USB2.0' in warm state. Jul 10 19:29:59 piccolo kernel: dvb-usb: will pass the complete MPEG2 transport stream to the demuxer. Jul 10 19:29:59 piccolo kernel: DVB: registering new adapter (Hanftek UMT-010 DVB-T USB2.0). Jul 10 19:29:59 piccolo kernel: DVB: registering frontend 0 (Zarlink MT352 DVB-T)... Jul 10 19:29:59 piccolo kernel: dvb-usb: Hanftek UMT-010 DVB-T USB2.0 successfully initialized and connected. The device seems to be accessible somehow, if I do a "scan file" with file being a file with some frequencies in it, the red LED will be lit and it seems to scan - but it never finds anything. So I got a channels.conf from a friend and tried: georg@piccolo:~$ sudo tzap -r RTL using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 538000000 Hz video pid 0x01b1, audio pid 0x01b2 status 00 | signal ffb7 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal ff00 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal ff00 | snr 0000 | ber 00000000 | unc 00000000 | status 00 | signal ff00 | snr 0000 | ber 00000000 | unc 00000000 | I then booted Windows and tried the Windows driver for the HanfTek UMT-010: Same effect, seems to work, but no channel will be found, but the red LED is lit. The next step was to run the original software from the included CD (which looks very similar to the Hanftek software) and then warm boot into linux. Now lsusb says: Bus 005 Device 002: ID 10b9:2000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x10b9 idProduct 0x2000 bcdDevice 0.01 iManufacturer 1 iProduct 2 USB DVB-T iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 450mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0178 1x 376 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 Is it worth opening the device and see which chips are in there (and no longer being able to give it back)? Or has anyone already done that? How are the chances then to make it work, given that the Hanftek Firmware doesn't seem to work correctly? Should I perhaps try to patch the dvb driver to make it accept the new USB ID? Can it work at all with the Windows firmware, i.e. is the protocol the firmware and the driver "talk" standardized? Georg
