OpenATV SoftCam Feed Discussion Thread

Hi.

Same issue here x3x2x1 :-(

I have been tested lot of new feed.

Notice: The new feed, doesn't work with the new feed of OpenATV 6.2 or OpenATV 6.3 for Oscam version "enigma2-softcams-oscam-all-images_11.523-emu-r796-arm+mips_all.ipk" or "enigma2-softcams-oscam-all-images_11.522-emu-r796-arm+mips_all.ipk".

To get oscam version 11.522 or 11523 working, it only works for older feed of Open ATV 6.2 or Open 6.3.

I've been tested Open ATV 6.2 "openatv-6.2-mutant51-20190611_usb.zip" and that works 100% with new version of OSCAM.

I guess we have to wait for a new feed of OpenATV 6.2 or 6.3 who works for a newer version of OSCAM.

****** Let us hear from others. ********

What have you done to make it work?

Please tell us in detail how you have solved the problem - so we others can benefit from your opinions :-)

Please send download links abu baniaz :-)

You wrote: "If you download oscam trunk, it will be the very latest. (up to 24 hour delay)".

Where did i find a download link for that softcam ?

????

Some news:

CAM related inside the oe-alliance core:

• The softcam (any softcam) gets now started later (but still before enigma2), as some binary blobs behaved badly when being started very early.

  
  

  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.

  https://github.com/oe-alliance…ae95c40e03f19e891224736d3

  https://github.com/oe-alliance…ad7aa5c045ed82945c5476c1e

Related to CAMs on the feed:

• oscam-smod no longer comes with SoftCam.Key compiled in

  
  

  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.

  https://github.com/oe-special/…02ab21d38e1b884a5d7fa8cae

• For sh4 boxes, mgcamd was bumped from 1.45b to 1.45c

  
  

  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.

  https://github.com/oe-special/…4169f3b685aee7badabc031bd

• A build error for all aarch64 cams for OpenATV 6.2 has been fixed:

  
  

  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 :)

• Using new source repository for NCam

  
  

  NCam development moved to https://github.com/OpenVisionE2/NCam

  I checked back with fairbird if the new repo is legit and he confirmed.

• Not that new, but still unposted: scam and wicardd

  
  

  scam and wicardd have been added to the feed (mips32el only).

  https://github.com/oe-special/…ce39347ffa091854f0a8f65e6

A quick question:

Why was the oscam version name removed from the startscripts? All oscam versions are now reported as simply oscam and the users have nowhere to see what version they run unless they enter the webif!

On the old openATV softcam system the full cam name could be read from .emu files or the confic.actcam params, however the new startscripts for both oscam and ncam only provide a short and long description which is always the same and lacks important info.

If a camname field with the full name (etc oscam-emu 11529.746) is added in the startscripts the skinners will also have a converter available to read the value and render it to skins.

Please take that into consideration, it's not as a minor issue as it may seem...

Thanks in advance!

Huh?

You get to see the full name .... "oscam-stable", "oscam-trunk", "oscam-smod" or "ncam".

No, that's not the full names, there's no version and there's nowhere for skinners to read even these values so that they render them on skins....
A converter cannot do the os.listdir function in real time without CPU exhaustion to read these names, the only solution is to read the values from the scripts and they are not there!

For instance this is the start of the script when using oscam, oscam-emu, oscam-trunk

### BEGIN INIT INFO
# Provides:          softcam
# Required-Start:    $local_fs
# Required-Stop:
# Should-Start:      $time $remote_fs cardserver
# Should-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: oscam
# Description:       oscam SoftCAM, card reader and server.
### END INIT INFO

All three versions have the exact same segment, so if a skinner uses that to read the cam name has only the short and description fields to do so.

A modification in Short-description from

# Short-Description: oscam

to

# Short-Description: oscam-emu 11529.746

would suffice for skinners to have the correct version readable on skins.

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-r11529

We 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.

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! So why you'd think the header containing the full camname is nonsense information is beyond me...

Anyway, I'll try to write code with reading from oscam.version, but I don't think it'll work as it should!

BTW why is there a cardserver section, is there any cam today that works this way that softcam won't cover? Seems way too redundant! For what is worth, if the system can run both a softcam and a cardserver then the latter could be named softcam2 and allow this function with two softcams...

Quote from glamour_services

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 0

It 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.2

But 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 IPv6

Yes, 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.

Quote from KiddaC

We 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.

Display More

What files are you referring to as "cam files"?

The binary? The config files?