[linux-dvb] WT-200U stops responding after long idle time

Steven Haigh netwiz at crc.id.au
Tue Mar 14 04:53:09 CET 2006


Hi guys,

I've got one of the WT-200U USB hdtv tuners, and I've set up a few  
scripts to capture stuff - pretty much like a HDTV VCR. What I have  
found however is that over time, when a program starts to record, I  
get the following output:

zapdvb: Info: config file : /usr/local/share/zapdvb/zapdvb.conf
zapdvb: Info: process info: /root/.zapdvb_run
zapdvb: Info: channel file: /usr/local/share/zapdvb/config/dvb-t_au- 
melbourne.conf
zapdvb: Info: channel='7 Digital' frequency=177.5MHz video=769 audio=770
zapdvb: Info: using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/ 
adapter0/demux0'
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Info: status 20 | signal 0000 | snr ffff | ber 00000000 | unc  
00000000
zapdvb: Error: Could not tune to the selected channel or got no signal

This also appears in the dmesg:
dvb-usb: recv bulk message failed: -75
dvb-usb: recv bulk message failed: -75
dvb-usb: recv bulk message failed: -75
dvb-usb: recv bulk message failed: -75
dvb-usb: recv bulk message failed: -75

If I remove/reinsert the modules for the USB tuner, I get this:
usbcore: deregistering driver dvb_usb_dtt200u
dvb-usb: WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0 (WT-200U)  
successfully deinitialized and disconnected.
dvb-usb: found a 'WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0  
(WT-200U)' in warm state.
dvb-usb: will use the device's hardware PID filter (table count: 15).
DVB: registering new adapter (WideView/Yuan/Yakumo/Hama/Typhoon DVB-T  
USB2.0 (WT-200U)).
DVB: registering frontend 0 (WideView USB DVB-T)...
input: IR-receiver inside an USB DVB receiver as /class/input/input1
dvb-usb: schedule remote query interval to 300 msecs.
dvb-usb: WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0 (WT-200U)  
successfully initialized and connected.
usbcore: registered new driver dvb_usb_dtt200u
dvb-usb: recv bulk message failed: -110

So, it looks to me as if the hardware is locking up - or at least  
doing something strange somewhere in the dvb driver stack. Anybody  
got any insight into this?

--
Steven Haigh

Email: netwiz at crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9017 0597 - 0412 935 897





More information about the linux-dvb mailing list