105 replies to this topic

[WanWizard]

No, it is on purpose that I made that change, as @foxbob reported that the binary doesn't start if it has a different name from "mgcamd".

 

opkg keeps track of installed files, so it can be removed if you uninstall. If you installed if before my change, it will try to remove mgcamd135a, which no longer exists.

[blzr]

binary starts perfectly regardless the name, I tested this ;-)

the other way around to fix this multiple mgcamd versions issue would be to eventually hardcode camname in camstart / camstop scripts to "mgcamd" in mgcamd-softcam.inc

CAMSTART ?= "exec start-stop-daemon -S -b -x /usr/bin/${CAMNAME}"
CAMSTOP  ?= "exec start-stop-daemon -K -o -R 2 -x /usr/bin/${CAMNAME}"

but I like my 'fix' better somehow...

 

[WanWizard]

Your "fix" just reverts my change of a few days ago. Which @foxbox reported didn't start.

 

So he has a different problem and the original recipes were ok?

[WanWizard]

Better revert this one then, and everything should be back to how it was: https://github.com/O...575e1d79085d301

[foxbob]

Rebuilt with the proposed change @blzr.I installed it using the new image the plugin was installed without errors.I added my settings - it worked.I deleted the plugin without errors,but there was still data in the cache,because after the restart of Gui there was still a picture.After a full reboot everything is normal.

[WanWizard]

I still don't understand what exactly is the working version.

 

@bzlr says everything worked fine, but if I start /usr/bin/mgcamd135a on the commandline, I get a "file not found" error, which does not appear if I rename it to /usr/bin/mgcamd ? Which is what @foxbob reported too.

 

So, @bzlr, you say the different mgcamd versions work fine in 8.0-release (which is the same as develop was a week ago)?

[blzr]

well, after lates changes you have in startup script:

CAMSTART ?= "exec start-stop-daemon -S -b -x /usr/bin/${CAMNAME}"

and you have hardcoded binary name to mgcamd:

install -m 0755 ${S}/mgcamd.${TARGET_ARCH} ${D}${bindir}/mgcamd

and for mgcamd 1.35a:

CAMNAME = "mgcamd${MGCAMVER}"

MGCAMVER = "135a"

so it's rather not surprising that /expected/ binary is not found by startup script (?)

 

I'm not sure what the actual problem was that caused this change to hardcoded binary name?

Edited by blzr, 24 May 2021 - 19:38.

[WanWizard]

The report of @foxbox was from BEFORE that change, I understand that it now doesn't start, but I don't want want to keep changing.

 

So, either it works fine if the binary is called ${CAMNAME}, in which case I revert my commit and @foxbob has a different problem, or I keep the commit and fix the typo you mentioned.

[HPPli]

Still this message with OpenPli Develop;

 

mgcamd135a: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by mgcamd135a)

 

libcrypto.so.1.0.0 will be into /usr/lib/ what wil be the meanining of version `OPENSSL_1.0.0' not found ?

[blzr]

The report of @foxbox was from BEFORE that change, I understand that it now doesn't start, but I don't want want to keep changing.

 

So, either it works fine if the binary is called ${CAMNAME}, in which case I revert my commit and @foxbob has a different problem, or I keep the commit and fix the typo you mentioned.

no idea why @foxbob reported problems, for me mgcamd135a started fine after you included older ssl libraries in libcrypto-compat, either with generic softcam start script, or later with tweaked mgcamd startup script...

 

Still this message with OpenPli Develop;

 

mgcamd135a: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by mgcamd135a)

 

libcrypto.so.1.0.0 will be into /usr/lib/ what wil be the meanining of version `OPENSSL_1.0.0' not found ?

definitely should not be the case in current develop, is your image up-to-date?

do you have librypto.so.1.0.0 binary or symlink to libcrypto 1.1 in /usr/lib?

what libcrypto-compat package version is installed?

[cope]opkg info libcrypto-compat[/code]

 

 

 

 

[HPPli]

We use latest nigtly-Develop and the inf of "libcrypto-compat" will show;

 

