Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages

Prefer not to use IPK packages? This tutorial walks you through installing a softcam (OSCam or CCcam) manually on Enigma2 — from PuTTY to the auto-start script.

This tutorial explains how to install a softcam (OSCam or CCcam) manually — useful if you would rather not use IPK packages.

Connecting to Your Box with PuTTY

  1. Find the IP address of your set-top box — check your Wi-Fi router under LAN clients, or look in the GUI menu of the box.
  2. Download PUTTY.EXE to your Windows desktop (if you are on Windows):
    File
    Putty
    PuTTY is an SSH and telnet client, developed originally by Simon Tatham for the Windows platform. PuTTY is an open source software that is available with source code and is developed and supported by a group of volunteers.
    master G
  3. Start PuTTY, enter the IP address of your box, choose the Telnet or SSH connection type, and open the connection. Log in as root; the password is empty by default (just press Enter).
  4. You are now connected to the command line (Shell) on your box. Continue with the instructions below.

Remove the Current OSCam IPK Package

If you already have OSCam installed as an IPK package, you must first stop the service and uninstall the entire IPK package with the following commands (in PuTTY):

Code
top | grep cam                       # to display running processes containing the term "cam", then cancel displaying with CTRL+C
killall -9 <softcam_process_name>

opkg list-installed | grep cam       # you get a list of installed packages that contain the word "cam"
opkg remove <softcam_package_name>   # remove the installed softcam package (oscam/cccam) which you want to replace

Installing the Softcam (OSCam) Manually

1. Identify Your Chipset / CPU Architecture

First, find out what chipset / CPU architecture your box uses: mipsel, armv7, aarch64, sh4, etc. You can also obtain this via the Shell:

uname -m

…or…

[ -d /etc/dpkg ] && dpkg --print-architecture || opkg print-architecture

2. Download the Correct OSCam Binary

Download the OSCam binary you need, depending on the chipset / architecture. If it comes as an archive (.rar / .zip / .7z / .tar.gz), unpack it first. Then upload the binary file to your box via FTP.

3. Open a Connection

If you haven't already, open a Telnet / SSH connection to your box (using PuTTY).

4. Set Permissions and Test

First, set the execute attribute on the binary file, then test whether it works — for example by displaying its information with --help. If it doesn't work, you probably downloaded the wrong binary for a different chipset.

(Note: in Total Commander, via the built-in FTP client, you can set the file attributes to 755 instead of using chmod a+x /path/file in the Shell.)

Code
chmod a+x /usr/bin/oscam
/usr/bin/oscam --help

5. Install the Auto-Start Script

Download the auto-start script, set its run level and enable the execute attribute. Here is the sequence of commands for the Shell:

Code
wget -O /etc/init.d/softcam --no-check-certificate https://github.com/s3n0/e2scripts/raw/master/softcam
chmod a+x /etc/init.d/softcam
update-rc.d softcam defaults 90  # to remove: update-rc.d -f softcam remove
reboot

That's all.

Notes

The standard run level of Linux on most Enigma editions is 3, so we use just the /etc/rc3.d directory — this single run level is sufficient. You can check the current run level with:

runlevel

If the update-rc.d command does not work, use the following command instead:

ln -sf /etc/init.d/softcam /etc/rc3.d/S90softcam

…and to remove it in future, use:

rm -f /etc/rc3.d/S90softcam

If the softcam binary also contains the Webif module, you can verify it is working via the web interface:

  • OSCam Webif: http://box_IP_address:8888
  • CCcam Webif: http://box_IP_address:16001

Unfortunately, in some cases the binary also depends on particular versions of the libraries and modules present in the Linux system, so not every binary will work even if it is designed for your chipset.

If you use OpenATV / OpenPLi, or another Enigma image with similar softcam support (Softcam management), use the wget command to download the softcam file (with the appropriate extension) to the /etc/init.d folder.

Important Note for CCcam

If you need to use this /etc/init.d/softcam script for CCcam, edit the script: in the USER SETUP section at the beginning, change the variables needed for CCcam (or modify as required).

Reference

Like 35 thumbs up 1 Thanks 1

About the Author

Quote from Georg Christoph Lichtenberg

"People need to be taught how to think, not what they think."

¯\_(ツ)_/¯

s3n0 Linuxsat VIP

