Since there has been no response to this issue, should I be filing  
this as a bug report?

What is the best kernel/ivtv combination to go back to? I just tried  
compiling 0.4.0 under 2.6.15-gentoo-r5 kernel and it failed pretty  
early on in msp3400. I understand that ivtv is a bit of a mess at the  
moment due to the rework of the API to go into the linux kernel and  
it is a shame that this transition has been pretty poorly handled.  
There doesn't appear to be anywhere where the stable releases are  
documented while these changes are happening. Can anyone suggest the  
best approach?

Ari Maniatis


Begin forwarded message:

> From: Aristedes Maniatis <[EMAIL PROTECTED]>
> Date: 22 February 2006 9:07:58 AM
> To: [email protected]
> Subject: 0.4.2/0.4.3 problem with PVR250 card
>
> I posted this to the ivtv-user list with no response, so I  
> understand this is the place of next resort.
>
> A system with two perfectly working cards (one PVR 150 and one PVR  
> 250) under 0.4.0 does not work after an upgrade to 0.4.2. A more  
> recent upgrade to 0.4.3 did not help.
>
> The cards:
>
> 00:09.0 Multimedia video controller: Internext Compression Inc  
> iTVC15 MPEG-2 Encoder (rev 01)
>         Subsystem: Hauppauge computer works Inc. WinTV PVR-250
>         Flags: bus master, medium devsel, latency 64, IRQ 18
>         Memory at dc000000 (32-bit, prefetchable) [size=64M]
>         Capabilities: [44] Power Management version 2
>
> 00:0b.0 Multimedia video controller: Internext Compression Inc  
> iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
>         Subsystem: Hauppauge computer works Inc. WinTV PVR 150
>         Flags: bus master, medium devsel, latency 64, IRQ 17
>         Memory at e0000000 (32-bit, prefetchable) [size=64M]
>         Capabilities: [44] Power Management version 2
>
> The system:
>
> Linux tv 2.6.15-gentoo-r5 #2 Sun Feb 12 22:37:48 EST 2006 i686 Intel 
> (R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
>
>
> The error (from dmesg):
>
> msp3400 0-0040: I/O error #1 (write 0x12/0x03)
> msp3400 0-0040: I/O error #2 (write 0x12/0x03)
> msp3400 0-0040: I/O error #3 (write 0x12/0x03)
> msp3400 0-0040: giving up, reseting chip. Sound will go off, sorry  
> folks :-|
> msp3400 0-0040: chip reset failed
>
> The above is repeated dozens of times withi dmesg. Unfortunately it  
> overflows the dmesg buffer and so I don't get the top of it. At the  
> end I get:
>
> ivtv0: Initialized WinTV PVR 250, card #0
>
>
> The second card (the PVR 150) initialises and works fine. The PVR  
> 250 card does not work at all, sound or video.
>
> If, after boot, I remove and modprobe the ivtv driver, I get some  
> different errors:
>
> Feb 20 16:13:42 tv ivtv:  ==================== START INIT IVTV  
> ====================
> Feb 20 16:13:42 tv ivtv:  version 0.4.3 (tagged release) loading
> Feb 20 16:13:42 tv ivtv:  Linux version: 2.6.15-gentoo-r5 PENTIUM4  
> gcc-3.3
> Feb 20 16:13:42 tv ivtv:  In case of problems please include the  
> debug info between
> Feb 20 16:13:42 tv ivtv:  the START INIT IVTV and END INIT IVTV  
> lines, along with
> Feb 20 16:13:42 tv ivtv:  any module options, when mailing the ivtv- 
> users mailinglist.
> Feb 20 16:13:42 tv ivtv0: Autodetected WinTV PVR 250 card (cx23415  
> based)
> Feb 20 16:13:42 tv ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17  
> (level, low) -> IRQ 18
> Feb 20 16:13:42 tv ivtv0: i2c attach to card #0 ok  
> [client=tveeprom, addr=50]
> Feb 20 16:13:42 tv tveeprom 0-0050: Hauppauge model 48014, rev  
> F408, serial# 5194951
> Feb 20 16:13:42 tv tveeprom 0-0050: tuner model is Philips FI1216  
> MK2 (idx 8, type 5)
> Feb 20 16:13:42 tv tveeprom 0-0050: TV standards PAL(B/G) (eeprom  
> 0x04)
> Feb 20 16:13:42 tv tveeprom 0-0050: audio processor is MSP3415 (idx 6)
> Feb 20 16:13:42 tv tveeprom 0-0050: has radio
> Feb 20 16:13:43 tv tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver  
> #0)
> Feb 20 16:13:43 tv ivtv0: i2c attach to card #0 ok [client=(tuner  
> unset), addr=61]
> Feb 20 16:13:43 tv saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c  
> driver #0)
> Feb 20 16:13:43 tv ivtv0: i2c attach to card #0 ok [client=saa7115,  
> addr=21]
> Feb 20 16:13:43 tv ivtv0: loaded v4l-cx2341x-enc.fw firmware  
> (262144 bytes)
> Feb 20 16:13:44 tv ivtv0: loaded v4l-cx2341x-dec.fw firmware  
> (262144 bytes)
> Feb 20 16:13:44 tv ivtv0: Encoder revision: 0x02050032
> Feb 20 16:13:44 tv ivtv0: Decoder revision: 0x02020023
> Feb 20 16:13:44 tv ivtv0: Allocate DMA encoder MPEG stream: 128 x  
> 32768 buffers (4096KB total)
> Feb 20 16:13:44 tv ivtv0: Allocate DMA encoder YUV stream: 161 x  
> 12960 buffers (2048KB total)
> Feb 20 16:13:44 tv ivtv0: Allocate DMA encoder VBI stream: 80 x  
> 26208 buffers (2048KB total)
> Feb 20 16:13:44 tv ivtv0: Allocate DMA encoder PCM audio stream:  
> 455 x 4608 buffers (2048KB total)
> Feb 20 16:13:44 tv ivtv0: Create encoder radio stream
> Feb 20 16:13:44 tv tuner 0-0061: type set to 5 (Philips PAL_BG  
> (FI1216 and compatibles))
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x40086d11!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x80287610!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x40287611!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x40085618!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x80287610!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x40287611!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x402c5639!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x80287610!
> Feb 20 16:13:44 tv ivtv0 warning: i2c client addr: 0x40 not found  
> for command 0x40287611!
> Feb 20 16:13:44 tv ivtv0: Initialized WinTV PVR 250, card #0
>
>
> Remember, all this worked perfectly before the upgrade of ivtv  
> (which was required by my upgrade of the kernel). I've read all the  
> howtos and troubleshooting guides but nothing that seems to address  
> this problem. The problematic card does not appear to work even  
> when installed all by itself, do it doesn't appear to be  
> interaction between the two cards causing the problem. ivtv was  
> installed with the gentoo portage system which in itself avoids  
> many common problems.
>
> Any clues or next troubleshooting steps?
>
> Ari Maniatis
>
>
>
>
> -------------------------->
> ish
> http://www.ish.com.au
> Level 1, 30 Wilson Street Newtown 2042 Australia
> phone +61 2 9550 5001   fax +61 2 9550 4001
> PGP fingerprint 08 57 20 4B 80 69 59 E2  A9 BF 2D 48 C2 20 0C C8
>
>
>




-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
PGP fingerprint 08 57 20 4B 80 69 59 E2  A9 BF 2D 48 C2 20 0C C8



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

Reply via email to