From: "Jürgen Hein" <jurhein@gmx.de>
To: linux-media@vger.kernel.org
Subject: Current drivers for Hauppauge NOVA-S Plus broken (?)
Date: Tue, 31 Jan 2012 12:39:31 +0100 [thread overview]
Message-ID: <1328009971.2853.9.camel@Zweitbox> (raw)
Hallo,
with the current drivers from media_build_experimental for hauppauge
NOVA-S Plus (Conexant 2388x (bt878 successor) support (VIDEO_CX88)
cx8800...)does this here not more. Picture and sound with significant
dropouts.
Log:
Jan 16 12:00:28 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:28 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:31 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:31 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:34 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:34 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:37 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:37 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:40 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:40 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:43 debian vdr: [2497] frontend 2/0 lost lock on channel
580, tp 111758
Jan 16 12:00:43 debian vdr: [2497] frontend 2/0 regained lock on channel
580, tp 111758
Jan 16 12:00:49 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:00:49 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:00:52 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:00:52 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:00:55 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:00:55 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:00:58 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:00:58 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:01:01 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:01:01 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:01:04 debian vdr: [2497] frontend 2/0 lost lock on channel 2,
tp 111836
Jan 16 12:01:04 debian vdr: [2497] frontend 2/0 regained lock on channel
2, tp 111836
Jan 16 12:01:10 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:10 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
Jan 16 12:01:13 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:13 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
Jan 16 12:01:16 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:16 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
Jan 16 12:01:19 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:19 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
Jan 16 12:01:22 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:22 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
Jan 16 12:01:25 debian vdr: [2497] frontend 2/0 lost lock on channel
101, tp 112031
Jan 16 12:01:25 debian vdr: [2497] frontend 2/0 regained lock on channel
101, tp 112031
ff..
With the drivers of 11.2011 is working properly.
(Excuse me, but I am speaking no english)
THX
next reply other threads:[~2012-01-31 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 11:39 Jürgen Hein [this message]
2012-02-04 9:22 ` Current drivers for Hauppauge NOVA-S Plus broken (?) Jürgen Hein
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=1328009971.2853.9.camel@Zweitbox \
--to=jurhein@gmx.de \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.