Posts by s3n0

    I am trying to install picons been getting a message 7-zip archiver not found on Dream Two

    Hi, and what Enigma2 image are you using ? That is some BUG in the plugin code.


    The plugin code must evaluate itself and try to find and / or download the 7z archiver.


    1. it tries to find the installed 7z in system as first

    2. then tries to search the feed-server, if found, install

    3. finally, a stand-alone executable is downloaded that does not have heavy requirements for the presence of complicated system libraries (stand-alone 7z-archiver does not need any or only basic packages that are included in almost every Linux distribution)


    If the plugin code has determined that 7z already exists on the system, it will not attempt to install or use it. Maybe the 7z archiver simply can't run because of the plugin's access rights. But there's something else... similar... that doesn't work.


    If possible, please turn on debugging in your Enigma2 distribution (I don't know which one you use). Then call the BUG plugin. And then send me the created debug file (it should be created somewhere on the disk, in the set-top box, but due to the insidiousness of the Enigma2 distribution, the file can be located anywhere).

    Hi. I made minor changes in the shell script - modified items for "oscam.server" file:


    - removed CAID filtering (it will be universal - i.e. for all CAIDs)

    - set group to the default value of 1 everywhere

    - fixed the incorrect insertion of an exclamation point in the services item, even though the services item is not necessary at all for other users

    (if someone would like to remove the services item, then it is also necessary to remove the two exclamation marks listed later in the script)

    - added a cccversion entry there

    Hi maldini75 .


    It's quite a problem. Unfortunately.


    Most of the free test CCCAM servers change their terms of use and also the website code, so it is difficult to always find a suitable and functional CCCAM free server.


    I use one too (edited shell-script "tichestart1.sh"), but I have to keep changing it because there is always a new one being created. You can try it, if you want. Unzip the shell-script and follow the information in the upper part of the script. I note that this is a guide only for experienced IT users or for at least beginning Linux users !

    Nope.


    Chocholousek's computer is only dead :). You have to wait. Unfortunately. A whole new PC workstation must now be prepared from all over again :). The data is backed up, so there will be no problem with the data.


    I don't know why the Picon.cz domain is currently down. The domain belongs to the company Ellano.sk and is managed by chocholousek. But I don't know why it is broken. I will ask Chocholousek if he knows anything about it. I am guessing that it is disconnected because the new picones are not ready yet.

    Hello, what is cccam_ext, what are the config.

    Hi.


    It was enough to use the search on this forum :)
    quick Question!


    So... the "cccam_ext" shows as protocol only in OSCam softcam. It means that the original CCcam client is not used and therefore it is not a communication of the original "cccam" protocol. It is an OSCam, that works as a CCcam client, but this OSCam does not use the original protocol, i.e. "cccam" but uses the "cccam_ext" protocol.

    Hi.


    I finally used a USB-to-Serial adapter... because RJ-11 works on Vu+ only as a diagnostic - during the booting of the set-top box. Then it gets blocked or I don't know what happens... probably there is just no driver for the Linux kernel used in Enigma2 :). I really don't know. It is possible that this serial interface is blocked in the RJ11 connector (on the rear panel), intentionally. It probably only works in the bootloader and not in the Linux system... unfortunately.

    5.0.240626

    Minor improvement:

    - although the use of SNP picons is not very popular, due to their partial support in the plugin, it was necessary to change the search algorithm of all available satellite packages

    - picon designer chocholousek, will now be able to add some other SNP picon packs to the database (but they are still not primarily used in the plugin)




    (download the plugin and more information can be found in the post #1)

    lory94


    Hi.


    There are several errors in the LOG. They arise primarily in the the file:

    "/usr/lib/enigma2/python/skin.py"


    But there is also an error (last error) in the file:

    "/usr/lib/enigma2/python/Components/Converter/NOVAccess.py"


    ...however, this NOVAccess.py file is not on the official Github from the OpenATV team. So it does not come from the OpenATV distribution, but from some third party. Probably the NOVAccess.py file is part of some SoftCAM package. Need to find out what this file comes from. I personally did not find any information on the internet.


    Both files can also come from some pre-installed, external package - from an alternative SKIN.


    matze90


    Hello. Yes, that is typical. Unfortunately, the Linux libraries were updated in your set-top box - to newer versions. Or vice-versa... Oscam binary file has been updated and requires newer libraries, but they are missing in your outdated OpenATV.


    All you can do is add sym-links of the missing libraries that will point to these real libraries - present in Linux.


    libcrypto3 (>= 3.3.0)

    libpcsclite1 (>= 2.0.3)

    libssl3 (>= 3.3.0)

    libusb-1.0-0 (>= 1.0.27)

    I've never had problems with this string and it has always downnloaded me the right and last version of the softcam feed that i usually install on a clean image...

    wget -O - -q http://updates.mynonpublic.com/oea/feed | bash

    Yes, the guy tried to add a base URL (with empty source), using the GUI MENU in OpenATV - as a new feed package source. But that won't work. Only if a specific URL was added with components that exactly specify the OE version (if needed some version) and also that exactly specify the chipset / architecture.

    the real mojo

    You probably just used the wrong URL (via the GUI MENU - in OpenATV).


    Adding a simple URL (http://updates.mynonpublic.com/oea/feed) probably won't be enough... I mean adding such a shortened URL and nothing more.


    I don't know for sure... but I think that there is another folder to be added to the URL - according to the OE version (enigma2 core in OpenATV) and according to the chipset/architecture of the set-top box.


    Anyway... the online shell-script performs more steps in its algorithm. It automatically detects the required enigma2 core version and also detects the chipset/architecture. Based on this information, the shell-script then creates and adds the appropriate feed source to the OPKG manager in your set-top box.

    Hi the real mojo .


    As giopet wrote... please explain what exactly this statement of yours means, because I don't understand:

    Quote

    Software update gets stuck on this link

    You could also add a screenshot of the error you see. Or... at least a copy from the terminal... for example, in PUTTY (opened terminal window): mark the text with the mouse, then when the text is marked, go to the web browser, to the discussion, and use the CTRL+V keyboard shortcut to insert the text. Then... mark the inserted text in the discussion forum and enclose it in CODE TAGs.


    Take a look and try to run the online shell-script for installing new softcam feed, using the debug / verbose argument:

    Hi.


    Exactly so. Just separate them with an empty line for better clarity. It is simple.


    You have just to create 8 these readers in the "oscam.server" file. OSCam alone, then selects automatically from the available readers, depending on which one has which CAID provider and available services. OSCam should handle it himself.


    However, it will help if you know the CAID for individual readers and add a line to specify the CAID everywhere ( https://wiki.streamboard.tv/wi…/Config/oscam.server#caid ). But it is not necessary.


    Also, don't forget to create an internal dvbapi user for local access if you use this OSCam of yours as a softcam-client and at the same time as a softcam+server for your own set-top box.

    It looks like someone tried to connect from several IP addresses. Either it is a dynamic IP address or it tries to attack from several hosts on the internet.


    You can find out the DNS name of each IP address, for example like this command: nslookup 192.168.1.1 . If they are always the same DNS name... then you can to block this DNS name.


    For now, try to create at least a regular account called anonymous in "oscam.user" and set a very strong password of at least 15-20 characters, also with various special characters (underscore, dash, wrapper, ... ) + with some numbers + with a different letter size.


    If the same IPs are always repeated, then disable them on the firewalls of the router or Linux set top box or, as written above, it can also be disabled in Oscam by IP.


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


    The "anonymous" account also shows up with various Oscam errors. Unfortunately, I don't remember exactly which errors. In the case of bugs such as poorly set cascading or reshare. When more than one account is connected at the same time and you have only allowed 1 account (in "oscam.user" file)... the attempt may be reported as a disconnected "anonymous" account. But I really don't know exactly... when this "anonymous" appears with which Oscam bugs.


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


    In Linux (in a set-top box) you can also disable groups of IP addresses... you can already find it in Google... but be careful... for example:

    Block range of IP Addresses
    I am getting bombarded with attempted hacks from China all with similar IPs. How would I block the IP range with something like 116.10.191.* etc. I am…
    serverfault.com

    You can try the older version from OpenPLi-7, which is a bit different. Strange because CCcam is closed code. I don't know where the OpenPLi team got this version of CCcam from. The difference is in the letter "a" in the version. The older version of CCcam softcam from OpenPLi-7 does not contain this letter "a". See Attachment.


    If it doesn't work well, feel free to try OSCam as well - I mean as a softcam client, instead of CCcam. OSCam is reliable in most cases, but with a few exceptions, it causes communication problems (paradoxically, between the same versions of OSCam !). Maybe it will work fine in your case.


    However, you have uClan Ustym 4K: Hisilicon Hi3798MV200 chipset / ARM Cortex A53 processor. So... I don't know. It depends on which version of Enigma2 you are using. The Cortex A53 processor is a bit more complex. It can run in ARM-7 backward compatibility mode as AArch32 mode. However, it can also run in full AArch64 / ARM-8 mode. I assume that OpenPLi-8 runs in the old compatible mode. Try to find out, for example, with the command in the linux terminal:

    uname -a

    ...or try the info from the listing:

    cat /proc/cpuinfo

    Thanks! now need CCcam 3.2.0---

    You probably wanted to write 2.3.0 and not 3.2.0.


    First, find out what chipset / CPU architecture you have in the set-top box :-).


    Then download the appropriate CCcam 2.3.0 accordingly.


    I think that even here on this forum, there should be binaries or installation packages. Binary is probably better + solve auto-start + add one configuration file ("/etc/CCcam.cfg").


    CCcams in attachments come from OpenPLi-8 feed. They are all IPK installation packages.


    Unfortunately for the ARM architecture you will not find v2.3.0 but only v2.3.2. I have not verified how v2.3.2 works, but I believe that it works well. Version 2.3.0 exists probably only for the MIPS architecture.

    Hi.


    Try the CCcam 2.3.0 softcam version... or... as a colleague wrote earlier... try CCcam, which is available on the OpenPLi feed. The OpenPLi team also has softcams on its feed servers (directly).


    On the other hand, it is also a fact that CCcam does not have an open source code ! The code is "secret". Unfortunately, it is not published on any Github or other portals. It is hard-compiled, so no CCcam should differ much from another build (OpenPLi vs OpenATV vs others) - they should all be identical. But it is possible that someone made CCcam 2.3.2 with some dependencies a long time ago. And these binaries for CCcam 2.3.2 are distributed differently among users. Well... and OpenPLi maybe uses the "appropriate" file that will work correctly in their own OpenPLi.


    If nothing helps, try the softcam version CCcam 2.3.0. This version, for me personally, always worked everywhere. All the others, I don't know why, older and newer, always have some minor problems over time.

    Hi.


    BTW, even though this topic is old... I have to mention here that cak7 has already been added to the official OSCam build. So, if a specific DVB provider does not use any specialties regarding cak7, then the official OSCam build should also work.



    SOURCE: https://trac.streamboard.tv/oscam/changeset/11735