You are not logged in.

#1 2011-05-30 13:36:13

cdwijs
Member
Registered: 2010-04-24
Posts: 295

TerraTec Cinergy T Stick RC: af9013: invalid bw or clock

Hi All,
I have just bought a TerraTec Cinergy T Stick RC. I plugged it in, and I got the following message on dmesg stating I did not have the firmware:

[19130.318157] usb 1-1: new high speed USB device using ehci_hcd and address 2
[19130.450587] input: NEWMI USB2.0 DVB-T TV Stick as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.1/input/input13
[19130.450754] generic-usb 0003:0CCD:0097.0003: input,hidraw2: USB HID v1.01 Keyboard [NEWMI USB2.0 DVB-T TV Stick] on usb-0000:00:1a.7-1/input1
[19131.042455] IR NEC protocol handler initialized
[19131.050086] IR RC5(x) protocol handler initialized
[19131.061841] IR RC6 protocol handler initialized
[19131.073625] IR JVC protocol handler initialized
[19131.077512] IR Sony protocol handler initialized
[19131.082037] lirc_dev: IR Remote Control driver registered, major 250 
[19131.090817] IR LIRC bridge handler initialized
[19131.415770] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in cold state, will try to load a firmware
[19131.460019] dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
[19131.460036] dvb_usb_af9015: probe of 1-1:1.0 failed with error -2
[19131.460264] usbcore: registered new interface driver dvb_usb_af9015

I installed the firmware from aur:
https://aur.archlinux.org/packages.php?ID=45814
Now the DVB stick is recognized:

[19410.824861] usb 1-1: new high speed USB device using ehci_hcd and address 3
[19411.316798] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in cold state, will try to load a firmware
[19411.319288] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[19411.386420] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in warm state.
[19411.386511] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[19411.386826] DVB: registering new adapter (TerraTec Cinergy T Stick RC)
[19411.467285] af9013: firmware version:4.95.0.0
[19411.471785] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
[19411.504281] tda18218: NXP TDA18218HN successfully identified.
[19411.506164] Registered IR keymap rc-empty
[19411.506330] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/rc/rc0/input14
[19411.506456] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/rc/rc0
[19411.506460] dvb-usb: schedule remote query interval to 500 msecs.
[19411.506463] dvb-usb: TerraTec Cinergy T Stick RC successfully initialized and connected.
[19411.518258] input: NEWMI USB2.0 DVB-T TV Stick as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.1/input/input15
[19411.518486] generic-usb 0003:0CCD:0097.0004: input,hidraw2: USB HID v1.01 Keyboard [NEWMI USB2.0 DVB-T TV Stick] on usb-0000:00:1a.7-1/input1

When Using tzap, I saw no signal, and mplayer could not open the device:

cedric@laptop:/dev/dvb/adapter0$ tzap -r  'Nederland 1'
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/cedric/.tzap/channels.conf'
tuning to 474000000 Hz
video pid 0x1b63, audio pid 0x1b64
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
$ mplayer /dev/dvb/adapter0/dvr0
MPlayer SVN-r33159-4.5.2 (C) 2000-2011 MPlayer Team
162 audio & 359 video codecs
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /dev/dvb/adapter0/dvr0.
.... and then nothing...

When I disconnect the receiver, I get the following in dmesg:

[20571.290046] usb 1-1: USB disconnect, address 3
[20760.444635] INFO: task khubd:834 blocked for more than 120 seconds.
[20760.444638] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[20760.444641] khubd           D f1f8bb60     0   834      2 0x00000000
[20760.444647]  f44d3dfc 00000046 f5002280 f1f8bb60 f44d3d80 00000282 c11a38d5 c123e512
[20760.444654]  c11a38d5 00000282 f1f83424 c144a9a0 f1f8bb60 f6206380 c14c4380 f4b4c000
[20760.444661]  f4b4c1c4 a1eaceea 000012b5 c14c4380 f6206380 f4b4c000 f4b00000 f44d3dc8
[20760.444667] Call Trace:
[20760.444676]  [<c11a38d5>] ? kobject_release+0x45/0x80
[20760.444681]  [<c123e512>] ? device_release+0x22/0x80
[20760.444684]  [<c11a38d5>] ? kobject_release+0x45/0x80
[20760.444688]  [<c11a37bd>] ? kobject_put+0x1d/0x50
[20760.444692]  [<c123e3cf>] ? put_device+0xf/0x20
[20760.444700]  [<f80d9645>] ? dvb_unregister_device+0x65/0x70 [dvb_core]
[20760.444704]  [<c1061203>] ? prepare_to_wait+0x43/0x70
[20760.444710]  [<f80d9c0d>] dvb_dmxdev_release+0x9d/0xf0 [dvb_core]
[20760.444713]  [<c10613a0>] ? autoremove_wake_function+0x0/0x40
[20760.444718]  [<f8091208>] dvb_usb_adapter_dvb_exit+0x38/0x60 [dvb_usb]
[20760.444722]  [<f809042d>] dvb_usb_exit+0x3d/0xa0 [dvb_usb]
[20760.444727]  [<f80904cd>] dvb_usb_device_exit+0x3d/0x60 [dvb_usb]
[20760.444731]  [<f80fb056>] af9015_usb_device_exit+0x46/0x50 [dvb_usb_af9015]
[20760.444750]  [<f890ec67>] usb_unbind_interface+0x37/0x140 [usbcore]
[20760.444755]  [<c1241a4c>] __device_release_driver+0x4c/0xa0
[20760.444758]  [<c1241abf>] device_release_driver+0x1f/0x30
[20760.444762]  [<c1241645>] bus_remove_device+0x55/0x80
[20760.444766]  [<c123f240>] device_del+0x100/0x170
[20760.444776]  [<f890ce13>] usb_disable_device+0x63/0x110 [usbcore]
[20760.444784]  [<f8906b36>] usb_disconnect+0x76/0xf0 [usbcore]
[20760.444792]  [<f89083b4>] hub_thread+0x7c4/0xe80 [usbcore]
[20760.444797]  [<c103540a>] ? check_preempt_curr+0x6a/0x80
[20760.444802]  [<c10613a0>] ? autoremove_wake_function+0x0/0x40
[20760.444806]  [<c1030389>] ? complete+0x49/0x60
[20760.444815]  [<f8907bf0>] ? hub_thread+0x0/0xe80 [usbcore]
[20760.444818]  [<c1060d08>] kthread+0x68/0x70
[20760.444821]  [<c1060ca0>] ? kthread+0x0/0x70
[20760.444826]  [<c1003d7e>] kernel_thread_helper+0x6/0x18

$ uname -a
Linux laptop 2.6.38-ARCH #1 SMP PREEMPT Fri May 13 07:54:18 UTC 2011 i686 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux

I will try again after a pacman -Suy.

Best regards,
Cedric

Offline

#2 2011-05-30 13:59:21

cdwijs
Member
Registered: 2010-04-24
Posts: 295

Re: TerraTec Cinergy T Stick RC: af9013: invalid bw or clock

I have done the update, and there's no change:

cedric@laptop:~$ tzap -r 'Nederland 1'
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/cedric/.tzap/channels.conf'
tuning to 474000000 Hz
video pid 0x1b63, audio pid 0x1b64
status 03 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 | 
status 03 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 
status 03 | signal 0000 | snr 0078 | ber 00000000 | unc 00000000 | 

$ uname -a
Linux laptop 2.6.38-ARCH #1 SMP PREEMPT Mon May 23 20:04:02 UTC 2011 i686 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux

Is there something I can do about this, or should I return the unit?

Best regards,
Cedric

Offline

Board footer

Powered by FluxBB