Dale Pontius <[email protected]> wrote: >On 06/07/2011 05:32:50 AM, Andy Walls wrote: >> Eric Morgan <[email protected]> wrote: >> >> >On Mon, Jun 6, 2011 at 6:50 AM, Eric Morgan <[email protected]> >> >wrote: >> > >> >> Actually at the moment I have a green screen on one an a red >> screen >> >on the >> >> other... >> >> On Jun 5, 2011 9:10 AM, "Eric Morgan" <[email protected]> >> wrote: >> >> > On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls >> ><[email protected]> >> >> wrote: >> >> > >> >> >> Hi Eric, >> >> >> >> >> >> (adding the list back to the Cc:) >> >> >> >> >> >> On Sat, 2011-06-04 at 10:12 -0700, Eric Morgan wrote: >> >> >> >> >> >> >> >> >> > Hi Andy, Thanks so much for the help. >> >> >> >> >> >> You're welcome. >> >> >> >> >> >> > >> >> >> > Here's the log: >> >> >> > server:~$ v4l2-ctl -d /dev/video0 --log-status >> >> >> >> >> >> This doesn't include all the messages that you get upon module >> >load, but >> >> >> honestly things appear to be OK from that perspective. I have >> some >> >> >> comments/questions on the log below: >> >> >> >> >> >> > Status Log: >> >> >> > >> >> >> > [45978.023303] cx18-0: ================= START STATUS CARD #0 >> >> >> ================= >> >> >> > [45978.023308] cx18-0: Version: 1.5.0 Card: Hauppauge >> HVR-1600 >> >> >> > [45978.065888] tveeprom 14-0050: Hauppauge model 74301, rev >> >F1F5, >> >> >> serial# [redacted] >> >> >> > [45978.065892] tveeprom 14-0050: MAC address is [redacted] >> >> >> > [45978.065895] tveeprom 14-0050: tuner model is NXP 18271C2 >> (idx >> >155, >> >> >> type 54) >> >> >> > [45978.065899] tveeprom 14-0050: TV standards PAL(B/G) NTSC >> (M) >> >PAL(I) >> >> >> SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc) >> >> >> > [45978.065902] tveeprom 14-0050: audio processor is CX23418 >> (idx >> >38) >> >> >> > [45978.065905] tveeprom 14-0050: decoder processor is CX23418 >> >(idx 31) >> >> >> > [45978.065908] tveeprom 14-0050: has no radio, has IR >> receiver, >> >has IR >> >> >> transmitter >> >> >> ^^ >> >> >> There are at least 15 I2C busses in your system. That's alot. I >> am >> >> >> going to assume there are a lot of various PCI/PCIe cards and/ >> or >> >USB >> >> >> peripherials installed in this machine. >> >> >> >> >> >> >> >> >> >> >> >> > [45978.065915] cx18-0 843: Video signal: not present >> >> >> >> >> >> The meaning of this is very clear. The CX25843 core inside the >> >CX23418 >> >> >> cannot get enough valid horizontal and vertical video sync >> pulses >> >from >> >> >> the analog video signal at the input of the CX23418 chip. >> >> >> >> >> >> This can happen for a number of reasons, but first.... >> >> >> >> >> >> > [45978.065917] cx18-0 843: Detected format: NTSC-M >> >> >> > [45978.065919] cx18-0 843: Specified standard: NTSC-M >> >> >> > [45978.065921] cx18-0 843: Specified video input: S-Video >> (Luma >> >> >> In1, Chroma In5) >> >> >> >> >> >> Do you have a known good S-Video source hooked up with an >> active >> >signal >> >> >> and a known good cable? >> >> >> >> >> >> > [45978.065924] cx18-0 843: Specified audioclock freq: 48000 >> Hz >> >> >> > [45978.065934] cx18-0 843: Detected audio mode: mono >> >> >> > [45978.065936] cx18-0 843: Detected audio standard: no >> detected >> >> >> audio standard >> >> >> > [45978.065938] cx18-0 843: Audio muted: no >> >> >> > [45978.065940] cx18-0 843: Audio microcontroller: stopped >> >> >> > [45978.065942] cx18-0 843: Configured audio standard: >> automatic >> >> >> detection >> >> >> > [45978.065944] cx18-0 843: Configured audio system: BTSC >> >> >> > [45978.065946] cx18-0 843: Specified audio input: External >> >> >> > [45978.065948] cx18-0 843: Preferred audio mode: stereo >> >> >> > [45978.066488] cx18-0 gpio-reset-ctrl: GPIO: direction >> >0x00003801, >> >> >> value 0x00003801 >> >> >> > [45978.068758] cs5345 14-004c: Input: 2 >> >> >> > [45978.068760] cs5345 14-004c: Volume: 0 dB >> >> >> > [45978.068763] cx18-0: Video Input: S-Video 1 >> >> >> > [45978.068765] cx18-0: Audio Input: Line In 1 >> >> >> > [45978.068768] cx18-0: GPIO: direction 0x00003801, value >> >0x00003801 >> >> >> > [45978.068770] cx18-0: Tuner: TV >> >> >> > [45978.068773] cx18-0: Stream Type: MPEG-2 Program Stream >> >> >> > [45978.068776] cx18-0: Stream VBI Format: No VBI >> >> >> > [45978.068779] cx18-0: Audio Sampling Frequency: 48 kHz >> >> >> > [45978.068782] cx18-0: Audio Encoding: MPEG-1/2 Layer II >> >> >> > [45978.068785] cx18-0: Audio Layer II Bitrate: 224 kbps >> >> >> > [45978.068787] cx18-0: Audio Stereo Mode: Stereo >> >> >> > [45978.068790] cx18-0: Audio Stereo Mode Extension: Bound 4 >> >(inactive) >> >> >> > [45978.068793] cx18-0: Audio Emphasis: No Emphasis >> >> >> > [45978.068796] cx18-0: Audio CRC: No CRC >> >> >> > [45978.068798] cx18-0: Audio Mute: false >> >> >> > [45978.068801] cx18-0: Video Encoding: MPEG-2 >> >> >> > [45978.068803] cx18-0: Video Aspect: 4x3 >> >> >> > [45978.068806] cx18-0: Video B Frames: 2 >> >> >> > [45978.068809] cx18-0: Video GOP Size: 15 >> >> >> > [45978.068811] cx18-0: Video GOP Closure: true >> >> >> > [45978.068814] cx18-0: Video Bitrate Mode: Variable Bitrate >> >> >> > [45978.068817] cx18-0: Video Bitrate: 6000000 >> >> >> > [45978.068819] cx18-0: Video Peak Bitrate: 8000000 >> >> >> > [45978.068822] cx18-0: Video Temporal Decimation: 0 >> >> >> > [45978.068825] cx18-0: Video Mute: false >> >> >> > [45978.068828] cx18-0: Video Mute YUV: 32896 >> >> >> > [45978.068830] cx18-0: Spatial Filter Mode: Manual >> >> >> > [45978.068833] cx18-0: Spatial Filter: 0 >> >> >> > [45978.068836] cx18-0: Spatial Luma Filter Type: 1D >> Horizontal >> >> >> > [45978.068839] cx18-0: Spatial Chroma Filter Type: 1D >> Horizontal >> >> >> > [45978.068841] cx18-0: Temporal Filter Mode: Manual >> >> >> > [45978.068844] cx18-0: Temporal Filter: 8 >> >> >> > [45978.068847] cx18-0: Median Filter Type: Off >> >> >> > [45978.068849] cx18-0: Median Luma Filter Minimum: 0 >> (inactive) >> >> >> > [45978.068852] cx18-0: Median Luma Filter Maximum: 255 >> >(inactive) >> >> >> > [45978.068855] cx18-0: Median Chroma Filter Minimum: 0 >> >(inactive) >> >> >> > [45978.068858] cx18-0: Median Chroma Filter Maximum: 255 >> >(inactive) >> >> >> > [45978.068861] cx18-0: Insert Navigation Packets: false >> >> >> > [45978.068864] cx18-0: Status flags: 0x00200001 >> >> >> > [45978.068867] cx18-0: Stream encoder MPEG: status 0x0000, 0% >> of >> >2048 >> >> >> KiB (64 buffers) in use >> >> >> > [45978.068871] cx18-0: Stream encoder YUV: status 0x0000, 0% >> of >> >2025 >> >> >> KiB (20 buffers) in use >> >> >> > [45978.068874] cx18-0: Stream encoder VBI: status 0x0000, 0% >> of >> >1015 >> >> >> KiB (20 buffers) in use >> >> >> > [45978.068877] cx18-0: Stream encoder PCM audio: status >> 0x0000, >> >0% of >> >> >> 1024 KiB (256 buffers) in use >> >> >> > [45978.068880] cx18-0: Read MPEG/VBI: 3893248/0 bytes >> >> >> >> >> >> I see you've been reading data from the MPEG device node. Are >> you >> >> >> getting a black screen, a grey screen, or (I hope not) a red >> >screen? >> >> >> >> >> >> Regards, >> >> >> Andy >> >> >> >> >> >> > [45978.068882] cx18-0: ================== END STATUS CARD #0 >> >> >> ================== >> >> >> > >> >> >> >> >> >> >> >> >> Thanks again... >> >> > >> >> > There are at least 15 I2C busses in your system. That's alot. I >> am >> >> >> going to assume there are a lot of various PCI/PCIe cards and/ >> or >> >USB >> >> >> peripherials installed in this machine. >> >> >> >> >> > >> >> > I have the two hvr-1600's and that's it. >> >> > >> >> > Do you have a known good S-Video source hooked up with an active >> >signal >> >> >> and a known good cable? >> >> >> >> >> > >> >> > I'm relatively sure the source is good. It was all hooked up to >> a >> >the >> >> same >> >> > system with a pair of PVR-150's which I assume were going bad >> >(unstable >> >> > signal, wavy picture). On this setup, one card's tuner was >> >connected to >> >> the >> >> > cable out of a cable box, and the other directly to cable. I >> wasn't >> >using >> >> > the box's s-video out. I've hooked both cables directly to a TV >> and >> >the >> >> > signal looks good there. I have not tested the s-video out of >> the >> >cable >> >> box >> >> > but assume it's ok. I'll see if I can find something to hook it >> to. >> >> > >> >> > There is a bit of splitting going on before the cards see the >> >cable. >> >> Perhaps >> >> > these cards need a bigger signal? Maybe the wavy pictures of the >> >> PVR-150's >> >> > was a drop in signal and not the tuners going bad? >> >> > >> >> > I see you've been reading data from the MPEG device node. Are >> you >> >> >> getting a black screen, a grey screen, or (I hope not) a red >> >screen? >> >> >> >> >> > >> >> > >> >> > Interestingly, one card shows a black screen (video1) and the >> other >> >shows >> >> > the red screen (video0). >> >> > >> >> > Eric >> >> >> > >> >Ok I've hunted through just about every log I can find. It appears >> that >> >everything is loading find and I don't see any errors. >> > >> >I left the cards in the mythbox and the schedule is running normally >> >from >> >when I had the PVR150's installed. One card is recording all red and >> >the >> >other is all green. >> > >> >What else can I look at/try? >> > >> >Thanks! >> >> I'll write up something later tonight, if/when I have time. (I >> usually only have time for about 1 properly researched email answer >> per day.) >> >> The only thing a user can do immediately, for a red-screen cx23418, >> is >> unload the cx18 driver and reload the cx18 driver. (My >> *speculation*, >> for when the red screen happens, is that the cx25843 core is not >> operating due to some race between the cx23418 and cx18 driver when >> initializing. I *speculate* it is due to intermittent system >> latencies or transient PCI bus conditions. I truly do not understand >> the mechanism, as I have only ever encoutered the problem once myself >> in 4(?) years or so of doing this.) >> >> Note that if cx18-alsa is loaded, cx18-alsa has to be unloaded first. >> Pulse-audio makes that a PITA, because it holds the device open and >> respawns when killed. >> >> Regards, >> Andy >> >I've probably had the most persistent problems with red-screen. I seem > >to remember that for me it took a complete power disconnection to clean > >up. A regular power-down still leaves power to some parts of the >system, and I had to either unplug or flip the switch on the back of >the power supply. > >But sometime around last summer I moved to a new kernel the the red- >screen problems went away. I don't know exactly what kernel fixed it, >but I see that a config dated Aug 15, 2010 was 2.6.35-gentoo-r1, and I >don't appear to have moved to a 2.6.36 series kernel until late >December. I'm guessing that 2.6.35+ fixed it, for me. > >Dale Pontius > > > > >_______________________________________________ >ivtv-users mailing list >[email protected] >http://ivtvdriver.org/mailman/listinfo/ivtv-users
As I ponder this more, I think it is a cx18 driver problem that userspace mitigates. The cx18 driver initializes the cx23418 chip and then doesn't load the firmware until somethings opens a device node. On all my systems a daemon queries the device node as soon as it appears, forcing an immediate firmware load. I wonder if the cx23418's internal processors are just free-running, trying to execute garbage, until the firmware load process starts. If the firmware load comes very late, this might be causing the red screen symptom. I'll work up a patch to eliminate that possibilty tonight or tommorrow. It's all wild speculation, but maybe it will help. -Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
