NextPVR Forums

I'm trying to replace my decade-old MythTV setup on Ubuntu with NextPVR.

My 2 USB-DVB-C-Tuners (CableStar Combo HD CI) have been working flawlessly all the time, but are obviously not recognized by NextPVR.



Prolog:

- The old MythTV-Service was shot down, to not block any DVB devices.

- NextPVR was installed on Ubuntu "eoan" following the description in the wiki. This basically worked without problems and the web UI was available after completion. However, it did not show any devices.



Analysis:



Device-Check:



$ ls -la /dev/dvb/adapter*

/dev/dvb/adapter0:

total 0

drwxr-xr-x  2 root root    140 Feb 16 12:51 .

drwxr-xr-x  4 root root      80 Feb 16 12:51 ..

crw-rw----+ 1 root video 212, 3 Feb 16 12:51 ca0

crw-rw----+ 1 root video 212, 0 Feb 16 12:51 demux0

crw-rw----+ 1 root video 212, 1 Feb 16 12:51 dvr0

crw-rw----+ 1 root video 212, 4 Feb 16 12:51 frontend0

crw-rw----+ 1 root video 212, 2 Feb 16 12:51 net0



/dev/dvb/adapter1:

total 0

drwxr-xr-x  2 root root    140 Feb 16 12:52 .

drwxr-xr-x  4 root root      80 Feb 16 12:51 ..

crw-rw----+ 1 root video 212, 8 Feb 16 12:52 ca0

crw-rw----+ 1 root video 212, 5 Feb 16 12:51 demux0

crw-rw----+ 1 root video 212, 6 Feb 16 12:51 dvr0

crw-rw----+ 1 root video 212, 9 Feb 16 12:52 frontend0

crw-rw----+ 1 root video 212, 7 Feb 16 12:51 net0



Group-Check:

$ getent group video

video:x:44:mythtv,nextpvr



So NextPVR should have access to the devices.

But devices are not detected:

$ sudo -u nextpvr /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover

<devices>

</devices>




Output from "lsusb -v" (for one of the 2 identical devices):

Bus 001 Device 002: ID 14f7:0003 TechniSat Digital GmbH CableStar Combo HD CI

Device Descriptor:

  bLength                18

  bDescriptorType        1

  bcdUSB              2.00

  bDeviceClass            0

  bDeviceSubClass        0

  bDeviceProtocol        0

  bMaxPacketSize0        64

  idVendor          0x14f7 TechniSat Digital GmbH

  idProduct          0x0003 CableStar Combo HD CI

  bcdDevice            0.03

  iManufacturer          1 TechniSat Digital S.A.

  iProduct                2 CableStar Combo HD CI

  iSerial                3 0008C9D91EA0

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                9

    bDescriptorType        2

    wTotalLength      0x0020

    bNumInterfaces          1

    bConfigurationValue    1

    iConfiguration          0

    bmAttributes        0xc0

      Self Powered

    MaxPower              100mA

    Interface Descriptor:

      bLength                9

      bDescriptorType        4

      bInterfaceNumber        0

      bAlternateSetting      0

      bNumEndpoints          2

      bInterfaceClass      255 Vendor Specific Class

      bInterfaceSubClass      0

      bInterfaceProtocol      0

      iInterface              0

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x81  EP 1 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type              None

          Usage Type              Data

        wMaxPacketSize    0x0200  1x 512 bytes

        bInterval            100

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x82  EP 2 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type              None

          Usage Type              Data

        wMaxPacketSize    0x0200  1x 512 bytes

        bInterval              1







Any advise welcome.

Does a dvbv5-scan detect your device?

Martin

Is this a DVB-C only device?

Up until now "DeviceHostLinux -discover" is currently expecting that DVB-C devices also support DVB-T. (long story, but related to FE_QAM devices being a bit ambiguous, since they could be European style DVB-C or North American style QAM)

I've made change to DeviceHostLinux, so that this device should be detected.

I should mention in advance though - it wont support the CI aspects of this device, so will only be useful for unencrypted content.

(2020-04-04, 12:48 PM)mvallevand Wrote: [ -> ]Does a dvbv5-scan detect your device? 

Yes, it does.

(2020-04-04, 04:25 PM)sub Wrote: [ -> ]Is this a DVB-C only device?

Up until now "DeviceHostLinux -discover" is currently expecting that DVB-C devices also support DVB-T.  (long story, but related to FE_QAM devices being a bit ambiguous, since they could be European style DVB-C or North American style QAM)

Yes, only DVB-C.

(2020-04-04, 04:27 PM)sub Wrote: [ -> ]I've made change to DeviceHostLinux, so that this device should be detected.

I should mention in advance though - it wont support the CI aspects of this device, so will only be useful for unencrypted content.

Uhh, thanks! As CI isn't used, that should do.

What would be the best approach to receive and install that changed "DeviceHostLinux" ?

If you're not up for waiting until the next release, you could try replacing your existing version with this one

(64bit intel version)

(2020-04-04, 10:12 PM)sub Wrote: [ -> ]If you're not up for waiting until the next release, you could try replacing your existing version with this one

(64bit intel version)

Thanks,
Devices are now visible and functioning.

Great!