Posts by s3n0

No, you misunderstand it.

This plugin is device-specific and firmware-specific. Unfortunately, devices differ in the way they use memory. Even memory capacity can affect the proper functioning of BackupSuite (you need a USB stick if you have little space in Internet flash memory or RAM and you may need EXT filesystem instead of FAT). They are also different in CFE-bootloaders, so loading the image into memory is different. Therefore, BackSuite on some devices must assume a different type of CFE-bootloader.

Unfortunately, BackupSuite is not universal, although many developers have customized this plugin to work with each one firmware. Then, for example, a different type of the Shell or a different version of the BusyBox in Linux is enough to make a problem.

I think it's stupid to make a full backup image. In my opinion, it is better to download the firmware from the internet, flash it, then add the necessary plugins and files, and finally replace the backed up file "/etc/enigma2/settings" or rather the entire contents of the "/etc/enigma2" folder. With Enigma2 stopped with "init 4" command in the Shell, of course.

If you want to solve functionality, you have to put the exact details of the problem and best on github (if you use OpenVisionE2 or OpenPLi, write about the problem on their Github server to Issues).

Hmm... no such file or directory ?

Unfortunately I don't know well the "dpkg" package manager (enigma core OE 2.2+), but I only know the "opkg" package manager (enigma core OE 1.6 / 2.0 or derived OE-Alliance Group).

There were similar problems before. Uninstall and install problem. Some CONTROL / DEBIAN scripts in the case of the "dpkg" manager probably also need delivery parameters, because they behave slightly differently than in the case of the older "opkg" manager. A similar problem has already been seen with regard to installing and reinstalling the plugin on the OE 2.5 core. You probably have an even newer core (since you're using the latest Dreambox genuine firmware). That's why I tried to solve this by gradually uninstalling and then reinstalling it: https://github.com/s3n0/e2plug…icons/src/plugin.py#L1057

Of course I have already treated it in CONTROL / DEBIAN scripts, as someone advised me above - since I do not know well "dpkg" package manager. I do not own any set-top box with OE 2.2 or 2.5 and higher (for a testing purpose).

It is also possible that you were using an older version of the ".deb" plugin package, which used old scripts and maybe they failed the installation. I hope it will be OK from now on. If not, then write about the problem again ;-).

I don't know the original Dreambox OS firmware. In my opinion it is possible to debug somehow also in Dreambox firmware. For example: http://wiki.blue-panel.com/index.php/Create_Enigma2_log_file

What about my other questions ? Please try the directory listing:

ls /usr/lib/enigma2/python/Plugins/Extensions/ChocholousekPicons

Are you using the default SKIN or other SKIN ?

Did you also try to restart the set top box ? Is the plugin really installed ? After restarting, check the folder:

/usr/lib/enigma2/python/Plugins/Extensions/ChocholousekPicons/

Which Enigma image do you use (name and version) ?

Is there also a debug-log in your Enigma ? Unfortunately, I am not the holder of all Enigma distributions in the world :-( so I can't debug the plugin in all Enigma distributions.

You need to show me some bug report or screenshot or how you are sure the installation was successful. Otherwise, unfortunately I cannot debug the error you mention other than with the help of the user.

I won't help you. I don't use this plugin. I'm not even the developer of this plugin (these shell scripts - to put it better).

Developers from the OpenVisionE2 team could help you, because this plugin is already included in their Enigma2. For example, the Github bake recipe also takes OpenPLi directly from them.

https://github.com/OpenVisionE2/BackupSuite

License: GNU GPL 3.0 (free distribution)

I currently consider OpenVisionE2 the only trusted source code for the BackupSuite plugin. So try to contact them.

You won't even find the official source for this "plugin", because everyone customizes it for themselves ... for years ... for each device differently and for each Enigma differently.

It would certainly help debug-log (if you allow it in your Enigma to generate it) or crash-log (if it was caused by a plugin crash). Unfortunately, there is very little information in your screen closer. I don't know exactly which Enigma you use and which set top box.

Quote from electron110

ENIGMA2

No, I don't want to know if you're using Enigma2 or not, but which distribution exactly. :) Such as: DreamElite, Merlin, OpenATV, OpenPLi, OpenVision, OpenHDF, OpenDroid, ... etc. ... there are many different distributions with different Enigma cores. Based on this Enigma2 distribution, you can then use a suitable installation package ... that is, designed to integrate it into a particular type of Enigma2 distribution.

