Posts by s3n0

Quote from .atari.

with the stability of the oscam i have never had any problems yet i have addressed the protocol and not the softcam itself!

and yes i know the code i said but that is not the topic here

However, I did not write about the stability of OSCam. The OSCam itself runs fine in Enigma.

Problems only occur when using a particular module or function - in some precise context with something else. Thus, under certain well-defined circumstances, OSCam, for example, may freeze as a client. It can be an error in the incompatibility of system libraries, it can be an error in differences in versions of the cccam / newcamd protocol, it can be an error of specifically used microprocessor instruction sets (mips, mips32el, mips-el, ...), it can be an error of added new special and little tested functions in OSCam, etc. ... the mistake can be anywhere.

You probably don't do very well programming and if so, not as a system programmer ... so you don't even understand the context in different types of algorithms (OSCam-softcam vs. CCcam-softcam). Sorry :-/.

The main problem is that OSCam is constantly evolving and renewing. However, CCcam-softcam is forgotten (I mean cccam as a softcam and not as a protocol). But even the cccam protocol simply needs different types of improvements. However, they may not be compatible with different versions of OSCam. It is complicated.

I am not saying that the problem cannot be solved. But it would have to be solved by some developer of DVB systems who understands DVB technology. It's not me. It is necessary to debug and search for the cause of the freeze, on a specific : device brand and device model, Linux kernel and its libraries, configuration, .... I'm not stupid either :) and I tried an huge number of configurations in 2 weeks. The result was always a frozen OSCam-Softcam in the position of the client (on any protocol). So it's an OSCam binary bug in this particular case.

@SpN1986 :

Well, unfortunately I don't know the ARM binaries of the CCcam Softcam. I wrote about the MIPSEL processor / chipset architecture. Sorry. You can try the CCcam binary v2.3.2 or an older version.

Quote from .atari.

When working good with cccam than working with oscam too

when I use homesharing use protocol cs378x and all fine

You have apparently never programmed microprocessors in Assembler or system programming (C language + Assembler). CCcam softcam is diametrically different from Oscam and works in quite different principles. The CCcam algorithm contains outdated source code. Since its source code is closed (it is not open source and is not freely available on the Internet), it is not even possible to improve this code. Oscam Softcam is the exact opposite. Oscam is constantly improving - also in terms of the principles of communication protocols (cccam, newcamd, cx3xxx and others). What you wrote definitely doesn't apply. In softcam algorithms, there are a lot of differences in algorithms, modules, dependencies on system libraries, ... that work differently. However, the main reason is that no one regularly updates CCcam Softcam for Enigma. It has its advantages and disadvantages. For example, the advantage is good and stable functionality, but the disadvantage is many BUGs that hackers and crackers know (guys who read literally machine code under Assembler and know the specific platform under which the code works).

4.0.210301

Improved Lithuanian language from 2021-02-16 (thx to Adga).

Fixed a minor bug in the sorting of database files in a folder:

- the error could theoretically cause the database update of available picons to be stuck

- so sorting files by algorithm is now alphabetical, not by creation date

Created and added a new bb-recipe to OpenATV feeds (thx to Nicker):

- https://github.com/nickersk/oe…37ac1297ae3d724713dad54b9

- https://github.com/oe-alliance…tv/image/openatv-feeds.bb

- https://github.com/oe-alliance…ns-chocholousek-picons.bb

Hello.

I recommend using Cccam-softcam instead of Oscam-softcam (if you only want to use softcam as a client). Personally for me the Oscam makes problems in Irdeto. Of course, this depends on the different details of the particular provider and the particular decoding card algorithm. In my opinion, changing the Oscam configuration will not help to you.

You can simply use the Cccam v2.3.0 softcam at least for stability testing. I had similar problems and no Oscam configuration helped to me. I already have better experience with configuring Oscam :) so I know what I'm setting up in Oscam. However, I have no experience with DVB technology (eg such as DVB-S encryption algorithms), because I am not very interested in this :). I've tested a lot of things in Oscam configuration. Unfortunately, no result.

In my case, the Oscam accidentally froze, within 1-2 days, any Oscam version (I tried old and new versions), as a softcam-client. I tested the connection via the "newcamd" protocol but also via the "cccam" protocol - I tried both protocols. In the case of cccam protocol, I also tried to force different version (2.0.11, 2.1.0, 2.2.1, 2.3.0, 2.3.2, ...).

Finally, the use of cccam-softcam (as a client) helped.

I did not use EMM packet writing (AU / AutoUpdate) with a remote softcam client. EMMs are registered on the main set-top box, on which Oscam (as a softcam-server) runs successfully.

It doesn't matter where it is. It can be adjusted in any case, according to your own needs.

You can easily make a rocket out of Enigma2 of a distributed Linux and then shoot it towards Mars :).

EDIT:

One way to find a startup shell script in Enigma2 with the closed source code (OE2.5+ enigma core) - powered by Dreambox:

find /lib/systemd/system -iname "*cam*"

Hi there.

Depending on the CCcam version, it is also possible to use the -C /config_path executable file argument. Example: /usr/bin/CCcam -C /var/etc/CCcam.cfg. So just edit the startup script and add the argument mentioned there when starting the CCcam process. I don't know where exactly lies the script for start|stop|restart of the CCcam, in Dream Elite 7.1, but it will probably be in the standard /etc/init.d folder.

