Bluescreen :(

[murruck]

Hallo,

Ich habe heute meine Quad Plus mit dem neusten Openatv Image geflasht.
Alles lief wie immer glatt.

Jetzt habe ich gerade ein paar Erweiterungen aktualisiert und installiert und plötzlich kam ein Bluescreen

Nun fährt die Box in Endlosschleife hoch und stürzt ab!

Kann mir jemand behilflich sein?

Du musst angemeldet sein, um Bilder zu sehen.

Vielen Dank im Voraus!


Gesendet von meinem iPhone mit Tapatalk

 

[bubbl]

AW: Bluescreen

Neu flashen

 

[murruck]

AW: Bluescreen

Echt jetzt?!? kann ich nicht via FTP das Problem beheben?

Was ist denn passiert?


Gesendet von meinem iPhone mit Tapatalk

 

[bubbl]

AW: Bluescreen

Ist ein Imageplatzer
Hast zu viel instalieren wollen

 

[murruck]

AW: Bluescreen

verdammt!!!

Gibt's einen Rat, damit das nicht noch einmal passieren kann?!

Was heißt zu viel?
Wo liegt die Grenze?


Gesendet von meinem iPhone mit Tapatalk

 

[bubbl]

AW: Bluescreen

Du kannst im Menü nachschauen wieviel Speicher noch frei ist
Unter Einstellung System glaub
Nach instalation jeder Erweiterung einfach dort nachschauen

Bei ca 80% aufhören etwas zu instalieren

 

[murruck]

AW: Bluescreen

1ooo Dank für die schnelle Antwort!

Dann beginne ich mal von vorn

Grüße!


Gesendet von meinem iPhone mit Tapatalk

 

[McMighty]

Bei der Quad+ Zuviel installiert? Das kann kaum möglich sein. Die hat 256MB Flashspeicher. Selbst XPicons kann man einfach so auf die Box werfen.
Einfach per FTP auf die Box und das Plugin, dass den Fehler verursacht löschen. Ganz easy...

 

[murruck]

AW: Bluescreen

okaaaay

Und welches ist es? Kannst du das aus dem Fehlerbild erkennen??

Wo genau liegen die Plugins?


Gesendet von meinem iPhone mit Tapatalk

 

[McMighty]

AW: Bluescreen

Der Bluescreen sagt nicht viel aus. Da musst Du den Crashlog mal hier posten.

 

[murruck]

AW: Bluescreen

unter Home/root/logs ??


Gesendet von meinem iPhone mit Tapatalk

 

[bubbl]

AW: Bluescreen

Im Bluescreen kann man den Fehler nicht sehen
Kann auch eine Erweiterung gewesen sein die nicht passte

 

[McMighty]

AW: Bluescreen

Hast Du eine Festplatte verbaut? Da speichert es den Log ab. Sonst meine ich direkt im Root Verzeichnis

 

[murruck]

AW: Bluescreen

verbaut keine - aber gemountet und als HDD Ersatz


Gesendet von meinem iPhone mit Tapatalk

- - - - - - - - - -

Das habe ich gefunden:

<?xml version="1.0" encoding="utf-8"?>
<openATV>
<enigma2>
<crashdate>Sa Jan 2 22:51:58 2016</crashdate>
<compiledate>Jan 2 2016</compiledate>
<contactemail>forum at www.opena.tv</contactemail>
<!-- Please email this crashlog to above address -->
<skin>MetrixHD/skin.xml</skin>
<sourcedate>2016-01-01</sourcedate>
<version>3.0.0</version>
</enigma2>
<image>
<stbmodel>gigablue</stbmodel>
<kernelversion>
<![CDATA[
Linux gbquadplus 4.0.1 #1 SMP Mon Dec 21 19:25:01 CET 2015 mips GNU/Linux
]]>
</kernelversion>
<kernelcmdline>ubi.mtd=rootfs rootfstype=ubifs root=ubi0:rootfs bmem=192M@64M bmem=256M@512M console=ttyS0,115200n8</kernelcmdline>
<nimsockets>NIM Socket 0:</nimsockets>
<imageversion>
<![CDATA[
box_type=gbquadplus
build_type=0
version=5.1
build=0
date=20151224054407
comment=openATV
target=9
creator=openATV
url=http://www.opena.tv
catalog=http://www.opena.tv
]]>
</imageversion>
<imageissue>
<![CDATA[
Welcome to openATV for %h
openatv 5.1 %h


]]>
</imageissue>
</image>
<crashlogs>
<enigma2crashlog>
<![CDATA[
ponents/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:51.652 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:51.652 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:51.653 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:51.653 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:51.653 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:51.654 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:51.654 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:51.654 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:51.654 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:51.798 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:51.800 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:52.093 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:52.094 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:52.095 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.095 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.095 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.096 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.096 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.096 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.096 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.097 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.097 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.097 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.291 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:52.293 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:52.449 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
22:51:52.451 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
22:51:52.452 { } Components/ActionMap.py:46 action action -> pcfsKeyActions ok
22:51:52.598 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
22:51:52.600 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
22:51:52.987 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:52.989 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:52.989 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.989 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.990 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.990 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.990 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.990 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.991 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.991 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:52.991 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:52.991 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.578 [ ] driver/rcinput.cpp:23 handleCode 2 6c 1
22:51:53.579 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 2 KEY_DOWN DOWN
22:51:53.580 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.580 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.580 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.580 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.581 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.581 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.581 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.581 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.582 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.582 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.686 [ ] driver/rcinput.cpp:23 handleCode 2 6c 1
22:51:53.688 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 2 KEY_DOWN DOWN
22:51:53.688 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.689 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.689 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.689 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.689 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.690 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.690 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.690 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.690 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.691 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.794 [ ] driver/rcinput.cpp:23 handleCode 2 6c 1
22:51:53.796 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 2 KEY_DOWN DOWN
22:51:53.796 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.797 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.797 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.797 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.797 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.798 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.798 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.798 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.798 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:53.799 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:53.943 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:53.945 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:54.187 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
22:51:54.188 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
22:51:54.189 { } Components/ActionMap.py:46 action action -> pcfsKeyActions ok
22:51:54.386 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
22:51:54.388 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
22:51:54.823 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:54.825 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:54.825 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:54.826 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:54.826 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:54.826 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:54.826 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:54.827 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:54.827 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:54.827 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:54.827 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:54.828 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:54.972 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:54.974 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:55.185 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:55.186 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:55.187 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:55.187 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:55.187 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:55.188 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:55.188 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:55.188 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:55.188 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:55.189 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:55.189 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:55.189 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:55.383 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:55.385 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:55.517 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
22:51:55.519 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
22:51:55.519 { } Components/ActionMap.py:46 action action -> pcfsKeyActions ok
22:51:55.978 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
22:51:55.979 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
22:51:56.749 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:56.750 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:56.751 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:56.752 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:56.752 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:56.752 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:56.753 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:56.753 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:56.753 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:56.753 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:56.754 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:56.754 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:56.947 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:56.949 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:57.020 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:57.021 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:57.022 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:57.022 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:57.022 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:57.023 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:57.023 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:57.023 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:57.023 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:57.024 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:57.024 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:57.024 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:57.218 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:57.220 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:57.360 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
22:51:57.361 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
22:51:57.362 { } Components/ActionMap.py:46 action action -> pcfsKeyActions ok
22:51:57.559 [ ] driver/rcinput.cpp:23 handleCode 0 160 1
22:51:57.561 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
22:51:58.123 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:58.125 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:58.126 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.126 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.126 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.126 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.127 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.127 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.127 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.127 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.128 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.128 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.322 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:58.324 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:58.410 [ ] driver/rcinput.cpp:23 handleCode 1 6c 1
22:51:58.412 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 0 KEY_DOWN DOWN
22:51:58.412 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.412 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.413 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.413 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.413 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.413 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.414 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.414 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.414 { } Components/ActionMap.py:46 action action -> pcfsKeyActions down
22:51:58.414 { W } Components/ActionMap.py:53 action unknown action pcfsKeyActions/down! typo in keymap?
22:51:58.717 [ ] driver/rcinput.cpp:23 handleCode 0 6c 1
22:51:58.719 { } Screens/InfoBarGenerics.py:204 actionA KEY: 108 1 KEY_DOWN DOWN
22:51:58.769 [ ] driver/rcinput.cpp:23 handleCode 1 160 1
22:51:58.771 { } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
22:51:58.771 { } Components/ActionMap.py:46 action action -> pcfsKeyActions ok
22:51:58.784 { D } Traceback (most recent call last):
22:51:58.784 { D } File "/usr/lib/enigma2/python/Components/ActionMap.py", line 48, in action
22:51:58.785 { D } File "/usr/lib/enigma2/python/Plugins/Extensions/PictureCenterFS/plugin.py", line 669, in KeyOk
22:51:58.786 { D } AttributeError: 'PictureCenterFS7' object has no attribute 'videoplay'
22:51:58.787 [ E ] python/python.cpp:209 call (PyObject_CallObject(<bound method HelpableActionMap.action of <Components.ActionMap.HelpableActionMap instance at 0x6e3d0328>>,('pcfsKeyActions', 'ok')) failed)
]]>
</enigma2crashlog>
</crashlogs>
</openATV>

 

[McMighty]

AW: Bluescreen

Bitte in Spoilern setzen!
Das Plugin "PictureCenterFS" ist wohl Schuld. Den Ordner mal löschen