On 01/16/2013 05:15 PM, Radoslaw Moszczynski wrote:
With Ubuntu's 3.5 kernel, the DVB-C frontend is not registered at all --
only DVB-T/T2 is available.
I'll do some more testing with newer/older kernels over the next few days.
That is because of changed functionality, multi-frontend to
single-frontend. As now there is only one frontend which supports all
the standards. You should set desired standard using tool:
$ dvb-fe-tool --set-delsys=DVBC/ANNEX_A
I am not a big fan of that new method of setting frontend type,
especially because there is now both old and new ways offered. That new
method dropped also way to tell supported frontend capabilities to the
userspace (anyway, almost all demods support all capabilities defined by
standard, so it is not a big loss).
regards
Antti
Regards-
-Radek
-----Original Message-----
From: Antti Palosaari [mailto:crope@xxxxxx]
Sent: Wednesday, January 16, 2013 3:37 PM
To: Radoslaw Moszczynski
Cc: linux-media@xxxxxxxxxxxxxxx
Subject: Re: PcTV Nanostick 290e -- DVB-C frontend only working after
reconnecting the device
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/
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
