s3n0

Enigma2 uses the so-called "plugins" and not "addons".

Addons are inserted (added), for example, in a web browser, or in the KODI multimedia interface, etc.

For Enigma2, you need to get a ".zip" archive that also contains a "plugin.py/.pyo" file... or need to get an .ipk installation package.

 

Go into plugin menu select the plugin and press the red button to suppress it.

the problem is that I don't see it on the list of installed plugins

 

So first try to check if the plugin is actually installed via opkg management:

opkg update
opkg list-installed | grep vfdcontrol

If you see the plugin in the list, then just uninstall it, as I wrote above. The likely package name is "enigma2-plugin-systemplugins-vfdcontrol" as @Pr2 wrote. If the name of the package is any other, use this other name.

opkg remove <package_name>

init 4; sleep 5; sed -i '/config\.misc\.startCounter/d' /etc/enigma2/settings; init 3

 

Please zip and attach it.

splash.zip

 

Hi. In the case of the Zgemma H8.* devices, it's not good. The "splash.bin" file should be in the "h8" folder... if I'm not mistaken . So it should be "/h8/splash.bin".

Hi.

Tell me why you use dist-upgrade in Linux-Shell.

A safer way is... update the Enigma2 (OpenPLi) and its packages only. Not a Linux distribution in a set-top box (system packages). The system is in danger of crashing then.

It is safer to back up all data (required plugins and configuration files) + then completely overwrite the entire firmware with the new version + restore the backed up data (required plugins and configuration files).

The safest way is to update the Enigma2 (all its packages and modules), but you should also do this regularly (1x per week), because otherwise some packages may be left behind (no ascending update / out of date / incomplete):

init 4
opkg update
opkg upgrade
reboot

As @WanWizard wrote before me - the right question is how did you turn off your set-top box. Do you mean the power switch on the set-top box ? Or did you simply switch the set-top box to standby mode with the help of the RCU (with the help of Enigma2 / GUI) ? Or another way to turn it off - for example, through a terminal connection or through the OpenWebif interface ?

It also depends on what or what style you have edited your list of favorite channels. Did you edit this channel list directly in Enigma2 / GUI, with the help of RCU ? If so, this list is saved only during certain events. Otherwise, the list remains only in the data area of the Enigma2 memory, but not on the internal disk. If I'm not mistaken, only when you use the standby mode of the set-top box, only then is the modified list of your channels saved on the internal disk.

What do you mean by "thanks" ?

Write how you proceeded... or what exactly you want advice on - helping with some app ? editing files in a text editor ? or what exactly you want help with ?

Or have you already solved it ?

And this wouldn't work ? - https://forums.openp...e-2#entry309825

I don't have time to look at the current OpenPLi source code right now, but maybe it's already fixed... so that after deleting the unnecessary .po files (language translation) as well as .png files (country flag), the OpenPLi system doesn't crash.

Normally, it would be enough to delete unnecessary languages from:
/usr/share/enigma2/po/ --- for languages
/usr/share/enigma2/skin_default/countries/ --- for flags
...but then probably OpenPLi won't boot... from what I've read in other discussions on the internet. So I don't know if the OpenPLi code has already been modified so that it doesn't freeze after deleting the mentioned files.

