Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen. This happens in most cases when the signal of the tv antenna is down or very weak. I haven't been able to decipher this error message. Is there a way to capture this message? I could then present it to the experts and see how I can get rid of this message. Pressing on the OK button at the far end of the message will kill the message but I would like to be free of it.
On 11/17/05, C. Brouerius van Nidek
Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen. This happens in most cases when the signal of the tv antenna is down or very weak.
I haven't been able to decipher this error message. Is there a way to capture this message? I could then present it to the experts and see how I can get rid of this message. Pressing on the OK button at the far end of the message will kill the message but I would like to be free of it.
Try to start xawtv with the -debug switch an specifiy the desired
debug level, e.g. 5:
% xawtv -debug 5
This produces a large number of output lines which you may want to
redirect to a file. It should then capture the message and other
important details as well.
\Steve
--
Steve Graegert
On Friday 18 November 2005 00:50, Steve Graegert wrote:
On 11/17/05, C. Brouerius van Nidek
wrote: Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen.
Try to start xawtv with the -debug switch an specifiy the desired debug level, e.g. 5:
% xawtv -debug 5
This produces a large number of output lines which you may want to redirect to a file. It should then capture the message and other important details as well.
Steve, Thanks for the tip. Trying out following command I do get a lot of info but nothing in the lof file that is in my /home. Something wrong with the log capturing command part? xawtv4 -debug 5 > /home/cons/tv.log
On 11/18/05, C. Brouerius van Nidek
On Friday 18 November 2005 00:50, Steve Graegert wrote:
On 11/17/05, C. Brouerius van Nidek
wrote: Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen.
Try to start xawtv with the -debug switch an specifiy the desired debug level, e.g. 5:
% xawtv -debug 5
This produces a large number of output lines which you may want to redirect to a file. It should then capture the message and other important details as well.
Steve, Thanks for the tip. Trying out following command I do get a lot of info but nothing in the lof file that is in my /home. Something wrong with the log capturing command part?
xawtv4 -debug 5 > /home/cons/tv.log
Try this:
% xawtv4 -debug 5 &> /home/cons/tv.log
Now, output to stdout and stderr is redirected to tv.log. Could have
mentioned that in the first place. Sorry for the invoncenience.
\Steve
--
Steve Graegert
On Friday 18 November 2005 16:35, Steve Graegert wrote:
On 11/18/05, C. Brouerius van Nidek
wrote: On Friday 18 November 2005 00:50, Steve Graegert wrote:
On 11/17/05, C. Brouerius van Nidek
wrote: Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen.
Try to start xawtv with the -debug switch an specifiy the desired debug level, e.g. 5:
% xawtv -debug 5
This produces a large number of output lines which you may want to redirect to a file. It should then capture the message and other important details as well.
Steve, Thanks for the tip. Trying out following command I do get a lot of info but nothing in the lof file that is in my /home. Something wrong with the log capturing command part?
xawtv4 -debug 5 > /home/cons/tv.log
Try this:
% xawtv4 -debug 5 &> /home/cons/tv.log
Now, output to stdout and stderr is redirected to tv.log. Could have mentioned that in the first place. Sorry for the invoncenience.
Only a missing ampersand ;( But by letting the debugging running I had in the meantime the same error message but now in a normal format. Message reads: ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown): Input/output error This line is written without line breaks and gives the extra long error message. Now to find out what really happens. Just Google away unless somebody can give me offhand an answer
On 11/18/05, C. Brouerius van Nidek
On Friday 18 November 2005 16:35, Steve Graegert wrote:
On 11/18/05, C. Brouerius van Nidek
wrote: On Friday 18 November 2005 00:50, Steve Graegert wrote:
On 11/17/05, C. Brouerius van Nidek
wrote: Using xawtv4 in my kde desktop I sometimes get an error message which is two times longer then the width of my screen.
Try to start xawtv with the -debug switch an specifiy the desired debug level, e.g. 5:
% xawtv -debug 5
This produces a large number of output lines which you may want to redirect to a file. It should then capture the message and other important details as well.
Steve, Thanks for the tip. Trying out following command I do get a lot of info but nothing in the lof file that is in my /home. Something wrong with the log capturing command part?
xawtv4 -debug 5 > /home/cons/tv.log
Try this:
% xawtv4 -debug 5 &> /home/cons/tv.log
Now, output to stdout and stderr is redirected to tv.log. Could have mentioned that in the first place. Sorry for the invoncenience.
Only a missing ampersand ;(
But by letting the debugging running I had in the meantime the same error message but now in a normal format.
Message reads:
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown): Input/output error
What I read from this message is that an empty buffer of type
v4l2_buffer is passed from the application to the driver or vice
versa. It should obviously carry some useful data which it does not.
Unless you know how to trace down this error and fix it, I'd recommend
contacting the author and filing a bug or something.
\Steve
--
Steve Graegert
On Friday 18 November 2005 18:39, Steve Graegert wrote:
On 11/18/05, C. Brouerius van Nidek
wrote: On Friday 18 November 2005 16:35, Steve Graegert wrote:
On 11/18/05, C. Brouerius van Nidek
wrote: On Friday 18 November 2005 00:50, Steve Graegert wrote:
On 11/17/05, C. Brouerius van Nidek
wrote: Using xawtv4 in my kde desktop I sometimes get an error message
What I read from this message is that an empty buffer of type v4l2_buffer is passed from the application to the driver or vice versa. It should obviously carry some useful data which it does not.
Unless you know how to trace down this error and fix it, I'd recommend contacting the author and filing a bug or something.
Steve Just what I am planning to do ;) Thanks
participants (2)
-
C. Brouerius van Nidek
-
Steve Graegert