Does this PVR250 have a different tuner compared to the others? It might
be interesting to compare the output of 'v4l2-ctl --log-status' for that
tuner while capturing channel 13 with the same output when capturing
another channel with that same card.
Regards,
Hans
> My parents are reporting that card #1, a pvr250 of 3 total, whenever it
> is programmed to record channel 13, there is no audio. If any of the
> other cards (all 250's) record 13 the audio is fine. If card 1 records
> any
> other channel its also fine.
>
> I've copied a few seconds of an example file up and played it with
> mplayer, no audio there either. mplayer doesn't show anything
> unusual in its console output for audio either.
>
> I've checked the backend.log and syslogs and don't see anything
> of note. Below I've included the last syslog init of this card.
>
> Backend details:
> ivtv driver 0.10.1
> linux 2.6.19.7
> AMD XP 2500, Mandriva 2007 PP i586
> 3 pvr250 cards
> 2 HD3000 cards
>
> I don't know if I'm looking at a bad card, and bad channel database entry,
> driver / firmware mismatch, or something else. I posted this note to the
> mythtv-users group but didn't get any reply. Any thoughts? Any tests I
> can run to narrow down the problem?
>
> Thanks,
> Brian
>
>
>
> May 9 21:53:04 pvr kernel: ivtv: ==================== START INIT IVTV
> ====================
> May 9 21:53:04 pvr kernel: ivtv: version 0.10.1 (tagged release) loading
> May 9 21:53:04 pvr kernel: ivtv: Linux version: 2.6.19.7_bkf2 mod_unload
> K7
> May 9 21:53:04 pvr kernel: ivtv: In case of problems please include the
> debug info between
> May 9 21:53:04 pvr kernel: ivtv: the START INIT IVTV and END INIT IVTV
> lines, along with
> May 9 21:53:04 pvr kernel: ivtv: any module options, when mailing the
> ivtv-users mailinglist.
> May 9 21:53:04 pvr kernel: ivtv0: Autodetected Hauppauge card (cx23416
> based)
> May 9 21:53:04 pvr kernel: ACPI: PCI Interrupt Link [LNK4] enabled at IRQ
> 9
> May 9 21:53:04 pvr kernel: ACPI: PCI Interrupt 0000:01:07.0[A] -> Link
> [LNK4]
> -> GSI 9 (level, low) -> IRQ 9
> May 9 21:53:04 pvr kernel: ivtv0: Unreasonably low latency timer, setting
> to
> 64 (was 32)
> May 9 21:53:04 pvr kernel: ieee1394: Host added: ID:BUS[0-00:1023]
> GUID[00e01800005ec313]
> May 9 21:53:04 pvr kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware
> (376836
> bytes)
> May 9 21:53:04 pvr kernel: ivtv0: Encoder revision: 0x02060039
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: Hauppauge model 32032, rev
> B310,
> serial# 7046004
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: tuner model is Philips FI1236
> MK2
> (idx 10, type 2)
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: TV standards NTSC(M) (eeprom
> 0x08)
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: audio processor is MSP4448
> (idx
> 27)
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: decoder processor is SAA7115
> (idx
> 19)
> May 9 21:53:04 pvr kernel: tveeprom 2-0050: has no radio, has IR remote
> May 9 21:53:04 pvr kernel: ivtv0: Autodetected Hauppauge WinTV PVR-250
> May 9 21:53:04 pvr kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c
> driver
> #0)
> May 9 21:53:04 pvr kernel: saa7115 2-0021: saa7115 found
> (1f7115d0e100000) @
> 0x42 (ivtv i2c driver #0)
> May 9 21:53:04 pvr kernel: msp3400 2-0040: MSP4448G-A2 found @ 0x80 (ivtv
> i2c
> driver #0)
> May 9 21:53:04 pvr kernel: msp3400 2-0040: MSP4448G-A2 supports radio,
> mode
> is autodetect and autoselect
> May 9 21:53:04 pvr kernel: ivtv0: Registered device video0 for encoder
> MPEG
> (4 MB)
> May 9 21:53:04 pvr kernel: ivtv0: Registered device video32 for encoder
> YUV
> (2 MB)
> May 9 21:53:04 pvr kernel: ivtv0: Registered device vbi0 for encoder VBI
> (1
> MB)
> May 9 21:53:04 pvr kernel: ivtv0: Registered device video24 for encoder
> PCM
> audio (1 MB)
> May 9 21:53:04 pvr kernel: tuner 2-0061: type set to 2 (Philips NTSC
> (FI1236,FM1236 and compatibles))
> May 9 21:53:04 pvr kernel: ivtv0: Initialized Hauppauge WinTV PVR-250,
> card
> #0
> May 9 21:53:04 pvr kernel: ivtv: ====================== NEXT CARD
> ======================
>
> _______________________________________________
> 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