Hi.

Which Enigma do you use ? Enigma also matters, so if you want to use the Softcam installation package. But if you would like to use the Softcam manual installation procedure, then Enigma distribution does not matter.

Hello.

Files "oscam.srvid" and "oscam.srvid2" are used to better identify channels in OscamWebif - so you will see the channel name (ServiceName) instead of the channel code (ServiceID).

However "oscam.srvid" should be up to date. Download it here: http://kos.twojeip.net/

Oscam creates the "oscam.srvid2" file itself from the available information about each switched channel (reading info from DVB transponder), but only if you enable this feature in the "oscam.conf" file - . He would not have to rewrite. Have Oscam create it automatically (if you allow it of course).

The "oscam.dvbapi" file is used to filter CAIDs / PROVIDs or create a redirect to another CAID. It depends on whether the entire Oscam is configured correctly.

The "oscam.service" file contains only channel group definitions, which you can then use as a filter or as an exclusive channel group (used in the "oscam.server" or "oscam.user" files).

More info about oscam config files:

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

You should always use backup tools designed for a particular Enigma. For example, if the BackupSuite plugin is on a particular Enigma feed, use that BackupSuite plugin and no other. Unfortunately, not every Enigma supports this universal BackupSuite plugin. BackupSuite may not work everywhere. It works for a while and it does not work for a while. Unfortunately, the functionality status varies depending on the version of Enigma, as well as the updates in Enigma. Unfortunately, many Enigma development teams turn away from the Enigma2 standard. Then these problems arise. However, each Enigma should have its own backup tool.

Ufff will not help with this. This "ubifs" is a matter of filesystem.

However, a bug in your screen-shot indicates a problem with using the "grep" tool. If not all the previous commands have been executed correctly, then any subsequent commands in the order will not be executed correctly.

Hi.

The path to the Oscam configuration directory after it has been installed can be found in several ways... for example:

(If you do not know the IP address of your set-top box, you can find it somewhere in the INFO MENU in Enigma (using RCU) or you can find it in the web configuration interface of your WiFi router.)

---- 1 ----

Via the Linux Shell:

find / -iname "oscam.server"

---- 2 ----

Use the Oscam-Webif (via the web-browser):

http://IP_address_of_your_Set-top-box:8888

...or:

http://hostname:8888 (for example, the hostname of Vu+ Solo SE V2 device is "vusolose")

Then go here:

Files --> oscam.version --> check the row, with the name "ConfigDir"

---- 3 ----

Via the Shell / terminal connection (using the PUTTY tool), for example:

wget -q -O - "http://127.0.0.1:8888/files.html?file=oscam.version" | grep -i "configdir"

- but if you also use a password in OscamWebif, then use this:

wget -q -O - "http://USERNAME:PASSWORD@127.0.0.1:8888/files.html?file=oscam.version" | grep -i "configdir"

Or... check the Oscam process as full command-line:

(A) top -bcn1 | grep -i oscam # only if the "top" is a full-featured Linux tool (for example in OpenATV)

(B) ps aux | grep -i oscam # only if the "ps" tool is a full-featured Linux tool (for example in OpenATV)

(C) ps | grep -i oscam # only if the "ps" tool is a part of BusyBox (for example in OpenPLi)

...look for the argument -c <path> in the oscam command-line, which specifies the config directory for Oscam

---- 4 ----

If the "-c" argument was not specified in the Oscam trigger, i.e. the configuration directory was not specified, then Oscam algorithm will automatically use the search sequence as follows:

Quote

/etc/tuxbox/config/

/etc/tuxbox/config/oscam/

/var/tuxbox/config/

/usr/keys/

/var/keys/

/var/etc/oscam/

/var/etc/

/var/oscam/

/config/oscam/

Display More

Source code is here:

oscam.c in trunk – OSCam

Thus, the configuration can also be uploaded to any of the listed folders. If there is no default configuration in any of these folders, then you may upload those of your own configuration to one of the listed folders (I recommend the first folder or the second folder in order).

You have to write more info - what version of plugin you use and where you got this version.

