View Full Version : DM800 Evocam config
smith
17th October, 2009, 01:35 PM
I've read the other threads about getting Evocam to work with E2 but I don't seem to be able to fix it! This is my camd_cfg in user/keys:-
I think the box copies the files in user/keys to var/keys when running. They all look there in both directories, what am I missing?
# debug messages level
# EMM messages
# 00 don't show any EMM's
# 01 show only valid EMM's, default setting
# 02 show valid and bad EMM's with complete data display
M: { 01 }
# ECM messages
# 00 don't show any ECM's
# 01 show only valid ECM's, default setting
# 02 show valid and bad ECM's with complete data display
C: { 01 }
# AU
# 00 is ignored (default)
# 01 enable AU
# 02 AU Auto
A: { 02 }
# Key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 01 }
# Key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 00 }
# # Hash pids
# 00 hash all pids
# 01 hash only pids with implemented algos (default)
H: { 00 }
# share Mode
# 00 Pure emu
# 01 Pure emu
# 02 Pure emu
# 03 alle network clients
# 04 newcamd share
# 05 radegast share
# 06 camd35 share(not in use)
G: { 00 }
# On Screen Display for Multicam
# 00 No OSD (default)
# 01 display Smartcard messages, box IP required
# 02 display Smartcard messages new nhttpd format, box IP required
O: { 01 }
USER = root
PWD = password
# To use UDP log
# 00 disabled
# 01 enabled
L: { 01 }192.168.0.115 10000
smith
17th October, 2009, 03:13 PM
Tried a "working" set of files from another user with no joy. Perhaps it is an issue with the image which is Blackhole v0.11.
Has anybody got Evocam v2.17 working with BH v0.11?
mercenary
17th October, 2009, 03:18 PM
i cant get it working with PLI either
AllyB
17th October, 2009, 06:11 PM
having the same problem as of about 2-3 weeks, on mgcamd it crashes too much but cant get it to load on evocamd :(
zaf786
17th October, 2009, 06:40 PM
Tried a "working" set of files from another user with no joy. Perhaps it is an issue with the image which is Blackhole v0.11.
Has anybody got Evocam v2.17 working with BH v0.11?
I had it working on 7025 i don,t see a reason why it won,t work on 800 have you had a look what attributes your k*ys and roms are set.they should be 644 if they are 644 and not working try chmodd 755 and restart enigma see what happens long shot this is worth a try
smith
17th October, 2009, 06:52 PM
A 7025 is E2 isn't it? Which image and cam versions have you used. All the files in the directory are set to 755. This is strange, obviously the pure emu setting stops the cam going to look for network keys, there must be another reason why it will not look at the key files.
AllyB
17th October, 2009, 07:08 PM
mine are all set to 755 too i think, which ones need to be 644? everything in the "keys" folder?
zaf786
17th October, 2009, 07:25 PM
A 7025 is E2 isn't it? Which image and cam versions have you used. All the files in the directory are set to 755. This is strange, obviously the pure emu setting stops the cam going to look for network keys, there must be another reason why it will not look at the key files.
Hi try this go to usr/bin and look for evocamd_2.17 and replace with this file and chmodd 755 and reboot and start your cam again to be safe save the existing evocamd_2.17 to desktop have all your files in correct folder usr/k and usr/scce chmod 644
extract the file with winrar before putting in usr/bin
smith
17th October, 2009, 07:46 PM
Thanks, tried the file and still no luck. Evocam seems to be working and it knows the stream is encrypted, the "N" is blue. The fact that it isn't going green seems to idicates that it cannot find the files.
AllyB
17th October, 2009, 11:10 PM
yep didn't work for me either, black screen as soon as i try to switch to evocamd, works fine again on mgcamd, but freezing lots
thanks for tryin, any other suggestions welcome :)
smith
17th October, 2009, 11:22 PM
I'm baffled, never seen this with Evocam using E1 on DM500, 600, DBox2's. Must be an E2 quirk as it seems to afflict a few images, not just Nabilosat BH. Although these images are generally for sat systems, so perhaps its something to do with the cable services side.
AllyB
17th October, 2009, 11:23 PM
so need to change the image? is there a dk image for the dm800?
smith
17th October, 2009, 11:30 PM
No I don't think it is an image problem, I think it is the way that the Enigma 2 OS is handling the the CAM messages. The fact that some people seem to still have it working with E2 (Enigma) means that there should be a way to configure it to work. I just can't see where it is going wrong at the moment. Perhaps sleep on it.
mercenary
18th October, 2009, 05:38 AM
please post your details here if you have a DM800 and evocam working!
mercenary
18th October, 2009, 07:06 AM
i think this is the cause, can someone, any dreambox model.
run evocamd from the prompt and see what its output should be.
mine is
root@dm800 ~ # evocamd
DEMUX DEVICE: No such file or directory
smith
18th October, 2009, 10:40 AM
When I run evocamd, I get file not found. The file is actually called evocamd_2.17 and when I run from the command prompt in telnet I get the same as you:-
root@dm800 ~ # evocamd_2.17
DEMUX DEVICE: No such file or directory
aftermath
18th October, 2009, 10:44 AM
try re-installing it from box via net
smith
18th October, 2009, 11:37 AM
try re-installing it from box via net
Hasn't made any difference I'm afraid
tomcat415
18th October, 2009, 06:13 PM
if its any help i got evocamd to work and update on my dm8000
add my scce and keys for you to try i have the Nabilosat Enigma2 Black Hole - DM8000 v0.12
and evocamd_2.17
smith
18th October, 2009, 08:47 PM
if its any help i got evocamd to work and update on my dm8000
add my scce and keys for you to try i have the Nabilosat Enigma2 Black Hole - DM8000 v0.12
and evocamd_2.17
Thanks tried this and I'm still in the same boat, worth a try. I noticed that your files have some sat stuff, is it a dual tuner? Also I didn't use the cables.xml as it seemed to be for the wrong area. I just nicked the one from my DM500 DK image, but I don't think that could be the problem.
Evocam is still completely dead, then as soon as I go to Mgcam it works straight away.
AllyB
18th October, 2009, 11:38 PM
this has got me beat, really dunno what else to try beyond a reimage and start from scratch
smith
19th October, 2009, 08:15 AM
this has got me beat, really dunno what else to try beyond a reimage and start from scratch
To be honest, I started with a fresh BH v0.11 image and the first thing I did was install Evocam. It didn't work and after reading a post on here installed MGCam and its been fine until recently.
wanhunlo
19th October, 2009, 08:30 PM
I have been getting the same problems. Only had the box for a few weeks, must of tried about 6 or 7 different images.
Evocamd will not work on any of them.
As someone mentioned earlier, telnet to the box and execute the script to start the emu and the evocam gives a "DEMUX DEVICE: No such file or directory" error. Must be why it doesn't work, missing something required by Evocamd?
Mgcamd gives an error too, dvb/adapter0/ca0 which is probably why it is freezing all the time.
If memory serves me from the old dbox2 satellite days I had to add ca0 in the image somewhere.
I guess these emus require something setup that E2 images don't have.
The question now is what other emus support Nagra. I tried CCcam but it gave me a not interested in nagra 1800: error and wouldn't decrypt. I read it doesn't support Nagra1
Maybe a mosc card is the only way to go for now. Anyone know how to setup the box to get a mosc working?
smith
19th October, 2009, 10:19 PM
I don't get an Mgcam error, it just seems to report the config settings.
I've noticed that it freezes when the Hex for the key changes. The stream seems to be rotating between the two keys 00 and 01, but Mgcam thinks that the hex code for key 00 is for key 01. That's when it freezes until the hex rotates again. Hope that makes sense.
hatchet
20th October, 2009, 02:41 PM
Having exactly the same problems.
Someone upload a working image of bh 0.11 with the clone bootloader, please ?
pob639
20th October, 2009, 10:06 PM
Have you tried an older version of cccam that can read nagra keys cccam_2.0.8 can if memory serves me right you'll just have to update softcam keys
well worth a try
Titan36
21st October, 2009, 08:10 PM
Is there a way of installing evocam 2.13.The reason i say this is my 600pvr would not clear channels with evo 2.17.When i went back to 2.13 i havent had a problem since.The 600pvr is not a clone though,so i had no problem down loading from pli.My 800 HD is a clone and i cant find anywhere to download evo 2.13 from the box.
Just a thought guys 2.13 may work on the clone.
AllyB
21st October, 2009, 09:51 PM
ah hell now mgcamd wont work, i guess iv messed about too much gonna have to reimage it now i think, unless anyone has any ideas?
AllyB
22nd October, 2009, 10:07 AM
still cant get it to work, i have reimaged it, iv tried a factory reset, iv manually updated keys iv downloaded the rom fix and replaced the one i had just in case, no pic on non free channels.
If anyone could help me id really appreciate it, the box is close to gettin chucked out the window right about now...
wanhunlo
22nd October, 2009, 07:24 PM
I don't get an Mgcam error, it just seems to report the config settings.
I've noticed that it freezes when the Hex for the key changes. The stream seems to be rotating between the two keys 00 and 01, but Mgcam thinks that the hex code for key 00 is for key 01. That's when it freezes until the hex rotates again. Hope that makes sense.
I hear what you are saying but why does the dm800 freeze when the dbox2 is fine?
Both used mgcamd. The 500c and 600c crowd don't seem to be suffering from this problem either.
Seems a bit strange, maybe an older version of mgcamd is required?
Does anyone know if the dm800 will support a nagra card?
zaf786
22nd October, 2009, 07:38 PM
if its any help i got evocamd to work and update on my dm8000
add my scce and keys for you to try i have the Nabilosat Enigma2 Black Hole - DM8000 v0.12
and evocamd_2.17
I thought we are not allowed to post keys in public isn,t this breaking the forum rules can someone clear this
Parisno
22nd October, 2009, 08:21 PM
Hi guys.
I have had my DM800 HD since they first came out, I have had every image possible on it, and messed around for hours and hours, this is what I have found.
All images will clear with Mgcamd (all versions) but will freeze, sometimes it will clear and run fine for weeks/months but other times will freeze repeatedly about every half-hour or more.
Blackhole 0.7 will clear and auto-update and NOT freeze with Evocamd but ALL other versionsof Blackhole and all other images are Free-to-view only with Evocamd.
So, for me its Blackhole0.7 and Evocamd, its the only image that will run Evocamd and Mgcamd is useless due to the freezing! Don't know why or what is different about v0.7 but it works for me. I try all the new releases every now and then and all new versions of Blackhole (up to 0.12) but nothing else has so far worked.
Don't know if its important, but I always update 0.7 with the latest seccond-stage-loader I can find, at the moment that's 75. Hope this helps and if anyone has any sugestions for getting later versions of Blackhole working I will gladly test them for you.
AllyB
23rd October, 2009, 05:47 PM
can i delete the current evocam and mgcamd files and start again? already tried to factory reset and manual scan instead of using my backup files. incase they r corrupt.
AllyB
23rd October, 2009, 05:49 PM
could it be a chmod setting somewhere? can someone list the correct settings for the correct files?
hatchet
23rd October, 2009, 05:57 PM
Just reflash the image mate and start again, ive still not got evocamd working.
AllyB
23rd October, 2009, 06:26 PM
i have reflashed it about 5 times diff images.
stratman
23rd October, 2009, 07:14 PM
Parisno is correct Blackhole0.7 is the only image that works with evocamd 2.17
zaf786
23rd October, 2009, 07:23 PM
Hi i don,t have dm800 i have in the past had problems clearing with evocamd 2_17 on my dm7025 pli images and nabilo images there are few versions of evocamd 2_17 try a diffrent version evocamd 2_17b or c
AllyB
23rd October, 2009, 07:34 PM
well im on blackhole 0.7 now and it still won't work, im afraid iv messed with it that much iv broke it :( i will try diff evocamds tho just in case.
zaf786
24th October, 2009, 08:05 PM
I don't get an Mgcam error, it just seems to report the config settings.
I've noticed that it freezes when the Hex for the key changes. The stream seems to be rotating between the two keys 00 and 01, but Mgcam thinks that the hex code for key 00 is for key 01. That's when it freezes until the hex rotates again. Hope that makes sense.
Hi can u try this evocamd version put this evocamd.mips and rename it as evocamd_2.17 and chmod 755 delete the existing evocamd version off cource this is in directory USR/BIN delete your k*ys and r*ms and reinsert them in again and restart cam best to reboot system
smith
25th October, 2009, 01:16 PM
Tried all these fixes without success. Tried newer images, when I should have been trying older ones.
I now have it working on BH 0.7.
Thanks
gezz
26th October, 2009, 10:24 PM
Had to tinker with my file to get it to work on my 7025. I've attached it for you to try if you want.
smith
26th October, 2009, 11:09 PM
Had to tinker with my file to get it to work on my 7025. I've attached it for you to try if you want.
Which image do you have?
gezz
26th October, 2009, 11:16 PM
Which image do you have?
I have PLi Jade
smith
26th October, 2009, 11:37 PM
Well its sorted now, it was an image problem, its fine on BH0.7 and I swear by Nabilosat images, I have them running on DM500/DM600/DM800. Didn't like PLI at all, very basic.
I do know that they changed the way BH handled CAMs in later images, perhaps there is a problem there, I have logged the issue with Nabilosat.
Parisno
27th October, 2009, 10:59 PM
Well its sorted now, it was an image problem, its fine on BH0.7 and I swear by Nabilosat images, I have them running on DM500/DM600/DM800. Didn't like PLI at all, very basic.
I do know that they changed the way BH handled CAMs in later images, perhaps there is a problem there, I have logged the issue with Nabilosat.
I would be interested in what they have to say on this!
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.