Posts by s3n0

alexbore:

I do not use wget for a long time in the plugin algorithm for downloading files from the Internet. There is used the "urllib2" python module, I mentioned it on Skype. Wget is only used to test SSL functionality in Enigma. There are sometimes problems with this SSL - especially in the case of your Enigma, which unfortunately uses the ordinary wget contained in BusyBox, which is a cropped version. This cropped wget has little or no support for SSL (HTTPS). SSL issues are already resolved in the plugin because I use two mirror servers even without SSL (i.e. HTTP mirror if HTTPS failed). As for downloading picon archives from drive.google, it should work as well (I don't have it verified because I don't own the OE 2.5+ core enigma). Unfortunately.

There was a different problem with device # 3 DM dm800hdse with OE 2.0. I mean the Green-Screen-Of-Death. There was a FONT problem right in the "configList" widget (a different config Screen class and its methods). Unfortunately, the new Enigma kernels - in your case, the new OE2.0 kernel in the NewEnigma2 image, cannot use the same font setup method as the old open-source OE 2.0 kernel. The problem was in detecting the kernel, but that should be resolved.

I think you have my code left in the plugin folder for testing. This is a mistake because it will not be overwritten by the new version from the Internet during the update. So even if you see the new version number of the plugin, you still have the source code of the older version and it takes precedence (the .pyo code is overwritten when you restart the Enigma with the .py source code). The solution is to delete the entire plugin or uninstall it. For sure, also delete the contents of the plugin folder. Then reinstall the plugin. I wrote to you on Skype today, but you didn't answer ... you probably have a lot of work to do :-/. Can you please send a new crash-log file? I'll be grateful. :) However, this will probably be the problem I just mentioned.

This is a bit complicated, as I said. It depends on the dependencies of the particular binary. Usually the "7za" full version of 7zip handles many features and therefore requires a lot of modules and libraries from the system. While the stand-alone version of "7z" does not need any modules, and if so, it will do the minimum of dependencies you will find in the Enigma. What is the full 7zip version for when the stand-alone "7za" is good?

Each Enigma distribution and each version of the Enigma core needs different libraries. You need a specific .deb package for a particular Enigma. Of course, you can also try to download and use a .deb package from another Enigma with the OE 2.5+ core and install it in your Enigma, but there will probably be some additions missing, and it's also a problem to get the installer because it's not free.

Hi. Check out LiveLog in the Oscam web interface (OscamWebif).

http://ip_your_device_address:8888

Is there something wrong to see or not ?

What do your oscam configuration files (.user / .server / .config) look like ?

If you don't have it, try adding the following in addition to keepalive in the oscam.server file, under the reader section:

inactivitytimeout     = 1
reconnecttimeout      = 30
keepalive             = 1

The softcam server is yours ? If not, you should resolve these problems with your softcam server administrator. He will give you the best advice. Send him LiveLog records from OscamWebif and ask him.

But there is already a .deb package with the ChocholousekPicons plugin and not just the .ipk package. The chipset / architecture detection is not working well. But I improved it a bit and changed the architecture detection priorities, so it should work correctly.

You mean "p7zip" installation package? If you want to use the full version of the 7-zip archiver in Enigma, unfortunately there are some dependencies on the modules / libraries in the system.

Since I do not own any Enigma based on core OE 2.2 and higher, I cannot even create a functional .deb package p7zip full. The binary "7za" is not enough ? It is a stand-alone version and contains a lot of features like the original "7z". For example, the stand-alone version "7za" lacks support for combining libraries ("ar" format). But it's a fully functional version.

----------------

2.0.200409

Added Polish language.

Improved algorithm for detecting chipset architecture aarch64 / arm64 (debugged on the Enigma core - OE 2.6), thx to alexbore.

Accepting sym-links to 7-zip executable file.

Changed Enigma core detection method - instead of detecting the Enigma core version, only the type of core will be detected (used for skin modification and timer function).

Hi, thanks again for reporting and testing...

That's all ... if the "7za" binary executable file works in your Shell ... you are done. Rename "7za_aarch64" to "7za": mv /usr/bin/7za_aarch64 /usr/bin/7za. The plugin should work.

I would be more interested in the DEBUG-LOG from your Enigma :). Otherwise I will not find the error and solve it.

In the first case, I wonder why he couldn't connect "wget" to "github.com". Perhaps the new version of "wget" used in your image does not allow connection with the argument "--no-check-certificate" ? Or maybe there is a SSL problem ?

