Vu+
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Sundtek + RTL2838U USB DVB-T Tuners not working together

Discussion in 'DVB Devices' started by HWTest, Oct 26, 2014.

  1. HWTest

    HWTest Vu+ Newbie

    Messages:
    11
    I have a VU+ Duo, Black Hole 2.1.1 and I was trying to make two additional USB DVB-T tuners to work.
    I had to install Sundtek drivers using the sundtek_netinst.sh script.
    If only one tuner is plugged, it is recognized as tuner C and is working.
    If both are plugged, the Sundtek is recognized as tuner C and is working but not reliably. No Realtek, no tuner D.
    I have tried to plug the tuners into a powered USB hub, not powered USB hub and different USB ports directly on the Duo - it didn't help.
    If there is any additional information needed, I'll gladly provide it
    Is it an unsupported feature, what I'm trying to do or should it work ?

    PS: A strange thing happens, when I connect a powered USB hub - the Duo isn't booting, I can hear the HDD spinning up, but the red LED stays on and nothing appears on the display.
     

    Attached Files:

  2. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,925
    Sundtek drivers takes no care about our USB DVB implementation when you try to use a Sundtek and another USB DVB device.
    The only (acceptable) solution is to make compatible the Sundtek device into standard LInux USB DVB drivers.
     
  3. HWTest

    HWTest Vu+ Newbie

    Messages:
    11
    And how do I do that?
     
  4. sundtek

    sundtek Vip

    Messages:
    32
    we aren't going to use this dinosaur technology as it's the most inflexible thing on earth.
    Our driver works as it is on many different architectures and systems without any additional modification, the dinosaur technology / "standard" Linux DVB drivers cannot do that at all and everytime something has to be updated things would have to be recompiled.. that's just insane.
    Aside of that "standard" regular drivers cannot be used on standard Android systems as well, while our driver can be used on it without rooting the system.

    There's also a network mode included in the driver, this is just another thing that cannot be done with regular drivers. Install the driver on one side (ARM, MIPS, PPC, SH4, X86/32-64bit) and stream it to settopboxes, linux, windows or MacOSX.

    Too many disadvantages. Our driver is fully configurable for every single possible option, however on the other side we do not support other devices (that said we do not lock them out either, if someone wants to have such setup he has to dig into our forum and find the solution by himself, we're busy enough with our own devices).

    The driver package has been developed for several years, also devices which are EOL on our side are still carried on with this package and automatically updated to the new interfaces.
    The "standard" driver technology is more than 14 years old, because back then the modern interfaces did not exist, now users of other devices have to live with that old cruft. Our one is around 4 years old and using the new interfaces which exist in Linux.

    We release a new device - we are able to support it everywhere from day one on.
     
    Last edited: Oct 27, 2014

Share This Page