[linux-dvb] Hanftek UMT-010 DVB-T USB2.0 Stick with Kubuntu Edgy
Eft, Kernel 2.6.17-10-generic
richard2504 at gmx.net
Tue Nov 7 14:14:09 CET 2006
I am sorry in case you think I haven't been polite. My Name is Richard
and this post here (you could have recieved it some days before) is my
first one. So I will ask you to help me, if you can. Please read this
mail (again), because I added an important point.
Thursday last week I bought a DVD-Stick, named 'Hanftek UMT-010 DVB-T
USB2.0'. I installed it under Windows XP and I could recieve channels.
Now I wanted to make it run with my linux OS, Kubuntu Edgy Eft / Kernel
I cloned the last v4l-Directories from linuxtv.org and integrated the
modules into my sytem with 'make' and make 'install'
After that I rebooted my Laptop and stuck in my DVB-T-stick and with
'dmesg' I recieved:
Nov 2 21:27:51 sedna kernel: [4294854.693000] usb 3-1: new high speed
USB device using ehci_hcd and address 3
--> Nov 2 21:27:51 sedna kernel: [4294855.020000] dvb-usb: found a
'Hanftek UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware
Nov 2 21:27:51 sedna kernel: [4294855.099000] dvb_usb_umt_010: probe of
3-1:1.0 failed with error -22
Nov 2 21:27:51 sedna kernel: [4294855.099000] usbcore: registered new
Nov 2 21:30:46 sedna kernel: [4295030.075000] eth0: link up, 100Mbps,
full-duplex, lpa 0x45E1
Nov 2 21:30:46 sedna kernel: [4295030.076000] ADDRCONF(NETDEV_CHANGE):
eth0: link becomes ready
Nov 2 21:32:31 sedna kernel: [4295134.987000] usb 3-1: USB disconnect,
Ok, I should copy the 'dvb-usb-umt-010-02.fw' firmware file into
/lib/firmware. I loaded it from linuxtv.org again and copied it.
After reboot, I stuck in again my stick and dmesg displayed now:
Nov 2 21:34:21 sedna kernel: [4295244.943000] usb 3-1: new high speed
USB device using ehci_hcd and address 4
Nov 2 21:34:21 sedna kernel: [4295245.057000] dvb-usb: found a 'Hanftek
UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware
Nov 2 21:34:21 sedna kernel: [4295245.075000] dvb-usb: downloading
firmware from file 'dvb-usb-umt-010-02.fw'
Nov 2 21:34:22 sedna kernel: [4295245.237000] usb 3-1: USB disconnect,
Nov 2 21:34:22 sedna kernel: [4295245.237000] dvb-usb: generic DVB-USB
module successfully deinitialized and disconnected.
Nov 2 21:34:23 sedna kernel: [4295246.943000] usb 3-1: new high speed
USB device using ehci_hcd and address 5
Nov 2 21:34:23 sedna kernel: [4295247.058000] dvb-usb: found a 'Hanftek
UMT-010 DVB-T USB2.0' in warm state.
Nov 2 21:34:23 sedna kernel: [4295247.069000] dvb-usb: will pass the
complete MPEG2 transport stream to the software demuxer.
Nov 2 21:34:23 sedna kernel: [4295247.069000] DVB: registering new
adapter (Hanftek UMT-010 DVB-T USB2.0).
Everything seems to be loaded properly. But my LED is not burning! Some
dvb-t description websites expected it should burn. And though I have a
proper channel-table file (de-KoelnBonn) I cannot scan for stations.
The scan runs within 10 seconds (too fast!) without finding any station.
It's telling 'tuning failed' 6 times.
With another pc and a build-in pci-card (ttpci) the scan runs well.
In Kaffeine I find the device 'Zarlink MT352' but scanning is
unsuccessful here, too. What I can see, that there is no signal beeing
recieved while scanning.
I followed the advice to rename the usb-dibusb-22.214.171.124.fw file into
usb-umt-010-02.fw, copied it into /lib/firmware to load this firmware
file instead of the original one. The result is worse then before.
Do you have any idea? Can I use an original Windows firmware dll or sys
file from the OEM-cd and rename it into usb-umt-010-02.fw, or what can I
To point the problem: My LED doesn't begin to burn after sticking in.
With Windows the LED is burning, and with linux it should burn when
using the right dirmware file.
Maybe important for you:
Output of lsusb:
Bus 005 Device 003: ID 15f4:0015 HanfTek
Thank you in advance.
More information about the linux-dvb