In the latter case, it is strange that the manual procedure for downloading the "7za" binary file and its test worked correctly. Not in the plugin algorithm.

Try looking for a different package name. Maybe another "7zip" package in DreamElite is used ... I don't know hm. Maybe 7zip is included in another package (for example, "compress-tools" or something similar). For example:

dpkg -l 7zip
dpkg -l compress
dpkg -l archivator

Or if you have free time and if you have Skype, you can write me and we can test this way :). Either you give me TeamViewer remotely if you trust me, or you just test a few things for me :). I don't own DreamElite or DreamOS ... unfortunately :(.

You don't need that. Each Enigma distribution has OpenWebif included in itself. All what you have to do is update the entire Enigma.

Alternatively, you can install OpenWebif manually. However, this has no meaning. On the contrary, some Enigma distributions may have modified OpenWebif source code or some included modules, so reinstallation will lose all the features in your Enigma distribution.

Hi.

Yes exactly. The p7zip-full package is required (picon archive files are in 7zip format).

Unfortunately, I do not own any Dreambox, so... I cannot debug it myself at home (of course - using Enigma such as Dream Elite 7 or DreamOS). So, please, is there any debug-LOG for me ? :-) I don't know if it's possible or how to debug your Enigma. I don't know exactly what the problem is to fix it. I have no idea where exactly there is a problem with installing a p7zip.....deb package from a feed or 7za binary file from the internet. I need to see some debug LOG from your Enigma.

In both cases, is it Aarch64 Enigma ? You can try to download and place the 7za binary files manually and test its functionality:

wget --no-check-certificate -O /usr/bin/7za "https://github.com/s3n0/e2plugins/raw/master/ChocholousekPicons/7za/7za_aarch64"
chmod a+x /usr/bin/7za
/usr/bin/7za          # test the executable binary file

However, this should be done by the plugin itself - unless the "p7zip-full" package was found on the Enigma feed: https://github.com/s3n0/e2plug…Picons/src/plugin.py#L522

I don't know if the "/usr/bin" folder is correct in the new Enigmas, but I hope so ;-).

Unfortunately, Cccam SoftCAM has very poor support for ARM processors. Originally, Cccam softcam is programmed to work on MIPS processors.

You can try to use the Oscam, which has open source code and all problems can be solved in Oscam. It has constantly updated. Cccam is forgotten because the whole world cannot work on it (to detect and report bugs in the Cccam softcam operation).

Quote from ddinc

I have 15 peers (gave only one as all are configured alike) don't have a local card.

Actually don't have other problems

Again ... what exactly do you mean ? Because I don't know.

I don't know what you mean by the term "peer".

If you mean one account that connects a lot of softcam clients, that's not a good solution. It is better to create 15 accounts and assign them a "uniq = 1" configuration item for better control http://www.streamboard.tv/wiki…en/Config/oscam.user#uniq . Or, some softcam clients may be reshare the softcam server and overwhelm it. I still don't understand how you use your entire softcam network. Is this your "softcam network"? Is there any other reshare in this softcam network? Who - for whom does he share?

If you don't want to explain, I can't advise you because I don't know what to advise you about. Example: If you ask someone why your car can't start the engine, it's just a stupid question ... you have to describe the details - such as when you put the key in the starter box the front lights come on or that when you start the engine, the starter rotates but the engine will not start. You just have to write details. I can't deduce anything from your "it doesn't work"! Likewise, LOG is unnecessary if I do not know what it belongs to. The LOG you sent can be the same in dozens of different cases.

If you want to assign only certain services (channels) for a specific Oscam reader, the "oscam.services" file is for this purpose: http://www.streamboard.tv/wiki…/en/Config/oscam.services In this file you will define the services (channels) to some set of "services".

You then apply this set of "services" in the "oscam.server" file, under a specific reader: http://www.streamboard.tv/wiki…fig/oscam.server#services It's easy.

To reject defined services, use the exclamation point at the beginning of the definition (services = !skyde_channels).

You can generate "oscam.services" for example. also here: http://kos.hdsat.pl/ First you mark the SkyDE provider for example and then click on the "oscam.services" button. However, I recommend verifying all included Service IDs in the file, as they may not always be all correct !

More info about configuration can be found here:

http://www.streamboard.tv/wiki/OSCam/en

