Hi.
Looking through the mailingtreads i see no sound issues on pvr-350 during 2006.
Replying to myself in favor of a no spam mail.

 Hi all.

Never had any audio issues until upgrading from ivtv-0.6.3.
I\'ve followed the list with closed eyes until now, as i did not have any 
problems before.

Inside-
Technotrend Systemtechnik GmbH Octal/Technotrend DVB-C for iTV SAA7146 (rev 01) 
(currently no in use)
Siemens Nixdorf AG Fujitsu/Siemens DVB-C card rev1.5 SAA7146 (rev 01)
pvr-350 Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)

Amd64 with kernel 2.6.18 gentoo.

There is h\'of alot of these in the log.
ivtv0-osd warning: Error OSD User DMA
ivtv0 warning: DMA_TO: REDO DMA took too many tries.

In addition to this( i think it was intruduced after adding dvb-c cards ), when 
channel scaning in mythtv i some times have system lockups.
And the scanner does not find more than ~35% of the channels. I discabled the 
dvb-c cards for testing signal issues. But same result.

MythTV-0.20.diff patched mythtv.20

Sep 28 10:45:24 tux ivtv: ==================== START INIT IVTV 
====================
Sep 28 10:45:24 tux ivtv: version 0.8.0 (tagged release) loading
Sep 28 10:45:24 tux ivtv: Linux version: 2.6.18-gentoo mod_unload gcc-4.1
Sep 28 10:45:24 tux ivtv: In case of problems please include the debug info 
between
Sep 28 10:45:24 tux ivtv: the START INIT IVTV and END INIT IVTV lines, along 
with
Sep 28 10:45:24 tux ivtv: any module options, when mailing the ivtv-users 
mailinglist.
Sep 28 10:45:24 tux ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 
based)
Sep 28 10:45:24 tux ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19
Sep 28 10:45:24 tux GSI 19 sharing vector 0xC9 and IRQ 19
Sep 28 10:45:24 tux ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKC] -> GSI 
19 (level, low) -> IRQ 201
Sep 28 10:45:24 tux ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Sep 28 10:45:24 tux ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
Sep 28 10:45:24 tux tveeprom 0-0050: Hauppauge model 48134, rev I121, serial# 
6183422
Sep 28 10:45:24 tux tveeprom 0-0050: tuner model is Philips FM1216 (idx 21, 
type 5)
Sep 28 10:45:24 tux tveeprom 0-0050: TV standards PAL(B/G) (eeprom 0x04)
Sep 28 10:45:24 tux tveeprom 0-0050: audio processor is MSP4418 (idx 25)
Sep 28 10:45:24 tux tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
Sep 28 10:45:24 tux tveeprom 0-0050: has radio, has IR remote
Sep 28 10:45:24 tux tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Sep 28 10:45:24 tux saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
Sep 28 10:45:24 tux saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)
Sep 28 10:45:24 tux msp3400 0-0040: MSP4418G-A2 found @ 0x80 (ivtv i2c driver 
#0)
Sep 28 10:45:24 tux msp3400 0-0040: MSP4418G-A2 supports nicam and radio, mode 
is autodetect and autoselect
Sep 28 10:45:24 tux ivtv0: Encoder revision: 0x02050032
Sep 28 10:45:24 tux ivtv0: Decoder revision: 0x02020023
Sep 28 10:45:24 tux ivtv0: Registered device video0 for encoder MPEG
Sep 28 10:45:24 tux ivtv0: Registered device video32 for encoder YUV
Sep 28 10:45:24 tux ivtv0: Registered device vbi0 for encoder VBI
Sep 28 10:45:24 tux ivtv0: Registered device video24 for encoder PCM audio
Sep 28 10:45:24 tux ivtv0: Registered device radio0 for encoder radio
Sep 28 10:45:24 tux ivtv0: Registered device video16 for decoder MPEG
Sep 28 10:45:24 tux ivtv0: Registered device vbi8 for decoder VBI
Sep 28 10:45:24 tux ivtv0: Registered device vbi16 for decoder VOUT
Sep 28 10:45:24 tux ivtv0: Registered device video48 for decoder YUV
Sep 28 10:45:24 tux ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
Sep 28 10:45:24 tux tuner 0-0061: type set to 5 (Philips PAL_BG (FI1216 and 
compatibles))
Sep 28 10:45:24 tux ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
Sep 28 10:45:24 tux ivtv: ==================== END INIT IVTV 
====================


I realize i dont have any errors here.
But what can i do to solve this? And how to debug it?


/Br Fredrik


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

Reply via email to