s3n0

I sent it to you in a private message, because it is forbidden to distribute modified (unofficial) Oscam versions everywhere on discussion forums.

Hi. For Czech/Slovak - Skylink cards you need more. Unfortunately, for the new Irdeto Layer-2B encoding system to work in Oscam, you need a modified Oscam, as the standard Oscam build does not support it. Second, your current Oscam configuration contains many inconsistencies (bugs). Thirdly, for this modified Oscam, you additionally need some suitable settings :-/ .

There are a lot of packages in the OpenPLi feed that have almost no meaning and purpose or have no universal use (I can find them on one device, but not on another device). But I have already written about the universality of use.

On the feed servers of various Enigma2 distributions there are plugins for picon updates and also directly IPK packages with picons... but not always all picons are found - for all EU satellite positions and usually only with one graphic design to choose from. And if you find all the EU satellite positions there, then you won't find a transparent picon design or picons with a white background (just as a design example), but often only one type of graphic design - usually everything is just picons with a black background.

I'm done here. I don't intend to debate this further.

If all this were up to me, the feed server would probably have ALL existing open source E2-plugins, which are, however:

1. problem-free (no ridiculous errors in the Python source code)
2. always up to date (the author of the plugin is not dead, so there is no reason for him not to take care of his plugin)
3. universal (people also know the plugin from other Enigma2 distributions)
4. simple (practical to use)

Really ALL open source E2-plugins should be on the feed server. That is, those that the plugin creator takes care of. Often in discussions I see problems with PY3 but with plugins that are directly on the OpenPLi feed . The ChocholousekPicons plugin has dozens of positive features . But if no one from the OpenPLi team mentions it on their Enigma2 feed, it won't bother me. It will only bother users who use OpenPLi and have to install the ChocholousekPicons plugin in a complicated way :-D.

I wish you a nice rest of the day ;-).

@Abu Baniaz

How about this... try the following:

#!/bin/bash


cd /tmp
ls
# p.ipk

ar --version
# BusyBox v1.36.0 () multi-call binary.
# ......

ar -x p.ipk
ls 
# control.tar.gz  data.tar.gz     debian-binary   p.ipk

tar -xzf control.tar.gz ./control                 # extracting the file "CONTROL/control"
ls
# control         control.tar.gz  data.tar.gz     debian-binary   p.ipk

TMP_VAR=$(cat control | grep -i "Depends:")
cat control | grep -i -v "Depends:" > control_; mv -f control_ control; chmod a+x control      # remove the whole line with "Depends:" string, ignoring LOWERCASE/UPPERCASE
echo "$TMP_VAR"           \
  | sed 's@libc6 (.*),@@' \
  | sed 's@libc6 (.*)@@'  \
  | sed 's@libc6,@@'      \
  | sed 's@libc6@@'       \
  | sed 's@enigma2,@@'    \
  | sed 's@enigma2@@'      >> control

gzip -d control.tar.gz                          # extacting "control.tar.gz" -> to -> "control.tar"
tar --delete -f control.tar ./control           # delete old file "control" from archive
tar -uf control.tar ./control                   # update this one "control" file in "control.tar" archive
gzip control.tar                                # compress "control.tar" -> to -> "control.tar.gz"


ar -r p_new.ipk ./debian-binary ./control.tar.gz ./data.tar.gz

Hi.

First, check if any packages containing the text "cam" are installed:

opkg list-installed | grep -i "cam"

If so, then you uninstall the packages you don't need (OSCam packages):

opkg remove <found_package_name>

Note: The name of the package you use must exactly match the name of the installed one.

If there really is no package under the installation manager (under the opkg), then you probably installed / changed something manually. In this case, delete the "init.d" scripts, which contain the OSCam process handle (primarily, this ensures that the process is started during Linux booting). Then check if any OSCam(s) are running (scroll and find them, for example, with the help of the top or htop tools). If you found any running OSCam, kill them directly in the top (htop) tool or with the command: killall -9 <process_name> . Finally, delete the OSCam binary files, belonging to OSCam, in the /usr/bin folder via FTP connection or manually.

 

But why do you really need the latest highest number? Do you have a good reason or is it just the number?
When you have a good reason we can also consider to change the number for our feeds!

simply to stay up to date

 

Hi, sorry, but you are wrong.

Oscam is not software or an operating system. It's just some software interface between DVB and decoding card. If everything works correctly, there is no reason to change anything there. I personally know people who use even very old versions of 115xx or 116xx. There's really no reason if you don't need to deal with a specific bug.

Binary files for the Oscam can be downloaded from anywhere. Although you can never guarantee that the binary file will not contain any spyware or malicious code. Namely, there is no antivirus software in small Linux distributions, that would automatically protect you from something similar. However, there are websites where Oscam binaries can be trusted (builds from different people making different builds of Oscam that work). So you can get and overwrite the original binary with the new one. You only need the binary that is intended for your chipset in the set-top box ("mips/32/el", "arm" or its derivatives and "sh4" chipsets).

how can i update openpli feeds?

By command in the terminal as follows:

opkg update

Not as opkg upgrade because the upgrade argument will start updating everything. While the update argument just updates the offline list of available (online) packages.

Or also when you enter the Plugin-MENU (the installation Plugin-MENU) with the help of RCU, the offline list of available (online) packages in your set-top box is also updated automatically.

Hi.

Is your Oscam 11719 running ? Are your DVB channels decoded correctly ?

What does the startup cmd-line for your Oscam look like ? You can find out with the following function, just copy the code using CTRL+C , and then paste it into PuTTY by right-clicking in the terminal window... and then just run it:

OSCAM_BIN_FNAME="oscam"
if ps --version 2>&1 | grep -q -i "busybox"; then
   ps | grep $OSCAM_BIN_FNAME | grep -v grep | head -n 1 | grep -o '/.*$'         # feature-poor `ps` command from BusyBox (for example in OpenPLi image)
else
   ps -f --no-headers -C $OSCAM_BIN_FNAME | head -n 1 | grep -o '/.*$'            # full-featured `ps` command from Linux OS (for example in OpenATV image)
fi

If necessary, also modify the name of the Oscam binary file (in the variable OSCAM_BIN_FNAME at the beginning of the algorithm).
 

Isn't there a modified directory path to the configuration files - in the starting cmd-line ? Because in that case, you have to move your configuration files to the appropriate directory. The forced change of the configuration directory can also be detected in the startup "init.d" script, which can be found in the directory /etc/init.d/softcam.....). Look for the "-c <dir>" or "--config-dir <dir>" parameter there.

Try running your Oscam in the terminal as well and watch what happens:

OSCAM_BIN_FNAME="oscam"
killall -9 $OSCAM_BIN_FNAME
/usr/bin/$OSCAM_BIN_FNAME

Hi.

It happens to me too, but I haven't found out why. Sometimes Oscam just stops working after booting. In my case, however, it is Enigma2 distribution OpenATV 7.3 + Formuler F4-Turbo set-top box.

In old versions of Enigma2 it was OK.

Since I don't often need to reboot the set-top box, it doesn't matter to me. I restart Oscam after booting Enigma2 manually and then Oscam works OK.

From my point of view, the problem can be, for example, in the loading of some libraries, drivers or the computer network itself. Apparently, Oscam has some problem with the mentioned system resources until they are fully started / fully implemented - fully available for the Linux system. But that's just my humble guess!

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