[linux-dvb] Freecom DVB-T USB stick - no signal

Simon Blandford simon at bkinfo.net
Mon Apr 17 20:41:57 CEST 2006


I have a Freecom DVB-T USB stick with the new vendor/product IDs of 
0x14aa:0x022a.

I have downloaded and installed the current v4l-dvb drivers and now it 
lights up. When I press the number buttons on its remote control the 
numbers appear in a console as if I typed them using a the keyboard 
which is interesting.

Problem: I can't seem to get any signal. I live in NW London and so I am 
using the UK Crystal Palace channels.conf file. I have plugged the unit 
into an outdoor UHF TV aerial which is known to provide good analogue TV 
signals. Crystal Palace is a major transmitter with about 1MW ERP on 
it's analogue services and 20KW on DVB.

Here is the output from tzap...

    [simon at simon ~]$ tzap "BBC NEWS 24"
    using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
    reading channels from file '/home/simon/.tzap/channels.conf'
    tuning to 505833333 Hz
    video pid 0x0280, audio pid 0x0281
    status 20 | signal ffff | snr ffff | ber 00000000 | unc 00000000 |
    status 20 | signal ffff | snr ffff | ber 00000000 | unc 00000000 |
    status 20 | signal ffff | snr ffff | ber 00000000 | unc 00000000 |
    status 20 | signal ffff | snr ffff | ber 00000000 | unc 00000000 |


Notice the unfeasible signal strength. When I scan Crystal Palace on 
Kaffeine it momentarily shows 100% signal and 100% s/n but finds nothing.

    If I try test_av from the dvb-apps I get...
    [simon at simon test]$ ./test_av
    using video device '/dev/dvb/adapter0/video0'
    using audio device '/dev/dvb/adapter0/audio0'
    enter command or h + enter for help
    open video device: No such file or directory

If I look in /dev/dvb/adapter0 I get...

    [simon at simon test]$ ls /dev/dvb/adapter0/
    demux0     dvr0       frontend0  net0

Not sure which one of those should equate to video0 and audio0. Maybe 
that is where the problem lies?

Below is some more diagnostic info.
Any help much appreciated.
Regards.

    [root at simon ~]# lsusb
    Bus 002 Device 005: ID 14aa:022b AVerMedia (again) or C&E
    Bus 002 Device 003: ID 046d:c00e Logitech, Inc. Optical Mouse
    Bus 002 Device 002: ID 0424:2504 Standard Microsystems Corp.
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 001: ID 0000:0000



    dmesg output
    usb 2-4.3: new high speed USB device using ehci_hcd and address 4
    usb 2-4.3: configuration #1 chosen from 1 choice
    dvb-usb: found a 'WideView WT-220U PenType Receiver (based on
    ZL353)' in cold state, will try to load a firmware
    dvb-usb: downloading firmware from file 'dvb-usb-wt220u-zl0353-01.fw'
    usbcore: registered new driver dvb_usb_dtt200u
    usb 2-4.3: USB disconnect, address 4
    dvb-usb: generic DVB-USB module successfully deinitialized and
    disconnected.
    usb 2-4.3: new high speed USB device using ehci_hcd and address 5
    usb 2-4.3: configuration #1 chosen from 1 choice
    dvb-usb: found a 'WideView WT-220U PenType Receiver (based on
    ZL353)' in warm state.
    dvb-usb: will use the device's hardware PID filter (table count: 15).
    DVB: registering new adapter (WideView WT-220U PenType Receiver
    (based on ZL353)).
    DVB: registering frontend 0 (WideView USB DVB-T)...
    input: IR-receiver inside an USB DVB receiver as /class/input/input2
    dvb-usb: schedule remote query interval to 300 msecs.
    dvb-usb: WideView WT-220U PenType Receiver (based on ZL353)
    successfully initialized and connected.
    dvb-usb: recv bulk message failed: -110









More information about the linux-dvb mailing list