krieg meine 525c nicht in den Rescue Loader

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Besten Dank ...
      das hab ich alles schon probiert .

      Es wird nicht's angezeigt im Monitor.. LED ist rot,

      Per Browser wird nicht's angezeigt (Firefox, Chrome, Edge , Safari)

      per telnet komm ich auf die Box ,
      den Ordner stb gibt es bei mir nicht ?!

      to-the-resecue kann ich ausführen ... Box bootet dann aber es scheint kein "richtiger" resecue zu sein !? (LED ist rot)

      Ansonsten lässt sich die Box normal starten, hab auch schon mal werkseinstellungen gemacht .. hat nix gebracht

      was könnt ich noch probieren ?

    • Quellcode

      1. x.[0m!
      2. [ 4.269000] systemd[1]: Set hostname to <dm520>.
      3. [ 4.883000] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
      4. [ 4.897000] systemd[1]: Expecting device dev-dvb-adapter0-video0.device...
      5. Expecting device dev-dvb-adapter0-video0.device...
      6. [ 4.901000] systemd[1]: Starting Generate environment for enigma2...
      7. Starting Generate environment for enigma2...
      8. [ 4.920000] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
      9. [ 4.922000] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
      10. [ 4.924000] systemd[1]: Expecting device dev-ttyS0.device...
      11. Expecting device dev-ttyS0.device...
      12. [ 4.927000] systemd[1]: Expecting device dev-sci0.device...
      13. Expecting device dev-sci0.device...
      14. [ 4.930000] systemd[1]: Expecting device dev-dvb-adapter0-demux0.device...
      15. Expecting device dev-dvb-adapter0-demux0.device...
      16. [ 4.933000] systemd[1]: Expecting device dev-dvb-adapter0-ca0.device...
      17. Expecting device dev-dvb-adapter0-ca0.device...
      18. [ 4.935000] systemd[1]: Expecting device dev-tpm0.device...
      19. Expecting device dev-tpm0.device...
      20. [ 4.938000] systemd[1]: Starting Delayed Shutdown Socket.
      21. [.[32m OK .[0m] Listening on Delayed Shutdown Socket.
      22. [ 4.954000] systemd[1]: Listening on Delayed Shutdown Socket.
      23. [ 4.955000] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
      24. [.[32m OK .[0m] Listening on /dev/initctl Compatibility Named Pipe.
      25. [ 4.957000] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
      26. [ 4.958000] systemd[1]: Starting Root Slice.
      27. [.[32m OK .[0m] Created slice Root Slice.
      28. [ 4.961000] systemd[1]: Created slice Root Slice.
      29. [ 4.961000] systemd[1]: Starting User and Session Slice.
      30. [.[32m OK .[0m] Created slice User and Session Slice.
      31. [ 4.965000] systemd[1]: Created slice User and Session Slice.
      32. [ 4.966000] systemd[1]: Starting System Slice.
      33. [.[32m OK .[0m] Created slice System Slice.
      34. [ 4.967000] systemd[1]: Created slice System Slice.
      35. [ 4.968000] systemd[1]: Starting Slices.
      36. [.[32m OK .[0m] Reached target Slices.
      37. [ 4.971000] systemd[1]: Reached target Slices.
      38. [ 4.971000] systemd[1]: Starting system-serial\x2dgetty.slice.
      39. [.[32m OK .[0m] Created slice system-serial\x2dgetty.slice.
      40. [ 4.976000] systemd[1]: Created slice system-serial\x2dgetty.slice.
      41. [ 4.977000] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
      42. [ 4.978000] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
      43. [ 4.979000] systemd[1]: Starting Paths.
      44. [.[32m OK .[0m] Reached target Paths.
      45. [ 4.982000] systemd[1]: Reached target Paths.
      46. [ 4.984000] systemd[1]: Starting udev Kernel Socket.
      47. [.[32m OK .[0m] Listening on udev Kernel Socket.
      48. [ 4.987000] systemd[1]: Listening on udev Kernel Socket.
      49. [ 4.988000] systemd[1]: Starting udev Control Socket.
      50. [.[32m OK .[0m] Listening on udev Control Socket.
      51. [ 4.990000] systemd[1]: Listening on udev Control Socket.
      52. [ 4.991000] systemd[1]: Starting Journal Socket.
      53. [.[32m OK .[0m] Listening on Journal Socket.
      54. [ 4.994000] systemd[1]: Listening on Journal Socket.
      55. [ 4.995000] systemd[1]: Starting udev Coldplug all Devices...
      56. Starting udev Coldplug all Devices...
      57. [ 5.007000] systemd[1]: Mounted Debug File System.
      58. [ 5.008000] systemd[1]: Mounted Huge Pages File System.
      59. [ 5.023000] systemd[1]: Starting Load Kernel Modules...
      60. Starting Load Kernel Modules...
      61. [ 5.060000] systemd[1]: Starting Apply Kernel Variables...
      62. Starting Apply Kernel Variables...
      63. [ 5.077000] systemd[1]: Starting Journal Service...
      64. Starting Journal Service...
      65. [.[32m OK .[0m] Started Journal Service.
      66. [ 5.109000] systemd[1]: Started Journal Service.
      67. [ 5.111000] systemd[1]: Starting Create list of required static device nodes for the current kernel...
      68. Starting Create list of required static device nodes...rrent kernel...
      69. [ 5.128000] systemd[1]: Mounting POSIX Message Queue File System...
      70. Mounting POSIX Message Queue File System...
      71. [ 5.144000] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
      72. [ 5.187000] systemd[1]: Started Set Up Additional Binary Formats.
      73. [ 5.188000] systemd[1]: Starting Swap.
      74. [.[32m OK .[0m] Reached target Swap.
      75. [ 5.191000] systemd[1]: Reached target Swap.
      76. [ 5.192000] systemd[1]: Started File System Check on Root Device.
      77. [ 5.193000] systemd[1]: Starting Remount Root and Kernel File Systems...
      78. Starting Remount Root and Kernel File Systems...
      79. [.[32m OK .[0m] Started Generate environment for enigma2.
      80. [ 5.331000] systemd[1]: Started Generate environment for enigma2.
      81. [.[32m OK .[0m] Started Apply Kernel Variables.
      82. [ 5.343000] systemd[1]: Started Apply Kernel Variables.
      83. [.[1;31mFAILED.[0m] Failed to start Load Kernel Modules.
      84. See 'systemctl status systemd-modules-load.service' for details.
      85. [.[32m OK .[0m] Mounted POSIX Message Queue File System.
      86. [.[32m OK .[0m] Started Remount Root and Kernel File Systems.
      87. [.[32m OK .[0m] Started Create list of required static device nodes ...current kernel.
      88. Starting Create static device nodes in /dev...
      89. Starting Load/Save Random Seed...
      90. [.[32m OK .[0m] Started udev Coldplug all Devices.
      91. [.[32m OK .[0m] Started Load/Save Random Seed.
      92. [.[32m OK .[0m] Started Create static device nodes in /dev.
      93. Starting udev Kernel Device Manager...
      94. [.[32m OK .[0m] Reached target Local File Systems (Pre).
      95. Mounting /var/volatile...
      96. Mounting /tmp...
      97. [.[32m OK .[0m] Mounted /var/volatile.
      98. [.[32m OK .[0m] Mounted /tmp.
      99. [.[32m OK .[0m] Reached target Local File Systems.
      100. Starting Recreate Volatile Files and Directories...
      101. [ 5.875000] systemd-udevd[95]: starting version 206
      102. [.[32m OK .[0m] Started udev Kernel Device Manager.
      103. [.[32m OK .[0m] Started Recreate Volatile Files and Directories.
      104. Starting Update UTMP about System Reboot/Shutdown...
      105. [.[32m OK .[0m] Started Update UTMP about System Reboot/Shutdown.
      106. [.[32m OK .[0m] Reached target System Initialization.
      107. [.[32m OK .[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
      108. [.[32m OK .[0m] Listening on D-Bus System Message Bus Socket.
      109. [.[32m OK .[0m] Listening on vsftpd.socket.
      110. [.[32m OK .[0m] Listening on dropbear.socket.
      111. [.[32m OK .[0m] Listening on busybox-telnetd.socket.
      112. [.[32m OK .[0m] Listening on tpmd.socket.
      113. [.[32m OK .[0m] Listening on streamproxy.socket.
      114. [.[32m OK .[0m] Reached target Timers.
      115. [.[32m OK .[0m] Listening on dbttcd.socket.
      116. [.[32m OK .[0m] Listening on dccamd.socket.
      117. [.[32m OK .[0m] Reached target Sockets.
      118. Starting enigma2...
      119. [.[32m OK .[0m] Reached target Basic System.
      120. Starting samba.service...
      121. Starting Telephony service...
      122. Starting dbttcd.service...
      123. Starting D-Bus System Message Bus...
      124. [.[32m OK .[0m] Started D-Bus System Message Bus.
      125. Starting Connection service...
      126. Starting Login Service...
      127. Starting Avahi mDNS/DNS-SD Stack...
      128. [.[32m OK .[0m] Found device /dev/ttyS0.
      129. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      130. See 'systemctl status dbttcd.service' for details.
      131. Stopping dbttcd.service...
      132. [.[32m OK .[0m] Stopped dbttcd.service.
      133. Starting dbttcd.service...
      134. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      135. See 'systemctl status dbttcd.service' for details.
      136. Stopping dbttcd.service...
      137. [.[32m OK .[0m] Stopped dbttcd.service.
      138. Starting dbttcd.service...
      139. [.[32m OK .[0m] Started Avahi mDNS/DNS-SD Stack.
      140. [.[32m OK .[0m] Started Connection service.
      141. [.[32m OK .[0m] Started Telephony service.
      142. [.[32m OK .[0m] Reached target Remote File Systems (Pre).
      143. [.[32m OK .[0m] Reached target Remote File Systems.
      144. Starting Trigger Flushing of Journal to Persistent Storage...
      145. [.[32m OK .[0m] Reached target Network.
      146. Starting Automounts filesystems on demand...
      147. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      148. See 'systemctl status dbttcd.service' for details.
      149. [.[32m OK .[0m] Started Login Service.
      150. Stopping dbttcd.service...
      151. [.[32m OK .[0m] Stopped dbttcd.service.
      152. Starting dbttcd.service...
      153. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      154. See 'systemctl status dbttcd.service' for details.
      155. Stopping dbttcd.service...
      156. [.[32m OK .[0m] Stopped dbttcd.service.
      157. Starting dbttcd.service...
      158. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      159. See 'systemctl status dbttcd.service' for details.
      160. Stopping dbttcd.service...
      161. [.[32m OK .[0m] Stopped dbttcd.service.
      162. Starting dbttcd.service...
      163. [.[1;31mFAILED.[0m] Failed to start dbttcd.service.
      164. See 'systemctl status dbttcd.service' for details.
      165. [.[32m OK .[0m] Started Trigger Flushing of Journal to Persistent Storage.
      166. Starting Permit User Sessions...
      167. [.[32m OK .[0m] Started Permit User Sessions.
      168. Starting Serial Getty on ttyS0...
      169. [.[32m OK .[0m] Started Serial Getty on ttyS0.
      170. [.[32m OK .[0m] Reached target Login Prompts.
      171. [.[32m OK .[0m] Started Automounts filesystems on demand.
      172. Starting WPA supplicant...
      173. Starting Hostname Service...
      174. [.[32m OK .[0m] Started Hostname Service.
      175. [ 9.319000] ADDRCONF(NETDEV_UP): eth0: link is not ready
      176. [.[32m OK .[0m] Started WPA supplicant.
      177. [.[32m OK .[0m] Started samba.service.
      178. [ 10.868000] bcmgenet bcmgenet.0: eth0: link up, 100 Mbps, full duplex
      179. [ 10.869000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
      182. opendreambox 2.2.0 dm520 ttyS0
      184. dm520 login:
      Alles anzeigen

    • Hast du auf der Dreambox bei Netzwerkeinstellungen Dhcp oder eine feste IP vergeben ?
      Ich hatte mal ein Problem mit einer DM7080, die einfach nicht in den Rescue loader ging. ( auch ohne Netzwerkkabel an der Box )
      Das Problem war die feste IP Adresse . Umgestellt auf dhcp und ich konnte in den Rescue loader.

      Hier auch noch die Anleitung Schnelleinstieg zu den aktuellen OE2.5 Images (DM520/525, DM820HD, DM7080HD, DM900UHD)

      Oder Video :

    • ManoMan ...

      nach dieser Anleitung hat es nun auf Anhieb geklappt ..

      1) Passendes Rescue-Image bei DMM runterladen
      2) zImage auf die box kopieren; z.B. nach /tmp
      3) per SSH/Telnet auf die Box
      4) nach /tmp wechseln
      5) flash-rescue dateiname ausführen


      das hat mich nun Stunden gekostet ...

    • Tja... Du hast ja auch immer nur spärliche Infos rausgerückt. Ich hatte im IHAD schon gestern nach einem Bootlog gefragt...
      Dort hattest du aber die Info unterschlagen, dass das reguläre Image intakt ist. Und ja, mit Bootlog und dieser Info hätte ich als nächstes update-rescue oder flash-rescue vorgeschlagen.

      Ein Verweis auf den anderen Thread und mal die Grundinfos hätten hier im Thread ne Menge Posts erspart!

      Wo du jetzt diese Anleitung her hast, will ich glaube ich gar nicht wissen... Wahrscheinlich noch ein 3. und 4. und 5. Forum, in dem du mit nochmal neuen Nicks gefragt hast? Ich fühl mich verarscht...