Jump to content


Photo

Boot problem

support

  • Please log in to reply
8 replies to this topic

#1 pitbull82

  • Member
  • 5 posts

0
Neutral

Posted 24 August 2015 - 10:18

Hi!

 

I have a little problem  :blink:

 

I think it has something to do with a skin... The box wont boot up. Anyone that have any ideas?

 

As you see i am told to send a .txt file but to who?

 

Vu+ solo

 

//Pitbull

Attached Files

  • Attached File  1.jpg   125.79KB   3 downloads


Re: Boot problem #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 42,395 posts

+676
Excellent

Posted 24 August 2015 - 10:21

This looks like a bug in the skin, but not all is visible. And look looks like you don't have a disk in your box, since it writes the log to /tmp, which is erased when the box restarts.

 

If you have linux experience, you can login using telnet, kill off the enigma script (so it doesn't reboot anymore), and then edit the settings file to switch back to the default skin.


Many answers to your question can be found in our new and improved wiki.

Currently in active use: VU+Solo 4K (1xFBC, 2xS2), VU+Zero, Edision OS mini+, Amiko Viper 2TC, Zgemma H3.2TC, Zgemma H6

For testing purposes: XP1000, Formuler F1 (2xS2), Miraclebox Premium Micro (S2+C/T), ET7500 (S2), ET8500 (S2), Zgemma H2.H (S2+C), Zgemma H5.2TC, SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, HD2400 (4xS2), ET10000 (4xS2), VU+Duo2 (1xS2), Edision OS nino


Re: Boot problem #3 pitbull82

  • Member
  • 5 posts

0
Neutral

Posted 24 August 2015 - 10:29

This looks like a bug in the skin, but not all is visible. And look looks like you don't have a disk in your box, since it writes the log to /tmp, which is erased when the box restarts.

 

If you have linux experience, you can login using telnet, kill off the enigma script (so it doesn't reboot anymore), and then edit the settings file to switch back to the default skin.

 

 

Hi!

 

I had the box for 1 day so have no experience.. nieghter with linux.. but i have the log file. I took it out with ftp.. but is it safe to upload here? if it shows my setting in the box?

 

I have very good computing skills, is it hard to use telnet and fix the script?



Re: Boot problem #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 42,395 posts

+676
Excellent

Posted 24 August 2015 - 10:34

The logfile doesn't show any settings.

 

You could probably even edit with FTP if you have a good client. You need to edit the file "/etc/enigma2/settings".

 

In there look for a line that starts with "config.skin.primary_skin=". Change that line so it reads "config.skin.primary_skin=PLi-HD/skin.xml" (all without the quotes). Once saved it will boot up with the default skin again.


Many answers to your question can be found in our new and improved wiki.

Currently in active use: VU+Solo 4K (1xFBC, 2xS2), VU+Zero, Edision OS mini+, Amiko Viper 2TC, Zgemma H3.2TC, Zgemma H6

For testing purposes: XP1000, Formuler F1 (2xS2), Miraclebox Premium Micro (S2+C/T), ET7500 (S2), ET8500 (S2), Zgemma H2.H (S2+C), Zgemma H5.2TC, SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, HD2400 (4xS2), ET10000 (4xS2), VU+Duo2 (1xS2), Edision OS nino


Re: Boot problem #5 pitbull82

  • Member
  • 5 posts

0
Neutral

Posted 24 August 2015 - 10:36

alright, this is the file.. 

Attached Files



Re: Boot problem #6 WanWizard

  • Forum Moderator
    PLi® Core member
  • 42,395 posts

+676
Excellent

Posted 24 August 2015 - 10:40

[SKIN] Parsing embedded skin <embedded-in-'Screensaver'>
[Skin] SKIN ERROR in SecondInfoBar: Bad magic number in /usr/lib/enigma2/python/Components/Converter/ExtraTuner.pyo
[Skin] SKIN ERROR in ChannelSelection: Bad magic number in /usr/lib/enigma2/python/Components/Converter/ChannelSelectionExtraInfo.pyo
warning, skin is missing element key_yellow in <class 'Screens.ChannelSelection.ChannelSelection'>
warning, skin is missing element key_blue in <class 'Screens.ChannelSelection.ChannelSelection'>
EXCEPTION IN PYTHON STARTUP CODE:
------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 569, in <module>
    runScreenTest()
  File "/usr/lib/enigma2/python/mytest.py", line 459, in runScreenTest
    runNextScreen(session, screensToRun)
  File "/usr/lib/enigma2/python/mytest.py", line 453, in runNextScreen
    session.openWithCallback(boundFunction(runNextScreen, session, screensToRun[1:]), screen, *args)
  File "/usr/lib/enigma2/python/mytest.py", line 274, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 284, in open
    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 244, in doInstantiateDialog
    dlg = screen(self, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 65, in __init__
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 567, in __init__
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 251, in doInstantiateDialog
    dlg.applySkin()
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 112, in applySkin
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 30, in createGUIScreen
  File "/usr/lib/enigma2/python/Components/ServiceList.py", line 128, in applySkin
TypeError: 'NoneType' object is not iterable
------------------------------------------------------------
<   632.554563> [MAIN] (exit code 5)
]]>

Bad magic number means the skin you installed contains Python binaries that are for an old version of Python. So fix the settings and once you have a working box again, delete the Skin.

 

And next time be careful what you install from third parties, contrary to popular belief, not all images available for your box are the same...


Many answers to your question can be found in our new and improved wiki.

Currently in active use: VU+Solo 4K (1xFBC, 2xS2), VU+Zero, Edision OS mini+, Amiko Viper 2TC, Zgemma H3.2TC, Zgemma H6

For testing purposes: XP1000, Formuler F1 (2xS2), Miraclebox Premium Micro (S2+C/T), ET7500 (S2), ET8500 (S2), Zgemma H2.H (S2+C), Zgemma H5.2TC, SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, HD2400 (4xS2), ET10000 (4xS2), VU+Duo2 (1xS2), Edision OS nino


Re: Boot problem #7 pitbull82

  • Member
  • 5 posts

0
Neutral

Posted 24 August 2015 - 10:42

I did change the setting.txt and now it works perfect!  Thank you a lot!  :)  :D  :)



Re: Boot problem #8 pitbull82

  • Member
  • 5 posts

0
Neutral

Posted 24 August 2015 - 10:44

[SKIN] Parsing embedded skin <embedded-in-'Screensaver'>
[Skin] SKIN ERROR in SecondInfoBar: Bad magic number in /usr/lib/enigma2/python/Components/Converter/ExtraTuner.pyo
[Skin] SKIN ERROR in ChannelSelection: Bad magic number in /usr/lib/enigma2/python/Components/Converter/ChannelSelectionExtraInfo.pyo
warning, skin is missing element key_yellow in <class 'Screens.ChannelSelection.ChannelSelection'>
warning, skin is missing element key_blue in <class 'Screens.ChannelSelection.ChannelSelection'>
EXCEPTION IN PYTHON STARTUP CODE:
------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 569, in <module>
    runScreenTest()
  File "/usr/lib/enigma2/python/mytest.py", line 459, in runScreenTest
    runNextScreen(session, screensToRun)
  File "/usr/lib/enigma2/python/mytest.py", line 453, in runNextScreen
    session.openWithCallback(boundFunction(runNextScreen, session, screensToRun[1:]), screen, *args)
  File "/usr/lib/enigma2/python/mytest.py", line 274, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 284, in open
    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 244, in doInstantiateDialog
    dlg = screen(self, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 65, in __init__
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 567, in __init__
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 251, in doInstantiateDialog
    dlg.applySkin()
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 112, in applySkin
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 30, in createGUIScreen
  File "/usr/lib/enigma2/python/Components/ServiceList.py", line 128, in applySkin
TypeError: 'NoneType' object is not iterable
------------------------------------------------------------
<   632.554563> [MAIN] (exit code 5)
]]>

Bad magic number means the skin you installed contains Python binaries that are for an old version of Python. So fix the settings and once you have a working box again, delete the Skin.

 

And next time be careful what you install from third parties, contrary to popular belief, not all images available for your box are the same...

 

No more changes  :rolleyes:



Re: Boot problem #9 imtiaz_2007

  • Member
  • 2 posts

0
Neutral

Posted 12 July 2018 - 16:39

enigma 2 but perablam
HELP






Also tagged with one or more of these keywords: support

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users