root@gbue4k:~# opkg info libcrypto-compat
Package: libcrypto-compat
Version: 1.0.2r-r0.0
Depends: libc6 (>= 2.30)
Provides: libcrypto-compat
Status: unknown ok not-installed
Section: libs/network
Architecture: cortexa15hf-neon-vfpv4
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: 0830e0ec7594002669fef2ddea9267bd
Size: 564102
Filename: libcrypto-compat_1.0.2r-r0.0_cortexa15hf-neon-vfpv4.ipk
Source: libcrypto-compat.bb
Description: Secure Socket Layer - Backward Compatibility package

Package: libcrypto-compat
Version: 1.1-r0.8
Depends: libcrypto1.1, libssl1.1, libxcrypt-compat
Provides: libcrypto0.9.7, libcrypto0.9.8, libcrypto1.0.0, libssl0.9.7, libssl0.9.8, libssl1.0.0
Replaces: libcrypto0.9.7, libcrypto0.9.8, libcrypto1.0.0, libssl0.9.7, libssl0.9.8, libssl1.0.0
Conflicts: libcrypto0.9.7, libcrypto0.9.8, libcrypto1.0.0, libssl0.9.7, libssl0.9.8, libssl1.0.0
Status: install ok installed
Architecture: cortexa15hf-neon-vfpv4
Installed-Time: 1620741454

[blzr]

hmm, looks that you have older (but higher) version installed that incudes only symlinks, version 1.0.2 is the latest and includes older binaries...

probably opkg upgrade refuses to "downgrade" the package (?)

 

maybe try:

opkg install --force-reinstall libcrypto-compat

[WanWizard]

If you have an old(er) develop then yes, you need to do this (or remove / reinstall ).

 

I always flash instead of update, so I never see issues like this (also, have no use for mgcamd, so I can't test it myself).

 

I have now reverted some of the changes, and only kept the init script that @foxbob posted earlier, which does some mgcamd specific things (different start parameters, delete ecm files, etc).

[kamaxx]

Hi all;

 

I flashed developer image on vuduo 4k and Mgcamd does not work

I need to mgcamd1.46 emu like @foxbob.

 

All oscam,cccam and wicardd works well but mgcamd is off.

 

PS:I have just read all on this thread and I applied libcrypto.so.1.0.2 and libssl.1.0.2 

Attached Files

•  usr.rar   966.51KB   25 downloads

Edited by kamaxx, 13 June 2021 - 16:18.

[WanWizard]

mgcamd in develop has been setup according to Foxbobs script.

 

I have noticed that if the binary isn't called "mgcamd" it refuses the start, but other uses have contradicted that, so maybe that is your problem too?

[kamaxx]

@WanWizard;

 

 

You were right and I did not realize that clue

 

Mgcamd last build v1.46-r3 version works now and I think It needs right priority parameters to speed up.

 

 

Attached Files

•  1_0_1_DB3_2D50_13E_820000_0_0_0_20210617200843.jpg   54.58KB   3 downloads
•  mgcamd_arm_openpli.rar   339.17KB   40 downloads

Edited by kamaxx, 17 June 2021 - 18:12.

[WanWizard]

So you are confirming my observation that the binary needs to be called mgcamd,  and not something else?

[blzr]

binary can be named anything you want, the point is, its name must match exactly the name in given softcam startup startup script (and vice versa)

that was my observation ;-)

Edited by blzr, 17 June 2021 - 18:56.

[WanWizard]

That seems obvious.

 

My problem is that if I rename the binary from "mgcamd" to something else (doesn't matter what), and than manually start it on the commandline, it crashes with "file or directory not found", like it wants to open itself for decompression or so.

 

If I rename it back, it starts without problems.

[kamaxx]

So you are confirming my observation that the binary needs to be called mgcamd,  and not something else?

Yes,Indeed !

 

I only had changed and updated libcrypt abd libssl files under /usr/libs

 

I maybe wrong but I suppose This emu can only work with  "mgcamd" key word which builded by owners.So I found "mgcamd" into binary file.

 

Most of channels can not decode but Right values under priorities are fast. I hope I can rearrange priority magic.