Mailing List Archive

HVR-1600 analog no signal
Hey all,

Just got a pair of hvr-1600 to replace my failing pvr-150s and the analog
side seems a no go. They are both 1199 (74301) models and I have compiled
what I think is the latest media_build.
Did this:
git clone git://linuxtv.org/git/media_build.git
cd media_build
./build.sh
(btw, seemed to work fine in Ubuntu 11.04)

The drivers seem to load fine and the only issue that my untrained eyes can
see is that the cards are reporting no video signal. I have not messed with
the firmware. The file dates are Nov 2010 for the firmware and seem newer
than that I could find at linuxtv (Jun 2010) or ivtv (2008) Here's the log:

dmesg |grep cx18-0
[ 11.503552] cx18-0: Initializing card 0
[ 11.503556] cx18-0: Autodetected Hauppauge card
[ 11.518334] cx18-0: cx23418 revision 01010000 (B)
[ 12.126513] cx18-0: Autodetected Hauppauge HVR-1600
[ 12.412021] cx18-0: Simultaneous Digital and Analog TV capture supported
[ 30.293196] cx18-0: Registered device video0 for encoder MPEG (64 x 32.00
kB)
[ 30.628597] cx18-0: DVB Frontend registered
[ 30.628602] cx18-0: Registered DVB adapter0 for TS (32 x 32.00 kB)
[ 30.628803] cx18-0: Registered device video32 for encoder YUV (20 x
101.25 kB)
[ 30.628987] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984
bytes)
[ 30.629179] cx18-0: Registered device video24 for encoder PCM audio (256
x 4.00 kB)
[ 30.629183] cx18-0: Initialized card: Hauppauge HVR-1600
[ 48.193002] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
[ 48.561956] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200
bytes)
[ 48.573866] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
[ 49.433337] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
[ 49.453580] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware
(16382 bytes)
[ 151.427081] cx18-0: ================= START STATUS CARD #0
=================
[ 151.427086] cx18-0: Version: 1.5.0 Card: Hauppauge HVR-1600
[ 151.469710] cx18-0 843: Video signal: not present
[ 151.469712] cx18-0 843: Detected format: NTSC-M
[ 151.469714] cx18-0 843: Specified standard: NTSC-M
[ 151.469717] cx18-0 843: Specified video input: Composite 7
[ 151.469719] cx18-0 843: Specified audioclock freq: 48000 Hz
[ 151.469729] cx18-0 843: Detected audio mode: mono
[ 151.469731] cx18-0 843: Detected audio standard: no detected audio
standard
[ 151.469733] cx18-0 843: Audio muted: yes
[ 151.469735] cx18-0 843: Audio microcontroller: running
[ 151.469737] cx18-0 843: Configured audio standard: automatic detection
[ 151.469739] cx18-0 843: Configured audio system: BTSC
[ 151.469742] cx18-0 843: Specified audio input: Tuner (In8)
[ 151.469744] cx18-0 843: Preferred audio mode: stereo
[ 151.469989] cx18-0 gpio-reset-ctrl: GPIO: direction 0x00003801, value
0x00003801
[ 151.472251] cx18-0: Video Input: Tuner 1
[ 151.472252] cx18-0: Audio Input: Tuner 1
[ 151.472255] cx18-0: GPIO: direction 0x00003801, value 0x00003801
[ 151.472257] cx18-0: Tuner: TV
[ 151.472259] cx18-0: Stream Type: MPEG-2 Program Stream
[ 151.472263] cx18-0: Stream VBI Format: No VBI
[ 151.472266] cx18-0: Audio Sampling Frequency: 48 kHz
[ 151.472268] cx18-0: Audio Encoding: MPEG-1/2 Layer II
[ 151.472271] cx18-0: Audio Layer II Bitrate: 224 kbps
[ 151.472274] cx18-0: Audio Stereo Mode: Stereo
[ 151.472277] cx18-0: Audio Stereo Mode Extension: Bound 4
[ 151.472280] cx18-0: Audio Emphasis: No Emphasis
[ 151.472283] cx18-0: Audio CRC: No CRC
[ 151.472285] cx18-0: Audio Mute: false
[ 151.472288] cx18-0: Video Encoding: MPEG-2
[ 151.472290] cx18-0: Video Aspect: 4x3
[ 151.472293] cx18-0: Video B Frames: 2
[ 151.472295] cx18-0: Video GOP Size: 15
[ 151.472298] cx18-0: Video GOP Closure: true
[ 151.472300] cx18-0: Video Bitrate Mode: Variable Bitrate
[ 151.472303] cx18-0: Video Bitrate: 6000000
[ 151.472306] cx18-0: Video Peak Bitrate: 8000000
[ 151.472309] cx18-0: Video Temporal Decimation: 0
[ 151.472312] cx18-0: Video Mute: false
[ 151.472314] cx18-0: Video Mute YUV: 32896
[ 151.472317] cx18-0: Spatial Filter Mode: Manual
[ 151.472320] cx18-0: Spatial Filter: 0
[ 151.472322] cx18-0: Spatial Luma Filter Type: 1D Horizontal
[ 151.472325] cx18-0: Spatial Chroma Filter Type: 1D Horizontal
[ 151.472328] cx18-0: Temporal Filter Mode: Manual
[ 151.472330] cx18-0: Temporal Filter: 8
[ 151.472333] cx18-0: Median Filter Type: Off
[ 151.472336] cx18-0: Median Luma Filter Minimum: 0
[ 151.472338] cx18-0: Median Luma Filter Maximum: 255
[ 151.472341] cx18-0: Median Chroma Filter Minimum: 0
[ 151.472344] cx18-0: Median Chroma Filter Maximum: 255
[ 151.472346] cx18-0: Insert Navigation Packets: false
[ 151.472349] cx18-0: Status flags: 0x00200001
[ 151.472352] cx18-0: Stream encoder MPEG: status 0x0000, 0% of 2048 KiB
(64 buffers) in use
[ 151.472356] cx18-0: Stream encoder YUV: status 0x0000, 0% of 2025 KiB (20
buffers) in use
[ 151.472359] cx18-0: Stream encoder VBI: status 0x0000, 0% of 1015 KiB (20
buffers) in use
[ 151.472362] cx18-0: Stream encoder PCM audio: status 0x0000, 0% of 1024
KiB (256 buffers) in use
[ 151.472365] cx18-0: Read MPEG/VBI: 0/0 bytes
[ 151.472367] cx18-0: ================== END STATUS CARD #0
==================


Any ideas?

Eric
Re: HVR-1600 analog no signal [ In reply to ]
Eric Morgan <gemorgan99@gmail.com> wrote:

