Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Themen - Simon78

Seiten: [1]
1
{Single, Dual, Quad} Sundtek SkyTV Ultimate / SkyTv Ultimate Dual , Continuity Errors , isochronous mode
« am: Oktober 04, 2023, 06:41:18 Vormittag »
Hallo,

ich lasse tvheadend 4.3 und kodi 20.2 auf nem Odroid H3 laufen ( 2,9ghz quad core atom , 16gb RAM und SSDs ), habe trotzdem continuity errors welche mir die streams kaputt machen !

Ich habe alles probiert :
- scheduling ist ok , tvheadend, kodi und mediasrv geniessen höchste Prio
- neueste intel media driver
- kernel 6.5.5 ( neuester )

ich würde gerne den Transfermodus mal auf isochronous umsetzen weil mir kaum was anderes noch einfällt, die Kiste hat genug Dampf und sonst keine Probleme, die USB Busse sind per PCIe angebunden mit genug Power

Aber:
wenn ich per mediaclient --transfermode=iso -d /dev/dvb/apapter0/frontend0 den Modus umstelle , passiert : nichts. ich habe das device auch stromlos gemacht und wieder eingesteckt, keine chance

lsusb zeigt immer noch bulk:

Bus 001 Device 004: ID 2659:1802 Sundtek Dual S2
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x2659 Sundtek
  idProduct          0x1802
  bcdDevice            0.00
  iManufacturer           1 Sundtek
  iProduct                2 Dual S2
  iSerial                 3 U220618172518
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0027
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              400mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0006  1x 6 bytes
        bInterval              10
      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               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

root@tvh:/root# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [             Dual S2]  DVB-S/S2, REMOTE-CONTROL, DVB-S/S2
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-3
  [SERIAL]:
     ID: U220618172518
  [DVB-S/S2]:
     FESTATUS: STANDBY
     LNBVOLTAGE: DISABLED
     LNBSUPPLY: USBPOWER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [DVB-S/S2]:
     FESTATUS: STANDBY
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0


Hinweis, ich lasse das seit längerem erfolgreich im unpriviligiertem LXC container laufen.

Würde mich über Hilfe freuen , mein Fernseherlebnis ist grade im Arxxx.

Danke !

2
{Single, Dual, Quad} Sundtek SkyTV Ultimate / SkyTv Ultimate Dual + LXC unpriviliged
« am: Januar 04, 2023, 11:34:54 Vormittag »
Hallo,

da es dazu noch keine Anleitung gibt , hangel ich mich mal dadurch.


bisher habe ich gemacht:

1. anlegen der /dev/dvb/card[0/1] devices auf dem host
2. installieren der netinst.sh auf dem LXC unpriv container
3. durchreichen des /dev/usb/001/005 devices an den container

das device ist per lsusb auch sichtbar. Jetzt hänge ich beim mediasrv wegen:

2023-01-04 09:27:52 [650]
2023-01-04 09:27:52 [650] Scanning for drivers
2023-01-04 09:27:52 [650] found lib: libdrv_ngTV.so
2023-01-04 09:27:52 [650] found lib: libdrv_net.so
2023-01-04 09:27:52 [650] found lib: libdrv_tntdvb.so
2023-01-04 09:27:52 [650] found lib: libdrv_hikarisoft_isdb.so
2023-01-04 09:27:52 [650] found lib: libdrv_fm.so
2023-01-04 09:27:52 [650] found lib: libdrv_vivi.so
2023-01-04 09:27:52 [650] found lib: libdrv_fm_dab_dabplus.so
2023-01-04 09:27:52 [650] found lib: libdrv_em28xx.so
2023-01-04 09:27:52 [650] found lib: libdrv_eLight.so
2023-01-04 09:27:52 [650]
2023-01-04 09:27:52 [650] Scanning for plugins
2023-01-04 09:27:52 [650] found lib: libencoder_plugin.so
2023-01-04 09:27:52 [650] MediaAVPlugin: MPEG Encoder
2023-01-04 09:27:52 [650] Copyright: (C) Tpe 2011/2012
2023-01-04 09:27:52 [650]
2023-01-04 09:27:52 [650] Starting up device manager
2023-01-04 09:27:52 [650] unable to create /dev/sundtek/usb/001/005, this will lead to a failure now
2023-01-04 09:27:52 [650] retrying with 3rd workaround now
2023-01-04 09:27:52 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/002)
2023-01-04 09:27:53 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/002)
2023-01-04 09:27:54 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/002)
2023-01-04 09:27:55 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/002)
2023-01-04 09:27:56 [650] skipping unknown busy device, check dmesg maybe a module is interfering (eg. usbhid)
2023-01-04 09:27:56 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/004)
2023-01-04 09:27:57 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/004)
2023-01-04 09:27:58 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/004)
2023-01-04 09:27:59 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/004)
2023-01-04 09:28:00 [650] skipping unknown busy device, check dmesg maybe a module is interfering (eg. usbhid)
2023-01-04 09:28:00 [650] Setting permission of /dev/dvb to 777
2023-01-04 09:28:00 [650] This is to avoid problems if TV Applications are started as another user
2023-01-04 09:28:00 [650] as seen on eg. Synology NAS Systems where tvheadend is unable to read
2023-01-04 09:28:00 [650] /dev/dvb and because of that would not detect the TV tuner
2023-01-04 09:28:00 [650] scanning devices done
2023-01-04 09:28:00 [650] attached devices:
2023-01-04 09:28:00 [651] Autostarting scripts in /etc/sundtek/
2023-01-04 09:28:00 [651] executed all available items
2023-01-04 09:28:07 [650] device not ready, sleeping 3 seconds and retrying (/dev/bus/usb/001/002)
^C2023-01-04 09:28:07 [650] Shutting down driver


es scheint so zu sein als ob ein /dev/sundtek irgendwas angelegt werden soll im LXC container. das ist nirgendwo beschrieben wo es mir bekannt wäre und der mediasrv wirft deswegen ab.


Wie gehts weiter ?

MFG,
Simon

Seiten: [1]