oscam problem with the newer versions

master64nl :

Sorry I can not.

I'd have to see what's what. In order not to remove functional libraries. However, you can always make links (symbolic links) in Linux ... but you must be sure which libraries are working in your Enigma. Probably the original version in your Enigma will be 1.0.2 and it needs to make symbolic links from the old versions if some old Softcam needs to use these old versions as well. If I don't know what's in your directory right now, I can't help you.

Unfortunately, as you mentioned earlier, you created links from the old versions to new version and thus non-existing files. So there may be a big mess now.

It looks like it now links to another link :). But no library files already exist in your directory :). Just links to links that don't exist. So I don't know.

djfrosty:

OpenATV SoftCam Feed Discussion Thread

master64nl:

The answer to your problem has already been written several times. If you still can't solve the problem yourself, you need a man with more experience in Enigma. Write me if you want on Skype, and if you believe me give me TeamViewer ID and look at it remotely - I hope you can fix it.

Why should I keep repeating what is wrong and what you have to fix in the set-top box. You won't do it anyway.

master64nl:

Because other Oscams do not contain the necessary libraries (libssl, libcrypto, ...) as well as this large file. These libraries are not included inside of other Oscams.

Since it did not solve the OpenPLi-7 library problem and there is chaos, libraries are used that are directly included in Oscam. Since you have not fixed the libssl and libcrypto libraries in your OpenPLi-7, then other OpenPLi tools that require these libraries (such as OpenVPN, OpenSSL, and others) will not work.

What exactly is meant by "replace for a oscam" ?

- do you mean IPK softcam package manually installed via the Shell ?

- do you mean IPK softcam packages installed from an additional softcam feed resource ?

- do you mean replacing the softcam binary file (in the folder "/usr/bin") ?

In such a case (binary file) the situation is more complicated.

A particular binary file may not contain all modules and functions (depending on which platform the binary is predetermined or for which platform it was compiled).

You need to be sure that the binary file is designed for Enigma distribution of a particular type and that it is designed for the chipset architecture in your set-top box (this is mainly CPU type). Otherwise, for example, if the binary file is designed for a WiFi router and not for a Enigma, then communication with the UNI card-reader will not work properly in your set-top box. If only the chipset architecture fits, it is not enough - there must fit everything.

To replace a binary, you must make sure that you use the correct type of binaries.

Most softcam binaries for Enigma distributions are compatible and should fit everywhere - into every Enigma. However, this is not always a condition.

It is also important to follow the procedure for replacing the binaries. First, stop the softcam daemon. Then overwrite the binary. If you rewrite a file, its attributes should be preserved. If you delete the old file first and then upload the new file, you must to set again the execution attributes (chmod +x /path/to/some/file). Then start the softcam again.

Basically, two chipset architectures are used currently as the most popular:

arm-v7/v8

mips-el

For Enigma distributions, only universal binaries are usually created (compiled) that should work in every Enigma.

Also, everything depends on the available libraries (modules) that are not included in the binaries. It is supposed to be part of every "small distribution" of Linux.

However, it depends very much on binary file launchers (of Softcam). Many Enigma distributions differ in Softcams support - this also applies to Softcam launchers. For example, if the configuration directory is not defined in the Softcam launcher, then it is automatically searched (using the Softcam binary algorithm). However, when a default configuration directory is found that has already been preinstalled by the IPK package (using the default config directory with default config. files), this is the first one found and not your another config folder, which may be the second one in the folder search order. If the configuration folder you have used so far is in the lower order then it will be ignored (you must move your config files to the first folder or add an argument specifying the configuration directory to the softcam launcher). Specifically, the oscam binary uses the "-c /path/to/config/directory" argument for this purpose.

Simply written - unfortunately, not every launcher (according to the IPK installer) also sets the argument to specify the configuration directory. In this case, the softcam must search for the configuration automatically. If softcam finds it, he will use it. However, the directory search order is precisely defined. For Oscam the config dir search order is defined here (searching for a specific "oscam.conf" file from several directories in order):

https://github.com/OpenVisionE…60476064123/oscam.c#L1652

http://www.streamboard.tv/oscam/browser/trunk/oscam.c#L1652

So if your current config is in a lower position than the default config installed with the IPK package, unfortunately your configuration directory will not be used, but only the default configuration directory. The "/etc/tuxbox/config/" directory has the highest priority in automatic configuration search (unless the directory was specified by the arguments in the Oscam launcher).

As I wrote, it is complicated and even with a small error, the whole system may fall quietly :). Linux / Unix based systems are perfect, but it is necessary to have at least basic experience.

What is the libcrypto-compat library ? You dont need that library, I think. BTW, you already have a libcrypto library installed. Otherwise, creating links to an existing libcrypto library would not work.

Of course, if you want to link the file-name directly, you must be in the appropriate folder, of course. So, as the first, you should use the directory change command: cd /usr/lib . Only then should you use the "ln" linking command.

And in your last command on the screenshot you even have errors in the path to the directory.