DVBSky T980C CI issues (kernel 4.0.x)

DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

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

Relevant kernel messages:

[   14.899827] cx25840 9-0044: loaded v4l-cx23885-avcore-01.fw firmware
(16382 bytes)
[   14.915384] cx23885_dvb_register() allocating 1 frontend(s)
[   14.915386] cx23885[0]: cx23885 based dvb card
[   15.326745] i2c i2c-8: Added multiplexed i2c bus 10
[   15.326747] si2168 8-0064: Silicon Labs Si2168 successfully attached
[   15.390538] si2157 10-0060: Silicon Labs Si2147/2148/2157/2158
successfully attached
[   15.390542] DVB: registering new adapter (cx23885[0])
[   15.390544] cx23885 0000:02:00.0: DVB: registering adapter 0 frontend
0 (Silicon Labs Si2168)...
[   15.758330] sp2 8-0040: CIMaX SP2 successfully attached
[   15.785785] DVBSky T980C MAC address: 00:17:42:54:09:88
[   15.785789] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   15.785792] cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 16,
latency: 0, mmio: 0xf7c00000
[   15.785883] CORE cx23885[1]: subsystem: 4254:980c, board: DVBSky
T980C [card=46,autodetected]
[   15.996981] EXT4-fs (sda2): mounted filesystem with ordered data
mode. Opts: (null)
[   16.015395] cx25840 13-0044: cx23885 A/V decoder found @ 0x88
(cx23885[1])
[   16.642705] cx25840 13-0044: loaded v4l-cx23885-avcore-01.fw firmware
(16382 bytes)
[   16.658240] cx23885_dvb_register() allocating 1 frontend(s)
[   16.658242] cx23885[1]: cx23885 based dvb card
[   16.659004] i2c i2c-12: Added multiplexed i2c bus 14
[   16.659006] si2168 12-0064: Silicon Labs Si2168 successfully attached
[   16.660689] si2157 14-0060: Silicon Labs Si2147/2148/2157/2158
successfully attached
[   16.660692] DVB: registering new adapter (cx23885[1])
[   16.660693] cx23885 0000:03:00.0: DVB: registering adapter 1 frontend
0 (Silicon Labs Si2168)...
[   16.667337] sp2 12-0040: CIMaX SP2 successfully attached
[   16.694845] DVBSky T980C MAC address: 00:17:42:54:09:88
[   16.694848] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   16.694852] cx23885[1]/0: found at 0000:03:00.0, rev: 4, irq: 17,
latency: 0, mmio: 0xf7a00000
[   16.694986] CORE cx23885[2]: subsystem: 4254:980c, board: DVBSky
T980C [card=46,autodetected]
[   16.924320] cx25840 17-0044: cx23885 A/V decoder found @ 0x88
(cx23885[2])
[   17.551377] cx25840 17-0044: loaded v4l-cx23885-avcore-01.fw firmware
(16382 bytes)
[   17.566994] cx23885_dvb_register() allocating 1 frontend(s)
[   17.566996] cx23885[2]: cx23885 based dvb card
[   17.567898] i2c i2c-16: Added multiplexed i2c bus 18
[   17.567900] si2168 16-0064: Silicon Labs Si2168 successfully attached
[   17.569710] si2157 18-0060: Silicon Labs Si2147/2148/2157/2158
successfully attached
[   17.569714] DVB: registering new adapter (cx23885[2])
[   17.569715] cx23885 0000:05:00.0: DVB: registering adapter 2 frontend
0 (Silicon Labs Si2168)...
[   17.576684] sp2 16-0040: CIMaX SP2 successfully attached
[   17.604168] DVBSky T980C MAC address: 00:17:42:54:09:88
[   17.604171] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   17.604174] cx23885[2]/0: found at 0000:05:00.0, rev: 4, irq: 19,
latency: 0, mmio: 0xf7800000

