Does supports dm800se v.2 original?
I flashed but it does not start after reboot.
Posts by Mananrusha
-
-
Can I use for DM800Sev.2 original?
-
Thanks, It was server problem, not Oscam and CCcam. I'm using CCcam 2.32 de, It's very stable and working fine.
-
cccam 2.3.2 per openesi-8.6-dm800se-20190519 dove la trovo grazie?
I suggest that your change your Image to OpenAtv it's very stable image.
https://www.opena.tv/downloads/1-openatv-6-2-images/
And
Softcam-feed-universal_6.Plus, just search on Google or her. -
What do you think, if I install Cccam mips on my new install Openatv 6.3 image?
For me CCcam 2.3.2-de works very well
Download from ATVT
Thank you, I found my problem, It was problem from Cccam server.
To day I Install OpenAtv 6.2 and Softcam-feed-universal_6.Plus_all with CCcam 2.3.2 , it Working perfect .
Sky sport De also working perfect without freeze. -
Cccam 2.3.2 mips + arm
- Fix SKY DEtest
What do you think, if I install Cccam mips on my new install Openatv 6.3 image?
You can delete my post, after your answer!
New DM user.
Dm Hd800se v.2 original -
Hello every one!
I installed new OpenATV 6.3 and updated.
DM800sev.2 original
what your recommanding for me CCcam- softcam or Oscam and witch version, because i had freezing on seky sport de og canal+ support.
Hotbird and Astra 19
-
I've already told you before, why do you ignore it and why don't you read it? Another link I found to you is found here, for example, and also concerns CW problems and their CRC checks: Everyone should correct the "disablecrccws_only_for" typo mistake
Thank you, I already putted in( disablecrccws_only_for = 0500:030B00;098C:000000;0E00:000000 ) in Osacam. conf
Under [global] without help . -
Freezing every 3 seconds
-
Display More
I have edit your post over since it contains info that can be abused.
But look over your username and password for your cccam reader
log shows a reject with wrong or unknow user.
Please when posting logs edit and remove any dyndns address also remove any username and passwords
before posting and keep in mind that support for Payservers are agains the forum rules
Ok thnx
But how do I fix the problem?
-
OK, please specify exactly how your OSCam freezes and how exactly it looks if it freezes. What do you see in LiveLOG under OscamWebif and what happens when it freezes.
Today I install new OpenAtv 6.3, old softcam panel v2.0 and Oscam 11.522-r 796, but freezing every 3-4 seconds.
Dm 800sev.2 original.
I have problem only sky Germany.
a152464c5f689f456b.jpgI removed you log file since it contains user information that can be abused or in wurst case senarion can be a payserver settings
Allways edit your logfiles so they dont contain any user info or address to any server privat / Payserver
Regards Seagen
-
Tnx, Now Openatv support softcam again, You could install many Oscam version and softcam CCcam 2.3 De, but freezing problem don't fix it yet.
-
I need Oscam stable and last version for OpenAtv 5.3
DM 800sev.2
Does anyone have Oscam without freezing sky DE?
-
Display More
MetrixStyleHD 11.4r7
- Screen EPGLoad Setup
- Screen Fancontrol
- Screens Multi EPG ValiMod
- Screen Grafischer Multi EPG
- neue Option für Hauptmenü - 'Farbe Symbolhintergrund - Farbe Auswahltext' ( bei 'Farbe Auswahltext - Weiß' ausgeblendet )
- PluginOption - Graphic / -MV , mit und ohne PIG ( Multi EPG ValiMod oder Grafischer Multi EPG muß installiert sein )
- diverse Fixe
Can I get mipsel fo DM 800 se.v2?
My DM not supporting Deb -
The only thing that has disappeared in OpenATV 6.2 and 6.3 is the "SoftCAM-Panel", which was just a control plugin for SoftCAMs.
It was not needed anymore, as the new feed - and yes, you get that if you follow my instructions about getting the new feed - contains only SoftCAMs with a different startup method.
And the control screen for the new cams was added end of April already ...
Thanks, today I copied the infopanel folder to my PC , then I updated the Openatv 6.3 image.
After rebooting the softcam panel missed, but when i recopied the infopanel , every think working perfect , but the Sky sport De freezing yet .
Oscam 11523 -
I think Openatv 6.3 is the best DM image, It was softcam problem after 14.Jun, but if you are coping infopanel folder before updating the Image, then replacing it after update so working perfect.
-
Can I use for Original DM pelase?
May be the DM can't start after flashing! -
Display More
The recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:
Codewget -O - -q http://updates.mynonpublic.com/oea/feed | bashThe easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.
That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.
No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.
Use version 4.3r2 or later in that case.
The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".
In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.
Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:
- "Menu -> Info Panel", just as before with softcam panel
- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel
- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places
The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.
Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)
The new feed has multiple advantages:
- All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.
oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.
Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...
- All OScams and Ncam are built every night if their sources get updated.
If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.
For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).
- Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
- CAMs started through init.d are easier to maintain remotely
You can simply start/stop/restart them from the shell
Coderoot@quad4k ~ # /etc/init.d/softcam stop Stopping Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam start Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam restart Stopping Softcam service oscam-smod: OK Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam status Softcam service oscam-smod: Running.e.g. after editing config files.
No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.
- CAMs started through init.d are ready when you are ...
As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.
Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station
Display MoreThe recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:
Codewget -O - -q http://updates.mynonpublic.com/oea/feed | bashThe easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.
That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.
No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.
Use version 4.3r2 or later in that case.
The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".
In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.
Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:
- "Menu -> Info Panel", just as before with softcam panel
- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel
- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places
The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.
Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)
The new feed has multiple advantages:
- All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.
oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.
Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...
- All OScams and Ncam are built every night if their sources get updated.
If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.
For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).
- Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
- CAMs started through init.d are easier to maintain remotely
You can simply start/stop/restart them from the shell
Coderoot@quad4k ~ # /etc/init.d/softcam stop Stopping Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam start Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam restart Stopping Softcam service oscam-smod: OK Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam status Softcam service oscam-smod: Running.e.g. after editing config files.
No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.
- CAMs started through init.d are ready when you are ...
As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.
Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station
I'm using openatv 6.3 image on 14.06, but if update so the softcam be unavailable, Can get the softcam back if I use your Code?
DM800 se v.2
openAtv 6.3
Oscam 11523 - All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.
-
Are this Image for Original DM or clone?
