Why would you want to replace a definitely working oscam with a different one you obviously didn't even compile yourself and that just "might work"?
I don't get it why people are that keen on going the hard way ...
If there are cams on an image's feed already, replacing them by some generic and usually silly built 3rd party cam packages or ipks can hardly work any better than the cams provided by the image team and built/compiled for that image.
There has never been a protocol "oscam".
oscam has no own protocol, the one that is closest to being an oscam native protocol is cccam, because oscam uses an extended variant of it if both sides use oscam.
And I don't get the problem:
Yes, the sample config comes with plenty of sample readers, that's because it's a sample config :)
Feel free to delete all the readers you do not need and add your own ones.
Configs are in /etc/tuxbox/config/oscam-stable (Based on the version you mentioned, I assume you installed oscam-stable), not in /usr/keys/somewhat anymore.
It's time to trash the Azbox:
No matter what you do, it won't be able to decrypt Sky (and certain other stations) anymore.
The reason is, that it's not the softcam configuration that messes things up on this box, but the firmware itself:
Even if you manage to configure oscam correctly, the xcas of the Azbox will still fuck things up for you.
Unless someone comes up with a patch for Azbox's xcas, there is no chance. Game over.
mv Azbox electronic_waste
What problem?
CCcam being a PITA?
Any, but people insist on continued usage of this garbage.
Edit:
I stay corrected in one point: On Astra, Sky Bundesliga UHD and Sky Sport UHD actually really don't work using CS.
It works for me, as I have Cable Internet and thus also some cable tuners and on Unitymedia cable it works using CS.
CCcam is a PITA anyways.
UHD channels do work, just like any other channel, except for Sky1 HD.
Changes on the feed:
- oscam-emu now also ships with current SoftCam.Key (That one made by BIGMAN_58)
- SoftCam.Key updated to 2019-07-13 in oscam-smod and oscam-emu
- oscam-smod now auto-detects Sogno 8800HD and Unibox HD eco+ boxes and auto-enables "boxtype = sogno" on these (Without this: Only audio, no picture).
Concerning SoftCam.Key:
Note that SoftCam.Key will not get updated fully-automatic if you update the softcam package, as SoftCam.Key is considered being a config file and changed config files are never overwritten ...
And as the emu writes the PowerVu AUs to SoftCam.Key, SoftCam.Key is always seen as "modified by the user".
So as SoftCam.Key also gets updated "over-the-air", I suggest: If things work, don't touch them :)
But if they stopped working and you need a new SoftCam.Key, you can copy /etc/tuxbox/config/oscam-smod/SoftCam.Key-opkg to /etc/tuxbox/config/oscam-smod/SoftCam.Key or - when using oscam-emu - /etc/tuxbox/config/oscam-emu/SoftCam.Key-opkg to /etc/tuxbox/config/oscam-emu/SoftCam.Key respectively.
BTW: 11530 is current :)
Give the servers some time to build it though ...
hello I would like to know which oscam 11529 I have to install on my Xtrend et 8000 image OpenAtv 6.3. Thank you.
Just get the one that is on the feed ...
You will need to install the softcam feed first though, as described here: OpenATV SoftCam Feed
I could recommend OpenPLi.
It's perfect for those who hate the easy way :)
You need a real card, local or shared, in order to watch SRF.
Watching SRF using only an emu stopped working several months ago.
guide how to install it into octagon sf8008 ? thank you
Which Image?
In OpenATV, there is the latest NCam on the secret-feed.
This feed should also fully work on OpenEight.
My parents teached me not to lie and thus I gave you the facts.
Reading a hard-coded version number from some script/config file is simply the silliest way to print "something".
Even making the output read "oscam-emu someversion" (and I mean "someversion" literally) would be better, because at least it's more probable correct.
If you want real information, you have to ask oscam about its actual version.
I showed two ways to this information (Where the way using /tmp/.oscam/oscam.version is the more reliable).
If you just want some static bullshit to fill your screen, which is wrong as soon as the user copies the script and uses it for his own oscam, you can as well write "foo bar" as version info.
Display MoreWe do definitely need some periodic auto cam check though. (like the original plugin)
I run a 3rd party script to update my cam files from a 3rd party source.
Every time I run this 3rd party plugin, I have to manually go into softcams and start the cams again.
This scenario also happens if you change the details of a cam file.
You have to manually restart softcams again.
What files are you referring to as "cam files"?
The binary? The config files?
OpenPLI's startscripts have the version name in the scripts and that facilitates the skinners, running commands within the converters to get the version from /tmp does not!
The softcams.inc used by me to auto-generate start scripts is the very same as on OpenPLi.
The resulting init.d for CCcam is:
#!/bin/sh
case "$1" in
start)
ulimit -s 1024
exec start-stop-daemon -S -x /usr/bin/CCcam
;;
stop)
exec start-stop-daemon -K -R 2 -x /usr/bin/CCcam
;;
restart|reload)
$0 stop
sleep 1
$0 start
;;
version)
echo "2.3.2"
;;
info)
echo "CCcam 2.3.2"
;;
*)
echo "Usage: $0 start|stop|restart"
exit 1
;;
esac
exit 0It has no header at all!
You can invoke the init-script with parameter "version" or "info" though, which will output the hardcoded version information:
root@quadbox ~ # /etc/init.d/softcam.CCcam version
2.3.2
root@quadbox ~ # /etc/init.d/softcam.CCcam info
CCcam 2.3.2But this also works for my oscam/ncam start script:
root@quadbox ~ # /etc/init.d/softcam version
oscam-smod-r11529 with IPv6
root@quadbox ~ # /etc/init.d/softcam info
oscam-smod-r11529 with IPv6Yes, I didn't strip "oscam-" from output for "version" parameter yet ...
You should be aware though that certain 3rd party CAM packages come with scripts that only interpret "start" and consider any other parameter as "stop", so the skin would stop the CAM permanently as soon as the user installs such a CAM.
This header is by no means meant to be filled with stuff like that.
For complete Linux distributions, the values here allow to detect how services depend on each other (or not) in order to determine an optimized boot order.
The minimalistic Linux on the box (yocto) doesn't actually intepret these lines when adding services, but as a matter of good style I added those headers anyways.
And also this header is not suitable as an information source for skinners either unless you want to see your box crash, just because of trying to gather nonsense information:
As nobody is forced to write proper headers in init.d scripts on E2 boxes, most people actually don't!
I could add these info inside the scripts for CAMs from the feed, but the assumptions of skinners would fail as soon as someone writes his own script or uses 3rd party ones, which is perfectly ok.
If you want more detailled info on the oscam version that is currently running, use the Python counterpart of
cat /tmp/.oscam/oscam.version | grep Version: | sed 's#Version: *##'Result:
root@quad4k ~ # cat /tmp/.oscam/oscam.version | grep Version: | sed 's#Version: *##'
oscam-smod-r11529Huh?
You get to see the full name .... "oscam-stable", "oscam-trunk", "oscam-smod" or "ncam".
Some news:
CAM related inside the oe-alliance core:
This change is in all OpenATV 6.2/6.3 images 2019-07-07 or later and in some images already on 2019-07-06.
Related to CAMs on the feed:
As SoftCam.Key couldn't be overridden by own ones from the user, I disabled this, so you can use own SoftCam.Key again.
The package ships with the (hopefully) latest one by BIGMAN_58. If you have better ones to suggest, I'm open to requests.
This version has Long ECM and Sky DE support patched in, but it's still recommended to switch to decent newer cams like oscam or ncam.
mgcamd for arm required libxcrypt which was missing on the feed, so the package couldn't be built at all, also preventing all other cams for aarch64 to be built for OpenATV 6.2.
https://github.com/oe-alliance…718129b606ce36119a0a1bcc7
Please note that the development focus has long shifted to 6.3 and 6.2 will soon be EOL, that's why nobody noticed :)
NCam development moved to https://github.com/OpenVisionE2/NCam
I checked back with fairbird if the new repo is legit and he confirmed.
scam and wicardd have been added to the feed (mips32el only).
That "copy binary blah to blubb, chmod 666, ..." stuff is only confusing people:
Those who can handle these steps don't need advise on how to do that!
Using softcams from the secret feed makes sure you get a SoftCAM compiled for your image and your architecture and it's the most transparent source you can have, the recipes can be seen here:
https://github.com/oe-special/recipes-sfeed
All those softcams from IPKs or ZIPs in forums or other download databases are far less trustworthy, as nobody knows who made them and how, using which toolchain, with which additional patches ...
Those people that can really create a softcam binary that is even more trustworthy than those from the feed, which means having to compile it on your own - most definitely also know how to write or adapt an existing init.d-Script.
