[linux-dvb] Re: AverTV DVB-T not working under Kernel 2.6.6

[Martin Kenny <marty@kennymoy.com.au>]

Hi Mike,

FWIW, I have the same card, here in Adelaide, (it's about 9 months old). 
I just did an experiment -- I unplugged my antenna, and got output from 
tzap that looked pretty close to yours (both the signal and snr fields 
were displaying ffff, and the ber and unc fields were jumping backwards 
and forwards similarly).
I'm using kernel 2.6.6-rc1.

Cheers,
Marty.

Mike Harris wrote:

> Hi,
>
> I've just bought a new AverTV DVB-T card. I configured & compiled Kernel
> 2.6.6 appropriately. The modules seem to go in OK & recognize the card &
> the firmware is downloaded OK. However, scan reports tuning errors and
> if I try to use tzap with a channels.conf file for my area (Melbourne,
> Aus) it never locks.
>
> dmesg output:
>
> Linux video capture interface: v1.00
> bttv: driver version 0.9.14 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> bttv: Host bridge needs ETBF enabled.
> bttv: Bt8xx card found (0).
> PCI: Found IRQ 9 for device 0000:00:0a.0
> PCI: Sharing IRQ 9 with 0000:00:0a.1
> bttv0: Bt878 (rev 17) at 0000:00:0a.0, irq: 9, latency: 64, mmio:
> 0xe7dfe000
> bttv0: subsystem: 1461:0761 (UNKNOWN)
> please mail id, board name and the correct card= insmod option to
> kraxel@bytesex.org
> bttv0: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected]
> bttv0: enabling ETBF (430FX/VP3 compatibilty)
> bttv0: gpio: en=00000000, out=00000000 in=0095009d [init]
> bttv0: using tuner=-1
> bttv0: i2c: checking for MSP34xx @ 0x80... not found
> bttv0: i2c: checking for TDA9875 @ 0xb0... not found
> bttv0: i2c: checking for TDA7432 @ 0x8a... not found
> bttv0: registered device video0
> bttv0: registered device vbi0
> bt878: AUDIO driver version 0.0.0 loaded
> bt878: Bt878 AUDIO function found (0).
> PCI: Found IRQ 9 for device 0000:00:0a.1
> PCI: Sharing IRQ 9 with 0000:00:0a.0
> bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 9, latency: 64, memory:
> 0xe7dff000
> attach: checking "bt878 #0 [sw]"
> find by pci: checking "bt878 #0 [sw]"
> attach: "bt878 #0 [sw]", to card 0
> DVB: registering new adapter (Ave).
> DVB: registering frontend 0:0 (Microtune MT7202DTF)...
> i2c_adapter i2c-0: sendbytes: error - bailout.
> sp887x_initial_setup: firmware upload... done.
>
> scan output:
>
> scanning dvb-t/au-Melbourne
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 226500000 1 3 0 3 1 1 0
> initial transponder 177500000 1 2 0 3 1 2 0
> initial transponder 191625000 1 3 0 3 1 1 0
> initial transponder 219500000 1 3 0 3 1 1 0
> initial transponder 536625000 1 2 0 3 1 2 0
>  
> > > > tune to:
> > > >        
> 226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed)
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed)
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed)
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed)
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
>  
> > > > tune to:
> > > >        
> 536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed)
> WARNING: >>> tuning failed!!!
> ERROR: initial tuning failed
> dumping lists (0 services)
> Done.
>
> tzap output:
> root ~/build/dvb-apps/util/szap # ./tzap -c
> channels-conf/dvb-t/au-Melbourne "Nine Digital"
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file 'channels-conf/dvb-t/au-Melbourne'
> tuning to 191625000 Hz
> video pid 0x0207, audio pid 0x02d0
> status 01 | signal ffff | snr 6b16 | ber 00003639 | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber 00003639 | unc ffffffff |
> status 01 | signal ffff | snr ffff | ber 00003639 | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber 00003639 | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber 0000363f | unc ffffffff |
> status 01 | signal ffff | snr ffff | ber 00003639 | unc ffffffff |
> status 01 | signal ffff | snr ffff | ber 0000363f | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber ffffffff | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber 0000363f | unc 00000000 |
> status 01 | signal ffff | snr ffff | ber 00003639 | unc 00000000 |
> ...etc
>
> I guess a signal level & snr of ffff are suspicious? Come to think of it
> the ber & unc don't look valid either.
>
> Any ideas? Dud card maybe? I don't have a win32 box to try it out on. Or
> maybe the HW has changed?
>
> Regards // Mike
>
>
>
>
>
>
>