10 replies to this topic

[lex7791]

Hello good morning everyone!!!!!!!

I have Zgemma H7S and also i have a plugin(it is special emu for opening some channels) it called zcamd.i will attach down.

It worked in vuzero4k and all vu+ and other 4k receivers with openpli(all versions of openpli) BUT in Zgemma not worked

It says ...

-----------------------------------------------------------------------------------------------------------

root@h7:~# cd /tmp
root@h7:/var/volatile/tmp# opkg install enigma2-plugin-softcams-zcamd_0.30b-open
pli_armv7ahf-neon.ipk
Not selecting enigma2-plugin-softcams-zcamd 0.30 due to incompatible architectur
e.
Unknown package 'enigma2-plugin-softcams-zcamd'.
Collected errors:
* opkg_solver_install: Cannot install package enigma2-plugin-softcams-zcamd.

----------------------------------------------------------------------------------------------------------

Can you please help me ? what is happening to Zgemma and openpli.

I have install the plugin in openatv(atv zcamd version arm) and it works.

only in openpli not works.

Thank you very much!!!

Attached Files

•  enigma2-plugin-softcams-zcamd_0.30b-openpli_armv7ahf-neon.ipk   290.41KB   55 downloads

[WanWizard]

The H7 isn't an "arm7ahf-neon" box, it's an "cortexa15hf-neon-vfpv4" box. I can't comment on what other images do, this is how the manufacturer defined it in their BSP.

[Persian Prince]

Another fork of OSCam for watching PayTV?

[athoik]

The OE-A are modifying the opkg-arch-config (meta-oe/recipes-devtools/opkg/opkg-arch-config_1.0.bbappend) in order to add more archs in /etc/opkg/arch.conf


In order to fix problem modify manually the /etc/opkg/arch.conf and append the following line.

arch armv7ahf-neon 100

[athoik]

Another fork of OSCam for watching PayTV?

AFAIK Yes, that's right. zcam is a modified version of oscam. Not just name, but also modified newcamd protocol, automatic download of settings from server based on unique hash created (from mac, model, cpu and few other files).

Just run it using strace

Edited by athoik, 16 July 2018 - 18:21.

[WanWizard]

The OE-A are modifying the opkg-arch-config (meta-oe/recipes-devtools/opkg/opkg-arch-config_1.0.bbappend) in order to add more archs in /etc/opkg/arch.conf

 

Since when are different arch's fully compatible with each other? This looks like the proverbial canon to kill a mosquito...

[athoik]

The OE-A are modifying the opkg-arch-config (meta-oe/recipes-devtools/opkg/opkg-arch-config_1.0.bbappend) in order to add more archs in /etc/opkg/arch.conf

 
Since when are different arch's fully compatible with each other? This looks like the proverbial canon to kill a mosquito...

Who cares? Users are happy.


For sure, mipsel binary packages are not compatible with arm. Although most closed ipk's around usually contain just py(o) files. Those will work!


Adding armv7ahf-neon on cortexa15hf-neon-vfpv4 is super fine. Actually it won't harm if we had such command for all arm.

do_compile_append_arm() {
    echo "arch armv7ahf-neon $priority" >> $archconf
}

[WanWizard]

I care, and I am dead against it.

 

If the plugin only contains python files, it shouldn't have a arm arch in the first place, so I don't see why we should fix the shit work of someone else.

 

Sooner or later a user installs something this way that does break something, and they we're of on a ghost chase. No, thank you.

[Erik Slagter]

From a pure technical point there is no harm in installing armv7ahf-neon on cortexa15hf-neon-vfpv4 and v.v. Using our OE and gcc, they're really the same.

 

But, if all packages are generated like they should, and users are not going to try foreign packages not built by our OE, then this is academic anyway.

[lex7791]

You are the best team!!!

[Dimmie]

What is better about zcamd compared to oscam ? And where is the website to download the different versions of Zcamd ?

Edited by Dimmie, 18 July 2018 - 23:37.