Hi.

Hard to advise... I still don't know your provider and the type of encoding of your card. So I don't know what to look for :).

Where did you get the Oscam configuration file settings from ? Are the Oscam configuration file settings OK ? For example, are you using the correct frequency of the card chip / card reader ?

I'm also not an expert on Oscam configurations :). I only know Irdeto coding curry and only a little :).

CAID 1805 is according to the https://trac.streamboard.tv/oscam/wiki/CardsList database, provider Mediaset (from Italy).

Hi.

What about other details ? ROFL !

1. What is a version of your Oscam ?
2. What platform (operating system, chipset / CPU architecture, device manufacturer, ...) ?
3. You could see the error copied here, directly from Oscam Webif / Live Log.
4. What is the exact wording of the LiveLog entries ?
5. What type of encoding is it (which decoder card / CAID or which provider) ?
6. How exactly does this problem manifest itself (one ECM is suspended and then continues without a problem) ?

Hi.

I think that your config entry "/dev/Sci0" is wrong. Correct entry is "/dev/sci0". Or maybe something like this "/dev/stapi/stpti4_ioctl" ? Or I am wrong ?

Does this device path apply to Android TV at all ? Isn't there something else ?

Don't want to connect to a softcam-server ? Instead of a fixed built-in card reader ?

4.0.210214

Add log output to the file "/tmp/chocholousek-picons.log", while updating picons.

Added testing of the connection to the server, which contains picon packages, after testing the internet connection.

Minor syntax modification according to PEP8 E251.

Renaming some functions (source code) to make them clearer.

I don't know. Try it please.

But it's probably compatible ... it should work in any Enigma2 distribution version.

master G

This whole discussion is about paid service. So why did you delete the URL for a procedure that was also copied from this website in previous posts ?

Why is the paid service URL banned, but the paid service discussion is allowed ? :) A bit strange rules of the discussion forum :). Why I even write in these topics :). It is best not to write anything at all.

Quote from technodvl2

952622b5f80.jpg

98924feb1110df2711e8.jpg

the only way i could import it

was to use dreamboxedit

Display More

It is not necessary to use DreamboxEdit. This can be done without DreamboxEdit:

1. copy the "userbouquet.sky.tv" file to the "/etc/enigma2" directory

2. add the new one userbouqet record into the user favorite list - i.e. into the file "/etc/enigma2/bouquets.tv"

- so add the new line there (using FTP connection for example):

#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.sky.tv" ORDER BY bouquet

3. reload the settings (userbouquets and lamedb) via the Shell, with the help of openwebif:

wget -qO- "http://127.0.0.1/web/servicelistreload?mode=0"; sleep 2; wget -qO- "http://127.0.0.1/web/servicelistreload?mode=4"

Unfortunately, the instructions are not completely accurate or are intended only for a specific Enigma2 distribution and not for all Enigma2:

xxxxxxxxxxxxxxxxxxxxxx

007.4 :

Try this via shell:

opkg update

Then copy the console output here. We can check - if updating of the softcam feed was done or if something was wrong there.

Also check the "/etc/opkg" folder (for example via an FTP connection to your set-top box), where a source (file) for softcams should be added, containing the URL "updates.mynonpublic.com".

Oscam 11684:

- added TotalTV Serbia (0911) ATR

Quote from m-tomatis

......alternative script I posted in a previous message of mine (I edited my post as you suggested).

Great. Thanks. But you could copy it from again with CTRL+C / CTRL+V , because there is an incorrect identation :).

If the second "init.d script" works for you, then it's OK.

The broken script could run in debug mode and find out where the problem is (insert debug output, from Shell, here in the discussion):

bash -xv /etc/init.d/<shell-script-filename> stop

...and also... :

bash -xv /etc/init.d/<shell-script-filename> start

But you must first state where the mistake is :). For example, generate a debug-log under your Enigma. There may be a visible problem with the freeze - because of the freezing of Oscam, as you write (and the freeze is supposed to occur during the reboot of Enigma).

BTW, edit your previous post and please re-insert the shell script into the CODE TAGs. It is very difficult to read. 🤔 Thanks.

There are a few things in this script that may not work in every Enigma. It was written by audi06_19 . If the "init.d script" is written specifically for OpenEight, then it must work correctly. But if the "init.d script" is written as universal, then it may not work correctly in every Enigma. Try using my softcam init.d script - https://github.com/s3n0/e2scripts/blob/master/softcam (you can find the procedure and explanation in my script). Of course, you should also customize this script of mine, and don't forget to assign the attributes of the script execution (chmod a+x /etc/init.d/softcam*).

https://github.com/Openeight/enigma2

https://github.com/Openeight/enigma2/search?q=Softcam

I don't know if this GitHub belongs to the official OpenEight, nor who is the author of this image. It looks like a copy of OpenATV, but maybe I'm wrong. I don't know where OpenEight comes from.

In my opinion, there is just some error in the init.d script used, as I wrote before. Alternatively, there is an error in improperly used / incompatible system Run-Levels.

Upload as an attachment here, your "init.d script" for the softcam you have in your Enigma.

:hello