On Sat, 7 Jan 2006, Hans Verkuil wrote:
> You are using the 0.4.0 ivtvctl with a 0.4.1 or later ivtv driver. Make
> sure you are using matching ivtvctl and ivtv driver! (ivtvctl --version
> reports the ivtv version for which it is compiled).
Right! However:
# /opt/ivtv/sbin/ivtvctl --version
ivtvctl version 0.4.2 (development revision 3101)
# /opt/ivtv/sbin/ivtvctl -I
check SAA7115 input signal
ioctl: Input detect failed (cannot read SAA regs)
ioctl: Input detect failed (cannot read SAA regs)
ioctl: VIDEO_STATUS = Bad
SAA7115 reg[STATUS#1 - 0x1E] = 177ff8e
Color Standard (D0-D1): PAL
White peak loop (D2): Activated
Gain value for act.lum. (min) (D3): Limited
Gain value for act.lum. (max) (D4): Not limited
WIPA-mode slow-time constant (D5): Not activated
Horizontal frequency (D6): Locked
Field length (D7): Standard
SAA7115 reg[STATUS#2 - 0x1F] = 177ff8e
Ready for capture (D0): No
Macrovision 7.01 (D1): Yes
MV Colorstripe burst (D2): Yes
MV Colorstripe burst type 3 (D3): Yes
Input signal timebase (D4): Non-stable (VCR)
Field frequency (D5): 50Hz
H & V loops (D6): Locked
Interlace (D7): Detected
The reg status look ok now, why is VIDEO_STATUS still bad?
Please note that I use PREFIX=/opt/ivtv and BINDIR=$(PREFIX)/sbin
compiling the utils. To change channels, set quality etc., I use my
own scripts located in /opt/ivtv/bin. All scripts have the line
export PATH=/opt/ivtv/sbin:/opt/ivtv/bin:${PATH}
to use the ivtv utils installed in /opt/ivtv/sbin.
I usually never run ivtvctl or any other utility manually,
so I forgot to specify the path and used the SuSE rpm
versions (ivtv-0.3.7c-3) from /usr/bin. Sorry about that!
To eliminate any further path conflicts, I've just removed the
rpm. I don't need it anyways.
Now, despite the path problems, the pvr350 is still broken.
Is there anything I can do/run/test for further diagnosis?
Regards, Walter
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
