From: Paul Shepherd <paul@whitelands.org.uk>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Tevii S660 USB card and dw2102 module generating RC messages
Date: Fri, 16 Apr 2010 08:31:43 +0100 [thread overview]
Message-ID: <4BC8125F.6000203@whitelands.org.uk> (raw)
I have a Tevii S660 (a usb dvb-s2 device) which is causing a problem.
After the S660 is attached to a USB 2 socket, the firmware is d/l and
everything looks fine but then there are continual RC (check/debug?)
messages every 150 ms, then some time later everything goes pear shaped,
see http://pastebin.com/r9DtUaqX
Tevii think the h/w is ok as it works in a Windows box with their
myTevii application. It does work with Ubuntu while the RC messages are
occurring, I can watch and record SD+HD content in mythtv until the crash.
I have tried the latest tevii beta s/w (v4l and .fw files) and also the
v4l-dvb drivers from linuxtv dated 6 april - the same result each time.
I can see in the dw2102.c where 150ms is defined and this seems the
same as other devices in the code.
Google suggests that others have seen the problem but it's not clear
what the solution is.
Three questions:
1) are the RC messages caused by a h/w or s/w issue?
2) if its s/w what do I need to do?
3) is the subsequent khubd crash related and how do I fix that?
I have a nova dvb-t usb box connected and that works fine - I assume
there's no interaction.
I am running Ubuntu 9.10 with the following kernel:
Linux antec300.home.org 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8
09:05:19 UTC 2010 i686 GNU/Linux
thanks for any suggestions, paul
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
reply other threads:[~2010-04-16 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BC8125F.6000203@whitelands.org.uk \
--to=paul@whitelands.org.uk \
--cc=linux-dvb@linuxtv.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox