Ergebnis 11 bis 20 von 40
-
04.10.2019, 16:36 #11
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.463
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 420
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
ThemenstarterBox 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOHi again,
because I was bored at home , so I did a RJ12/RJ11 connector adapter to a DB9 connector for my Vu+ device. Connected to PC with the null-modem serial cable.
When Enigma remains frozen while trying to start (via "init 4 && sleep 10 && init 3"), the PUTTY serial terminal shows the following:
Code:INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal [VID]: VIDEO_STOP 1 1 [AUD]: AUDIO_STOP 0 [AUD]: AUDIO_CONINUE 0 0 aph=0x0 [AUD]: AUDIO_CONTINUE aph=0 0 0 INIT: Switching to runlevel: 3 Starting system message bus: dbus-daemon[7966]: Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file dbus. killall: showiframe: no process killed [VID]: VIDEO_SET_STREAMTYPE 0 [VID]: VIDEO_SELECT_SOURCE 1 0 [VID]: VIDEO_PLAY 1 2 0 [VID]: VIDEO_CONTINUE 1 1 [VID]: VIDEO_CLEAR_BUFFER 1 1 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 vm.dirty_writeback_centisecs = 300 vm.dirty_background_ratio = 1 vm.min_free_kbytes = 8192 vm.dirty_ratio = 60 vm.swappiness = 30 [VID]: VIDEO_STOP 0 1 [VID]: VIDEO_SELECT_SOURCE 0 0 /usr/bin/enigma2.sh: line 149: 7986 Killed LD_PRELOAD=$LIBS /usr/bin/enigma2 --debug-no-color $VERBOSE &> ${LOGFOLDER}Enigma2-debug-$(date +%Y%m%d_%H-%M-%S)${RANDOMIZE1970}.log killall: showiframe: no process killed enigma2 is the main pvr application... adjust oom score! /usr/bin/enigma2.sh: line 123: /proc//oom_adj: Permission denied [VID]: VIDEO_SET_STREAMTYPE 0 [VID]: VIDEO_SELECT_SOURCE 1 0 [VID]: VIDEO_PLAY 1 2 0 [VID]: VIDEO_CONTINUE 1 1 [VID]: VIDEO_CLEAR_BUFFER 1 1 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 vm.dirty_writeback_centisecs = 300 vm.dirty_background_ratio = 1 vm.min_free_kbytes = 8192 vm.dirty_ratio = 60 vm.swappiness = 30 [VID]: VIDEO_STOP 0 1 [VID]: VIDEO_SELECT_SOURCE 0 0 enigma2 is the main pvr application... adjust oom score!
Code:/usr/bin/enigma2.sh: line 123: /proc//oom_adj: Permission denied
The $PID was not determined because the "enigma2" process did not start. I don't know why the "enigma2" process is not running.
The second incomprehensible problem: (I'm just guessing of course)
Code:enigma2 is the main pvr application ... adjust oom score!
Third point of interest in LOG:
Code:/usr/bin/enigma2.sh: line 176: 1200 Killed LD_PRELOAD=$LIBS /usr/bin/enigma2 --debug-no-color $VERBOSE &> ${LOGFOLDER}Enigma2-debug-$(date +%Y%m%d_%H-%M-%S)${RANDOMIZE1970}.log
/////////////////////////// EDIT 1:
And here is the LOG when Enigma successfully starts (via "init 4 && sleep 10 && init 3"):
Code:INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal [VID]: VIDEO_STOP 1 1 [AUD]: AUDIO_STOP 0 [AUD]: AUDIO_CONTINUE 0 0 aph=0x0 [AUD]: AUDIO_CONTINUE aph=0 0 0 INIT: no more processes left in this runlevel INIT: Switching to runlevel: 3 Starting system message bus: dbus-daemon[950]: Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file dbus. killall: showiframe: no process killed [VID]: VIDEO_SET_STREAMTYPE 0 [VID]: VIDEO_SELECT_SOURCE 1 0 [VID]: VIDEO_PLA 1 2 0 [VID]: VIDEO_CONTINUE 1 1 [VID]: VIEO_CLEAR_BUFFER 1 1 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 vm.dirty_writeback_centisecs = 300 vm.dirty_background_ratio = 1 vm.min_free_kbytes = 8192 vm.dirty_ratio = 60 vm.swappiness = 30 [VID]: VIDEO_STOP 0 1 [VID]: VIDEO_SELECT_SOURCE 0 0 enigma2 is the main pvr application... adjust oom score! UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16 [AUD]: AUDIO_SET_MUTE 0 [AUD]: AUDIO_SET_MIXER -854385160 [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0 [AUD]: AUDIO_SET_MIXER : next left volume -1352, right volume -1352 [AUD]: AUDIO_SET_MIXER : next left volume -210, right volume -210 [AUD]: AUDIO_SET_MIXER -854385160 [AUD]: AUDIO_SET_MIXER : amixl 16, amixr 16 [AUD]: AUDIO_SET_MIXER : next left volume -210, right volume -210 [AUD]: AUDIO_SET_MIXER : next left volume -1352, right volume -1352 [AUD]: AUDIO_SELECT_SOURCE 0 [AUD]: AUDIO_SET_BYPASS_MODE 1 [AUD]: downmix 0 state : 0 [AUD]: AUDIO_PAUSE 0 [AUD]: AUDIO_PLAY 0 decoder start : 0 [VID]: VIDEO_SELECT_SOURCE 0 0 [VID]: VIDEO_GET_SIZE src w: 1280 h:720 display w:1280 h:720 [VID]: VIDEO_GET_SIZE aspect: 1 3 [VID]: VIDEO_SET_STREAMTYPE 1 [VID]: VIDEO_FREEZE 0 0 [VID]: VIDEO_PLAY 0 5 2 [VID]: VIDEO_SLOWMOTION 0 1 [VID]: VIDEO_FAST_FORWARD 0 1 [VID]: VIDEO_CONTINUE 0 1 [AUD]: AUDIO_CONTINUE 0 1 aph=0xca8c1480 [AUD]: Mute : 0 [AUD]: AUDIO_CHANNEL_SELECT 0
/////////////////////////// EDIT 2:
A copy from the terminal when I try to run an Enigma that is already "frozen" (via "init 4 && sleep 10 && init 3"):
Again there is the same problem - ie the path to the object "oom_adj" in the appropriate directory.
Then there are of course more "enigma2" processes. So also some associated PIDs for the "enigma2" process. Therefore, the $PID variable is populated with multiple numbers separated by spaces, and this cannot be used as a directory name.
Code:INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal INIT: Switching to runlevel: 3 Starting system message bus: dbus-daemon[2613]: Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file dbus. killall: showiframe: no process killed [VID]: VIDEO_SET_STREAMTYPE 0 [VID]: VIDEO_SELECT_SOURCE 1 0 [VID]: VIDEO_PLAY 1 2 0 [VID]: VIDEO_CONTINUE 1 1 [VID]: VIDEO_CLEAR_BUFFER 1 1 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 vm.dirty_writeback_centisecs = 300 vm.dirty_background_ratio = 1 vm.min_free_kbytes = 8192 vm.dirty_ratio = 60 vm.swappiness = 30 [VID]: VIDEO_STOP 0 1 [VID]: VIDEO_SELECT_SOURCE 0 0 enigma2 is the main pvr application... adjust oom score! /usr/bin/enigma2.sh: line 123: [: /proc/2633: binary operator expected /usr/bin/enigma2.sh: line 123: /proc/2633 2564/oom_adj: No such file or directory
Geändert von s3n0 (06.10.2019 um 15:30 Uhr)
-
Danke - 1 Thanksjackslater bedankten sich
-
Advertising
-
15.10.2019, 22:10 #12
- Registriert seit
- 23.05.2015
- Beiträge
- 40
- Thanks (gegeben)
- 15
- Thanks (bekommen)
- 1
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Vu+ Solo SE V2Box 2:Vu+ SoloI really hope this gets fixed.
I noticed the problem happens not only during GUI reboot but also during full reboot (and even after I turn it off using the switch button on the back).
-
15.10.2019, 22:47 #13
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.463
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 420
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
ThemenstarterBox 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOYes, the same for me, unfortunately sometimes even when booting set-top-box does not start Enigma - i.e. that will remain stuck when booting. Then I have to use "reboot" in Shell again. It has also happened to me that she did not boot Enigma twice in a row and booted up to the third attempt.
-
16.10.2019, 06:28 #14
- Registriert seit
- 03.04.2013
- Beiträge
- 14.861
- Thanks (gegeben)
- 763
- Thanks (bekommen)
- 21093
- Total Downloaded
- 162,47 MB
- Total Downloaded
- 162,47 MB
at the moment i have no free time but soon i must check openatv 6.4 for this model i take a look
openATV we are open Source
Boykott GPL violator
-
Danke - 3 Thanks
-
11.11.2019, 01:43 #15
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.463
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 420
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
ThemenstarterBox 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOHello.
I just found one fact. When I back up and delete the "/etc/enigma2/settings" file - that means I will do OpenATV Enigma "Factory Reset", then all "quick reboots" of OpenATV-6.3 Enigma are OK !
I played with it a bit. I returned my backed "settings" file to OpenATV.
The only thing I found out is that if I delete all the "MyMetrixLite" entries from the "/etc/enigma2/settings" file, the "quick reboots" are going well.
If so, it could mean that the problem is in the MyMetrixLite Configurator or directly in the Metrix SKIN when booting OpenATV.
Code:init 4 cp /etc/enigma2/settings /etc/enigma2/settings___backup_`date '+%Y-%m-%d_%H-%M'` # making a backup sed -i '/config\.plugins\.MyMetrixLite/d' /etc/enigma2/settings # deleting all lines containing the string 'config.plugins.MyMetrixLite' init 3
Code:for x in {1..20}; do init 4; sleep 5; init 3; echo "$x --- waiting 40 secs"; sleep 40; done;
However, yesterday, when I added my color configuration through the MyMetrixLite plugin, quick restarts didn't work anymore (Enigma remained frozen after about 3-7 reboots). Enigma quick restarts worked smoothly (20 x quick restarts without problems) only if I deleted "MyMetrixLite" in the "settings" file.
Of course, I used the green button on RCU to apply new settings of MyMetrixLite plugin + then again green button to save the settings + restart Enigma. Twenty reboots went without problems today. I really don't know where the fault is.
There will probably be some combination of SKIN settings. I had set the colors and weather (city) in MyMetrixLite plugin. Then I switched the SKIN resolution in MyMetrixLite from HD to FullHD, restarted and immediately freezed OpenATV during the first "quick restart".
The fact is that removing "MyMetrixLite" all items from the "settings" file will help.Geändert von s3n0 (11.11.2019 um 12:59 Uhr)
-
Danke - 1 Thanksjackslater bedankten sich
-
14.11.2019, 22:04 #16
- Registriert seit
- 23.05.2015
- Beiträge
- 40
- Thanks (gegeben)
- 15
- Thanks (bekommen)
- 1
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Vu+ Solo SE V2Box 2:Vu+ SoloYou are doing a great work to solve this issue. Thank you once again!
The strange part is that after you added your color configuration in MyMetrixLite plugin it started to fail again. Do you mean you added a previously saved config from the save/restore option, right?
In this case maybe there is one specific line causing the issue.
I have a lot of lines from mymetrix in my config, I can share here:
Code:config.plugins.MyMetrixLiteColors.backgroundtextborderwidth=0 config.plugins.MyMetrixLiteColors.epgeventdescriptionbackground=151515 config.plugins.MyMetrixLiteColors.epgeventdescriptionbackgroundtransparency=34 config.plugins.MyMetrixLiteColors.epgeventselectedbackground=1BA1E2 config.plugins.MyMetrixLiteColors.epgeventselectedbackgroundtransparency=34 config.plugins.MyMetrixLiteColors.infobarprogress=1BA1E2 config.plugins.MyMetrixLiteColors.layeraprogress=1BA1E2 config.plugins.MyMetrixLiteColors.layerbbackground=151515 config.plugins.MyMetrixLiteColors.layerbbackgroundtransparency=34 config.plugins.MyMetrixLiteColors.layerbprogress=27408B config.plugins.MyMetrixLiteColors.layerbprogresstransparency=34 config.plugins.MyMetrixLiteColors.layerbselectionbackground=27408B config.plugins.MyMetrixLiteColors.layerbselectionbackgroundtransparency=34 config.plugins.MyMetrixLiteFonts.Arial_scale=100 config.plugins.MyMetrixLiteFonts.Console_scale=100 config.plugins.MyMetrixLiteFonts.epgevent_scale=95 config.plugins.MyMetrixLiteFonts.epginfo_scale=95 config.plugins.MyMetrixLiteFonts.epgtext_scale=95 config.plugins.MyMetrixLiteFonts.Fixed_scale=100 config.plugins.MyMetrixLiteFonts.globalbutton_scale=90 config.plugins.MyMetrixLiteFonts.globalclock_scale=100 config.plugins.MyMetrixLiteFonts.globallarge_scale=60 config.plugins.MyMetrixLiteFonts.globalmenu_scale=100 config.plugins.MyMetrixLiteFonts.globalsmall_scale=95 config.plugins.MyMetrixLiteFonts.globaltitle_scale=100 config.plugins.MyMetrixLiteFonts.infobarevent_scale=95 config.plugins.MyMetrixLiteFonts.infobartext_scale=95 config.plugins.MyMetrixLiteFonts.Lcd_scale=100 config.plugins.MyMetrixLiteFonts.Meteo_scale=100 config.plugins.MyMetrixLiteFonts.Regular_scale=95 config.plugins.MyMetrixLiteFonts.RegularLight_scale=95 config.plugins.MyMetrixLiteFonts.Replacement_scale=100 config.plugins.MyMetrixLiteFonts.screeninfo_scale=100 config.plugins.MyMetrixLiteFonts.screenlabel_scale=95 config.plugins.MyMetrixLiteFonts.screentext_scale=95 config.plugins.MyMetrixLiteFonts.SetrixHD_scale=100 config.plugins.MyMetrixLiteOther.channelSelectionStyle=CHANNELSELECTION-2 config.plugins.MyMetrixLiteOther.EHDfontoffset=0 config.plugins.MyMetrixLiteOther.EHDtested=vusolose_|_01 config.plugins.MyMetrixLiteOther.layeraunderlineposy=0 config.plugins.MyMetrixLiteOther.layeraunderlinesize=1 config.plugins.MyMetrixLiteOther.runningTextSpeed=900 config.plugins.MyMetrixLiteOther.runningTextStartdelay=1500 config.plugins.MyMetrixLiteOther.setFieldMargin=5 config.plugins.MyMetrixLiteOther.setItemDistance=5 config.plugins.MyMetrixLiteOther.showChannelListRunningtext=true config.plugins.MyMetrixLiteOther.showChannelNumber=false config.plugins.MyMetrixLiteOther.showCPULoad=false config.plugins.MyMetrixLiteOther.showExtended_caid=false config.plugins.MyMetrixLiteOther.showExtendedinfo=true config.plugins.MyMetrixLiteOther.showInfoBarRunningtext=true config.plugins.MyMetrixLiteOther.showMovieName=false config.plugins.MyMetrixLiteOther.showOrbitalposition=false config.plugins.MyMetrixLiteOther.showSTBinfo=true config.plugins.MyMetrixLiteOther.SkinDesignButtonsFrameSize=0 config.plugins.MyMetrixLiteOther.SkinDesignButtonsTextPosition=0 config.plugins.MyMetrixLiteOther.SkinDesignButtonsTextSize=24 config.plugins.MyMetrixLiteOther.SkinDesignInfobarXPiconPosX=0 config.plugins.MyMetrixLiteOther.SkinDesignInfobarXPiconPosY=0 config.plugins.MyMetrixLiteOther.SkinDesignInfobarZZZPiconPosX=0 config.plugins.MyMetrixLiteOther.SkinDesignInfobarZZZPiconPosY=0 config.plugins.MyMetrixLiteOther.SkinDesignInfobarZZZPiconSize=0 config.plugins.MyMetrixLiteOther.SkinDesignScrollbarBorderWidth=1 config.plugins.MyMetrixLiteOther.SkinDesignScrollbarSliderWidth=10 config.plugins.MyMetrixLiteOther.STBDistance=10
If you enable another skin and leave the mymetrix entries in the config file, does it work fine?
-
15.11.2019, 10:37 #17
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.463
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 420
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
ThemenstarterBox 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBONo, I meant adding colors one by one after deleting all MyMetrixLite settings from the "/etc/enigma2/settings" file. It seems that most problems with fast rebooting of Enigma will be caused by adding FullHD resolution in combination with adding some colors.
Specifically, I set these colors in my configuration:
- channel list - font color for events
- channel list - font color for event under cursor
- graphical EPG - background of all event shelves in current time
- graphical EPG - background color under the current zapped channel logo
In my opinion, it does not matter which colors I set. The problem will probably be somewhere in MyMetrixLite plugin or MetrixHD SKIN. Not in the specific colors I want to set.
Still, if I delete all MyMetrixLite settings (...Fonts ; ...Colors ; ...Other) from the "settings" file (as I mentioned above), then quick restarts work without any problems.Geändert von s3n0 (15.11.2019 um 10:43 Uhr)
-
Danke - 1 Thanksjackslater bedankten sich
-
01.12.2019, 15:18 #18
- Registriert seit
- 23.05.2015
- Beiträge
- 40
- Thanks (gegeben)
- 15
- Thanks (bekommen)
- 1
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Vu+ Solo SE V2Box 2:Vu+ SoloHi s3n0, I removed all the "MyMetrixLite" entries from the "/etc/enigma2/settings" file by using your script, and I confirm that the reboot works normally.
One thing I noticed is that the issue happens even if you have another skin active, instead of MyMetrix.So it just depends on what is in the "settings" file, and not on what skin is actually loaded.
-
01.12.2019, 19:32 #19
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.463
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 420
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
ThemenstarterBox 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBORather, I would guess the problem on too much MetrixHD SKIN settings . For example, if I just set the colors or just change the resolution of the SKIN to FHD and do nothing else, then it works pretty cool. However, if there is a change in color adjustments for SKIN and also I change the resolution and also something else, then there is a problem when restarting the Enigma (after 1x to 10x fast reboots, the Enigma hangs).
Currently I am still using SKIN MetrixHD without my own settings, so I have the default SKIN setting there, and a quick restart is without freezing the Enigma.
-
11.12.2019, 19:43 #20
- Registriert seit
- 29.08.2017
- Beiträge
- 5
- Thanks (gegeben)
- 0
- Thanks (bekommen)
- 0
- Total Downloaded
- 0
- Total Downloaded
- 0
Hi all, I am experiencing the exactly same problem with 6.3.
Like you, I was using "MetrixHD" Skin.
I have de-installed the skin and all its contents and whipped the corresponding settings with "sed -i '/config\.plugins\.MyMetrixLite/d' /etc/enigma2/settings ".
For me, this does not help. I've got still failed boots (3 out of 6 or so?)
I dont know how to go ahead with debugging this issue... I want to avoid to do a complete re-installation of the box. But I am stuck.
Can somebody help out?
Regards,
Matthias
Lesezeichen