7.95.1 BETA - 8.1.1: [Technotrend TT-connect CT-3650] dvb no signal after upgrade

tcamargo · January 23, 2017 at 6:53 PM

Hi,

Upgraded from 7.90.010 to 7.95.1 yesterday and my dvb device (Technotrend TT-connect CT-3650) stopped working. No signal on all frequencies. A downgrade to 7.90.010 solved the problem.

I assume we have an issue with the linux kernel (4.9.0 vs 4.9.3). dmesg output is a bit different and there are changes in the dvb subsystem. Although, I cannot pinpoint the problem.

Full log in gC8BpEfG

Thanks!
Tiago

tcamargo · February 8, 2017 at 10:59 AM

Hi,

Problem persists in 7.95.2.

Code

# w_scan -I initial -f c 
w_scan -I initial -f c 
w_scan version 20141122 (compiled for DVB API 5.10)
parsing initial tuning data "initial"..
	transponder QAM_256  f = 322000 kHz S5217C0  (0:0:0)
scan type CABLE, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
	/dev/dvb/adapter0/frontend0 -> CABLE "Philips TDA10023 DVB-C": good :-)
	/dev/dvb/adapter0/frontend1 -> "NXP TDA10048HN DVB-T" doesnt support CABLE -> SEARCH NEXT ONE.
Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Philips TDA10023 DVB-C' supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO
FREQ (47.00MHz ... 862.00MHz)
SRATE (0.458MSym/s ... 7.333MSym/s)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
updating transponder list..
QAM_256  f = 322000 kHz S5217C0  (0:0:0): 


tune to: QAM_AUTO f = 322000 kHz S5217C999  (0:0:0) (time: 00:08.073)  (no signal)
----------no signal----------
tune to: QAM_AUTO f = 322000 kHz S5217C999  (0:0:0) (time: 00:12.593)  (no signal)
----------no signal----------


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

Display More

Code

Bus 001 Device 003: ID 0b48:300d TechnoTrend AG TT-connect CT-3650 CI

**smp** · February 8, 2017 at 2:03 PM

Maybe a media_build issue? 7.90.010 didn't include it.

tcamargo · February 8, 2017 at 2:18 PM

dmesg is different..

Code

LibreELEC (Krypton) v7.95.1 BETA
# dmesg | grep dvb
[    4.717961] dvb-usb: found a 'Technotrend TT-connect CT-3650' in warm state.
[    4.719777] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    4.719781] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    4.721359] dvbdev: DVB: registering new adapter (Technotrend TT-connect CT-3650)
[    4.725424] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    4.785784] dvbdev: dvb_create_media_entity: media entity 'dvb-ca-en50221' registered.
[    4.807485] dvbdev: dvb_create_media_entity: media entity 'Philips TDA10023 DVB-C' registered.
[    4.875453] dvbdev: dvb_create_media_entity: media entity 'NXP TDA10048HN DVB-T' registered.
[    4.925346] dvb-usb: schedule remote query interval to 150 msecs.
[    4.925786] dvb-usb: Technotrend TT-connect CT-3650 successfully initialized and connected.
[    4.925834] usbcore: registered new interface driver dvb_usb_ttusb2




LibreELEC (Krypton) v7.90.010 ALPHA
# dmesg | grep dvb
[    5.286965] dvb-usb: found a 'Technotrend TT-connect CT-3650' in warm state.
[    5.303193] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    5.303197] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    5.712742] dvb-usb: schedule remote query interval to 150 msecs.
[    5.716549] dvb-usb: Technotrend TT-connect CT-3650 successfully initialized and connected.
[    5.716619] usbcore: registered new interface driver dvb_usb_ttusb2

Display More

tcamargo · February 9, 2017 at 9:35 AM

Any way to disable media_build modules in runtime? I tried to rmmod dvb* and then insmod the vanilla versions by hand, but kernel complained about unknown symbols. Probably missed some dependency.

Thanks!

**smp** · February 9, 2017 at 2:33 PM

Try my custom build that I posted here. I compiled it without media_build.

tcamargo · February 9, 2017 at 2:38 PM

Thanks, but I am not using a RPi.

**smp** · February 9, 2017 at 2:46 PM

Oops, I forgot that there are other platforms...

Anyway, it's easy to compile it without media_build. Just edit the project options file.

**CvH** · February 9, 2017 at 6:49 PM Official Post

ups didn't saw this thread, could you test both images ?
Index of /Test/tt3650/

kernel 4.10 drivers and vanilla 4.9 drivers, maybe it is already broken at 4.9 like the TT-S2-3600

tcamargo · February 9, 2017 at 9:18 PM

Thanks, CvH!

LibreELEC-Generic.x86_64-7.95.3-mb_without.img.gz - Good!
LibreELEC-Generic.x86_64-7.95.3-mb_latest.img.gz - Bad!

