Sundtek Support Forum

Hallo,

Ich habe einen "Sundtek MediaTV Digital Home (DVB-C/T)" Stick im Internet bestellt, da dieser sich angeblich unter Linux einsetzen lässt. Bereits beim Auspacken hatte ich das Gefühl, daß es sich nicht um Neuware handelt. Da ich nicht so leicht abzuschrecken bin, habe ich ihn trotzdem versucht zum Laufen zu bekommen. Ein Einstecken an verschiedenen USB-Ports (ohne vorherige Treiberinstallation) ergab jedoch im Log nur folgende Meldungen:

Jul 26 14:31:34 foobar kernel: usb 4-2: new full-speed USB device number 3 using uhci_hcd
Jul 26 14:31:34 foobar kernel: usb 4-2: device descriptor read/64, error -71
Jul 26 14:31:34 foobar kernel: usb 4-2: device descriptor read/64, error -71
Jul 26 14:31:34 foobar kernel: usb 4-2: new full-speed USB device number 4 using uhci_hcd
Jul 26 14:31:34 foobar kernel: usb 4-2: device descriptor read/64, error -71
Jul 26 14:31:35 foobar kernel: usb 4-2: device descriptor read/64, error -71
Jul 26 14:31:35 foobar kernel: usb 4-2: new full-speed USB device number 5 using uhci_hcd
Jul 26 14:31:35 foobar kernel: usb 4-2: device not accepting address 5, error -71
Jul 26 14:31:35 foobar kernel: usb 4-2: new full-speed USB device number 6 using uhci_hcd
Jul 26 14:31:36 foobar kernel: usb 4-2: device not accepting address 6, error -71
Jul 26 14:31:36 foobar kernel: hub 4-0:1.0: unable to enumerate USB device on port 2
...

Mit lspci wird auch kein neues Gerät aufgelistet. Nach einigem Rumprobieren hat sich dann jedoch ein Port gefunden wo folgendes passiert ist:

Jul 26 14:32:19 foobar kernel: usb 3-2: new full-speed USB device number 6 using xhci_hcd
Jul 26 14:32:19 foobar kernel: usb 3-2: device descriptor read/64, error -71
Jul 26 14:32:19 foobar kernel: xhci_hcd 0000:04:00.0: Setup ERROR: setup context command for slot 1.
Jul 26 14:32:20 foobar kernel: usb 3-2: new full-speed USB device number 7 using xhci_hcd
Jul 26 14:32:20 foobar kernel: usb 3-2: device descriptor read/64, error -71
Jul 26 14:32:20 foobar kernel: xhci_hcd 0000:04:00.0: Setup ERROR: setup context command for slot 1.
Jul 26 14:32:20 foobar kernel: usb 3-2: new full-speed USB device number 8 using xhci_hcd
Jul 26 14:32:20 foobar kernel: usb 3-2: Device not responding to setup address.
Jul 26 14:32:20 foobar kernel: usb 3-2: Device not responding to setup address.
Jul 26 14:32:20 foobar kernel: usb 3-2: device not accepting address 8, error -71
Jul 26 14:32:20 foobar kernel: usb 3-2: new full-speed USB device number 9 using xhci_hcd
Jul 26 14:32:20 foobar kernel: usb 3-2: Device not responding to setup address.
Jul 26 14:32:21 foobar kernel: usb 3-2: Device not responding to setup address.
Jul 26 14:32:21 foobar kernel: usb 3-2: device not accepting address 9, error -71
Jul 26 14:32:21 foobar kernel: hub 3-0:1.0: unable to enumerate USB device on port 2
Jul 26 14:32:21 foobar kernel: usb 9-2: new full-speed USB device number 3 using uhci_hcd
Jul 26 14:32:21 foobar kernel: usb 9-2: not running at top speed; connect to a high speed hub
Jul 26 14:32:21 foobar kernel: usb 9-2: New USB device found, idVendor=eb1a, idProduct=51b2
Jul 26 14:32:21 foobar kernel: usb 9-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Jul 26 14:32:21 foobar kernel: usb 9-2: Product: MediaTV Digital Home
Jul 26 14:32:21 foobar kernel: usb 9-2: Manufacturer: Sundtek
Jul 26 14:32:21 foobar kernel: usb 9-2: SerialNumber: U120509210647
Jul 26 14:32:21 foobar kernel: usb 9-2: can't set config #1, error -84
Jul 26 14:32:23 foobar systemd-udevd[4755]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.3/usb9/9-2 9 3': No such file or directory
Jul 26 14:32:24 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:26 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:34 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:36 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:39 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:42 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:44 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:47 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
Jul 26 14:32:50 foobar kernel: hub 3-0:1.0: connect-debounce failed, port 2 disabled
...

