From: Nuno Silva <nuno.silva@vgertech.com>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Michael Buesch <mbuesch@freenet.de>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [2.6-test7] [bttv] lots of warning/error messages
Date: Sat, 11 Oct 2003 05:32:10 +0100 [thread overview]
Message-ID: <3F8787CA.3030607@vgertech.com> (raw)
In-Reply-To: <20031010090955.GE32386@bytesex.org>
Hi!
Gerd Knorr wrote:
>>get lots of warning/error messages from the bttv driver.
>>Here are todays messages:
>>
>>Oct 9 15:51:13 lfs kernel: bttv0: skipped frame. no signal? high irq latency?
>>Oct 9 15:57:57 lfs kernel: bttv0: OCERR @ 1fd95000,bits: HSYNC OFLOW OCERR*
>
>
> Hmm. Is the signal good?
>
[..snip..]
I *had* the same problem. It's was not the signal so I persued the other
hint: "high irq latency?"
I opened the box and saw the NIC in slot 2 and winTV in slot3 and
switched them. Never saw this message again :)
In 2.6.0-test7 zapping (a tv viewer) doesn't work in "capture" mode.
-----------------
Console started, stardate Sat Oct 11 05:26:35 2003
Please tell the maintainer about any bugs you find.
Error: capture.c (870) [capture_start]:
Couldn't start capture: no capture format available
Error: callbacks.c (156) [switch_mode]:
[tveng25.c] tveng25_set_capture_format (line 932)
VIDIOC_S_FMT failed: Device or resource busy
-----------------
xawtv doesn't work, in grabdisplay mode, either.
(overlay is fine on both)
They work with 2.6.0-test4, at least.
Any hints on this one? Can I provide more information?
Thanks,
Nuno Silva
next prev parent reply other threads:[~2003-10-11 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 15:29 [2.6-test7] [bttv] lots of warning/error messages Michael Buesch
2003-10-10 9:09 ` Gerd Knorr
2003-10-10 16:51 ` Michael Buesch
2003-10-11 4:32 ` Nuno Silva [this message]
2003-10-11 18:10 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F8787CA.3030607@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox