[mythtv-users] compro dvbt-300 no luck with no lock

[Lewis]

Hi All,

I'm toying with a dvb-t300 that appears to be almost there...
I tried 2.6.17, but couldn't get the dvb-t300 nor the 0.7 series ivtv drivers,  for the --normally working well-- hauppage pvr-250mce, to work at all.   
Reverted to 2.6.16, no luck with the stock kernel drivers => installed v4l-dvb-a3a095225de1.  & 0.6.3 ivtv =>  looking better.....  but unable to get mythtv to successfully use the new dvbt-300 card.
I was unable to get anything out of the analogue or dvb of the dvbt-300, despite all devices being created as you'd like them to. 
I suspect tuner type issues may be at hand...?
Nothing from the analogue tuner which is listed in saa7134-cards.c as a TD1316; on the card is also a TDA9886TS that loads with a TDA9887 tuner.
After creating the relevant transports for AU and scanning in mythtv, no lock ony any channel, despite signal  strength >Import of channel info from zap did not assist still unable to get lock on dvb.
The correct tuner appears to be detected ... on card lists as a TDA10046A & dmesg shows TDA10046H frontend.  
Are there any module parameters to play with here for the tuner modules e.g. a PAL setting?
I've had a dig around the relevant c files but can't see anything obvious.

Better still,  can anyone tell me that they have a dvbt-300 behaving and what it took?
Cheers,
Lew
A bit more detail below for anyone interested in picking through the heap below in search of something to fit the picture together. 

relevant dmesg entries...
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7134[0]: found at 0000:02:07.0, rev: 1, irq: 201, latency: 32, mmio: 0xf500a000
saa7134[0]: subsystem: 185b:c900, board: Compro Videomate DVB-T300 [cardp,autodetected]
saa7134[0]: board init: gpio is 843f00
input: saa7134 IR (Compro Videomate DV as /class/input/input2
saa7134[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7134[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 87 ff ff ff ff
saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7134[0]: i2c eeprom 40: ff 02 00 c2 86 10 ff ff ff ff ff ff ff ff ff ff
saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
saa7134[0]: i2c eeprom 60: 34 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner 2-0061: chip found @ 0xc2 (saa7134[0])
tuner 2-0068: chip found @ 0xd0 (saa7134[0])
tda9887 2-0043: chip found @ 0x86 (saa7134[0])
saa7134[0]: registered device video0 [v4l2]
saa7134[0]: registered device vbi0
saa7134 OSS driver for DMA sound loaded
saa7134[0]: registered device dsp1
saa7134[0]: registered device mixer1
DVB: registering new adapter (saa7134[0]).
tda9887 2-0043: chip found @ 0x86 (saa7134[0])
tveeprom 3-0050: tuner model is Philips FM1216 ME MK3 (idx 57, type 3

tuner 2-0061: chip found @ 0xc2 (saa7134[0])
tuner 2-0061: type set to 67 (Philips TD1316 Hybrid Tuner)
tuner 2-0068: chip found @ 0xd0 (saa7134[0])

DVB: registering new adapter (saa7134[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...

tda9887 3-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 23 -- ok
tda9887 2-0043: chip found @ 0x86 (saa7134[0])
tda9887 3-0043: chip found @ 0x86 (ivtv i2c driver #0)

I'm a bit concerned about the duplication with the tda9887, wondering if the ivtv & std drivers play well together?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060703/e4349d83/attachment.htm