Alan Secker wrote:

>I had a working Hauppauge PVR350 running in a machine with the following:
>Pentium 4-2.53Ghz, 1 Gb RAM, 120Gb disk
>ivtv-0.2.0-rc3j
>mythtv-0.18.1
>xmltv-0.5.40
>Mandriva LE2005
>
>The dmesg output is below:
>  
>
Looks like you are using the tveeprom from the kernel on the P4 machine 
and tveeprom from ivtv driver on the AMD64 machine. Which may explain 
your differences.

A better grep is:
dmesg | sed -n '/== START INIT IVTV ==/,/==  END INIT IVTV  ==/p'
then you get everything between the start and end lines.

Regards
Duncan

>[EMAIL PROTECTED] ~]$ dmesg|grep ivtv
>ivtv: ==================== START INIT IVTV ====================
>ivtv: version 0.2.0 (rc3j) loading
>ivtv: Linux version: 2.6.11-6-win4lin 686 gcc-3.4
>ivtv: In case of problems please include the debug info
>ivtv: between the START INIT IVTV and END INIT IVTV lines when
>ivtv: mailing the ivtv-devel mailinglist.
>ivtv: Autodetected WinTV PVR 250 card
>ivtv: Found an iTVC15 based chip
>ivtv: Unreasonably low latency timer, setting to 64 (was 32)
>ivtv: XXX PCI device: 0x0655 vendor: 0x1039
>ivtv: i2c attach [client=tveeprom[0],ok]
>ivtv: Tuner Type 1, Tuner formats 0x00000010, Radio: yes, Model 0x009d7451, 
>Revision 0x00000004
>ivtv: PAL tuner detected
>ivtv: Radio detected
>tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
>ivtv: i2c attach [client=(tuner unset),ok]
>saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
>ivtv: i2c attach [client=saa7115[0],ok]
>msp34xx: ivtv version
>ivtv: i2c attach [client=MSP3415G-B8,ok]
>ivtv: Encoder revision: 0x02010703
>ivtv: Decoder revision: 0x01120002
>ivtv: Configuring WinTV PVR 250 card with 5 streams
>ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
>ivtv: Registered v4l2 device, streamtype 0 minor 0
>ivtv: Create DMA stream 1
>ivtv: Registered v4l2 device, streamtype 1 minor 32
>ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
>ivtv: Registered v4l2 device, streamtype 2 minor 224
>ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
>ivtv: Registered v4l2 device, streamtype 3 minor 24
>ivtv: Create stream 4
>ivtv: Registered v4l2 device, streamtype 4 minor 64
>ivtv: Setting Tuner 1
>tuner: type set to 1 (Philips PAL_I (FI1246 and compatibles)) by ivtv i2c 
>driver #0
>ivtv: Setting audio matrix to input 3, output 1
>ivtv: Switching standard to PAL.
>ivtv: ivtv_enc_thread: pid = 4159, itv = 0xf8e707c0
>ivtv: Initialized WinTV PVR 250, card #0
>ivtv: ====================  END INIT IVTV  ====================
>ivtv: Setting audio matrix to input 1, output 1
>ivtv: Setting audio matrix to input 3, output 1
>[EMAIL PROTECTED] ~]$
>
>I moved it to a new machine:
>AMD Athlon 64-3700, 1Gb RAM 250Gb disk
>ivtv-0.4.2
>mythtv-0.19.0 (not yet working)
>xmltv-0.5.42  (not yet working)
>Mandriva 2006 
>
>The output of dmesg is as below.
>I spotted advice to another user with a similar configuration suggesting that
>the SAA7115 on his board was broken. Well after moving my card back and forth
>betwwen the two machines, I don't think it is. Something else is screwing up
>the results. My card does have an SAA7115 but I cannot see an SAA7127. Perhaps
>it mascarades as something else. Because I have problems getting mythtv and
>xmltv to work, I cannot be sure whether or not ivtv in its present state is
>contributing to thed problem or not. Any idea anyone?
>
>Notice the change from PVR-250 to PVR-350 detected by the two ivtv vewrsions.
>
>
>ivtv:  ==================== START INIT IVTV ====================
>ivtv:  version 0.4.2 (tagged release) loading
>ivtv:  Linux version: 2.6.12-12.mm.1mdkcustom preempt 586 gcc-4.0
>ivtv:  In case of problems please include the debug info between
>ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
>ivtv:  any module options, when mailing the ivtv-users mailinglist.
>ivtv0: User specified WinTV PVR 350 card (detected cx23415 based chip)
>ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
>tveeprom: ivtv version
>ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
>tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
>ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
>ivtv0 warning: i2c client addr: 0x21 not found for command 0x8004646b!
>msp3400 0-0040: ivtv driver
>ivtv0: i2c attach to card #0 ok [client=MSP3415G-B8, addr=40]
>ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
>ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
>ivtv0: Encoder revision: 0x02050032
>ivtv0: Decoder revision: 0x02020023
>ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
>ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
>ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
>ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
>ivtv0: Create encoder radio stream
>ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total)
>ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total)
>ivtv0: Create decoder VOUT stream
>ivtv0: Allocate DMA decoder YUV stream: 20 x 51840 buffers (1024KB total)
>ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
>tuner: type set to 1 (Philips PAL_I (FI1246 and compatibles)) by ivtv i2c 
>driver #0
>ivtv0 warning: i2c client addr: 0x21 not found for command 0x40085618!
>ivtv0 warning: i2c client addr: 0x21 not found for command 0xc0045627!
>ivtv0 warning: i2c client addr: 0x21 not found for command 0x40085618!
>ivtv0 warning: i2c client addr: 0x44 not found for command 0x40085618!
>ivtv0 warning: i2c client addr: 0x21 not found for command 0x40045613!
>ivtv0 warning: i2c client addr: 0x21 not found for command 0x40045612!
>ivtv0: Initialized WinTV PVR 350, card #0
>ivtv:  ====================  END INIT IVTV  ====================
>[EMAIL PROTECTED] ~]$
>
>
>
>
>
>_______________________________________________
>ivtv-devel mailing list
>[email protected]
>http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>  
>


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

Reply via email to