>Hey all,
>
>Just got a pair of hvr-1600 to replace my failing pvr-150s and the
>analog
>side seems a no go. They are both 1199 (74301) models and I have
>compiled
>what I think is the latest media_build.
>Did this:
>git clone git://linuxtv.org/git/media_build.git
>cd media_build
>./build.sh
>(btw, seemed to work fine in Ubuntu 11.04)
>
>The drivers seem to load fine and the only issue that my untrained eyes
>can
>see is that the cards are reporting no video signal. I have not messed
>with
>the firmware. The file dates are Nov 2010 for the firmware and seem
>newer
>than that I could find at linuxtv (Jun 2010) or ivtv (2008) Here's the
>log:
>
>dmesg |grep cx18-0
>[ 11.503552] cx18-0: Initializing card 0
>[ 11.503556] cx18-0: Autodetected Hauppauge card
>[ 11.518334] cx18-0: cx23418 revision 01010000 (B)
>[ 12.126513] cx18-0: Autodetected Hauppauge HVR-1600
>[ 12.412021] cx18-0: Simultaneous Digital and Analog TV capture
>supported
>[ 30.293196] cx18-0: Registered device video0 for encoder MPEG (64 x
>32.00
>kB)
>[ 30.628597] cx18-0: DVB Frontend registered
>[ 30.628602] cx18-0: Registered DVB adapter0 for TS (32 x 32.00 kB)
>[ 30.628803] cx18-0: Registered device video32 for encoder YUV (20 x
>101.25 kB)
>[ 30.628987] cx18-0: Registered device vbi0 for encoder VBI (20 x
>51984
>bytes)
>[ 30.629179] cx18-0: Registered device video24 for encoder PCM audio
>(256
>x 4.00 kB)
>[ 30.629183] cx18-0: Initialized card: Hauppauge HVR-1600
>[ 48.193002] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332
>bytes)
>[ 48.561956] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000
>(141200
>bytes)
>[ 48.573866] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
>[ 49.433337] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382
>bytes)
>[ 49.453580] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware
>(16382 bytes)
>[ 151.427081] cx18-0: ================= START STATUS CARD #0
>=================
>[ 151.427086] cx18-0: Version: 1.5.0 Card: Hauppauge HVR-1600
>[ 151.469710] cx18-0 843: Video signal: not present
>[ 151.469712] cx18-0 843: Detected format: NTSC-M
>[ 151.469714] cx18-0 843: Specified standard: NTSC-M
>[ 151.469717] cx18-0 843: Specified video input: Composite 7
>[ 151.469719] cx18-0 843: Specified audioclock freq: 48000 Hz
>[ 151.469729] cx18-0 843: Detected audio mode: mono
>[ 151.469731] cx18-0 843: Detected audio standard: no detected audio
>standard
>[ 151.469733] cx18-0 843: Audio muted: yes
>[ 151.469735] cx18-0 843: Audio microcontroller: running
>[ 151.469737] cx18-0 843: Configured audio standard: automatic
>detection
>[ 151.469739] cx18-0 843: Configured audio system: BTSC
>[ 151.469742] cx18-0 843: Specified audio input: Tuner (In8)
>[ 151.469744] cx18-0 843: Preferred audio mode: stereo
>[ 151.469989] cx18-0 gpio-reset-ctrl: GPIO: direction 0x00003801,
>value
>0x00003801
>[ 151.472251] cx18-0: Video Input: Tuner 1
>[ 151.472252] cx18-0: Audio Input: Tuner 1
>[ 151.472255] cx18-0: GPIO: direction 0x00003801, value 0x00003801
>[ 151.472257] cx18-0: Tuner: TV
>[ 151.472259] cx18-0: Stream Type: MPEG-2 Program Stream
>[ 151.472263] cx18-0: Stream VBI Format: No VBI
>[ 151.472266] cx18-0: Audio Sampling Frequency: 48 kHz
>[ 151.472268] cx18-0: Audio Encoding: MPEG-1/2 Layer II
>[ 151.472271] cx18-0: Audio Layer II Bitrate: 224 kbps
>[ 151.472274] cx18-0: Audio Stereo Mode: Stereo
>[ 151.472277] cx18-0: Audio Stereo Mode Extension: Bound 4
>[ 151.472280] cx18-0: Audio Emphasis: No Emphasis
>[ 151.472283] cx18-0: Audio CRC: No CRC
>[ 151.472285] cx18-0: Audio Mute: false
>[ 151.472288] cx18-0: Video Encoding: MPEG-2
>[ 151.472290] cx18-0: Video Aspect: 4x3
>[ 151.472293] cx18-0: Video B Frames: 2
>[ 151.472295] cx18-0: Video GOP Size: 15
>[ 151.472298] cx18-0: Video GOP Closure: true
>[ 151.472300] cx18-0: Video Bitrate Mode: Variable Bitrate
>[ 151.472303] cx18-0: Video Bitrate: 6000000
>[ 151.472306] cx18-0: Video Peak Bitrate: 8000000
>[ 151.472309] cx18-0: Video Temporal Decimation: 0
>[ 151.472312] cx18-0: Video Mute: false
>[ 151.472314] cx18-0: Video Mute YUV: 32896
>[ 151.472317] cx18-0: Spatial Filter Mode: Manual
>[ 151.472320] cx18-0: Spatial Filter: 0
>[ 151.472322] cx18-0: Spatial Luma Filter Type: 1D Horizontal
>[ 151.472325] cx18-0: Spatial Chroma Filter Type: 1D Horizontal
>[ 151.472328] cx18-0: Temporal Filter Mode: Manual
>[ 151.472330] cx18-0: Temporal Filter: 8
>[ 151.472333] cx18-0: Median Filter Type: Off
>[ 151.472336] cx18-0: Median Luma Filter Minimum: 0
>[ 151.472338] cx18-0: Median Luma Filter Maximum: 255
>[ 151.472341] cx18-0: Median Chroma Filter Minimum: 0
>[ 151.472344] cx18-0: Median Chroma Filter Maximum: 255
>[ 151.472346] cx18-0: Insert Navigation Packets: false
>[ 151.472349] cx18-0: Status flags: 0x00200001
>[ 151.472352] cx18-0: Stream encoder MPEG: status 0x0000, 0% of 2048
>KiB
>(64 buffers) in use
>[ 151.472356] cx18-0: Stream encoder YUV: status 0x0000, 0% of 2025
>KiB (20
>buffers) in use
>[ 151.472359] cx18-0: Stream encoder VBI: status 0x0000, 0% of 1015
>KiB (20
>buffers) in use
>[ 151.472362] cx18-0: Stream encoder PCM audio: status 0x0000, 0% of
>1024
>KiB (256 buffers) in use
>[ 151.472365] cx18-0: Read MPEG/VBI: 0/0 bytes
>[ 151.472367] cx18-0: ================== END STATUS CARD #0
>==================
>
>
>Any ideas?
>
>Eric
>_______________________________________________
>ivtv-users mailing list
>ivtv-users@ivtvdriver.org
>http://ivtvdriver.org/mailman/listinfo/ivtv-users

Try blacklisting the cx18 driver in /etc/modprobe.d/... so it doesn't load at boot. Then load the cx18 driver some time after boot up manually.

Also try and see if composite or svideo works even if the analog tuner doesn't.

Regards,
Andy

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
On Fri, Jun 3, 2011 at 6:40 PM, Andy Walls <awalls@md.metrocast.net> wrote:

> Eric Morgan <gemorgan99@gmail.com> wrote:
>
> >Hey all,
> >
> >Just got a pair of hvr-1600 to replace my failing pvr-150s and the
> >analog
> >side seems a no go. They are both 1199 (74301) models and I have
> >compiled
> >what I think is the latest media_build.
> >Did this:
> >git clone git://linuxtv.org/git/media_build.git
> >cd media_build
> >./build.sh
> >(btw, seemed to work fine in Ubuntu 11.04)
> >
> >The drivers seem to load fine and the only issue that my untrained eyes
> >can
> >see is that the cards are reporting no video signal. I have not messed
> >with
> >the firmware. The file dates are Nov 2010 for the firmware and seem
> >newer
> >than that I could find at linuxtv (Jun 2010) or ivtv (2008) Here's the
> >log:
> >
> >dmesg |grep cx18-0
> >[ 11.503552] cx18-0: Initializing card 0
> >[ 11.503556] cx18-0: Autodetected Hauppauge card
> >[ 11.518334] cx18-0: cx23418 revision 01010000 (B)
> >[ 12.126513] cx18-0: Autodetected Hauppauge HVR-1600
> >[ 12.412021] cx18-0: Simultaneous Digital and Analog TV capture
> >supported
> >[ 30.293196] cx18-0: Registered device video0 for encoder MPEG (64 x
> >32.00
> >kB)
> >[ 30.628597] cx18-0: DVB Frontend registered
> >[ 30.628602] cx18-0: Registered DVB adapter0 for TS (32 x 32.00 kB)
> >[ 30.628803] cx18-0: Registered device video32 for encoder YUV (20 x
> >101.25 kB)
> >[ 30.628987] cx18-0: Registered device vbi0 for encoder VBI (20 x
> >51984
> >bytes)
> >[ 30.629179] cx18-0: Registered device video24 for encoder PCM audio
> >(256
> >x 4.00 kB)
> >[ 30.629183] cx18-0: Initialized card: Hauppauge HVR-1600
> >[ 48.193002] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332
> >bytes)
> >[ 48.561956] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000
> >(141200
> >bytes)
> >[ 48.573866] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
> >[ 49.433337] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382
> >bytes)
> >[ 49.453580] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware
> >(16382 bytes)
> >[ 151.427081] cx18-0: ================= START STATUS CARD #0
> >=================
> >[ 151.427086] cx18-0: Version: 1.5.0 Card: Hauppauge HVR-1600
> >[ 151.469710] cx18-0 843: Video signal: not present
> >[ 151.469712] cx18-0 843: Detected format: NTSC-M
> >[ 151.469714] cx18-0 843: Specified standard: NTSC-M
> >[ 151.469717] cx18-0 843: Specified video input: Composite 7
> >[ 151.469719] cx18-0 843: Specified audioclock freq: 48000 Hz
> >[ 151.469729] cx18-0 843: Detected audio mode: mono
> >[ 151.469731] cx18-0 843: Detected audio standard: no detected audio
> >standard
> >[ 151.469733] cx18-0 843: Audio muted: yes
> >[ 151.469735] cx18-0 843: Audio microcontroller: running
> >[ 151.469737] cx18-0 843: Configured audio standard: automatic
> >detection
> >[ 151.469739] cx18-0 843: Configured audio system: BTSC
> >[ 151.469742] cx18-0 843: Specified audio input: Tuner (In8)
> >[ 151.469744] cx18-0 843: Preferred audio mode: stereo
> >[ 151.469989] cx18-0 gpio-reset-ctrl: GPIO: direction 0x00003801,
> >value
> >0x00003801
> >[ 151.472251] cx18-0: Video Input: Tuner 1
> >[ 151.472252] cx18-0: Audio Input: Tuner 1
> >[ 151.472255] cx18-0: GPIO: direction 0x00003801, value 0x00003801
> >[ 151.472257] cx18-0: Tuner: TV
> >[ 151.472259] cx18-0: Stream Type: MPEG-2 Program Stream
> >[ 151.472263] cx18-0: Stream VBI Format: No VBI
> >[ 151.472266] cx18-0: Audio Sampling Frequency: 48 kHz
> >[ 151.472268] cx18-0: Audio Encoding: MPEG-1/2 Layer II
> >[ 151.472271] cx18-0: Audio Layer II Bitrate: 224 kbps
> >[ 151.472274] cx18-0: Audio Stereo Mode: Stereo
> >[ 151.472277] cx18-0: Audio Stereo Mode Extension: Bound 4
> >[ 151.472280] cx18-0: Audio Emphasis: No Emphasis
> >[ 151.472283] cx18-0: Audio CRC: No CRC
> >[ 151.472285] cx18-0: Audio Mute: false
> >[ 151.472288] cx18-0: Video Encoding: MPEG-2
> >[ 151.472290] cx18-0: Video Aspect: 4x3
> >[ 151.472293] cx18-0: Video B Frames: 2
> >[ 151.472295] cx18-0: Video GOP Size: 15
> >[ 151.472298] cx18-0: Video GOP Closure: true
> >[ 151.472300] cx18-0: Video Bitrate Mode: Variable Bitrate
> >[ 151.472303] cx18-0: Video Bitrate: 6000000
> >[ 151.472306] cx18-0: Video Peak Bitrate: 8000000
> >[ 151.472309] cx18-0: Video Temporal Decimation: 0
> >[ 151.472312] cx18-0: Video Mute: false
> >[ 151.472314] cx18-0: Video Mute YUV: 32896
> >[ 151.472317] cx18-0: Spatial Filter Mode: Manual
> >[ 151.472320] cx18-0: Spatial Filter: 0
> >[ 151.472322] cx18-0: Spatial Luma Filter Type: 1D Horizontal
> >[ 151.472325] cx18-0: Spatial Chroma Filter Type: 1D Horizontal
> >[ 151.472328] cx18-0: Temporal Filter Mode: Manual
> >[ 151.472330] cx18-0: Temporal Filter: 8
> >[ 151.472333] cx18-0: Median Filter Type: Off
> >[ 151.472336] cx18-0: Median Luma Filter Minimum: 0
> >[ 151.472338] cx18-0: Median Luma Filter Maximum: 255
> >[ 151.472341] cx18-0: Median Chroma Filter Minimum: 0
> >[ 151.472344] cx18-0: Median Chroma Filter Maximum: 255
> >[ 151.472346] cx18-0: Insert Navigation Packets: false
> >[ 151.472349] cx18-0: Status flags: 0x00200001
> >[ 151.472352] cx18-0: Stream encoder MPEG: status 0x0000, 0% of 2048
> >KiB
> >(64 buffers) in use
> >[ 151.472356] cx18-0: Stream encoder YUV: status 0x0000, 0% of 2025
> >KiB (20
> >buffers) in use
> >[ 151.472359] cx18-0: Stream encoder VBI: status 0x0000, 0% of 1015
> >KiB (20
> >buffers) in use
> >[ 151.472362] cx18-0: Stream encoder PCM audio: status 0x0000, 0% of
> >1024
> >KiB (256 buffers) in use
> >[ 151.472365] cx18-0: Read MPEG/VBI: 0/0 bytes
> >[ 151.472367] cx18-0: ================== END STATUS CARD #0
> >==================
> >
> >
> >Any ideas?
> >
> >Eric
> >_______________________________________________
> >ivtv-users mailing list
> >ivtv-users@ivtvdriver.org
> >http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> Try blacklisting the cx18 driver in /etc/modprobe.d/... so it doesn't load
> at boot. Then load the cx18 driver some time after boot up manually.
>
> Also try and see if composite or svideo works even if the analog tuner
> doesn't.
>
> Regards,
> Andy
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>


