linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russel Winder <russel@winder.org.uk>
To: DVB_Linux_Media <linux-media@vger.kernel.org>
Subject: Re: PCTV 292e weirdness
Date: Sat, 13 Feb 2016 11:04:37 +0000	[thread overview]
Message-ID: <1455361477.1704.11.camel@winder.org.uk> (raw)
In-Reply-To: <1454523447.1970.15.camel@itzinteractive.com>

[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]

From what I can see, this problem has gone away – hopefully
permanently.

As far as I can tell the only change is that there has been a firmware
file update at git@github.com:OpenELEC/dvb-firmware.git that reverts
4.0.19 to 4.0.11

On Wed, 2016-02-03 at 18:17 +0000, Russel Winder wrote:
> I am fairly sure I didn't see this before, but then I am not sure I
> have a new kernel, libdvbv5 or dvbtools. Also people are bad
> witnesses.
> However, if I plug the device in I can either scan with it or tune
> it,
> but only once thereafter it goes into "won't do anything so there"
> mode. For example:
> 
> 
> > > dvbv5-zap -c save_channels.conf "BBC NEWS"
> using demux '/dev/dvb/adapter0/demux0'
> reading channels from file 'save_channels.conf'
> service has pid type 05:  7270
> tuning to 490000000 Hz
> video pid 501
>   dvb_set_pesfilter 501
> audio pid 502
>   dvb_set_pesfilter 502
>        (0x00)
> Lock   (0x1f) Signal= -51.00dBm C/N= 23.50dB
> 582 anglides:~/Repositories/Git/Git/Me-TV (git:master)
> > > dvbv5-zap -c save_channels.conf "BBC NEWS"
> using demux '/dev/dvb/adapter0/demux0'
> reading channels from file 'save_channels.conf'
> service has pid type 05:  7270
> tuning to 490000000 Hz
> video pid 501
>   dvb_set_pesfilter 501
> audio pid 502
>   dvb_set_pesfilter 502
>        (0x00) C/N= 23.50dB
>        (0x00) Signal= -67.00dBm C/N= 23.50dB
>        (0x00) Signal= -67.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
>        (0x00) Signal= -109.00dBm C/N= 23.50dB
> 
> 
> If I use a PCTV 282e this does not happen. As far as I can tell there
> has been no change of firmware either, and yet…
> 
> 
-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2016-02-13 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 18:17 PCTV 292e weirdness Russel Winder
2016-02-04 16:14 ` Antti Palosaari
2016-02-04 19:06   ` Russel Winder
2016-02-05  9:40     ` Rune Petersen
2016-02-05 19:07       ` Torbjorn Jansson
2016-02-07 21:26       ` Antti Palosaari
2016-02-08  8:46       ` Russel Winder
2016-02-13 11:04 ` Russel Winder [this message]
2016-02-14 17:10   ` 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=1455361477.1704.11.camel@winder.org.uk \
    --to=russel@winder.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).