Nope.
Please install this Softcam-feed into your Enigma2-OpenATV as first.
After successful installation, another feed-source will appear (a new group of available packages, among plugins). There you will download the required Softcam.
Of course you can also use the Linux Shell:
opkg update
opkg list | grep -i "oscam"
opkg install <package_name>You can download the latest Oscam-trunk (the latest version of trunk is 11704).
OK... ddinc ... now a little off topic:
For what purpose do you actually need to "kill" or "restart" the Oscam process ?
:)
So what ? All is done ?
Which solution ultimately works in your case ? In case someone comes and finds this discussion thread ... maybe it will help other users :) ...in the future.
How do you know it doesn't work ? This "sysctl" only stop the process but leave it in system memory. Test if Oscam-Webif works. If it doesn't work, then Oscam is stopped.
Hi.
You could paste a copy from the Linux console into the CODE TAG. It's then clearer.
Also, the "killall" command is unfortunately not quite universal and may behave a little differently, in different versions of it (BusyBox complex versions as well as in full-fledged Linux versions). In some versions, the signal number is not used, but the signal name, such as:
killall -SIGKILL oscam_11704
And somewhere I think the hyphen in front of the signal must not be used. I don't remember exactly. Sorry. But I know it's a mess with the new versions.
You can also use the "kill" command to kill processes, not just "killall". However, then you need to find out all PID numbers (values representing the process number). For example, as follows:
kill -n 9 $(pidof oscam_11704)
- or :
kill -9 $(pidof oscam_11704)
- or :
kill $(pidof oscam_11704)
(It really depends on the version of your "kill" command (or rather "kill" tool) that how it will behave.)
However, using killall and kill is very difficult on new Linux systems (Dreambox firmware) or even compared to old versions, many things always change! Therefore, it is better to use the standard path. If you show me an IPK package for your Oscam, I'll unpack it and tell you exactly how Oscam restarts in your case :) - based on the unpacked IPK package (using a 7-zip archiver you can unpack).
So... again... you must first know what startup principle is used on your Linux system. Maybe sysctl is not used for Oscam but systemd. You have to find out first.
Depending on what you copied from your console, you still haven't tried the "init.d" scripts !
I dont know all Enigma2 distributions in the world and I dont know in which Enigma2 there are exactly what options (installed components and tools of the Linux system).
OpenDreambox 2.5 should use sysctl, if I'm not mistaken. But the systemd / init.d service launcher can also be used there.
Or maybe "start-stop-daemon" is also used in your case. I really do not know. Linux systems are very extensive in this regard - in terms of processes and their management by the system administrator.
Hi.
First you need to find out which launcher for Oscam is used in your system (sysctl / systemd or maybe "init.d" scripts). Accordingly, it is appropriate to drop or restart the service accordingly.
If you are using an "init.d" script, then there should be functional parameters for that script, such as start | stop | restart, for example:
/etc/init.d/softcam restart
-or:
/etc/init.d/softcam.oscam restart
If you want to list files that contain the word "cam" in the file name (inside the "/etc/init.d" folder), use this command:
ls -al /etc/init.d/*cam*
Of course, you can also "kill" the process, but first find out its name, for example like this:
ps -aux | grep -i "cam"
-or:
ps | grep -i "cam"
And here in the list you will probably see your Oscam and its name. Then it should be enough to use a hard kill:
killall -9 <process_name>
When using the "ps" command, you may notice the entire command-line of your Oscam, i.e. including the arguments placed behind the Oscam binary file. To start Oscam again, use exactly the same command-line including the same arguments. For example:
/usr/bin/oscam -b -r 2
Good Luck :)
/// EDIT:
Are you using OE2.5 ?
Oh sorry... so then you probably use "sysctl" and not "init.d", for purpose of the start | stop | restart services. This tool is used a little differently. Of course, you can use the sysctl command to control processes (including the oscam process).
Example: systemctl restart <service_name>
Here is more info: https://crunchify.com/systemd-…respawn-process-linux-os/
Guys, please stop constantly speculating with new test versions of Enigma2 / OpenATV 7.X.
These new versions are still under development - beta or alpha (I don't know exactly).
Of course, these versions of OpenATV contain lots of BUGs !!!
If you find a BUG, you can report it (if it has not been fixed yet) on the discussion forum http://www.opena.tv, where on the main page of the discussion forum search for the version "7.0" or "7.1" via the web browser (press CTRL + F) and you can then write reports to this discussion thread.
These are versions based on Python 3 and are not yet officially released. Support for Python 3, on the Enigma2 distribution side, is still very weak. However, this should change over time (I think).
I don't understand why someone installs a test version of Enigma2 and then shouts at the world that it doesn't work. I see it everywhere every day.
LOL, why don't you try to look for an existing configuration - via a command in the Linux Shell ?
find / -iname "oscam.conf"
If you used the compiler to compile Oscam online, then probably the configuration files do not exist in your Linux and you have to create them + upload them yourself. Alternatively, download them from the Internet and then move them to the appropriate folder.
Here's how to find the default configuration components in standard Oscam:
(to one of the folders, you can upload your configuration files for oscam and if the folder does not exist, create it)
See also here:
Probably the files in your Oscam are misconfigured ? I mean the "oscam.server" file.
Or maybe you have a card tucked in there ? Usually the cards are inserted with the chip facing each other.
I don't know exactly how ... but it's best based on the behavior of your card ... that is, via Oscam-Webif LOG ... but I can't help you with that, because I don't know CONAX very well + I don't know your satellite decoding card at all.
Hi again.
Follow this older thread please:
According to an old discussion, you should also have the following in the Oscam configuration, in the oscam.server file:
caid = 0B00
emmcache = 1,3,2
pincode = 0000
ident = 0B00:000000
ecmwhitelist = 0B00:4E,5D,6E,66,69,FFFFFFFFI also found information on Google (https://www.google.com/search?q=oscam+settings+for+DigitAlb) that some DigitAlb channels have been moved to IRDETO 2 encryption mode (i.e. CAID 0609, at 10887Hz frequency), from the original CONAX mode (CAID 0Bxx). Isn't this your case too ?
Do you also have... in your Oscam... as I mentioned last time... a properly set up... enabled and functional AutoUpdate/AU (for writing EMMs packets to your card) ?
Hi.
CAID 0B00 is a very comprehensive description of the card.
You must enter the name of the provider or the country. Then someone who knows your provider may be able to advise
This CAID 0Bxx represents the Conax encoding type. You get an EMM packet write to your card from the AV-stream, for the purpose of AutoUpdate (AU) of your Entitlements... and then it should work. However, in other circumstances, various problems may arise, usually with card sharing protection (too much ECM decoding requests) or specific other channel decoding protection (ECM decoding needs the pairing - between the card and the SoftCAM).
I do not know. I'm not an Oscam developer ;-). I don't even know exactly what needs to be modified in Oscam. I am not interested in DVB programming either.
Yes, I know about Oscam version 11523 (Layer 2B). But I don't use it, so I can't advise configuring this modified version 11523. The standard Skylink-Irdeto configuration is probably used there, as is the case with every Oscam. I don't know for sure.
As for the reader with an external USB connection, each can usually operate in multiple modes. So Oscam does not always directly support only the smart-reader protocol. It should be possible to connect it by another method. I don't remember how. Try searching the discussion forum called your external USB reader. It's another topic, too, and it doesn't belong here anymore.
And in general... this thread should be deleted. Support for modified / private Oscams is prohibited. Only support for mainstream Oscam development is allowed. :-/
Sorry, I don't know the Hungarian channels from Skylink provider. I have no experience with them.
But it is possible that they also work on the new Irdeto Layer 2B mode, as mentioned above.
However, you need to use a modified (non-public) Oscam, unfortunately. The risk of using it is up to you. Maybe it will be OK, maybe not. I have no idea, I'm sorry.
I assume you have paid the Hungarian package (this is paid as an additional Skylink package).
This is not the source code of Oscam, which you attached above - as a binary file (already compiled by Oscam from an unknown source).
I would like the source code, which is also stored somewhere on the internet and which can always be checked, or even downloaded as SVN and compiled it myself.
EDIT:
This is just an explanation of what principle Irdeto Layer 2B seems to be working on.
Is not private oscam,publicly available at the Czech Forum.
There is only one official Oscam and its source code is also publicly available:
Unfortunately, there is only a modified Oscam on the Czech discussion forum. However, if you have its source code, I'll be happy to look at it. I want to see all the changes that have been made compared to the original Oscam (mainstream development of Oscam). I hope that I will not find any opening ports or sending "other data" to the internet.
There are many discussion forums where you can find various modified Oscams.
However, you never have a guarantee until you check the source code for the modified Oscam yourself and compile it yourself (for yourself). Only then are you sure that everything is fine. Even the Oscam binaries available on the Internet are a small threat. Because even these supposedly official binaries can always contain some malicious code. You are never one hundred percent sure. Unfortunately. Welcome to the world of Linux :).
Hi.
You can download this Oscam 11704 from tomek6680 attachment, inserted above: RE: Need help with Skylink ice card.... (post No. #5) or find it even everywhere on the internet.
The LOG from Oscam-Webif would really help. I have no idea what exactly is not working for you or what the problem is with you. You must describe the problem in detail.
If you would like, in the attachment you have a basic, functional configuration for Oscam with CAID 0624 (for Enigma2 set-top box with the internal card reader).
/// EDIT :
I still forgot. Unfortunately, support for the private Oscam (modified for special purpose) is prohibited on the discussion forum.
So... I don't know... if this can be considered a private Oscam or a public one. Because he is public, this code is not public. Unfortunately, the author did not include his code in the official Oscam source code on the internet.
Modified Oscam from an unknown source (third party) may contain malicious source code... or... for example, may to send some of your personal information to the internet (somewhere)... or they may share your official satellite card with third parties (and you have no idea about it). Therefore, support for the private Oscam is prohibited in the discussion forum.
