linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtmkramer@xs4all.nl>
To: Torbjorn Jansson <torbjorn.jansson@mbox200.swipnet.se>
Cc: linux-media@vger.kernel.org
Subject: Re: DVBSky T980C CI issues (kernel 4.0.x)
Date: Sat, 12 Sep 2015 09:02:06 +0200	[thread overview]
Message-ID: <1442041326.2442.2.camel@xs4all.nl> (raw)
In-Reply-To: <55F332FE.7040201@mbox200.swipnet.se>

On Fri, 2015-09-11 at 22:01 +0200, Torbjorn Jansson wrote:
> On 2015-08-23 19:50, Jurgen Kramer wrote:
> >
> > On Sun, 2015-07-12 at 12:38 +0200, Jurgen Kramer wrote:
> >> I have been running a couple of DVBSky T980C's with CIs with success
> >> using an older kernel (3.17.8) with media-build and some added patches
> >> from the mailing list.
> >>
> >> I thought lets try a current 4.0 kernel to see if I no longer need to be
> >> running a custom kernel. Everything works just fine except the CAM
> >> module. I am seeing these:
> >>
> >> [  456.574969] dvb_ca adapter 0: Invalid PC card inserted :(
> >> [  456.626943] dvb_ca adapter 1: Invalid PC card inserted :(
> >> [  456.666932] dvb_ca adapter 2: Invalid PC card inserted :(
> >>
> >> The normal 'CAM detected and initialised' messages to do show up with
> >> 4.0.8
> >>
> >> I am not sure what changed in the recent kernels, what is needed to
> >> debug this?
> >>
> >> Jurgen
> > Retest. I've isolated one T980C on another PC with kernel 4.1.5, still the same 'Invalid PC card inserted :(' message.
> > Even after installed today's media_build from git no improvement.
> >
> > Any hints where to start looking would be appreciated!
> >
> > cimax2.c|h do not seem to have changed. There are changes to
> > dvb_ca_en50221.c
> >
> > Jurgen
> >
> 
> did you get it to work?

No, it needs a thorough debug session. So far no one seems able to
help...

> i got a dvbsky T980C too for dvb-t2 reception and so far the only 
> drivers that have worked at all is the ones from dvbsky directly.
> 
> i was very happy when i noticed that recent kernels have support for it 
> built in but unfortunately only the modules and firmware loads but then 
> nothing actually works.
> i use mythtv and it complains a lot about the signal, running femon also 
> produces lots of errors.
> 
> so i had to switch back to kernel 4.0.4 with mediabuild from dvbsky.
> 
> if there were any other dvb-t2 card with ci support that had better 
> drivers i would change right away.
> 
> one problem i have with the mediabuilt from dvbsky is that at boot the 
> cam never works and i have to first tune a channel, then remove and 
> reinstert the cam to get it to work.
> without that nothing works.
> 
> and finally a problem i ran into when i tried mediabuilt from linuxtv.org.
> fedora uses kernel modules with .ko.xz extension so when you install the 
> mediabuilt modulels you get one modulename.ko and one modulename.ko.xz
> 
> before a make install from mediabuild overwrote the needed modules.
> any advice on how to handle this now?
> 
> 



  parent reply	other threads:[~2015-09-12  7:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 10:38 DVBSky T980C CI issues (kernel 4.0.x) Jurgen Kramer
2015-08-23 17:50 ` Jurgen Kramer
2015-09-11 20:01   ` Torbjorn Jansson
2015-09-12  5:48     ` Tycho Lürsen
2015-09-12  7:02     ` Jurgen Kramer [this message]
2016-01-28 17:26       ` Olli Salonen
2016-01-28 18:57         ` Jurgen Kramer
2016-01-28 19:42           ` Olli Salonen
2016-01-31  8:55             ` Torbjorn Jansson
2016-02-16 20:20               ` Olli Salonen
2016-02-16 23:12                 ` Torbjorn Jansson
2016-02-17  6:24                   ` Olli Salonen
2016-02-17 13:42                     ` Olli Salonen
2016-02-17 21:54                       ` Torbjorn Jansson
2016-02-17 22:15                         ` Torbjorn Jansson
2016-02-18  5:56                           ` Olli Salonen
2016-02-18  7:56                             ` Torbjorn Jansson
2016-02-17 16:55                 ` Jurgen Kramer
2016-02-20 15:57                 ` Torbjorn Jansson
2016-02-20 17:20                   ` Jurgen Kramer
2016-02-20 17:40                     ` Torbjorn Jansson
2016-03-03 11:02                     ` Olli Salonen
2016-03-03 18:22                       ` Torbjorn Jansson
     [not found]                         ` <56D8B3A1.9030001@mbox200.swipnet.se>
     [not found]                           ` <56D8B4A2.2090402@mbox200.swipnet.se>
     [not found]                             ` <CAAZRmGxceZmWrvGbKgnPTUc0jyy0npC4cW1d225bo8oE3E7sgg@mail.gmail.com>
2016-03-04 23:07                               ` Torbjorn Jansson
     [not found]                                 ` <CAAZRmGyOxfANyZ884id5ZdTwyG2sfV1AE1KjSmaH1HHBrhmByg@mail.gmail.com>
2016-03-05  8:18                                   ` Torbjorn Jansson
2016-06-06 11:30                             ` Torbjorn Jansson
2017-07-17  8:38                               ` Torbjorn Jansson
2016-03-04  8:15                       ` Jurgen Kramer
2016-03-04  8:28                         ` Olli Salonen
2016-03-04 12:07                           ` Jurgen Kramer

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=1442041326.2442.2.camel@xs4all.nl \
    --to=gtmkramer@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=torbjorn.jansson@mbox200.swipnet.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 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).