All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: Peter Fassberg <pf@leissner.se>
Cc: linux-media@vger.kernel.org
Subject: Re: PCTV Triplestick and Raspberry Pi B+
Date: Sun, 05 Jul 2015 15:43:16 +0100	[thread overview]
Message-ID: <55994284.6080209@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1507051542470.72900@nic-i.leissner.se>

Peter Fassberg wrote:
>
>> Peter Fassberg wrote:
>>>
>>>>> I'm trying to get PCTV TripleStick 292e working in a
>>>>> Raspberry Pi B+ environment.
>>>>>
>>>>> I have no problem getting DVB-T to work, but I can't tune to
>>>>> any DVB-T2 channels. I have tried with three different
>>>>> kernels: 3.18.11, 3.18.16 and 4.0.6.  Same problem.  I also
>>>>> cloned the media_build under 4.0.6 to no avail.
>>>>>
>>>>> The same physical stick works perfectly with DVB-T2 in an
>>>>> Intel platform using kernel 3.16.0.
>>>>>
>>>>> Do you have any suggestions what I can do to get this running
>>>>> or is there a known problem with Raspberry/ARM?
>>>>
>>>> What are you trying to tune with?
>>>
>>> I'm using dvbv5-scan.
>>>
>>> I use the same program on the system that works.
>>>
>>> The output for a DVB-T mux: Lock   (0x1f) Signal= -42.00dBm C/N=
>>> 20.25dB
>>>
>>> And a DVB-T2: Carrier(0x03) Signal= -35.00dBm
>>>
>>> There is a difference between Raspberry/ARM and Intel that I
>>> don't understand.
>>
>> Hmm, not sure then - maybe try md5sum on the firmware that dmesg
>> shows loading on each then if different backup/copy over etc.
>>
>> I am just a user so don't know what's different between 3.16 and
>> later.
>>
>> One thing I noticed at one point when setting mine up was (after
>> unknowingly breaking a splitter) that with the degraded splitter I
>> could get working/not on some T2 muxed by flipping the lna on off
>> with the option available with dvbv5-*.
>
> Yes, I also tested that.  The firmware is identical and the LNA as
> well.
>
> It do work 100% of the times I scan on the Intel platform.

OK - strange, is the issue reproducable with the current version of w_scan?



  reply	other threads:[~2015-07-05 14:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04 11:07 PCTV Triplestick and Raspberry Pi B+ Peter Fassberg
2015-07-05  9:50 ` Andy Furniss
2015-07-05 11:27   ` Peter Fassberg
2015-07-05 11:59     ` Andy Furniss
2015-07-05 13:44       ` Peter Fassberg
2015-07-05 14:43         ` Andy Furniss [this message]
2015-07-05 15:45           ` Peter Fassberg
2015-07-06  8:52             ` Andy Furniss
2015-07-05 16:44 ` Patrick Boettcher
2015-07-07 15:33   ` Peter Fassberg
2015-07-07 15:35     ` Patrick Boettcher
2015-07-07 15:38       ` Peter Fassberg
2015-07-07 16:25         ` Patrick Boettcher
2015-07-07 16:31           ` Patrick Boettcher
2015-07-07 16:44             ` Peter Fassberg
2015-07-07 16:51           ` Peter Fassberg
2015-07-08  7:33             ` Patrick Boettcher
2015-07-08  7:52               ` Olli Salonen

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=55994284.6080209@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=pf@leissner.se \
    /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.