BTW, when I searched the OpenPLi discussion forum, there are a lot of questions about deleting unnecessary language translations. However, OpenPLi has language translations hardwired into the code. It is therefore necessary to modify the entire code (if it still hasn't happened) so that OpenPLi does not freeze, after deleting unnecessary translation files (.po) and also images with flags (.png).

Yes. "Init.d" script is not a standard script, but a script that requires input argument processing. In the case of Enigma2 distributions in lightweight Linux systems, at least the following arguments (parameters) are used:

start | stop | restart

The "start" argument is sent to the "init.d" script when a specific service run through init.d is starting (for example, when booting a Linux system).

The "stop" argument is invoked when the Linux system reboots / shuts down. Therefore, these basic arguments (parameters) must be captured there.

In some cases, the return value (error code) from the "init.d" script also plays an important role ! Be careful, don't confuse it with the "status" arguments for the init.d script. If "status" argument is requested through some "init.d" script, then the return values represent the "status code" of the service, and they are different codes than in the case of "exit code".

Many additional arguments for "init.d" scripts, in the case of Enigma2 set top boxes, are not needed or are not implemented (it varies depending on which Linux system is used and whether it is a light version or a full version of the Linux system).

You can find more information on the internet... for example, here:

https://refspecs.lin...niscrptact.html

https://www.novell.c...ml/ch13s04.html

With some script-examples:

https://bash.cyberci...ide//etc/init.d

https://unix.stackex...d-start-at-boot

Ok
But usr/script I can't find it!

Inviato dal mio SM-G990B utilizzando Tapatalk

Hi.

You can use my universal softcam "init.d" script ... if you really can't find it in the IPK package .

CODE: https://github.com/s.../master/softcam

RAW: https://github.com/s.../master/softcam

In my script, you have to modify several variables (they are located at the beginning of the script, after the instructions) - for the NCam.

Edit the name of the binary file according to the one you have in the /usr/bin folder - probably ncam (instead of oscam). So in my softcam script you modify the binary name variable (BINFILENAME), so that it refers to the binary name "ncam" instead of "oscam".

Do not forget to assign startup attributes (chmod a+x /directory-path/file). For binary file (in the /usr/bin folder) and also for the script (in the /etc/init.d folder)

Ncam uses the default configuration directory /var/tuxbox/config and not /etc/tuxbox/config/oscam. If you want to change the default configuration directory, then you use an additional argument in the adjustable parameters (BINARGS) in my softcam script:

BINARGS="-b -r 2"

...to the following (as example):

BINARGS="-b -r 2 -c /etc/tuxbox/config/ncam"

NCam also uses ncam.* configuration file names (e.g. ncam.conf) rather than OScam's oscam.* (e.g. oscam.conf).

How to install the softcam script is stated directly in the guide - inside the softcam script, at its beginning.

The name of the script-file in the /etc/init.d folder, I recommend renaming it from softcam to softcam.NCam and activating / running it via Enigma2 / GUI. Another symbolic link to /etc/init.d/softcam will then be created, and you do not have to create a "run-level" launcher according to the instructions in my script - by creating a special symbolic link to the /etc/rc3.d folder.

Hi all.

The guy had OpenATV installed and this Enigma2 (this OpenATV) unfortunately overwrites the original Splash Screen with a new one, produced in the OpenATV team.

But that doesn't mean we can't help this guy . There is a problem with the set-top box, not with the Enigma2 itself.

In the case of my Vu+ Solo SE V2, I can't use 720x576 resolution because the bootloader doesn't read this image size. I don't know why I have to use a resolution of 720 x 480 and consequently, this image is automatically stretched to a different resolution.

I haven't detected a bootloader algorithm principle, but it's probably checking the correct file size. If it is incorrect, it will not be displayed at all. If the file was smaller (850 kB), it was not displayed at all. Instead of a splash-screen, I only saw a black screen. However, if the image was around 980 kB - 1100 kB, then it worked.

Step by step:

1. you need a BMP-image (.bmp file)
2. it should have 720x480 resolution and 24 bit colors (RGB = 3 x 8 bit, no "Alpha" byte)
3. when the BMP image is ready, it must be renamed to the file name "splash_cfe_auto.bin"
4. copy the file to a USB key (FAT32 formatted) in the following folder, depending on the shortcut name of your set-top box:

"/vuplus/your_box/"
(example: "/vuplus/solose/splash_cfe_auto.bin")

A note:

Of course, just use this one splash....bin file ! Do not use the firmware file ! Otherwise, the entire firmware would flash into the set-top box again .
5. You can now flash your set-top box from the USB key as usual when flashing the set-top box

If you want ... you can try my boot splash-screen. Unfortunately, my original Vu+ splash was also deleted / replaced when flashing the OpenATV image. Therefore, I use this alternative (new) logo for my Vu+ device. BTW, the directory on the USB key, must be renamed according to your set-top-box name.

Exactly so.

Enigma2 usually takes into account and checks the script files /etc/init.d/softcam and /etc/init.d/softcam.<softcam-name>

The original "init.d" script apparently changed during the Enigma2-OpenPLi update. If you use Oscam installed as an IPK from the OpenPLi feed server, then with the new Oscam version, this softcam script will also be overwritten (or will be added) as the new updated "init.d" softcam script.

So... the new "init.d" script will be added to Enigma2 again, after Enigma2 updating, and there will be two "init.d" softcam scripts (one of your own and one original after its update), for the same Oscam.

It would be better to use the manual Softcam installation method. Do not use the IPK package to install Softcam. And you will solve your problem. See also my instructions, in my softcam script: https://github.com/s3n0/e2scripts (because I don't want to describe the whole thing here again ... sorry). In this case, you don't even have to rename this file ... you can leave the name "softcam". It will not be updated by Enigma2 and therefore will not be overwritten by a new - ie updated script.

It can be installed... normally you can install the original OpenWebif from the GitHub server.

As the first, when Enigma2 is stopped (which you stop with the init 4 command in the linux shell), you need to uninstall the OpenWebif - through the package manager (opkg in the linux shell). Then, through the package manager, you will disable updates from the feed (opkg flag hold enigma2-plugin-extensions-openwebif), just for this OpenWebif, so that your new OpenWebif with updates from the Internet - from the OpenPLi source - will not be overwritten. And then you install / download the source code OR ipk package - the full version of OpenWebif. You can find the procedure directly on Github here: https://github.com/E...lugin-OpenWebif (scroll down with the mouse wheel).

But then there will no longer be 100% compatibility from the creator of the distribution of the specific Enigma2 (i.e. OpenPLi). For example, new OpenWebif may require an SSL library for 2022, but OpenPLi will still have the old SSL library from 2021. It is, of course, just a fictional possible example of incompatibility. Possible incompatibilities could occur elsewhere. Possibly at the next update sometime later (a year later).

Hi.

Do you mean Plugin-MENU in Enigma2-GUI ? How is it possible ? Did you do something ? I don't know the OpenPLi firmware very well, but it is possible that OpenWebif is a built-in component in the firmware and is not listed in the plugin list. Try using the package manager (opkg). Uninstall the entire OpenWebif and then install it again .

First of all, try this:

init 3     # stop the Enigma2
opkg update
opkg install --force-reinstall enigma2-plugin-extensions-openwebif
reboot

If does not work, then try the following procedure... however, it is a risky procedure... and you need to know what you're doing:

init 3    # stop the Enigma2
opkg update
opkg remove --force-remove enigma2-plugin-extensions-openwebif
opkg install --force-reinstall enigma2-plugin-extensions-openwebif
reboot

Which Enigma2 do you use ? The original Enigma2 OpenPLi image ? Isn't this a modified OpenPLi image ? There may have been a failure of feed server resources, as you do not see some packages (openwebif) in the Plugin-MENU.