Posts by manuel06

Had the same problem as I wrote here:Ncam 3.6 compiled and patched by marouan & RAED

Changed softcam key and problem was solved. Maybe if you change the softcam key your problem will be solved too.

Thanks for keys. AFN channels on 16e have sound but no picture. Any suggestions?

I'm having the same problem with Ncam 3.6 that I have with Ncam v3.5. As quoted here:Ncam 3.5 compiled and patched by marouan & RAED I cannot open RSl LA1, RSI LA 2, RTS Un and RTS Deux on Sat 13E. No problem with Ncam 3.3. Can someone help me with this problem as it seems that I'm going to be stuck on Ncam 3.3.

Today I changed the Softcam key to that by enigma1969 and channels are opening well. Thanks enigma1969.

From my location we don't receive 57e. My motor dish is mounted to receive the following Sats: 9e, 13e, 16e, 19.2e, 23.5e, 39e, 0.8w, 7w, 30w. I have no problems in opening channels on these Sats with Ncam 3.5. As softcam.key I always use the one by Serjoga that is updated in this Forum.

Ncam 3.5 is working well on my Vu Uno 4K, Blackhole v3.0.4D image on all packages but having problems in opening RSI LA 1, RSI LA 2, RTS Un and RTS Deux on Sat 13E. It opens then after very few seconds it freezes. No such problems with Ncam 3.3 or OScam 11392 on same decoder and image. Gone back to Ncam 3.3 but wish to have a solution for this problem. Thanks.

can we have cortexa9hf-vfp-neon-ARM for Ncam v2.9. Thanks for everything.

I started everything from fresh re Oscam. I uninstalled the one I had and installed Oscam 11278. I tested that it's working correctly and then added the new script for Arm base receivers that there is in post #1 and attributed 755. Now I'm having the below images.

When I entered on Oscam Webinterface it is showing OSCam r11391 and not 11278 as was before. So it's working now. Don't understand the info on last image, about missing in line 73 and 77. Here are additional info about these lines so that I could get help to understand this and if need be to adjust. Thanks for everything.

Line 73 and 77 are the following:

73 $oscamstop

74 echo "Copie du $oscambin"

75 cp -f oscam $oscambin > /dev/null 2>&1

76 echo "Demarrage du Oscam ..."

77 $oscamstart

My Ncam_Oscam.sh is as follows:

#!/bin/sh

CAMNAME="OSCam 11278"

remove_tmp () {

rm -rf /tmp/*.info* /tmp/*.tmp*

}

case "$1" in

start)

echo "[SCRIPT] $1: $CAMNAME"

remove_tmp

/usr/bin/oscam -b &

sleep 2

;;

stop)

echo "[SCRIPT] $1: $CAMNAME"

killall -9 oscam 2>/dev/null

sleep 1

remove_tmp

;;

*)

$0 stop

exit 0

;;

esac

exit 0

Thanks for your help.

Oscam_update.sh in /usr/script has 0755 as attributes. Both scripts that I tried had the same attributes but I had different errors.

Is the script for Vu Solo 4K the same for Uno 4K with same BH image? If not, I would appreciate if it will be downloaded here. Thanks.

I wish to add to my previous post that when I change the script with the one for Solo 4k, it gave me this error:

I tried this script on Vu+ Uno 4k with Blackhole image 3.0.4C and didn't work. I noticed that it's for Solo 4K, but I gave it a try. Is this script only for Solo 4k or also for Ultimo 4k and Uno 4K besides other decoders?

When I tried this script I got this error:

Thanks. Changed my ncam (v2.0) in bin with the one from this, ncam.cortexa9hf-vfp-neon.zip, and after restarted my Vu+ Uno 4K with Blackhole 3.0.4C works perfectly.

Quote from master G

Quote from manuel06

But I need mgcamd.

Then use Blackhole image.

So I take it that mgcamd doesn't work on OBH. I had it on Blackhole image but when I installed the OBH, it stopped functioning. If that's the case it will solve my problem and wait until there is mgcamd compatible with OBH for Uno 4K. Thanks

Quote from gap30

Quote from manuel06

I installed the Mgcamd on my Vu+ Uno 4K with OBH image 1.0 and didn't opened channels. Have no problem with OSCam but wish to have MGcamd also functioning. I have other boxes working with mgcamd. Don't know the problem, maybe the mg_cfg file?

use ncam 1.1 it just works

Yes I tried it and works. But I need mgcamd. For me it's more like a hobby than watching TV. The thing that OScam and Ncam are working and Mgcamd not on MY uno 4K, I need to find the problem.

I installed the Mgcamd on my Vu+ Uno 4K with OBH image 1.0 and didn't opened channels. Have no problem with OSCam but wish to have MGcamd also functioning. I have other boxes working with mgcamd. Don't know the problem, maybe the mg_cfg file?

I am using mgcamd 1.35a on my Vu+ Uno 4K and today stopped opening S*k De and Polsat. It is still opening packages on 13e and 19.2 but not these packages. Tried Oscam and Ncam 1.1 but still no luck. Blackhole image 3.0.3E. No problem viewing these channels on Vu+ Duo2 with mgcamd 1.38c (different dish) but not opening with Oscam and Ncam 1.1. Is this only my problem? Any help will be appreciated.

I have mgcamd 135a on my Vu+ Uno 4K, but wish to change to OSCam. If I install your oscam 11284 ipk, what do I need to do more? I have both CCcam and MGcamd Lines activated that I could convert to oscam.

I have Vu+Uno 4k with Blackhole image 3.0.3C and wish to install OScam. I have an activated CCcam line that wish to use it on it. I have tried and tried but without success. I installed [Black Hole] OSCam 11278 from the Linuxsat Panel that I installed on the Vu+ Uno 4K and then converted the CCcam line to Oscam with cccam2oscam and pasted the oscam.server on etc/tuxbox/config. Did something wrong or/and need to do more. Appreciate any help. Happy New Year to all.

I tried Mgcamd 1.45a on Vu+ SoloSE with Blackhole image and didn't noticed any difference from Mgcamd 1.38c using the same mg_cfg file. What is the difference between MGcamd 1.45a and MGcamd 1.38c? Are there any packages that are opened with 1.45a that are not opened with 1.38c? I find it a bit problematic to open Canal Sat France 19.2E with both 1.38c and 1.145a. The channels that are opened on this package take a longer time than on other packages to open.

When you press the Blue Button have you checked that the Active Cam selected is on the MGcamd and not on the Common Interface? Also check that the newcamd.list file in the /usr/keys is correct and active.

As the Timezone Country and Timezone are greyed out, is there any other way that one can correct the time on Kodi Jarvis v16.1 on BlackHole image V3.0.2B. Thanks.