LinHES Forums
http://forums.linhes.org/

Perfect picture - no sound (msp3400 problem)
http://forums.linhes.org/viewtopic.php?f=1&t=1069		 Page 1 of 1
Author:  DrHoneydew1975 [ Fri Mar 26, 2004 4:10 pm ]
Post subject:  Perfect picture - no sound (msp3400 problem)
Ok, first of all - I'm no expert at this. Have made an auto install of R4V2. Live in Sweden so after some manual configuration of channels I got the tuning working. The picture quality is really good but I get no sound what so ever!

I'v checked the alsamixer and I don't think there any problems there.

During boot I get serveral error messages concerning the msp34xx module. A pice of the syslog follows:

Mar 26 22:22:08 mythtv kernel: i2c-core.o: i2c core module
Mar 26 22:22:08 mythtv kernel: i2c-algo-bit.o: i2c bit algorithm module
Mar 26 22:22:08 mythtv kernel: i2c-core.o: driver i2c TV tuner driver registered.
Mar 26 22:22:08 mythtv kernel: i2c-core.o: driver saa7115 registered.
Mar 26 22:22:08 mythtv kernel: i2c-core.o: driver i2c msp3400 driver registered.
Mar 26 22:22:08 mythtv kernel: ivtv: version 0.1.9 (release) loading
Mar 26 22:22:08 mythtv kernel: ivtv: SGarray_size = 340, DSGarray_size = 16
Mar 26 22:22:08 mythtv kernel: ivtv: Found an iTVC15 based chip
Mar 26 22:22:08 mythtv kernel: PCI: Enabling device 00:0f.0 (0014 -> 0016)
Mar 26 22:22:08 mythtv kernel: PCI: Assigned IRQ 9 for device 00:0f.0
Mar 26 22:22:08 mythtv kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32)
Mar 26 22:22:08 mythtv kernel: tuner: probing ivtv i2c driver #0 i2c adapter [id=0x10005]
Mar 26 22:22:08 mythtv kernel: tuner: chip found @ 0xc2
Mar 26 22:22:08 mythtv kernel: tuner(bttv): type forced to 5 (Philips PAL_BG (FI1216 and compatibles)) [insmod]
Mar 26 22:22:08 mythtv kernel: i2c-core.o: client [Philips PAL_BG (FI1216 and compa] registered to adapter [ivtv i2c driver #0](pos. 0).
Mar 26 22:22:08 mythtv kernel: saa7114.c: starting probe for adapter ivtv i2c driver #0 (0x10005)
Mar 26 22:22:08 mythtv kernel: saa7114.c: detecting saa7114 client on address 0x42
Mar 26 22:22:08 mythtv kernel: saa7115.c: writing init values
Mar 26 22:22:10 mythtv kernel: status: (1E) 0x50, (1F) 0xc0
Mar 26 22:22:10 mythtv kernel: i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos. 1).
Mar 26 22:22:10 mythtv kernel: msp34xx: init: chip=MSP3415D-B3, has NICAM support
Mar 26 22:22:10 mythtv kernel: msp3410: daemon started
Mar 26 22:22:10 mythtv kernel: i2c-core.o: client [MSP3415D-B3] registered to adapter [ivtv i2c driver #0](pos. 2).
Mar 26 22:22:10 mythtv kernel: i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #1 (read 0x10/0x200)
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #2 (read 0x10/0x200)
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #3 (read 0x10/0x200)
Mar 26 22:22:12 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:12 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x08)
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x08)
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x08)
Mar 26 22:22:12 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:12 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x09)
Mar 26 22:22:12 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x09)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x09)
Mar 26 22:22:13 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:13 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x0a)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x0a)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x0a)
Mar 26 22:22:13 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:13 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x0b)
Mar 26 22:22:13 mythtv kernel: ivtv: Encoder revision: 0x02040011
Mar 26 22:22:13 mythtv kernel: ivtv: Decoder revision: 0x02020023
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x13)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x0b)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x13)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x0b)
Mar 26 22:22:13 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x13)
Mar 26 22:22:13 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:13 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:13 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:13 mythtv kernel: msp3400: chip reset failed
Mar 26 22:22:13 mythtv kernel: ivtv: Registered v4l2 device, minor 0
Mar 26 22:22:13 mythtv kernel: ivtv: Registered v4l2 device, minor 32
Mar 26 22:22:13 mythtv kernel: ivtv: Registered v4l2 device, minor 224
Mar 26 22:22:13 mythtv kernel: ivtv: loaded
Mar 26 22:22:13 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
Mar 26 22:22:13 mythtv kernel: bttv: driver version 0.7.104 loaded
Mar 26 22:22:13 mythtv kernel: bttv: using 4 buffers with 2080k (8320k total) for capture
Mar 26 22:22:13 mythtv kernel: bttv: Host bridge is VIA Technologies, Inc. VT8367 [KT266]
Mar 26 22:22:13 mythtv insmod: /lib/modules/2.4.21-xfs/kernel/drivers/media/video/bttv.o: init_module: No such device
Mar 26 22:22:13 mythtv insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Mar 26 22:22:13 mythtv insmod: /lib/modules/2.4.21-xfs/kernel/drivers/media/video/bttv.o: insmod bttv failed
Mar 26 22:22:13 mythtv modprobe: modprobe: Can't locate module rivatv
Mar 26 22:22:14 mythtv kernel: i2c-core.o: driver i2c ir driver registered.
Mar 26 22:22:14 mythtv kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
Mar 26 22:22:14 mythtv kernel: i2c-core.o: client [Hauppauge IR] registered to adapter [ivtv i2c driver #0](pos. 3).
Mar 26 22:22:14 mythtv kernel: lirc_dev: lirc_register_plugin:sample_rate: 10
Mar 26 22:22:14 mythtv insmod: Warning: ignoring debug=1, no such parameter in this module
Mar 26 22:22:14 mythtv insmod: Warning: ignoring ivtv=pal, no such parameter in this module
Mar 26 22:22:14 mythtv insmod: Module ivtv loaded, with warnings
Mar 26 22:22:14 mythtv insmod: Module lirc_dev loaded, with warnings
Mar 26 22:22:14 mythtv insmod: Module lirc_i2c loaded, with warnings
Mar 26 22:22:14 mythtv kernel: msp34xx: I/O error #1 (write 0x12/0x00)
Mar 26 22:22:14 mythtv kernel: msp34xx: I/O error #2 (write 0x12/0x00)
Mar 26 22:22:14 mythtv kernel: msp34xx: I/O error #3 (write 0x12/0x00)
Mar 26 22:22:14 mythtv kernel: msp34xx: giving up, reseting chip. Sound will go off, sorry folks :-|
Mar 26 22:22:14 mythtv kernel: msp3400: chip reset failed

What's the problem with the msp3400 module?

Any ideas? Please... need help! :(
Author:  Xsecrets [ Fri Mar 26, 2004 10:59 pm ]
Post subject: 
I've never heard of the msp3400 driver what is your hardware?
Author:  DrHoneydew1975 [ Sat Mar 27, 2004 4:42 am ]
Post subject: 
The TV-card is a:
Hauppauge WinTV PVR-250 (PAL - B/G, 48014 REV F408)

The mashine:
ASUS A7V266-E
AMD Athlon XP 1700+
512MB DDR
ASUS V8200 T2 64MB (GeForce2)
SoundBlaster Live (CT4830)
3Com 3C905-TX networkcard
Seagate 80GB

I think the msp3400 module is a part of bttv and msp34xx is a soundprocessing chip on the TV card. The syslog show that the msp3400 module identifies the chip as a MSP3415D B3 chip and thats right!

Enough info?
Author:  willem [ Sun Mar 28, 2004 2:17 pm ]
Post subject: 
There is a sound issue for PAL users that I ran into also. In my case every now and then a recording would have no audio while others where just fine. This is a thread I found regarding this problem:

http://www.poptix.net/ivtv/May-2003/msg00474.html

It is almost a year old so I don't know if it is fixed by now. It may have nothing to do with your problem, but could be worth trying. I havent done much testing myself, but you may try append standard=0x08 to your msp3400 options line in /etc/mythtv/modules/ivtv and run update-modules.
Author:  DrHoneydew1975 [ Tue Mar 30, 2004 3:10 am ]
Post subject: 
Thanks for the tip but unfortunately I've had no luck. :cry: I'v tried everything but I still get the I/O error #1,2 and 3 from the msp3400 module.

I've used the card in Windows XP and it worked fine (but it was quite some time ago so maybe I should test it again to see if it's broken or not!).

Does anyone else have the same MSP chip as I? I'v got the MSP3415D B3 (onbord the Hauppauge PVR250 card). If yes - do you got sound?

All feedback welcome...
Author:  cesman [ Tue Mar 30, 2004 11:42 am ]
Post subject: 
Have you posted to the ivtv mailing list? If not, I'd suggest you do.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/