Thanks for the reply. I had already tried the s-video input but I'm not sure
I was doing it right. If I cat from /dev/video32 I can't play the file
using vlc. Also, there's this:

server:~$ v4l2-ctl -i=1 -d /dev/video0 --verbose
VIDIOC_QUERYCAP: ok
VIDIOC_S_INPUT: ok
Video input set to 0 (Tuner 1)

Which isn't right. It's not setting to s-video
server:~$ v4l2-ctl -n -d /dev/video0
ioctl: VIDIOC_ENUMINPUT
Input : 0
Name : Tuner 1
Type : 0x00000001
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 1
Name : S-Video 1
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 2
Name : Composite 1
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 3
Name : S-Video 2
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 4
Name : Composite 2
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

That mean anything?
Re: HVR-1600 analog no signal [ In reply to ]
I have the reverse problem in Fedora 14 (HVR-1600 model 1388): the analog side
works totally fine (at /dev/video0) while I can't get the digital side to tune properly.
The digital side has occasionally been able to record in SD and HD, but since the tuning
is wrong Mythtv refuses to record, or it records the wrong program. Does your digital
side work?


Eric Morgan <gemorgan99@gmail.com> wrote:

>Hey all,
>
>Just got a pair of hvr-1600 to replace my failing pvr-150s and the analog
>side seems a no go. They are both 1199 (74301) models and I have compiled
>what I think is the latest media_build.
>Did this:
>git clone git://linuxtv.org/git/media_build.git
>cd media_build
>./build.sh
>(btw, seemed to work fine in Ubuntu 11.04)
Re: HVR-1600 analog no signal [ In reply to ]
On Fri, 2011-06-03 at 21:47 -0700, Eric Morgan wrote:
> On Fri, Jun 3, 2011 at 6:40 PM, Andy Walls <awalls@md.metrocast.net>
> wrote:
>
> Eric Morgan <gemorgan99@gmail.com> wrote:
>
> >Hey all,
> >
> >Just got a pair of hvr-1600 to replace my failing pvr-150s
> and the
> >analog
> >side seems a no go. They are both 1199 (74301) models and I
> have
> >compiled
> >what I think is the latest media_build.
> >Did this:
> >git clone git://linuxtv.org/git/media_build.git
> >cd media_build
> >./build.sh
> >(btw, seemed to work fine in Ubuntu 11.04)
> >
> >The drivers seem to load fine and the only issue that my
> untrained eyes
> >can
> >see is that the cards are reporting no video signal. I have
> not messed
> >with
> >the firmware. The file dates are Nov 2010 for the firmware
> and seem
> >newer
> >than that I could find at linuxtv (Jun 2010) or ivtv (2008)
> Here's the
> >log:
> >
> >dmesg |grep cx18-0

If you grep for only cx18, you lose the messages emitted from tveeprom,
the tuner drivers, the demodulator drivers, the DVB subsystem, and the
V4L2 infrastructure.

Providing the complete set of HVR-1600 messages might help me see if
anything else is wrong.


> >[ 11.503552] cx18-0: Initializing card 0
....
> >[ 30.629183] cx18-0: Initialized card: Hauppauge HVR-1600


> >[ 48.193002] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
> >[ 48.561956] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
> >[ 48.573866] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
> >[ 49.433337] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
> >[ 49.453580] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)


> >[ 151.427081] cx18-0: ================= START STATUS CARD #0 =================
> >[ 151.427086] cx18-0: Version: 1.5.0 Card: Hauppauge HVR-1600
....
> >[ 151.472367] cx18-0: ================== END STATUS CARD #0 ==================
> >

>
> Try blacklisting the cx18 driver in /etc/modprobe.d/... so it
> doesn't load at boot. Then load the cx18 driver some time
> after boot up manually.
>
> Also try and see if composite or svideo works even if the
> analog tuner doesn't.
>


> Thanks for the reply. I had already tried the s-video input but I'm
> not sure I was doing it right. If I cat from /dev/video32 I can't
> play the file using vlc. Also, there's this:
>
> server:~$ v4l2-ctl -i=1 -d /dev/video0 --verbose
^
|
Don't put in an '=' sign.


> VIDIOC_QUERYCAP: ok
> VIDIOC_S_INPUT: ok
> Video input set to 0 (Tuner 1)

$ v4l2-ctl -i 1 -d /dev/video0 --verbose
VIDIOC_QUERYCAP: ok
VIDIOC_S_INPUT: ok
Video input set to 1 (S-Video 1: ok)


Also with cx18 driver v1.5.0, the YUV /dev/video32 node has the mmap()
interface added to it (for tvtime, etc.), which is sort of a major
change for /dev/video32. Let's not troubleshoot using /dev/video32,
just to eliminate any unknowns with the new functionality.


Just use mplayer on the MPEG /dev/video0 node to view video for testing:

