Does this dvb s2 tuner work?

    Quote from JoeAverage

    there is an M88DS3103(-C) also in the pipe:

    Satellite STB Solutions | Montage

    @Softlander

    did you check this in the opened device, too ?

    No I did not open my tuner yet. If we can find a solution without openning it, that will be nice. If it is a must, then I have no other choice I will open the box.

    Anyway I am out of the 14 days period for returning the device.

    But the information I have provided is from DVBShop. I think it should be true.

    this is with a distro kernel-4.15.8-300.fc27.x86_64 (Fedora 27) on another box Intel 6700, Board: MSI B250 PC Mate

    there is this media-m88ds3103 patch in:

    kernel/git/stable/stable-queue.git - Linux kernel stable patch queue

    ...

    [ 116.839342] usb 1-3: new high-speed USB device number 5 using xhci_hcd

    [ 116.966078] usb 1-3: New USB device found, idVendor=0ccd, idProduct=0105

    [ 116.966084] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

    [ 116.966088] usb 1-3: Product: TERRATEC USB Tuner

    [ 116.966091] usb 1-3: Manufacturer: Tevii

    [ 116.966095] usb 1-3: SerialNumber: 000000031

    [ 117.006978] dw2102: su3000_identify_state

    [ 117.006978] dvb-usb: found a 'Terratec Cinergy S2 USB BOX' in warm state.

    [ 117.006981] dw2102: su3000_power_ctrl: 1, initialized 0

    [ 117.007032] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

    [ 117.007073] dvbdev: DVB: registering new adapter (Terratec Cinergy S2 USB BOX)

    [ 117.011071] dvb-usb: MAC address: bc:ea:2b:46:13:a5

    [ 117.338804] m88ds3103 5-0068: Unknown device. Chip_id=52

    [ 117.338849] dvb-usb: no frontend was attached by 'Terratec Cinergy S2 USB BOX'

    [ 117.367356] Registered IR keymap rc-tt-1500

    [ 117.367422] rc rc0: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0

    [ 117.367509] input: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0/input18

    [ 117.367834] dvb-usb: schedule remote query interval to 250 msecs.

    [ 117.367840] dw2102: su3000_power_ctrl: 0, initialized 1

    [ 117.367843] dvb-usb: Terratec Cinergy S2 USB BOX successfully initialized and connected.

    [ 117.367925] usbcore: registered new interface driver dw2102

    [ 117.386830] usbcore: registered new interface driver dvb_usb_dvbsky

    [ 119.649430] dvb-usb: recv bulk message failed: -110

    [ 119.649439] dw2102: i2c transfer failed.

    ...

    Edited once, last by GDPR-7: typO (March 12, 2018 at 5:37 PM).

    and with vanilla 4.16.0-rc5:

    on USB2:

    [ 151.642506] usb 1-3: new high-speed USB device number 5 using xhci_hcd

    [ 151.803006] dw2102: su3000_identify_state

    [ 151.803007] dvb-usb: found a 'Terratec Cinergy S2 USB BOX' in warm state.

    [ 151.803009] dw2102: su3000_power_ctrl: 1, initialized 0

    [ 151.803129] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

    [ 151.803192] dvbdev: DVB: registering new adapter (Terratec Cinergy S2 USB BOX)

    [ 151.807280] dvb-usb: MAC address: bc:ea:2b:46:13:a5

    [ 152.117261] m88ds3103 5-0068: Unknown device. Chip_id=52

    [ 152.117299] dvb-usb: no frontend was attached by 'Terratec Cinergy S2 USB BOX'

    [ 152.117414] Registered IR keymap rc-tt-1500

    [ 152.117536] rc rc0: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0

    [ 152.117710] input: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0/input19

    [ 152.118039] dvb-usb: schedule remote query interval to 250 msecs.

    [ 152.118043] dw2102: su3000_power_ctrl: 0, initialized 1

    [ 152.118045] dvb-usb: Terratec Cinergy S2 USB BOX successfully initialized and connected.

    [ 152.118143] usbcore: registered new interface driver dw2102

    [ 152.120575] usbcore: registered new interface driver dvb_usb_dvbsky

    [ 154.437594] dvb-usb: recv bulk message failed: -110

    [ 154.437605] dw2102: i2c transfer failed.

    [ 166.261822] usb 1-3: USB disconnect, device number 5

    on USB3:

    [ 166.277588] dvb-usb: Terratec Cinergy S2 USB BOX successfully deinitialized and disconnected.

    [ 168.406828] usb 1-1: new high-speed USB device number 6 using xhci_hcd

    [ 168.534421] dw2102: su3000_identify_state

    [ 168.534424] dvb-usb: found a 'Terratec Cinergy S2 USB BOX' in warm state.

    [ 168.534433] dw2102: su3000_power_ctrl: 1, initialized 0

    [ 168.534642] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

    [ 168.534708] dvbdev: DVB: registering new adapter (Terratec Cinergy S2 USB BOX)

    [ 168.538862] dvb-usb: MAC address: bc:ea:2b:46:13:a5

    [ 168.849764] m88ds3103 5-0068: Unknown device. Chip_id=52

    [ 168.849816] dvb-usb: no frontend was attached by 'Terratec Cinergy S2 USB BOX'

    [ 168.849945] Registered IR keymap rc-tt-1500

    [ 168.850002] rc rc0: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-1/rc/rc0

    [ 168.850084] input: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:14.0/usb1/1-1/rc/rc0/input20

    [ 168.850287] dvb-usb: schedule remote query interval to 250 msecs.

    [ 168.850291] dw2102: su3000_power_ctrl: 0, initialized 1

    [ 168.850293] dvb-usb: Terratec Cinergy S2 USB BOX successfully initialized and connected.

    [ 171.141939] dvb-usb: recv bulk message failed: -110

    [ 171.141949] dw2102: i2c transfer failed.


    So, I got 13 days left to test.

    Any hints ?

    Edited once, last by GDPR-7: typo (March 12, 2018 at 5:38 PM).

    Don't know if it can be useful for this topic, but I own a Geniatech Hdstar Dvb-s2 box, which should be a twin of Technotrend (and also of Terratec cinergy dvb-s2).

    Same Tuner Montage 2022 and demod Montage M88DS310

    Noticed that in my config the box is always recognized, but tuner fails (no signal in the latest Milhouse builds). It works perfectly in Libreelec 8.2.3.

    So tried also in Ubuntu and these are the results:

    A) Ubuntu 17.10 with media_build drivers compiled from git://http://linuxtv.org/media_build.git

    No signal

    B) Ubuntu 17.10 with drivers compiled from updatelee / v4l-updatelee — Bitbucket

    works

    C) Libreelec 8.2.3

    works

    D) Libreelec 9.0 Default

    no signal

    E) Libreelec 9.0 Crazycat

    works

    F) Libreelec 9.0 Hauppauge

    no signal

    If it is useful can post dmesg.

    Thank you

    Thanks for help, but I doubt they are twins, maybe they were in the past, before undocumented changes.

    @Softlander's and my devices don't run with LE 8.2.3 !

    Where do you get Libreelec 9.0 Crazycat from ?

    link ?

    Thank you CvH

    from LinuxTV

    Geniatech HdStar (2.0 and 3.0) : Cypress CY7C68013
    Terratec Cinergy: Cypress CY7C68013A

    Dvbsky S960: Cypress CY68013

    Technotrend TT-connect S2-4600: Cypress CY7C68013A (saw on another site)

    Remember to have read somewhere a while ago that they were all quite the same box with different names (in fact bought Geniatech at € 34 because costs less).

    Maybe the final "A" makes difference?

    Sometimes they change components without changing names.

    Anyway, there a problem in the latest Milhouse builds (standard drivers), because the box works perfectly in 8.2.3.

    Bye,

    sdf

    Hey guys!

    I'm just setting up a tvheadend server for my libreelec clients. On the server I use debian 9.4.

    I just bought the Technotrend-connect S2-4600 because they're listed as supported on linuxtv. Seems like I have the same problem, maybe you can take a look at the dmesg | paste:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    I still have a few days to return the tuners to amazon, so I'll be happy to help. Can you guys recommend any working USB DVB-S2 Tuner that is supported by Linux and still in stock on most online retailers?

    Thanks a lot!

    so, I tested LE 8.2.4: same bug as in #57 with LE 8.2.3.

    it's not surprising, cause none, whether milhouse nor release running kernels beginning with 4.15.8 where the patch which prevents "NULL pointer dereference" is in !

    to sum it up (please correct if I'm wrong)

    (newer, since ~ beginning 2018) Technotrend TT-connect S2-4600 and Terratec Cinergy S2 USB BOX do NOT run under LE und other distro's.

    It seems that the internals for this devices are undocumented changed so there is currently (march 2018) no driver support or bugs in the kernel.

    This situation may somewhat, but not sufficient, improve if LE or distro's runs kernels beginning with 4.15.8.

    It has to be mentioned that kernel 4.15.8 - IFAIK- only filters out a kernel crash, but does not fix the underlying problem (bug fix, improved driver support)

    I suggest to make this statement somehow sticky in LE Forum, so everybody can easily (without searching/reading through long threads) read this, before buying a useless device.


    My intention is to lower or to prevent user pain, that's all.

    My intentions is not to blame or to harm developers or supporters of LE/distro's !!!

    P.S.

    maybe I find a way to publicize my view/findings at dvb wiki...

    Edited once, last by GDPR-7 (March 14, 2018 at 7:57 PM).

    Allright, so after looking at the logs with CvH this evening a bit, the following is clear.

    The new TT S2-4600 contains an updated version of the M88DS3103 demodulator chip, the M88DS3103B. The USB bridge is the same. The current m88ds3103 driver in the Linux media_tree only supports M88DS3103 (chip ID 0x70) and M88RS6000 (chip ID 0x74). It does not support M88DS3103B (chip ID 0x75). Now, if the M88DS3103B and M88DS3103 are very similar with each other, as often is the case, then it will be quite easy to modify the driver to support also the B version. It goes without saying that if there are bigger differences between them it'll be more difficult.

    Now what CvH did was a quick and dirty hack: make the m88ds3103 driver think that the chip ID of the standard M88DS3103 is 0x75 instead of 0x70. This means that when you plug in a new TT S2-4600, the driver will recognize the chip and continue initialization. However, this probably also means that the driver will try to load the M88DS3103 firmware into the M88DS3103B which will likely fail. In any case, trying out the build CvH pointed out could give us a bit more information.

    If we could extract the firmware from the new TT S2-4600 Windows drivers (it's part of the .sys or .dll files) and replace the old M88DS3103 firmware with the new, we could even see if the firmware loading is successful. However, extracting the firmware would probably need some USB capture (I do that using USBlyzer software usually) of a Windows system at the time of device plug in. And some analysis of the capture of course...