Code

LibreELEC-Generic.x86_64-7.95.3-mb_without.img.gz
# uname -a
Linux liessa 4.9.8 #1 SMP Thu Feb 9 18:28:08 CET 2017 x86_64 GNU/Linux
# w_scan -I initial -f c 
w_scan -I initial -f c 
w_scan version 20141122 (compiled for DVB API 5.10)
parsing initial tuning data "initial"..
transponder QAM_256  f = 322000 kHz S5217C0  (0:0:0)
scan type CABLE, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> CABLE "Philips TDA10023 DVB-C": good :-)
/dev/dvb/adapter0/frontend1 -> "NXP TDA10048HN DVB-T" doesnt support CABLE -> SEARCH NEXT ONE.
Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Philips TDA10023 DVB-C' supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO
FREQ (47.00MHz ... 862.00MHz)
SRATE (0.458MSym/s ... 7.333MSym/s)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
updating transponder list..
QAM_256  f = 322000 kHz S5217C0  (0:0:0): signal ok
        QAM_256  f = 322000 kHz S5217C0  (0:0:0) : updating transport_stream_id: -> (0:0:9)
        QAM_256  f = 322000 kHz S5217C0  (0:0:9) : updating network_id -> (0:3:9)
        new transponder: (QAM_256  f = 303000 kHz S5217C34  (3:3:1)) 0x4044
        new transponder: (QAM_256  f = 405000 kHz S5217C34  (3:3:2)) 0x4044
        new transponder: (QAM_256  f = 363000 kHz S5217C34  (3:3:3)) 0x4044

Display More

Code

LibreELEC-Generic.x86_64-7.95.3-mb_latest.img.gz
# uname -a
Linux liessa 4.9.8 #1 SMP Thu Feb 9 18:28:08 CET 2017 x86_64 GNU/Linux
# w_scan -I initial -f c 
w_scan -I initial -f c 
w_scan version 20141122 (compiled for DVB API 5.10)
parsing initial tuning data "initial"..
transponder QAM_256  f = 322000 kHz S5217C0  (0:0:0)
scan type CABLE, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> CABLE "Philips TDA10023 DVB-C": good :-)
/dev/dvb/adapter0/frontend1 -> "NXP TDA10048HN DVB-T" doesnt support CABLE -> SEARCH NEXT ONE.
Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Philips TDA10023 DVB-C' supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO
FREQ (47.00MHz ... 862.00MHz)
SRATE (0.458MSym/s ... 7.333MSym/s)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
updating transponder list..
QAM_256  f = 322000 kHz S5217C0  (0:0:0): 


tune to: QAM_AUTO f = 322000 kHz S5217C999  (0:0:0) (time: 00:08.090)  (no signal)
----------no signal----------
tune to: QAM_AUTO f = 322000 kHz S5217C999  (0:0:0) (time: 00:12.626)  (no signal)
----------no signal----------


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

Display More

**CvH** · February 9, 2017 at 10:20 PM Official Post

could you try Index of /Test/tt3650/
latest10 (maybe fixed)

tcamargo · February 9, 2017 at 10:47 PM

LibreELEC-Generic.x86_64-7.95.3-mb_latest10.img.gz - Bad!

**CvH** · February 12, 2017 at 2:44 PM Official Post

could you provide an full dmesg | paste (of the working version) ?

I have not really an idea what commit is the cause of this issue.

tcamargo · February 12, 2017 at 10:58 PM

dmesg from LibreELEC-Generic.x86_64-7.95.3-mb_without.img.gz
ZhXT

**CvH** · February 13, 2017 at 11:00 AM Official Post

Index of /Test/tt3650/
3 new images, pls test (I really just "test" some ideas as I have still no idea what creates that problem)
work/not work is enough

tcamargo · February 16, 2017 at 4:28 PM

No luck...

LibreELEC-Generic.x86_64-7.95.3-allyes-patch.img.gz - don't work
LibreELEC-Generic.x86_64-7.95.3-allyes.img.gz - don't work
LibreELEC-Generic.x86_64-7.95.3-latest-10.2.img.gz - don't work

Where can I find the source for LibreELEC-Generic.x86_64-7.95.3-mb_without.img.gz?

Thanks!

**CvH** · February 16, 2017 at 9:42 PM Official Post

mb_without uses normal LE8 without media_build -> kernel 4.9.0 dvb drivers
everything else is using media_build in different version, per default we deliver ~kernel 4.10rc1 dvb drivers

so it is broken somewhere between 4.9 and 4.10rc1 no idea where to look for as i don't find a change at all that change anything for this card

tcamargo · February 18, 2017 at 7:28 PM

Thanks! I will setup a build box next week and try to git bisect the problem.