$ mplayer /dev/video0 -cache 8192
MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team
...
Playing /dev/video0.
Cache fill: 17.68% (1482752 bytes)
MPEG-PS file format detected.
VIDEO: MPEG2 720x480 (aspect 2) 29.970 fps 8000.0 kbps (1000.0 kbyte/s)
...
A: 8.3 V: 8.3 A-V: 0.000 ct: 0.047 241/241 24% 0% 1.0% 1 0 12%



Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
On Fri, 2011-06-03 at 23:01 -0700, Greg Fruth wrote:
> I have the reverse problem in Fedora 14 (HVR-1600 model 1388): the
> analog side
> works totally fine (at /dev/video0) while I can't get the digital side
> to tune properly.
> The digital side has occasionally been able to record in SD and HD,
> but since the tuning
> is wrong Mythtv refuses to record, or it records the wrong program.
> Does your digital
> side work?


MythTV is not a good troubleshooting tool - too many moving parts, so to
speak.

Instead, use the basic dvb utilities to create a channels.conf file from
the stdout of [dvb]scan and do some basic tests:

http://www.linuxtv.org/wiki/index.php/User_Information
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device


You can then put the channels.conf file into ~/.mplayer/channels.conf
and use mplayer to test DTV:

(kill the mythbackend and then...)

$ mplayer dvb://WJLA-HD -cache 8192
MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team
...
Playing dvb://WJLA-HD.
dvb_tune Freq: 177028615
Cache fill: 19.82% (1662976 bytes)
TS file format detected.
VIDEO MPEG2(pid=49) AUDIO A52(pid=52) NO SUBS (yet)! PROGRAM N. 0
VIDEO: MPEG2 1280x720 (aspect 3) 59.940 fps 17782.8 kbps (2222.8 kbyte/s)
...
A:28772.1 V:28771.8 A-V: 0.289 ct: -0.785 1452/1452 54% 0% 2.1% 5 0 13%


"WJLA-HD" is a channel name in my channels.conf file. (The first field
on each line is a channel name.)


If [dvb]scan can't a decent channels.conf, either the digital tuner
drivers need work, or you have signal quality problems. Please check
the list of items here, just in case:

http://ivtvdriver.org/index.php/Howto:Improve_signal_quality


