[mythtv-users] Ideas to diagnose one faulty DVB-T adapter (on a dual adapter USB stick)

John Pilkington J.Pilk at tesco.net
Tue Oct 30 18:12:31 UTC 2012


On 30/10/12 17:19, Dan Gravell wrote:
> I first set up my MythTV backend a few months ago. I got it all working with one WinTV Duet stick. Both adapters were working at this stage; I could record two channels at once.
>
> Now I've come back to it and it seems like the first adapter does not work. I guess Myth defaults to the first as I cannot get a lock in Live TV and recordings all fail.
>
> Any ideas to diagnose why one of the tuners on my WinTV Duet works and the other doesn't? Scanning the second adapter brings back channels, e.g:
>
> sudo scan /usr/share/dvb/dvb-t/uk-CrystalPalace -a 1 -o zap
>
> But scanning the first finds nothing but gives lots of 'WARNING: filter timeout pid 0x0000' messages:
>
> gravelld at bordeaux:~$ sudo scan /usr/share/dvb/dvb-t/uk-CrystalPalace -o zap
> scanning /usr/share/dvb/dvb-t/uk-CrystalPalace
>
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 506000000 0 3 9 3 1 0 0
> initial transponder 482000000 0 3 9 3 1 0 0
> initial transponder 490000000 0 2 9 3 1 0 0
> initial transponder 514000000 0 2 9 3 1 0 0
> initial transponder 529833000 0 3 9 3 1 0 0
>>>> tune to: 506000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
>>>> tune to: 482000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
>>>> tune to: 490000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
> [and so on...]
>
> Dan

Why not use the tools in MythTV?  If you know you should use Crystal 
Palace it ought to be easy - unless, of course, there *is* something 
wrong, or Myth won't recognise the device.  There have been lots of 
posts about this sort of thing.  Here' a recent one that should get you 
going in a few minutes.

http://www.gossamer-threads.com/lists/mythtv/users/531976#531976

HTH

John P





More information about the mythtv-users mailing list