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.
Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages
- s3n0
- 11 Replies
- 43,960 Views
How to connect with PUTTY to your set-top box:
- Check the IP address of your set top box - find it through your WiFi-router under LAN-clients or find it somewhere in the GUI MENU of your set top box.
- Download the PUTTY.EXE to your Windows desktop (if you have OS Windows):
- Start the PUTTY, put the IP address of your set top box, choose the Telnet or SSH connection type and then open connection:
-login = root
-password = (empty as default - press the ENTER key) - Now you are connected to the command-line (Shell) in your set-top box... continue with the instructions below...
Remove the current softcam - Oscam IPK package:
If you have an Oscam installed as the IPK installation package, you must first uninstall it - stop the service and then uninstall the entire IPK package with the following commands (using the 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 replaceHere is a manual way to install softcam (Oscam):
-- 1 --
First, find out what chipset / CPU architecture is in your set-top box: mipsel, arm_v7, aarch64, sh4, etc. . Information about the CPU architecture can also be obtained via Shell (command line):
uname -m
..or..
[ -d /etc/dpkg ] && dpkg --print-architecture || opkg print-architecture
-- 2 --
Download the Oscam binary file which you need - depending on chipset / architecture. Of course, if it's an archive (.rar / .zip / .7z / .tar.gz), we'll unpack it as first ! Then upload the binary file via FTP connection to your set-top box, namely to this folder: /usr/bin If the name of the binary file is different than simply "oscam" then rename it.
-- 3 --
If you do not yet, open the Telnet / SSH connection to your set-top box (using PUTTY).
-- 4 --
As first, set the execute attribute for the binary file. Then test whether the binary is working, for example by displaying information ("--help"). If it doesn't work, you probably downloaded the wrong binary for a different type of chipset from the internet.
(A note: Even in Total Commander, via the built-in FTP client, it is possible to set the file attributes to 755, instead of "chmod a+x /path/file" in the Shell.)
Code
chmod a+x /usr/bin/oscam
/usr/bin/oscam --help-- 5 --
Download the auto-start script from the Internet, set it to run-level, enable execute attributes ...... here is the sequence of commands to the command line (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
rebootThat's all.
A notes:
- If the "update-rc.d" command does not work, use the following command instead of the "update-rc.d":
ln -sf /etc/init.d/softcam /etc/rc3.d/S90softcam
...to remove (in the future), use the following command:
rm -f /etc/rc3.d/S90softcam
(more information is described at the beginning of the "softcam" script)
- The standard mode of operation of Linux (run-level) on the most Enigma editions is number 3, so we will use just the "/etc/rc3.d" directory and this one run-level mode is sufficient. Of course, the "update-rc.d" command can handle all run-level modes. If there is another default run-level on some Enigmas, you will find it under running Enigma via Shell, with the command:
runlevel
- If the softcam binary also contains the Webif module, you can verify functionality via Webif:
OSCam Webif: http://box_IP_address:8888
CCCam Webif: http://box_IP_address:16001
- Unfortunately, in some cases, the binary file also depends on different versions of the libraries and modules present in the Linux system. So ... not every binary works, even if it is designed for your chipset - CPU architecture. Then you need to find a binary that will work in your Enigma distribution with the dependencies of the required versions of libraries and modules. In some cases it is sufficient to create a symbolic link between versions of libraries, but this is not recommended (there are possible compatibility issues).
- If you use OpenATV / OpenPLi, or another Enigma based on similar Softcam support (Softcam management), then use the "wget" command to download the "softcam" file with the added extension to the "/etc/init.d" folder .CCcam "or" .oscam ". In this case, however, you will not use the "update-rc.d" tool! You can then simply activate a specific Softcam via the GUI-MENU in Enigma. Example for OpenATV: blue button on RCU -> Softcams -> use the left / right arrows to select the required softcam and activate it.
Important note for CCCam:
- If you need to use this '/etc/init.d/softcam' script for CCcam, please make changes by editing this script - in the "USER SETUP" section at the beginning of the script, change the variables needed for CCcam (or modify as needed)
About the Author
Quote from Georg Christoph Lichtenberg"People need to be taught how to think, not what they think."
¯\_(ツ)_/¯
s3n0
Linuxsat VIP
Replies 11
s3n0
s3n0
:hello
s3n0
:don-t_mention:
s3n0
s3n0
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.
johnvucz
but why to hate ipk packages when it does it all for urself? I dont get the point of doing it manually :D
s3n0
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.
s3n0
Minor update of archive containing information - how to manually install SoftCAMs in Enigma2 set-top boxes.
DemoUser
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
i copy and paste this but now the ncam does not even like to start at alll even with restart or anything....
s3n0
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.