Unfortunately my only late model HVR-1600 is in Europe with Hans for
worldwide analog signal tuning verification. I don't have one in hand
at the moment. (Maybe I'll just go buy another one this week).


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
> Unfortunately my only late model HVR-1600 is in Europe with Hans for
> worldwide analog signal tuning verification. I don't have one in hand
> at the moment. (Maybe I'll just go buy another one this week).
>
>
> Regards,
> Andy
>

Hi Andy,

I've been out of circulation for a while and am just catching up on my list
messages now. Any news from Hans on that testing with the 1388?

Also, have you heard anything about the digital tuner on the 1388 being
capable of DVB-S as well?

-Jeff
Re: HVR-1600 analog no signal [ In reply to ]
On Sat, 2011-06-04 at 21:34 -0700, Jeff Campbell wrote:
>
> Unfortunately my only late model HVR-1600 is in Europe with
> Hans for
> worldwide analog signal tuning verification. I don't have one
> in hand
> at the moment. (Maybe I'll just go buy another one this
> week).
>
>
>
> Regards,
> Andy
>
>
> Hi Andy,
>
> I've been out of circulation for a while and am just catching up on my
> list messages now. Any news from Hans on that testing with the 1388?

Hi Jeff,

I know Hans received it on the week of 16 May, but informed me on 31 May
he hadn't tested it yet.

Hans,

Any notion of when you'll be able to verify non-NTSC-M analog TV
standards on the newer HVR-1600?


> Also, have you heard anything about the digital tuner on the 1388
> being capable of DVB-S as well?

Jeff,

Even if the TDA18271 tuner chip can support DVB-S, the CX24228 digital
demodulator on the HVR-1600 does not.

The Conexant CX24228 (aka Samsung S5H1411) digital demodulator can only
demodulate ATSC 8-VSB IAW A/53 and North American cable 64-QAM or
256-QAM IAW SCTE-DVS-031 (aka ANSI/SCTE-07 aka ITU-T J.83 Annex B).

http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=840&partnum=S5H1411&xFmly_id=839
http://atsc.org/cms/standards/a53/a_53-Part-1-6-2007.pdf
http://www.scte.org/documents/pdf/Standards/ANSISCTE072006.pdf


DVB-S is quite different from both of those:

http://www.etsi.org/deliver/etsi_en/300400_300499/300421/01.01.02_60/en_300421v010102p.pdf


If you need a DVB-S/DVB-S2 tuner supported under Linux, I'll point you
to the Wiki as a place to start research:

http://linuxtv.org/wiki/index.php/Hardware_Device_Information


If you need a DVB-T card, the cx18 driver supports the LeadTek DVR 3100
H and, to some degree, the Yuan MPC718. The Yuan PG-718 should also be
be possible.

Regards,
Andy



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
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 ==================
>



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls <awalls@md.metrocast.net> 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
Re: HVR-1600 analog no signal [ In reply to ]
Andy,

Thanks for the pointers! What I'm trying to get working is the unencrypted channels that are available
on my terrestrial digital cable, which are evidently QAM-256.

I used "w_scan -fa -A2 -c US -X -o 7" to generate a channels.conf file. w_scan successfully finds all the
digital channels I expect to see, both HD and SD.  I then use azap to tune, but it seems the audio portion
is missing. The "audio pid" that azap reports is 0x0000:

% azap -c channels.conf -r 'KABC HD'
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 783000000 Hz
video pid 0x1556, audio pid 0x0000
status 07 | signal 0186 | snr 0186 | ber 00000000 | unc 00000000 |
status 1f | signal 0190 | snr 0190 | ber 000000b4 | unc 000000b4 | FE_HAS_LOCK
status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

etc.

dvbtraffic reports this:


-PID--FREQ-----BANDWIDTH-BANDWIDTH-
0000    10 p/s     1 kb/s    16 kbit
1555    15 p/s     2 kb/s    23 kbit
1556  9901 p/s  1817 kb/s 14891 kbit
1557   262 p/s    48 kb/s   394 kbit
1558   133 p/s    24 kb/s   200 kbit
155f    15 p/s     2 kb/s    23 kbit
1560  8998 p/s  1651 kb/s 13532 kbit
1561   260 p/s    47 kb/s   391 kbit
1562   133 p/s    24 kb/s   200 kbit
1569    15 p/s     2 kb/s    23 kbit
156a  4720 p/s   866 kb/s  7099 kbit
156b   309 p/s    56 kb/s   464 kbit
156c   265 p/s    48 kb/s   399 kbit
1aa0     2 p/s     0 kb/s     4 kbit
1aa1     2 p/s     0 kb/s     4 kbit
1aa2     2 p/s     0 kb/s     4 kbit
1aa3     2 p/s     0 kb/s     4 kbit
1ffb     8 p/s     1 kb/s    13 kbit
1fff   892 p/s   163 kb/s  1342 kbit
2000 25956 p/s  4765 kb/s 39038 kbit


Then (as a consequence, I guess) Mplayer says "no audio":

% mplayer /dev/dvb/adapter0/dvr0
MPlayer SVN-r33254-snapshot-4.5.1 (C) 2000-2011 MPlayer Team
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /dev/dvb/adapter0/dvr0.
TS file format detected.
VIDEO MPEG2(pid=5462) NO AUDIO!  NO SUBS (yet)!  PROGRAM N. 0
VIDEO:  MPEG2  1280x720  (aspect 3)  59.940 fps  38810.4 kbps (4851.3 kbyte/s)
Load subtitles in /dev/dvb/adapter0/
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
==========================================================================
Audio: no sound


The HD video playback looks great, however. (I'm not worrying about joystick or LIRC controls at
this point, as this is a desktop PC.)


I don't see any obvious errors in dmesg, except this:


cx18-0: Unreasonably low latency timer, setting to 64 (was 32)


But it looks like the driver automatically fixed that problem.  Hmm, is there supposed to be
a /dev/dvb/adapter0/audio0 file?  All I have is demux0, dvr0, frontend0 and net0.




>________________________________
>From: Andy Walls <awalls@md.metrocast.net>
>To: Greg Fruth <gf20613@yahoo.com>; User discussion about IVTV <ivtv-users@ivtvdriver.org>
>Cc: "gemorgan99@gmail.com" <gemorgan99@gmail.com>; hverkuil@xs4all.nl
>Sent: Saturday, June 4, 2011 5:53 AM
>Subject: Re: [ivtv-users] HVR-1600 analog no signal
>
>On Fri, 2011-06-03 at 23:01 -0700, Greg Fruth wrote:
>> I have the reverse problem in Fedora 14 (HVR-1600 model 1388): the
>> analog side
>> works totally fine (at /dev/video0) while I can't get the digital side
>> to tune properly.
>> The digital side has occasionally been able to record in SD and HD,
>> but since the tuning
>> is wrong Mythtv refuses to record, or it records the wrong program.
>> Does your digital
>> side work?
>
>
>MythTV is not a good troubleshooting tool - too many moving parts, so to
>speak.
>
>Instead, use the basic dvb utilities to create a channels.conf file from
>the stdout of [dvb]scan and do some basic tests:
>
>http://www.linuxtv.org/wiki/index.php/User_Information
>http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
>
>
>You can then put the channels.conf file into ~/.mplayer/channels.conf
>and use mplayer to test DTV:
>
>(kill the mythbackend and then...)
>
>$ mplayer dvb://WJLA-HD -cache 8192
>MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team
>...
>Playing dvb://WJLA-HD.
>dvb_tune Freq: 177028615
>Cache fill: 19.82% (1662976 bytes) 
>TS file format detected.
>VIDEO MPEG2(pid=49) AUDIO A52(pid=52) NO SUBS (yet)!  PROGRAM N. 0
>VIDEO:  MPEG2  1280x720  (aspect 3)  59.940 fps  17782.8 kbps (2222.8 kbyte/s)
>...
>A:28772.1 V:28771.8 A-V:  0.289 ct: -0.785 1452/1452 54%  0%  2.1% 5 0 13%     
>
>
>"WJLA-HD" is a channel name in my channels.conf file. (The first field
>on each line is a channel name.)
>
>
>If [dvb]scan can't a decent channels.conf, either the digital tuner
>drivers need work, or you have signal quality problems.  Please check
>the list of items here, just in case:
>
>http://ivtvdriver.org/index.php/Howto:Improve_signal_quality
>
>
>Unfortunately my only late model HVR-1600 is in Europe with Hans for
>worldwide analog signal tuning verification.  I don't have one in hand
>at the moment.  (Maybe I'll just go buy another one this week).
>
>
>Regards,
>Andy
>
>
>
>
Re: HVR-1600 analog no signal [ In reply to ]
On Sun, 2011-06-05 at 17:25 -0700, Greg Fruth wrote:
> Andy,
>
>
> Thanks for the pointers! What I'm trying to get working is the
> unencrypted channels that are available
> on my terrestrial digital cable, which are evidently QAM-256.

Yes, from what little I've seen, QAM-64 is not used very much.

Note that re-broadcasts of you local Over-The-Air digital channels may
be on the cable as ATSC 8-VSB. Cable companies may choose to not
convert them to QAM.



>
> I used "w_scan -fa -A2 -c US -X -o 7" to generate a channels.conf
> file. w_scan successfully finds all the
> digital channels I expect to see, both HD and SD.

I've never used w_scan myself. Please be advised, that unless you have
a very recent w_scan, ATSC 8-VSB scanning might have problems. See here
for the discussion and fixes, if needed:

http://www.kernellabs.com/blog/?p=1494

I normally use "scandvb" (name may vary with your distro) and a
frequency file:

$ locate 8VSB | grep us
/usr/share/dvb-apps/atsc/us-ATSC-center-frequencies-8VSB
/usr/share/dvb-apps/atsc/us-NTSC-center-frequencies-8VSB

$ locate QAM | grep us
/usr/share/dvb-apps/atsc/us-Cable-EIA-542-HRC-center-frequencies-QAM256
/usr/share/dvb-apps/atsc/us-Cable-EIA-542-IRC-center_frequencies-QAM256
/usr/share/dvb-apps/atsc/us-Cable-HRC-center-frequencies-QAM256
/usr/share/dvb-apps/atsc/us-Cable-IRC-center-frequencies-QAM256
/usr/share/dvb-apps/atsc/us-Cable-Standard-center-frequencies-QAM256



> I then use azap to tune,

Hmmm. I was under the impression that czap was needed for cable QAM
DTV. (I don't have cable myself.) Maybe that matters?


> but it seems the audio portion
> is missing. The "audio pid" that azap reports is 0x0000:

The audio pid should be listed in your channels.conf. Open it up with a
text editor and take a look.


>
>
> % azap -c channels.conf -r 'KABC HD'
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> tuning to 783000000 Hz
> video pid 0x1556, audio pid 0x0000

I'll bet you a $1 that the audio pid is 0x1557. It's just the way
people seem to do things. Just edit the line for 'KABC HD' in your
channels.conf and wing in 0x1557.



> status 07 | signal 0186 | snr 0186 | ber 00000000 | unc 00000000 |
> status 1f | signal 0190 | snr 0190 | ber 000000b4 | unc 000000b4 |
> FE_HAS_LOCK
> status 1f | signal 0190 | snr 0190 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK

You have a lock, that's good.

I see the s5h1411 driver needs some work on proper status reporting of
signal/SNR and BER/unc. Right now, a BER/unc count of 0 is what you
want for error free reception.

> etc.
>
>
> dvbtraffic reports this:

I can eyeball three DTV "channels" on this frequency


> -PID--FREQ-----BANDWIDTH-BANDWIDTH-
> 0000 10 p/s 1 kb/s 16 kbit

> 1555 15 p/s 2 kb/s 23 kbit
> 1556 9901 p/s 1817 kb/s 14891 kbit <--- Video
> 1557 262 p/s 48 kb/s 394 kbit <--- Audio ?
> 1558 133 p/s 24 kb/s 200 kbit

> 155f 15 p/s 2 kb/s 23 kbit
> 1560 8998 p/s 1651 kb/s 13532 kbit <--- Video
> 1561 260 p/s 47 kb/s 391 kbit <--- Audio ?
> 1562 133 p/s 24 kb/s 200 kbit

> 1569 15 p/s 2 kb/s 23 kbit
> 156a 4720 p/s 866 kb/s 7099 kbit <--- Video
> 156b 309 p/s 56 kb/s 464 kbit <--- Audio ?
> 156c 265 p/s 48 kb/s 399 kbit

> 1aa0 2 p/s 0 kb/s 4 kbit
> 1aa1 2 p/s 0 kb/s 4 kbit
> 1aa2 2 p/s 0 kb/s 4 kbit
> 1aa3 2 p/s 0 kb/s 4 kbit

> 1ffb 8 p/s 1 kb/s 13 kbit
> 1fff 892 p/s 163 kb/s 1342 kbit
> 2000 25956 p/s 4765 kb/s 39038 kbit



> Then (as a consequence, I guess) Mplayer says "no audio":

Just hand edit your channels.conf with a good guess for the audio pid.

> % mplayer /dev/dvb/adapter0/dvr0
> MPlayer SVN-r33254-snapshot-4.5.1 (C) 2000-2011 MPlayer Team
> Can't open joystick device /dev/input/js0: No such file or directory
> Can't init input joystick
> mplayer: could not connect to socket
> mplayer: No such file or directory
> Failed to open LIRC support. You will not be able to use your remote
> control.
>
> Playing /dev/dvb/adapter0/dvr0.
> TS file format detected.
> VIDEO MPEG2(pid=5462) NO AUDIO! NO SUBS (yet)! PROGRAM N. 0
> VIDEO: MPEG2 1280x720 (aspect 3) 59.940 fps 38810.4 kbps (4851.3
> kbyte/s)
> Load subtitles in /dev/dvb/adapter0/
> ==========================================================================
> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
> ==========================================================================
> Audio: no sound
>
>
>
> The HD video playback looks great, however. (I'm not worrying about
> joystick or LIRC controls at
> this point, as this is a desktop PC.)
>
>
>
> I don't see any obvious errors in dmesg, except this:

> cx18-0: Unreasonably low latency timer, setting to 64 (was 32)

That's an information message, not an error. No worries....

> But it looks like the driver automatically fixed that problem.

You are free to change the PCI latency for the CX23418 (maximum burst of
PCI clock cycles the CX23418 is allowed to use the PCI bus segment at a
time) to whatever you need using 'setpci'. Most people don't, unless
they really need to tune PCI bus performance.



> Hmm, is there supposed to be
> a /dev/dvb/adapter0/audio0 file?

Nope.

> All I have is demux0, dvr0, frontend0 and net0.


I don't know why your channels.conf doesn't have the correct audio pid.
I'm guessing:

1. w_scan isn't outputing the right channels.conf format for mplayer.
(channels.conf is *not* standardized across apps :( )

2. w_scan has a bug

3. Someone recently introduced a bug into the linux kernel DVB
subsystem, which causes w_scan to miss information. (The media build
process builds the bleeding edge DVB modules.)

4. Your cable service provider is providing the information in some
unexpected manner, or relying on implicit association of the pid
following the video pid.


Regards,
Andy
>
> ______________________________________________________________
> From: Andy Walls <awalls@md.metrocast.net>
> To: Greg Fruth <gf20613@yahoo.com>; User discussion about IVTV
> <ivtv-users@ivtvdriver.org>
> Cc: "gemorgan99@gmail.com" <gemorgan99@gmail.com>;
> hverkuil@xs4all.nl
> Sent: Saturday, June 4, 2011 5:53 AM
> Subject: Re: [ivtv-users] HVR-1600 analog no signal
>
> On Fri, 2011-06-03 at 23:01 -0700, Greg Fruth wrote:
> > I have the reverse problem in Fedora 14 (HVR-1600 model
> 1388): the
> > analog side
> > works totally fine (at /dev/video0) while I can't get the
> digital side
> > to tune properly.
> > The digital side has occasionally been able to record in SD
> and HD,
> > but since the tuning
> > is wrong Mythtv refuses to record, or it records the wrong
> program.
> > Does your digital
> > side work?
>
>
> MythTV is not a good troubleshooting tool - too many moving
> parts, so to
> speak.
>
> Instead, use the basic dvb utilities to create a channels.conf
> file from
> the stdout of [dvb]scan and do some basic tests:
>
> http://www.linuxtv.org/wiki/index.php/User_Information
> http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
>
>
> You can then put the channels.conf file into
> ~/.mplayer/channels.conf
> and use mplayer to test DTV:
>
> (kill the mythbackend and then...)
>
> $ mplayer dvb://WJLA-HD -cache 8192
> MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team
> ...
> Playing dvb://WJLA-HD.
> dvb_tune Freq: 177028615
> Cache fill: 19.82% (1662976 bytes)
> TS file format detected.
> VIDEO MPEG2(pid=49) AUDIO A52(pid=52) NO SUBS (yet)! PROGRAM
> N. 0
> VIDEO: MPEG2 1280x720 (aspect 3) 59.940 fps 17782.8 kbps
> (2222.8 kbyte/s)
> ...
> A:28772.1 V:28771.8 A-V: 0.289 ct: -0.785 1452/1452 54% 0%
> 2.1% 5 0 13%
>
>
> "WJLA-HD" is a channel name in my channels.conf file. (The
> first field
> on each line is a channel name.)
>
>
> If [dvb]scan can't a decent channels.conf, either the digital
> tuner
> drivers need work, or you have signal quality problems.
> Please check
> the list of items here, just in case:
>
> http://ivtvdriver.org/index.php/Howto:Improve_signal_quality
>
>
> Unfortunately my only late model HVR-1600 is in Europe with
> Hans for
> worldwide analog signal tuning verification. I don't have one
> in hand
> at the moment. (Maybe I'll just go buy another one this
> week).
>
>
> Regards,
> Andy




_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
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" <gemorgan99@gmail.com> wrote:
> On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls <awalls@md.metrocast.net>
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
Re: HVR-1600 analog no signal [ In reply to ]
On Mon, Jun 6, 2011 at 6:50 AM, Eric Morgan <gemorgan99@gmail.com> 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" <gemorgan99@gmail.com> wrote:
> > On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls <awalls@md.metrocast.net>
> 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!
Re: HVR-1600 analog no signal [ In reply to ]
Eric Morgan <gemorgan99@gmail.com> wrote:

>On Mon, Jun 6, 2011 at 6:50 AM, Eric Morgan <gemorgan99@gmail.com>
>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" <gemorgan99@gmail.com> wrote:
>> > On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls
><awalls@md.metrocast.net>
>> 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

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
On 06/07/2011 05:32:50 AM, Andy Walls wrote:
> Eric Morgan <gemorgan99@gmail.com> wrote:
>
> >On Mon, Jun 6, 2011 at 6:50 AM, Eric Morgan <gemorgan99@gmail.com>
> >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" <gemorgan99@gmail.com>
> wrote:
> >> > On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls
> ><awalls@md.metrocast.net>
> >> 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
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
Dale Pontius <DEPontius@edgehp.net> wrote:

>On 06/07/2011 05:32:50 AM, Andy Walls wrote:
>> Eric Morgan <gemorgan99@gmail.com> wrote:
>>
>> >On Mon, Jun 6, 2011 at 6:50 AM, Eric Morgan <gemorgan99@gmail.com>
>> >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" <gemorgan99@gmail.com>
>> wrote:
>> >> > On Sun, Jun 5, 2011 at 5:37 AM, Andy Walls
>> ><awalls@md.metrocast.net>
>> >> 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
>ivtv-users@ivtvdriver.org
>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
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
I'll try to unloading and reloading drivers tonight. I'll figure out a
better way to test the cable signal too.

Any idea what's up with a green screen? When I was originally cat'ing
directly from video1 it was black but all the myth recordings are green. I
can try to capture with cat again to see if it's black if it'll help...
On Jun 7, 2011 8:36 AM, "Andy Walls" <awalls@md.metrocast.net> wrote:
Re: HVR-1600 analog no signal [ In reply to ]
On Tue, 2011-06-07 at 13:50 -0700, Eric Morgan wrote:
> I'll try to unloading and reloading drivers tonight. I'll figure out a
> better way to test the cable signal too.

As something that may be worthwhile, you might also wish to try

1. removing all but one capture card from your system (PVR-150 or
HVR-1600 doesn't matter at the moment), and see how well that one card
performs. Make sure it is away from any disk controller or video
graphics cards. (Trying to reduce EMI inside the PC case.)

You might also want to disconnect the coaxial cables and just use a
composite or SVideo source for the test. (Trying to eliminate any
ground loops.)

I'm just guessing that the PVR-150 problems you described may have been
caused by EMI or a grounding problem.



> Any idea what's up with a green screen?

Not really. Since the CX23418 uses YUV (YCrCb) as an intermediate
format before MPEG encoding, a memory region filled with 00 00 00 as YUV
values would end up as dark green (I think).


The red screen is definitely a bad symptom though.


> When I was originally cat'ing directly from video1 it was black but
> all the myth recordings are green. I can try to capture with cat again
> to see if it's black if it'll help...

Nope. Don't bother.

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
On Tue, Jun 7, 2011 at 3:38 PM, Andy Walls <awalls@md.metrocast.net> wrote:

> On Tue, 2011-06-07 at 13:50 -0700, Eric Morgan wrote:
> > I'll try to unloading and reloading drivers tonight. I'll figure out a
> > better way to test the cable signal too.
>
> As something that may be worthwhile, you might also wish to try
>
> 1. removing all but one capture card from your system (PVR-150 or
> HVR-1600 doesn't matter at the moment), and see how well that one card
> performs. Make sure it is away from any disk controller or video
> graphics cards. (Trying to reduce EMI inside the PC case.)
>
> You might also want to disconnect the coaxial cables and just use a
> composite or SVideo source for the test. (Trying to eliminate any
> ground loops.)
>
> I'm just guessing that the PVR-150 problems you described may have been
> caused by EMI or a grounding problem.
>
>
>
> > Any idea what's up with a green screen?
>
> Not really. Since the CX23418 uses YUV (YCrCb) as an intermediate
> format before MPEG encoding, a memory region filled with 00 00 00 as YUV
> values would end up as dark green (I think).
>
>
> The red screen is definitely a bad symptom though.
>
>
> > When I was originally cat'ing directly from video1 it was black but
> > all the myth recordings are green. I can try to capture with cat again
> > to see if it's black if it'll help...
>
> Nope. Don't bother.
>
> Regards,
> Andy
>
>
Ok! I played with the system some tonight and took some notes.

o machine was booted with blacklisted cx18 a day or so ago so shut it down.
o removed the card with the red screen and left the green screen card in its
original slot
o booted, still with cx18 blacklisted.
o loaded cx18 module and captured from the tuner -> BLACK SCREEN
o switched to s-video -> GREEN SCREEN
o removed cx18_alsa and cx18 and reloaded -> Same results as 3 and 4.
o removed this card and put it in the other slot and booted still with cx18
blacklisted
o s-video -> LIGHT GREEN SCREEN
o tuner -> RED SCREEN!
o removed the cx18 modules and reloaded
o s-video -> GREY SCREEN
o tuner -> PICTURE! (Doogie Houser <cringe>)
o switch back to s-video -> BLACK SCREEN
o put card back in other slot and booted blacklisted cx18 and modprobed the
driver
o tuner -> PICTURE!
o s-video -> BLACK SCREEN
o removed coax (straight from cable co.) from card to hook up cable box coax
to card and screen goes BLACK
o Thought to check the input on the cable box.
o Actually plugged cable TV coax into cable box so it would have a signal to
supply it's s-video out
o s-video -> PICTURE!

o reinstalled the 2nd card (so config is the same)
o booted blacklisted still and modprobed
o video0 -> PICTURE!
o video1 tuner -> PINK SCREEN (correctly hooked to cable box)
o video1 s-video -> WHITE SCREEN (correctly hooked to cable box)
o modprobe removed cx18's and reloaded and...
o PICTURE! both cards, tuner and s-video.

So, it seems I can get it working with intervention after rebooting. Are
people having trouble with the red screen appearing intermittently without
being triggered by reboot? I assume this is the big issue you all are
working on with this driver/card combo?

Thanks a ton Andy. I really do appreciate the hard work you all do!

Eric
Re: HVR-1600 analog no signal [ In reply to ]
Hi Andy,

Doing a spot of renovating around the house and had to power my server down
in case I tripped the wrong breaker. To complicate things, I had done the
kernel upgrade from 2.6.38-10-generic to 2.6.38-11-generic but had not
rebooted. When done, I powered the machine up and did my customary stopping
of mythtv-backend, remove cx18_alsa and cx18 and reloading cx18 but one of
my tuners is still red screen.

I pulled the plug completely on the machine in case a complete power down
was needed but with no luck. And I have reverted to the 2.6.38-10-generic
kernel that was working.

I had been operating since Jun 7 (no reboots :) with no problems.

What's the status of the red screen thing. Is there some workaround? Fix? I
had read that there were fixes that were supposed to be included in newer
versions of the kernel but no luck here.

Thanks for any help!
Eric

On Tue, Jun 7, 2011 at 7:07 PM, Eric Morgan <gemorgan99@gmail.com> wrote:

> On Tue, Jun 7, 2011 at 3:38 PM, Andy Walls <awalls@md.metrocast.net>wrote:
>
>> On Tue, 2011-06-07 at 13:50 -0700, Eric Morgan wrote:
>> > I'll try to unloading and reloading drivers tonight. I'll figure out a
>> > better way to test the cable signal too.
>>
>> As something that may be worthwhile, you might also wish to try
>>
>> 1. removing all but one capture card from your system (PVR-150 or
>> HVR-1600 doesn't matter at the moment), and see how well that one card
>> performs. Make sure it is away from any disk controller or video
>> graphics cards. (Trying to reduce EMI inside the PC case.)
>>
>> You might also want to disconnect the coaxial cables and just use a
>> composite or SVideo source for the test. (Trying to eliminate any
>> ground loops.)
>>
>> I'm just guessing that the PVR-150 problems you described may have been
>> caused by EMI or a grounding problem.
>>
>>
>>
>> > Any idea what's up with a green screen?
>>
>> Not really. Since the CX23418 uses YUV (YCrCb) as an intermediate
>> format before MPEG encoding, a memory region filled with 00 00 00 as YUV
>> values would end up as dark green (I think).
>>
>>
>> The red screen is definitely a bad symptom though.
>>
>>
>> > When I was originally cat'ing directly from video1 it was black but
>> > all the myth recordings are green. I can try to capture with cat again
>> > to see if it's black if it'll help...
>>
>> Nope. Don't bother.
>>
>> Regards,
>> Andy
>>
>>
> Ok! I played with the system some tonight and took some notes.
>
> o machine was booted with blacklisted cx18 a day or so ago so shut it down.
> o removed the card with the red screen and left the green screen card in
> its original slot
> o booted, still with cx18 blacklisted.
> o loaded cx18 module and captured from the tuner -> BLACK SCREEN
> o switched to s-video -> GREEN SCREEN
> o removed cx18_alsa and cx18 and reloaded -> Same results as 3 and 4.
> o removed this card and put it in the other slot and booted still with cx18
> blacklisted
> o s-video -> LIGHT GREEN SCREEN
> o tuner -> RED SCREEN!
> o removed the cx18 modules and reloaded
> o s-video -> GREY SCREEN
> o tuner -> PICTURE! (Doogie Houser <cringe>)
> o switch back to s-video -> BLACK SCREEN
> o put card back in other slot and booted blacklisted cx18 and modprobed the
> driver
> o tuner -> PICTURE!
> o s-video -> BLACK SCREEN
> o removed coax (straight from cable co.) from card to hook up cable box
> coax to card and screen goes BLACK
> o Thought to check the input on the cable box.
> o Actually plugged cable TV coax into cable box so it would have a signal
> to supply it's s-video out
> o s-video -> PICTURE!
>
> o reinstalled the 2nd card (so config is the same)
> o booted blacklisted still and modprobed
> o video0 -> PICTURE!
> o video1 tuner -> PINK SCREEN (correctly hooked to cable box)
> o video1 s-video -> WHITE SCREEN (correctly hooked to cable box)
> o modprobe removed cx18's and reloaded and...
> o PICTURE! both cards, tuner and s-video.
>
> So, it seems I can get it working with intervention after rebooting. Are
> people having trouble with the red screen appearing intermittently without
> being triggered by reboot? I assume this is the big issue you all are
> working on with this driver/card combo?
>
> Thanks a ton Andy. I really do appreciate the hard work you all do!
>
> Eric
>
Re: HVR-1600 analog no signal [ In reply to ]
Eric Morgan <gemorgan99@gmail.com> wrote:

>Hi Andy,
>
>Doing a spot of renovating around the house and had to power my server
>down
>in case I tripped the wrong breaker. To complicate things, I had done
>the
>kernel upgrade from 2.6.38-10-generic to 2.6.38-11-generic but had not
>rebooted. When done, I powered the machine up and did my customary
>stopping
>of mythtv-backend, remove cx18_alsa and cx18 and reloading cx18 but one
>of
>my tuners is still red screen.
>
>I pulled the plug completely on the machine in case a complete power
>down
>was needed but with no luck. And I have reverted to the
>2.6.38-10-generic
>kernel that was working.
>
>I had been operating since Jun 7 (no reboots :) with no problems.
>
>What's the status of the red screen thing. Is there some workaround?
>Fix? I
>had read that there were fixes that were supposed to be included in
>newer
>versions of the kernel but no luck here.
>
>Thanks for any help!
>Eric
>
>On Tue, Jun 7, 2011 at 7:07 PM, Eric Morgan <gemorgan99@gmail.com>
>wrote:
>
>> On Tue, Jun 7, 2011 at 3:38 PM, Andy Walls
><awalls@md.metrocast.net>wrote:
>>
>>> On Tue, 2011-06-07 at 13:50 -0700, Eric Morgan wrote:
>>> > I'll try to unloading and reloading drivers tonight. I'll figure
>out a
>>> > better way to test the cable signal too.
>>>
>>> As something that may be worthwhile, you might also wish to try
>>>
>>> 1. removing all but one capture card from your system (PVR-150 or
>>> HVR-1600 doesn't matter at the moment), and see how well that one
>card
>>> performs. Make sure it is away from any disk controller or video
>>> graphics cards. (Trying to reduce EMI inside the PC case.)
>>>
>>> You might also want to disconnect the coaxial cables and just use a
>>> composite or SVideo source for the test. (Trying to eliminate any
>>> ground loops.)
>>>
>>> I'm just guessing that the PVR-150 problems you described may have
>been
>>> caused by EMI or a grounding problem.
>>>
>>>
>>>
>>> > Any idea what's up with a green screen?
>>>
>>> Not really. Since the CX23418 uses YUV (YCrCb) as an intermediate
>>> format before MPEG encoding, a memory region filled with 00 00 00 as
>YUV
>>> values would end up as dark green (I think).
>>>
>>>
>>> The red screen is definitely a bad symptom though.
>>>
>>>
>>> > When I was originally cat'ing directly from video1 it was black
>but
>>> > all the myth recordings are green. I can try to capture with cat
>again
>>> > to see if it's black if it'll help...
>>>
>>> Nope. Don't bother.
>>>
>>> Regards,
>>> Andy
>>>
>>>
>> Ok! I played with the system some tonight and took some notes.
>>
>> o machine was booted with blacklisted cx18 a day or so ago so shut it
>down.
>> o removed the card with the red screen and left the green screen card
>in
>> its original slot
>> o booted, still with cx18 blacklisted.
>> o loaded cx18 module and captured from the tuner -> BLACK SCREEN
>> o switched to s-video -> GREEN SCREEN
>> o removed cx18_alsa and cx18 and reloaded -> Same results as 3 and 4.
>> o removed this card and put it in the other slot and booted still
>with cx18
>> blacklisted
>> o s-video -> LIGHT GREEN SCREEN
>> o tuner -> RED SCREEN!
>> o removed the cx18 modules and reloaded
>> o s-video -> GREY SCREEN
>> o tuner -> PICTURE! (Doogie Houser <cringe>)
>> o switch back to s-video -> BLACK SCREEN
>> o put card back in other slot and booted blacklisted cx18 and
>modprobed the
>> driver
>> o tuner -> PICTURE!
>> o s-video -> BLACK SCREEN
>> o removed coax (straight from cable co.) from card to hook up cable
>box
>> coax to card and screen goes BLACK
>> o Thought to check the input on the cable box.
>> o Actually plugged cable TV coax into cable box so it would have a
>signal
>> to supply it's s-video out
>> o s-video -> PICTURE!
>>
>> o reinstalled the 2nd card (so config is the same)
>> o booted blacklisted still and modprobed
>> o video0 -> PICTURE!
>> o video1 tuner -> PINK SCREEN (correctly hooked to cable box)
>> o video1 s-video -> WHITE SCREEN (correctly hooked to cable box)
>> o modprobe removed cx18's and reloaded and...
>> o PICTURE! both cards, tuner and s-video.
>>
>> So, it seems I can get it working with intervention after rebooting.
>Are
>> people having trouble with the red screen appearing intermittently
>without
>> being triggered by reboot? I assume this is the big issue you all
>are
>> working on with this driver/card combo?
>>
>> Thanks a ton Andy. I really do appreciate the hard work you all do!
>>
>> Eric
>>

Hi Eric,

My hypothesis is that the CX23418 firmware needs to be loaded shortly after bringing the chip up.

Currently the driver bring the chip up and defers firmware loading; which probably leaves the chip executing random garbage that might screw up registers in the integrated CX25843.

I have had no time to implement that change and test it. However you can initiate the firmware load from userspace by opening a device node and performing an operation with v4l2-ctl or ivtv-tune or cat shortly after the driver loads.
Note this "workaround" probably won't help with the newest HVR1600s that have the new analog tuner with the long calibration delay.

Regards,
Andy

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: HVR-1600 analog no signal [ In reply to ]
When you say "newest", how new? Mine are both ones of the "newer" models
but I don't think they are the newest...

Thanks!
-
Eric



On Mon, Sep 19, 2011 at 3:30 AM, Andy Walls <awalls@md.metrocast.net> wrote:

> Eric Morgan <gemorgan99@gmail.com> wrote:
>
> >Hi Andy,
> >
> >Doing a spot of renovating around the house and had to power my server
> >down
> >in case I tripped the wrong breaker. To complicate things, I had done
> >the
> >kernel upgrade from 2.6.38-10-generic to 2.6.38-11-generic but had not
> >rebooted. When done, I powered the machine up and did my customary
> >stopping
> >of mythtv-backend, remove cx18_alsa and cx18 and reloading cx18 but one
> >of
> >my tuners is still red screen.
> >
> >I pulled the plug completely on the machine in case a complete power
> >down
> >was needed but with no luck. And I have reverted to the
> >2.6.38-10-generic
> >kernel that was working.
> >
> >I had been operating since Jun 7 (no reboots :) with no problems.
> >
> >What's the status of the red screen thing. Is there some workaround?
> >Fix? I
> >had read that there were fixes that were supposed to be included in
> >newer
> >versions of the kernel but no luck here.
> >
> >Thanks for any help!
> >Eric
> >
> >On Tue, Jun 7, 2011 at 7:07 PM, Eric Morgan <gemorgan99@gmail.com>
> >wrote:
> >
> >> On Tue, Jun 7, 2011 at 3:38 PM, Andy Walls
> ><awalls@md.metrocast.net>wrote:
> >>
> >>> On Tue, 2011-06-07 at 13:50 -0700, Eric Morgan wrote:
> >>> > I'll try to unloading and reloading drivers tonight. I'll figure
> >out a
> >>> > better way to test the cable signal too.
> >>>
> >>> As something that may be worthwhile, you might also wish to try
> >>>
> >>> 1. removing all but one capture card from your system (PVR-150 or
> >>> HVR-1600 doesn't matter at the moment), and see how well that one
> >card
> >>> performs. Make sure it is away from any disk controller or video
> >>> graphics cards. (Trying to reduce EMI inside the PC case.)
> >>>
> >>> You might also want to disconnect the coaxial cables and just use a
> >>> composite or SVideo source for the test. (Trying to eliminate any
> >>> ground loops.)
> >>>
> >>> I'm just guessing that the PVR-150 problems you described may have
> >been
> >>> caused by EMI or a grounding problem.
> >>>
> >>>
> >>>
> >>> > Any idea what's up with a green screen?
> >>>
> >>> Not really. Since the CX23418 uses YUV (YCrCb) as an intermediate
> >>> format before MPEG encoding, a memory region filled with 00 00 00 as
> >YUV
> >>> values would end up as dark green (I think).
> >>>
> >>>
> >>> The red screen is definitely a bad symptom though.
> >>>
> >>>
> >>> > When I was originally cat'ing directly from video1 it was black
> >but
> >>> > all the myth recordings are green. I can try to capture with cat
> >again
> >>> > to see if it's black if it'll help...
> >>>
> >>> Nope. Don't bother.
> >>>
> >>> Regards,
> >>> Andy
> >>>
> >>>
> >> Ok! I played with the system some tonight and took some notes.
> >>
> >> o machine was booted with blacklisted cx18 a day or so ago so shut it
> >down.
> >> o removed the card with the red screen and left the green screen card
> >in
> >> its original slot
> >> o booted, still with cx18 blacklisted.
> >> o loaded cx18 module and captured from the tuner -> BLACK SCREEN
> >> o switched to s-video -> GREEN SCREEN
> >> o removed cx18_alsa and cx18 and reloaded -> Same results as 3 and 4.
> >> o removed this card and put it in the other slot and booted still
> >with cx18
> >> blacklisted
> >> o s-video -> LIGHT GREEN SCREEN
> >> o tuner -> RED SCREEN!
> >> o removed the cx18 modules and reloaded
> >> o s-video -> GREY SCREEN
> >> o tuner -> PICTURE! (Doogie Houser <cringe>)
> >> o switch back to s-video -> BLACK SCREEN
> >> o put card back in other slot and booted blacklisted cx18 and
> >modprobed the
> >> driver
> >> o tuner -> PICTURE!
> >> o s-video -> BLACK SCREEN
> >> o removed coax (straight from cable co.) from card to hook up cable
> >box
> >> coax to card and screen goes BLACK
> >> o Thought to check the input on the cable box.
> >> o Actually plugged cable TV coax into cable box so it would have a
> >signal
> >> to supply it's s-video out
> >> o s-video -> PICTURE!
> >>
> >> o reinstalled the 2nd card (so config is the same)
> >> o booted blacklisted still and modprobed
> >> o video0 -> PICTURE!
> >> o video1 tuner -> PINK SCREEN (correctly hooked to cable box)
> >> o video1 s-video -> WHITE SCREEN (correctly hooked to cable box)
> >> o modprobe removed cx18's and reloaded and...
> >> o PICTURE! both cards, tuner and s-video.
> >>
> >> So, it seems I can get it working with intervention after rebooting.
> >Are
> >> people having trouble with the red screen appearing intermittently
> >without
> >> being triggered by reboot? I assume this is the big issue you all
> >are
> >> working on with this driver/card combo?
> >>
> >> Thanks a ton Andy. I really do appreciate the hard work you all do!
> >>
> >> Eric
> >>
>
> Hi Eric,
>
> My hypothesis is that the CX23418 firmware needs to be loaded shortly after
> bringing the chip up.
>
> Currently the driver bring the chip up and defers firmware loading; which
> probably leaves the chip executing random garbage that might screw up
> registers in the integrated CX25843.
>
> I have had no time to implement that change and test it. However you can
> initiate the firmware load from userspace by opening a device node and
> performing an operation with v4l2-ctl or ivtv-tune or cat shortly after the
> driver loads.
> Note this "workaround" probably won't help with the newest HVR1600s that
> have the new analog tuner with the long calibration delay.
>
> Regards,
> Andy
>
Re: HVR-1600 analog no signal [ In reply to ]
>
> Hi Eric,
>
> My hypothesis is that the CX23418 firmware needs to be loaded shortly after
> bringing the chip up.
>
> Currently the driver bring the chip up and defers firmware loading; which
> probably leaves the chip executing random garbage that might screw up
> registers in the integrated CX25843.
>
> I have had no time to implement that change and test it. However you can
> initiate the firmware lohttp://www.google.com/ad from userspace by opening
> a device node and performing an operation with v4l2-ctl or ivtv-tune or cat
> shortly after the driver loads.
> Note this "workaround" probably won't help with the newest HVR1600s that
> have the new analog tuner with the long calibration delay.
>
> Regards,
> Andy
>


I was able to get running again by re-compiling the latest drivers from git.
I don't have high confidence yet since my older drivers were working but
then wouldn't. Keeping fingers crossed.

Thanks for the help again...

-
Eric
Re: HVR-1600 analog no signal [ In reply to ]
On Sun, 2011-09-25 at 12:28 -0700, Eric Morgan wrote:
> Hi Eric,
>
> My hypothesis is that the CX23418 firmware needs to be loaded
> shortly after bringing the chip up.
>
> Currently the driver bring the chip up and defers firmware
> loading; which probably leaves the chip executing random
> garbage that might screw up registers in the integrated
> CX25843.
>
> I have had no time to implement that change and test it.
> However you can initiate the firmware
> lohttp://www.google.com/ad from userspace by opening a device
> node and performing an operation with v4l2-ctl or ivtv-tune or
> cat shortly after the driver loads.
> Note this "workaround" probably won't help with the newest
> HVR1600s that have the new analog tuner with the long
> calibration delay.
>
> Regards,
> Andy
>
>
>
> I was able to get running again by re-compiling the latest drivers
> from git. I don't have high confidence yet since my older drivers were
> working but then wouldn't. Keeping fingers crossed.

Hi,

Sorry for the late reply on the firmware question.

I don't have high hopes for the new driver "making it all better".
Since the red-screen, if it happens, happens at boot. A power cycle is
needed to clear it.

This really indicates the cx18 driver is racing with the CX23418
hardware or with the cx18 driver itself somehow. Nothing has changed
with the driver init sequence in a long time.

> Thanks for the help again...

If I find time to change the driver to load the firmware early, I'll
email that I need a patch tested. Hopefully sometime in October....

Regards,
Andy



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users