From: Antti Palosaari <crope@iki.fi>
To: Radoslaw Moszczynski <r.moszczynsk@samsung.com>
Cc: linux-media@vger.kernel.org
Subject: Re: PcTV Nanostick 290e -- DVB-C frontend only working after reconnecting the device
Date: Wed, 16 Jan 2013 16:37:08 +0200 [thread overview]
Message-ID: <50F6BB14.40302@iki.fi> (raw)
In-Reply-To: <016601cdf3f1$9e7925e0$db6b71a0$%moszczynsk@samsung.com>
On 01/16/2013 03:58 PM, Radoslaw Moszczynski wrote:
> Hi,
>
> I'm not sure if this has been already reported, but I was playing around
> with Nanostick 290e today and I encountered some weird behavior with the
> DVB-C frontend.
>
> The DVB-C frontend only seems to work once after plugging in the device.
> During subsequent uses, it fails to lock on to signal. However, you can
> unplug the Nanostick, plug it back in, and it is able to lock on again. But
> only once -- then you have to replug it again.
>
> The exact actions that I took:
>
> 1. Plug in the Nanostick.
> 2. Run dvbstream to record a DVB-C stream -- works OK.
> 3. Run dvbstream to record a DVB-C stream again -- fail to lock on signal.
> 4. Unplug the Nanostick. Plug it back in.
> 5. Run dvbstream to record a DVB-C stream -- works OK.
> 6. Run dvbstream to record a DVB-C stream again -- fail to lock on signal.
>
> I'm using kernel 3.2.0 on Ubuntu x86. The DVB-T/T2 frontend doesn't display
> this behavior.
>
> If anyone's interested in debugging this, I'll be happy to provide more
> information.
Could you test first quite latest Kernel, 3.7 or even 3.8. If 3.7
behaves similarly, then test older Kernel 3.0.
Working only on first tuning attempt sounds like it should not be common
problem - otherwise there should be million bug reports like that.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-01-16 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:58 PcTV Nanostick 290e -- DVB-C frontend only working after reconnecting the device Radoslaw Moszczynski
2013-01-16 14:37 ` Antti Palosaari [this message]
2013-01-16 15:15 ` Radoslaw Moszczynski
2013-01-16 15:27 ` Antti Palosaari
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=50F6BB14.40302@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=r.moszczynsk@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).