[linux-dvb] Tuning doesn't work with Wideview driver

[Benjamin Gillam]

Hi, I have a card with the same ID, mine is  Freecom one. I do not use mine as 
it screws up my system (keyboard stops working, other USB peripherals stop 
working, kernel oopses,...), however, I had similar tuning problems. I found 
that editing the initial tuning data worked. I think I adjusted all values by 
167k, and that seemed to make it work fine, so try adding or subtracting that 
value from the values in the initial file 
/usr/share/doc/dvb-utils/examples/scan/dvb-t/es-Alfabia (make a new file), and 
see if that helps.

Good luck,

Benjie.

Jesús Jiménez wrote:
> Hi
> 
> I recently purchased a Redbell TDT-2Go DVB-T USB stick, as it appeared as 
> Linux-compatible at linuxtv.org Wiki (Wideview driver, USB ID 14aa:0226). 
> I've compiled and installed the latest CVS version of the dvb v4l drivers, 
> and placed the right firmware into the right directory, and it gets loaded 
> successfully.
> 
> The problem is that, despite the stick is correctly recognized, tuning with 
> the scan utility fails miserably. The output is as follows:
> 
> scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/es-Alfabia
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 810000000 0 2 0 3 1 3 0
> initial transponder 834000000 0 2 0 3 1 3 0
> initial transponder 842000000 0 2 0 3 1 3 0
> initial transponder 850000000 0 2 0 3 1 3 0
> initial transponder 858000000 0 2 0 3 1 3 0
>>>> tune to: 
> 810000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>>>> tune to: 
> 810000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE 
> (tuning failed)
> WARNING: >>> tuning failed!!!
> (...some more lines...)
> ERROR: initial tuning failed
> dumping lists (0 services)
> Done.
> 
> 
> 
> I've tried with different kernel versions (Ubuntu Dapper 2.6.15, Ubuntu Edgy 
> 2.6.17), with the same results. I even downloaded a live-CD version of Ubuntu 
> Edgy in order to isolate from other possible problems, with no success.
> 
> Looking at system logs, the only strange things are some kind of -110 error, 
> and a udevd_event error, but the rest seems ok. Here's the dmesg output when 
> the stick is inserted:
> 
> 
> 
> kernel: [17179970.184000] usb 2-7: new high speed USB device using ehci_hcd 
> and address 8
> kernel: [17179970.316000] dvb-usb: found a 'WideView WT-220U PenType Receiver 
> (Typhoon/Freecom)' in cold state, will try to load a firmware
> kernel: [17179970.344000] dvb-usb: downloading firmware from 
> file 'dvb-usb-wt220u-fc03.fw'
> kernel: [17179971.960000] usb 2-7: USB disconnect, address 8
> : [17179971.960000] dvb-usb: generic DVB-USB module successfully deinitialized 
> and disconnected.
> kernel: [17179972.956000] usb 2-7: new high speed USB device using ehci_hcd 
> and address 9
> kernel: [17179973.088000] dvb-usb: found a 'WideView WT-220U PenType Receiver 
> (Typhoon/Freecom)' in warm state.
> kernel: [17179973.088000] dvb-usb: will use the device's hardware PID filter 
> (table count: 15).
> kernel: [17179973.088000] DVB: registering new adapter (WideView WT-220U 
> PenType Receiver (Typhoon/Freecom)).
> kernel: [17179973.088000] DVB: registering frontend 0 (WideView USB DVB-T)...
> kernel: [17179973.088000] input: IR-receiver inside an USB DVB receiver 
> as /class/input/input5
> kernel: [17179973.088000] dvb-usb: schedule remote query interval to 300 
> msecs.
> kernel: [17179973.088000] dvb-usb: WideView WT-220U PenType Receiver 
> (Typhoon/Freecom) successfully initialized and connected.
> kernel: [17179975.388000] dvb-usb: recv bulk message failed: -110
> udevd-event[6486]: wait_for_sysfs: waiting 
> for '/sys/devices/pci0000:00/0000:00:02.1/usb2/2-7/2-7:1.1/bus' failed
> kernel: [17179983.092000] drivers/usb/input/hid-core.c: timeout initializing 
> reports
> kernel: [17179983.092000]
> kernel: [17179983.092000] input: Digital TV Receiver Digital TV Receiver 
> as /class/input/input6
> kernel: [17179983.092000] input: USB HID v1.10 Keyboard [Digital TV Receiver 
> Digital TV Receiver] on usb-0000:00:02.1-7
> 
> 
> 
> Well, I don't know what to try next, I would thank any advice. The situation 
> is specially frustrating since I purchased this model because it was 
> explicitly stated as Linux-compatible, so I would thank any advice.
> 
> Thanks in advance