The above error in the screenshot probably refers to the grep tool - incompatibility of parameters, probably because of a different version of the grep tool or incorrect use of grep in the BackupSuite plugin.

BTW, the patch on the getBoxType problem I mentioned above has already been modified in the BackupSuite plug-in, which comes from the OpenVision Enigma2 image (also found on github).

Quote from Panda555

I really don't know how. I read about this on Openpli forum, but it's seems that serviceapp is never implemented as plugin in

Openpli images. I have also DM800SE, now with Pure2 image. Consider a recommendation of master G , and install these image.

ServiceApp is already included in the new OpenPLi images. You probably read badly. ServiceApp is not implemented as a standard component after installing the OpenPLi image, but it exists on the feed server and the user can install it himself.

You must just install the serviceapp and use it with a userbouquet file (service number 5001-5003) after configuring all services via plugin MENU -> ServiceApp. Or can you find it only in System-MENU and not in Plugin-MENU? Sorry, I don't remember where to find ServiceApp after installing (and restarting Enigma).

The serviceapp package should also include exteplayer3 and ffmpeg dependencies, so they do not need to be installed before the serviceapp package is installed. When you try to install the serviceapp package, these dependencies will also be automatically checked and installed. If there are no dependencies added to the serviceapp package, then there is no problem to install them manually, as mentioned by hecha71 :

opkg update && opkg install ffmpeg exteplayer3 serviceapp

I have another observation for you ... I see that your softcam client sends requests for CAID 604, but also for CAID 606. But only CAID 604 works - according to LOG.

So if you use any CAIDs limitations, remove them from your Oscam configuration.

And, of course, if you want to use the "/etc/rc.local" file as trigger (to start the softcam) then a script file "/etc/init.d/softcam...." must be also removed.

You haven't written down which Enigma2 distribution you're using, so it's really hard to give you advice.

Are EMMs written to the satellite card ? See it OscamWebif -> Readers (you'll see EMM statistics columns on the right side of the view).

I don't know how your card coding works, but I think you only need to send Conax EMM entries once. Of course, your card must be functional at the time of sending the EMM. Some Conax need EMM command only once. When you pay a fee, they are sent for only a few hours and then stop sending - but the validity of the date is stored on your card via EMM. I do not know :). Sorry.

What expiration dates are on your "entitlements" in OscamWebif - for your reader ?

In a classic satellite receiver, did you test your card ? Does it work at least in a classic receiver ?

Some channels work and some don't work ?

Will you finally write what is the provider and what card coding ?

:derpthink:

Your Oscam configuration files are wrong...

2020/03/27 14:15:09 0BD6A8E4 c   (dvbapi) Demuxer 0 no suitable readers found that can be used for decoding!

Maybe missed some CAID definition ? I haven't seen your Oscam configuration files, so I can't advise you.

Why "oscam.conf" uhm ... I have already told you that the server can run all available protocols as a server.

The only thing that matters is that your "sleeping" user does not connect via newcamd, but cccam:

2020/03/27 12:09:45 205E28A3 c (newcamd) client connected to 10002 port
2020/03/27 12:09:45 205E28A3 c (client) encrypted newcamd:10002-client 80.___.__.__ granted (sleeping, au=on (1 reader))
2020/03/27 12:09:45 205E28A3 c (newcamd) user sleeping authenticated successfully (CCcam)
2020/03/27 12:09:45 205E28A3 c (newcamd) AU enabled for user sleeping on reader Canal_Digital

For cccam settings (C-Line, N-Line) check the following links:

N-Line format vs Oscam: N-Line vs Oscam

C-Line format vs Oscam: C-Line vs Oscam

So try to reconfigure the client "sleeping", the connection from newcamd (N-line) to cccam (C-line). But that probably won't help ... even though I'm not sure if AU / EMMs are working properly, it looks like they should work.

Just comment (with a # at the beginning of the lines) the newcamd definition in the softcam server configuration. Or stop attaching the newcamd protocol on the client side! Easy! Why do you connect both newcamd and cccam from client ? :) Use only one protocol at the client side.

You can also leave multiple communication protocols open on the server. It doesn't interfere. The best way is to stop using both protocols on the softcam client side. That is, delete the newcamd config on the client side and leave only cccam (or vice versa - depending on which encoding is used or according to the DVB provider, other softcam protocols are always more appropriate).