sundtek dvbs stick

    • sundtek dvbs stick

      Hallo bekomme leider eine Bootschleife mit angehangenem Stick:

      root@dm800se:~# init 5
      root@dm800se:~# enigma2
      Enigma2 v4.0.0 (revision: tarball-20131118-0-g8b3054f, date: 2013-11-18)

      Enigma2 is property of Dream Multimedia GmbH. All copyrights with regard to
      Enigma2 belong to Dream Multimedia GmbH only.

      The full license text is available at /usr/share/doc/enigma2/LICENSE.

      PYTHONPATH: /usr/lib/enigma2/python
      + (1) Background File Eraser
      before: 1
      after: 1
      + (8) graphics acceleration manager
      setIoPrio best-effort level 7 ok
      + (9) GFBDC
      16384k video mem
      - double buffering not available.
      14764kB available for acceleration surfaces.
      resolution: 720 x 576 x 32 (stride: 2880)
      + (9) gLCDDC
      found OLED display!
      lcd buffer 0x92e298 12288 bytes, stride 192
      + (9) Font Render Class
      [FONT] initializing lib...
      [FONT] loading fonts...
      [FONT] Intializing font cache, using max. 4MB...
      + (10) gRC
      RC thread created successfully
      + (15) eWindowStyleManager
      + (20) DVB-CI UI
      + (20) UHF Modulator
      couldnt open /dev/rfmod0!!!!
      + (20) RC Input layer
      + (20) misc options
      + (20) HDMI CEC Subsystem
      attached: hdmi attached
      attached: hdmi cec address acknowledged
      my physical: 1.0.0.0 logical 3
      + (20) AVSwitch Driver
      couldnt open /dev/dbox/fp0 to monitor vcr scart slow blanking changed!
      + (21) input device driver
      Input device "dreambox front panel" is a remotecontrol
      Input device "dreambox remote control (native)" is a remotecontrol
      Input device "dreambox advanced remote control (native)" is a remotecontrol
      Input device "dreambox ir keyboard" is a keyboard
      Input device "dreambox ir mouse" is a mouse
      Found 5 input devices!
      + (21) Console RC Driver
      + (30) eActionMap
      + (35) CI Slots
      scanning for common interfaces..
      cannot open /proc/stb/tsmux/input0
      cannot open /proc/stb/tsmux/input1
      done, found 0 common interface slots
      + (40) eServiceCenter
      settings instance.
      + (41) eHbbtv
      + (41) eServiceFactoryBludisc
      + (41) eServiceFactoryM2TS
      + (41) eServiceFactoryMP3
      + (41) eServiceFactoryFS
      + (41) eServiceFactoryDVB
      reached rl 70
      ---- opening lame channel db
      reading services (version 4)
      loaded 0 services
      scanning for frontends..
      opening frontend 0
      detected cable frontend
      close frontend 0
      opening frontend 1
      detected satellite frontend
      (1)setTone Off
      (1)setVoltage 0V
      FE_ENABLE_HIGH_LNB_VOLTAGE: Interrupted system call
      close frontend 1
      main thread is non-idle! display spinner!
      no spinner DC!
      FE_ENABLE_HIGH_LNB_VOLTAGE: Interrupted system call
      scanning for demux..
      scanning for decoders..
      scanning for descramblers..
      found 1 adapter, 2 frontends(2 sim) and 5 demux, boxtype 3
      [eDVBLocalTimeHandler] Use valid Linux Time 'Sat Feb 8 05:42:10 2014' :) (RTC?)
      [EPGC] Initialized EPGCache (wait for setCacheFile call now)
      Loading spinners...
      found 12 spinners!
      executing main
      setIoPrio best-effort level 6 ok
      main thread is non-idle! display spinner!
      warning: unknown NIM type , not using.
      Reading cables.xml
      couldn't open /etc/tuxbox/cables.xml!!
      sec config cleared
      setSlotInfo for dvb frontend 0 to slotid 0, descr Philips CU1216Mk3, need rotorworkaround No, enabled Yes, DVB-S2 No
      Traceback (most recent call last):
      File "/usr/lib/enigma2/python/mytest.py", line 84, in <module>
      from Components.DreamInfoHandler import ImageDefaultInstaller
      File "/usr/lib/enigma2/python/Components/DreamInfoHandler.py", line 4, in <module>
      from Components.NimManager import nimmanager
      File "/usr/lib/enigma2/python/Components/NimManager.py", line 1592, in <module>
      nimmanager = NimManager()
      File "/usr/lib/enigma2/python/Components/NimManager.py", line 812, in __init__
      InitNimManager(self) #init config stuff
      File "/usr/lib/enigma2/python/Components/NimManager.py", line 1590, in InitNimManager
      nimmgr.sec = SecConfigure(nimmgr)
      File "/usr/lib/enigma2/python/Components/NimManager.py", line 486, in __init__
      self.update()
      File "/usr/lib/enigma2/python/Components/NimManager.py", line 153, in update
      eDVBResourceManager.getInstance().setFrontendSlotInformations(used_nim_slots)
      StandardError: eDVBResourceManager::setFrontendSlotInformations .. assigned 2 socket informations, but 1 registered frontends!
      ---- saving lame channel db
      saved 0 channels and 0 services!
      release cached channel (timer timeout)
      set RTC to previous valid time
      - (41) eHbbtv
      - (41) eServiceFactoryBludisc
      - (41) eServiceFactoryM2TS
      - (41) eServiceFactoryMP3
      - (41) eServiceFactoryFS
      - (41) eServiceFactoryDVB
      - (40) eServiceCenter
      clear instance
      - (35) CI Slots
      - (30) eActionMap
      - (21) input device driver
      - (21) Console RC Driver
      - (20) DVB-CI UI
      - (20) UHF Modulator
      - (20) RC Input layer
      - (20) misc options
      - (20) HDMI CEC Subsystem
      - (20) AVSwitch Driver
      - (15) eWindowStyleManager
      - (10) gRC
      waiting for gRC thread shutdown
      gRC thread has finished
      - (9) GFBDC
      - (9) gLCDDC
      - (9) Font Render Class
      - (8) graphics acceleration manager
      - (1) Background File Eraser
      eBackgroundFileEraser got quit message
      thread joined 0
      reached rl -1
      root@dm800se:~#
    • Mrmr schrieb:

      war ein Treiberproblem, wurde von sundtek gefixt.


      Woher hast du diese Info? Habe am Wochenende auch Stress mit meiner Sundtek DVB-S gehabt. Nach Neuinstallation des 4.08 Lean ist die Kiste immer kurz vor Ende des Bootvorgangs abgestürzt. Blinkendes Front-Display. Ziehe ich die Sundtek aus der 800se raus bootet die Kiste ohne Probleme.

      Bekomme sie aber immer noch nicht zum laufen. Werden die gefixten Treiber über das Control Center automatisch eingespielt oder nur per Telnet?
    • genau das gleiche hatte ich auch, probier mal nochmal von sundtek alles neu installiieren mit dem settopbox programm.
      sundtek hatte zugriff per tunnel auf meinen stick da haben die das treiber problem gelöst, aber meinten das sie jetzt auch was bei treiber online geändert haben.

      probier mal aus

      gruss
      mrmr