I don't understand this at all. Are you doing a reshare decoding card? Or what exactly does an external card reader mean? Who does it belong to? If the softcam server belongs to you, then configure this softcam server correctly - where your decoder card is located.

You write about cards, but I only see one in your configuration.

Sorry, I don't understand how you got everything done there. I don't know the whole situation and now I don't even know exactly where the problem is. You have to describe your problem clearly and in detail. Otherwise, no one can help you.

I don't know exactly what you need, so I can't even give you advice.

What does "working badly" mean ?

Will some services (channels) stop working ? Will latency of server response time increase ? Do channels start lagging and the client no longer reconnects to the server ?

For softcam server overload problems, it is best to set lb_weight for each reader, but first enable this function in the oscam.conf file by lb_mode item: http://www.streamboard.tv/wiki…g/oscam.conf#Loadbalancer I recommend reading all about Loadbalancing: http://www.streamboard.tv/wiki/OSCam/en/Loadbalancing

If this is only a problem with poor connectivity, then it should be sufficient to set the timeout of your softcam client connection to the softcam server or set one reader as fallback (http://www.streamboard.tv/wiki…en/Config/oscam.#fallback server).

The priority for CAID, PROVID, SRVID and even CHID (not to confuse CHID with SRVID) can be set in the oscam.dvbapi file: http://www.streamboard.tv/wiki/OSCam/en/Config/oscam.dvbapi can be a little tricky to set up.

Do you use any ECM configuration items to adjust the timing in the reader settings ?

I mean these configuration items: CAID 0680 surflock active . plz give option fix it

If so, try removing them or temporarily commenting with a "#" and restart Oscam.

What you need is not Oscam for "Amiko A3", but for the chipset https://en.wikipedia.org/wiki/ARM_Cortex-A9 (i.e. arm v7 architecture) + for Android OS. I don't know Android Oscam, so I can't advise you. And you didn't answer all my questions in the first post (no LOG = no HELP).

Oscam does not use N-line or C-line.

Uses at least 3 configuration files (oscam.server, oscam.config, oscam.user).

The C or N line is translated into the "oscam.server" file as follows:

C-line -> oscam.server

N-lline -> oscam.server

Hi.

What exactly doesn't work ? What do you want to do ?

How do you set up Oscam files (OscamWebif -> Files -> ....) ?

What does LiveLOG look like ? Delete passwords and logins from LiveLOG and show what it contains.

2.0.200406

Added Lithuanian language.

(Download link can be found in the first POST of this thread.)

This is done on a Linux PC machine and not on Enigma2. Unfortunately, Enigma2 is a small and cropped version of Linux. If it could be done on Enigma2, it's more complicated than with a Linux PC.

For example, you need Debian Linux and you can try to compile Oscam for all sorts of platforms. The procedure for Linux PC x86 is simple but for other platforms it is a bit more complicated. You can find procedures on the Internet (Google search engine).

http://www.streamboard.tv/oscam/wiki/BuildingOscam

http://www.streamboard.tv/oscam/wiki/crosscompiling

http://www.satnigmo.com/2264/c…-with-simplebuild-script/ (old article)

Of course you need to have advanced knowledge of Linux systems. I do not compile Oscam for multiple platforms at all. So I can't advise you.

Hi.

Which Enigma ? Which set-top-box model ?

For example, the latest Oscam version 11573 (mips32el) from the OpenPLi team (feed server 5. April 2020), contains smargo and smartreader modules (see the attachments), but not also the pcsc module .

However, the last Oscam is version 11578 (5. April 2020), but OpenPLi uploads new versions to the feed server only after testing. So the Oscam versions are there about a month behind, there's not exactly the latest Oscam version.

It's not that simple.

You must also take into account your manually installed plugins (if you have uploaded and installed one yourself). For example, if you installed Oscam manually as a trigger in the "/etc/init.d" folder. You also need to take into account the Oscam configuration directory and back it up.

The only problem with the "settings" file, in which the plugin and Enigma settings are, can only arise on a different or new version of Enigma - with different settings (such as OpenPLi 7.1 vs 7.2), but it should also work. Of course, you first need to install all plugins before uploading their configuration (some Enigmas or plugins can clear the state of the current plugin configuration after you install it). So first install the plugins into Enigma after flashing and then restore the "settings" file or the entire "/etc/enigma2" folder.

For this purpose I use my own script (you need to edit its defined files and folders - what you need to back up):

https://github.com/s3n0/e2scripts/blob/master/backrest