Tweet
In fact, the official release already has preinstalled emulator dccamd. But as it works only with access cards so even with exotic encoding Dreamcrypt / Firecrypt, it not much we can help to solve our "modest" goals. So try to install the official image of something more popular and useful ...
Long thought of as paint, so it was clear people are not very familiar with Linux device. But since the installer uses a powerful Enigma2 ipkg, as a result decided not to depart from tradition and the whole setup emulator laid on the installation ipk-packages (see end of post). So far only collected Package mgcamd_1.35a, but if I try other emus at of.relize or will enroll, you will also try to collect installs packages and put in this post.
Once again I want to emphasize, especially to experimenters that there ipk-packages only for factory images! If you try to install them on the alternative image, type NewNigma2, DreamElite, etc., can not doubt the problems with viewing the images you are guaranteed. I warned ...
Installing ipk-package ...
Download and unpack the attached archive at the end of this post.
Connect to the Dream by FTP.
File (s) from the archive with the extension *. ipk throws in the / tmp directory on the Dream. First make sure that this directory has no other files with the extension *. ipk.
Connect to the Dream of Telnet and give this command:
ipkg install / tmp / *. ipk
In response to see something like this:
ID:
root @ dm500hd: ~ # ipkg install / tmp/dreambox-mgcamd_1.35a_dm500hd.ipk
Installing dreambox-mgcamd (1.35a) to root ...
Configuring dreambox-mgcamd
root @ dm500hd: ~ #
This means that the installation is successful, otherwise it will display an error message, and it is bad and will need to separately understand what was happening.
After successful installation, if necessary, should correct configs under. For example, if you install the mgcamd, then it will be files that are placed in / usr / keys directory Dreama:
/ Usr / keys / mg_cfg # <- the configuration file mgcamd
/ Usr / keys / newcamd.list # <- address file / rendezvous / passwords for sh @ ring
Other files with the extension *. list in this directory are optional and setting them requires some additional knowledge.
Upon completion of the installation required! will need to restart the Dream. You can right here in the telnet session (Commands: reboot), but you can and through the receiver's menu:
Menu -> Standby / Restart -> Restart.
Another couple of useful commands ...
see a list of all installed packages: ipkg list_installed
see a list of all available packages: ipkg list
remove the package: ipkg remove package_name
see инфу of installed package: ipkg info packagename
see a list of files in the package: ipkg files package_name
** Package_name - this is usually the first part (before the first underscore) in the file name *. ipk
If something is wrong with the emulator ...
After successful installation ipk-package and reboot the receiver, in the idea, the emulator should start automatically. But no reports on the TV screen you will not see. Image of a primitive, at least possibilities.
If you suspect that the emulator does not start automatic, you need to connect to the Dream of Telnet and give commands ps, to bring the entire list of running processes on the screen. Ie you should see something like this is the case with mgcamd:
Code:
root @ dm500hd: ~ # ps
PID Uid VmSize Stat Command
1 root 672 S init [3]
2 root SWN [ksoftirqd / 0]
...
...
blah-blah-blah
...
...
717 root 1420 S / usr/bin/mgcamd_1.35a
718 root 1420 S / usr/bin/mgcamd_1.35a
719 root 1420 S / usr/bin/mgcamd_1.35a
...
...
root @ dm500hd: ~ #
The lines with the word mgcamd tell us that at this moment the emulator up and running. And if the pictures on the TV screen do not continue, it is necessary to include logging emulator on the console (file mg_cfg, setting L: (02)) and restart the emulator of the two commands:
killall -9 mgcamd_1.35a
/ Usr/bin/mgcamd_1.35a
Now you can see the emulator log directly into the console and have from these data to look for a solution. How to work with the gully mgcamd can be read here.
By the way, if you need to stop / start / restart the emulator, you can use these commands:
/ Etc/init.d/mgcamd_1.35a stop
/ Etc/init.d/mgcamd_1.35a start
/ Etc/init.d/mgcamd_1.35a restart
PS. All tested and isprobavano for Firmware Release 2.7.1 (17.02.2010).
The process of installing and running / emulator I have no reprimands, although he is still not fully tested. So, what if you have any problems during the installation of cool do not worry and take everything as a little experiment. Good luck ...
Long thought of as paint, so it was clear people are not very familiar with Linux device. But since the installer uses a powerful Enigma2 ipkg, as a result decided not to depart from tradition and the whole setup emulator laid on the installation ipk-packages (see end of post). So far only collected Package mgcamd_1.35a, but if I try other emus at of.relize or will enroll, you will also try to collect installs packages and put in this post.
Once again I want to emphasize, especially to experimenters that there ipk-packages only for factory images! If you try to install them on the alternative image, type NewNigma2, DreamElite, etc., can not doubt the problems with viewing the images you are guaranteed. I warned ...
Installing ipk-package ...
Download and unpack the attached archive at the end of this post.
Connect to the Dream by FTP.
File (s) from the archive with the extension *. ipk throws in the / tmp directory on the Dream. First make sure that this directory has no other files with the extension *. ipk.
Connect to the Dream of Telnet and give this command:
ipkg install / tmp / *. ipk
In response to see something like this:
ID:
root @ dm500hd: ~ # ipkg install / tmp/dreambox-mgcamd_1.35a_dm500hd.ipk
Installing dreambox-mgcamd (1.35a) to root ...
Configuring dreambox-mgcamd
root @ dm500hd: ~ #
This means that the installation is successful, otherwise it will display an error message, and it is bad and will need to separately understand what was happening.
After successful installation, if necessary, should correct configs under. For example, if you install the mgcamd, then it will be files that are placed in / usr / keys directory Dreama:
/ Usr / keys / mg_cfg # <- the configuration file mgcamd
/ Usr / keys / newcamd.list # <- address file / rendezvous / passwords for sh @ ring
Other files with the extension *. list in this directory are optional and setting them requires some additional knowledge.
Upon completion of the installation required! will need to restart the Dream. You can right here in the telnet session (Commands: reboot), but you can and through the receiver's menu:
Menu -> Standby / Restart -> Restart.
Another couple of useful commands ...
see a list of all installed packages: ipkg list_installed
see a list of all available packages: ipkg list
remove the package: ipkg remove package_name
see инфу of installed package: ipkg info packagename
see a list of files in the package: ipkg files package_name
** Package_name - this is usually the first part (before the first underscore) in the file name *. ipk
If something is wrong with the emulator ...
After successful installation ipk-package and reboot the receiver, in the idea, the emulator should start automatically. But no reports on the TV screen you will not see. Image of a primitive, at least possibilities.
If you suspect that the emulator does not start automatic, you need to connect to the Dream of Telnet and give commands ps, to bring the entire list of running processes on the screen. Ie you should see something like this is the case with mgcamd:
Code:
root @ dm500hd: ~ # ps
PID Uid VmSize Stat Command
1 root 672 S init [3]
2 root SWN [ksoftirqd / 0]
...
...
blah-blah-blah
...
...
717 root 1420 S / usr/bin/mgcamd_1.35a
718 root 1420 S / usr/bin/mgcamd_1.35a
719 root 1420 S / usr/bin/mgcamd_1.35a
...
...
root @ dm500hd: ~ #
The lines with the word mgcamd tell us that at this moment the emulator up and running. And if the pictures on the TV screen do not continue, it is necessary to include logging emulator on the console (file mg_cfg, setting L: (02)) and restart the emulator of the two commands:
killall -9 mgcamd_1.35a
/ Usr/bin/mgcamd_1.35a
Now you can see the emulator log directly into the console and have from these data to look for a solution. How to work with the gully mgcamd can be read here.
By the way, if you need to stop / start / restart the emulator, you can use these commands:
/ Etc/init.d/mgcamd_1.35a stop
/ Etc/init.d/mgcamd_1.35a start
/ Etc/init.d/mgcamd_1.35a restart
PS. All tested and isprobavano for Firmware Release 2.7.1 (17.02.2010).
The process of installing and running / emulator I have no reprimands, although he is still not fully tested. So, what if you have any problems during the installation of cool do not worry and take everything as a little experiment. Good luck ...