Replies 13

  • :thank_you2:

    Like 4

  • :hello

    Like 5

  • :don-t_mention:

    Like 4 Thanks 1

  • :smiling face with sunglasses:

    Like 1 OK 1 Thanks 1

  • The ___how_to_manual_installing_Oscam.txt file now contains some info about installing on the "systemd" method ... and not only "init.d" method.


    The "systemd" method is used in Enigma2 distributions, which are based on the new Enigma2 core - close to the original Dreambox. Or on Enigma2 distributions that come from Dreambox. But, of course, open-source Enigma2 distributions usually use the "init.d" method.


    :goodluck:

    Thanks 1 thumbs up 1
  • Quote from s3n0

    Discussion of article Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages:

    Quote
    OMG ... don't use IPK packages. Don't be lazy to learn something. Use the manual installation method to install SoftCams like OSCam or CCcam.

    but why to hate ipk packages when it does it all for urself? I dont get the point of doing it manually :D

  • Mastering the Linux process, for installing any new service (binary file) is unprecedented :).


    The Linux installation-way will work anytime and anywhere... and under any circumstances.


    During the installation via the Linux Shell, if something does not work, you will immediately find out what does not work and why.


    IPKs are packages made up of different (random) people, often people without a good knowledge of Linux.


    IPK is just an installation package and nothing more. The IPK should ensure that everything is "done automatically per user".


    There are already a lot of IPK packages on the internet today, but almost half of them may not work (fit) in your Enigma2 distribution unless they come from a feed-server designed specifically for your Enigma2 distribution.


    Very often, users use these IPK packages downloaded from the internet. But these IPK packages are not always universal (so-called "_ALL"). Even if it is an IPK package that is designed for "all" ("_ALL") Enigma2 distributions and for all CPU/chipset architectures, there may still be a problem. And there can be many of these problems ! For example: The IPK package will include an Oscam binary file that was compiled without USB external reader support or without SSL support. But what then, if the user needs these modules in Oscam ? He must then look for another IPK package ? :) It's really complicated. Unfortunately, Linux is not Windows :). Although Linux appears to be a universal OS, the opposite is true.


    The manual installation method using a binary file is quick and easy. You don't even need a feed server. BTW, many Enigma2 distributions, even on the feed server do not even have Softcams packages. Even then, you must use the manual Softcam installation procedure.


    Running the right Softcam in a set-top box is often accompanied by many problems.


    You may also update your Enigma2 distribution and Softcam will immediately stop working. Even then, you have to use the Linux Shell again to find out why your Softcam doesn't start. If you have your init.d script ready and you know where the binary is, then you can easily find out why it doesn't start.


    Some IPK packages may have forced directory settings for softcam configuration files. Then, when you reinstall Softcam or use a different IPK package, the default directories for configuration files can be used there. But the newly-launched Softcam will not find your previous / alternate configuration directory.


    It could take a long time ... there are really many causes and problems with Softcam startup.


    The average user will usually not encounter problems. If a problem also arises, it will be solved, for example, through a discussion forum and then it will definitely forget about its troubles.


    I have personally dealt with X cases of a malfunctioning Softcam start on set-top boxes. Thanks to the Linux Shell, I have always solved everything. Even less experienced users can then write a question to the discussion, with the error message in the Linux Shell.


    ////// EDIT :


    I would like to add, that some users (although in my view it is nonsense) also requires running multiple Softcams at the same time, on one Linux set-top box. And in this case, again, the knowledge of manual installation of the service (its auto-start) will serve best. Many IPK packages do not address these ideas at all.


    If you want to install 2 x OSCam, it will simply overwrite the original, including the default configuration + without backing up the original configuration... because most IPK packages are really primitive (without an intelligent algorithm in the installation script).


    However, this also applies to the installation of two different Softcams (for example Oscam + Ncam). Many "Softcam-Panels" for managing Softcams in GUI / SKIN do not allow to start, several Softcams at the same time.


    Since I also mentioned the lost Softcam configuration, this is also a common problem for users if they use IPK. Users reinstall the IPK package, but often forget to back up their own Softcam configuration. This configuration is usually silently overwritten, the default configuration, after a new IPK package is installed. Therefore, again, the advantage is to stop the Softcam service, swap the binary in Linux, and restart this Softcam service.


    As you can see ... the method of manual installation of the Softcam service ultimately has a lot of benefits.

    Thanks 2 clapping hands 1

  • Minor update of archive containing information - how to manually install SoftCAMs in Enigma2 set-top boxes.

    Like 1 Sláinte 1

  • hello i need help about softcamstartup on vu zero original receivers and dreambox 800hd se original receiver ....

    i got NCAM on all of them latest version installed but it does not autostart

    any config or ipk or what to do to install i tryed already this command

    Code

    Code
    wget -O /etc/init.d/softcam --no-check-certificate https://github.com/s3n0/e2scripts/raw/master/softcam
chmod a+x /etc/init.d/softcam
update-rc.d softcam defaults 90  # to remove: update-rc.d -f softcam remove
reboot

    i copy and paste this but now the ncam does not even like to start at alll even with restart or anything....

  • Hello.


    You must first edit the "softcam" shell-script. Change the variable

    BINFILENAME="oscam"

    - to :

    BINFILENAME="ncam"

    ... and also rename the binary file in the "/usr/bin" folder to "ncam" if it is not there.


    Also, one of the default configuration files for Ncam is different than in the Oscam case, for example here:

    /etc/tuxbox/config/ncam


    You also have to change the names of the configuration files from:

    oscam.*

    - to :

    ncam.*


    Everything else is described inside the "softcam" shell-script.

    clapping hands 1 Thanks 1
  • Join the discussion! 3 more replies