Are you sure that your /usr/share/dvb/dvb-t/uk-EmleyMoor is correct? I'm in Spain and tried using the default es-Seville file but it didn't work either. I think if the initial frequency isn't correct in the file then nothing will tune (?). In the end I ran the Windows application, did a scan of all the channels and wrote down the frequencies, etc. I then updated the es-Seville in Linux and it tuned OK. Regards, Stephen. On Wed, 2006-04-05 at 12:19 -0700, linux-dvb-request@xxxxxxxxxxx wrote: > Date: Wed, 5 Apr 2006 14:08:12 +0100 > From: Rob Andrews <rob@xxxxxxxxxxxxx> > Subject: Freecom DVB-T (new 14aa:022a/b model) not tuning. > To: linux-dvb@xxxxxxxxxxx > Message-ID: > <20060405130812.GA7956@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=us-ascii > > Hi, > > Following the recent threads about the new Freecom DVB-T with usb > vid:pid of 14aa:022a, I checked out the latest mercurial sources for > v4l-dvb and built and installed the driver. > > Device initialisation goes something like: > > usb 1-8: new high speed USB device using ehci_hcd and address 5 > usb 1-8: 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 1-8: USB disconnect, address 5 > dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. > usb 1-8: new high speed USB device using ehci_hcd and address 6 > usb 1-8: 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/input3 > 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 > > However, any attempt to tune the device is totally futile: > > $ dvbscan -v /usr/share/dvb/dvb-t/uk-EmleyMoor > scanning /usr/share/dvb/dvb-t/uk-EmleyMoor > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > initial transponder 673833330 0 3 3 1 0 0 0 > >>> tune to: > >>> 673833330:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > WARNING: >>> tuning failed!!! > >>> tune to: > >>> 673833330:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE > >>> (tuning failed) > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > >>> tuning status == 0x20 > WARNING: >>> tuning failed!!! > ERROR: initial tuning failed > dumping lists (0 services) > Done. > > The (orange whilst idle) LED *should* blink green when tuning, but it > doesn't blink at all. I did happen to get it to tune once on Sunday > afternoon, but it's not managed to repeat it since. Even with the > channels.conf I had generated from then, tzap just returns: > > status 00 | 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 | > [ad infinitum] > > Does anyone have any suggestions? > > For reference, the hardware is an Athlon 64 (using Linux x86_64, not i386) > with a VIA K8T890-southbridge USB chipset. The device is plugged > straight into the onboard USB, not through a hub. > > I can if needed try the stick on an 32-bit system with ICH5-integrated > USB controller. > > thanks, > rob _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
