[linux-dvb] Tuner not detected on second Kworld card

David Engel david at istwok.net
Thu Oct 11 20:46:32 CEST 2007


Hi,

I have a MythTV backend with two Kworld ATSC 115 and two Hauppage PVR
x50 cards.  I've been using the Kworld cards for digital capture for
some time now without problem.  I'd like to now use them for analog
capture too and am having a problem.

The first detected card seems to work fine except for one minor thing
I'll address separately below.  The second detected card doesn't work
and only captures all black video or noise.  In looking at my logs, I
think there is a problem detecting the tuner on the second card.

Oct 11 12:34:21 tux kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
Oct 11 12:34:21 tux kernel: saa7133[0]: found at 0000:02:04.0, rev: 209, irq: 21, latency: 32, mmio: 0xf1009000
Oct 11 12:34:21 tux kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110 [card=90,insmod option]
Oct 11 12:34:21 tux kernel: saa7133[0]: board init: gpio is 100
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: tuner 1-0061: chip found @ 0xc2 (saa7133[0])
Oct 11 12:34:21 tux kernel: saa7133[0]: registered device video2 [v4l2]
Oct 11 12:34:21 tux kernel: saa7133[0]: registered device vbi2
Oct 11 12:34:21 tux kernel: saa7133[1]: found at 0000:02:09.0, rev: 209, irq: 17, latency: 32, mmio: 0xf100a000
Oct 11 12:34:21 tux kernel: saa7133[1]: subsystem: 17de:7352, board: Kworld ATSC110 [card=90,insmod option]
Oct 11 12:34:21 tux kernel: saa7133[1]: board init: gpio is 100
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 11 12:34:21 tux kernel: saa7133[1]: registered device video3 [v4l2]
Oct 11 12:34:21 tux kernel: saa7133[1]: registered device vbi3
Oct 11 12:34:21 tux kernel: DVB: registering new adapter (saa7133[0]).
Oct 11 12:34:21 tux kernel: DVB: registering new adapter (saa7133[1]).
Oct 11 12:34:21 tux kernel: saa7134 ALSA driver for DMA sound loaded
Oct 11 12:34:21 tux kernel: saa7133[0]/alsa: saa7133[0] at 0xf1009000 irq 21 registered as card 2
Oct 11 12:34:21 tux kernel: saa7133[1]/alsa: saa7133[1] at 0xf100a000 irq 17 registered as card 3

Notice the absence of an equivalent "tuner 1-0061: chip found" line
for saa7133[1].  This occurs with both the 2.6.21 and 2.6.22.*
kernels.  I briefly tested analog and digital capture on both cards in
a separate system before installing them in the MythTV backend so I
don't suspect a hardware problem.

Not being able to tune could explain not being able to to an analog
capture.  Could this be another case of probing being done by the
various drivers causing problems?  If so, has any of it been fixed in
the recently released 2.6.23 kernel?  I've already had to go back to
the 2.6.21 series on this system because the probing caused a minor
problem with the Hauppauge cards.

The minor problem I mentioned earlier has to do with using the
saa7134-alsa module to capture sound directly from the card.  A quick
glance at the driver source code looks like it shold support 32 and 48
kHz sampling rates.  I've only been able to get 32 kHz working well so
far with MythTV.  Trying 48 kHz results in some sort of rate mismatch.
Is 48 kHz supposed to work?

David
-- 
David Engel
david at istwok.net



More information about the linux-dvb mailing list