Das sieht nicht besonders gut aus! lsusb sagt jedoch zumindest etwas:

foobar:~# lsusb
Bus 009 Device 003: ID eb1a:51b2 eMPIA Technology, Inc.

foobar:~# lusb -v
Bus 009 Device 003: ID eb1a:51b2 eMPIA Technology, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0xeb1a eMPIA Technology, Inc.
  idProduct          0x51b2
  bcdDevice            1.00
  iManufacturer           1 (error)
  iProduct                3 (error)
  iSerial                 2 (error)
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           41
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Hierauf habe ich mal die Software installiert, wie im Internet beschrieben:

foobar:~# ./sundtek_netinst.sh
Busybox installation

Welcome to the Sundtek linux driver setup
(C)opyright 2008-2014 Sundtek <kontakt@sundtek.de>

Legal notice:
This software comes without any warranty, use it at your own risk

Please note it's only allowed to use this driver package with devices from
authorized distributors or from Sundtek Germany
The Virtual analogTV Grabber (vivi) might be used freely for testing purpose

Do you want to continue [Y/N]:
Nutzungsbedingungen:
Sundtek übernimmt keinerlei Haftung für Schäden welche eventuell durch
das System oder die angebotenen Dateien entstehen können.

Dieses Softwarepaket darf ausschließlich mit Geraeten von authorisierten
Distributoren oder Sundtek Deutschland verwendet werden
Der Virtuelle AnalogTV Treiber (vivi) kann für Testzwecke ohne jegliche
Restriktionen verwendet werden

Wollen Sie fortfahren [J/N]:
j
adding /opt/bin to environment paths
unpacking...
checking system... testing libc OK 2.19.0
32Bit System detected
installing (netinstall mode) ...
Downloading architecture specific driver ... 32bit
Download finished, installing now ...
installing remote control support
finalizing configuration... (can take a few seconds) 
Starting driver...
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 128 rq 6 len 18 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 0 len 1 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 0 len 1 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
Jul 26 14:35:40 foobar kernel: usb 9-2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 2 ret -71
...

Diese Meldungen wiederholten sich uber viele Bildschirmseiten! Kein gutes Zeichen denke ich. Nun habe ich trotzdem noch das probiert:

foobar:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Pro/Digital Home] foobar:~#

Sonderbarerweise bricht das Programm mitten in einer Zeile ab (hier fehlt wohl auch ein Returncode!). Ich nehme an, daß das Programm versucht hat Informationen über den Stick auszulesen und hier etwas schief gegangen ist.

Ausstecken und einstecken vom Stick ergibt wieder folgende Systemfehlermeldungen:

Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:33 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:34 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:34 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 34 ret -71
Jul 26 14:37:34 foobar kernel: usb 11-8: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 3 len 34 ret -71
Jul 26 14:37:36 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:36 foobar kernel: usb 11-2: device not accepting address 2, error -71
Jul 26 14:37:36 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:37 foobar kernel: usb 11-2: device not accepting address 2, error -71
Jul 26 14:37:37 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:38 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:40 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:43 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
Jul 26 14:37:44 foobar kernel: usb 11-2: device not accepting address 2, error -71
Jul 26 14:37:44 foobar kernel: usb 11-2: reset high-speed USB device number 2 using ehci-pci
...

Ich bin mir nicht sicher ob ich etwas falsch mache, für mich sieht das aber so aus, als ob das Gerät defekt ist. Kann mir hier jemand weiterhelfen? Vielleicht gibt es ja noch irgendwas was ich testen kann? Vielleicht gibt es auch einige Möglichkeit herauszufinden, ob das Gerät schon im Einsatz war? Das Gehäuse sieht eigentlich so aus (hat einen auffälligen Kratzer).

Mein System ist ein tagesaktuelles Debian testing mit Kernel

Linux version 3.14-1-686-pae (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11)

auf einem Intel Core i7 860 und ca. 4 Jahre alt.

Gruss,
Thomas.