Hello Hans,

Thanks for your reply.

> Can you give me the ivtv initialization messages from your kernel log? 
> I'm particularly interested in the tuner that you have.

Certainly.  I've grepped for 'ivtv' in my kernel log.  Hopefully those
are the only interesting lines:

2008-02-12_01:03:01.89848 kern.info: ivtv:  ==================== START INIT 
IVTV ====================
2008-02-12_01:03:01.89848 kern.info: ivtv:  version 1.0.0 (2.6.22 preempt 
mod_unload K7 ) loading
2008-02-12_01:03:01.89862 kern.info: ivtv0: Autodetected Hauppauge card 
(cx23415 based)
2008-02-12_01:03:01.89863 kern.info: ivtv0: Unreasonably low latency timer, 
setting to 64 (was 32)
2008-02-12_01:03:01.89869 kern.info: ivtv0: loaded v4l-cx2341x-enc.fw firmware 
(376836 bytes)
2008-02-12_01:03:01.89869 kern.info: ivtv0: loaded v4l-cx2341x-dec.fw firmware 
(262144 bytes)
2008-02-12_01:03:01.89870 kern.info: ivtv0: Encoder revision: 0x02060039
2008-02-12_01:03:01.89871 kern.info: ivtv0: Decoder revision: 0x02020023
2008-02-12_01:03:01.89871 kern.warn: ir-kbd-i2c: i2c IR (Hauppauge) detected at 
i2c-2/2-0018/ir0 [ivtv i2c driver #0]
2008-02-12_01:03:01.89873 kern.info: msp3400 2-0040: MSP4448G-A2 found @ 0x80 
(ivtv i2c driver #0)
2008-02-12_01:03:01.89875 kern.info: tuner 2-0043: chip found @ 0x86 (ivtv i2c 
driver #0)
2008-02-12_01:03:01.89876 kern.info: tuner 2-0061: chip found @ 0xc2 (ivtv i2c 
driver #0)
2008-02-12_01:03:01.89877 kern.info: ivtv0: Autodetected Hauppauge WinTV PVR-350
2008-02-12_01:03:01.89877 kern.info: ivtv0: No tuner detected, default to NTSC-M
2008-02-12_01:03:01.89877 kern.info: saa7115 2-0021: saa7115 found 
(1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
2008-02-12_01:03:01.89878 kern.info: saa7127 2-0044: saa7127 found @ 0x88 (ivtv 
i2c driver #0)
2008-02-12_01:03:01.89879 kern.info: ivtv0: Registered device video0 for 
encoder MPEG (4 MB)
2008-02-12_01:03:01.89879 kern.info: ivtv0: Registered device video32 for 
encoder YUV (2 MB)
2008-02-12_01:03:01.89880 kern.info: ivtv0: Registered device vbi0 for encoder 
VBI (1 MB)
2008-02-12_01:03:01.89881 kern.info: ivtv0: Registered device video24 for 
encoder PCM audio (1 MB)
2008-02-12_01:03:01.89881 kern.info: ivtv0: Registered device radio0 for 
encoder radio
2008-02-12_01:03:01.89882 kern.info: ivtv0: Registered device video16 for 
decoder MPEG (1 MB)
2008-02-12_01:03:01.89882 kern.info: ivtv0: Registered device vbi8 for decoder 
VBI (1 MB)
2008-02-12_01:03:01.89882 kern.info: ivtv0: Registered device vbi16 for decoder 
VOUT
2008-02-12_01:03:01.89883 kern.info: ivtv0: Registered device video48 for 
decoder YUV (1 MB)
2008-02-12_01:03:01.89883 kern.info: ivtv0: loaded v4l-cx2341x-init.mpg 
firmware (155648 bytes)
2008-02-12_01:03:01.89884 kern.info: ivtv0: Initialized Hauppauge WinTV 
PVR-350, card #0
2008-02-12_01:03:01.89884 kern.info: ivtv:  ====================  END INIT IVTV 
 ====================


Also, here's some lspci output.  Not sure if it's useful, but might as well 
include it:

lspci -vv -s 01:06.0
01:06.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 
Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc. WinTV PVR-350
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2
                      Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                             Status: D0 PME-Enable- DSel=0 DScale=0 PME-
                             Kernel driver in use: ivtv
                             Kernel modules: ivtv


If I have some more time, I can try to take a tally of which channels work and 
which don't.  
I'm sure I could probably whip out a quick shell script for such a task.

thanks again,
tim

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to