[  220.616002] si2168 8-0064: found a 'Silicon Labs Si2168-A30'
[  220.635026] si2168 8-0064: downloading firmware from file
'dvb-demod-si2168-a30-01.fw'
[  223.744845] si2168 8-0064: firmware version: 3.0.16
[  223.753441] si2157 10-0060: found a 'Silicon Labs Si2158-A20'
[  223.777443] si2157 10-0060: downloading firmware from file
'dvb-tuner-si2158-a20-01.fw'
[  224.577779] si2157 10-0060: firmware version: 2.1.6
[  224.683600] si2168 12-0064: found a 'Silicon Labs Si2168-A30'
[  224.683633] si2168 12-0064: downloading firmware from file
'dvb-demod-si2168-a30-01.fw'
[  227.797635] si2168 12-0064: firmware version: 3.0.16
[  227.806235] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
[  227.806249] si2157 14-0060: downloading firmware from file
'dvb-tuner-si2158-a20-01.fw'
[  228.606280] si2157 14-0060: firmware version: 2.1.6
[  228.644496] si2168 16-0064: found a 'Silicon Labs Si2168-A30'
[  228.644521] si2168 16-0064: downloading firmware from file
'dvb-demod-si2168-a30-01.fw'
[  231.763081] si2168 16-0064: firmware version: 3.0.16
[  231.771685] si2157 18-0060: found a 'Silicon Labs Si2158-A20'
[  231.771711] si2157 18-0060: downloading firmware from file
'dvb-tuner-si2158-a20-01.fw'
[  232.571684] si2157 18-0060: firmware version: 2.1.6
[  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 :(
[  481.638979] dvb_ca adapter 0: Invalid PC card inserted :(

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

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


> Relevant kernel messages:
> 
> [   14.899827] cx25840 9-0044: loaded v4l-cx23885-avcore-01.fw firmware
> (16382 bytes)
> [   14.915384] cx23885_dvb_register() allocating 1 frontend(s)
> [   14.915386] cx23885[0]: cx23885 based dvb card
> [   15.326745] i2c i2c-8: Added multiplexed i2c bus 10
> [   15.326747] si2168 8-0064: Silicon Labs Si2168 successfully attached
> [   15.390538] si2157 10-0060: Silicon Labs Si2147/2148/2157/2158
> successfully attached
> [   15.390542] DVB: registering new adapter (cx23885[0])
> [   15.390544] cx23885 0000:02:00.0: DVB: registering adapter 0 frontend
> 0 (Silicon Labs Si2168)...
> [   15.758330] sp2 8-0040: CIMaX SP2 successfully attached
> [   15.785785] DVBSky T980C MAC address: 00:17:42:54:09:88
> [   15.785789] cx23885_dev_checkrevision() Hardware revision = 0xa5
> [   15.785792] cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 16,
> latency: 0, mmio: 0xf7c00000
> [   15.785883] CORE cx23885[1]: subsystem: 4254:980c, board: DVBSky
> T980C [card=46,autodetected]
> [   15.996981] EXT4-fs (sda2): mounted filesystem with ordered data
> mode. Opts: (null)
> [   16.015395] cx25840 13-0044: cx23885 A/V decoder found @ 0x88
> (cx23885[1])
> [   16.642705] cx25840 13-0044: loaded v4l-cx23885-avcore-01.fw firmware
> (16382 bytes)
> [   16.658240] cx23885_dvb_register() allocating 1 frontend(s)
> [   16.658242] cx23885[1]: cx23885 based dvb card
> [   16.659004] i2c i2c-12: Added multiplexed i2c bus 14
> [   16.659006] si2168 12-0064: Silicon Labs Si2168 successfully attached
> [   16.660689] si2157 14-0060: Silicon Labs Si2147/2148/2157/2158
> successfully attached
> [   16.660692] DVB: registering new adapter (cx23885[1])
> [   16.660693] cx23885 0000:03:00.0: DVB: registering adapter 1 frontend
> 0 (Silicon Labs Si2168)...
> [   16.667337] sp2 12-0040: CIMaX SP2 successfully attached
> [   16.694845] DVBSky T980C MAC address: 00:17:42:54:09:88
> [   16.694848] cx23885_dev_checkrevision() Hardware revision = 0xa5
> [   16.694852] cx23885[1]/0: found at 0000:03:00.0, rev: 4, irq: 17,
> latency: 0, mmio: 0xf7a00000
> [   16.694986] CORE cx23885[2]: subsystem: 4254:980c, board: DVBSky
> T980C [card=46,autodetected]
> [   16.924320] cx25840 17-0044: cx23885 A/V decoder found @ 0x88
> (cx23885[2])
> [   17.551377] cx25840 17-0044: loaded v4l-cx23885-avcore-01.fw firmware
> (16382 bytes)
> [   17.566994] cx23885_dvb_register() allocating 1 frontend(s)
> [   17.566996] cx23885[2]: cx23885 based dvb card
> [   17.567898] i2c i2c-16: Added multiplexed i2c bus 18
> [   17.567900] si2168 16-0064: Silicon Labs Si2168 successfully attached
> [   17.569710] si2157 18-0060: Silicon Labs Si2147/2148/2157/2158
> successfully attached
> [   17.569714] DVB: registering new adapter (cx23885[2])
> [   17.569715] cx23885 0000:05:00.0: DVB: registering adapter 2 frontend
> 0 (Silicon Labs Si2168)...
> [   17.576684] sp2 16-0040: CIMaX SP2 successfully attached
> [   17.604168] DVBSky T980C MAC address: 00:17:42:54:09:88
> [   17.604171] cx23885_dev_checkrevision() Hardware revision = 0xa5
> [   17.604174] cx23885[2]/0: found at 0000:05:00.0, rev: 4, irq: 19,
> latency: 0, mmio: 0xf7800000
> 
> [  220.616002] si2168 8-0064: found a 'Silicon Labs Si2168-A30'
> [  220.635026] si2168 8-0064: downloading firmware from file
> 'dvb-demod-si2168-a30-01.fw'
> [  223.744845] si2168 8-0064: firmware version: 3.0.16
> [  223.753441] si2157 10-0060: found a 'Silicon Labs Si2158-A20'
> [  223.777443] si2157 10-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [  224.577779] si2157 10-0060: firmware version: 2.1.6
> [  224.683600] si2168 12-0064: found a 'Silicon Labs Si2168-A30'
> [  224.683633] si2168 12-0064: downloading firmware from file
> 'dvb-demod-si2168-a30-01.fw'
> [  227.797635] si2168 12-0064: firmware version: 3.0.16
> [  227.806235] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
> [  227.806249] si2157 14-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [  228.606280] si2157 14-0060: firmware version: 2.1.6
> [  228.644496] si2168 16-0064: found a 'Silicon Labs Si2168-A30'
> [  228.644521] si2168 16-0064: downloading firmware from file
> 'dvb-demod-si2168-a30-01.fw'
> [  231.763081] si2168 16-0064: firmware version: 3.0.16
> [  231.771685] si2157 18-0060: found a 'Silicon Labs Si2158-A20'
> [  231.771711] si2157 18-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [  232.571684] si2157 18-0060: firmware version: 2.1.6
> [  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 :(
> [  481.638979] dvb_ca adapter 0: Invalid PC card inserted :(
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

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?

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?

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Tycho Lürsen]

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



Op 11-09-15 om 22:01 schreef Torbjorn Jansson:
>
> did you get it to work?
>
> 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?
You could patch the Makefile with a patch from Oliver Endriss (attached).
This way all modules get installed in /lib/modules/`uname -r`/updates/media
If your kernel needs it, you can compress them afterwards.
>
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: v4l-make-install.patch --]
[-- Type: text/x-patch, Size: 1060 bytes --]

--- v4l/Makefile	2013-11-27 16:15:21.528260850 +0100
+++ v4l/Makefile	2013-11-27 16:24:37.171815316 +0100
@@ -154,6 +154,7 @@
 PWD		:= $(shell pwd)
 DEST		:= /lib/modules/$(KERNELRELEASE)/v4l2
 KDIR26		:= /lib/modules/$(KERNELRELEASE)/kernel/drivers/media
+INSTDIR 	:= $(DESTDIR)/lib/modules/$(KERNELRELEASE)/updates/media
 
 #################################################
 # Compiler fixup rules
@@ -202,9 +203,18 @@
 #################################################
 # installation invocation rules
 
-modules_install install:: media-install firmware_install
-
-remove rminstall:: media-rminstall
+modules_install install:: rminstall firmware_install
+	install -d -v $(INSTDIR)
+	@for i in *.ko; do				\
+		echo "install $$i -> $(INSTDIR)/";	\
+		install -p -m 644 $$i $(INSTDIR);	\
+	done;
+	strip --strip-debug $(INSTDIR)/*.ko
+	/sbin/depmod -a $(KERNELRELEASE) $(if $(DESTDIR),-b $(DESTDIR))
+
+remove rminstall::
+	@rm -Rfv $(INSTDIR)
+	/sbin/depmod -a $(KERNELRELEASE) $(if $(DESTDIR),-b $(DESTDIR))
 
 firmware_install::
 	make -C firmware install

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

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?
> 
> 

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Jürgen,

Did you get anywhere with this?

I have a clone of your card and was just starting to look at this
issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
time to try to pinpoint this more?

Cheers,
-olli

On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
> 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?
>>
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

Hi Olli,

On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
> Hi Jürgen,
> 
> Did you get anywhere with this?
> 
> I have a clone of your card and was just starting to look at this
> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
> time to try to pinpoint this more?
No, unfortunately not. I have spend a few hours adding printk's but it
did not get me any closer what causes the issue. This really needs
investigation from someone who is more familiar with linux media.

Last thing I tried was the latest (semi open) drivers from dvbsky on a
4.3 kernel. Here the CI and CAM registered successfully.

Greetings,
Jurgen

> Cheers,
> -olli
> 
> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
> wrote:
> > 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?
> > > 
> > > 
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> > media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Jürgen & Mauro,

I did bisect this and it seems this rather big patch broke it:

2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
commit 2b0aac3011bc7a9db27791bed4978554263ef079
Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Date:   Tue Dec 23 13:48:07 2014 -0200

    [media] cx23885: move CI/MAC registration to a separate function

    As reported by smatch:
        drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
Function too hairy.  Giving up.

    This is indeed a too complex function, with lots of stuff inside.
    Breaking this into two functions makes it a little bit less hairy.

    Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>

It's getting a bit late, so I'll call it a day now and have a look at
the patch to see what goes wrong there.

Cheers,
-olli

On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
> Hi Olli,
>
> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>> Hi Jürgen,
>>
>> Did you get anywhere with this?
>>
>> I have a clone of your card and was just starting to look at this
>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>> time to try to pinpoint this more?
> No, unfortunately not. I have spend a few hours adding printk's but it
> did not get me any closer what causes the issue. This really needs
> investigation from someone who is more familiar with linux media.
>
> Last thing I tried was the latest (semi open) drivers from dvbsky on a
> 4.3 kernel. Here the CI and CAM registered successfully.
>
> Greetings,
> Jurgen
>
>> Cheers,
>> -olli
>>
>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>> wrote:
>> > 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?
>> > >
>> > >
>> >
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-
>> > media" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

this ci problem is the reason i decided to buy the CT2-4650 usb based 
device instead.
but the 4650 was a slightly newer revision needing a patch i submitted 
earlier.
and also this 4650 device does not have auto switching between dvb-t and 
t2 like the dvbsky card have, so i also need an updated version of mythtv.

my long term wish is to not have to patch things or build custom kernels 
or modules.
so anything done to improve the dvbsky card or the 4650 is much appreciated.


On 2016-01-28 20:42, Olli Salonen wrote:
> Hi Jürgen & Mauro,
>
> I did bisect this and it seems this rather big patch broke it:
>
> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
> commit 2b0aac3011bc7a9db27791bed4978554263ef079
> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> Date:   Tue Dec 23 13:48:07 2014 -0200
>
>      [media] cx23885: move CI/MAC registration to a separate function
>
>      As reported by smatch:
>          drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
> Function too hairy.  Giving up.
>
>      This is indeed a too complex function, with lots of stuff inside.
>      Breaking this into two functions makes it a little bit less hairy.
>
>      Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>
> It's getting a bit late, so I'll call it a day now and have a look at
> the patch to see what goes wrong there.
>
> Cheers,
> -olli
>
> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>> Hi Olli,
>>
>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>> Hi Jürgen,
>>>
>>> Did you get anywhere with this?
>>>
>>> I have a clone of your card and was just starting to look at this
>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>> time to try to pinpoint this more?
>> No, unfortunately not. I have spend a few hours adding printk's but it
>> did not get me any closer what causes the issue. This really needs
>> investigation from someone who is more familiar with linux media.
>>
>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>> 4.3 kernel. Here the CI and CAM registered successfully.
>>
>> Greetings,
>> Jurgen
>>
>>> Cheers,
>>> -olli
>>>
>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>> wrote:
>>>> 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?
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-
>>>> media" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi all,

Found the issue and submitted a patch.

The I2C buses for T980C/T2-4500CI were crossed when CI registration
was moved to its own function.

Cheers,
-olli

On 31 January 2016 at 10:55, Torbjorn Jansson
<torbjorn.jansson@mbox200.swipnet.se> wrote:
> this ci problem is the reason i decided to buy the CT2-4650 usb based device
> instead.
> but the 4650 was a slightly newer revision needing a patch i submitted
> earlier.
> and also this 4650 device does not have auto switching between dvb-t and t2
> like the dvbsky card have, so i also need an updated version of mythtv.
>
> my long term wish is to not have to patch things or build custom kernels or
> modules.
> so anything done to improve the dvbsky card or the 4650 is much appreciated.
>
>
> On 2016-01-28 20:42, Olli Salonen wrote:
>>
>> Hi Jürgen & Mauro,
>>
>> I did bisect this and it seems this rather big patch broke it:
>>
>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>
>>      [media] cx23885: move CI/MAC registration to a separate function
>>
>>      As reported by smatch:
>>          drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>> Function too hairy.  Giving up.
>>
>>      This is indeed a too complex function, with lots of stuff inside.
>>      Breaking this into two functions makes it a little bit less hairy.
>>
>>      Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>
>> It's getting a bit late, so I'll call it a day now and have a look at
>> the patch to see what goes wrong there.
>>
>> Cheers,
>> -olli
>>
>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>
>>> Hi Olli,
>>>
>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>
>>>> Hi Jürgen,
>>>>
>>>> Did you get anywhere with this?
>>>>
>>>> I have a clone of your card and was just starting to look at this
>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>> time to try to pinpoint this more?
>>>
>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>> did not get me any closer what causes the issue. This really needs
>>> investigation from someone who is more familiar with linux media.
>>>
>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>
>>> Greetings,
>>> Jurgen
>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>> wrote:
>>>>>
>>>>> 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?
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-
>>>>> media" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

Perfect.
Looks like i have some more testing to do in the next few days.

something else, when testing my 4650 card i cant get it to tune properly 
to dvb-t2 muxes.
but i'm not yet sure if this is a driver issue or if i made a mistake 
with the tuning parameters since the file i use that came with the dvbv5 
programs was missing the t2 mux so i had to put that one in manually.

so more testing is needed first and with your patch for the T980C card i 
can probably test both things at the same time.


On 2016-02-16 21:20, Olli Salonen wrote:
> Hi all,
>
> Found the issue and submitted a patch.
>
> The I2C buses for T980C/T2-4500CI were crossed when CI registration
> was moved to its own function.
>
> Cheers,
> -olli
>
> On 31 January 2016 at 10:55, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> this ci problem is the reason i decided to buy the CT2-4650 usb based device
>> instead.
>> but the 4650 was a slightly newer revision needing a patch i submitted
>> earlier.
>> and also this 4650 device does not have auto switching between dvb-t and t2
>> like the dvbsky card have, so i also need an updated version of mythtv.
>>
>> my long term wish is to not have to patch things or build custom kernels or
>> modules.
>> so anything done to improve the dvbsky card or the 4650 is much appreciated.
>>
>>
>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>
>>> Hi Jürgen & Mauro,
>>>
>>> I did bisect this and it seems this rather big patch broke it:
>>>
>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>
>>>       [media] cx23885: move CI/MAC registration to a separate function
>>>
>>>       As reported by smatch:
>>>           drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>>> Function too hairy.  Giving up.
>>>
>>>       This is indeed a too complex function, with lots of stuff inside.
>>>       Breaking this into two functions makes it a little bit less hairy.
>>>
>>>       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>
>>> It's getting a bit late, so I'll call it a day now and have a look at
>>> the patch to see what goes wrong there.
>>>
>>> Cheers,
>>> -olli
>>>
>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>
>>>> Hi Olli,
>>>>
>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>
>>>>> Hi Jürgen,
>>>>>
>>>>> Did you get anywhere with this?
>>>>>
>>>>> I have a clone of your card and was just starting to look at this
>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>> time to try to pinpoint this more?
>>>>
>>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>>> did not get me any closer what causes the issue. This really needs
>>>> investigation from someone who is more familiar with linux media.
>>>>
>>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>
>>>> Greetings,
>>>> Jurgen
>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>> wrote:
>>>>>>
>>>>>> 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?
>>>>>>>
>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Torbjörn,

I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
that there's something wrong with tuning to T2 channels.

Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
then with the CT2-4650CI.

olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
teema.ts -t 10
using demux '/dev/dvb/adapter1/demux0'
reading channels from file 'dvb_channel.conf'
service has pid type 06:  50
tuning to 184500000 Hz
video pid 316
  dvb_set_pesfilter 316
audio pid 880
  dvb_set_pesfilter 880
       (0x00)
Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
Record to file 'teema.ts' started
copied 6478856 bytes (632 Kbytes/sec)
Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB

olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o teema.ts -t 3
using demux '/dev/dvb/adapter0/demux0'
reading channels from file 'dvb_channel.conf'
service has pid type 06:  50
tuning to 184500000 Hz
video pid 316
  dvb_set_pesfilter 316
audio pid 880
  dvb_set_pesfilter 880
       (0x00)
       (0x00) Signal= -104.00dBm
       (0x00) Signal= -104.00dBm

frontend doesn't lock

I'll try to look into that...

Cheers,
-olli

On 17 February 2016 at 01:12, Torbjorn Jansson
<torbjorn.jansson@mbox200.swipnet.se> wrote:
> Perfect.
> Looks like i have some more testing to do in the next few days.
>
> something else, when testing my 4650 card i cant get it to tune properly to
> dvb-t2 muxes.
> but i'm not yet sure if this is a driver issue or if i made a mistake with
> the tuning parameters since the file i use that came with the dvbv5 programs
> was missing the t2 mux so i had to put that one in manually.
>
> so more testing is needed first and with your patch for the T980C card i can
> probably test both things at the same time.
>
>
> On 2016-02-16 21:20, Olli Salonen wrote:
>>
>> Hi all,
>>
>> Found the issue and submitted a patch.
>>
>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>> was moved to its own function.
>>
>> Cheers,
>> -olli
>>
>> On 31 January 2016 at 10:55, Torbjorn Jansson
>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>
>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>> device
>>> instead.
>>> but the 4650 was a slightly newer revision needing a patch i submitted
>>> earlier.
>>> and also this 4650 device does not have auto switching between dvb-t and
>>> t2
>>> like the dvbsky card have, so i also need an updated version of mythtv.
>>>
>>> my long term wish is to not have to patch things or build custom kernels
>>> or
>>> modules.
>>> so anything done to improve the dvbsky card or the 4650 is much
>>> appreciated.
>>>
>>>
>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>
>>>>
>>>> Hi Jürgen & Mauro,
>>>>
>>>> I did bisect this and it seems this rather big patch broke it:
>>>>
>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>
>>>>       [media] cx23885: move CI/MAC registration to a separate function
>>>>
>>>>       As reported by smatch:
>>>>           drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>>>> Function too hairy.  Giving up.
>>>>
>>>>       This is indeed a too complex function, with lots of stuff inside.
>>>>       Breaking this into two functions makes it a little bit less hairy.
>>>>
>>>>       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>
>>>> It's getting a bit late, so I'll call it a day now and have a look at
>>>> the patch to see what goes wrong there.
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>>
>>>>>
>>>>> Hi Olli,
>>>>>
>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>
>>>>>>
>>>>>> Hi Jürgen,
>>>>>>
>>>>>> Did you get anywhere with this?
>>>>>>
>>>>>> I have a clone of your card and was just starting to look at this
>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>> time to try to pinpoint this more?
>>>>>
>>>>>
>>>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>>>> did not get me any closer what causes the issue. This really needs
>>>>> investigation from someone who is more familiar with linux media.
>>>>>
>>>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>
>>>>> Greetings,
>>>>> Jurgen
>>>>>
>>>>>> Cheers,
>>>>>> -olli
>>>>>>
>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> 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?
>>>>>>>>
>>>>>>>>
>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Torbjörn,

Try commenting out this line in si2168.c and let me know if that changes things.

        if (c->delivery_system == SYS_DVBT2) {
                /* select PLP */
                cmd.args[0] = 0x52;
                cmd.args[1] = c->stream_id & 0xff;
//              cmd.args[2] = c->stream_id == NO_STREAM_ID_FILTER ? 0 : 1;
                cmd.wlen = 3;
                cmd.rlen = 1;
                ret = si2168_cmd_execute(s, &cmd);
                if (ret)
                        goto err;
        }


Cheers,
-olli

On 17 February 2016 at 08:24, Olli Salonen <olli.salonen@iki.fi> wrote:
> Hi Torbjörn,
>
> I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
> that there's something wrong with tuning to T2 channels.
>
> Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
> then with the CT2-4650CI.
>
> olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
> teema.ts -t 10
> using demux '/dev/dvb/adapter1/demux0'
> reading channels from file 'dvb_channel.conf'
> service has pid type 06:  50
> tuning to 184500000 Hz
> video pid 316
>   dvb_set_pesfilter 316
> audio pid 880
>   dvb_set_pesfilter 880
>        (0x00)
> Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
> Record to file 'teema.ts' started
> copied 6478856 bytes (632 Kbytes/sec)
> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>
> olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o teema.ts -t 3
> using demux '/dev/dvb/adapter0/demux0'
> reading channels from file 'dvb_channel.conf'
> service has pid type 06:  50
> tuning to 184500000 Hz
> video pid 316
>   dvb_set_pesfilter 316
> audio pid 880
>   dvb_set_pesfilter 880
>        (0x00)
>        (0x00) Signal= -104.00dBm
>        (0x00) Signal= -104.00dBm
>
> frontend doesn't lock
>
> I'll try to look into that...
>
> Cheers,
> -olli
>
> On 17 February 2016 at 01:12, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> Perfect.
>> Looks like i have some more testing to do in the next few days.
>>
>> something else, when testing my 4650 card i cant get it to tune properly to
>> dvb-t2 muxes.
>> but i'm not yet sure if this is a driver issue or if i made a mistake with
>> the tuning parameters since the file i use that came with the dvbv5 programs
>> was missing the t2 mux so i had to put that one in manually.
>>
>> so more testing is needed first and with your patch for the T980C card i can
>> probably test both things at the same time.
>>
>>
>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>
>>> Hi all,
>>>
>>> Found the issue and submitted a patch.
>>>
>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>> was moved to its own function.
>>>
>>> Cheers,
>>> -olli
>>>
>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>
>>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>>> device
>>>> instead.
>>>> but the 4650 was a slightly newer revision needing a patch i submitted
>>>> earlier.
>>>> and also this 4650 device does not have auto switching between dvb-t and
>>>> t2
>>>> like the dvbsky card have, so i also need an updated version of mythtv.
>>>>
>>>> my long term wish is to not have to patch things or build custom kernels
>>>> or
>>>> modules.
>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>> appreciated.
>>>>
>>>>
>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>
>>>>>
>>>>> Hi Jürgen & Mauro,
>>>>>
>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>
>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>
>>>>>       [media] cx23885: move CI/MAC registration to a separate function
>>>>>
>>>>>       As reported by smatch:
>>>>>           drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>>>>> Function too hairy.  Giving up.
>>>>>
>>>>>       This is indeed a too complex function, with lots of stuff inside.
>>>>>       Breaking this into two functions makes it a little bit less hairy.
>>>>>
>>>>>       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>
>>>>> It's getting a bit late, so I'll call it a day now and have a look at
>>>>> the patch to see what goes wrong there.
>>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Olli,
>>>>>>
>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi Jürgen,
>>>>>>>
>>>>>>> Did you get anywhere with this?
>>>>>>>
>>>>>>> I have a clone of your card and was just starting to look at this
>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>>> time to try to pinpoint this more?
>>>>>>
>>>>>>
>>>>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>>>>> did not get me any closer what causes the issue. This really needs
>>>>>> investigation from someone who is more familiar with linux media.
>>>>>>
>>>>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>
>>>>>> Greetings,
>>>>>> Jurgen
>>>>>>
>>>>>>> Cheers,
>>>>>>> -olli
>>>>>>>
>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> 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?
>>>>>>>>>
>>>>>>>>>
>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

testing is likely to be a bit problematic because using the most recent 
code from media_tree results in the following during module load and 
after this the modules are not loaded properly (/dev/dvb missing)

i will retry with older code.


[    5.558524] WARNING: You are using an experimental version of the 
media stack.
                 As the driver is backported to an older kernel, it 
doesn't offer
                 enough quality for its usage in production.
                 Use it with care.
                Latest git patches (needed if you report a bug to 
linux-media@vger.kernel.org):
                 3d0ccad0dbbd51b64d307c64cc163002334afbfa [media] siano: 
use generic function to create MC device
                 dd47fbd40e6ea6884e295e13a2e50b0894258fdf [media] 
smsusb: don't sleep while atomic
                 21cf734c79e6c741dcdf383dbaef3b551b931568 [media] siano: 
firmware buffer is too small
[    5.750834] usb 1-2: dvb_usb_v2: found a 'TechnoTrend TT-connect 
CT2-4650 CI v1.1' in warm state
[    5.751737] usb 1-2: dvb_usb_v2: will pass the complete MPEG2 
transport stream to the software demuxer
[    5.751754] DVB: registering new adapter (TechnoTrend TT-connect 
CT2-4650 CI v1.1)
[    5.751799] usb 1-2: media controller created
[    5.754172] usb 1-2: dvb_usb_v2: MAC address: bc:ea:2b:65:06:6f
[    5.754527] dvb_create_media_entity: media entity 'dvb-demux' registered.
[    5.761734] i2c i2c-1: Added multiplexed i2c bus 2
[    5.761738] si2168 1-0064: Silicon Labs Si2168 successfully attached
[    5.767308] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 
successfully attached
[    5.776422] dvb_create_media_entity: media entity 'dvb-ca-en50221' 
registered.
[    5.777199] sp2 1-0040: CIMaX SP2 successfully attached
[    5.777211] usb 1-2: DVB: registering adapter 0 frontend 0 (Silicon 
Labs Si2168)...
[    5.777214] dvb_create_media_entity: media entity 'Silicon Labs 
Si2168' registered.
[    5.780048] ------------[ cut here ]------------
[    5.780059] WARNING: CPU: 1 PID: 568 at lib/idr.c:1051 
ida_remove+0xef/0x120()
[    5.780060] ida_remove called for id=512 which is not allocated.
[    5.780061] Modules linked in: sp2(OE) si2157(OE) si2168(OE) 
dvb_usb_dvbsky(OE+) m88ds3103(OE) dvb_usb_v2(OE) i2c_mux dvb_core(OE) 
rc_core(OE) videodev(OE) media(OE) iosf_mbi ppdev crct10dif_pclmul 
crc32_pclmul crc32c_intel snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm 
parport_pc joydev snd_timer snd parport virtio_balloon soundcore pvpanic 
i2c_piix4 acpi_cpufreq tpm_tis tpm qxl 8021q drm_kms_helper garp stp llc 
mrp virtio_blk ttm virtio_net virtio_console drm serio_raw virtio_pci 
virtio_ring ata_generic virtio pata_acpi
[    5.780086] CPU: 1 PID: 568 Comm: systemd-udevd Tainted: G 
OE   4.3.4-200.fc22.x86_64 #1
[    5.780087] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[    5.780089]  0000000000000000 0000000069734069 ffff88007c23b6f8 
ffffffff813a625f
[    5.780090]  ffff88007c23b740 ffff88007c23b730 ffffffff810a07c2 
ffff88003680ac08
[    5.780092]  ffff88003680ac08 0000000000000206 ffff88007b7a4500 
ffff88007b43e158
[    5.780094] Call Trace:
[    5.780097]  [<ffffffff813a625f>] dump_stack+0x44/0x55
[    5.780100]  [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0
[    5.780102]  [<ffffffff810a085c>] warn_slowpath_fmt+0x5c/0x80
[    5.780107]  [<ffffffff813bab85>] ? find_next_bit+0x15/0x20
[    5.780109]  [<ffffffff813a73ff>] ida_remove+0xef/0x120
[    5.780110]  [<ffffffff813a7e7b>] ida_simple_remove+0x2b/0x50
[    5.780114]  [<ffffffffa022404d>] 
__media_device_unregister_entity+0x2d/0xd0 [media]
[    5.780116]  [<ffffffffa022411c>] 
media_device_unregister_entity+0x2c/0x40 [media]
[    5.780119]  [<ffffffffa02770ff>] dvb_media_device_free+0x1f/0x130 
[dvb_core]
[    5.780122]  [<ffffffffa0277252>] dvb_unregister_device+0x42/0x80 
[dvb_core]
[    5.780125]  [<ffffffffa027da05>] dvb_ca_en50221_release+0x75/0xb0 
[dvb_core]
[    5.780127]  [<ffffffffa02af289>] sp2_remove+0x49/0xa0 [sp2]
[    5.780134]  [<ffffffff815dc18b>] i2c_device_remove+0x4b/0xa0
[    5.780137]  [<ffffffff814d9501>] __device_release_driver+0xa1/0x150
[    5.780141]  [<ffffffff814d95d3>] device_release_driver+0x23/0x30
[    5.780143]  [<ffffffff814d8c21>] bus_remove_device+0x101/0x170
[    5.780145]  [<ffffffff814d4ec9>] device_del+0x139/0x260
[    5.780147]  [<ffffffff813a8647>] ? kobject_put+0x27/0x50
[    5.780149]  [<ffffffff815dc680>] ? __unregister_dummy+0x30/0x30
[    5.780151]  [<ffffffff814d500e>] device_unregister+0x1e/0x60
[    5.780153]  [<ffffffff815dc6be>] __unregister_client+0x3e/0x50
[    5.780154]  [<ffffffff814d4970>] device_for_each_child+0x50/0x90
[    5.780156]  [<ffffffff815de99e>] i2c_del_adapter+0x20e/0x300
[    5.780166]  [<ffffffff81203ed8>] ? kfree+0x128/0x130
[    5.780169]  [<ffffffffa025c974>] dvb_usbv2_exit+0x1c4/0x3c0 [dvb_usb_v2]
[    5.780171]  [<ffffffffa025d44f>] dvb_usbv2_probe+0xff/0x1200 
[dvb_usb_v2]
[    5.780174]  [<ffffffff814e4619>] ? __pm_runtime_set_status+0x189/0x230
[    5.780182]  [<ffffffff81570282>] usb_probe_interface+0x1b2/0x2d0
[    5.780184]  [<ffffffff814d9b82>] driver_probe_device+0x222/0x480
[    5.780185]  [<ffffffff814d9e64>] __driver_attach+0x84/0x90
[    5.780187]  [<ffffffff814d9de0>] ? driver_probe_device+0x480/0x480
[    5.780188]  [<ffffffff814d765c>] bus_for_each_dev+0x6c/0xc0
[    5.780190]  [<ffffffff814d933e>] driver_attach+0x1e/0x20
[    5.780191]  [<ffffffff814d8e7b>] bus_add_driver+0x1eb/0x280
[    5.780193]  [<ffffffff814da6b0>] driver_register+0x60/0xe0
[    5.780195]  [<ffffffff8156eb24>] usb_register_driver+0x84/0x140
[    5.780196]  [<ffffffffa00bb000>] ? 0xffffffffa00bb000
[    5.780199]  [<ffffffffa00bb01e>] dvbsky_usb_driver_init+0x1e/0x1000 
[dvb_usb_dvbsky]
[    5.780202]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
[    5.780206]  [<ffffffff8177d99e>] ? preempt_schedule_common+0x1e/0x40
[    5.780208]  [<ffffffff8177d9dc>] ? _cond_resched+0x1c/0x30
[    5.780210]  [<ffffffff8120427e>] ? kmem_cache_alloc_trace+0x19e/0x220
[    5.780214]  [<ffffffff811a4947>] ? do_init_module+0x27/0x1e5
[    5.780215]  [<ffffffff811a497f>] do_init_module+0x5f/0x1e5
[    5.780221]  [<ffffffff811254fe>] load_module+0x201e/0x2630
[    5.780223]  [<ffffffff811219c0>] ? __symbol_put+0x60/0x60
[    5.780229]  [<ffffffff81229830>] ? kernel_read+0x50/0x80
[    5.780231]  [<ffffffff81125d59>] SyS_finit_module+0xb9/0xf0
[    5.780237]  [<ffffffff8178182e>] entry_SYSCALL_64_fastpath+0x12/0x71
[    5.780239] ---[ end trace 944e313bd83469d2 ]---
[    5.783508] dvb_usb_dvbsky: probe of 1-2:1.0 failed with error -12
[    5.783524] usbcore: registered new interface driver dvb_usb_dvbsky




On 2016-02-17 14:42, Olli Salonen wrote:
> Hi Torbjörn,
>
> Try commenting out this line in si2168.c and let me know if that changes things.
>
>          if (c->delivery_system == SYS_DVBT2) {
>                  /* select PLP */
>                  cmd.args[0] = 0x52;
>                  cmd.args[1] = c->stream_id & 0xff;
> //              cmd.args[2] = c->stream_id == NO_STREAM_ID_FILTER ? 0 : 1;
>                  cmd.wlen = 3;
>                  cmd.rlen = 1;
>                  ret = si2168_cmd_execute(s, &cmd);
>                  if (ret)
>                          goto err;
>          }
>
>
> Cheers,
> -olli
>
> On 17 February 2016 at 08:24, Olli Salonen <olli.salonen@iki.fi> wrote:
>> Hi Torbjörn,
>>
>> I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
>> that there's something wrong with tuning to T2 channels.
>>
>> Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
>> then with the CT2-4650CI.
>>
>> olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
>> teema.ts -t 10
>> using demux '/dev/dvb/adapter1/demux0'
>> reading channels from file 'dvb_channel.conf'
>> service has pid type 06:  50
>> tuning to 184500000 Hz
>> video pid 316
>>    dvb_set_pesfilter 316
>> audio pid 880
>>    dvb_set_pesfilter 880
>>         (0x00)
>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>> Record to file 'teema.ts' started
>> copied 6478856 bytes (632 Kbytes/sec)
>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>
>> olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o teema.ts -t 3
>> using demux '/dev/dvb/adapter0/demux0'
>> reading channels from file 'dvb_channel.conf'
>> service has pid type 06:  50
>> tuning to 184500000 Hz
>> video pid 316
>>    dvb_set_pesfilter 316
>> audio pid 880
>>    dvb_set_pesfilter 880
>>         (0x00)
>>         (0x00) Signal= -104.00dBm
>>         (0x00) Signal= -104.00dBm
>>
>> frontend doesn't lock
>>
>> I'll try to look into that...
>>
>> Cheers,
>> -olli
>>
>> On 17 February 2016 at 01:12, Torbjorn Jansson
>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>> Perfect.
>>> Looks like i have some more testing to do in the next few days.
>>>
>>> something else, when testing my 4650 card i cant get it to tune properly to
>>> dvb-t2 muxes.
>>> but i'm not yet sure if this is a driver issue or if i made a mistake with
>>> the tuning parameters since the file i use that came with the dvbv5 programs
>>> was missing the t2 mux so i had to put that one in manually.
>>>
>>> so more testing is needed first and with your patch for the T980C card i can
>>> probably test both things at the same time.
>>>
>>>
>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Found the issue and submitted a patch.
>>>>
>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>> was moved to its own function.
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>
>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>>>> device
>>>>> instead.
>>>>> but the 4650 was a slightly newer revision needing a patch i submitted
>>>>> earlier.
>>>>> and also this 4650 device does not have auto switching between dvb-t and
>>>>> t2
>>>>> like the dvbsky card have, so i also need an updated version of mythtv.
>>>>>
>>>>> my long term wish is to not have to patch things or build custom kernels
>>>>> or
>>>>> modules.
>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>> appreciated.
>>>>>
>>>>>
>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>
>>>>>>
>>>>>> Hi Jürgen & Mauro,
>>>>>>
>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>
>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>
>>>>>>        [media] cx23885: move CI/MAC registration to a separate function
>>>>>>
>>>>>>        As reported by smatch:
>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>>>>>> Function too hairy.  Giving up.
>>>>>>
>>>>>>        This is indeed a too complex function, with lots of stuff inside.
>>>>>>        Breaking this into two functions makes it a little bit less hairy.
>>>>>>
>>>>>>        Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>
>>>>>> It's getting a bit late, so I'll call it a day now and have a look at
>>>>>> the patch to see what goes wrong there.
>>>>>>
>>>>>> Cheers,
>>>>>> -olli
>>>>>>
>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi Olli,
>>>>>>>
>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Jürgen,
>>>>>>>>
>>>>>>>> Did you get anywhere with this?
>>>>>>>>
>>>>>>>> I have a clone of your card and was just starting to look at this
>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>>>> time to try to pinpoint this more?
>>>>>>>
>>>>>>>
>>>>>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>>>>>> did not get me any closer what causes the issue. This really needs
>>>>>>> investigation from someone who is more familiar with linux media.
>>>>>>>
>>>>>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Jurgen
>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -olli
>>>>>>>>
>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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?
>>>>>>>>>>
>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

retested with media_tree at commit: 13f6e8887a1f61764a05a3348476d38071201f08
this is the most recent one that i bisected before that doesn't result 
in module load problems.

with my patch to add the new revision of the 4650 usb device and above 
commit plus your proposed change to si2168.c did not produce any 
different result.
still problems tuning dvbt2 channels.

i also tested my updated tuning file for dvbv5-scan with my other usb stick:
Bus 001 Device 004: ID 2013:024f PCTV Systems nanoStick T2 290e
to confirm the scanning input file was good and it was.
the pctv stick can properly tune the t2 muxes.



On 2016-02-17 22:54, Torbjorn Jansson wrote:
> testing is likely to be a bit problematic because using the most recent
> code from media_tree results in the following during module load and
> after this the modules are not loaded properly (/dev/dvb missing)
>
> i will retry with older code.
>
>
> [    5.558524] WARNING: You are using an experimental version of the
> media stack.
>                  As the driver is backported to an older kernel, it
> doesn't offer
>                  enough quality for its usage in production.
>                  Use it with care.
>                 Latest git patches (needed if you report a bug to
> linux-media@vger.kernel.org):
>                  3d0ccad0dbbd51b64d307c64cc163002334afbfa [media] siano:
> use generic function to create MC device
>                  dd47fbd40e6ea6884e295e13a2e50b0894258fdf [media]
> smsusb: don't sleep while atomic
>                  21cf734c79e6c741dcdf383dbaef3b551b931568 [media] siano:
> firmware buffer is too small
> [    5.750834] usb 1-2: dvb_usb_v2: found a 'TechnoTrend TT-connect
> CT2-4650 CI v1.1' in warm state
> [    5.751737] usb 1-2: dvb_usb_v2: will pass the complete MPEG2
> transport stream to the software demuxer
> [    5.751754] DVB: registering new adapter (TechnoTrend TT-connect
> CT2-4650 CI v1.1)
> [    5.751799] usb 1-2: media controller created
> [    5.754172] usb 1-2: dvb_usb_v2: MAC address: bc:ea:2b:65:06:6f
> [    5.754527] dvb_create_media_entity: media entity 'dvb-demux'
> registered.
> [    5.761734] i2c i2c-1: Added multiplexed i2c bus 2
> [    5.761738] si2168 1-0064: Silicon Labs Si2168 successfully attached
> [    5.767308] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158
> successfully attached
> [    5.776422] dvb_create_media_entity: media entity 'dvb-ca-en50221'
> registered.
> [    5.777199] sp2 1-0040: CIMaX SP2 successfully attached
> [    5.777211] usb 1-2: DVB: registering adapter 0 frontend 0 (Silicon
> Labs Si2168)...
> [    5.777214] dvb_create_media_entity: media entity 'Silicon Labs
> Si2168' registered.
> [    5.780048] ------------[ cut here ]------------
> [    5.780059] WARNING: CPU: 1 PID: 568 at lib/idr.c:1051
> ida_remove+0xef/0x120()
> [    5.780060] ida_remove called for id=512 which is not allocated.
> [    5.780061] Modules linked in: sp2(OE) si2157(OE) si2168(OE)
> dvb_usb_dvbsky(OE+) m88ds3103(OE) dvb_usb_v2(OE) i2c_mux dvb_core(OE)
> rc_core(OE) videodev(OE) media(OE) iosf_mbi ppdev crct10dif_pclmul
> crc32_pclmul crc32c_intel snd_hda_codec_generic snd_hda_intel
> snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm
> parport_pc joydev snd_timer snd parport virtio_balloon soundcore pvpanic
> i2c_piix4 acpi_cpufreq tpm_tis tpm qxl 8021q drm_kms_helper garp stp llc
> mrp virtio_blk ttm virtio_net virtio_console drm serio_raw virtio_pci
> virtio_ring ata_generic virtio pata_acpi
> [    5.780086] CPU: 1 PID: 568 Comm: systemd-udevd Tainted: G OE
> 4.3.4-200.fc22.x86_64 #1
> [    5.780087] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
> [    5.780089]  0000000000000000 0000000069734069 ffff88007c23b6f8
> ffffffff813a625f
> [    5.780090]  ffff88007c23b740 ffff88007c23b730 ffffffff810a07c2
> ffff88003680ac08
> [    5.780092]  ffff88003680ac08 0000000000000206 ffff88007b7a4500
> ffff88007b43e158
> [    5.780094] Call Trace:
> [    5.780097]  [<ffffffff813a625f>] dump_stack+0x44/0x55
> [    5.780100]  [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0
> [    5.780102]  [<ffffffff810a085c>] warn_slowpath_fmt+0x5c/0x80
> [    5.780107]  [<ffffffff813bab85>] ? find_next_bit+0x15/0x20
> [    5.780109]  [<ffffffff813a73ff>] ida_remove+0xef/0x120
> [    5.780110]  [<ffffffff813a7e7b>] ida_simple_remove+0x2b/0x50
> [    5.780114]  [<ffffffffa022404d>]
> __media_device_unregister_entity+0x2d/0xd0 [media]
> [    5.780116]  [<ffffffffa022411c>]
> media_device_unregister_entity+0x2c/0x40 [media]
> [    5.780119]  [<ffffffffa02770ff>] dvb_media_device_free+0x1f/0x130
> [dvb_core]
> [    5.780122]  [<ffffffffa0277252>] dvb_unregister_device+0x42/0x80
> [dvb_core]
> [    5.780125]  [<ffffffffa027da05>] dvb_ca_en50221_release+0x75/0xb0
> [dvb_core]
> [    5.780127]  [<ffffffffa02af289>] sp2_remove+0x49/0xa0 [sp2]
> [    5.780134]  [<ffffffff815dc18b>] i2c_device_remove+0x4b/0xa0
> [    5.780137]  [<ffffffff814d9501>] __device_release_driver+0xa1/0x150
> [    5.780141]  [<ffffffff814d95d3>] device_release_driver+0x23/0x30
> [    5.780143]  [<ffffffff814d8c21>] bus_remove_device+0x101/0x170
> [    5.780145]  [<ffffffff814d4ec9>] device_del+0x139/0x260
> [    5.780147]  [<ffffffff813a8647>] ? kobject_put+0x27/0x50
> [    5.780149]  [<ffffffff815dc680>] ? __unregister_dummy+0x30/0x30
> [    5.780151]  [<ffffffff814d500e>] device_unregister+0x1e/0x60
> [    5.780153]  [<ffffffff815dc6be>] __unregister_client+0x3e/0x50
> [    5.780154]  [<ffffffff814d4970>] device_for_each_child+0x50/0x90
> [    5.780156]  [<ffffffff815de99e>] i2c_del_adapter+0x20e/0x300
> [    5.780166]  [<ffffffff81203ed8>] ? kfree+0x128/0x130
> [    5.780169]  [<ffffffffa025c974>] dvb_usbv2_exit+0x1c4/0x3c0
> [dvb_usb_v2]
> [    5.780171]  [<ffffffffa025d44f>] dvb_usbv2_probe+0xff/0x1200
> [dvb_usb_v2]
> [    5.780174]  [<ffffffff814e4619>] ? __pm_runtime_set_status+0x189/0x230
> [    5.780182]  [<ffffffff81570282>] usb_probe_interface+0x1b2/0x2d0
> [    5.780184]  [<ffffffff814d9b82>] driver_probe_device+0x222/0x480
> [    5.780185]  [<ffffffff814d9e64>] __driver_attach+0x84/0x90
> [    5.780187]  [<ffffffff814d9de0>] ? driver_probe_device+0x480/0x480
> [    5.780188]  [<ffffffff814d765c>] bus_for_each_dev+0x6c/0xc0
> [    5.780190]  [<ffffffff814d933e>] driver_attach+0x1e/0x20
> [    5.780191]  [<ffffffff814d8e7b>] bus_add_driver+0x1eb/0x280
> [    5.780193]  [<ffffffff814da6b0>] driver_register+0x60/0xe0
> [    5.780195]  [<ffffffff8156eb24>] usb_register_driver+0x84/0x140
> [    5.780196]  [<ffffffffa00bb000>] ? 0xffffffffa00bb000
> [    5.780199]  [<ffffffffa00bb01e>] dvbsky_usb_driver_init+0x1e/0x1000
> [dvb_usb_dvbsky]
> [    5.780202]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
> [    5.780206]  [<ffffffff8177d99e>] ? preempt_schedule_common+0x1e/0x40
> [    5.780208]  [<ffffffff8177d9dc>] ? _cond_resched+0x1c/0x30
> [    5.780210]  [<ffffffff8120427e>] ? kmem_cache_alloc_trace+0x19e/0x220
> [    5.780214]  [<ffffffff811a4947>] ? do_init_module+0x27/0x1e5
> [    5.780215]  [<ffffffff811a497f>] do_init_module+0x5f/0x1e5
> [    5.780221]  [<ffffffff811254fe>] load_module+0x201e/0x2630
> [    5.780223]  [<ffffffff811219c0>] ? __symbol_put+0x60/0x60
> [    5.780229]  [<ffffffff81229830>] ? kernel_read+0x50/0x80
> [    5.780231]  [<ffffffff81125d59>] SyS_finit_module+0xb9/0xf0
> [    5.780237]  [<ffffffff8178182e>] entry_SYSCALL_64_fastpath+0x12/0x71
> [    5.780239] ---[ end trace 944e313bd83469d2 ]---
> [    5.783508] dvb_usb_dvbsky: probe of 1-2:1.0 failed with error -12
> [    5.783524] usbcore: registered new interface driver dvb_usb_dvbsky
>
>
>
>
> On 2016-02-17 14:42, Olli Salonen wrote:
>> Hi Torbjörn,
>>
>> Try commenting out this line in si2168.c and let me know if that
>> changes things.
>>
>>          if (c->delivery_system == SYS_DVBT2) {
>>                  /* select PLP */
>>                  cmd.args[0] = 0x52;
>>                  cmd.args[1] = c->stream_id & 0xff;
>> //              cmd.args[2] = c->stream_id == NO_STREAM_ID_FILTER ? 0
>> : 1;
>>                  cmd.wlen = 3;
>>                  cmd.rlen = 1;
>>                  ret = si2168_cmd_execute(s, &cmd);
>>                  if (ret)
>>                          goto err;
>>          }
>>
>>
>> Cheers,
>> -olli
>>
>> On 17 February 2016 at 08:24, Olli Salonen <olli.salonen@iki.fi> wrote:
>>> Hi Torbjörn,
>>>
>>> I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
>>> that there's something wrong with tuning to T2 channels.
>>>
>>> Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
>>> then with the CT2-4650CI.
>>>
>>> olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
>>> teema.ts -t 10
>>> using demux '/dev/dvb/adapter1/demux0'
>>> reading channels from file 'dvb_channel.conf'
>>> service has pid type 06:  50
>>> tuning to 184500000 Hz
>>> video pid 316
>>>    dvb_set_pesfilter 316
>>> audio pid 880
>>>    dvb_set_pesfilter 880
>>>         (0x00)
>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>> Record to file 'teema.ts' started
>>> copied 6478856 bytes (632 Kbytes/sec)
>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>>
>>> olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o
>>> teema.ts -t 3
>>> using demux '/dev/dvb/adapter0/demux0'
>>> reading channels from file 'dvb_channel.conf'
>>> service has pid type 06:  50
>>> tuning to 184500000 Hz
>>> video pid 316
>>>    dvb_set_pesfilter 316
>>> audio pid 880
>>>    dvb_set_pesfilter 880
>>>         (0x00)
>>>         (0x00) Signal= -104.00dBm
>>>         (0x00) Signal= -104.00dBm
>>>
>>> frontend doesn't lock
>>>
>>> I'll try to look into that...
>>>
>>> Cheers,
>>> -olli
>>>
>>> On 17 February 2016 at 01:12, Torbjorn Jansson
>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>> Perfect.
>>>> Looks like i have some more testing to do in the next few days.
>>>>
>>>> something else, when testing my 4650 card i cant get it to tune
>>>> properly to
>>>> dvb-t2 muxes.
>>>> but i'm not yet sure if this is a driver issue or if i made a
>>>> mistake with
>>>> the tuning parameters since the file i use that came with the dvbv5
>>>> programs
>>>> was missing the t2 mux so i had to put that one in manually.
>>>>
>>>> so more testing is needed first and with your patch for the T980C
>>>> card i can
>>>> probably test both things at the same time.
>>>>
>>>>
>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Found the issue and submitted a patch.
>>>>>
>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>> was moved to its own function.
>>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>
>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>>>>> device
>>>>>> instead.
>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>> submitted
>>>>>> earlier.
>>>>>> and also this 4650 device does not have auto switching between
>>>>>> dvb-t and
>>>>>> t2
>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>> mythtv.
>>>>>>
>>>>>> my long term wish is to not have to patch things or build custom
>>>>>> kernels
>>>>>> or
>>>>>> modules.
>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>> appreciated.
>>>>>>
>>>>>>
>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi Jürgen & Mauro,
>>>>>>>
>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>
>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>
>>>>>>>        [media] cx23885: move CI/MAC registration to a separate
>>>>>>> function
>>>>>>>
>>>>>>>        As reported by smatch:
>>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>> dvb_register()
>>>>>>> Function too hairy.  Giving up.
>>>>>>>
>>>>>>>        This is indeed a too complex function, with lots of stuff
>>>>>>> inside.
>>>>>>>        Breaking this into two functions makes it a little bit
>>>>>>> less hairy.
>>>>>>>
>>>>>>>        Signed-off-by: Mauro Carvalho Chehab
>>>>>>> <mchehab@osg.samsung.com>
>>>>>>>
>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>> look at
>>>>>>> the patch to see what goes wrong there.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> -olli
>>>>>>>
>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Olli,
>>>>>>>>
>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Jürgen,
>>>>>>>>>
>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>
>>>>>>>>> I have a clone of your card and was just starting to look at this
>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>
>>>>>>>>
>>>>>>>> No, unfortunately not. I have spend a few hours adding printk's
>>>>>>>> but it
>>>>>>>> did not get me any closer what causes the issue. This really needs
>>>>>>>> investigation from someone who is more familiar with linux media.
>>>>>>>>
>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>> dvbsky on a
>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>
>>>>>>>> Greetings,
>>>>>>>> Jurgen
>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> -olli
>>>>>>>>>
>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 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?
>>>>>>>>>>>
>>>>>>>>>>>
>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Torbjörn,

If you did bisect this, can you please send the bisect result and a
description of the issue to the linux-media mailing list and to the
author of the commit that caused the problem?

Thanks!

Cheers,
-olli

On 18 February 2016 at 00:15, Torbjorn Jansson
<torbjorn.jansson@mbox200.swipnet.se> wrote:
> retested with media_tree at commit: 13f6e8887a1f61764a05a3348476d38071201f08
> this is the most recent one that i bisected before that doesn't result in
> module load problems.
>
> with my patch to add the new revision of the 4650 usb device and above
> commit plus your proposed change to si2168.c did not produce any different
> result.
> still problems tuning dvbt2 channels.
>
> i also tested my updated tuning file for dvbv5-scan with my other usb stick:
> Bus 001 Device 004: ID 2013:024f PCTV Systems nanoStick T2 290e
> to confirm the scanning input file was good and it was.
> the pctv stick can properly tune the t2 muxes.
>
>
>
> On 2016-02-17 22:54, Torbjorn Jansson wrote:
>>
>> testing is likely to be a bit problematic because using the most recent
>> code from media_tree results in the following during module load and
>> after this the modules are not loaded properly (/dev/dvb missing)
>>
>> i will retry with older code.
>>
>>
>> [    5.558524] WARNING: You are using an experimental version of the
>> media stack.
>>                  As the driver is backported to an older kernel, it
>> doesn't offer
>>                  enough quality for its usage in production.
>>                  Use it with care.
>>                 Latest git patches (needed if you report a bug to
>> linux-media@vger.kernel.org):
>>                  3d0ccad0dbbd51b64d307c64cc163002334afbfa [media] siano:
>> use generic function to create MC device
>>                  dd47fbd40e6ea6884e295e13a2e50b0894258fdf [media]
>> smsusb: don't sleep while atomic
>>                  21cf734c79e6c741dcdf383dbaef3b551b931568 [media] siano:
>> firmware buffer is too small
>> [    5.750834] usb 1-2: dvb_usb_v2: found a 'TechnoTrend TT-connect
>> CT2-4650 CI v1.1' in warm state
>> [    5.751737] usb 1-2: dvb_usb_v2: will pass the complete MPEG2
>> transport stream to the software demuxer
>> [    5.751754] DVB: registering new adapter (TechnoTrend TT-connect
>> CT2-4650 CI v1.1)
>> [    5.751799] usb 1-2: media controller created
>> [    5.754172] usb 1-2: dvb_usb_v2: MAC address: bc:ea:2b:65:06:6f
>> [    5.754527] dvb_create_media_entity: media entity 'dvb-demux'
>> registered.
>> [    5.761734] i2c i2c-1: Added multiplexed i2c bus 2
>> [    5.761738] si2168 1-0064: Silicon Labs Si2168 successfully attached
>> [    5.767308] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158
>> successfully attached
>> [    5.776422] dvb_create_media_entity: media entity 'dvb-ca-en50221'
>> registered.
>> [    5.777199] sp2 1-0040: CIMaX SP2 successfully attached
>> [    5.777211] usb 1-2: DVB: registering adapter 0 frontend 0 (Silicon
>> Labs Si2168)...
>> [    5.777214] dvb_create_media_entity: media entity 'Silicon Labs
>> Si2168' registered.
>> [    5.780048] ------------[ cut here ]------------
>> [    5.780059] WARNING: CPU: 1 PID: 568 at lib/idr.c:1051
>> ida_remove+0xef/0x120()
>> [    5.780060] ida_remove called for id=512 which is not allocated.
>> [    5.780061] Modules linked in: sp2(OE) si2157(OE) si2168(OE)
>> dvb_usb_dvbsky(OE+) m88ds3103(OE) dvb_usb_v2(OE) i2c_mux dvb_core(OE)
>> rc_core(OE) videodev(OE) media(OE) iosf_mbi ppdev crct10dif_pclmul
>> crc32_pclmul crc32c_intel snd_hda_codec_generic snd_hda_intel
>> snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm
>> parport_pc joydev snd_timer snd parport virtio_balloon soundcore pvpanic
>> i2c_piix4 acpi_cpufreq tpm_tis tpm qxl 8021q drm_kms_helper garp stp llc
>> mrp virtio_blk ttm virtio_net virtio_console drm serio_raw virtio_pci
>> virtio_ring ata_generic virtio pata_acpi
>> [    5.780086] CPU: 1 PID: 568 Comm: systemd-udevd Tainted: G OE
>> 4.3.4-200.fc22.x86_64 #1
>> [    5.780087] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
>> [    5.780089]  0000000000000000 0000000069734069 ffff88007c23b6f8
>> ffffffff813a625f
>> [    5.780090]  ffff88007c23b740 ffff88007c23b730 ffffffff810a07c2
>> ffff88003680ac08
>> [    5.780092]  ffff88003680ac08 0000000000000206 ffff88007b7a4500
>> ffff88007b43e158
>> [    5.780094] Call Trace:
>> [    5.780097]  [<ffffffff813a625f>] dump_stack+0x44/0x55
>> [    5.780100]  [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0
>> [    5.780102]  [<ffffffff810a085c>] warn_slowpath_fmt+0x5c/0x80
>> [    5.780107]  [<ffffffff813bab85>] ? find_next_bit+0x15/0x20
>> [    5.780109]  [<ffffffff813a73ff>] ida_remove+0xef/0x120
>> [    5.780110]  [<ffffffff813a7e7b>] ida_simple_remove+0x2b/0x50
>> [    5.780114]  [<ffffffffa022404d>]
>> __media_device_unregister_entity+0x2d/0xd0 [media]
>> [    5.780116]  [<ffffffffa022411c>]
>> media_device_unregister_entity+0x2c/0x40 [media]
>> [    5.780119]  [<ffffffffa02770ff>] dvb_media_device_free+0x1f/0x130
>> [dvb_core]
>> [    5.780122]  [<ffffffffa0277252>] dvb_unregister_device+0x42/0x80
>> [dvb_core]
>> [    5.780125]  [<ffffffffa027da05>] dvb_ca_en50221_release+0x75/0xb0
>> [dvb_core]
>> [    5.780127]  [<ffffffffa02af289>] sp2_remove+0x49/0xa0 [sp2]
>> [    5.780134]  [<ffffffff815dc18b>] i2c_device_remove+0x4b/0xa0
>> [    5.780137]  [<ffffffff814d9501>] __device_release_driver+0xa1/0x150
>> [    5.780141]  [<ffffffff814d95d3>] device_release_driver+0x23/0x30
>> [    5.780143]  [<ffffffff814d8c21>] bus_remove_device+0x101/0x170
>> [    5.780145]  [<ffffffff814d4ec9>] device_del+0x139/0x260
>> [    5.780147]  [<ffffffff813a8647>] ? kobject_put+0x27/0x50
>> [    5.780149]  [<ffffffff815dc680>] ? __unregister_dummy+0x30/0x30
>> [    5.780151]  [<ffffffff814d500e>] device_unregister+0x1e/0x60
>> [    5.780153]  [<ffffffff815dc6be>] __unregister_client+0x3e/0x50
>> [    5.780154]  [<ffffffff814d4970>] device_for_each_child+0x50/0x90
>> [    5.780156]  [<ffffffff815de99e>] i2c_del_adapter+0x20e/0x300
>> [    5.780166]  [<ffffffff81203ed8>] ? kfree+0x128/0x130
>> [    5.780169]  [<ffffffffa025c974>] dvb_usbv2_exit+0x1c4/0x3c0
>> [dvb_usb_v2]
>> [    5.780171]  [<ffffffffa025d44f>] dvb_usbv2_probe+0xff/0x1200
>> [dvb_usb_v2]
>> [    5.780174]  [<ffffffff814e4619>] ? __pm_runtime_set_status+0x189/0x230
>> [    5.780182]  [<ffffffff81570282>] usb_probe_interface+0x1b2/0x2d0
>> [    5.780184]  [<ffffffff814d9b82>] driver_probe_device+0x222/0x480
>> [    5.780185]  [<ffffffff814d9e64>] __driver_attach+0x84/0x90
>> [    5.780187]  [<ffffffff814d9de0>] ? driver_probe_device+0x480/0x480
>> [    5.780188]  [<ffffffff814d765c>] bus_for_each_dev+0x6c/0xc0
>> [    5.780190]  [<ffffffff814d933e>] driver_attach+0x1e/0x20
>> [    5.780191]  [<ffffffff814d8e7b>] bus_add_driver+0x1eb/0x280
>> [    5.780193]  [<ffffffff814da6b0>] driver_register+0x60/0xe0
>> [    5.780195]  [<ffffffff8156eb24>] usb_register_driver+0x84/0x140
>> [    5.780196]  [<ffffffffa00bb000>] ? 0xffffffffa00bb000
>> [    5.780199]  [<ffffffffa00bb01e>] dvbsky_usb_driver_init+0x1e/0x1000
>> [dvb_usb_dvbsky]
>> [    5.780202]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
>> [    5.780206]  [<ffffffff8177d99e>] ? preempt_schedule_common+0x1e/0x40
>> [    5.780208]  [<ffffffff8177d9dc>] ? _cond_resched+0x1c/0x30
>> [    5.780210]  [<ffffffff8120427e>] ? kmem_cache_alloc_trace+0x19e/0x220
>> [    5.780214]  [<ffffffff811a4947>] ? do_init_module+0x27/0x1e5
>> [    5.780215]  [<ffffffff811a497f>] do_init_module+0x5f/0x1e5
>> [    5.780221]  [<ffffffff811254fe>] load_module+0x201e/0x2630
>> [    5.780223]  [<ffffffff811219c0>] ? __symbol_put+0x60/0x60
>> [    5.780229]  [<ffffffff81229830>] ? kernel_read+0x50/0x80
>> [    5.780231]  [<ffffffff81125d59>] SyS_finit_module+0xb9/0xf0
>> [    5.780237]  [<ffffffff8178182e>] entry_SYSCALL_64_fastpath+0x12/0x71
>> [    5.780239] ---[ end trace 944e313bd83469d2 ]---
>> [    5.783508] dvb_usb_dvbsky: probe of 1-2:1.0 failed with error -12
>> [    5.783524] usbcore: registered new interface driver dvb_usb_dvbsky
>>
>>
>>
>>
>> On 2016-02-17 14:42, Olli Salonen wrote:
>>>
>>> Hi Torbjörn,
>>>
>>> Try commenting out this line in si2168.c and let me know if that
>>> changes things.
>>>
>>>          if (c->delivery_system == SYS_DVBT2) {
>>>                  /* select PLP */
>>>                  cmd.args[0] = 0x52;
>>>                  cmd.args[1] = c->stream_id & 0xff;
>>> //              cmd.args[2] = c->stream_id == NO_STREAM_ID_FILTER ? 0
>>> : 1;
>>>                  cmd.wlen = 3;
>>>                  cmd.rlen = 1;
>>>                  ret = si2168_cmd_execute(s, &cmd);
>>>                  if (ret)
>>>                          goto err;
>>>          }
>>>
>>>
>>> Cheers,
>>> -olli
>>>
>>> On 17 February 2016 at 08:24, Olli Salonen <olli.salonen@iki.fi> wrote:
>>>>
>>>> Hi Torbjörn,
>>>>
>>>> I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
>>>> that there's something wrong with tuning to T2 channels.
>>>>
>>>> Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
>>>> then with the CT2-4650CI.
>>>>
>>>> olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
>>>> teema.ts -t 10
>>>> using demux '/dev/dvb/adapter1/demux0'
>>>> reading channels from file 'dvb_channel.conf'
>>>> service has pid type 06:  50
>>>> tuning to 184500000 Hz
>>>> video pid 316
>>>>    dvb_set_pesfilter 316
>>>> audio pid 880
>>>>    dvb_set_pesfilter 880
>>>>         (0x00)
>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>>> Record to file 'teema.ts' started
>>>> copied 6478856 bytes (632 Kbytes/sec)
>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>>>
>>>> olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o
>>>> teema.ts -t 3
>>>> using demux '/dev/dvb/adapter0/demux0'
>>>> reading channels from file 'dvb_channel.conf'
>>>> service has pid type 06:  50
>>>> tuning to 184500000 Hz
>>>> video pid 316
>>>>    dvb_set_pesfilter 316
>>>> audio pid 880
>>>>    dvb_set_pesfilter 880
>>>>         (0x00)
>>>>         (0x00) Signal= -104.00dBm
>>>>         (0x00) Signal= -104.00dBm
>>>>
>>>> frontend doesn't lock
>>>>
>>>> I'll try to look into that...
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 17 February 2016 at 01:12, Torbjorn Jansson
>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>
>>>>> Perfect.
>>>>> Looks like i have some more testing to do in the next few days.
>>>>>
>>>>> something else, when testing my 4650 card i cant get it to tune
>>>>> properly to
>>>>> dvb-t2 muxes.
>>>>> but i'm not yet sure if this is a driver issue or if i made a
>>>>> mistake with
>>>>> the tuning parameters since the file i use that came with the dvbv5
>>>>> programs
>>>>> was missing the t2 mux so i had to put that one in manually.
>>>>>
>>>>> so more testing is needed first and with your patch for the T980C
>>>>> card i can
>>>>> probably test both things at the same time.
>>>>>
>>>>>
>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Found the issue and submitted a patch.
>>>>>>
>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>> was moved to its own function.
>>>>>>
>>>>>> Cheers,
>>>>>> -olli
>>>>>>
>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>
>>>>>>>
>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>>>>>> device
>>>>>>> instead.
>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>> submitted
>>>>>>> earlier.
>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>> dvb-t and
>>>>>>> t2
>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>> mythtv.
>>>>>>>
>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>> kernels
>>>>>>> or
>>>>>>> modules.
>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>> appreciated.
>>>>>>>
>>>>>>>
>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>
>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>
>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>
>>>>>>>>        [media] cx23885: move CI/MAC registration to a separate
>>>>>>>> function
>>>>>>>>
>>>>>>>>        As reported by smatch:
>>>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>> dvb_register()
>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>
>>>>>>>>        This is indeed a too complex function, with lots of stuff
>>>>>>>> inside.
>>>>>>>>        Breaking this into two functions makes it a little bit
>>>>>>>> less hairy.
>>>>>>>>
>>>>>>>>        Signed-off-by: Mauro Carvalho Chehab
>>>>>>>> <mchehab@osg.samsung.com>
>>>>>>>>
>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>> look at
>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -olli
>>>>>>>>
>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Olli,
>>>>>>>>>
>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>
>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>
>>>>>>>>>> I have a clone of your card and was just starting to look at this
>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> No, unfortunately not. I have spend a few hours adding printk's
>>>>>>>>> but it
>>>>>>>>> did not get me any closer what causes the issue. This really needs
>>>>>>>>> investigation from someone who is more familiar with linux media.
>>>>>>>>>
>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>> dvbsky on a
>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>
>>>>>>>>> Greetings,
>>>>>>>>> Jurgen
>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> -olli
>>>>>>>>>>
>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 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?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

already done, see mail i sent to the list 2016-02-06 with subject 
"dvb_usb_dvbsky module not loading (ida_remove something)"
i dont know if more info is needed or not.


On 2016-02-18 06:56, Olli Salonen wrote:
> Hi Torbjörn,
>
> If you did bisect this, can you please send the bisect result and a
> description of the issue to the linux-media mailing list and to the
> author of the commit that caused the problem?
>
> Thanks!
>
> Cheers,
> -olli
>
> On 18 February 2016 at 00:15, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> retested with media_tree at commit: 13f6e8887a1f61764a05a3348476d38071201f08
>> this is the most recent one that i bisected before that doesn't result in
>> module load problems.
>>
>> with my patch to add the new revision of the 4650 usb device and above
>> commit plus your proposed change to si2168.c did not produce any different
>> result.
>> still problems tuning dvbt2 channels.
>>
>> i also tested my updated tuning file for dvbv5-scan with my other usb stick:
>> Bus 001 Device 004: ID 2013:024f PCTV Systems nanoStick T2 290e
>> to confirm the scanning input file was good and it was.
>> the pctv stick can properly tune the t2 muxes.
>>
>>
>>
>> On 2016-02-17 22:54, Torbjorn Jansson wrote:
>>>
>>> testing is likely to be a bit problematic because using the most recent
>>> code from media_tree results in the following during module load and
>>> after this the modules are not loaded properly (/dev/dvb missing)
>>>
>>> i will retry with older code.
>>>
>>>
>>> [    5.558524] WARNING: You are using an experimental version of the
>>> media stack.
>>>                   As the driver is backported to an older kernel, it
>>> doesn't offer
>>>                   enough quality for its usage in production.
>>>                   Use it with care.
>>>                  Latest git patches (needed if you report a bug to
>>> linux-media@vger.kernel.org):
>>>                   3d0ccad0dbbd51b64d307c64cc163002334afbfa [media] siano:
>>> use generic function to create MC device
>>>                   dd47fbd40e6ea6884e295e13a2e50b0894258fdf [media]
>>> smsusb: don't sleep while atomic
>>>                   21cf734c79e6c741dcdf383dbaef3b551b931568 [media] siano:
>>> firmware buffer is too small
>>> [    5.750834] usb 1-2: dvb_usb_v2: found a 'TechnoTrend TT-connect
>>> CT2-4650 CI v1.1' in warm state
>>> [    5.751737] usb 1-2: dvb_usb_v2: will pass the complete MPEG2
>>> transport stream to the software demuxer
>>> [    5.751754] DVB: registering new adapter (TechnoTrend TT-connect
>>> CT2-4650 CI v1.1)
>>> [    5.751799] usb 1-2: media controller created
>>> [    5.754172] usb 1-2: dvb_usb_v2: MAC address: bc:ea:2b:65:06:6f
>>> [    5.754527] dvb_create_media_entity: media entity 'dvb-demux'
>>> registered.
>>> [    5.761734] i2c i2c-1: Added multiplexed i2c bus 2
>>> [    5.761738] si2168 1-0064: Silicon Labs Si2168 successfully attached
>>> [    5.767308] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158
>>> successfully attached
>>> [    5.776422] dvb_create_media_entity: media entity 'dvb-ca-en50221'
>>> registered.
>>> [    5.777199] sp2 1-0040: CIMaX SP2 successfully attached
>>> [    5.777211] usb 1-2: DVB: registering adapter 0 frontend 0 (Silicon
>>> Labs Si2168)...
>>> [    5.777214] dvb_create_media_entity: media entity 'Silicon Labs
>>> Si2168' registered.
>>> [    5.780048] ------------[ cut here ]------------
>>> [    5.780059] WARNING: CPU: 1 PID: 568 at lib/idr.c:1051
>>> ida_remove+0xef/0x120()
>>> [    5.780060] ida_remove called for id=512 which is not allocated.
>>> [    5.780061] Modules linked in: sp2(OE) si2157(OE) si2168(OE)
>>> dvb_usb_dvbsky(OE+) m88ds3103(OE) dvb_usb_v2(OE) i2c_mux dvb_core(OE)
>>> rc_core(OE) videodev(OE) media(OE) iosf_mbi ppdev crct10dif_pclmul
>>> crc32_pclmul crc32c_intel snd_hda_codec_generic snd_hda_intel
>>> snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm
>>> parport_pc joydev snd_timer snd parport virtio_balloon soundcore pvpanic
>>> i2c_piix4 acpi_cpufreq tpm_tis tpm qxl 8021q drm_kms_helper garp stp llc
>>> mrp virtio_blk ttm virtio_net virtio_console drm serio_raw virtio_pci
>>> virtio_ring ata_generic virtio pata_acpi
>>> [    5.780086] CPU: 1 PID: 568 Comm: systemd-udevd Tainted: G OE
>>> 4.3.4-200.fc22.x86_64 #1
>>> [    5.780087] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
>>> [    5.780089]  0000000000000000 0000000069734069 ffff88007c23b6f8
>>> ffffffff813a625f
>>> [    5.780090]  ffff88007c23b740 ffff88007c23b730 ffffffff810a07c2
>>> ffff88003680ac08
>>> [    5.780092]  ffff88003680ac08 0000000000000206 ffff88007b7a4500
>>> ffff88007b43e158
>>> [    5.780094] Call Trace:
>>> [    5.780097]  [<ffffffff813a625f>] dump_stack+0x44/0x55
>>> [    5.780100]  [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0
>>> [    5.780102]  [<ffffffff810a085c>] warn_slowpath_fmt+0x5c/0x80
>>> [    5.780107]  [<ffffffff813bab85>] ? find_next_bit+0x15/0x20
>>> [    5.780109]  [<ffffffff813a73ff>] ida_remove+0xef/0x120
>>> [    5.780110]  [<ffffffff813a7e7b>] ida_simple_remove+0x2b/0x50
>>> [    5.780114]  [<ffffffffa022404d>]
>>> __media_device_unregister_entity+0x2d/0xd0 [media]
>>> [    5.780116]  [<ffffffffa022411c>]
>>> media_device_unregister_entity+0x2c/0x40 [media]
>>> [    5.780119]  [<ffffffffa02770ff>] dvb_media_device_free+0x1f/0x130
>>> [dvb_core]
>>> [    5.780122]  [<ffffffffa0277252>] dvb_unregister_device+0x42/0x80
>>> [dvb_core]
>>> [    5.780125]  [<ffffffffa027da05>] dvb_ca_en50221_release+0x75/0xb0
>>> [dvb_core]
>>> [    5.780127]  [<ffffffffa02af289>] sp2_remove+0x49/0xa0 [sp2]
>>> [    5.780134]  [<ffffffff815dc18b>] i2c_device_remove+0x4b/0xa0
>>> [    5.780137]  [<ffffffff814d9501>] __device_release_driver+0xa1/0x150
>>> [    5.780141]  [<ffffffff814d95d3>] device_release_driver+0x23/0x30
>>> [    5.780143]  [<ffffffff814d8c21>] bus_remove_device+0x101/0x170
>>> [    5.780145]  [<ffffffff814d4ec9>] device_del+0x139/0x260
>>> [    5.780147]  [<ffffffff813a8647>] ? kobject_put+0x27/0x50
>>> [    5.780149]  [<ffffffff815dc680>] ? __unregister_dummy+0x30/0x30
>>> [    5.780151]  [<ffffffff814d500e>] device_unregister+0x1e/0x60
>>> [    5.780153]  [<ffffffff815dc6be>] __unregister_client+0x3e/0x50
>>> [    5.780154]  [<ffffffff814d4970>] device_for_each_child+0x50/0x90
>>> [    5.780156]  [<ffffffff815de99e>] i2c_del_adapter+0x20e/0x300
>>> [    5.780166]  [<ffffffff81203ed8>] ? kfree+0x128/0x130
>>> [    5.780169]  [<ffffffffa025c974>] dvb_usbv2_exit+0x1c4/0x3c0
>>> [dvb_usb_v2]
>>> [    5.780171]  [<ffffffffa025d44f>] dvb_usbv2_probe+0xff/0x1200
>>> [dvb_usb_v2]
>>> [    5.780174]  [<ffffffff814e4619>] ? __pm_runtime_set_status+0x189/0x230
>>> [    5.780182]  [<ffffffff81570282>] usb_probe_interface+0x1b2/0x2d0
>>> [    5.780184]  [<ffffffff814d9b82>] driver_probe_device+0x222/0x480
>>> [    5.780185]  [<ffffffff814d9e64>] __driver_attach+0x84/0x90
>>> [    5.780187]  [<ffffffff814d9de0>] ? driver_probe_device+0x480/0x480
>>> [    5.780188]  [<ffffffff814d765c>] bus_for_each_dev+0x6c/0xc0
>>> [    5.780190]  [<ffffffff814d933e>] driver_attach+0x1e/0x20
>>> [    5.780191]  [<ffffffff814d8e7b>] bus_add_driver+0x1eb/0x280
>>> [    5.780193]  [<ffffffff814da6b0>] driver_register+0x60/0xe0
>>> [    5.780195]  [<ffffffff8156eb24>] usb_register_driver+0x84/0x140
>>> [    5.780196]  [<ffffffffa00bb000>] ? 0xffffffffa00bb000
>>> [    5.780199]  [<ffffffffa00bb01e>] dvbsky_usb_driver_init+0x1e/0x1000
>>> [dvb_usb_dvbsky]
>>> [    5.780202]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
>>> [    5.780206]  [<ffffffff8177d99e>] ? preempt_schedule_common+0x1e/0x40
>>> [    5.780208]  [<ffffffff8177d9dc>] ? _cond_resched+0x1c/0x30
>>> [    5.780210]  [<ffffffff8120427e>] ? kmem_cache_alloc_trace+0x19e/0x220
>>> [    5.780214]  [<ffffffff811a4947>] ? do_init_module+0x27/0x1e5
>>> [    5.780215]  [<ffffffff811a497f>] do_init_module+0x5f/0x1e5
>>> [    5.780221]  [<ffffffff811254fe>] load_module+0x201e/0x2630
>>> [    5.780223]  [<ffffffff811219c0>] ? __symbol_put+0x60/0x60
>>> [    5.780229]  [<ffffffff81229830>] ? kernel_read+0x50/0x80
>>> [    5.780231]  [<ffffffff81125d59>] SyS_finit_module+0xb9/0xf0
>>> [    5.780237]  [<ffffffff8178182e>] entry_SYSCALL_64_fastpath+0x12/0x71
>>> [    5.780239] ---[ end trace 944e313bd83469d2 ]---
>>> [    5.783508] dvb_usb_dvbsky: probe of 1-2:1.0 failed with error -12
>>> [    5.783524] usbcore: registered new interface driver dvb_usb_dvbsky
>>>
>>>
>>>
>>>
>>> On 2016-02-17 14:42, Olli Salonen wrote:
>>>>
>>>> Hi Torbjörn,
>>>>
>>>> Try commenting out this line in si2168.c and let me know if that
>>>> changes things.
>>>>
>>>>           if (c->delivery_system == SYS_DVBT2) {
>>>>                   /* select PLP */
>>>>                   cmd.args[0] = 0x52;
>>>>                   cmd.args[1] = c->stream_id & 0xff;
>>>> //              cmd.args[2] = c->stream_id == NO_STREAM_ID_FILTER ? 0
>>>> : 1;
>>>>                   cmd.wlen = 3;
>>>>                   cmd.rlen = 1;
>>>>                   ret = si2168_cmd_execute(s, &cmd);
>>>>                   if (ret)
>>>>                           goto err;
>>>>           }
>>>>
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 17 February 2016 at 08:24, Olli Salonen <olli.salonen@iki.fi> wrote:
>>>>>
>>>>> Hi Torbjörn,
>>>>>
>>>>> I connected my old v1 CT2-4650CI to my test PC and indeed, it seems
>>>>> that there's something wrong with tuning to T2 channels.
>>>>>
>>>>> Here's first a tune with the CT2-4500CI (same as DVBSky T980C) and
>>>>> then with the CT2-4650CI.
>>>>>
>>>>> olli@dl160:~$ dvbv5-zap -a 1 "Yle Teema HD" -c dvb_channel.conf -o
>>>>> teema.ts -t 10
>>>>> using demux '/dev/dvb/adapter1/demux0'
>>>>> reading channels from file 'dvb_channel.conf'
>>>>> service has pid type 06:  50
>>>>> tuning to 184500000 Hz
>>>>> video pid 316
>>>>>     dvb_set_pesfilter 316
>>>>> audio pid 880
>>>>>     dvb_set_pesfilter 880
>>>>>          (0x00)
>>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.75dB
>>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>>>> Record to file 'teema.ts' started
>>>>> copied 6478856 bytes (632 Kbytes/sec)
>>>>> Lock   (0x1f) Signal= -72.00dBm C/N= 26.50dB
>>>>>
>>>>> olli@dl160:~$ dvbv5-zap -a 0 "Yle Teema HD" -c dvb_channel.conf -o
>>>>> teema.ts -t 3
>>>>> using demux '/dev/dvb/adapter0/demux0'
>>>>> reading channels from file 'dvb_channel.conf'
>>>>> service has pid type 06:  50
>>>>> tuning to 184500000 Hz
>>>>> video pid 316
>>>>>     dvb_set_pesfilter 316
>>>>> audio pid 880
>>>>>     dvb_set_pesfilter 880
>>>>>          (0x00)
>>>>>          (0x00) Signal= -104.00dBm
>>>>>          (0x00) Signal= -104.00dBm
>>>>>
>>>>> frontend doesn't lock
>>>>>
>>>>> I'll try to look into that...
>>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 17 February 2016 at 01:12, Torbjorn Jansson
>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>
>>>>>> Perfect.
>>>>>> Looks like i have some more testing to do in the next few days.
>>>>>>
>>>>>> something else, when testing my 4650 card i cant get it to tune
>>>>>> properly to
>>>>>> dvb-t2 muxes.
>>>>>> but i'm not yet sure if this is a driver issue or if i made a
>>>>>> mistake with
>>>>>> the tuning parameters since the file i use that came with the dvbv5
>>>>>> programs
>>>>>> was missing the t2 mux so i had to put that one in manually.
>>>>>>
>>>>>> so more testing is needed first and with your patch for the T980C
>>>>>> card i can
>>>>>> probably test both things at the same time.
>>>>>>
>>>>>>
>>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Found the issue and submitted a patch.
>>>>>>>
>>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>>> was moved to its own function.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> -olli
>>>>>>>
>>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb based
>>>>>>>> device
>>>>>>>> instead.
>>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>>> submitted
>>>>>>>> earlier.
>>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>>> dvb-t and
>>>>>>>> t2
>>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>>> mythtv.
>>>>>>>>
>>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>>> kernels
>>>>>>>> or
>>>>>>>> modules.
>>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>>> appreciated.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>>
>>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>>
>>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>>
>>>>>>>>>         [media] cx23885: move CI/MAC registration to a separate
>>>>>>>>> function
>>>>>>>>>
>>>>>>>>>         As reported by smatch:
>>>>>>>>>             drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>>> dvb_register()
>>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>>
>>>>>>>>>         This is indeed a too complex function, with lots of stuff
>>>>>>>>> inside.
>>>>>>>>>         Breaking this into two functions makes it a little bit
>>>>>>>>> less hairy.
>>>>>>>>>
>>>>>>>>>         Signed-off-by: Mauro Carvalho Chehab
>>>>>>>>> <mchehab@osg.samsung.com>
>>>>>>>>>
>>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>>> look at
>>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> -olli
>>>>>>>>>
>>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Olli,
>>>>>>>>>>
>>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>>
>>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>>
>>>>>>>>>>> I have a clone of your card and was just starting to look at this
>>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> No, unfortunately not. I have spend a few hours adding printk's
>>>>>>>>>> but it
>>>>>>>>>> did not get me any closer what causes the issue. This really needs
>>>>>>>>>> investigation from someone who is more familiar with linux media.
>>>>>>>>>>
>>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>>> dvbsky on a
>>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>>
>>>>>>>>>> Greetings,
>>>>>>>>>> Jurgen
>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> -olli
>>>>>>>>>>>
>>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 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?
>>>>>>>>>>>>>
>>>>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

On Tue, 2016-02-16 at 22:20 +0200, Olli Salonen wrote:
> Hi all,
> 
> Found the issue and submitted a patch.
> 
> The I2C buses for T980C/T2-4500CI were crossed when CI registration
> was moved to its own function.
Great! Thanks for looking into this.

Jurgen

> Cheers,
> -olli
> 
> On 31 January 2016 at 10:55, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
> > this ci problem is the reason i decided to buy the CT2-4650 usb
> > based device
> > instead.
> > but the 4650 was a slightly newer revision needing a patch i
> > submitted
> > earlier.
> > and also this 4650 device does not have auto switching between dvb-
> > t and t2
> > like the dvbsky card have, so i also need an updated version of
> > mythtv.
> > 
> > my long term wish is to not have to patch things or build custom
> > kernels or
> > modules.
> > so anything done to improve the dvbsky card or the 4650 is much
> > appreciated.
> > 
> > 
> > On 2016-01-28 20:42, Olli Salonen wrote:
> > > 
> > > Hi Jürgen & Mauro,
> > > 
> > > I did bisect this and it seems this rather big patch broke it:
> > > 
> > > 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
> > > commit 2b0aac3011bc7a9db27791bed4978554263ef079
> > > Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > > Date:   Tue Dec 23 13:48:07 2014 -0200
> > > 
> > >      [media] cx23885: move CI/MAC registration to a separate
> > > function
> > > 
> > >      As reported by smatch:
> > >          drivers/media/pci/cx23885/cx23885-dvb.c:2080
> > > dvb_register()
> > > Function too hairy.  Giving up.
> > > 
> > >      This is indeed a too complex function, with lots of stuff
> > > inside.
> > >      Breaking this into two functions makes it a little bit less
> > > hairy.
> > > 
> > >      Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.co
> > > m>
> > > 
> > > It's getting a bit late, so I'll call it a day now and have a
> > > look at
> > > the patch to see what goes wrong there.
> > > 
> > > Cheers,
> > > -olli
> > > 
> > > On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl>
> > > wrote:
> > > > 
> > > > Hi Olli,
> > > > 
> > > > On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
> > > > > 
> > > > > Hi Jürgen,
> > > > > 
> > > > > Did you get anywhere with this?
> > > > > 
> > > > > I have a clone of your card and was just starting to look at
> > > > > this
> > > > > issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
> > > > > have any
> > > > > time to try to pinpoint this more?
> > > > 
> > > > No, unfortunately not. I have spend a few hours adding printk's
> > > > but it
> > > > did not get me any closer what causes the issue. This really
> > > > needs
> > > > investigation from someone who is more familiar with linux
> > > > media.
> > > > 
> > > > Last thing I tried was the latest (semi open) drivers from
> > > > dvbsky on a
> > > > 4.3 kernel. Here the CI and CAM registered successfully.
> > > > 
> > > > Greetings,
> > > > Jurgen
> > > > 
> > > > > Cheers,
> > > > > -olli
> > > > > 
> > > > > On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4al
> > > > > l.nl>
> > > > > wrote:
> > > > > > 
> > > > > > 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?
> > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > > --
> > > > > > To unsubscribe from this list: send the line "unsubscribe
> > > > > > linux-
> > > > > > media" in
> > > > > > the body of a message to majordomo@vger.kernel.org
> > > > > > More majordomo info at  http://vger.kernel.org/majordomo-in
> > > > > > fo.html
> > 
> > 

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

i have tested your patch with my dvbsky dvb-t2 card.
testing was done by compiling a custom kernel with your patch included.
test was done against fedora 22 4.3.4-200 kernel

with the patch included the CI slot is found.
so there is some progress for sure
-----
[   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw firmware 
(16382 bytes)
[   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
[   10.207968] cx23885[0]: cx23885 based dvb card
[   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
[   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully attached
[   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 
successfully attached
[   10.244560] DVB: registering new adapter (cx23885[0])
[   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0 frontend 
0 (Silicon Labs Si2168)...
[   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
[   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
[   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19, 
latency: 0, mmio: 0xf6e00000

later when tuning:

[   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
[   67.802203] si2168 10-0064: downloading firmware from file 
'dvb-demod-si2168-a20-01.fw'
[   68.968336] si2168 10-0064: firmware version: 2.0.5
[   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
[   69.961057] si2157 12-0060: downloading firmware from file 
'dvb-tuner-si2158-a20-01.fw'
[   70.969094] si2157 12-0060: firmware version: 2.1.9
----

but using dvbv5-scan to scan it doesn't find any channel.
all i get is this:
----
Scanning frequency #1 770000000
        (0x00) Signal= -114.00dBm
Scanning frequency #2 754000000
        (0x00) Signal= -27.00dBm C/N= 32.50dB
Scanning frequency #3 546000000
        (0x00) Signal= -25.00dBm C/N= 33.75dB
Scanning frequency #4 650000000
        (0x00) Signal= -18.00dBm C/N= 36.00dB
Scanning frequency #5 522000000
        (0x00) Signal= -28.00dBm C/N= 33.00dB
----

so something else is broken too.


On 2016-02-16 21:20, Olli Salonen wrote:
> Hi all,
>
> Found the issue and submitted a patch.
>
> The I2C buses for T980C/T2-4500CI were crossed when CI registration
> was moved to its own function.
>
> Cheers,
> -olli
>
> On 31 January 2016 at 10:55, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> this ci problem is the reason i decided to buy the CT2-4650 usb based device
>> instead.
>> but the 4650 was a slightly newer revision needing a patch i submitted
>> earlier.
>> and also this 4650 device does not have auto switching between dvb-t and t2
>> like the dvbsky card have, so i also need an updated version of mythtv.
>>
>> my long term wish is to not have to patch things or build custom kernels or
>> modules.
>> so anything done to improve the dvbsky card or the 4650 is much appreciated.
>>
>>
>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>
>>> Hi Jürgen & Mauro,
>>>
>>> I did bisect this and it seems this rather big patch broke it:
>>>
>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad commit
>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>
>>>       [media] cx23885: move CI/MAC registration to a separate function
>>>
>>>       As reported by smatch:
>>>           drivers/media/pci/cx23885/cx23885-dvb.c:2080 dvb_register()
>>> Function too hairy.  Giving up.
>>>
>>>       This is indeed a too complex function, with lots of stuff inside.
>>>       Breaking this into two functions makes it a little bit less hairy.
>>>
>>>       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>
>>> It's getting a bit late, so I'll call it a day now and have a look at
>>> the patch to see what goes wrong there.
>>>
>>> Cheers,
>>> -olli
>>>
>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>
>>>> Hi Olli,
>>>>
>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>
>>>>> Hi Jürgen,
>>>>>
>>>>> Did you get anywhere with this?
>>>>>
>>>>> I have a clone of your card and was just starting to look at this
>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you have any
>>>>> time to try to pinpoint this more?
>>>>
>>>> No, unfortunately not. I have spend a few hours adding printk's but it
>>>> did not get me any closer what causes the issue. This really needs
>>>> investigation from someone who is more familiar with linux media.
>>>>
>>>> Last thing I tried was the latest (semi open) drivers from dvbsky on a
>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>
>>>> Greetings,
>>>> Jurgen
>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>> wrote:
>>>>>>
>>>>>> 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?
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-
>>>>>> media" in
>>>>>> the body of a message to majordomo@vger.kernel.org
>>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

Hi,

On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
> i have tested your patch with my dvbsky dvb-t2 card.
> testing was done by compiling a custom kernel with your patch
> included.
> test was done against fedora 22 4.3.4-200 kernel
> 
> with the patch included the CI slot is found.
> so there is some progress for sure
> -----
> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
> firmware 
> (16382 bytes)
> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
> [   10.207968] cx23885[0]: cx23885 based dvb card
> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
> attached
> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 
> successfully attached
> [   10.244560] DVB: registering new adapter (cx23885[0])
> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
> frontend 
> 0 (Silicon Labs Si2168)...
> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19, 
> latency: 0, mmio: 0xf6e00000
> 
> later when tuning:
> 
> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
> [   67.802203] si2168 10-0064: downloading firmware from file 
> 'dvb-demod-si2168-a20-01.fw'
> [   68.968336] si2168 10-0064: firmware version: 2.0.5
> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
> [   69.961057] si2157 12-0060: downloading firmware from file 
> 'dvb-tuner-si2158-a20-01.fw'
> [   70.969094] si2157 12-0060: firmware version: 2.1.9
> ----
> 
> but using dvbv5-scan to scan it doesn't find any channel.
> all i get is this:
> ----
> Scanning frequency #1 770000000
>         (0x00) Signal= -114.00dBm
> Scanning frequency #2 754000000
>         (0x00) Signal= -27.00dBm C/N= 32.50dB
> Scanning frequency #3 546000000
>         (0x00) Signal= -25.00dBm C/N= 33.75dB
> Scanning frequency #4 650000000
>         (0x00) Signal= -18.00dBm C/N= 36.00dB
> Scanning frequency #5 522000000
>         (0x00) Signal= -28.00dBm C/N= 33.00dB
> ----
> 
> so something else is broken too.
> 
I have been using the patches for a few days. So far everything works
great (using MythTV). Scanning with dvbv5_scan does indeed not work
(never did for me). w_scan works though.

Can these patches please be included in the stable kernels ?

Jurgen


> On 2016-02-16 21:20, Olli Salonen wrote:
> > Hi all,
> > 
> > Found the issue and submitted a patch.
> > 
> > The I2C buses for T980C/T2-4500CI were crossed when CI registration
> > was moved to its own function.
> > 
> > Cheers,
> > -olli
> > 
> > On 31 January 2016 at 10:55, Torbjorn Jansson
> > <torbjorn.jansson@mbox200.swipnet.se> wrote:
> > > this ci problem is the reason i decided to buy the CT2-4650 usb
> > > based device
> > > instead.
> > > but the 4650 was a slightly newer revision needing a patch i
> > > submitted
> > > earlier.
> > > and also this 4650 device does not have auto switching between
> > > dvb-t and t2
> > > like the dvbsky card have, so i also need an updated version of
> > > mythtv.
> > > 
> > > my long term wish is to not have to patch things or build custom
> > > kernels or
> > > modules.
> > > so anything done to improve the dvbsky card or the 4650 is much
> > > appreciated.
> > > 
> > > 
> > > On 2016-01-28 20:42, Olli Salonen wrote:
> > > > 
> > > > Hi Jürgen & Mauro,
> > > > 
> > > > I did bisect this and it seems this rather big patch broke it:
> > > > 
> > > > 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
> > > > commit
> > > > commit 2b0aac3011bc7a9db27791bed4978554263ef079
> > > > Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > > > Date:   Tue Dec 23 13:48:07 2014 -0200
> > > > 
> > > >       [media] cx23885: move CI/MAC registration to a separate
> > > > function
> > > > 
> > > >       As reported by smatch:
> > > >           drivers/media/pci/cx23885/cx23885-dvb.c:2080
> > > > dvb_register()
> > > > Function too hairy.  Giving up.
> > > > 
> > > >       This is indeed a too complex function, with lots of stuff
> > > > inside.
> > > >       Breaking this into two functions makes it a little bit
> > > > less hairy.
> > > > 
> > > >       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
> > > > .com>
> > > > 
> > > > It's getting a bit late, so I'll call it a day now and have a
> > > > look at
> > > > the patch to see what goes wrong there.
> > > > 
> > > > Cheers,
> > > > -olli
> > > > 
> > > > On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
> > > > > wrote:
> > > > > 
> > > > > Hi Olli,
> > > > > 
> > > > > On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
> > > > > > 
> > > > > > Hi Jürgen,
> > > > > > 
> > > > > > Did you get anywhere with this?
> > > > > > 
> > > > > > I have a clone of your card and was just starting to look
> > > > > > at this
> > > > > > issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
> > > > > > have any
> > > > > > time to try to pinpoint this more?
> > > > > 
> > > > > No, unfortunately not. I have spend a few hours adding
> > > > > printk's but it
> > > > > did not get me any closer what causes the issue. This really
> > > > > needs
> > > > > investigation from someone who is more familiar with linux
> > > > > media.
> > > > > 
> > > > > Last thing I tried was the latest (semi open) drivers from
> > > > > dvbsky on a
> > > > > 4.3 kernel. Here the CI and CAM registered successfully.
> > > > > 
> > > > > Greetings,
> > > > > Jurgen
> > > > > 
> > > > > > Cheers,
> > > > > > -olli
> > > > > > 
> > > > > > On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
> > > > > > all.nl>
> > > > > > wrote:
> > > > > > > 
> > > > > > > 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?
> > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > --
> > > > > > > To unsubscribe from this list: send the line "unsubscribe
> > > > > > > linux-
> > > > > > > media" in
> > > > > > > the body of a message to majordomo@vger.kernel.org
> > > > > > > More majordomo info at  http://vger.kernel.org/majordomo-
> > > > > > > info.html
> 

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

On 2016-02-20 18:20, Jurgen Kramer wrote:
> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>> so something else is broken too.
>>
> I have been using the patches for a few days. So far everything works
> great (using MythTV). Scanning with dvbv5_scan does indeed not work
> (never did for me). w_scan works though.
>

interesting.
sounds like i need to test this again.

am i right in assuming that you are running mythtv 0.27 or have you 
switched the newer code?
reason for asking is because 0.27 don't know how to change between t & 
t2 and it relies on the driver to auto switch but this fixed (or will be 
once released) in 0.28

maybe someone here can explain why dvbv5-scan doesn't work with this 
dvbsky card?
or should i retest with latest code from media_tree ?

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Jurgen, Torbjörn,

I've noticed that there is currently a small confusion about the
firmware versions for the Si2168-A20 demodulator. This is used in the
older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
T980C (TechnoTrend CT2-4500 CI).

The version 2.0.5 does not support PLP handling and seems to work very
badly with the Linux driver - at least for me. Version 2.0.35 on the
other hand seems to find all DVB-T/T2 channels for me just fine with
both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
CT2-4650 CI and TechnoTrend CT2-4500 CI new version).

Versions used:
dvbv5-scan version 1.7.0
w_scan version 20150111 (compiled for DVB API 5.10)

So if you are running these Si2168-A20 based devices, make sure you've
got the firmware 2.0.35 that can be downloaded for example here:
http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/

Cheers,
-olli

On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
> Hi,
>
> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>> i have tested your patch with my dvbsky dvb-t2 card.
>> testing was done by compiling a custom kernel with your patch
>> included.
>> test was done against fedora 22 4.3.4-200 kernel
>>
>> with the patch included the CI slot is found.
>> so there is some progress for sure
>> -----
>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>> firmware
>> (16382 bytes)
>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>> [   10.207968] cx23885[0]: cx23885 based dvb card
>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>> attached
>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>> successfully attached
>> [   10.244560] DVB: registering new adapter (cx23885[0])
>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>> frontend
>> 0 (Silicon Labs Si2168)...
>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>> latency: 0, mmio: 0xf6e00000
>>
>> later when tuning:
>>
>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>> [   67.802203] si2168 10-0064: downloading firmware from file
>> 'dvb-demod-si2168-a20-01.fw'
>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>> [   69.961057] si2157 12-0060: downloading firmware from file
>> 'dvb-tuner-si2158-a20-01.fw'
>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>> ----
>>
>> but using dvbv5-scan to scan it doesn't find any channel.
>> all i get is this:
>> ----
>> Scanning frequency #1 770000000
>>         (0x00) Signal= -114.00dBm
>> Scanning frequency #2 754000000
>>         (0x00) Signal= -27.00dBm C/N= 32.50dB
>> Scanning frequency #3 546000000
>>         (0x00) Signal= -25.00dBm C/N= 33.75dB
>> Scanning frequency #4 650000000
>>         (0x00) Signal= -18.00dBm C/N= 36.00dB
>> Scanning frequency #5 522000000
>>         (0x00) Signal= -28.00dBm C/N= 33.00dB
>> ----
>>
>> so something else is broken too.
>>
> I have been using the patches for a few days. So far everything works
> great (using MythTV). Scanning with dvbv5_scan does indeed not work
> (never did for me). w_scan works though.
>
> Can these patches please be included in the stable kernels ?
>
> Jurgen
>
>
>> On 2016-02-16 21:20, Olli Salonen wrote:
>> > Hi all,
>> >
>> > Found the issue and submitted a patch.
>> >
>> > The I2C buses for T980C/T2-4500CI were crossed when CI registration
>> > was moved to its own function.
>> >
>> > Cheers,
>> > -olli
>> >
>> > On 31 January 2016 at 10:55, Torbjorn Jansson
>> > <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> > > this ci problem is the reason i decided to buy the CT2-4650 usb
>> > > based device
>> > > instead.
>> > > but the 4650 was a slightly newer revision needing a patch i
>> > > submitted
>> > > earlier.
>> > > and also this 4650 device does not have auto switching between
>> > > dvb-t and t2
>> > > like the dvbsky card have, so i also need an updated version of
>> > > mythtv.
>> > >
>> > > my long term wish is to not have to patch things or build custom
>> > > kernels or
>> > > modules.
>> > > so anything done to improve the dvbsky card or the 4650 is much
>> > > appreciated.
>> > >
>> > >
>> > > On 2016-01-28 20:42, Olli Salonen wrote:
>> > > >
>> > > > Hi Jürgen & Mauro,
>> > > >
>> > > > I did bisect this and it seems this rather big patch broke it:
>> > > >
>> > > > 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>> > > > commit
>> > > > commit 2b0aac3011bc7a9db27791bed4978554263ef079
>> > > > Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>> > > > Date:   Tue Dec 23 13:48:07 2014 -0200
>> > > >
>> > > >       [media] cx23885: move CI/MAC registration to a separate
>> > > > function
>> > > >
>> > > >       As reported by smatch:
>> > > >           drivers/media/pci/cx23885/cx23885-dvb.c:2080
>> > > > dvb_register()
>> > > > Function too hairy.  Giving up.
>> > > >
>> > > >       This is indeed a too complex function, with lots of stuff
>> > > > inside.
>> > > >       Breaking this into two functions makes it a little bit
>> > > > less hairy.
>> > > >
>> > > >       Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>> > > > .com>
>> > > >
>> > > > It's getting a bit late, so I'll call it a day now and have a
>> > > > look at
>> > > > the patch to see what goes wrong there.
>> > > >
>> > > > Cheers,
>> > > > -olli
>> > > >
>> > > > On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>> > > > > wrote:
>> > > > >
>> > > > > Hi Olli,
>> > > > >
>> > > > > On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>> > > > > >
>> > > > > > Hi Jürgen,
>> > > > > >
>> > > > > > Did you get anywhere with this?
>> > > > > >
>> > > > > > I have a clone of your card and was just starting to look
>> > > > > > at this
>> > > > > > issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>> > > > > > have any
>> > > > > > time to try to pinpoint this more?
>> > > > >
>> > > > > No, unfortunately not. I have spend a few hours adding
>> > > > > printk's but it
>> > > > > did not get me any closer what causes the issue. This really
>> > > > > needs
>> > > > > investigation from someone who is more familiar with linux
>> > > > > media.
>> > > > >
>> > > > > Last thing I tried was the latest (semi open) drivers from
>> > > > > dvbsky on a
>> > > > > 4.3 kernel. Here the CI and CAM registered successfully.
>> > > > >
>> > > > > Greetings,
>> > > > > Jurgen
>> > > > >
>> > > > > > Cheers,
>> > > > > > -olli
>> > > > > >
>> > > > > > On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>> > > > > > all.nl>
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > 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?
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > --
>> > > > > > > To unsubscribe from this list: send the line "unsubscribe
>> > > > > > > linux-
>> > > > > > > media" in
>> > > > > > > the body of a message to majordomo@vger.kernel.org
>> > > > > > > More majordomo info at  http://vger.kernel.org/majordomo-
>> > > > > > > info.html
>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

i was about to ask how to easiest see what firmware i was running 
without rebooting when i realized i already have it in this mail thread ;)

all of the firmware i'm running is the ones that came from dvbsky 
directly in this file:
http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz

i suspect i should go thru all of the firmware files i use since if one 
is bad the other ones is probably also bad.

i assume i also should also check: dvb-tuner-si2158-a20-01.fw
what version is a good one? i have found 2 different files:

the one i current usefrom dvbsky, also same as OpenELEC fw repo uses 
with md5sum:
8e98d25d6219e235b519a3c47dbfa856  dvb-tuner-si2158-a20-01.fw

and then i found another one at 
http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/Si2158-A20/
0cba7ce61c1411cbe7f22c0746e24e33  dvb-tuner-si2158-a20-01.fw
this file is a bit smaller.

i will retest with the new firmware you suggested and see what happens.


On 2016-03-03 12:02, Olli Salonen wrote:
> Hi Jurgen, Torbjörn,
>
> I've noticed that there is currently a small confusion about the
> firmware versions for the Si2168-A20 demodulator. This is used in the
> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
> T980C (TechnoTrend CT2-4500 CI).
>
> The version 2.0.5 does not support PLP handling and seems to work very
> badly with the Linux driver - at least for me. Version 2.0.35 on the
> other hand seems to find all DVB-T/T2 channels for me just fine with
> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>
> Versions used:
> dvbv5-scan version 1.7.0
> w_scan version 20150111 (compiled for DVB API 5.10)
>
> So if you are running these Si2168-A20 based devices, make sure you've
> got the firmware 2.0.35 that can be downloaded for example here:
> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/
>
> Cheers,
> -olli
>
> On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>> Hi,
>>
>> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>>> i have tested your patch with my dvbsky dvb-t2 card.
>>> testing was done by compiling a custom kernel with your patch
>>> included.
>>> test was done against fedora 22 4.3.4-200 kernel
>>>
>>> with the patch included the CI slot is found.
>>> so there is some progress for sure
>>> -----
>>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>>> firmware
>>> (16382 bytes)
>>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>>> [   10.207968] cx23885[0]: cx23885 based dvb card
>>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>>> attached
>>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>>> successfully attached
>>> [   10.244560] DVB: registering new adapter (cx23885[0])
>>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>>> frontend
>>> 0 (Silicon Labs Si2168)...
>>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>>> latency: 0, mmio: 0xf6e00000
>>>
>>> later when tuning:
>>>
>>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>>> [   67.802203] si2168 10-0064: downloading firmware from file
>>> 'dvb-demod-si2168-a20-01.fw'
>>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>>> [   69.961057] si2157 12-0060: downloading firmware from file
>>> 'dvb-tuner-si2158-a20-01.fw'
>>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>>> ----
>>>
>>> but using dvbv5-scan to scan it doesn't find any channel.
>>> all i get is this:
>>> ----
>>> Scanning frequency #1 770000000
>>>          (0x00) Signal= -114.00dBm
>>> Scanning frequency #2 754000000
>>>          (0x00) Signal= -27.00dBm C/N= 32.50dB
>>> Scanning frequency #3 546000000
>>>          (0x00) Signal= -25.00dBm C/N= 33.75dB
>>> Scanning frequency #4 650000000
>>>          (0x00) Signal= -18.00dBm C/N= 36.00dB
>>> Scanning frequency #5 522000000
>>>          (0x00) Signal= -28.00dBm C/N= 33.00dB
>>> ----
>>>
>>> so something else is broken too.
>>>
>> I have been using the patches for a few days. So far everything works
>> great (using MythTV). Scanning with dvbv5_scan does indeed not work
>> (never did for me). w_scan works though.
>>
>> Can these patches please be included in the stable kernels ?
>>
>> Jurgen
>>
>>
>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>> Hi all,
>>>>
>>>> Found the issue and submitted a patch.
>>>>
>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>> was moved to its own function.
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb
>>>>> based device
>>>>> instead.
>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>> submitted
>>>>> earlier.
>>>>> and also this 4650 device does not have auto switching between
>>>>> dvb-t and t2
>>>>> like the dvbsky card have, so i also need an updated version of
>>>>> mythtv.
>>>>>
>>>>> my long term wish is to not have to patch things or build custom
>>>>> kernels or
>>>>> modules.
>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>> appreciated.
>>>>>
>>>>>
>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>
>>>>>> Hi Jürgen & Mauro,
>>>>>>
>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>
>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>>>>>> commit
>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>
>>>>>>        [media] cx23885: move CI/MAC registration to a separate
>>>>>> function
>>>>>>
>>>>>>        As reported by smatch:
>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>> dvb_register()
>>>>>> Function too hairy.  Giving up.
>>>>>>
>>>>>>        This is indeed a too complex function, with lots of stuff
>>>>>> inside.
>>>>>>        Breaking this into two functions makes it a little bit
>>>>>> less hairy.
>>>>>>
>>>>>>        Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>>>>>> .com>
>>>>>>
>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>> look at
>>>>>> the patch to see what goes wrong there.
>>>>>>
>>>>>> Cheers,
>>>>>> -olli
>>>>>>
>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Olli,
>>>>>>>
>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>
>>>>>>>> Hi Jürgen,
>>>>>>>>
>>>>>>>> Did you get anywhere with this?
>>>>>>>>
>>>>>>>> I have a clone of your card and was just starting to look
>>>>>>>> at this
>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>>>>>>>> have any
>>>>>>>> time to try to pinpoint this more?
>>>>>>>
>>>>>>> No, unfortunately not. I have spend a few hours adding
>>>>>>> printk's but it
>>>>>>> did not get me any closer what causes the issue. This really
>>>>>>> needs
>>>>>>> investigation from someone who is more familiar with linux
>>>>>>> media.
>>>>>>>
>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>> dvbsky on a
>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Jurgen
>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -olli
>>>>>>>>
>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>>>>>>>> all.nl>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> 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?
>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

using a 4.2 kernel i get a bit further but now i'm getting a completely 
different oops:
[  181.077662] BUG: unable to handle kernel NULL pointer dereference at 
0000000000000010
[  181.077723] IP: [<ffffffffa05c0fd9>] 
v4l_vb2q_enable_media_source+0x9/0x40 [videodev]

latest git code is too unstable for testing this.
i will instead try to redo my test by rebuilding the kernel rpms and 
include the patch to fix the CI.

the point of the test i was trying to do was to try the newer version of 
the firmware and see if that improved things.


On 2016-03-04 05:42, Olli Salonen wrote:
> Hi,
>
> You probably have kernel 4.3 or newer? I've seen this same happening
> as well. It's probable that the media_build will be updated in the
> coming days to fix this, but so far I did not found an easy way out.
> Kernel 4.2 or older works fine though.
>
> Hans Verkuil is the resident media_build guru, so maybe he can help
> you with that...
>
> Cheers,
> -olli
>
>
> On 4 March 2016 at 00:03, Torbjorn Jansson
> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>> found something, modprobe results in the following dmesg message:
>>
>> frame_vector: exports duplicate symbol frame_vector_create (owned by kernel)
>>
>> every time i do a modprobe of cx23885
>> what does this mean?
>>
>> On 2016-03-03 22:58, Torbjorn Jansson wrote:
>>>
>>> i'm having a bit of a problem testing the changed firmware on my t980c
>>> card.
>>>
>>> complied the code from media_tree and i get the usb card to work with
>>> those modules but for some reason modprobe of cx23885 results in:
>>> # modprobe cx23885
>>> modprobe: ERROR: could not insert 'cx23885': Exec format error
>>>
>>> all the other modules work just fine, i'm not sure what i'm doing wrong.
>>>
>>>
>>> On 2016-03-03 19:22, Torbjorn Jansson wrote:
>>>>
>>>> i was about to ask how to easiest see what firmware i was running
>>>> without rebooting when i realized i already have it in this mail
>>>> thread ;)
>>>>
>>>> all of the firmware i'm running is the ones that came from dvbsky
>>>> directly in this file:
>>>> http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz
>>>>
>>>> i suspect i should go thru all of the firmware files i use since if one
>>>> is bad the other ones is probably also bad.
>>>>
>>>> i assume i also should also check: dvb-tuner-si2158-a20-01.fw
>>>> what version is a good one? i have found 2 different files:
>>>>
>>>> the one i current usefrom dvbsky, also same as OpenELEC fw repo uses
>>>> with md5sum:
>>>> 8e98d25d6219e235b519a3c47dbfa856  dvb-tuner-si2158-a20-01.fw
>>>>
>>>> and then i found another one at
>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/Si2158-A20/
>>>> 0cba7ce61c1411cbe7f22c0746e24e33  dvb-tuner-si2158-a20-01.fw
>>>> this file is a bit smaller.
>>>>
>>>> i will retest with the new firmware you suggested and see what happens.
>>>>
>>>>
>>>> On 2016-03-03 12:02, Olli Salonen wrote:
>>>>>
>>>>> Hi Jurgen, Torbjörn,
>>>>>
>>>>> I've noticed that there is currently a small confusion about the
>>>>> firmware versions for the Si2168-A20 demodulator. This is used in the
>>>>> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
>>>>> T980C (TechnoTrend CT2-4500 CI).
>>>>>
>>>>> The version 2.0.5 does not support PLP handling and seems to work very
>>>>> badly with the Linux driver - at least for me. Version 2.0.35 on the
>>>>> other hand seems to find all DVB-T/T2 channels for me just fine with
>>>>> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
>>>>> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>>>>>
>>>>> Versions used:
>>>>> dvbv5-scan version 1.7.0
>>>>> w_scan version 20150111 (compiled for DVB API 5.10)
>>>>>
>>>>> So if you are running these Si2168-A20 based devices, make sure you've
>>>>> got the firmware 2.0.35 that can be downloaded for example here:
>>>>>
>>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/
>>>>>
>>>>>
>>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>>>>>>>
>>>>>>> i have tested your patch with my dvbsky dvb-t2 card.
>>>>>>> testing was done by compiling a custom kernel with your patch
>>>>>>> included.
>>>>>>> test was done against fedora 22 4.3.4-200 kernel
>>>>>>>
>>>>>>> with the patch included the CI slot is found.
>>>>>>> so there is some progress for sure
>>>>>>> -----
>>>>>>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>>>>>>> firmware
>>>>>>> (16382 bytes)
>>>>>>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>>>>>>> [   10.207968] cx23885[0]: cx23885 based dvb card
>>>>>>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>>>>>>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>>>>>>> attached
>>>>>>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>>>>>>> successfully attached
>>>>>>> [   10.244560] DVB: registering new adapter (cx23885[0])
>>>>>>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>>>>>>> frontend
>>>>>>> 0 (Silicon Labs Si2168)...
>>>>>>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>>>>>>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>>>>>>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>>>>>>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>>>>>>> latency: 0, mmio: 0xf6e00000
>>>>>>>
>>>>>>> later when tuning:
>>>>>>>
>>>>>>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>>>>>>> [   67.802203] si2168 10-0064: downloading firmware from file
>>>>>>> 'dvb-demod-si2168-a20-01.fw'
>>>>>>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>>>>>>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>>>>>>> [   69.961057] si2157 12-0060: downloading firmware from file
>>>>>>> 'dvb-tuner-si2158-a20-01.fw'
>>>>>>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>>>>>>> ----
>>>>>>>
>>>>>>> but using dvbv5-scan to scan it doesn't find any channel.
>>>>>>> all i get is this:
>>>>>>> ----
>>>>>>> Scanning frequency #1 770000000
>>>>>>>           (0x00) Signal= -114.00dBm
>>>>>>> Scanning frequency #2 754000000
>>>>>>>           (0x00) Signal= -27.00dBm C/N= 32.50dB
>>>>>>> Scanning frequency #3 546000000
>>>>>>>           (0x00) Signal= -25.00dBm C/N= 33.75dB
>>>>>>> Scanning frequency #4 650000000
>>>>>>>           (0x00) Signal= -18.00dBm C/N= 36.00dB
>>>>>>> Scanning frequency #5 522000000
>>>>>>>           (0x00) Signal= -28.00dBm C/N= 33.00dB
>>>>>>> ----
>>>>>>>
>>>>>>> so something else is broken too.
>>>>>>>
>>>>>> I have been using the patches for a few days. So far everything works
>>>>>> great (using MythTV). Scanning with dvbv5_scan does indeed not work
>>>>>> (never did for me). w_scan works though.
>>>>>>
>>>>>> Can these patches please be included in the stable kernels ?
>>>>>>
>>>>>> Jurgen
>>>>>>
>>>>>>
>>>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Found the issue and submitted a patch.
>>>>>>>>
>>>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>>>> was moved to its own function.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -olli
>>>>>>>>
>>>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>>>
>>>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb
>>>>>>>>> based device
>>>>>>>>> instead.
>>>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>>>> submitted
>>>>>>>>> earlier.
>>>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>>>> dvb-t and t2
>>>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>>>> mythtv.
>>>>>>>>>
>>>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>>>> kernels or
>>>>>>>>> modules.
>>>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>>>> appreciated.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>>>
>>>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>>>
>>>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>>>>>>>>>> commit
>>>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>>>
>>>>>>>>>>         [media] cx23885: move CI/MAC registration to a separate
>>>>>>>>>> function
>>>>>>>>>>
>>>>>>>>>>         As reported by smatch:
>>>>>>>>>>             drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>>>> dvb_register()
>>>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>>>
>>>>>>>>>>         This is indeed a too complex function, with lots of stuff
>>>>>>>>>> inside.
>>>>>>>>>>         Breaking this into two functions makes it a little bit
>>>>>>>>>> less hairy.
>>>>>>>>>>
>>>>>>>>>>         Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>>>>>>>>>> .com>
>>>>>>>>>>
>>>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>>>> look at
>>>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> -olli
>>>>>>>>>>
>>>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Olli,
>>>>>>>>>>>
>>>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>>>
>>>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>>>
>>>>>>>>>>>> I have a clone of your card and was just starting to look
>>>>>>>>>>>> at this
>>>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>>>>>>>>>>>> have any
>>>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> No, unfortunately not. I have spend a few hours adding
>>>>>>>>>>> printk's but it
>>>>>>>>>>> did not get me any closer what causes the issue. This really
>>>>>>>>>>> needs
>>>>>>>>>>> investigation from someone who is more familiar with linux
>>>>>>>>>>> media.
>>>>>>>>>>>
>>>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>>>> dvbsky on a
>>>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>>>
>>>>>>>>>>> Greetings,
>>>>>>>>>>> Jurgen
>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> -olli
>>>>>>>>>>>>
>>>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>>>>>>>>>>>> all.nl>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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?
>>>>>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

that worked a bit better.

first some dmesg output for reference:
[   15.002224] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw firmware 
(16382 bytes)
[   15.019548] cx23885_dvb_register() allocating 1 frontend(s)
[   15.021444] cx23885[0]: cx23885 based dvb card
[   15.169994] i2c i2c-10: Added multiplexed i2c bus 12
[   15.172514] si2168 10-0064: Silicon Labs Si2168 successfully attached
[   15.232989] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 
successfully attached
[   15.235445] DVB: registering new adapter (cx23885[0])
[   15.237911] cx23885 0000:07:00.0: DVB: registering adapter 0 frontend 
0 (Silicon Labs Si2168)...
[   15.383847] sp2 9-0040: CIMaX SP2 successfully attached
[   15.414270] DVBSky T980C MAC address: 00:17:42:54:09:85
[   15.416377] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   15.418433] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19, 
latency: 0, mmio: 0xf6e00000

[   21.612743] dvb_ca adapter 0: DVB CAM detected and initialised 
successfully


[   61.890098] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
[   62.000956] si2168 10-0064: downloading firmware from file 
'dvb-demod-si2168-a20-01.fw'
[   67.113044] si2168 10-0064: firmware version: 2.0.35
[   67.121721] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
[   67.147054] si2157 12-0060: downloading firmware from file 
'dvb-tuner-si2158-a20-01.fw'
[   68.155814] si2157 12-0060: firmware version: 2.1.9



first test:
looks like it locks on and this time also the dvb-t2 muxes.
BUT output of w_scan for each found mux is like this:
770000: (time: 03:31.238)         signal ok:    QAM_AUTO f = 770000 kHz 
I999B8C999D999T999G999Y999P0 (0:0:0)
         Info: no data from PAT after 2 seconds
         deleting (QAM_AUTO f = 770000 kHz I999B8C999D999T999G999Y999P0 
(0:0:0))

and finally:
ERROR: Sorry - i couldn't get any working frequency/transponder
  Nothing to scan!!


and w_scan never outputs the channel names as it normally does at the end.

second test:
unplug CA module and reinsert.
this is normally needed before i get picture with other programs than 
w_scan.

this did not result in any change, w_scan still outputs "no data from 
PAT after 2 seconds" for each found frequency.


third test:
remove CA module and repeat.
Success!
both t2 muxes was found and w_scan showed what looked like the complete 
channel list.


forth test:
now that it is working, reinsert CA module and retest.
problem is back.
same error as previous tests with CA module inserted "no data from PAT 
after 2 seconds" on each locked on frequency.



a comment regarding the CA module.
no matter what driver i have used, the dvbsky binary blob driver or 
linux-media driver or kernels built in driver all of them have had minor 
CA issues.

at every boot i need to first tune to a dvb channel then unplug the CA 
module and reinsert it, when this is done the channel starts working.
if i don't do this manually i will never get a picture.

i guess this could be an application issue too since sending a CA_RESET 
also seems to fix it, but because of how the program i use work doing a 
good test is a bit hard.



On 2016-03-05 06:36, Olli Salonen wrote:
> Hi Torbjörn,
>
> Apply the recent patch from Shuah to fix that recent oops:
>
> https://patchwork.linuxtv.org/patch/33353/
>
> It's not yet in the media_tree, but I reckon it'll be there shortly...
>
> Cheers,
> Olli
> On 5 Mar 2016 1:09 a.m., "Torbjorn Jansson" <
> torbjorn.jansson@mbox200.swipnet.se> wrote:
>
>> using a 4.2 kernel i get a bit further but now i'm getting a completely
>> different oops:
>> [  181.077662] BUG: unable to handle kernel NULL pointer dereference at
>> 0000000000000010
>> [  181.077723] IP: [<ffffffffa05c0fd9>]
>> v4l_vb2q_enable_media_source+0x9/0x40 [videodev]
>>
>> latest git code is too unstable for testing this.
>> i will instead try to redo my test by rebuilding the kernel rpms and
>> include the patch to fix the CI.
>>
>> the point of the test i was trying to do was to try the newer version of
>> the firmware and see if that improved things.
>>
>>
>> On 2016-03-04 05:42, Olli Salonen wrote:
>>
>>> Hi,
>>>
>>> You probably have kernel 4.3 or newer? I've seen this same happening
>>> as well. It's probable that the media_build will be updated in the
>>> coming days to fix this, but so far I did not found an easy way out.
>>> Kernel 4.2 or older works fine though.
>>>
>>> Hans Verkuil is the resident media_build guru, so maybe he can help
>>> you with that...
>>>
>>> Cheers,
>>> -olli
>>>
>>>
>>> On 4 March 2016 at 00:03, Torbjorn Jansson
>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>
>>>> found something, modprobe results in the following dmesg message:
>>>>
>>>> frame_vector: exports duplicate symbol frame_vector_create (owned by
>>>> kernel)
>>>>
>>>> every time i do a modprobe of cx23885
>>>> what does this mean?
>>>>
>>>> On 2016-03-03 22:58, Torbjorn Jansson wrote:
>>>>
>>>>>
>>>>> i'm having a bit of a problem testing the changed firmware on my t980c
>>>>> card.
>>>>>
>>>>> complied the code from media_tree and i get the usb card to work with
>>>>> those modules but for some reason modprobe of cx23885 results in:
>>>>> # modprobe cx23885
>>>>> modprobe: ERROR: could not insert 'cx23885': Exec format error
>>>>>
>>>>> all the other modules work just fine, i'm not sure what i'm doing wrong.
>>>>>
>>>>>
>>>>> On 2016-03-03 19:22, Torbjorn Jansson wrote:
>>>>>
>>>>>>
>>>>>> i was about to ask how to easiest see what firmware i was running
>>>>>> without rebooting when i realized i already have it in this mail
>>>>>> thread ;)
>>>>>>
>>>>>> all of the firmware i'm running is the ones that came from dvbsky
>>>>>> directly in this file:
>>>>>> http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz
>>>>>>
>>>>>> i suspect i should go thru all of the firmware files i use since if one
>>>>>> is bad the other ones is probably also bad.
>>>>>>
>>>>>> i assume i also should also check: dvb-tuner-si2158-a20-01.fw
>>>>>> what version is a good one? i have found 2 different files:
>>>>>>
>>>>>> the one i current usefrom dvbsky, also same as OpenELEC fw repo uses
>>>>>> with md5sum:
>>>>>> 8e98d25d6219e235b519a3c47dbfa856  dvb-tuner-si2158-a20-01.fw
>>>>>>
>>>>>> and then i found another one at
>>>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/Si2158-A20/
>>>>>> 0cba7ce61c1411cbe7f22c0746e24e33  dvb-tuner-si2158-a20-01.fw
>>>>>> this file is a bit smaller.
>>>>>>
>>>>>> i will retest with the new firmware you suggested and see what happens.
>>>>>>
>>>>>>
>>>>>> On 2016-03-03 12:02, Olli Salonen wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi Jurgen, Torbjörn,
>>>>>>>
>>>>>>> I've noticed that there is currently a small confusion about the
>>>>>>> firmware versions for the Si2168-A20 demodulator. This is used in the
>>>>>>> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
>>>>>>> T980C (TechnoTrend CT2-4500 CI).
>>>>>>>
>>>>>>> The version 2.0.5 does not support PLP handling and seems to work very
>>>>>>> badly with the Linux driver - at least for me. Version 2.0.35 on the
>>>>>>> other hand seems to find all DVB-T/T2 channels for me just fine with
>>>>>>> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
>>>>>>> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>>>>>>>
>>>>>>> Versions used:
>>>>>>> dvbv5-scan version 1.7.0
>>>>>>> w_scan version 20150111 (compiled for DVB API 5.10)
>>>>>>>
>>>>>>> So if you are running these Si2168-A20 based devices, make sure you've
>>>>>>> got the firmware 2.0.35 that can be downloaded for example here:
>>>>>>>
>>>>>>>
>>>>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>> -olli
>>>>>>>
>>>>>>> On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> i have tested your patch with my dvbsky dvb-t2 card.
>>>>>>>>> testing was done by compiling a custom kernel with your patch
>>>>>>>>> included.
>>>>>>>>> test was done against fedora 22 4.3.4-200 kernel
>>>>>>>>>
>>>>>>>>> with the patch included the CI slot is found.
>>>>>>>>> so there is some progress for sure
>>>>>>>>> -----
>>>>>>>>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>>>>>>>>> firmware
>>>>>>>>> (16382 bytes)
>>>>>>>>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>>>>>>>>> [   10.207968] cx23885[0]: cx23885 based dvb card
>>>>>>>>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>>>>>>>>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>>>>>>>>> attached
>>>>>>>>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>>>>>>>>> successfully attached
>>>>>>>>> [   10.244560] DVB: registering new adapter (cx23885[0])
>>>>>>>>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>>>>>>>>> frontend
>>>>>>>>> 0 (Silicon Labs Si2168)...
>>>>>>>>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>>>>>>>>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>>>>>>>>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>>>>>>>>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>>>>>>>>> latency: 0, mmio: 0xf6e00000
>>>>>>>>>
>>>>>>>>> later when tuning:
>>>>>>>>>
>>>>>>>>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>>>>>>>>> [   67.802203] si2168 10-0064: downloading firmware from file
>>>>>>>>> 'dvb-demod-si2168-a20-01.fw'
>>>>>>>>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>>>>>>>>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>>>>>>>>> [   69.961057] si2157 12-0060: downloading firmware from file
>>>>>>>>> 'dvb-tuner-si2158-a20-01.fw'
>>>>>>>>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>>>>>>>>> ----
>>>>>>>>>
>>>>>>>>> but using dvbv5-scan to scan it doesn't find any channel.
>>>>>>>>> all i get is this:
>>>>>>>>> ----
>>>>>>>>> Scanning frequency #1 770000000
>>>>>>>>>            (0x00) Signal= -114.00dBm
>>>>>>>>> Scanning frequency #2 754000000
>>>>>>>>>            (0x00) Signal= -27.00dBm C/N= 32.50dB
>>>>>>>>> Scanning frequency #3 546000000
>>>>>>>>>            (0x00) Signal= -25.00dBm C/N= 33.75dB
>>>>>>>>> Scanning frequency #4 650000000
>>>>>>>>>            (0x00) Signal= -18.00dBm C/N= 36.00dB
>>>>>>>>> Scanning frequency #5 522000000
>>>>>>>>>            (0x00) Signal= -28.00dBm C/N= 33.00dB
>>>>>>>>> ----
>>>>>>>>>
>>>>>>>>> so something else is broken too.
>>>>>>>>>
>>>>>>>>> I have been using the patches for a few days. So far everything
>>>>>>>> works
>>>>>>>> great (using MythTV). Scanning with dvbv5_scan does indeed not work
>>>>>>>> (never did for me). w_scan works though.
>>>>>>>>
>>>>>>>> Can these patches please be included in the stable kernels ?
>>>>>>>>
>>>>>>>> Jurgen
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> Found the issue and submitted a patch.
>>>>>>>>>>
>>>>>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>>>>>> was moved to its own function.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> -olli
>>>>>>>>>>
>>>>>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb
>>>>>>>>>>> based device
>>>>>>>>>>> instead.
>>>>>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>>>>>> submitted
>>>>>>>>>>> earlier.
>>>>>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>>>>>> dvb-t and t2
>>>>>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>>>>>> mythtv.
>>>>>>>>>>>
>>>>>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>>>>>> kernels or
>>>>>>>>>>> modules.
>>>>>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>>>>>> appreciated.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>>>>>
>>>>>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>>>>>
>>>>>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>>>>>>>>>>>> commit
>>>>>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>>>>>
>>>>>>>>>>>>          [media] cx23885: move CI/MAC registration to a separate
>>>>>>>>>>>> function
>>>>>>>>>>>>
>>>>>>>>>>>>          As reported by smatch:
>>>>>>>>>>>>              drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>>>>>> dvb_register()
>>>>>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>>>>>
>>>>>>>>>>>>          This is indeed a too complex function, with lots of stuff
>>>>>>>>>>>> inside.
>>>>>>>>>>>>          Breaking this into two functions makes it a little bit
>>>>>>>>>>>> less hairy.
>>>>>>>>>>>>
>>>>>>>>>>>>          Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>>>>>>>>>>>> .com>
>>>>>>>>>>>>
>>>>>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>>>>>> look at
>>>>>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> -olli
>>>>>>>>>>>>
>>>>>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Olli,
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have a clone of your card and was just starting to look
>>>>>>>>>>>>>> at this
>>>>>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>>>>>>>>>>>>>> have any
>>>>>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> No, unfortunately not. I have spend a few hours adding
>>>>>>>>>>>>> printk's but it
>>>>>>>>>>>>> did not get me any closer what causes the issue. This really
>>>>>>>>>>>>> needs
>>>>>>>>>>>>> investigation from someone who is more familiar with linux
>>>>>>>>>>>>> media.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>>>>>> dvbsky on a
>>>>>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Greetings,
>>>>>>>>>>>>> Jurgen
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>> -olli
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>>>>>>>>>>>>>> all.nl>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

FYI i still get "Exec format error" while modprobing cx23885 with 
media_build from today.

any chance of having this fixed so i can test the mediabuild code with 
my dvbsky card?



On 2016-03-03 23:03, Torbjorn Jansson wrote:
> found something, modprobe results in the following dmesg message:
>
> frame_vector: exports duplicate symbol frame_vector_create (owned by
> kernel)
>
> every time i do a modprobe of cx23885
> what does this mean?
>
> On 2016-03-03 22:58, Torbjorn Jansson wrote:
>> i'm having a bit of a problem testing the changed firmware on my t980c
>> card.
>>
>> complied the code from media_tree and i get the usb card to work with
>> those modules but for some reason modprobe of cx23885 results in:
>> # modprobe cx23885
>> modprobe: ERROR: could not insert 'cx23885': Exec format error
>>
>> all the other modules work just fine, i'm not sure what i'm doing wrong.
>>
>>
>> On 2016-03-03 19:22, Torbjorn Jansson wrote:
>>> i was about to ask how to easiest see what firmware i was running
>>> without rebooting when i realized i already have it in this mail
>>> thread ;)
>>>
>>> all of the firmware i'm running is the ones that came from dvbsky
>>> directly in this file:
>>> http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz
>>>
>>> i suspect i should go thru all of the firmware files i use since if one
>>> is bad the other ones is probably also bad.
>>>
>>> i assume i also should also check: dvb-tuner-si2158-a20-01.fw
>>> what version is a good one? i have found 2 different files:
>>>
>>> the one i current usefrom dvbsky, also same as OpenELEC fw repo uses
>>> with md5sum:
>>> 8e98d25d6219e235b519a3c47dbfa856  dvb-tuner-si2158-a20-01.fw
>>>
>>> and then i found another one at
>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/Si2158-A20/
>>> 0cba7ce61c1411cbe7f22c0746e24e33  dvb-tuner-si2158-a20-01.fw
>>> this file is a bit smaller.
>>>
>>> i will retest with the new firmware you suggested and see what happens.
>>>
>>>
>>> On 2016-03-03 12:02, Olli Salonen wrote:
>>>> Hi Jurgen, Torbjörn,
>>>>
>>>> I've noticed that there is currently a small confusion about the
>>>> firmware versions for the Si2168-A20 demodulator. This is used in the
>>>> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
>>>> T980C (TechnoTrend CT2-4500 CI).
>>>>
>>>> The version 2.0.5 does not support PLP handling and seems to work very
>>>> badly with the Linux driver - at least for me. Version 2.0.35 on the
>>>> other hand seems to find all DVB-T/T2 channels for me just fine with
>>>> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
>>>> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>>>>
>>>> Versions used:
>>>> dvbv5-scan version 1.7.0
>>>> w_scan version 20150111 (compiled for DVB API 5.10)
>>>>
>>>> So if you are running these Si2168-A20 based devices, make sure you've
>>>> got the firmware 2.0.35 that can be downloaded for example here:
>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/
>>>>
>>>>
>>>>
>>>>
>>>> Cheers,
>>>> -olli
>>>>
>>>> On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>>>>>> i have tested your patch with my dvbsky dvb-t2 card.
>>>>>> testing was done by compiling a custom kernel with your patch
>>>>>> included.
>>>>>> test was done against fedora 22 4.3.4-200 kernel
>>>>>>
>>>>>> with the patch included the CI slot is found.
>>>>>> so there is some progress for sure
>>>>>> -----
>>>>>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>>>>>> firmware
>>>>>> (16382 bytes)
>>>>>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>>>>>> [   10.207968] cx23885[0]: cx23885 based dvb card
>>>>>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>>>>>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>>>>>> attached
>>>>>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>>>>>> successfully attached
>>>>>> [   10.244560] DVB: registering new adapter (cx23885[0])
>>>>>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>>>>>> frontend
>>>>>> 0 (Silicon Labs Si2168)...
>>>>>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>>>>>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>>>>>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>>>>>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>>>>>> latency: 0, mmio: 0xf6e00000
>>>>>>
>>>>>> later when tuning:
>>>>>>
>>>>>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>>>>>> [   67.802203] si2168 10-0064: downloading firmware from file
>>>>>> 'dvb-demod-si2168-a20-01.fw'
>>>>>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>>>>>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>>>>>> [   69.961057] si2157 12-0060: downloading firmware from file
>>>>>> 'dvb-tuner-si2158-a20-01.fw'
>>>>>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>>>>>> ----
>>>>>>
>>>>>> but using dvbv5-scan to scan it doesn't find any channel.
>>>>>> all i get is this:
>>>>>> ----
>>>>>> Scanning frequency #1 770000000
>>>>>>          (0x00) Signal= -114.00dBm
>>>>>> Scanning frequency #2 754000000
>>>>>>          (0x00) Signal= -27.00dBm C/N= 32.50dB
>>>>>> Scanning frequency #3 546000000
>>>>>>          (0x00) Signal= -25.00dBm C/N= 33.75dB
>>>>>> Scanning frequency #4 650000000
>>>>>>          (0x00) Signal= -18.00dBm C/N= 36.00dB
>>>>>> Scanning frequency #5 522000000
>>>>>>          (0x00) Signal= -28.00dBm C/N= 33.00dB
>>>>>> ----
>>>>>>
>>>>>> so something else is broken too.
>>>>>>
>>>>> I have been using the patches for a few days. So far everything works
>>>>> great (using MythTV). Scanning with dvbv5_scan does indeed not work
>>>>> (never did for me). w_scan works though.
>>>>>
>>>>> Can these patches please be included in the stable kernels ?
>>>>>
>>>>> Jurgen
>>>>>
>>>>>
>>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Found the issue and submitted a patch.
>>>>>>>
>>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>>> was moved to its own function.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> -olli
>>>>>>>
>>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb
>>>>>>>> based device
>>>>>>>> instead.
>>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>>> submitted
>>>>>>>> earlier.
>>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>>> dvb-t and t2
>>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>>> mythtv.
>>>>>>>>
>>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>>> kernels or
>>>>>>>> modules.
>>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>>> appreciated.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>>
>>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>>
>>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>>
>>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>>>>>>>>> commit
>>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>>
>>>>>>>>>        [media] cx23885: move CI/MAC registration to a separate
>>>>>>>>> function
>>>>>>>>>
>>>>>>>>>        As reported by smatch:
>>>>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>>> dvb_register()
>>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>>
>>>>>>>>>        This is indeed a too complex function, with lots of stuff
>>>>>>>>> inside.
>>>>>>>>>        Breaking this into two functions makes it a little bit
>>>>>>>>> less hairy.
>>>>>>>>>
>>>>>>>>>        Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>>>>>>>>> .com>
>>>>>>>>>
>>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>>> look at
>>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> -olli
>>>>>>>>>
>>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Olli,
>>>>>>>>>>
>>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>>
>>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>>
>>>>>>>>>>> I have a clone of your card and was just starting to look
>>>>>>>>>>> at this
>>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>>>>>>>>>>> have any
>>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>>
>>>>>>>>>> No, unfortunately not. I have spend a few hours adding
>>>>>>>>>> printk's but it
>>>>>>>>>> did not get me any closer what causes the issue. This really
>>>>>>>>>> needs
>>>>>>>>>> investigation from someone who is more familiar with linux
>>>>>>>>>> media.
>>>>>>>>>>
>>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>>> dvbsky on a
>>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>>
>>>>>>>>>> Greetings,
>>>>>>>>>> Jurgen
>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> -olli
>>>>>>>>>>>
>>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>>>>>>>>>>> all.nl>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> 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?
>>>>>>>>>>>>>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Torbjorn Jansson]

i think i need to revive this very old thread.
i ran into some problems with my new dvb box after the old one gave up 
permanently (probably due to worn out flash) and then learned a few things.

apparently i need to use PLP=1 for the dvb-t2 channels to get a lock.
if i use my dvb box and uses plp=0 as is the default it never locks on 
to the t2 frequencies and never finds any of the dvb-t2 channels (= all 
the hd channels)

so as was discussed earlier i think my issue with the new version of 
ct2-4650 is related to plp.

when this thread was going last year i ran into issues i could not solve 
and then gave up since it wasn't too important to have the ct2-4650 working.
but maybe it is time to give this another try.

also last year i had issues loading the media build modules due to an 
extra kernel module that was built that i just had to delete (didn't 
know it back then)



so, two main questions:
how is plp supposed to work? is the drivers supposed to auto detect this?
if so, how do i convince the drivers to use plp=1 when i use for example 
w_scan ?

and secondly, if drivers is supposed to auto detect plp, it clearly 
doesn't happen for me.
since this works on windows, is it possible that the windows driver is 
using a newer firmware for the si6168-b40 than 4.0.25?
(latest one i found on: 
http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-B40/)
any advice on how to check or capture what the windows driver uses?

thanks.


On 2016-06-06 13:30, Torbjorn Jansson wrote:
> FYI i still get "Exec format error" while modprobing cx23885 with 
> media_build from today.
> 
> any chance of having this fixed so i can test the mediabuild code with 
> my dvbsky card?
> 
> 
> 
> On 2016-03-03 23:03, Torbjorn Jansson wrote:
>> found something, modprobe results in the following dmesg message:
>>
>> frame_vector: exports duplicate symbol frame_vector_create (owned by
>> kernel)
>>
>> every time i do a modprobe of cx23885
>> what does this mean?
>>
>> On 2016-03-03 22:58, Torbjorn Jansson wrote:
>>> i'm having a bit of a problem testing the changed firmware on my t980c
>>> card.
>>>
>>> complied the code from media_tree and i get the usb card to work with
>>> those modules but for some reason modprobe of cx23885 results in:
>>> # modprobe cx23885
>>> modprobe: ERROR: could not insert 'cx23885': Exec format error
>>>
>>> all the other modules work just fine, i'm not sure what i'm doing wrong.
>>>
>>>
>>> On 2016-03-03 19:22, Torbjorn Jansson wrote:
>>>> i was about to ask how to easiest see what firmware i was running
>>>> without rebooting when i realized i already have it in this mail
>>>> thread ;)
>>>>
>>>> all of the firmware i'm running is the ones that came from dvbsky
>>>> directly in this file:
>>>> http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz
>>>>
>>>> i suspect i should go thru all of the firmware files i use since if one
>>>> is bad the other ones is probably also bad.
>>>>
>>>> i assume i also should also check: dvb-tuner-si2158-a20-01.fw
>>>> what version is a good one? i have found 2 different files:
>>>>
>>>> the one i current usefrom dvbsky, also same as OpenELEC fw repo uses
>>>> with md5sum:
>>>> 8e98d25d6219e235b519a3c47dbfa856  dvb-tuner-si2158-a20-01.fw
>>>>
>>>> and then i found another one at
>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/Si2158-A20/
>>>> 0cba7ce61c1411cbe7f22c0746e24e33  dvb-tuner-si2158-a20-01.fw
>>>> this file is a bit smaller.
>>>>
>>>> i will retest with the new firmware you suggested and see what happens.
>>>>
>>>>
>>>> On 2016-03-03 12:02, Olli Salonen wrote:
>>>>> Hi Jurgen, Torbjörn,
>>>>>
>>>>> I've noticed that there is currently a small confusion about the
>>>>> firmware versions for the Si2168-A20 demodulator. This is used in the
>>>>> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
>>>>> T980C (TechnoTrend CT2-4500 CI).
>>>>>
>>>>> The version 2.0.5 does not support PLP handling and seems to work very
>>>>> badly with the Linux driver - at least for me. Version 2.0.35 on the
>>>>> other hand seems to find all DVB-T/T2 channels for me just fine with
>>>>> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
>>>>> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>>>>>
>>>>> Versions used:
>>>>> dvbv5-scan version 1.7.0
>>>>> w_scan version 20150111 (compiled for DVB API 5.10)
>>>>>
>>>>> So if you are running these Si2168-A20 based devices, make sure you've
>>>>> got the firmware 2.0.35 that can be downloaded for example here:
>>>>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713b33915f674bfb2c209beaea5/ 
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Cheers,
>>>>> -olli
>>>>>
>>>>> On 20 February 2016 at 19:20, Jurgen Kramer <gtmkramer@xs4all.nl>
>>>>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> On Sat, 2016-02-20 at 16:57 +0100, Torbjorn Jansson wrote:
>>>>>>> i have tested your patch with my dvbsky dvb-t2 card.
>>>>>>> testing was done by compiling a custom kernel with your patch
>>>>>>> included.
>>>>>>> test was done against fedora 22 4.3.4-200 kernel
>>>>>>>
>>>>>>> with the patch included the CI slot is found.
>>>>>>> so there is some progress for sure
>>>>>>> -----
>>>>>>> [   10.189408] cx25840 11-0044: loaded v4l-cx23885-avcore-01.fw
>>>>>>> firmware
>>>>>>> (16382 bytes)
>>>>>>> [   10.206683] cx23885_dvb_register() allocating 1 frontend(s)
>>>>>>> [   10.207968] cx23885[0]: cx23885 based dvb card
>>>>>>> [   10.224306] i2c i2c-10: Added multiplexed i2c bus 12
>>>>>>> [   10.225633] si2168 10-0064: Silicon Labs Si2168 successfully
>>>>>>> attached
>>>>>>> [   10.243310] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158
>>>>>>> successfully attached
>>>>>>> [   10.244560] DVB: registering new adapter (cx23885[0])
>>>>>>> [   10.245807] cx23885 0000:07:00.0: DVB: registering adapter 0
>>>>>>> frontend
>>>>>>> 0 (Silicon Labs Si2168)...
>>>>>>> [   10.417402] sp2 9-0040: CIMaX SP2 successfully attached
>>>>>>> [   10.447120] DVBSky T980C MAC address: 00:17:42:54:09:85
>>>>>>> [   10.448844] cx23885_dev_checkrevision() Hardware revision = 0xa5
>>>>>>> [   10.450550] cx23885[0]/0: found at 0000:07:00.0, rev: 4, irq: 19,
>>>>>>> latency: 0, mmio: 0xf6e00000
>>>>>>>
>>>>>>> later when tuning:
>>>>>>>
>>>>>>> [   67.728109] si2168 10-0064: found a 'Silicon Labs Si2168-A20'
>>>>>>> [   67.802203] si2168 10-0064: downloading firmware from file
>>>>>>> 'dvb-demod-si2168-a20-01.fw'
>>>>>>> [   68.968336] si2168 10-0064: firmware version: 2.0.5
>>>>>>> [   68.977071] si2157 12-0060: found a 'Silicon Labs Si2158-A20'
>>>>>>> [   69.961057] si2157 12-0060: downloading firmware from file
>>>>>>> 'dvb-tuner-si2158-a20-01.fw'
>>>>>>> [   70.969094] si2157 12-0060: firmware version: 2.1.9
>>>>>>> ----
>>>>>>>
>>>>>>> but using dvbv5-scan to scan it doesn't find any channel.
>>>>>>> all i get is this:
>>>>>>> ----
>>>>>>> Scanning frequency #1 770000000
>>>>>>>          (0x00) Signal= -114.00dBm
>>>>>>> Scanning frequency #2 754000000
>>>>>>>          (0x00) Signal= -27.00dBm C/N= 32.50dB
>>>>>>> Scanning frequency #3 546000000
>>>>>>>          (0x00) Signal= -25.00dBm C/N= 33.75dB
>>>>>>> Scanning frequency #4 650000000
>>>>>>>          (0x00) Signal= -18.00dBm C/N= 36.00dB
>>>>>>> Scanning frequency #5 522000000
>>>>>>>          (0x00) Signal= -28.00dBm C/N= 33.00dB
>>>>>>> ----
>>>>>>>
>>>>>>> so something else is broken too.
>>>>>>>
>>>>>> I have been using the patches for a few days. So far everything works
>>>>>> great (using MythTV). Scanning with dvbv5_scan does indeed not work
>>>>>> (never did for me). w_scan works though.
>>>>>>
>>>>>> Can these patches please be included in the stable kernels ?
>>>>>>
>>>>>> Jurgen
>>>>>>
>>>>>>
>>>>>>> On 2016-02-16 21:20, Olli Salonen wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Found the issue and submitted a patch.
>>>>>>>>
>>>>>>>> The I2C buses for T980C/T2-4500CI were crossed when CI registration
>>>>>>>> was moved to its own function.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> -olli
>>>>>>>>
>>>>>>>> On 31 January 2016 at 10:55, Torbjorn Jansson
>>>>>>>> <torbjorn.jansson@mbox200.swipnet.se> wrote:
>>>>>>>>> this ci problem is the reason i decided to buy the CT2-4650 usb
>>>>>>>>> based device
>>>>>>>>> instead.
>>>>>>>>> but the 4650 was a slightly newer revision needing a patch i
>>>>>>>>> submitted
>>>>>>>>> earlier.
>>>>>>>>> and also this 4650 device does not have auto switching between
>>>>>>>>> dvb-t and t2
>>>>>>>>> like the dvbsky card have, so i also need an updated version of
>>>>>>>>> mythtv.
>>>>>>>>>
>>>>>>>>> my long term wish is to not have to patch things or build custom
>>>>>>>>> kernels or
>>>>>>>>> modules.
>>>>>>>>> so anything done to improve the dvbsky card or the 4650 is much
>>>>>>>>> appreciated.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 2016-01-28 20:42, Olli Salonen wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Jürgen & Mauro,
>>>>>>>>>>
>>>>>>>>>> I did bisect this and it seems this rather big patch broke it:
>>>>>>>>>>
>>>>>>>>>> 2b0aac3011bc7a9db27791bed4978554263ef079 is the first bad
>>>>>>>>>> commit
>>>>>>>>>> commit 2b0aac3011bc7a9db27791bed4978554263ef079
>>>>>>>>>> Author: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>>>>>>>> Date:   Tue Dec 23 13:48:07 2014 -0200
>>>>>>>>>>
>>>>>>>>>>        [media] cx23885: move CI/MAC registration to a separate
>>>>>>>>>> function
>>>>>>>>>>
>>>>>>>>>>        As reported by smatch:
>>>>>>>>>>            drivers/media/pci/cx23885/cx23885-dvb.c:2080
>>>>>>>>>> dvb_register()
>>>>>>>>>> Function too hairy.  Giving up.
>>>>>>>>>>
>>>>>>>>>>        This is indeed a too complex function, with lots of stuff
>>>>>>>>>> inside.
>>>>>>>>>>        Breaking this into two functions makes it a little bit
>>>>>>>>>> less hairy.
>>>>>>>>>>
>>>>>>>>>>        Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung
>>>>>>>>>> .com>
>>>>>>>>>>
>>>>>>>>>> It's getting a bit late, so I'll call it a day now and have a
>>>>>>>>>> look at
>>>>>>>>>> the patch to see what goes wrong there.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> -olli
>>>>>>>>>>
>>>>>>>>>> On 28 January 2016 at 20:57, Jurgen Kramer <gtmkramer@xs4all.nl
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Olli,
>>>>>>>>>>>
>>>>>>>>>>> On Thu, 2016-01-28 at 19:26 +0200, Olli Salonen wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Jürgen,
>>>>>>>>>>>>
>>>>>>>>>>>> Did you get anywhere with this?
>>>>>>>>>>>>
>>>>>>>>>>>> I have a clone of your card and was just starting to look
>>>>>>>>>>>> at this
>>>>>>>>>>>> issue. Kernel 3.19 seems to work ok, but 4.3 not. Did you
>>>>>>>>>>>> have any
>>>>>>>>>>>> time to try to pinpoint this more?
>>>>>>>>>>>
>>>>>>>>>>> No, unfortunately not. I have spend a few hours adding
>>>>>>>>>>> printk's but it
>>>>>>>>>>> did not get me any closer what causes the issue. This really
>>>>>>>>>>> needs
>>>>>>>>>>> investigation from someone who is more familiar with linux
>>>>>>>>>>> media.
>>>>>>>>>>>
>>>>>>>>>>> Last thing I tried was the latest (semi open) drivers from
>>>>>>>>>>> dvbsky on a
>>>>>>>>>>> 4.3 kernel. Here the CI and CAM registered successfully.
>>>>>>>>>>>
>>>>>>>>>>> Greetings,
>>>>>>>>>>> Jurgen
>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> -olli
>>>>>>>>>>>>
>>>>>>>>>>>> On 12 September 2015 at 10:02, Jurgen Kramer <gtmkramer@xs4
>>>>>>>>>>>> all.nl>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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?
>>>>>>>>>>>>>>
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

Hi Olli,

On Thu, 2016-03-03 at 13:02 +0200, Olli Salonen wrote:
> Hi Jurgen, Torbjörn,
> 
> I've noticed that there is currently a small confusion about the
> firmware versions for the Si2168-A20 demodulator. This is used in the
> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
> T980C (TechnoTrend CT2-4500 CI).
> 
> The version 2.0.5 does not support PLP handling and seems to work
> very
> badly with the Linux driver - at least for me. Version 2.0.35 on the
> other hand seems to find all DVB-T/T2 channels for me just fine with
> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
> 
> Versions used:
> dvbv5-scan version 1.7.0
> w_scan version 20150111 (compiled for DVB API 5.10)
> 
> So if you are running these Si2168-A20 based devices, make sure
> you've
> got the firmware 2.0.35 that can be downloaded for example here:
> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713
> b33915f674bfb2c209beaea5/

It seems my TC980Cs have Si2168-A30's on board

[  118.526665] si2168 8-0064: found a 'Silicon Labs Si2168-A30'
[  118.640642] si2168 8-0064: downloading firmware from file 'dvb-
demod-si2168-a30-01.fw'
[  121.762983] si2168 8-0064: firmware version: 3.0.16

dvbv5_scan does not work me.
sha1sum for this firmware is:
59a0b90703d65229fb2589b52834ca68d1e96ad9  dvb-demod-si2168-a30-01.fw

Jurgen

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Olli Salonen]

Hi Jurgen,

Ah, that's interesting. My T980C (and based on printout from Torbjörn
his as well) have Si2168-A20 chips.

Some things I'd like to understand:
- is there a difference if the CI slot is populated or not?
- is there any difference between the different firmwares?
- does it work with the DVBSky provided driver?
- when you say it doesn't work, is the issue that the demodulator does
not lock on the DVB-T2 muxes?

Two different firmwares for A30 chip:
https://github.com/OpenELEC/dvb-firmware/blob/18b12de1f57b3c70a681983638989f94590b19f1/firmware/dvb-demod-si2168-a30-01.fw?raw=true
https://github.com/OpenELEC/dvb-firmware/raw/dc7cf270e328de144e75a30d970b6e147e8bcb6e/firmware/dvb-demod-si2168-a30-01.fw

I think the second one is newer, but don't have the means to verify right now...

Cheers,
-olli

On 4 March 2016 at 10:15, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
> Hi Olli,
>
> On Thu, 2016-03-03 at 13:02 +0200, Olli Salonen wrote:
>> Hi Jurgen, Torbjörn,
>>
>> I've noticed that there is currently a small confusion about the
>> firmware versions for the Si2168-A20 demodulator. This is used in the
>> older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and DVBSky
>> T980C (TechnoTrend CT2-4500 CI).
>>
>> The version 2.0.5 does not support PLP handling and seems to work
>> very
>> badly with the Linux driver - at least for me. Version 2.0.35 on the
>> other hand seems to find all DVB-T/T2 channels for me just fine with
>> both dvbv5-scan and w_scan (devices used for this test: TechnoTrend
>> CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
>>
>> Versions used:
>> dvbv5-scan version 1.7.0
>> w_scan version 20150111 (compiled for DVB API 5.10)
>>
>> So if you are running these Si2168-A20 based devices, make sure
>> you've
>> got the firmware 2.0.35 that can be downloaded for example here:
>> http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e06713
>> b33915f674bfb2c209beaea5/
>
> It seems my TC980Cs have Si2168-A30's on board
>
> [  118.526665] si2168 8-0064: found a 'Silicon Labs Si2168-A30'
> [  118.640642] si2168 8-0064: downloading firmware from file 'dvb-
> demod-si2168-a30-01.fw'
> [  121.762983] si2168 8-0064: firmware version: 3.0.16
>
> dvbv5_scan does not work me.
> sha1sum for this firmware is:
> 59a0b90703d65229fb2589b52834ca68d1e96ad9  dvb-demod-si2168-a30-01.fw
>
> Jurgen
>

Re: DVBSky T980C CI issues (kernel 4.0.x)

[Jurgen Kramer]

Hi Olli,

On Fri, 2016-03-04 at 10:28 +0200, Olli Salonen wrote:
> Hi Jurgen,
> 
> Ah, that's interesting. My T980C (and based on printout from Torbjörn
> his as well) have Si2168-A20 chips.
> 
> Some things I'd like to understand:
> - is there a difference if the CI slot is populated or not?
Not sure, will test
> - is there any difference between the different firmwares?
I'll check the second newer one.
> - does it work with the DVBSky provided driver?
Will test this as well (dvbv5-scan)
> - when you say it doesn't work, is the issue that the demodulator
> does
> not lock on the DVB-T2 muxes?
I am using DVB-C, I do not have issues with tuning. Only dvbv5-scan
does not work.
> 
> Two different firmwares for A30 chip:
> https://github.com/OpenELEC/dvb-firmware/blob/18b12de1f57b3c70a681983
> 638989f94590b19f1/firmware/dvb-demod-si2168-a30-01.fw?raw=true
> https://github.com/OpenELEC/dvb-firmware/raw/dc7cf270e328de144e75a30d
> 970b6e147e8bcb6e/firmware/dvb-demod-si2168-a30-01.fw
> 
> I think the second one is newer, but don't have the means to verify
> right now...
I am currently using the first one.

What about the si2158?
[  121.771582] si2157 10-0060: found a 'Silicon Labs Si2158-A20'
[  121.794158] si2157 10-0060: downloading firmware from file 'dvb-
tuner-si2158-a20-01.fw'
[  122.594826] si2157 10-0060: firmware version: 2.1.6

Bye,
Jurgen

> 
> Cheers,
> -olli
> 
> On 4 March 2016 at 10:15, Jurgen Kramer <gtmkramer@xs4all.nl> wrote:
> > 
> > Hi Olli,
> > 
> > On Thu, 2016-03-03 at 13:02 +0200, Olli Salonen wrote:
> > > 
> > > Hi Jurgen, Torbjörn,
> > > 
> > > I've noticed that there is currently a small confusion about the
> > > firmware versions for the Si2168-A20 demodulator. This is used in
> > > the
> > > older versions of DVBSky T680C (TechnoTrend CT2-4650 CI) and
> > > DVBSky
> > > T980C (TechnoTrend CT2-4500 CI).
> > > 
> > > The version 2.0.5 does not support PLP handling and seems to work
> > > very
> > > badly with the Linux driver - at least for me. Version 2.0.35 on
> > > the
> > > other hand seems to find all DVB-T/T2 channels for me just fine
> > > with
> > > both dvbv5-scan and w_scan (devices used for this test:
> > > TechnoTrend
> > > CT2-4650 CI and TechnoTrend CT2-4500 CI new version).
> > > 
> > > Versions used:
> > > dvbv5-scan version 1.7.0
> > > w_scan version 20150111 (compiled for DVB API 5.10)
> > > 
> > > So if you are running these Si2168-A20 based devices, make sure
> > > you've
> > > got the firmware 2.0.35 that can be downloaded for example here:
> > > http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-A20/32e0
> > > 6713
> > > b33915f674bfb2c209beaea5/
> > It seems my TC980Cs have Si2168-A30's on board
> > 
> > [  118.526665] si2168 8-0064: found a 'Silicon Labs Si2168-A30'
> > [  118.640642] si2168 8-0064: downloading firmware from file 'dvb-
> > demod-si2168-a30-01.fw'
> > [  121.762983] si2168 8-0064: firmware version: 3.0.16
> > 
> > dvbv5_scan does not work me.
> > sha1sum for this firmware is:
> > 59a0b90703d65229fb2589b52834ca68d1e96ad9  dvb-demod-si2168-a30-
> > 01.fw
> > 
> > Jurgen
> >