USB DVB-S errors

[Steven Haigh]

As a followup, I've installed kernel-2.6.16-1.2236_FC6 from the devel stream.

When I just tune the card using tzap, all works fine, the card locks, and
I get the following:

# tzap "7 Digital"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 177500000 Hz
video pid 0x0301, audio pid 0x0302
status 1f | signal 4747 | snr ecec | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 4848 | snr ecec | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 4747 | snr ecec | ber 0000fb00 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 4747 | snr ecec | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
etc.

If I try tuning the DVB card via VLC, I get:
[00000288] main stream output debug: adding a new input
[00000295] main private debug: adding a new input
[00000295] mux_ts private debug: adding input codec=mpgv pid=69
[00000295] mux_ts private debug: new PCR PID is 69
[00000297] dvb access debug: frontend has acquired signal
[00000297] dvb access debug: frontend has acquired carrier
[00000297] dvb access debug: frontend has acquired stable FEC
[00000297] dvb access debug: frontend has acquired sync
[00000297] dvb access debug: frontend has acquired lock
[00000297] dvb access debug: - Bit error rate: 0
[00000297] dvb access debug: - Signal strength: 18247
[00000297] dvb access debug: - SNR: 60652

This seems to indicate that the comms with the card is fine, however MPEG
data isn't being streamed from the card as it should...

Using ZapDVB, I get:
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: Writing output to file: /home/captemp/2006-06-03 - test.mpg

Again, this would indicate that the tuner is correct tuned and locked,
however no data is received - a correctly working zapdvb output would have
the res of the stream, bitrate, audio quality (Khz/Kbps) and a few other
details. The file produced by zapdvb is 0 bytes - which is also consistent
with the card not sending it's bitstream...

I believe this is a kernel issue, as everything works perfectly with
kernel-2.6.15-1.2054_FC5.

In kernel-2.6.16-1.2236_FC6, dmesg shows this about the card:

# dmesg | grep dvb
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-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

Rebooting into kernel-2.6.15-1.2054_FC5, we see exactly the same:

# dmesg | grep dvb
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-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

Anyone have any ideas on this?

-- 
Steven Haigh

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