Thema: GUI restart problems - possible problem with hardware drivers on Vu+ Solo SE V2 ?

Hi 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!

A possible first problem: (I'm just guessing of course)

Code:

/usr/bin/enigma2.sh: line 123: /proc//oom_adj: Permission denied

I just guess, I don't know what "/proc/$PID/oom_adj" is for. Something like setting up and controlling the amount of memory used by a particular process?

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!

There is also a 2 x line in the LOG: "enigma2 is the main pvr application ... adjust oom score!" which means that the script "/usr/bin/enigma2.sh" was run twice in a row for an unknown reason. Of course, at this point, 2 x PIDs will occur immediately, and the next error in the order is precisely those 2 x or more existing PIDs. The reported error concerns accessing a directory that does not exist because the $PID variable already contains two PIDs instead of one PID for the "enigma2" process.

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

I use DebugLOG enabled in OpenATV (enabled via GUI MENU). Could there be a problem in this view ? If the Enigma remains stuck on startup, the mentioned line above ("....LD_PRELOAD=....") also appears in the 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

Yes, 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.

at the moment i have no free time but soon i must check openatv 6.4 for this model i take a look

Hello.

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

I tested through a simple for-loop (via the Shell):

Code:

for x in {1..20}; do init 4; sleep 5; init 3; echo "$x --- waiting 40 secs"; sleep 40; done;

Um, or maybe there are not many items in the "settings" file to make Enigma's "quick restart" work . It's really hard to judge what causes problems. I did more tests and gradually added colors in MyMetrixLite, and then when everything worked. Later I added the weather settings (city). Both additions worked.

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.

Zitat von jackslater

You 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.

No, 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.

Zitat von jackslater

What about config.plugins.MetrixWeather items? Does removing/keeping them make any difference?
If you enable another skin and leave the mymetrix entries in the config file, does it work fine?

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.

Rather, 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.