https://wiki.openpli.org/api.php?action=feedcontributions&user=Rick+Hunter&feedformat=atomOpenPLi Wiki - User contributions [en]2024-03-29T14:12:34ZUser contributionsMediaWiki 1.28.0https://wiki.openpli.org/index.php?title=Problems_and_Solutions&diff=22883Problems and Solutions2023-01-14T17:26:05Z<p>Rick Hunter: /* Multiboot crash - Boot loop */</p>
<hr />
<div>=='''Alternative numbering mode'''==<br />
Are you confronted with channellist (bouquet) that don't start with the number 1, then enable this and it will. Goto '''Main Menu -> Setup -> System -> GUI Settings -> User Interface''' and enable "Alternative numbering mode"<br />
<br />
[[File:Problems-and-Solutions-001.jpg|frameless|centre|600px]]<br />
<br />
<br />
=='''Brand\Vendor related'''== <br />
==='''Vu<sup>+</sup> related'''=== <br />
<br />
===='''Cable Scan issue's?''' ====<br />
<br />
There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used. <br />
<br />
<u>This is the issue:</u><br />
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.<br />
<br />
/proc/stb/tsmux/input1_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input0_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input3:A<br />
/proc/stb/tsmux/input2:A<br />
/proc/stb/tsmux/input1:B<br />
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.<br />
<br />
<u>Temporary solution until reboot</u><br />
echo -n C > /proc/stb/tsmux/input2<br />
echo -n D > /proc/stb/tsmux/input3<br />
<br />
Note: VU+ should add input2_choices and input3_choices nodes.<br />
<br />
<u>Temporary Solution, that still works after a reboot:</u><br />
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207<br />
Reboot the receiver, and the scan problems are solved.<br />
<br />
===='''Restore Splash screen for Factory bootlogo'''====<br />
<br />
The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models: duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero, zero4k and the Duo 4K SE<br />
You do not have to pick one of the bootlogo's, your receiver selects only the file that must be needed. <br />
<br />
So the following steps must be taken:<br />
# place the content of the zip file on the USB pendrive <br />
# reboot your receiver<br />
# flash the 'image' (this will take just a few seconds)<br />
# when the flash is completed, remove the USB pendrive<br />
# restart your receiver<br />
<br />
<br />
<br />
duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the Duo 4K SE<br />
<br />
<u>Note</u>: for some reason Vu+ changed the name of the splash file introducing the Vu Duo 4K SE from splash_cfe_auto.bin to splash_auto.bin<br />
<br />
<br />
Download splash file: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=134711<br />
<br />
===''' Amiko related'''===<br />
===='''Restore Splash screen for Amiko Viper Combo HDD'''====<br />
Source: https://forums.openpli.org/topic/56843-flash-amiko-viper-combo/#entry1179308<br />
<br />
<br />
==='''Edision related'''===<br />
===='''Restore Splash screen for Edision'''====<br />
Source: https://forums.openpli.org/topic/47499-splash-for-edision-os-mega/#entry652041<br />
<br />
<br />
==='''ET6000'''===<br />
===='''Install bootloader'''====<br />
<br />
Unpack the zip and place the et6x00 folder with its contents on an usb stick. Flash this as if it were an image. Here is the link to the bootloader for the ET6000<br />
Here is the link to the bootloader for the ET6000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132322<br />
<br />
<br />
==='''ET7000'''===<br />
===='''Install bootloader'''====<br />
Unpack the zip and place the et7x00 folder with its contents on an usb stick. Flash this as if it were an image.<br />
Here is the link to the bootloader for the ET7000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132262<br />
<br />
<br />
==='''Zgemma related'''=== <br />
===='''Restore Splash screen for Zgemma'''====<br />
Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387<br />
<br />
<br />
=='''CI module with softcam (eg. OScam), so using both and making them work together'''==<br />
If for some reason you want to use a CI module and OScam, you will probably run into error messages. The problem or better the errors are there because CI modules are designed to work standalone. So if you want to make them working together, best practice is using the "Commoninterfaceassignment plugin”. So to let a CI work together with a softcam download and install "Commoninterfaceassignment plugin" which is located in the system section of the [[Plugin_Wiki:Information| <span style="color:SteelBlue">Plugin browser</span>]]. After installing the plugin goto '''Menu-> Setup -> SoftCam/CI -> Common Interface Assignment''' and define every channel for this CI module, that you have a subscription for. Enigma2 (OpenPLi) will then send all the other channels to the Softcam (OScam) and not to the CI module.<br />
<br />
<br />
=='''Crash logs'''==<br />
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org <span style="color:SteelBlue">forum</span>]. The crash log file is named like in the example below:<br />
<br />
enigma2_crash_3891289128.log<br />
<br />
<br />
===The location of the crash log file when there is a HDD (Harddisk) present===<br />
Normally the crash.log file is stored in the root of the HDD so in<br />
/media/hdd<br />
<br />
<br />
===The location of the crash.log file without any HDD (Harddisk) present===<br />
Normally the crash log file is stored in the <br />
/home/root<br />
<br />
<br />
===How to get the crash log file===<br />
If you don't want to use the command line or telnet to get the crash.log file, you can grab it using your favorite ftp client or just use a (internet)browser. On how to do this take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
<br />
=='''Debugging Enigma'''==<br />
<br />
===Debugging from the menu===<br />
As of OpenPLi 7.1 you can start debug mode from the menu, if you press the on/off key and hold it and a menu will appear which has the option to select '''Restart enigma in debug mode''', this will make the receiver restart and debug mode will be running in the background (you won't see this). <br />
[[File:Problems_and_Solutions-003.jpg|frameless|centre|750px]]<br />
Now you can start or test anything you think is not right or for some reason want to know what is happening in the background. Once you have tested what you wanted to test you can press the on/off button and hold it, a menu will appear which has the option to select '''Restart enigma in normal mode'''. <br />
[[File:Problems_and_Solutions-004.jpg|frameless|centre|750px]]<br />
Don't forget to do this, as debugging uses CPU power and it creates a debug file that keeps on growing as long as your debugging. The debug file that is created during debug is located at, <br />
<br />
/home/root/enigma.20190901.debuglog<br />
<br />
you can grab it using your favorite ftp client or just use a browser, on how to take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
===Debugging from the command line===<br />
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:<br />
root@<receiver>: init 4<br />
root@<receiver>: ENIGMA_DEBUG_LVL=4 enigma2<br />
<br />
To stop: Press CRTL-C. Enigma will halt. Then start enigma with:<br />
root@<receiver>: init 3<br />
Or reboot the receiver with:<br />
root@<receiver>: reboot<br />
<br />
<u>'''Note:'''</u> For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2'''<br /><br />
<br />
<br />
====For easier reading (Less logging) use:====<br />
<br />
ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2<br />
<br />
<br />
====Writing debug log (to a USB stick)====<br />
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /home/root/enigma.log<br />
<br />
or <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 2>&1 | tee ./enigma.log<br />
<br />
or to USB<br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /media/usb/enigma.log<br />
<br />
=='''Dual tuner problems'''==<br />
When your receiver has more than one tuner slot with 2 different tuners types, for instance DBV-T and DVB-C and you swap these tuners, then you might probably need to manually clean the nim entries in the [[Tips_and_Tweaks#Settings_file_in_OpenPLi| <span style="color:SteelBlue">settings</span>]] file and then reconfigure the tuner and perform a scan.<br />
<br />
<br />
<br />
=='''Flickering dashed line in screen'''==<br />
When you see a dashed flickering line on the "top" of the screen, you can cover this by pressing the menu when you are in the bouquetlist and select "cover dashed flickering line for this service".<br />
[[File:Problems_and_Solutions-003.png|frameless|centre|750px]]<br />
<br />
Or you can also install the plugin: '''Blackout Blind''' (enigma2-plugin-extensions-blackoutblind) this will permanently hide the dotted lines.<br />
<br />
=='''Freeze, Lock, Halt, Hang of OpenPLi and what to do, to gain control again over your receiver'''==<br />
When this happens, never (well only as a real last resort!!!) switch off the power or pull the power plug, this will -in time- certainly destroy the filesystem on which OpenPLi is running and as by-catch this may also destroy the filesystem of your HDD (when installed). So the best way is to login with [[Tips_and_Tweaks#Accessing_your_receiver_and_editing_files_using_the_command_line | <span style="color:SteelBlue">Telnet</span>]] and type:<br />
<br />
root@<receiver>: init 4<br />
<br />
This stops Enigma2 (operating system) gracefully, waiting for all it's components to stop and places Enigma2 into a "sleep" mode and then type:<br />
<br />
root@<receiver>: init 3<br />
<br />
This wakes enigma from the "sleeping" state and restarts the GUI (Graphical User Interface).<br />
<br />
=='''Harddisk Check'''==<br />
Harddrives will fail, that's just a question of time, so a check from time to time is prudent,certainly when you have switched it off using the power switch or pulled the plug, as this will mess-up the filesystem. (btw it can also be a USB stick but it has to be formated ext3 or 4). When a internal drive is present you can check it using the menu. '''Main menu -> Setup -> System -> Expert Settings -> Harddisk -> Filesystem check'''.<br />
<br />
It needs some xpert to explain what to do if the hardrive is busy and umount does not do the trick.<br />
<br />
=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se / Zero 4K)'''==<br />
By default some Vu<sup>+</sup> boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the <br />
''extensions'' section of the [[Plugin_Wiki| <span style="color:SteelBlue">plugin browser</span>]].<br />
<br />
<br />
=='''HbbTV and Kodi problems'''==<br />
HbbTV applications, browsers (Chromium) and Kodi make use of functionality of the SoC (the "processor") that is not required for enigma ("watch TV"). <br />
This functionality is in the SoC, but must also be made accessible/available for applications (which include browsers and Kodi). <br />
The supplier does this by means of the drivers, the sources of which are not available (also known as "closed source"). Because the interface to those <br />
drivers is not known (and we also have no sources) it cannot be otherwise than that the supplier also supplies the applications (Kodi, browsers ...). <br />
Sometimes they do, sometimes they don't, it depends on the supplier. The form in which these applications are offered is usually also <br />
without source, at least in part. This means that we are completely dependent on the supplier for the whole, if we have no sources, we cannot do anything. <br />
Especially if we move to a newer version of OE, this can cause problems and we have seen this for years, at various levels. Sometimes we manage to get it all going, but often not.<br />
<br />
<br />
<u>Short summary:</u> for applications such as Kodi and HbbTV OpenPLi is completely dependent on the <u>supplier as in Vendor</u>, OpenPLi cannot do anything about that, so OpenPLi cannot guarantee HbbTV and Kodi. If it works: Great! If it doesn't work then the supplier did not consider it necessary to offer it to the user in working order. Sad but true.<br />
<br />
=='''Missing menu items or changing the access level of the configuration menu'''==<br />
As of OpenPLi 7.0 during a fresh flash (so no backup used) during the [[Installation | <span style="color:SteelBlue">Installation</span>]] you will be asked which suer mode you want to use. Here you can choose between 3 different user modes; Normal, Advanced or Expert. Each mode will reveal more options in the Menu, so if you are missing menu items, then you can change the user mode in the menu go to '''Main Menu > Setup > System > Expert settings > User Mode'''.<br />
<br />
<br />
=='''Movies or media files not playing'''==<br />
To play a certain movie or media file a codec ('''CO'''der/'''DEC'''oder) is needed. When a movie file won't play in OpenPLi this codec might be "missing" and sadly there is no way to add this missing codec, because opposite to a personal computer, which can install missing codecs, a STB (SetTopBOX)/receiver uses codecs from within the chip, so if the codec needed for a certain movie file is not in the chip of the receiver you are using, it cannot play it and you cannot add this missing codec, as you cannot add anything to a silicon chip. You could try using the [[Plugin_Wiki:ServiceApp| <span style="color:SteelBlue">'''ServiceApp'''</span>]].<br />
<br />
So if you have a movie that can't be played, the only thing you can try, is to re-code it. For this you can use programs like [https://handbrake.fr/ <span style="color:SteelBlue">Handbrake</span>]. A good choice would be h264 or h265 as the video codec and mp2, mp3 or ac3 as an audio codec.<br />
<br />
<br />
<br />
<u>Please Note:</u> Files like AVI and MKV are containers and say nothing about the CODEC needed to play whats inside them!!<br />
<br />
=='''Mountmanager Problems'''==<br />
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.<br />
<br />
<br />
===Autodetection===<br />
As of OpenPLi 7.2 CIFS config has SMB version and security protocol autodetection, so that you no longer have to start looking for whether options have to be given, they are now entered automatically, so practically it means that the suggestions below should not be needed anymore, the system will try all options until one settings works!!<br />
<br />
===Older vs newer Kernel===<br />
<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution. <br />
<br />
<u>The solution</u> is simple, you can try the following; If you make a mount with [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.<br />
<br />
Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.<br />
<br />
===Older vs newer SMB Protocol===<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).<br />
<br />
Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols, when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been configured with, and if you, as a user, need a different version, you will need to specify this in the mount options.<br />
<br />
Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.<br />
<br />
<br />
<u>The solution</u> is to change the SMB version used to mount, to do this in [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]] change the "mount options" from "rw" to "rw, vers=3.0" or whatever version you want to mount. You might have to try a few, if you don't know which one your server supports, always start with the highest version.<br />
<br />
This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/<br />
<br />
The same is true for the authentication mechanism used to setup a share/mount. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). So depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the command line too.<br />
<br />
<br />
<u>'''Note:'''</u> For the Dutch, also have a look here https://forums.openpli.org/topic/71313-bestaande-en-werkende-cifs-mounts-werken-nu-niet-meer-in-72rc/page-5#entry1114216<br />
<br />
<br />
'''So as explained above, if the protocol version that the box uses differ from the server side, then no connection is possible without additional actions.'''<br />
----<br />
If you have a server that does not support SMBv2, you can force a connection to SMBv1 on the box by adding vers=1.0 to the mount options<br />
If you have a server that does not support NTLMssp, you can change it by adding sec=ntlmv2 or sec=ntlm to the mount options on the box<br />
<br />
What works is a matter of trying, you may even need both. See below is an example on connecting to a Synology that "still" uses Samba version 1 and security NTLM:<br />
<br />
<br />
<br />
[[File:Problems_and_Solutions-005.jpg|frameless|centre|750px]]<br />
[[File:Problems_and_Solutions-006.jpg|frameless|centre|750px]]<br />
<br />
=='''Multiboot crash - Boot loop '''==<br />
<br />
If you make use of multiboot and somehow get stuck at boot, by let's say a GSOD (Green Screen of Death) you can try to login your box/receiver with telnet and try the following:<br />
<br />
mkdir /tmp/t<br />
mount /dev/mmcblk0p3 /tmp/t<br />
cd /tmp/t<br />
<br />
Because the '''Edision OS mio ...''' uses mmcblk1... this throws an error and you can try this:<br />
<br />
mount /dev/mmcblk1p3 /tmp/t<br />
cd /tmp/t<br />
<br />
You should then see in this directory several startup files. If you eg want to start image in slot 1 do<br />
<br />
cp STARTUP_1 STARTUP<br />
<br />
If you want to start image in slot 2 then<br />
<br />
cp STARTUP_2 STARTUP<br />
<br />
And so on, then reboot the box.<br />
<br />
'''On the AB PULSe 4K:<br />
''' - turn it off with the back power switch.<br />
- Point the RCU to it and press the power button of the RCU (keep it pressed).<br />
- turn on the back power switch (while still pressing the RCU power button don't release it).<br />
- When the boot selection screen is displayed release the RCU power button and select the slot you want to boot to.<br />
<br />
If you want to flash from the Bootmenu insert the USB stick with the .zip image file on the back USB slot (it doesn't work on the front one!).<br />
<br />
Remark this doesn't work with the front panel power button you really need to use the RCU.<br />
<br />
'''On the HD51 use the following commands to start with bootslot 2:'''<br />
<br />
* mkdir /tmp/t<br />
* mount /dev/mmcblk0p1 /tmp/t<br />
* cd /tmp/t<br />
* cp STARTUP_BOOTSLOT_1_MODE_1 STARTUP<br />
* reboot<br />
<br />
EXAMPLES of content within STARTUP files...<br />
* Booting from SLOT 2-Mode1<br />
* boot emmcflash0.kernel2 'root=/dev/mmcblk0p5 rw rootwait hd51_4.boxmode=1'<br />
<br />
* Booting from SLOT 4-Mode1<br />
* boot emmcflash0.kernel4 'root=/dev/mmcblk0p9 rw rootwait hd51_4.boxmode=1'<br />
<br />
=='''Reset lost password'''==<br />
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.<br />
<br />
<br />
===Install the "setpasswd" plugin===<br />
Easiest way is to install a plugin and reset or delete your password. Goto Main menu -> Plugin browser and press the green button "download plugins" goto systemplugins and goto setpasswd and press ok on your remote to install it. After you installed goto Main menu -> Setup -> System -> Change Root Password and press the red button to delete it.<br />
<br />
===Using the command line method 1===<br />
I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution. <br />
# Go to the map /etc where you find the file shadow. <br />
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'. <br />
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow. <br />
<br />
<br />
===Using the command line: method 2 ===<br />
There is a second scenario to solve this.<br />
# Go to the map /etc where you also find the file passwd.<br />
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++<br />
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW<br />
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh<br />
# Save / overwrite this file and exit Notepad ++.<br />
<br />
<br />
=='''Satellites.xml returning-over-and-over'''==<br />
The default satellites.xml is in the image, and is under version control. So it will be overwritten everytime you do an update.<br />
<br />
This is the standard situation:<br />
-rw-r--r-- 1 root root 531573 Jun 6 02:01 /etc/tuxbox/satellites.xml <br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /etc/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/tuxbox/satellites.xml -> /etc/tuxbox/satellites.xml<br />
<br />
You see that /etc/tuxbox is the file that is provided by the image and is versioned, the others are not present by default, and are symlinked to the versioned file.<br />
<br />
If you have a custom file, you should place it in /etc/enigma2, and it will take precedence over the system file in /etc/tuxbox. If you don't, and overwrite the system file, it will be removed and overwritten with a new system the next time you run an update.<br />
<br />
<br />
=='''<N/A> in a bouquet list'''==<br />
When you have a <N/A> in your channel (bouquet) list there is a mismatch between 2 files <br />
lamedb <br />
and <br />
satellites.xml. <br />
You can not solve this by a scan or downloding a settings list, because when you scan (which happens on the basis of the satellites.xml) the lamedb is updated with the wrong service refs. This way the entry that is in the bouquet file can no longer be found in the lamedb and thus yields an <N/A>.<br />
<br />
What you will need to do is remove the file <br />
satellites.xml<br />
<br />
which normally is located in <br />
<br />
/etc/tuxbox/satellites.xml<br />
<br />
and delete it. Then install a new one.<br />
<br />
opkg update<br />
opkg install tuxbox-common --force-reinstall<br />
<br />
<br />
=='''Splash screen replacement'''==<br />
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.<br />
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer. <br />
<br />
If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:<br />
<br />
splash screen site:openpli.org<br />
<br />
===For the Edision jump to [[Problems_and_Solutions#Edision_related | <span style="color:SteelBlue">Restore Splash screen for Edision</span>]]===<br />
<br />
===For the Vu<sup>+</sup> jump to [[Problems_and_Solutions#Restore_Splash_screen_for_Factory_bootlogo | <span style="color:SteelBlue">Restore Splash screen for Vu</span>]]===<br />
<br />
===For the Zgemma jump to [[Problems_and_Solutions#Zgemma_related | <span style="color:SteelBlue">Restore Splash screen for Zgemma</span>]]===<br />
<br />
<br />
=='''Time, if you have problems getting the correct time'''==<br />
<br />
<br />
<br />
<br />
[[File:Problems and Solutions-007.jpg|frameless|centre|750px]]<br />
<br />
<br />
<br />
<u>'''Please note</u>''': As of OpenPLi 8.1 systemtime is integrated in OpenPLi and by default enabled, so you don't have to install it separately (as suggested below) anymore. If for some reason you want to change the settings goto '''Menu -> Setup -> System -> Customize''' (scroll way down to the bottom). You can choose between Auto - Transponder Time (satellite) Internet.<br />
----<br />
<br />
Method for OpenPLi 8.0 and below:<br />
<br />
There are 2 solutions, if somehow you don't have the right time on you receiver, using the internet or use the transponder of a satellite.<br />
<br />
===Internet===<br />
Here you install a plugin called Systemtime, it is in '''Main menu > Pluginbrowser > Download plugins > Systemplugins''' and uses NTP, just like your desktop PC, to get the time from an internet time server, so after installing it, it will be in '''Main menu > Setup > Sytem''' and there are various settings.<br />
<br />
===Satellite===<br />
OpenPLi will, at startup retrieve the time from a transponder, so if you have a satellite setup, it is wise to make use of the [https://wiki.openpli.org/index.php/Hidden_functions#Startup_Service<span style="color:SteelBlue">Startup service</span>]. By doing so and choosing a reliable transponder (=channel) you will always have the right time. For the Dutch, choosing an NPO channel will be a good choice.<br />
<br />
=='''Unsupported receiver! How to request OpenPLi team to support a new receiver brand or model?'''==<br />
When your receiver is not supported by OpenPLi and you want it to be supported, what now? So before we can support any type of receiver, there have to be a few requirements met:<br />
<br />
#'''It must be an opensource receiver.''' - So not closed source.<br />
#'''It must be an Enigma2 receiver.''' - As we only support OpenEmbedded ([https://wiki.yoctoproject.org/wiki/Releases<span style="color:SteelBlue">Yocto project</span>]) boxes running Enigma2. This is essential of course as Enigma2 is the operating system that OpenPLi runs on.<br />
#'''The manufacturer/vendor has to ask us, so not the other way around!''' - As in the manufacturer/vendor has to mail OpenPLi to request support for this type/brand of receiver. <br />
#'''The manufacturer/vendor has to provide us (as in the OpenPLi team) with a functioning BSP layer.''' - A BSP ('''B'''oard '''S'''upport '''P'''ackage) contains, among other things, the drivers needed to build OpenPLi for your receiver. <br />
#'''We need interaction with the development team of the manufacturer/vendor.''' - The manufacturer needs to create the BSP and we need to be able to report and get driver bugs fixed, which is the reason we '''NEVER''' accept requests from end-users, we '''ONLY''' accept support requests from the manufacturer/vendor!<br />
<br />
=='''USB memory sticks working or not'''==<br />
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:<br />
<br />
#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.<br />
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.<br />
<br />
Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Problems_and_Solutions&diff=22879Problems and Solutions2023-01-14T17:24:09Z<p>Rick Hunter: /* Multiboot crash - Boot loop */</p>
<hr />
<div>=='''Alternative numbering mode'''==<br />
Are you confronted with channellist (bouquet) that don't start with the number 1, then enable this and it will. Goto '''Main Menu -> Setup -> System -> GUI Settings -> User Interface''' and enable "Alternative numbering mode"<br />
<br />
[[File:Problems-and-Solutions-001.jpg|frameless|centre|600px]]<br />
<br />
<br />
=='''Brand\Vendor related'''== <br />
==='''Vu<sup>+</sup> related'''=== <br />
<br />
===='''Cable Scan issue's?''' ====<br />
<br />
There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used. <br />
<br />
<u>This is the issue:</u><br />
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.<br />
<br />
/proc/stb/tsmux/input1_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input0_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input3:A<br />
/proc/stb/tsmux/input2:A<br />
/proc/stb/tsmux/input1:B<br />
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.<br />
<br />
<u>Temporary solution until reboot</u><br />
echo -n C > /proc/stb/tsmux/input2<br />
echo -n D > /proc/stb/tsmux/input3<br />
<br />
Note: VU+ should add input2_choices and input3_choices nodes.<br />
<br />
<u>Temporary Solution, that still works after a reboot:</u><br />
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207<br />
Reboot the receiver, and the scan problems are solved.<br />
<br />
===='''Restore Splash screen for Factory bootlogo'''====<br />
<br />
The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models: duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero, zero4k and the Duo 4K SE<br />
You do not have to pick one of the bootlogo's, your receiver selects only the file that must be needed. <br />
<br />
So the following steps must be taken:<br />
# place the content of the zip file on the USB pendrive <br />
# reboot your receiver<br />
# flash the 'image' (this will take just a few seconds)<br />
# when the flash is completed, remove the USB pendrive<br />
# restart your receiver<br />
<br />
<br />
<br />
duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the Duo 4K SE<br />
<br />
<u>Note</u>: for some reason Vu+ changed the name of the splash file introducing the Vu Duo 4K SE from splash_cfe_auto.bin to splash_auto.bin<br />
<br />
<br />
Download splash file: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=134711<br />
<br />
===''' Amiko related'''===<br />
===='''Restore Splash screen for Amiko Viper Combo HDD'''====<br />
Source: https://forums.openpli.org/topic/56843-flash-amiko-viper-combo/#entry1179308<br />
<br />
<br />
==='''Edision related'''===<br />
===='''Restore Splash screen for Edision'''====<br />
Source: https://forums.openpli.org/topic/47499-splash-for-edision-os-mega/#entry652041<br />
<br />
<br />
==='''ET6000'''===<br />
===='''Install bootloader'''====<br />
<br />
Unpack the zip and place the et6x00 folder with its contents on an usb stick. Flash this as if it were an image. Here is the link to the bootloader for the ET6000<br />
Here is the link to the bootloader for the ET6000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132322<br />
<br />
<br />
==='''ET7000'''===<br />
===='''Install bootloader'''====<br />
Unpack the zip and place the et7x00 folder with its contents on an usb stick. Flash this as if it were an image.<br />
Here is the link to the bootloader for the ET7000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132262<br />
<br />
<br />
==='''Zgemma related'''=== <br />
===='''Restore Splash screen for Zgemma'''====<br />
Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387<br />
<br />
<br />
=='''CI module with softcam (eg. OScam), so using both and making them work together'''==<br />
If for some reason you want to use a CI module and OScam, you will probably run into error messages. The problem or better the errors are there because CI modules are designed to work standalone. So if you want to make them working together, best practice is using the "Commoninterfaceassignment plugin”. So to let a CI work together with a softcam download and install "Commoninterfaceassignment plugin" which is located in the system section of the [[Plugin_Wiki:Information| <span style="color:SteelBlue">Plugin browser</span>]]. After installing the plugin goto '''Menu-> Setup -> SoftCam/CI -> Common Interface Assignment''' and define every channel for this CI module, that you have a subscription for. Enigma2 (OpenPLi) will then send all the other channels to the Softcam (OScam) and not to the CI module.<br />
<br />
<br />
=='''Crash logs'''==<br />
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org <span style="color:SteelBlue">forum</span>]. The crash log file is named like in the example below:<br />
<br />
enigma2_crash_3891289128.log<br />
<br />
<br />
===The location of the crash log file when there is a HDD (Harddisk) present===<br />
Normally the crash.log file is stored in the root of the HDD so in<br />
/media/hdd<br />
<br />
<br />
===The location of the crash.log file without any HDD (Harddisk) present===<br />
Normally the crash log file is stored in the <br />
/home/root<br />
<br />
<br />
===How to get the crash log file===<br />
If you don't want to use the command line or telnet to get the crash.log file, you can grab it using your favorite ftp client or just use a (internet)browser. On how to do this take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
<br />
=='''Debugging Enigma'''==<br />
<br />
===Debugging from the menu===<br />
As of OpenPLi 7.1 you can start debug mode from the menu, if you press the on/off key and hold it and a menu will appear which has the option to select '''Restart enigma in debug mode''', this will make the receiver restart and debug mode will be running in the background (you won't see this). <br />
[[File:Problems_and_Solutions-003.jpg|frameless|centre|750px]]<br />
Now you can start or test anything you think is not right or for some reason want to know what is happening in the background. Once you have tested what you wanted to test you can press the on/off button and hold it, a menu will appear which has the option to select '''Restart enigma in normal mode'''. <br />
[[File:Problems_and_Solutions-004.jpg|frameless|centre|750px]]<br />
Don't forget to do this, as debugging uses CPU power and it creates a debug file that keeps on growing as long as your debugging. The debug file that is created during debug is located at, <br />
<br />
/home/root/enigma.20190901.debuglog<br />
<br />
you can grab it using your favorite ftp client or just use a browser, on how to take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
===Debugging from the command line===<br />
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:<br />
root@<receiver>: init 4<br />
root@<receiver>: ENIGMA_DEBUG_LVL=4 enigma2<br />
<br />
To stop: Press CRTL-C. Enigma will halt. Then start enigma with:<br />
root@<receiver>: init 3<br />
Or reboot the receiver with:<br />
root@<receiver>: reboot<br />
<br />
<u>'''Note:'''</u> For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2'''<br /><br />
<br />
<br />
====For easier reading (Less logging) use:====<br />
<br />
ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2<br />
<br />
<br />
====Writing debug log (to a USB stick)====<br />
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /home/root/enigma.log<br />
<br />
or <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 2>&1 | tee ./enigma.log<br />
<br />
or to USB<br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /media/usb/enigma.log<br />
<br />
=='''Dual tuner problems'''==<br />
When your receiver has more than one tuner slot with 2 different tuners types, for instance DBV-T and DVB-C and you swap these tuners, then you might probably need to manually clean the nim entries in the [[Tips_and_Tweaks#Settings_file_in_OpenPLi| <span style="color:SteelBlue">settings</span>]] file and then reconfigure the tuner and perform a scan.<br />
<br />
<br />
<br />
=='''Flickering dashed line in screen'''==<br />
When you see a dashed flickering line on the "top" of the screen, you can cover this by pressing the menu when you are in the bouquetlist and select "cover dashed flickering line for this service".<br />
[[File:Problems_and_Solutions-003.png|frameless|centre|750px]]<br />
<br />
Or you can also install the plugin: '''Blackout Blind''' (enigma2-plugin-extensions-blackoutblind) this will permanently hide the dotted lines.<br />
<br />
=='''Freeze, Lock, Halt, Hang of OpenPLi and what to do, to gain control again over your receiver'''==<br />
When this happens, never (well only as a real last resort!!!) switch off the power or pull the power plug, this will -in time- certainly destroy the filesystem on which OpenPLi is running and as by-catch this may also destroy the filesystem of your HDD (when installed). So the best way is to login with [[Tips_and_Tweaks#Accessing_your_receiver_and_editing_files_using_the_command_line | <span style="color:SteelBlue">Telnet</span>]] and type:<br />
<br />
root@<receiver>: init 4<br />
<br />
This stops Enigma2 (operating system) gracefully, waiting for all it's components to stop and places Enigma2 into a "sleep" mode and then type:<br />
<br />
root@<receiver>: init 3<br />
<br />
This wakes enigma from the "sleeping" state and restarts the GUI (Graphical User Interface).<br />
<br />
=='''Harddisk Check'''==<br />
Harddrives will fail, that's just a question of time, so a check from time to time is prudent,certainly when you have switched it off using the power switch or pulled the plug, as this will mess-up the filesystem. (btw it can also be a USB stick but it has to be formated ext3 or 4). When a internal drive is present you can check it using the menu. '''Main menu -> Setup -> System -> Expert Settings -> Harddisk -> Filesystem check'''.<br />
<br />
It needs some xpert to explain what to do if the hardrive is busy and umount does not do the trick.<br />
<br />
=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se / Zero 4K)'''==<br />
By default some Vu<sup>+</sup> boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the <br />
''extensions'' section of the [[Plugin_Wiki| <span style="color:SteelBlue">plugin browser</span>]].<br />
<br />
<br />
=='''HbbTV and Kodi problems'''==<br />
HbbTV applications, browsers (Chromium) and Kodi make use of functionality of the SoC (the "processor") that is not required for enigma ("watch TV"). <br />
This functionality is in the SoC, but must also be made accessible/available for applications (which include browsers and Kodi). <br />
The supplier does this by means of the drivers, the sources of which are not available (also known as "closed source"). Because the interface to those <br />
drivers is not known (and we also have no sources) it cannot be otherwise than that the supplier also supplies the applications (Kodi, browsers ...). <br />
Sometimes they do, sometimes they don't, it depends on the supplier. The form in which these applications are offered is usually also <br />
without source, at least in part. This means that we are completely dependent on the supplier for the whole, if we have no sources, we cannot do anything. <br />
Especially if we move to a newer version of OE, this can cause problems and we have seen this for years, at various levels. Sometimes we manage to get it all going, but often not.<br />
<br />
<br />
<u>Short summary:</u> for applications such as Kodi and HbbTV OpenPLi is completely dependent on the <u>supplier as in Vendor</u>, OpenPLi cannot do anything about that, so OpenPLi cannot guarantee HbbTV and Kodi. If it works: Great! If it doesn't work then the supplier did not consider it necessary to offer it to the user in working order. Sad but true.<br />
<br />
=='''Missing menu items or changing the access level of the configuration menu'''==<br />
As of OpenPLi 7.0 during a fresh flash (so no backup used) during the [[Installation | <span style="color:SteelBlue">Installation</span>]] you will be asked which suer mode you want to use. Here you can choose between 3 different user modes; Normal, Advanced or Expert. Each mode will reveal more options in the Menu, so if you are missing menu items, then you can change the user mode in the menu go to '''Main Menu > Setup > System > Expert settings > User Mode'''.<br />
<br />
<br />
=='''Movies or media files not playing'''==<br />
To play a certain movie or media file a codec ('''CO'''der/'''DEC'''oder) is needed. When a movie file won't play in OpenPLi this codec might be "missing" and sadly there is no way to add this missing codec, because opposite to a personal computer, which can install missing codecs, a STB (SetTopBOX)/receiver uses codecs from within the chip, so if the codec needed for a certain movie file is not in the chip of the receiver you are using, it cannot play it and you cannot add this missing codec, as you cannot add anything to a silicon chip. You could try using the [[Plugin_Wiki:ServiceApp| <span style="color:SteelBlue">'''ServiceApp'''</span>]].<br />
<br />
So if you have a movie that can't be played, the only thing you can try, is to re-code it. For this you can use programs like [https://handbrake.fr/ <span style="color:SteelBlue">Handbrake</span>]. A good choice would be h264 or h265 as the video codec and mp2, mp3 or ac3 as an audio codec.<br />
<br />
<br />
<br />
<u>Please Note:</u> Files like AVI and MKV are containers and say nothing about the CODEC needed to play whats inside them!!<br />
<br />
=='''Mountmanager Problems'''==<br />
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.<br />
<br />
<br />
===Autodetection===<br />
As of OpenPLi 7.2 CIFS config has SMB version and security protocol autodetection, so that you no longer have to start looking for whether options have to be given, they are now entered automatically, so practically it means that the suggestions below should not be needed anymore, the system will try all options until one settings works!!<br />
<br />
===Older vs newer Kernel===<br />
<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution. <br />
<br />
<u>The solution</u> is simple, you can try the following; If you make a mount with [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.<br />
<br />
Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.<br />
<br />
===Older vs newer SMB Protocol===<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).<br />
<br />
Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols, when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been configured with, and if you, as a user, need a different version, you will need to specify this in the mount options.<br />
<br />
Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.<br />
<br />
<br />
<u>The solution</u> is to change the SMB version used to mount, to do this in [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]] change the "mount options" from "rw" to "rw, vers=3.0" or whatever version you want to mount. You might have to try a few, if you don't know which one your server supports, always start with the highest version.<br />
<br />
This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/<br />
<br />
The same is true for the authentication mechanism used to setup a share/mount. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). So depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the command line too.<br />
<br />
<br />
<u>'''Note:'''</u> For the Dutch, also have a look here https://forums.openpli.org/topic/71313-bestaande-en-werkende-cifs-mounts-werken-nu-niet-meer-in-72rc/page-5#entry1114216<br />
<br />
<br />
'''So as explained above, if the protocol version that the box uses differ from the server side, then no connection is possible without additional actions.'''<br />
----<br />
If you have a server that does not support SMBv2, you can force a connection to SMBv1 on the box by adding vers=1.0 to the mount options<br />
If you have a server that does not support NTLMssp, you can change it by adding sec=ntlmv2 or sec=ntlm to the mount options on the box<br />
<br />
What works is a matter of trying, you may even need both. See below is an example on connecting to a Synology that "still" uses Samba version 1 and security NTLM:<br />
<br />
<br />
<br />
[[File:Problems_and_Solutions-005.jpg|frameless|centre|750px]]<br />
[[File:Problems_and_Solutions-006.jpg|frameless|centre|750px]]<br />
<br />
=='''Multiboot crash - Boot loop '''==<br />
<br />
If you make use of multiboot and somehow get stuck at boot, by let's say a GSOD (Green Screen of Death) you can try to login your box/receiver with telnet and try the following:<br />
<br />
mkdir /tmp/t<br />
mount /dev/mmcblk0p3 /tmp/t<br />
cd /tmp/t<br />
<br />
Because the '''Edision OS mio ...''' uses mmcblk1... this throws an error and you can try this:<br />
<br />
mount /dev/mmcblk1p3 /tmp/t<br />
cd /tmp/t<br />
<br />
You should then see in this directory several startup files. If you eg want to start image in slot 1 do<br />
<br />
cp STARTUP_1 STARTUP<br />
<br />
If you want to start image in slot 2 then<br />
<br />
cp STARTUP_2 STARTUP<br />
<br />
And so on, then reboot the box.<br />
<br />
'''On the AB PULSe 4K:<br />
''' - turn it off with the back power switch.<br />
- Point the RCU to it and press the power button of the RCU (keep it pressed).<br />
- turn on the back power switch (while still pressing the RCU power button don't release it).<br />
- When the boot selection screen is displayed release the RCU power button and select the slot you want to boot to.<br />
<br />
If you want to flash from the Bootmenu insert the USB stick with the .zip image file on the back USB slot (it doesn't work on the front one!).<br />
<br />
Remark this doesn't work with the front panel power button you really need to use the RCU.<br />
<br />
'''On the HD51 use the following commands to start with bootslot 2:'''<br />
<br />
mkdir /tmp/t<br />
<br />
mount /dev/mmcblk0p1 /tmp/t<br />
<br />
cd /tmp/t<br />
<br />
cp STARTUP_BOOTSLOT_1_MODE_1 STARTUP<br />
<br />
reboot<br />
<br />
EXAMPLES of content within STARTUP files...<br />
Booting from SLOT 2-Mode1<br />
boot emmcflash0.kernel2 'root=/dev/mmcblk0p5 rw rootwait hd51_4.boxmode=1'<br />
Booting from SLOT 4-Mode1<br />
boot emmcflash0.kernel4 'root=/dev/mmcblk0p9 rw rootwait hd51_4.boxmode=1'<br />
<br />
=='''Reset lost password'''==<br />
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.<br />
<br />
<br />
===Install the "setpasswd" plugin===<br />
Easiest way is to install a plugin and reset or delete your password. Goto Main menu -> Plugin browser and press the green button "download plugins" goto systemplugins and goto setpasswd and press ok on your remote to install it. After you installed goto Main menu -> Setup -> System -> Change Root Password and press the red button to delete it.<br />
<br />
===Using the command line method 1===<br />
I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution. <br />
# Go to the map /etc where you find the file shadow. <br />
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'. <br />
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow. <br />
<br />
<br />
===Using the command line: method 2 ===<br />
There is a second scenario to solve this.<br />
# Go to the map /etc where you also find the file passwd.<br />
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++<br />
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW<br />
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh<br />
# Save / overwrite this file and exit Notepad ++.<br />
<br />
<br />
=='''Satellites.xml returning-over-and-over'''==<br />
The default satellites.xml is in the image, and is under version control. So it will be overwritten everytime you do an update.<br />
<br />
This is the standard situation:<br />
-rw-r--r-- 1 root root 531573 Jun 6 02:01 /etc/tuxbox/satellites.xml <br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /etc/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/tuxbox/satellites.xml -> /etc/tuxbox/satellites.xml<br />
<br />
You see that /etc/tuxbox is the file that is provided by the image and is versioned, the others are not present by default, and are symlinked to the versioned file.<br />
<br />
If you have a custom file, you should place it in /etc/enigma2, and it will take precedence over the system file in /etc/tuxbox. If you don't, and overwrite the system file, it will be removed and overwritten with a new system the next time you run an update.<br />
<br />
<br />
=='''<N/A> in a bouquet list'''==<br />
When you have a <N/A> in your channel (bouquet) list there is a mismatch between 2 files <br />
lamedb <br />
and <br />
satellites.xml. <br />
You can not solve this by a scan or downloding a settings list, because when you scan (which happens on the basis of the satellites.xml) the lamedb is updated with the wrong service refs. This way the entry that is in the bouquet file can no longer be found in the lamedb and thus yields an <N/A>.<br />
<br />
What you will need to do is remove the file <br />
satellites.xml<br />
<br />
which normally is located in <br />
<br />
/etc/tuxbox/satellites.xml<br />
<br />
and delete it. Then install a new one.<br />
<br />
opkg update<br />
opkg install tuxbox-common --force-reinstall<br />
<br />
<br />
=='''Splash screen replacement'''==<br />
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.<br />
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer. <br />
<br />
If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:<br />
<br />
splash screen site:openpli.org<br />
<br />
===For the Edision jump to [[Problems_and_Solutions#Edision_related | <span style="color:SteelBlue">Restore Splash screen for Edision</span>]]===<br />
<br />
===For the Vu<sup>+</sup> jump to [[Problems_and_Solutions#Restore_Splash_screen_for_Factory_bootlogo | <span style="color:SteelBlue">Restore Splash screen for Vu</span>]]===<br />
<br />
===For the Zgemma jump to [[Problems_and_Solutions#Zgemma_related | <span style="color:SteelBlue">Restore Splash screen for Zgemma</span>]]===<br />
<br />
<br />
=='''Time, if you have problems getting the correct time'''==<br />
<br />
<br />
<br />
<br />
[[File:Problems and Solutions-007.jpg|frameless|centre|750px]]<br />
<br />
<br />
<br />
<u>'''Please note</u>''': As of OpenPLi 8.1 systemtime is integrated in OpenPLi and by default enabled, so you don't have to install it separately (as suggested below) anymore. If for some reason you want to change the settings goto '''Menu -> Setup -> System -> Customize''' (scroll way down to the bottom). You can choose between Auto - Transponder Time (satellite) Internet.<br />
----<br />
<br />
Method for OpenPLi 8.0 and below:<br />
<br />
There are 2 solutions, if somehow you don't have the right time on you receiver, using the internet or use the transponder of a satellite.<br />
<br />
===Internet===<br />
Here you install a plugin called Systemtime, it is in '''Main menu > Pluginbrowser > Download plugins > Systemplugins''' and uses NTP, just like your desktop PC, to get the time from an internet time server, so after installing it, it will be in '''Main menu > Setup > Sytem''' and there are various settings.<br />
<br />
===Satellite===<br />
OpenPLi will, at startup retrieve the time from a transponder, so if you have a satellite setup, it is wise to make use of the [https://wiki.openpli.org/index.php/Hidden_functions#Startup_Service<span style="color:SteelBlue">Startup service</span>]. By doing so and choosing a reliable transponder (=channel) you will always have the right time. For the Dutch, choosing an NPO channel will be a good choice.<br />
<br />
=='''Unsupported receiver! How to request OpenPLi team to support a new receiver brand or model?'''==<br />
When your receiver is not supported by OpenPLi and you want it to be supported, what now? So before we can support any type of receiver, there have to be a few requirements met:<br />
<br />
#'''It must be an opensource receiver.''' - So not closed source.<br />
#'''It must be an Enigma2 receiver.''' - As we only support OpenEmbedded ([https://wiki.yoctoproject.org/wiki/Releases<span style="color:SteelBlue">Yocto project</span>]) boxes running Enigma2. This is essential of course as Enigma2 is the operating system that OpenPLi runs on.<br />
#'''The manufacturer/vendor has to ask us, so not the other way around!''' - As in the manufacturer/vendor has to mail OpenPLi to request support for this type/brand of receiver. <br />
#'''The manufacturer/vendor has to provide us (as in the OpenPLi team) with a functioning BSP layer.''' - A BSP ('''B'''oard '''S'''upport '''P'''ackage) contains, among other things, the drivers needed to build OpenPLi for your receiver. <br />
#'''We need interaction with the development team of the manufacturer/vendor.''' - The manufacturer needs to create the BSP and we need to be able to report and get driver bugs fixed, which is the reason we '''NEVER''' accept requests from end-users, we '''ONLY''' accept support requests from the manufacturer/vendor!<br />
<br />
=='''USB memory sticks working or not'''==<br />
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:<br />
<br />
#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.<br />
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.<br />
<br />
Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Problems_and_Solutions&diff=22875Problems and Solutions2023-01-14T17:15:32Z<p>Rick Hunter: /* Multiboot crash - Boot loop */</p>
<hr />
<div>=='''Alternative numbering mode'''==<br />
Are you confronted with channellist (bouquet) that don't start with the number 1, then enable this and it will. Goto '''Main Menu -> Setup -> System -> GUI Settings -> User Interface''' and enable "Alternative numbering mode"<br />
<br />
[[File:Problems-and-Solutions-001.jpg|frameless|centre|600px]]<br />
<br />
<br />
=='''Brand\Vendor related'''== <br />
==='''Vu<sup>+</sup> related'''=== <br />
<br />
===='''Cable Scan issue's?''' ====<br />
<br />
There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used. <br />
<br />
<u>This is the issue:</u><br />
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.<br />
<br />
/proc/stb/tsmux/input1_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input0_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input3:A<br />
/proc/stb/tsmux/input2:A<br />
/proc/stb/tsmux/input1:B<br />
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.<br />
<br />
<u>Temporary solution until reboot</u><br />
echo -n C > /proc/stb/tsmux/input2<br />
echo -n D > /proc/stb/tsmux/input3<br />
<br />
Note: VU+ should add input2_choices and input3_choices nodes.<br />
<br />
<u>Temporary Solution, that still works after a reboot:</u><br />
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207<br />
Reboot the receiver, and the scan problems are solved.<br />
<br />
===='''Restore Splash screen for Factory bootlogo'''====<br />
<br />
The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models: duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero, zero4k and the Duo 4K SE<br />
You do not have to pick one of the bootlogo's, your receiver selects only the file that must be needed. <br />
<br />
So the following steps must be taken:<br />
# place the content of the zip file on the USB pendrive <br />
# reboot your receiver<br />
# flash the 'image' (this will take just a few seconds)<br />
# when the flash is completed, remove the USB pendrive<br />
# restart your receiver<br />
<br />
<br />
<br />
duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the Duo 4K SE<br />
<br />
<u>Note</u>: for some reason Vu+ changed the name of the splash file introducing the Vu Duo 4K SE from splash_cfe_auto.bin to splash_auto.bin<br />
<br />
<br />
Download splash file: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=134711<br />
<br />
===''' Amiko related'''===<br />
===='''Restore Splash screen for Amiko Viper Combo HDD'''====<br />
Source: https://forums.openpli.org/topic/56843-flash-amiko-viper-combo/#entry1179308<br />
<br />
<br />
==='''Edision related'''===<br />
===='''Restore Splash screen for Edision'''====<br />
Source: https://forums.openpli.org/topic/47499-splash-for-edision-os-mega/#entry652041<br />
<br />
<br />
==='''ET6000'''===<br />
===='''Install bootloader'''====<br />
<br />
Unpack the zip and place the et6x00 folder with its contents on an usb stick. Flash this as if it were an image. Here is the link to the bootloader for the ET6000<br />
Here is the link to the bootloader for the ET6000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132322<br />
<br />
<br />
==='''ET7000'''===<br />
===='''Install bootloader'''====<br />
Unpack the zip and place the et7x00 folder with its contents on an usb stick. Flash this as if it were an image.<br />
Here is the link to the bootloader for the ET7000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132262<br />
<br />
<br />
==='''Zgemma related'''=== <br />
===='''Restore Splash screen for Zgemma'''====<br />
Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387<br />
<br />
<br />
=='''CI module with softcam (eg. OScam), so using both and making them work together'''==<br />
If for some reason you want to use a CI module and OScam, you will probably run into error messages. The problem or better the errors are there because CI modules are designed to work standalone. So if you want to make them working together, best practice is using the "Commoninterfaceassignment plugin”. So to let a CI work together with a softcam download and install "Commoninterfaceassignment plugin" which is located in the system section of the [[Plugin_Wiki:Information| <span style="color:SteelBlue">Plugin browser</span>]]. After installing the plugin goto '''Menu-> Setup -> SoftCam/CI -> Common Interface Assignment''' and define every channel for this CI module, that you have a subscription for. Enigma2 (OpenPLi) will then send all the other channels to the Softcam (OScam) and not to the CI module.<br />
<br />
<br />
=='''Crash logs'''==<br />
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org <span style="color:SteelBlue">forum</span>]. The crash log file is named like in the example below:<br />
<br />
enigma2_crash_3891289128.log<br />
<br />
<br />
===The location of the crash log file when there is a HDD (Harddisk) present===<br />
Normally the crash.log file is stored in the root of the HDD so in<br />
/media/hdd<br />
<br />
<br />
===The location of the crash.log file without any HDD (Harddisk) present===<br />
Normally the crash log file is stored in the <br />
/home/root<br />
<br />
<br />
===How to get the crash log file===<br />
If you don't want to use the command line or telnet to get the crash.log file, you can grab it using your favorite ftp client or just use a (internet)browser. On how to do this take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
<br />
=='''Debugging Enigma'''==<br />
<br />
===Debugging from the menu===<br />
As of OpenPLi 7.1 you can start debug mode from the menu, if you press the on/off key and hold it and a menu will appear which has the option to select '''Restart enigma in debug mode''', this will make the receiver restart and debug mode will be running in the background (you won't see this). <br />
[[File:Problems_and_Solutions-003.jpg|frameless|centre|750px]]<br />
Now you can start or test anything you think is not right or for some reason want to know what is happening in the background. Once you have tested what you wanted to test you can press the on/off button and hold it, a menu will appear which has the option to select '''Restart enigma in normal mode'''. <br />
[[File:Problems_and_Solutions-004.jpg|frameless|centre|750px]]<br />
Don't forget to do this, as debugging uses CPU power and it creates a debug file that keeps on growing as long as your debugging. The debug file that is created during debug is located at, <br />
<br />
/home/root/enigma.20190901.debuglog<br />
<br />
you can grab it using your favorite ftp client or just use a browser, on how to take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
===Debugging from the command line===<br />
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:<br />
root@<receiver>: init 4<br />
root@<receiver>: ENIGMA_DEBUG_LVL=4 enigma2<br />
<br />
To stop: Press CRTL-C. Enigma will halt. Then start enigma with:<br />
root@<receiver>: init 3<br />
Or reboot the receiver with:<br />
root@<receiver>: reboot<br />
<br />
<u>'''Note:'''</u> For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2'''<br /><br />
<br />
<br />
====For easier reading (Less logging) use:====<br />
<br />
ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2<br />
<br />
<br />
====Writing debug log (to a USB stick)====<br />
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /home/root/enigma.log<br />
<br />
or <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 2>&1 | tee ./enigma.log<br />
<br />
or to USB<br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /media/usb/enigma.log<br />
<br />
=='''Dual tuner problems'''==<br />
When your receiver has more than one tuner slot with 2 different tuners types, for instance DBV-T and DVB-C and you swap these tuners, then you might probably need to manually clean the nim entries in the [[Tips_and_Tweaks#Settings_file_in_OpenPLi| <span style="color:SteelBlue">settings</span>]] file and then reconfigure the tuner and perform a scan.<br />
<br />
<br />
<br />
=='''Flickering dashed line in screen'''==<br />
When you see a dashed flickering line on the "top" of the screen, you can cover this by pressing the menu when you are in the bouquetlist and select "cover dashed flickering line for this service".<br />
[[File:Problems_and_Solutions-003.png|frameless|centre|750px]]<br />
<br />
Or you can also install the plugin: '''Blackout Blind''' (enigma2-plugin-extensions-blackoutblind) this will permanently hide the dotted lines.<br />
<br />
=='''Freeze, Lock, Halt, Hang of OpenPLi and what to do, to gain control again over your receiver'''==<br />
When this happens, never (well only as a real last resort!!!) switch off the power or pull the power plug, this will -in time- certainly destroy the filesystem on which OpenPLi is running and as by-catch this may also destroy the filesystem of your HDD (when installed). So the best way is to login with [[Tips_and_Tweaks#Accessing_your_receiver_and_editing_files_using_the_command_line | <span style="color:SteelBlue">Telnet</span>]] and type:<br />
<br />
root@<receiver>: init 4<br />
<br />
This stops Enigma2 (operating system) gracefully, waiting for all it's components to stop and places Enigma2 into a "sleep" mode and then type:<br />
<br />
root@<receiver>: init 3<br />
<br />
This wakes enigma from the "sleeping" state and restarts the GUI (Graphical User Interface).<br />
<br />
=='''Harddisk Check'''==<br />
Harddrives will fail, that's just a question of time, so a check from time to time is prudent,certainly when you have switched it off using the power switch or pulled the plug, as this will mess-up the filesystem. (btw it can also be a USB stick but it has to be formated ext3 or 4). When a internal drive is present you can check it using the menu. '''Main menu -> Setup -> System -> Expert Settings -> Harddisk -> Filesystem check'''.<br />
<br />
It needs some xpert to explain what to do if the hardrive is busy and umount does not do the trick.<br />
<br />
=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se / Zero 4K)'''==<br />
By default some Vu<sup>+</sup> boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the <br />
''extensions'' section of the [[Plugin_Wiki| <span style="color:SteelBlue">plugin browser</span>]].<br />
<br />
<br />
=='''HbbTV and Kodi problems'''==<br />
HbbTV applications, browsers (Chromium) and Kodi make use of functionality of the SoC (the "processor") that is not required for enigma ("watch TV"). <br />
This functionality is in the SoC, but must also be made accessible/available for applications (which include browsers and Kodi). <br />
The supplier does this by means of the drivers, the sources of which are not available (also known as "closed source"). Because the interface to those <br />
drivers is not known (and we also have no sources) it cannot be otherwise than that the supplier also supplies the applications (Kodi, browsers ...). <br />
Sometimes they do, sometimes they don't, it depends on the supplier. The form in which these applications are offered is usually also <br />
without source, at least in part. This means that we are completely dependent on the supplier for the whole, if we have no sources, we cannot do anything. <br />
Especially if we move to a newer version of OE, this can cause problems and we have seen this for years, at various levels. Sometimes we manage to get it all going, but often not.<br />
<br />
<br />
<u>Short summary:</u> for applications such as Kodi and HbbTV OpenPLi is completely dependent on the <u>supplier as in Vendor</u>, OpenPLi cannot do anything about that, so OpenPLi cannot guarantee HbbTV and Kodi. If it works: Great! If it doesn't work then the supplier did not consider it necessary to offer it to the user in working order. Sad but true.<br />
<br />
=='''Missing menu items or changing the access level of the configuration menu'''==<br />
As of OpenPLi 7.0 during a fresh flash (so no backup used) during the [[Installation | <span style="color:SteelBlue">Installation</span>]] you will be asked which suer mode you want to use. Here you can choose between 3 different user modes; Normal, Advanced or Expert. Each mode will reveal more options in the Menu, so if you are missing menu items, then you can change the user mode in the menu go to '''Main Menu > Setup > System > Expert settings > User Mode'''.<br />
<br />
<br />
=='''Movies or media files not playing'''==<br />
To play a certain movie or media file a codec ('''CO'''der/'''DEC'''oder) is needed. When a movie file won't play in OpenPLi this codec might be "missing" and sadly there is no way to add this missing codec, because opposite to a personal computer, which can install missing codecs, a STB (SetTopBOX)/receiver uses codecs from within the chip, so if the codec needed for a certain movie file is not in the chip of the receiver you are using, it cannot play it and you cannot add this missing codec, as you cannot add anything to a silicon chip. You could try using the [[Plugin_Wiki:ServiceApp| <span style="color:SteelBlue">'''ServiceApp'''</span>]].<br />
<br />
So if you have a movie that can't be played, the only thing you can try, is to re-code it. For this you can use programs like [https://handbrake.fr/ <span style="color:SteelBlue">Handbrake</span>]. A good choice would be h264 or h265 as the video codec and mp2, mp3 or ac3 as an audio codec.<br />
<br />
<br />
<br />
<u>Please Note:</u> Files like AVI and MKV are containers and say nothing about the CODEC needed to play whats inside them!!<br />
<br />
=='''Mountmanager Problems'''==<br />
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.<br />
<br />
<br />
===Autodetection===<br />
As of OpenPLi 7.2 CIFS config has SMB version and security protocol autodetection, so that you no longer have to start looking for whether options have to be given, they are now entered automatically, so practically it means that the suggestions below should not be needed anymore, the system will try all options until one settings works!!<br />
<br />
===Older vs newer Kernel===<br />
<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution. <br />
<br />
<u>The solution</u> is simple, you can try the following; If you make a mount with [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.<br />
<br />
Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.<br />
<br />
===Older vs newer SMB Protocol===<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).<br />
<br />
Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols, when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been configured with, and if you, as a user, need a different version, you will need to specify this in the mount options.<br />
<br />
Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.<br />
<br />
<br />
<u>The solution</u> is to change the SMB version used to mount, to do this in [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]] change the "mount options" from "rw" to "rw, vers=3.0" or whatever version you want to mount. You might have to try a few, if you don't know which one your server supports, always start with the highest version.<br />
<br />
This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/<br />
<br />
The same is true for the authentication mechanism used to setup a share/mount. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). So depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the command line too.<br />
<br />
<br />
<u>'''Note:'''</u> For the Dutch, also have a look here https://forums.openpli.org/topic/71313-bestaande-en-werkende-cifs-mounts-werken-nu-niet-meer-in-72rc/page-5#entry1114216<br />
<br />
<br />
'''So as explained above, if the protocol version that the box uses differ from the server side, then no connection is possible without additional actions.'''<br />
----<br />
If you have a server that does not support SMBv2, you can force a connection to SMBv1 on the box by adding vers=1.0 to the mount options<br />
If you have a server that does not support NTLMssp, you can change it by adding sec=ntlmv2 or sec=ntlm to the mount options on the box<br />
<br />
What works is a matter of trying, you may even need both. See below is an example on connecting to a Synology that "still" uses Samba version 1 and security NTLM:<br />
<br />
<br />
<br />
[[File:Problems_and_Solutions-005.jpg|frameless|centre|750px]]<br />
[[File:Problems_and_Solutions-006.jpg|frameless|centre|750px]]<br />
<br />
=='''Multiboot crash - Boot loop '''==<br />
<br />
If you make use of multiboot and somehow get stuck at boot, by let's say a GSOD (Green Screen of Death) you can try to login your box/receiver with telnet and try the following:<br />
<br />
mkdir /tmp/t<br />
mount /dev/mmcblk0p3 /tmp/t<br />
cd /tmp/t<br />
<br />
Because the '''Edision OS mio ...''' uses mmcblk1... this throws an error and you can try this:<br />
<br />
mount /dev/mmcblk1p3 /tmp/t<br />
cd /tmp/t<br />
<br />
You should then see in this directory several startup files. If you eg want to start image in slot 1 do<br />
<br />
cp STARTUP_1 STARTUP<br />
<br />
If you want to start image in slot 2 then<br />
<br />
cp STARTUP_2 STARTUP<br />
<br />
And so on, then reboot the box.<br />
<br />
'''On the AB PULSe 4K:<br />
''' - turn it off with the back power switch.<br />
- Point the RCU to it and press the power button of the RCU (keep it pressed).<br />
- turn on the back power switch (while still pressing the RCU power button don't release it).<br />
- When the boot selection screen is displayed release the RCU power button and select the slot you want to boot to.<br />
<br />
If you want to flash from the Bootmenu insert the USB stick with the .zip image file on the back USB slot (it doesn't work on the front one!).<br />
<br />
Remark this doesn't work with the front panel power button you really need to use the RCU.<br />
<br />
'''EXAMPLE: On the HD51 use the following commands to start with bootslot 2:'''<br />
<br />
mkdir /tmp/t<br />
<br />
mount /dev/mmcblk0p1 /tmp/t<br />
<br />
cd /tmp/t<br />
<br />
cp STARTUP_BOOTSLOT_1_MODE_1 STARTUP<br />
<br />
reboot<br />
<br />
=='''Reset lost password'''==<br />
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.<br />
<br />
<br />
===Install the "setpasswd" plugin===<br />
Easiest way is to install a plugin and reset or delete your password. Goto Main menu -> Plugin browser and press the green button "download plugins" goto systemplugins and goto setpasswd and press ok on your remote to install it. After you installed goto Main menu -> Setup -> System -> Change Root Password and press the red button to delete it.<br />
<br />
===Using the command line method 1===<br />
I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution. <br />
# Go to the map /etc where you find the file shadow. <br />
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'. <br />
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow. <br />
<br />
<br />
===Using the command line: method 2 ===<br />
There is a second scenario to solve this.<br />
# Go to the map /etc where you also find the file passwd.<br />
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++<br />
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW<br />
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh<br />
# Save / overwrite this file and exit Notepad ++.<br />
<br />
<br />
=='''Satellites.xml returning-over-and-over'''==<br />
The default satellites.xml is in the image, and is under version control. So it will be overwritten everytime you do an update.<br />
<br />
This is the standard situation:<br />
-rw-r--r-- 1 root root 531573 Jun 6 02:01 /etc/tuxbox/satellites.xml <br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /etc/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/tuxbox/satellites.xml -> /etc/tuxbox/satellites.xml<br />
<br />
You see that /etc/tuxbox is the file that is provided by the image and is versioned, the others are not present by default, and are symlinked to the versioned file.<br />
<br />
If you have a custom file, you should place it in /etc/enigma2, and it will take precedence over the system file in /etc/tuxbox. If you don't, and overwrite the system file, it will be removed and overwritten with a new system the next time you run an update.<br />
<br />
<br />
=='''<N/A> in a bouquet list'''==<br />
When you have a <N/A> in your channel (bouquet) list there is a mismatch between 2 files <br />
lamedb <br />
and <br />
satellites.xml. <br />
You can not solve this by a scan or downloding a settings list, because when you scan (which happens on the basis of the satellites.xml) the lamedb is updated with the wrong service refs. This way the entry that is in the bouquet file can no longer be found in the lamedb and thus yields an <N/A>.<br />
<br />
What you will need to do is remove the file <br />
satellites.xml<br />
<br />
which normally is located in <br />
<br />
/etc/tuxbox/satellites.xml<br />
<br />
and delete it. Then install a new one.<br />
<br />
opkg update<br />
opkg install tuxbox-common --force-reinstall<br />
<br />
<br />
=='''Splash screen replacement'''==<br />
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.<br />
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer. <br />
<br />
If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:<br />
<br />
splash screen site:openpli.org<br />
<br />
===For the Edision jump to [[Problems_and_Solutions#Edision_related | <span style="color:SteelBlue">Restore Splash screen for Edision</span>]]===<br />
<br />
===For the Vu<sup>+</sup> jump to [[Problems_and_Solutions#Restore_Splash_screen_for_Factory_bootlogo | <span style="color:SteelBlue">Restore Splash screen for Vu</span>]]===<br />
<br />
===For the Zgemma jump to [[Problems_and_Solutions#Zgemma_related | <span style="color:SteelBlue">Restore Splash screen for Zgemma</span>]]===<br />
<br />
<br />
=='''Time, if you have problems getting the correct time'''==<br />
<br />
<br />
<br />
<br />
[[File:Problems and Solutions-007.jpg|frameless|centre|750px]]<br />
<br />
<br />
<br />
<u>'''Please note</u>''': As of OpenPLi 8.1 systemtime is integrated in OpenPLi and by default enabled, so you don't have to install it separately (as suggested below) anymore. If for some reason you want to change the settings goto '''Menu -> Setup -> System -> Customize''' (scroll way down to the bottom). You can choose between Auto - Transponder Time (satellite) Internet.<br />
----<br />
<br />
Method for OpenPLi 8.0 and below:<br />
<br />
There are 2 solutions, if somehow you don't have the right time on you receiver, using the internet or use the transponder of a satellite.<br />
<br />
===Internet===<br />
Here you install a plugin called Systemtime, it is in '''Main menu > Pluginbrowser > Download plugins > Systemplugins''' and uses NTP, just like your desktop PC, to get the time from an internet time server, so after installing it, it will be in '''Main menu > Setup > Sytem''' and there are various settings.<br />
<br />
===Satellite===<br />
OpenPLi will, at startup retrieve the time from a transponder, so if you have a satellite setup, it is wise to make use of the [https://wiki.openpli.org/index.php/Hidden_functions#Startup_Service<span style="color:SteelBlue">Startup service</span>]. By doing so and choosing a reliable transponder (=channel) you will always have the right time. For the Dutch, choosing an NPO channel will be a good choice.<br />
<br />
=='''Unsupported receiver! How to request OpenPLi team to support a new receiver brand or model?'''==<br />
When your receiver is not supported by OpenPLi and you want it to be supported, what now? So before we can support any type of receiver, there have to be a few requirements met:<br />
<br />
#'''It must be an opensource receiver.''' - So not closed source.<br />
#'''It must be an Enigma2 receiver.''' - As we only support OpenEmbedded ([https://wiki.yoctoproject.org/wiki/Releases<span style="color:SteelBlue">Yocto project</span>]) boxes running Enigma2. This is essential of course as Enigma2 is the operating system that OpenPLi runs on.<br />
#'''The manufacturer/vendor has to ask us, so not the other way around!''' - As in the manufacturer/vendor has to mail OpenPLi to request support for this type/brand of receiver. <br />
#'''The manufacturer/vendor has to provide us (as in the OpenPLi team) with a functioning BSP layer.''' - A BSP ('''B'''oard '''S'''upport '''P'''ackage) contains, among other things, the drivers needed to build OpenPLi for your receiver. <br />
#'''We need interaction with the development team of the manufacturer/vendor.''' - The manufacturer needs to create the BSP and we need to be able to report and get driver bugs fixed, which is the reason we '''NEVER''' accept requests from end-users, we '''ONLY''' accept support requests from the manufacturer/vendor!<br />
<br />
=='''USB memory sticks working or not'''==<br />
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:<br />
<br />
#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.<br />
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.<br />
<br />
Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Problems_and_Solutions&diff=22871Problems and Solutions2023-01-14T17:12:40Z<p>Rick Hunter: /* Multiboot crash - Boot loop */</p>
<hr />
<div>=='''Alternative numbering mode'''==<br />
Are you confronted with channellist (bouquet) that don't start with the number 1, then enable this and it will. Goto '''Main Menu -> Setup -> System -> GUI Settings -> User Interface''' and enable "Alternative numbering mode"<br />
<br />
[[File:Problems-and-Solutions-001.jpg|frameless|centre|600px]]<br />
<br />
<br />
=='''Brand\Vendor related'''== <br />
==='''Vu<sup>+</sup> related'''=== <br />
<br />
===='''Cable Scan issue's?''' ====<br />
<br />
There is bug with the VU+ drivers so that a scan can not be completed if tuner D is used. <br />
<br />
<u>This is the issue:</u><br />
input3 and input2 have no input3_choices or input4_choices so the Enigma2 doesn't try to initialize them.<br />
<br />
/proc/stb/tsmux/input1_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input0_choices:CI0 CI1 A B<br />
/proc/stb/tsmux/input3:A<br />
/proc/stb/tsmux/input2:A<br />
/proc/stb/tsmux/input1:B<br />
/proc/stb/tsmux/input0:AA simple solution is to initialize them manually.<br />
<br />
<u>Temporary solution until reboot</u><br />
echo -n C > /proc/stb/tsmux/input2<br />
echo -n D > /proc/stb/tsmux/input3<br />
<br />
Note: VU+ should add input2_choices and input3_choices nodes.<br />
<br />
<u>Temporary Solution, that still works after a reboot:</u><br />
Install the IPK files that are posted at: https://forums.openpli.org/topic/49214-vuplus-duo2-dvb-t2-tuner-nim-tt3l10-stopped-working/page-3#entry701207<br />
Reboot the receiver, and the scan problems are solved.<br />
<br />
===='''Restore Splash screen for Factory bootlogo'''====<br />
<br />
The file that can be found at the forum (see below) will place the original factory bootlogo back on your receiver. The content of the file needs to be placed on a USB pen drive. The file contains splash screens for the models: duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero, zero4k and the Duo 4K SE<br />
You do not have to pick one of the bootlogo's, your receiver selects only the file that must be needed. <br />
<br />
So the following steps must be taken:<br />
# place the content of the zip file on the USB pendrive <br />
# reboot your receiver<br />
# flash the 'image' (this will take just a few seconds)<br />
# when the flash is completed, remove the USB pendrive<br />
# restart your receiver<br />
<br />
<br />
<br />
duo2, solo2, solo4k, solose, ultimo, ultimo4k, vuduo4k, uno, uno4k, uno4kse, zero and the Duo 4K SE<br />
<br />
<u>Note</u>: for some reason Vu+ changed the name of the splash file introducing the Vu Duo 4K SE from splash_cfe_auto.bin to splash_auto.bin<br />
<br />
<br />
Download splash file: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=134711<br />
<br />
===''' Amiko related'''===<br />
===='''Restore Splash screen for Amiko Viper Combo HDD'''====<br />
Source: https://forums.openpli.org/topic/56843-flash-amiko-viper-combo/#entry1179308<br />
<br />
<br />
==='''Edision related'''===<br />
===='''Restore Splash screen for Edision'''====<br />
Source: https://forums.openpli.org/topic/47499-splash-for-edision-os-mega/#entry652041<br />
<br />
<br />
==='''ET6000'''===<br />
===='''Install bootloader'''====<br />
<br />
Unpack the zip and place the et6x00 folder with its contents on an usb stick. Flash this as if it were an image. Here is the link to the bootloader for the ET6000<br />
Here is the link to the bootloader for the ET6000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132322<br />
<br />
<br />
==='''ET7000'''===<br />
===='''Install bootloader'''====<br />
Unpack the zip and place the et7x00 folder with its contents on an usb stick. Flash this as if it were an image.<br />
Here is the link to the bootloader for the ET7000<br />
<br />
Source: https://forums.openpli.org/index.php?app=core&module=attach&section=attach&attach_id=132262<br />
<br />
<br />
==='''Zgemma related'''=== <br />
===='''Restore Splash screen for Zgemma'''====<br />
Source: https://forums.openpli.org/topic/41521-boot-screen/#entry549387<br />
<br />
<br />
=='''CI module with softcam (eg. OScam), so using both and making them work together'''==<br />
If for some reason you want to use a CI module and OScam, you will probably run into error messages. The problem or better the errors are there because CI modules are designed to work standalone. So if you want to make them working together, best practice is using the "Commoninterfaceassignment plugin”. So to let a CI work together with a softcam download and install "Commoninterfaceassignment plugin" which is located in the system section of the [[Plugin_Wiki:Information| <span style="color:SteelBlue">Plugin browser</span>]]. After installing the plugin goto '''Menu-> Setup -> SoftCam/CI -> Common Interface Assignment''' and define every channel for this CI module, that you have a subscription for. Enigma2 (OpenPLi) will then send all the other channels to the Softcam (OScam) and not to the CI module.<br />
<br />
<br />
=='''Crash logs'''==<br />
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org <span style="color:SteelBlue">forum</span>]. The crash log file is named like in the example below:<br />
<br />
enigma2_crash_3891289128.log<br />
<br />
<br />
===The location of the crash log file when there is a HDD (Harddisk) present===<br />
Normally the crash.log file is stored in the root of the HDD so in<br />
/media/hdd<br />
<br />
<br />
===The location of the crash.log file without any HDD (Harddisk) present===<br />
Normally the crash log file is stored in the <br />
/home/root<br />
<br />
<br />
===How to get the crash log file===<br />
If you don't want to use the command line or telnet to get the crash.log file, you can grab it using your favorite ftp client or just use a (internet)browser. On how to do this take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
<br />
=='''Debugging Enigma'''==<br />
<br />
===Debugging from the menu===<br />
As of OpenPLi 7.1 you can start debug mode from the menu, if you press the on/off key and hold it and a menu will appear which has the option to select '''Restart enigma in debug mode''', this will make the receiver restart and debug mode will be running in the background (you won't see this). <br />
[[File:Problems_and_Solutions-003.jpg|frameless|centre|750px]]<br />
Now you can start or test anything you think is not right or for some reason want to know what is happening in the background. Once you have tested what you wanted to test you can press the on/off button and hold it, a menu will appear which has the option to select '''Restart enigma in normal mode'''. <br />
[[File:Problems_and_Solutions-004.jpg|frameless|centre|750px]]<br />
Don't forget to do this, as debugging uses CPU power and it creates a debug file that keeps on growing as long as your debugging. The debug file that is created during debug is located at, <br />
<br />
/home/root/enigma.20190901.debuglog<br />
<br />
you can grab it using your favorite ftp client or just use a browser, on how to take a look here [[Tips_and_Tweaks#Accessing_the_receiver_using_a_.28internet.29browser | <span style="color:SteelBlue">accessing files on your receiver</span>]].<br />
<br />
===Debugging from the command line===<br />
If you want to debug and want to know what is happening in Enigma, you can start your receiver in debug mode with the following command:<br />
root@<receiver>: init 4<br />
root@<receiver>: ENIGMA_DEBUG_LVL=4 enigma2<br />
<br />
To stop: Press CRTL-C. Enigma will halt. Then start enigma with:<br />
root@<receiver>: init 3<br />
Or reboot the receiver with:<br />
root@<receiver>: reboot<br />
<br />
<u>'''Note:'''</u> For '''debugging gstreamer''' with read actions stuff use: '''ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:6,*dvb*:6 enigma2'''<br /><br />
<br />
<br />
====For easier reading (Less logging) use:====<br />
<br />
ENIGMA_DEBUG_LVL=4 GST_DEBUG=*soup*:4,*dvb*:4 enigma2<br />
<br />
<br />
====Writing debug log (to a USB stick)====<br />
If for some reason your receiver reboots your debug log might be gone. Then plugin a USB stick in your receiver and use the command below, which writes the debug log to and USB stick <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /home/root/enigma.log<br />
<br />
or <br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 2>&1 | tee ./enigma.log<br />
<br />
or to USB<br />
<br />
ENIGMA_DEBUG_LVL=4 enigma2 > /media/usb/enigma.log<br />
<br />
=='''Dual tuner problems'''==<br />
When your receiver has more than one tuner slot with 2 different tuners types, for instance DBV-T and DVB-C and you swap these tuners, then you might probably need to manually clean the nim entries in the [[Tips_and_Tweaks#Settings_file_in_OpenPLi| <span style="color:SteelBlue">settings</span>]] file and then reconfigure the tuner and perform a scan.<br />
<br />
<br />
<br />
=='''Flickering dashed line in screen'''==<br />
When you see a dashed flickering line on the "top" of the screen, you can cover this by pressing the menu when you are in the bouquetlist and select "cover dashed flickering line for this service".<br />
[[File:Problems_and_Solutions-003.png|frameless|centre|750px]]<br />
<br />
Or you can also install the plugin: '''Blackout Blind''' (enigma2-plugin-extensions-blackoutblind) this will permanently hide the dotted lines.<br />
<br />
=='''Freeze, Lock, Halt, Hang of OpenPLi and what to do, to gain control again over your receiver'''==<br />
When this happens, never (well only as a real last resort!!!) switch off the power or pull the power plug, this will -in time- certainly destroy the filesystem on which OpenPLi is running and as by-catch this may also destroy the filesystem of your HDD (when installed). So the best way is to login with [[Tips_and_Tweaks#Accessing_your_receiver_and_editing_files_using_the_command_line | <span style="color:SteelBlue">Telnet</span>]] and type:<br />
<br />
root@<receiver>: init 4<br />
<br />
This stops Enigma2 (operating system) gracefully, waiting for all it's components to stop and places Enigma2 into a "sleep" mode and then type:<br />
<br />
root@<receiver>: init 3<br />
<br />
This wakes enigma from the "sleeping" state and restarts the GUI (Graphical User Interface).<br />
<br />
=='''Harddisk Check'''==<br />
Harddrives will fail, that's just a question of time, so a check from time to time is prudent,certainly when you have switched it off using the power switch or pulled the plug, as this will mess-up the filesystem. (btw it can also be a USB stick but it has to be formated ext3 or 4). When a internal drive is present you can check it using the menu. '''Main menu -> Setup -> System -> Expert Settings -> Harddisk -> Filesystem check'''.<br />
<br />
It needs some xpert to explain what to do if the hardrive is busy and umount does not do the trick.<br />
<br />
=='''I cannot record with my receiver or recording with a Zapper (eg. Vu Zero / Vu Solo Se / Zero 4K)'''==<br />
By default some Vu<sup>+</sup> boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the <br />
''extensions'' section of the [[Plugin_Wiki| <span style="color:SteelBlue">plugin browser</span>]].<br />
<br />
<br />
=='''HbbTV and Kodi problems'''==<br />
HbbTV applications, browsers (Chromium) and Kodi make use of functionality of the SoC (the "processor") that is not required for enigma ("watch TV"). <br />
This functionality is in the SoC, but must also be made accessible/available for applications (which include browsers and Kodi). <br />
The supplier does this by means of the drivers, the sources of which are not available (also known as "closed source"). Because the interface to those <br />
drivers is not known (and we also have no sources) it cannot be otherwise than that the supplier also supplies the applications (Kodi, browsers ...). <br />
Sometimes they do, sometimes they don't, it depends on the supplier. The form in which these applications are offered is usually also <br />
without source, at least in part. This means that we are completely dependent on the supplier for the whole, if we have no sources, we cannot do anything. <br />
Especially if we move to a newer version of OE, this can cause problems and we have seen this for years, at various levels. Sometimes we manage to get it all going, but often not.<br />
<br />
<br />
<u>Short summary:</u> for applications such as Kodi and HbbTV OpenPLi is completely dependent on the <u>supplier as in Vendor</u>, OpenPLi cannot do anything about that, so OpenPLi cannot guarantee HbbTV and Kodi. If it works: Great! If it doesn't work then the supplier did not consider it necessary to offer it to the user in working order. Sad but true.<br />
<br />
=='''Missing menu items or changing the access level of the configuration menu'''==<br />
As of OpenPLi 7.0 during a fresh flash (so no backup used) during the [[Installation | <span style="color:SteelBlue">Installation</span>]] you will be asked which suer mode you want to use. Here you can choose between 3 different user modes; Normal, Advanced or Expert. Each mode will reveal more options in the Menu, so if you are missing menu items, then you can change the user mode in the menu go to '''Main Menu > Setup > System > Expert settings > User Mode'''.<br />
<br />
<br />
=='''Movies or media files not playing'''==<br />
To play a certain movie or media file a codec ('''CO'''der/'''DEC'''oder) is needed. When a movie file won't play in OpenPLi this codec might be "missing" and sadly there is no way to add this missing codec, because opposite to a personal computer, which can install missing codecs, a STB (SetTopBOX)/receiver uses codecs from within the chip, so if the codec needed for a certain movie file is not in the chip of the receiver you are using, it cannot play it and you cannot add this missing codec, as you cannot add anything to a silicon chip. You could try using the [[Plugin_Wiki:ServiceApp| <span style="color:SteelBlue">'''ServiceApp'''</span>]].<br />
<br />
So if you have a movie that can't be played, the only thing you can try, is to re-code it. For this you can use programs like [https://handbrake.fr/ <span style="color:SteelBlue">Handbrake</span>]. A good choice would be h264 or h265 as the video codec and mp2, mp3 or ac3 as an audio codec.<br />
<br />
<br />
<br />
<u>Please Note:</u> Files like AVI and MKV are containers and say nothing about the CODEC needed to play whats inside them!!<br />
<br />
=='''Mountmanager Problems'''==<br />
Here are some solutions when you run into problems with mounting\sharing a medium (HDD) in your network.<br />
<br />
<br />
===Autodetection===<br />
As of OpenPLi 7.2 CIFS config has SMB version and security protocol autodetection, so that you no longer have to start looking for whether options have to be given, they are now entered automatically, so practically it means that the suggestions below should not be needed anymore, the system will try all options until one settings works!!<br />
<br />
===Older vs newer Kernel===<br />
<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
When your box uses a kernel 3.x ('''Menu-Information-About''') and you want to mount something that has a kernel 4.x your CIFS share might fail, even though you entered the data carefully, but there is a solution. <br />
<br />
<u>The solution</u> is simple, you can try the following; If you make a mount with [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]], change the "mount options" from "rw" to "rw, sec=ntlm", this will lower the security standard from ntlmv2 (default with kernel 4.x and up) to ntlm.<br />
<br />
Now exit and re-mount or Reboot your box and if this was the cause, you can now access your share.<br />
<br />
===Older vs newer SMB Protocol===<br />
'''<u>Note: </u>''' This only accounts for OpenPLi versions below 7.2, as of version 7.2 SMB and SEC protocols are auto detected,so please do enter anything in the options:<br />
<br />
There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.technet.microsoft.com/josebda/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-are-you-using/ for more in-depth information).<br />
<br />
Recently, due to several security issues, an action has been ongoing to disable the unsafe SMBv1, not only in Windows, but also in NAS systems like Synology for example. Windows has the option to cycle through all available and allowed protocols, when you want to connect to a share, so you as a user don't notice anything and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been configured with, and if you, as a user, need a different version, you will need to specify this in the mount options.<br />
<br />
Up to kernel v4.13 (at the moment of writing all supported receivers), the default was SMBv1, after that, the default has been upgraded to SMBv3. So if your box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.<br />
<br />
<br />
<u>The solution</u> is to change the SMB version used to mount, to do this in [[MountManager | <span style="color:SteelBlue">Mountmanager</span>]] change the "mount options" from "rw" to "rw, vers=3.0" or whatever version you want to mount. You might have to try a few, if you don't know which one your server supports, always start with the highest version.<br />
<br />
This is a good overview on this subject: https://www.happyassassin.net/2017/11/03/linux-kernel-4-13-and-smb-protocol-version-fun/<br />
<br />
The same is true for the authentication mechanism used to setup a share/mount. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). So depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the command line too.<br />
<br />
<br />
<u>'''Note:'''</u> For the Dutch, also have a look here https://forums.openpli.org/topic/71313-bestaande-en-werkende-cifs-mounts-werken-nu-niet-meer-in-72rc/page-5#entry1114216<br />
<br />
<br />
'''So as explained above, if the protocol version that the box uses differ from the server side, then no connection is possible without additional actions.'''<br />
----<br />
If you have a server that does not support SMBv2, you can force a connection to SMBv1 on the box by adding vers=1.0 to the mount options<br />
If you have a server that does not support NTLMssp, you can change it by adding sec=ntlmv2 or sec=ntlm to the mount options on the box<br />
<br />
What works is a matter of trying, you may even need both. See below is an example on connecting to a Synology that "still" uses Samba version 1 and security NTLM:<br />
<br />
<br />
<br />
[[File:Problems_and_Solutions-005.jpg|frameless|centre|750px]]<br />
[[File:Problems_and_Solutions-006.jpg|frameless|centre|750px]]<br />
<br />
=='''Multiboot crash - Boot loop '''==<br />
<br />
If you make use of multiboot and somehow get stuck at boot, by let's say a GSOD (Green Screen of Death) you can try to login your box/receiver with telnet and try the following:<br />
<br />
mkdir /tmp/t<br />
mount /dev/mmcblk0p3 /tmp/t<br />
cd /tmp/t<br />
<br />
Because the '''Edision OS mio ...''' uses mmcblk1... this throws an error and you can try this:<br />
<br />
mount /dev/mmcblk1p3 /tmp/t<br />
cd /tmp/t<br />
<br />
You should then see in this directory several startup files. If you eg want to start image in slot 1 do<br />
<br />
cp STARTUP_1 STARTUP<br />
<br />
If you want to start image in slot 2 then<br />
<br />
cp STARTUP_2 STARTUP<br />
<br />
And so on, then reboot the box.<br />
<br />
'''On the AB PULSe 4K:<br />
''' - turn it off with the back power switch.<br />
- Point the RCU to it and press the power button of the RCU (keep it pressed).<br />
- turn on the back power switch (while still pressing the RCU power button don't release it).<br />
- When the boot selection screen is displayed release the RCU power button and select the slot you want to boot to.<br />
<br />
If you want to flash from the Bootmenu insert the USB stick with the .zip image file on the back USB slot (it doesn't work on the front one!).<br />
<br />
Remark this doesn't work with the front panel power button you really need to use the RCU.<br />
<br />
'''EXAMPLE: On the HD51 use the following commands to start with bootslot 2:<br />
'''mkdir /tmp/t<br />
mount /dev/mmcblk0p1 /tmp/t<br />
cd /tmp/t<br />
cp STARTUP_BOOTSLOT_1_MODE_1 STARTUP<br />
reboot<br />
<br />
=='''Reset lost password'''==<br />
In case you have lost your box password or someone else has been so 'funny' to create a password without having informed you, there are several ways to solve this issue.<br />
<br />
<br />
===Install the "setpasswd" plugin===<br />
Easiest way is to install a plugin and reset or delete your password. Goto Main menu -> Plugin browser and press the green button "download plugins" goto systemplugins and goto setpasswd and press ok on your remote to install it. After you installed goto Main menu -> Setup -> System -> Change Root Password and press the red button to delete it.<br />
<br />
===Using the command line method 1===<br />
I assume that you still have access via Explorer with \\boxname or \\ipaddressbox. If not, then the only 'solution' to get access again is to flash your box which is actually not a solution. <br />
# Go to the map /etc where you find the file shadow. <br />
# If you owe another Enigma2 box then go to the map \etc and copy there that file 'shadow'. <br />
# Go to the box with the unknown password and paste the just copied file from the other box over your present version of shadow. <br />
<br />
<br />
===Using the command line: method 2 ===<br />
There is a second scenario to solve this.<br />
# Go to the map /etc where you also find the file passwd.<br />
# Select and edit the file passwd with right mouse button and select a proper editer. I use Notepad ++<br />
# In this file the line: root: x: 0: 0: root: / root: / bin / sh or something as root: EIfidfjeSAEFKEOlasdf5ewr3rWEW: 0: 0: root: / root: / bin / sh is the actual PW. The Password field is x or the encrypted string EIfidfjeSAEFKEOlasdf5ewr3rWEW<br />
# Delete the x or the string The line is now following: root :: 0: 0: root: / root: / bin / sh<br />
# Save / overwrite this file and exit Notepad ++.<br />
<br />
<br />
=='''Satellites.xml returning-over-and-over'''==<br />
The default satellites.xml is in the image, and is under version control. So it will be overwritten everytime you do an update.<br />
<br />
This is the standard situation:<br />
-rw-r--r-- 1 root root 531573 Jun 6 02:01 /etc/tuxbox/satellites.xml <br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /etc/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/satellites.xml -> /etc/tuxbox/satellites.xml<br />
lrwxrwxrwx 1 root root 26 Jun 9 19:28 /usr/share/tuxbox/satellites.xml -> /etc/tuxbox/satellites.xml<br />
<br />
You see that /etc/tuxbox is the file that is provided by the image and is versioned, the others are not present by default, and are symlinked to the versioned file.<br />
<br />
If you have a custom file, you should place it in /etc/enigma2, and it will take precedence over the system file in /etc/tuxbox. If you don't, and overwrite the system file, it will be removed and overwritten with a new system the next time you run an update.<br />
<br />
<br />
=='''<N/A> in a bouquet list'''==<br />
When you have a <N/A> in your channel (bouquet) list there is a mismatch between 2 files <br />
lamedb <br />
and <br />
satellites.xml. <br />
You can not solve this by a scan or downloding a settings list, because when you scan (which happens on the basis of the satellites.xml) the lamedb is updated with the wrong service refs. This way the entry that is in the bouquet file can no longer be found in the lamedb and thus yields an <N/A>.<br />
<br />
What you will need to do is remove the file <br />
satellites.xml<br />
<br />
which normally is located in <br />
<br />
/etc/tuxbox/satellites.xml<br />
<br />
and delete it. Then install a new one.<br />
<br />
opkg update<br />
opkg install tuxbox-common --force-reinstall<br />
<br />
<br />
=='''Splash screen replacement'''==<br />
The splashscreen is written in a limited reserved space of flash. We believe that the splash screen is not intended to be image specific, it should just show the manufacturer and/or box type information. The dimensions and type of splash file supported by the bootloader, differ per brand, and possibly even per box.<br />
We advice to stay away from that, leave the splash screen to the bootloader, and the manufacturer. <br />
<br />
If by some reason, let's say another image, has changed it, you can restore it to the one from the manufacturer. Do a search on the OpenPLi site using Google and type:<br />
<br />
splash screen site:openpli.org<br />
<br />
===For the Edision jump to [[Problems_and_Solutions#Edision_related | <span style="color:SteelBlue">Restore Splash screen for Edision</span>]]===<br />
<br />
===For the Vu<sup>+</sup> jump to [[Problems_and_Solutions#Restore_Splash_screen_for_Factory_bootlogo | <span style="color:SteelBlue">Restore Splash screen for Vu</span>]]===<br />
<br />
===For the Zgemma jump to [[Problems_and_Solutions#Zgemma_related | <span style="color:SteelBlue">Restore Splash screen for Zgemma</span>]]===<br />
<br />
<br />
=='''Time, if you have problems getting the correct time'''==<br />
<br />
<br />
<br />
<br />
[[File:Problems and Solutions-007.jpg|frameless|centre|750px]]<br />
<br />
<br />
<br />
<u>'''Please note</u>''': As of OpenPLi 8.1 systemtime is integrated in OpenPLi and by default enabled, so you don't have to install it separately (as suggested below) anymore. If for some reason you want to change the settings goto '''Menu -> Setup -> System -> Customize''' (scroll way down to the bottom). You can choose between Auto - Transponder Time (satellite) Internet.<br />
----<br />
<br />
Method for OpenPLi 8.0 and below:<br />
<br />
There are 2 solutions, if somehow you don't have the right time on you receiver, using the internet or use the transponder of a satellite.<br />
<br />
===Internet===<br />
Here you install a plugin called Systemtime, it is in '''Main menu > Pluginbrowser > Download plugins > Systemplugins''' and uses NTP, just like your desktop PC, to get the time from an internet time server, so after installing it, it will be in '''Main menu > Setup > Sytem''' and there are various settings.<br />
<br />
===Satellite===<br />
OpenPLi will, at startup retrieve the time from a transponder, so if you have a satellite setup, it is wise to make use of the [https://wiki.openpli.org/index.php/Hidden_functions#Startup_Service<span style="color:SteelBlue">Startup service</span>]. By doing so and choosing a reliable transponder (=channel) you will always have the right time. For the Dutch, choosing an NPO channel will be a good choice.<br />
<br />
=='''Unsupported receiver! How to request OpenPLi team to support a new receiver brand or model?'''==<br />
When your receiver is not supported by OpenPLi and you want it to be supported, what now? So before we can support any type of receiver, there have to be a few requirements met:<br />
<br />
#'''It must be an opensource receiver.''' - So not closed source.<br />
#'''It must be an Enigma2 receiver.''' - As we only support OpenEmbedded ([https://wiki.yoctoproject.org/wiki/Releases<span style="color:SteelBlue">Yocto project</span>]) boxes running Enigma2. This is essential of course as Enigma2 is the operating system that OpenPLi runs on.<br />
#'''The manufacturer/vendor has to ask us, so not the other way around!''' - As in the manufacturer/vendor has to mail OpenPLi to request support for this type/brand of receiver. <br />
#'''The manufacturer/vendor has to provide us (as in the OpenPLi team) with a functioning BSP layer.''' - A BSP ('''B'''oard '''S'''upport '''P'''ackage) contains, among other things, the drivers needed to build OpenPLi for your receiver. <br />
#'''We need interaction with the development team of the manufacturer/vendor.''' - The manufacturer needs to create the BSP and we need to be able to report and get driver bugs fixed, which is the reason we '''NEVER''' accept requests from end-users, we '''ONLY''' accept support requests from the manufacturer/vendor!<br />
<br />
=='''USB memory sticks working or not'''==<br />
When you want to use an USB memory stick, lets say for flashing your box with OpenPLi, there is no way of telling your stick might work, it's trial and error! Because the USB detection system in the bootloader of your receiver is very simple, there are 2 things to consider:<br />
<br />
#It has a short device detection time, which is as it should be, because a long device detection time could result in an annoying long booting procedure. This (short device detection) causes devices whose detection takes (too) long (usb3 devices, large sticks) not to be seen in time.<br />
#It takes the first device that is found and if you've connected multiple devices, chances are that it's not the device you want to use.<br />
<br />
Generally speaking, small old USB sticks with less than 1Gb have a bigger change to work.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=How_to_Flash_your_receiver&diff=13345How to Flash your receiver2019-06-08T13:35:28Z<p>Rick Hunter: </p>
<hr />
<div>* [https://openpli.org/download<span style="color:SteelBlue">Settop Boxes that are supported</span>]<br />
Follow this link if you want to know if you can flash a receiver/Setop Box with OpenPLi.<br />
<br />
* [[Receivers:Settopbox_Comparison| <span style="color:SteelBlue">Settop Box Comparison</span>]] <br /><br />
Here is a table where Settop boxes are compared, right down to component level, nice when you want to buy one.<br />
<br />
* [[Receivers:Power_comparison| <span style="color:SteelBlue">Settop Box Power comparison</span>]]<br /><br />
<br /><br />
<br />
'''How flash'''<br />
----<br />
Below in alphabetic order links on how to flash a certain brand Settop Box (btw if it's not there yet, please feel free to add it).<br />
<br />
<br />
* '''[[Amiko| <span style="color:SteelBlue">Amiko</span>]]'''<br />
* '''[[Axas| <span style="color:SteelBlue">Axas</span>]]'''<br />
* '''[[Receivers:Dreambox| <span style="color:SteelBlue">Dreambox</span>]]'''<br />
* '''[[Receivers:Edision| <span style="color:SteelBlue">Edision</span>]]'''<br />
* '''[[Receivers:Formuler| <span style="color:SteelBlue">Formuler</span>]]'''<br />
* '''[[Receivers:Gi| <span style="color:SteelBlue">Gi</span>]]'''<br />
* '''[[Receivers:GigaBlue| <span style="color:SteelBlue">GigaBlue</span>]]'''<br />
* '''[[Receivers:Golden_Interstar| <span style="color:SteelBlue">Golden Interstar</span>]]<br />
* '''[[Receivers:Maxdigital| <span style="color:SteelBlue">Maxdigital</span>]]'''<br />
* '''[[Receivers:Maxytex| <span style="color:SteelBlue">Maxytec</span>]]'''<br />
* '''[[Receivers:Mircablebox| <span style="color:SteelBlue">Miraclebox</span>]]'''<br />
* '''[[Receivers:Mut@nt| <span style="color:SteelBlue">Mut@nt</span>]]'''<br />
* '''[[Qviart| <span style="color:SteelBlue">Qviart</span>]]'''<br />
* '''[[Receivers:SAB| <span style="color:SteelBlue">SAB</span>]]'''<br />
* '''[[Spycat| <span style="color:SteelBlue">Spycat</span>]]'''<br />
* '''[[Vimastec| <span style="color:SteelBlue">Vimastec</span>]]'''<br />
* '''[[Receivers:Vu| <span style="color:SteelBlue">Vu<sup>+</sup></span>]]'''<br />
* '''[[Xsarius| <span style="color:SteelBlue">Xsarius</span>]]'''<br />
* '''[[Media:Leaflet-XsariusFusionHDSE.pdf|Fusion HD SE]]'''<br />
* '''[[Wetek| <span style="color:SteelBlue">Wetek</span>]]'''<br />
* '''[[Receivers:Xtrend| <span style="color:SteelBlue">Xtrend</span>]]'''<br />
* '''[[Zgemma| <span style="color:SteelBlue">Zgemma</span>]]'''</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Receivers:Mut@nt&diff=13305Receivers:Mut@nt2019-05-26T12:20:51Z<p>Rick Hunter: </p>
<hr />
<div>[[File:RECEIVER-Mutant-001.jpg|frameless|right]]<br />
<br />
=='''How to flash the new HD 60 UHD receiver...'''<br />==<br />
<br />
Flashing the Receiver.<br />
# Power off the receiver<br />
# Insert the USB stick containing the image files into one of the USB ports on the receiver.<br />
# Push and hold the small button next to the TF card slot at the lift side of the box.<br />
# Power the receiver on.<br />
# After a short while the red power led at the front starts to blink. Now you can release the button.<br />
# If successful the receiver will reboot it self after the flashing process has completed.<br />
# During the setup process you will be requested to restore a previous backup in case you have made one on your USB stick. <br />
<br />
The flashing process should take approximately 1.5 minutes to complete, while the receiver is being flashed, it is important that you DO NOT power the receiver down for any reason as this can cause serious and or permanent damage.<br />
<br />
<br />
=='''How to flash the HD 51 receiver...'''<br />==<br />
<br />
Flashing the Receiver.<br />
# Power off the receiver<br />
# Ensure no other USB devices are plugged into the receiver while flashing.<br />
# Insert the USB stick containing the image files into one of the USB ports on the receiver, rear USB port is advised if possible.<br />
# Power the receiver on.<br />
# Immediately after powering on PRESS AND HOLD the front power button until ‘flashing..’ appears on front display. <br />
# If successful the receiver will reboot it self after the flashing process has completed.<br />
# Remove USB stick that contains the images files.<br />
<br />
The flashing process should take approximately two to four minutes to complete, while the receiver is being flashed, it is important that you DO NOT power the receiver down for any reason as this can cause serious and or permanent damage.<br />
<br />
<br />
=='''How to flash the other receivers...'''<br />==<br />
<br />
Download a image from: https://openpli.org<br />
Unpack the ZIP file and place the content on a USB disk.<br />
<br />
FLASHING THE RECEIVER. <br /><br />
# Unzip compressed file.<br /><br />
# Copy the folder to a USB Pen Drive.<br /><br />
# Power off or reboot the receiver with the mains switch on the rear. Connect USB Pen Drive.<br /><br />
# Power on receiver with the mains switch on the rear.<br /><br />
# After rebooting or cold start the power LED will blink several times after some time. At that moment press the power button on the front panel.<br /><br />
# Flashing of the image will start<br /><br />
# Booting will start automatically once the flashing process has completed<br /><br />
<br />
<u>Note:</u> In order to load the image automatically, rename the file called "noforce" to "force"<br />
<br />
<br />
<br />
'''Specific information for HD51''' new bootloader V1.07-r19.<br />
---- <br />
The file can be download at: http://downloads.mut...olt-v107r19.zip<br />
<br />
<br />
The easy way to check the bootloader version is by going to '''Menu > Information > About'''<br />
<br />
Alternative using the CLI to check the bootloader version you have... Enter the receiver with telnet, enter the following command:<br />
#:/cat /sys/firmware/devicetree/base/bolt/tag<br />
<br />
Notice: This update is imported if you make use of the boxmode function. (Boxmode 1 is default and boxmode 12 activate PiP)<br />
<br />
the update goes the same way as flashing a image. <br />
The HD51 folder on the USB disc must be clean before placing the content of the zip file on the USB disk.<br />
The zip file contains 2 files: '''hd51-bolt.bin''' and '''imageversion'''<br />
<br />
There are two ways to place the boot loader on your receiver:<br />
Option 1: Press the standby button for 15 seconds until BOLT appears on the display.<br />
Option 2: Start your receiver via the power plug and hold the standby button until BOLT appears on the display.<br />
<br />
The flash procedure will only take a few seconds and when Complete appears at the display, the receiver will restart.<br />
Warning: Do not unplug the receiver during the update process!<br />
<br />
Source: https://forums.openpli.org/topic/43945-hd51-bootloader-v107/<br />
<br />
<br />
'''Remark:''' When usesing the HD51 as a 4k receiver do not set the AV mode (Resolution of the screen) other than 50Hz. When the signal receives 60Hz the receiver disrupts the TV output. In most cases the display is black and a restart of the receiver is needed to regain TV functionality.<br />
<br />
<br />
'''Boxmode for HD51 how to...'''<br /><br />
----<br />
There are currently two box mode options for the HD51.<br />
* Mode 1 = 2 video encoder for main screen <br />
* Mode 12 = 2 video encoder for main screen + 1 video encoder for 2nd screen (PiP)<br />
<br />
To alter your receiver into a different box mode<br />
Goto folder: '''/media/mmc/STARTUP'''<br />
default:<br />
boot emmcflash0.kernel1 'root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1'<br />
if you alter '''hd51_4.boxmode=1''' into 12, your receiver is switching to boxmode 12 when you restart your receiver.<br />
so:<br />
boot emmcflash0.kernel1 'root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=12'<br />
<br />
'''Must I switch from mode?'''<br />
The answer is no. If you switching into box mode 12, the energy consumption will increase.<br /><br />
<br />
Source: https://forums.openpli.org/topic/43945-hd51-bootloader-v107/<br />
<br />
<br />
<br />
'''Specific information for HD2400'''<br />
----<br />
Bootloader V36 (Available since may 2015), supports images up to 500MB, support multi boot by kexec, support systemd images, support images startup from USB, SSD, HDD and SDcard.<br />
<br />
Before you install the new bootloader, please been certain there is no map called /hd2400 on your USB stick.It can happen that the bootloader will not install when a splash or force file is in the /hd2400 map.<br />
<br />
Follow the next steps to successful update the bootloader.<br />
<br />
# Remove the map /hd2400 when it's already on your USB stick. <br />
# Unzip the file to an USB stick. (You will see a map called /hd2400 with 2 files image version and hd2400-cfe.bin)<br />
# Place the USB stick in an USB socket of the HD2400.<br />
# Start the box with the power switch at the back of the box.<br />
# The display will show a message, to load the new bootloader you will need to press the second button which has a down arrowhead (V) symbol.<br />
# The display will show flashing for about 10 seconds and after this the HD2400 will reboot automatically.<br />
<br />
----</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Plugin_Wiki:USTVNow&diff=10142Plugin Wiki:USTVNow2018-10-28T22:35:28Z<p>Rick Hunter: </p>
<hr />
<div><u>'''How to install:'''</u><br /><br />
[[File:USTVNow.gif|right]]<br />
<br />
'''1.''' First place the content of the ustvnow.zip file to folder: '''/usr/lib/enigma2/python/Plugins/Extensions/Ustvnow/'''<br /><br />
'''2.''' Install the plugin: ServiceApp <br /><br />
'''3.''' Adjust the ServiceApp settings to:- Enigma2 playback system: '''serviceapp'''<br /><br />
- Enigma2 playback system: '''serviceapp'''<br /><br />
- Player: '''exteplayer3'''<br /><br />
- HLS Explorer must be set on '''true'''<br /><br />
'''4.''' Restart enigma2<br /><br />
<br />
'''5.''' Go to the website: www.ustvnow.com and make a new account. Use the free ($0.00) version to watch the free to view channels.<br /><br />
'''6.''' Verify / confirm the e-mail from USTVNow to activate your account.<br /><br />
'''7.''' Use the plugin: \Menu\Plugins\USTVnow\ and enter your e-mail address and password. <br /><br />
'''8.''' Use green to save the settings.. and/or OK to create a bouquet.<br /><br />
<u>'''Note:'''</u> Due to a bug in the python code, changing the quality will not improve the quality. SD is the standard.<br />
<br />
'''9.''' A few seconds are needed to create a new Bouquet USTVNow with 5 US-TV Channels:<br /><br />
<big>ABC, CBS, CW, My9, PBS</big><br /><br />
<br />
<u>'''Note:'''</u> To watch the TV Channels, once a day at 11.00 CET the URL's are changed, so then you need to reload the Channel's with the usage of the plugin. If you select the channels and see no image, use step 7,8 and 9 again.<br />
<u>'''Note:'''</u> The free account is active for 45 day's to watch the channels in HD and via streaming option. After 45 day's, you only can watch the channels at the website: www.ustvnow.com.. But.. I created a new account.. and continue to watch the channels.. -> You need a new e-mail address of course.<br />
<br />
'''The Plugin can be found at''': Menu, Applications, Green, Extensions</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Plugin_Wiki:USTVNow&diff=10138Plugin Wiki:USTVNow2018-10-28T21:16:44Z<p>Rick Hunter: </p>
<hr />
<div><u>'''How to install:'''</u><br /><br />
[[File:USTVNow.gif|right]]<br />
<br />
'''1.''' First place the content of the ustvnow.zip file to folder: '''/usr/lib/enigma2/python/Plugins/Extensions/Ustvnow/'''<br /><br />
'''2.''' Install the plugin: ServiceApp <br /><br />
'''3.''' Adjust the ServiceApp settings to:- Enigma2 playback system: '''serviceapp'''<br /><br />
- Enigma2 playback system: '''serviceapp'''<br /><br />
- Player: '''exteplayer3'''<br /><br />
- HLS Explorer must be set on '''true'''<br /><br />
'''4.''' Restart enigma2<br /><br />
<br />
'''5.''' Go to the website: www.ustvnow.com and make a new account. Use the free ($0.00) version to watch the free to view channels.<br /><br />
'''6.''' Verify / confirm the e-mail from USTVNow to activate your account.<br /><br />
'''7.''' Use the plugin: \Menu\Plugins\USTVnow\ and enter your e-mail address and password. <br /><br />
'''8.''' Use green to save the settings.. and/or OK to create a bouquet.<br /><br />
<u>'''Note:'''</u> Due to a bug in the python code, changing the quality will not improve the quality. SD is the standard.<br />
<br />
'''9.''' A few seconds are needed to create a new Bouquet USTVNow with 5 US-TV Channels:<br /><br />
<big>ABC, CBS, CW, My9, PBS</big><br /><br />
<br />
<u>'''Note:'''</u> To watch the TV Channels, once a day at 11.00 CET the URL's are changed, so then you need to reload the Channel's with the usage of the plugin. If you select the channels and see no image, use step 7,8 and 9 again.<br />
<u>'''Note:'''</u> The free account is active for 45 day's to watch the channels in HD and via streaming option. After 45 day's, you only can watch the channels at the website: www.ustvnow.com.. But.. I created a new account.. and continue to watch the channels.. -> You need a new e-mail address of course.<br />
<br />
'''The Plugin can be found at''': https://forums.openpli.org/topic/52252-ustvnow-plugin/#entry741181</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Tips_and_Tweaks&diff=10106Tips and Tweaks2018-10-24T08:24:20Z<p>Rick Hunter: /* Settings file in OpenPLi */</p>
<hr />
<div>=='''Accessing your receiver and editing files'''==<br />
You can change many settings using the Graphical User Interface (GUI), but in some cases it can be necessary to access the files manually. You can do this by downloading and using [http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html <span style="color:SteelBlue">Putty</span>]. By default you can login with telnet, so if you use puttytel.exe (a Telnet-only client) and login your box. By default there is no password for the root, so login with "''root''" and so you should not have to enter a password.<br />
<br />
<br />
===Telnet usage===<br />
By default the enigma receiver does not have a password. To access the receiver via de command line, use a program like [http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html <span style="color:SteelBlue">Putty</span>], or use the command 'Telnet' from the commandline.<br />
<br />
telnet <ip address receiver><br /><br />
telnet 192.168.65.247<br />
Trying 192.168.65.247...<br />
Connected to 192.168.65.247.<br />
Escape character is '^]]'.<br />
Username: root<br />
Password: no password, leave blank<br />
<br />
===Telnet with Mac OS High Sierra===<br />
With the arrival of Mac OS High Sierra, the Telnet command has been removed. You need to use network connect (nc) instead of telnet the syntax to use is:<br />
nc ip_of_box 23<br />
(where 23 is the port used for the telnet service).<br />
<br />
Anyway if you want to restore the telnet command, see [https://apple.stackexchange.com/questions/299758/how-to-get-bsd-ftp-and-telnet-back-in-10-13-high-sierra/312273#312273 this post on StackOverflow].<br />
<br />
''Note that you only need to install telnet, not the other tools mentioned in the post!''<br />
<br />
===How to use SSH instead of Telnet===<br />
SSH runs on OpenPLI by default.... But, to use SSH you need to set a password first. <br />
<br />
First Login with telnet. (See above)<br /><br />
Then change the password with the command 'passwd'.<br />
root@et7x00:~# passwd<br />
Changing password for root<br />
Enter the new password (minimum of 5 characters)<br />
Please use a combination of upper and lower case letters and numbers.<br />
New password: <br />
Re-enter new password: <br />
passwd: password changed.<br />
<br />
Then close the telnet session<br />
root@et7x00:~# exit<br />
Connection closed by foreign host.<br />
<br />
Ok, now the box is ready to be accessed by ssh:<br />
<br />
ssh root@192.168.65.247<br />
Warning: Permanently added 'p247,192.168.65.247' (RSA) to the list of known hosts.<br />
root@p247's password: <br />
root@et7x00:~# <br />
<br />
Remark: When you connect for the first time with ssh, you'll get a fingerprint notification. You can accept this by typing 'yes'<br />
<br />
RSA key fingerprint is SHA256:x2iV/az3N6IVgWYEpAw4mDE5ahaRX2hEDb7xxEgaVO9.<br />
Are you sure you want to continue connecting (yes/no)? yes<br />
<br />
<br />
===I forgot my password===<br />
If you forgot your password or used an extension for changing it with OpenPLi you can clear the password by editing the first line in /etc/shadow which contains the hash of your password.<br />
Just delete the second parameter.<br /><br />
<br />
example:<br />
root:.3nwZcSK66fbg:15617:0:99999:7::: \\with password:<br /><br />
root::15617:0:99999:7::: \\without password:<br />
<br />
===How to create a log file of your Putty session===<br />
If you want to record what is happening during your Putty session here is how you can let Putty [[Tips:Session_Record_Putty | <span style="color:SteelBlue">Record</span>]] it.<br />
<br />
===Install an IPK file===<br />
<br />
When you come across a plugin that you want to install in OpenPLi, you can do this with one of the following 2 methods:<br />
<br />
====Using the graphical user interface====<br />
[[File:Install-an-IPK-file-001.gif|right|480px]]<br />
* Copy your IPK file to a removable medium like an USB stick. <br />
* Then in OpenPLi goto the Main Menu -> Plugins -> Software management -> Install local extension <br />
* Then select your media <br />
* Select 1 Install extensions, select the IPK file and press the green button <br />
* Now your IPK will be installed and if everything is nicely coded there should be no error messages<br />
* Reboot your box and if all is well then under Plugins your program should be there.<br />
<br />
<br />
====Using the command line interface====<br />
copy your IPK file onto your box to the folder /tmp<br />
<br />
- login your box with Telnet (Putty) and enter the following commands at the command line:<br />
<br />
cd /tmp<br />
<br />
opkg install pluginname.ipk<br />
<br />
'''Note:''' if you'll reboot the IPK will be removed from the /tmp folder as it is a temporary folder!!<br />
<br />
<br />
=='''Adding IP Camera's to your channellist'''==<br />
It is possible to watch your IP Camera on TV. Here you can find the [[Tips:Add_your_IP-Camera | <span style="color:SteelBlue">necessary</span>]] information.<br />
<br />
<br />
=='''Bootlogo location'''==<br />
When you want to change the bootlogo for some reason. You can find it in the location<br />
/usr/share <br />
the file your are looking for is<br />
bootlogo.mvi<br />
<br />
<br />
=='''Crash logs'''==<br />
Crash logs are generated during a system crash, also known as a GSOD (green screen of death). The log can give insight to the probable cause of the crash. If you want help with the content of the file, you can post it on our [https://forums.openpli.org <span style="color:SteelBlue">forum</span>]. The crash log file is named like in the example below:<br />
<br />
enigma2_crash_3891289128.log<br />
<br />
===The location of the crash log file when there is a HDD (Harddisk) present===<br />
Normally the crash.log file is stored in the root of the HDD so in<br />
/media/hdd<br />
<br />
===The location of the crash.log file without any HDD (Harddisk) present===<br />
Normally the crash log file is stored in the <br />
/home/root<br />
<br />
<br />
=='''Do or don't - placing a Solid Sate Disk SSD in your satellite receiver'''==<br />
Placing a Solid State Drive (SSD) in a (satellite) receiver is a topic that is regularly discussed on this forum. SSD’s make (desktop and labtop) computers spectacularly faster, so it is not surprising anyone wanting to replace a Hard Disk drive (HDD) or install an SSD in a receiver. However, it is a bad idea, because there are no advantages of an SSD in a receiver.<br />
<br />
On a desktop computer, especially when starting up the device, many small files are read. A reading pattern is created in which data from random locations on the disk can be read. A 7200 rpm drive (HDD) can change location approximately 83 times per second, this has to do with the (reading) head's travel time and the time waiting as it circulates for all the data to pass the head. <br />
<br />
An SSD can change places tens of thousands of times per second and this is where the spectacular speed difference compared to a HDD comes from. Although a HDD performs much better when it reads large files (the data is then contiguous and the HDD can then reach speeds above 200MB/s), an SSD is still faster as it achieves speeds up and over 500MB/s.<br />
<br />
Recordings of television broadcasts are large, contiguous files. The bitrates for broadcasts are roughly between 1.5 and 25 Mb/s, which translates into speeds of about 175KB/s to 3125KB/s. The read/write pattern therefore corresponds well to what hard drives are good at and the speeds that are needed are far below what a hard drive can deliver. So even when you do a lot of recordings at the same time, you will not quickly reach the limit of the hard drive. That is why the difference in speed that you experience when you use an SSD is practically zero. Some users note, that if they copy files over the network, the speeds are lower than expected (for example 70MB/s) and they think that the hard disk is the cause. This is unjustified, the hard drive is not the bottle neck. The bottle neck is located elsewhere in the receiver. The cause are the network controller and the disk controller, which are not as powerful as the equivalents in desktop and labtop computers. This has to do with the relatively low speeds that are required, because there is no added value for the manufacturers of the relevant chips to build fastest controllers. Energy consumption and price of the chip are factors that play an important role here.<br />
<br />
The energy consumption of an SSD is lower than that of a HDD. So energy consumption and the associated heat production is, of course, an argument. However, a HDD in an OpenPLi supported receiver doesn’t run continuously, but is only activated when necessary, so the energy consumption is already very low, especially HDD’s intended for laptops often consume scarcely more than an SSD. So this benefit can also be questioned.<br />
<br />
So we can conclude that an SSD is not ideal, but what do you have to put in your receiver? The best choice is a traditional HDD with a speed of 5400 rpm. This gives you a lot of capacity/euro and is a lot faster than necessary. The use of 5400 rpm ensures low energy consumption and these discs are generally completely inaudible due to the low speeds. A 3.5-inch copy is usually fine, 2.5-inch for laptops are even more economical, but offer less capacity. If energy use or heat is really very critical, take a 2.5-inch and some receivers only have space for 2.5 inches.<br />
<br />
<br />
=='''ECM info'''==<br />
[[File:ECM-Info.gif|right|480px]]<br />
If you want to see how the current channel is encrypted, you can look this up with ECM Info. <br />
The white lines tels you what kind of encryptions are being used and the yellow line tells you with type of encryption is used to decrypt the channel.<br />
lems with the stability of your WiFi connection) to make use of a wireless bridge.<br />
<br />
<br />
=='''Edit files on a Linux system'''==<br />
When you want to edit files on a Linux distro (distribution) like Enigma2 (OpenPLi) it's best to use the native editors like Vi, VIM or Nano. For Windows users that don't want to use telnet, but want to edit files it is not advisable to use the default Windows editors, like WordPad or NotePad. What you can you use instead is Notepad++ , it's a free source editor and you can download it at [https://notepad-plus-plus.org/<span style="color:SteelBlue">Notepad++</span>]<br />
<br />
If you want to use Nano at your receiver you can install nano with the command:<br />
<br />
opkg update && opkg install nano<br />
<br />
<br />
=='''Having your receiver always using the correct time'''==<br />
Having the correct time is essential for many processes in your receiver, albeit only for your time scheduled recordings. There are 2 ways to ensure that the box has the correct time right at start-up:<br />
#Setting up a startup transmitter on a transponder with the right time, any Astra transponder will do, so like BBC1 HD or NPO1 HD. Take a look at [[Hidden_functions#Startup_Service | <span style="color:SteelBlue">Startup service</span>]] for the details and how to set it up.<br />
#Install the system-time plugin and setting it to retrieve the time from on-line (Internet) service, during booting (startup) of your box. Check out the [[Plugin_Wiki:Information | <span style="color:SteelBlue">Plugin section</span>]] of the Wiki, to download it on your box, goto '''Systemplugins'''.<br />
<br />
Note: If your box has an Internet connection, option 2 is the most stable one.<br />
<br />
<br />
=='''HDD and temperature'''==<br />
If for some reason you are interested in the temperature of your harddisk, then you can install a plugin using telnet, it must be done manually.<br />
<br />
opkg install hddtemp<br />
<br />
and then use:<br />
<br />
hddtemp /dev/sdX ... X is a, b, c ...<br />
<br />
<br />
=='''Mediaplayer (gstreamer) and subtitles'''==<br />
OpenPLi's media player ''gstreamer'' can play many external content, like MKV, MP4, etc. If you want to add a subtitle to these containers (MKV, MP4, etc) it is best to mux them. Muxing is the process of combining these video, audio and subtitle components into the container file, so that it can be read/played back. Take a look at<br />
[[GStreamer | <span style="color:SteelBlue">GStreamer</span>]]<br />
<br />
<br />
=='''Menu Levels'''==<br />
[[File:MENU-Levels.gif|right|480px]]<br />
The enigma receiver has a lot of options in the menu. Some are easy to understand, and some are not so common used. So we reworked the menu's Setup\System section. <br /><br />
The main goal is that simple, advanced and expert settings are properly separated. At the Customize option you can enter Normal, Advanced or Expert. This will result in less or more options in the Customize option and also on the User interface, Audio / Video and Expert settings menu's.<br />
<br />
<br />
=='''Recording with a Zapper (eg. Vu Zero / Vu Solo Se)'''==<br />
By default some Vu<sup>+</sup> boxes are a ''zapper'', meaning you can not record with it. If you want to record with it, you can install the "pau" plugin/extension. It is located in the <br />
''extensions'' section of the [[Plugin_Wiki| <span style="color:SteelBlue">plugin browser</span>]].<br />
<br />
<br />
=='''Samba in OpenPLi'''==<br />
By default Samba is working, meaning the daemon/service is run at startup and should make all media accessible from any external device. There are no passwords or login required, guest access is on. As the Samba package is kept small there is no easy way to create passwords for users.<br />
<br />
When you want to access you box media (HDD, Root or external media) there are a few ways to do it:<br />
<br />
<br />
=='''Screenshot'''==<br />
If you want to take a screenshot, let's say to show a certain result to someone, you can make a screenshot of the current state of the screen on your TV using [[Webif | <span style="color:SteelBlue">Webif</span>]]. When in Webif on the left of the screen you open ''remote control'' and click on ''Make screenshot''.<br />
<br />
You can also generate a screenshot from command line, connect in telnet and type:<br />
<br />
this example will generate: screenshot.bmp<br />
<br />
cd /tmp<br />
grab<br />
<br />
or this example will generate: screenshot.jpg<br />
<br />
cd /tmp<br />
grab -j<br />
<br />
Then use your favorite ftp client to retrieve the generated screenshot file.<br />
<br />
Another option is possible -p to generate a .png file.<br />
Yo get all possible options use:<br />
<br />
grab -h<br />
<br />
<br />
=='''Searching the forum is not perfect'''==<br />
The search function on the OpenPLi forum is not perfect. In stead you could use Google and use the following: <br />
here you type the keywords what you are looking for '''site:openpli.org'''<br />
Using the above on Google and you search the OpenPLi site for the keywords you have entered, so good luck!<br />
<br />
<br />
=='''Accessing the receiver using a (internet)browser'''==<br />
When you want to access your receiver using your favorite Internet browser, Firefox, Chrome, Microsoft Edge, Opera or whatever: <br />
<br />
===Windows===<br />
*Click Start button - Click Run and enter:<br />
<br />
\\ipaddress-of-your-box\<br />
<br />
*Open your browser (FF, IE or ME) and enter the following:<br />
<br />
file://///ipaddress-of-your-box/root<br />
file://///ipaddress-of-your-box/Harddisk <br />
file://///ipaddress-of-your-box/Media<br />
<br />
===Linux===<br />
*In your browser (FF, Iceweasel) enter the following:<br />
<br />
smb://ipaddress-of-your-box<br />
<br />
===Mac===<br />
* In Finder, select your receiver name at the left side. The common name is your receiver type, like et1000, HD2400<br />
<br />
<br />
If you want to edit the samba config file at your receiver it is located at:<br />
<br />
/etc/samba/smb.conf<br />
<br />
'''Note:''' OpenPLi 6.x uses Samba version 4 and the syntax is very different from the version used in OpenPLi 4<br />
<br />
<br />
=='''Settings file in OpenPLi'''==<br />
Many things that you change from the default settings in OpenPLi are stored in the file ''/etc/enigma2/settings'', Bouquets files for radio and TV and enigma settings can be found at this location.<br />
If you want to edit/copy/backup this file, it is best to stop source and destination, by doing the following:<br />
<br />
root@<receiver>: init 4<br />
<br />
This stops Enigma2 (operating system) gracefully, waiting for all it's components to stop and places Enigma2 into a "sleep" mode allowing you to edit or modify files that otherwise would corrupt or become damaged, if edited while running.<br />
<br />
<br />
now go to ''/etc/enigma2'' and edit/copy/backup the file named ''settings'', when done do:<br />
<br />
root@<receiver>: init 3<br />
<br />
This wakes enigma from the "sleeping" state and restarts the GUI (Graphical User Interface).<br />
<br />
<br />
BTW 1 if you want to edit this file and not use Vi (native editor of Unix/Linux) but use a Windows editor, we can advise [[Tips_and_Tweaks#Edit_files_on_a_Linux_system | <span style="color:SteelBlue">Notepad++</span>]]<br />
<br />
BTW 2 if you need to edit file in telnet but don't know very well vi you can install nano (opkg update && opkg install nano) this is a more user friendly editor. Simply type: nano filename<br />
<br />
BTW 3 Don't use "killall 9 enigma2" this will cause a sudden stop all enigma2 services without waiting to close anything and leave all opened files in an uncertain state!<br />
<br />
=='''Shell'''==<br />
By default OpenPLi has a stripped-down version of busybox. If you want more, you could install the "Bash" shell by entering:<br />
<br />
opkg update && opkg install bash<br />
<br />
<br />
=='''Skip time'''==<br />
Skip time in a recording works much faster than using the forward or rewind keys on your remote. You can customize the Skip time keys on your remote in '''Menu > Setup > System > Expert Settings> Record''' and adjust the settings for '1'/'3' - '4'/'6' -'7'/'9' buttons''.<br />
[[File:Tips and Tricks-001.jpg|frameles|left|300px]]<br />
[[File:Tips and Tricks-002.jpg|frameles|right|300px]]<br />
<br />
Default: <br /><br />
* 1 = -15 seconds back in the recording<br />
* 3 = +15 seconds forward in the recording<br />
* 4 = -1 minute<br />
* 6 = +1 minute<br />
* 7 = - 5 minutes<br />
* 9 = + 5 minutes<br />
<br />
<br />
=='''Wireless Bridge'''==<br />
If you want to use WiFi with your box, there are many solutions, like dongles, WiFi USB adapter, powerline adapters, etc. In general we recommend (but certainly if you have problems with the stability of your WiFi connection) to make use of a wireless bridge.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Up-Download_magazine&diff=10070Up-Download magazine2018-10-22T09:00:14Z<p>Rick Hunter: </p>
<hr />
<div>UP/DOWNLINK’ is voor iedere satliefhebber. Een streepje voor hebben leden van De Transponder (deze krijgen het per e-mail). Anderen kunnen het iets later downloaden en lezen via de site van De Transponder.<br />
De naam ‘UP/DOWNLINK’ staat niet alleen voor de satellietterm (up naar de satelliet en down naar de schotel) maar ook voor alle informatie die wij verzamelen (up) te verspreiden naar geïnteresseerden (down). Wij hopen dat er veel bijdragen van jullie komen; hoe meer ‘ups’ des te beter!<br /><br />
De nieuwsbrief UP/DOWNLINK verschijnt een keer per maand.<br />
[[File:TRANSPONDER-UpDownload-001.jpg|frame|right]]<br />
Je mail is zeer welkom via '''specials@detransponder.nl'''<br />
<br />
<u>UP/DOWNLINK</u><br />
<br />
[https://www.detransponder.nl/wp-content/uploads/2018/10/Index-onderwerpen-van-alle-uitgebrachte-UP_DOWNLINKs.pdf <span style="color:SteelBlue">Index onderwerpen van alle uitgebrachte UP-DOWNLINKs</span>]<br />
<br />
De UP/DOWNLINKS magazines zijn [http://www.detransponder.nl/wordpress/downloads/nieuwsbrieven/ <span style="color:SteelBlue">hier</span>] te downloaden.<br /><br />
De daarin genoemde specials zijn [http://www.detransponder.nl/wordpress/downloads/specials/ <span style="color:SteelBlue">hier</span>] te downloaden.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9955Dvb-fe-tool2018-09-22T22:42:27Z<p>Rick Hunter: </p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. Use the command:'''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: Monitoring<br /><br />
-f: Get the Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.<br /><br />
A good satellite signal gives the following result:<br /><br />
Lock (0x1f) Signal= 18.93% C/N= 13.97dB<br />
Layer A: C/N= 71.00%</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9951Dvb-fe-tool2018-09-22T22:42:06Z<p>Rick Hunter: </p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. Use the command:'''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: monitoring<br /><br />
-f: Get the Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.<br /><br />
A good satellite signal gives the following result:<br /><br />
Lock (0x1f) Signal= 18.93% C/N= 13.97dB<br />
Layer A: C/N= 71.00%</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9947Dvb-fe-tool2018-09-22T22:24:13Z<p>Rick Hunter: </p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. '''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: monitoring<br /><br />
-f: Get the Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.<br /><br />
A good satellite signal gives the following result:<br /><br />
Lock (0x1f) Signal= 18.93% C/N= 13.97dB<br />
Layer A: C/N= 71.00%</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9943Dvb-fe-tool2018-09-22T22:23:35Z<p>Rick Hunter: </p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. '''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: monitoring<br /><br />
-f: Get the Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br /><br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.<br /><br />
A good satellite signal gives the following result:<br /><br />
Lock (0x1f) Signal= 18.93% C/N= 13.97dB<br /><br />
Layer A: C/N= 71.00%<br /></div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9939Dvb-fe-tool2018-09-22T22:20:39Z<p>Rick Hunter: </p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. '''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: monitoring<br /><br />
-f: Get the Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br /><br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Dvb-fe-tool&diff=9935Dvb-fe-tool2018-09-22T22:19:44Z<p>Rick Hunter: Created page with " When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included wit..."</p>
<hr />
<div><br />
When you want to look for the signal strength via the commandline use the tool: dvb-fe-tool. This tool is included with the v4l-util toolpack that isn't standard included within the image.<br />
<br />
Fist: '''v4l-utils''' needs to be installed ont he receiver. '''opkg install v4l-utils'''<br /><br />
Then used the command '''dvb-fe-tool'''. <br /><br />
The parameters that must be added:<br /><br />
-m: monitoring<br /><br />
-f: Gets Front-end parameters<br /><br />
value: 0 = tuner A, 1 = tuner B, 2 = tuner C, 3 = tuner D<br /><br />
<br />
Then I made a scan for tuner C (value in this case is then 2)<br /><br />
'''dvb-fe-tool -m -f 2''' <br />
<br />
With gave the results:<br />
<br />
'''root@hd2400:/# dvb-fe-tool -m -f 2<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%<br /><br />
Lock (0x1f) Signal= 0.39% C/N= 54.00%'''<br /><br />
<br />
To stop the monitoring Press '''CTRL-C'''<br />
<br />
In this case the signal strength is 54% with is good for a cable channel.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Knowledge_base&diff=9931Knowledge base2018-09-22T22:14:01Z<p>Rick Hunter: </p>
<hr />
<div>=='''OpenPLi - Knowledge base'''==<br />
===[[Abbreviations | <span style="color:SteelBlue">'''• Abbreviations'''</span>]]===<br />
===[[dvb_s_s2_c_t_Tuners | <span style="color:SteelBlue">'''• DVB-S/S2/C/T/S2X Tuners''' </span>]]=== <br />
===[[Extended CW API | <span style="color:SteelBlue">'''• Extended CW API'''</span>]]===<br />
===[[Full_Band_Capture | <span style="color:SteelBlue">'''• Full Band Capture Tuner (FBC)'''</span>]]===<br />
===[[GStreamer | <span style="color:SteelBlue">'''• GStreamer'''</span>]]===<br />
===[[HbbTV | <span style="color:SteelBlue">'''• HbbTV'''</span>]]===<br />
===[[Multistream | <span style="color:SteelBlue">'''• Multistream''' </span>]]=== <br />
===[[Offline_decoding | <span style="color:SteelBlue">'''• Offline decoding'''</span>]]===<br />
===[[Overscan | <span style="color:SteelBlue">'''• Overscan'''</span>]]=== <br />
===[[Ppanel | <span style="color:SteelBlue">'''• PPanel'''</span>]]===<br />
===[[Satfinders | <span style="color:SteelBlue">'''• Satfinders'''</span>]]===<br />
===[[SD_HD_4K | <span style="color:SteelBlue">'''• SD - HD - 4K'''</span>]]=== <br />
===[[Transcoding | <span style="color:SteelBlue">'''• Transcoding'''</span>]]===<br />
===[[TV-headend | <span style="color:SteelBlue">'''• TV-Headend'''</span>]]=== <br />
===[[Unicable_/_Jess | <span style="color:SteelBlue">'''• Unicable / Jess'''</span>]]=== <br />
===[[VPN | <span style="color:SteelBlue">'''• VPN'''</span>]]===<br />
===[[dvb-fe-tool | <span style="color:SteelBlue">'''• dvd-fe-tool'''</span>]]===</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Webif&diff=8962Webif2018-06-01T21:01:27Z<p>Rick Hunter: </p>
<hr />
<div>With the Webif (short for Web interface) you can control your Box using a Browser. The Web interface is included in OpenPLi. You can reach the WebIf by pointing your Browser to the IP of your Box (e.g. <nowiki>http://192.168.0.21)</nowiki>. The Web interface is fully embedded into Enigma2. It is able to use ANY functionality and obtain ANY Information Enigma2 can deliver. Webif has it's own developing site. Webif has many features and there all self explanatory, have fun.<br />
<br />
[[File:Webif-001.png|frameless|centre|800px]]<br />
<br />
<br />
<br />
'''Access OpenWebif from another subnet'''<br />
----<br />
<br />
There are currently three levels possible:<br />
<br />
1. Local access (= same subnet) is always allowed even if no login/pass is set (But if you enable auth, it will require auth).<br />
<br />
2. VPN access (= any subnet from private address space) can be allowed to access w/o password (But if you enable auth, it will require auth).<br />
<br />
3. External access non-optionally requires a login/pass to be set.<br />
<br />
<br />
VPN access is disabled by default, just go to '''Menu -> Plugins -> OpenWebif''' and toggle the setting "Enable access from VPNs" (or whatever it gets translated to) to "yes".<br />
If set to "yes" VPNs count as local network, if set to "no" VPNs are treated the same way as external networks.<br />
<br />
<br />
'''Satfinder function in the Web Interface'''<br />
----<br />
<br />
For unkown reason the Web Interface builders didn't add the hidden sat finder function. <br />
<br />
Go to: '''http://<IP address receiver>/mobile/satfinder''' to see the signal levels.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Webif&diff=8959Webif2018-06-01T21:01:08Z<p>Rick Hunter: </p>
<hr />
<div>With the Webif (short for Web interface) you can control your Box using a Browser. The Web interface is included in OpenPLi. You can reach the WebIf by pointing your Browser to the IP of your Box (e.g. <nowiki>http://192.168.0.21)</nowiki>. The Web interface is fully embedded into Enigma2. It is able to use ANY functionality and obtain ANY Information Enigma2 can deliver. Webif has it's own developing site. Webif has many features and there all self explanatory, have fun.<br />
<br />
[[File:Webif-001.png|frameless|centre|800px]]<br />
<br />
<br />
<br />
'''Access OpenWebif from another subnet'''<br />
----<br />
<br />
There are currently three levels possible:<br />
<br />
1. Local access (= same subnet) is always allowed even if no login/pass is set (But if you enable auth, it will require auth).<br />
<br />
2. VPN access (= any subnet from private address space) can be allowed to access w/o password (But if you enable auth, it will require auth).<br />
<br />
3. External access non-optionally requires a login/pass to be set.<br />
<br />
<br />
VPN access is disabled by default, just go to '''Menu -> Plugins -> OpenWebif''' and toggle the setting "Enable access from VPNs" (or whatever it gets translated to) to "yes".<br />
If set to "yes" VPNs count as local network, if set to "no" VPNs are treated the same way as external networks.<br />
<br />
<br />
'''Satfinder function in the Web Interface''';<br />
For unkown reason the Web Interface builders didn't add the hidden sat finder function. <br />
<br />
Go to: '''http://<IP address receiver>/mobile/satfinder''' to see the signal levels.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Receivers:Xtrend&diff=8353Receivers:Xtrend2018-05-15T18:12:02Z<p>Rick Hunter: </p>
<hr />
<div>'''Supported receivers'''<br /><br />
<br />
[[File:RECEIVERS-Xtrend-001.png|frameless|right]]<br />
* ET4x00<br /><br />
* ET5x00<br /><br />
* ET6000<br /><br />
* ET6500<br /><br />
* ET7000<br /><br />
* ET7500<br /><br />
* ET8000<br /><br />
* ET8500<br /><br />
* ET9000<br /><br />
* ET9200<br /><br />
* ET9500<br /><br />
* ET10000<br /><br />
<br />
Broken Securityboard? [[Receivers:Xtrend_Securityboard | Here]] is a repair instruction. (Not confirmed yet and in the German Language) or try the new drivers look at take a look in the forum Looking for our [https://forums.openpli.org <span style="color:SteelBlue"> Forum </span>]<br />
<br />
<br />
<br />
=='''How to flash the receiver...'''<br />==<br />
<br />
Download a image from: https://openpli.org<br />
Unpack the ZIP file and place the content on a USB disk.<br />
<br />
FLASHING THE RECEIVER. <br /><br />
# Unzip compressed file.<br /><br />
# Copy the "etxxxx" folder to a USB Pen Drive.<br /><br />
# Power off or reboot the receiver with the mains switch on the rear. Connect USB Pen Drive.<br /><br />
# Power on receiver with the mains switch on the rear.<br /><br />
# After rebooting or cold start the power LED will blink several times after some time. At that moment press the power button on the front panel.<br /><br />
# Flashing of the image will start<br /><br />
# Booting will start automatically once the flashing process has completed<br /><br />
<br />
<u>Note:</u> In order to load the image automagically, rename the file called "noforce" to "force"<br />
<br />
<u>'''Note:'''</u> When using a rotor unit on a ET8500 receiver, do not put the rotor on tuner 3 or 4. Somehow the rotor command's are not transmitted correctly so moving the dish isn't working. So put the rotor on tuner 1 or 2.<br />
<br />
=='''How to flash the receiver ET7x00...'''<br />==<br />
<br />
Flashing the Receiver.<br />
1) Power off the receiver<br />
2) Ensure no other USB devices are plugged into the receiver while flashing.<br />
3) Insert the USB stick containing the image files into one of the USB ports on the receiver, rear USB port is advised if possible.<br />
4) Power the receiver on, you will now see a RED LED.<br />
5) When the RED LED BLINKS after 2-3 seconds press the FRONT STANDBY button located on the front panel of the receiver to start the flashing process, a GREEN LED will also appear to indicate that the flashing is in progress.<br />
6) During the flashing process both the GREEN LED and RED LED will remain alight.<br />
7) Once complete the receiver will automatically boot into the new image.<br />
The flashing process should take approximately two to four minutes to complete, while the receiver is being flashed, it is important that you DO NOT power the receiver down for any reason as this can cause serious and or permanent damage.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7978Releasenotes-6.22018-04-17T22:56:30Z<p>Rick Hunter: /* Known issues: */</p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
* HDMI Colorimetry selectable (at Menu, Setup, System, Audio / Video, A/V settings)<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* FFMpeg update 3.4.2 and aarch64 support<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
* Fallback remote receiver setup (at Menu, Setup, Service searching). '''Beware''': If to select Import from remote receiver URL, all channel settings are replaced from remote receiver<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Lunix / Lunix3 4K<br />
<br />
== Known issues: ==<br />
* Mode 12 is not alway's possible due to hardware limitations of the SOC.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releases&diff=7975Releases2018-04-17T22:56:04Z<p>Rick Hunter: </p>
<hr />
<div>[[File:OpenPLi_6.0.png|frameless|right]]<br />
'''OpenPLi 6.0''' - The long awaited OpenPLi 6.0 heralds a new era of OpenPLi images.<br />
<br />
As of this release, we no longer release automated nightly beta images, but use a develop -> release candidate -> release flow, with fully tested and stable images are a result.<br />
<br />
'''Known Issues'''<br />
* When you create a CIFS mapping to a device mounted under /media, you get an "out of space on device" error. We are still looking for a solution for this problem.<br />
* The xmltvimport plugin no longer exists. This may give an error if you restore a backup of OpenPLi 4 on OpenPLi 6.0. To address this, install EPGimport from the plugin menu. <br />
<br />
[[Releasenotes-6.0|See the releasenotes]]<br />
<br clear=all><br />
----<br />
<br />
[[File:OpenPLi 6.1.png|frameless|right]]<br />
'''OpenPLi 6.1''' - Improvement of a good image.<br />
<br />
New receiver support for Amiko Viper Combo, Amiko Viper T2/C, VU+ Uno 4K SE, Zgemma H6, Edision OSnino. Bugfixes and introduction of new features.<br />
<br />
'''Known Issues'''<br />
* Due to problems with the overscan wizard, Xtrend ET8000 and ET10000 images can have display problems. We are still looking for a solution for this problem.<br />
* On a Mutant HD51 with mode 12 active, you can not use Video 60p frequency. With mode 1 everything is fine.<br />
* If you upgrade on the box, avahi-daemon might not want to restart (see fix in the releasenotes).<br />
<br />
[[Releasenotes-6.1|See the releasenotes]]<br />
<br clear=all><br />
----<br />
[[File:OpenPLi 6.2.png|frameless|right]]<br />
'''OpenPLi 6.2''' - Tweak and Tune.<br />
<br />
New receiver support for Zgemma support for the H9, Axas E4HD 4K Ultra, Qviart Lunix / Lunix3 4K. New drivers for the Xtend ET8000 / ET1000 Bugfixes and introduction of new features.<br />
<br />
'''Known Issues'''<br />
* Mode 12 is not alway's possible due to hardware limitations of the SOC. Further investigation is needed.<br />
<br />
[[Releasenotes-6.2|See the releasenotes]]<br />
<br clear=all><br />
----</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7972Releasenotes-6.22018-04-17T22:54:22Z<p>Rick Hunter: /* Known issues: */</p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
* HDMI Colorimetry selectable (at Menu, Setup, System, Audio / Video, A/V settings)<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* FFMpeg update 3.4.2 and aarch64 support<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
* Fallback remote receiver setup (at Menu, Setup, Service searching). '''Beware''': If to select Import from remote receiver URL, all channel settings are replaced from remote receiver<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Lunix / Lunix3 4K<br />
<br />
== Known issues: ==<br />
* Mode 12 is not alway's possible due to hardware limitations</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7969Releasenotes-6.22018-04-17T21:51:52Z<p>Rick Hunter: /* Other improvements: */</p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
* HDMI Colorimetry selectable (at Menu, Setup, System, Audio / Video, A/V settings)<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* FFMpeg update 3.4.2 and aarch64 support<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
* Fallback remote receiver setup (at Menu, Setup, Service searching). '''Beware''': If to select Import from remote receiver URL, all channel settings are replaced from remote receiver<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Lunix / Lunix3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Up-Download_magazine&diff=7894Up-Download magazine2018-04-15T13:02:12Z<p>Rick Hunter: </p>
<hr />
<div>UP/DOWNLINK’ is voor iedere satliefhebber. Een streepje voor hebben leden van De Transponder (deze krijgen het per e-mail). Anderen kunnen het iets later downloaden en lezen via de site van De Transponder.<br />
De naam ‘UP/DOWNLINK’ staat niet alleen voor de satellietterm (up naar de satelliet en down naar de schotel) maar ook voor alle informatie die wij verzamelen (up) te verspreiden naar geïnteresseerden (down). Wij hopen dat er veel bijdragen van jullie komen; hoe meer ‘ups’ des te beter!<br /><br />
De nieuwsbrief UP/DOWNLINK verschijnt een keer per maand.<br />
[[File:TRANSPONDER-UpDownload-001.jpg|frame|right]]<br />
Je mail is zeer welkom via '''specials@detransponder.nl'''<br />
<br />
<u>UP/DOWNLINK</u><br />
<br />
[http://www.detransponder.nl/wp-content/uploads/2018/03/Index-onderwerpen-van-alle-uitgebrachte-UP_DOWNLINKs.pdf <span style="color:SteelBlue">Index onderwerpen van alle uitgebrachte UP-DOWNLINKs</span>]<br />
<br />
De UP/DOWNLINKS magazines zijn [http://www.detransponder.nl/wordpress/downloads/nieuwsbrieven/ <span style="color:SteelBlue">hier</span>] te downloaden.<br /><br />
De daarin genoemde specials zijn [http://www.detransponder.nl/wordpress/downloads/specials/ <span style="color:SteelBlue">hier</span>] te downloaden.</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7891Releasenotes-6.22018-04-15T12:51:46Z<p>Rick Hunter: /* Other improvements: */</p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
* HDMI Colorimetry selectable (at Menu, Setup, System, Audio / Video, A/V settings)<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* FFMpeg update 3.4.2 and aarch64 support<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
* Fallback remote receiver setup (at Menu, Setup, Service searching). '''Beware''': If to select Import from remote receiver UTL, all channel settings are replaced from remote receiver<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Linux / Linux3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7888Releasenotes-6.22018-04-15T12:37:35Z<p>Rick Hunter: </p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
* HDMI Colorimetry selectable (at Menu, Setup, System, Audio / Video, A/V settings)<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
* Fallback remote receiver setup (at Menu, Setup, Service searching). '''Beware''': If to select Import from remote receiver UTL, all channel settings are replaced from remote receiver<br />
<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Linux / Linux3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7885Releasenotes-6.22018-04-15T12:29:27Z<p>Rick Hunter: </p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Linux / Linux3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7882Releasenotes-6.22018-04-15T12:25:40Z<p>Rick Hunter: </p>
<hr />
<div>[[File:OpenPLi 6.2.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Linux / Linux3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releases&diff=7879Releases2018-04-15T12:23:47Z<p>Rick Hunter: </p>
<hr />
<div>[[File:OpenPLi_6.0.png|frameless|right]]<br />
'''OpenPLi 6.0''' - The long awaited OpenPLi 6.0 heralds a new era of OpenPLi images.<br />
<br />
As of this release, we no longer release automated nightly beta images, but use a develop -> release candidate -> release flow, with fully tested and stable images are a result.<br />
<br />
'''Known Issues'''<br />
* When you create a CIFS mapping to a device mounted under /media, you get an "out of space on device" error. We are still looking for a solution for this problem.<br />
* The xmltvimport plugin no longer exists. This may give an error if you restore a backup of OpenPLi 4 on OpenPLi 6.0. To address this, install EPGimport from the plugin menu. <br />
<br />
[[Releasenotes-6.0|See the releasenotes]]<br />
<br clear=all><br />
----<br />
<br />
[[File:OpenPLi 6.1.png|frameless|right]]<br />
'''OpenPLi 6.1''' - Improvement of a good image.<br />
<br />
New receiver support for Amiko Viper Combo, Amiko Viper T2/C, VU+ Uno 4K SE, Zgemma H6, Edision OSnino. Bugfixes and introduction of new features.<br />
<br />
'''Known Issues'''<br />
* Due to problems with the overscan wizard, Xtrend ET8000 and ET10000 images can have display problems. We are still looking for a solution for this problem.<br />
* On a Mutant HD51 with mode 12 active, you can not use Video 60p frequency. With mode 1 everything is fine.<br />
* If you upgrade on the box, avahi-daemon might not want to restart (see fix in the releasenotes).<br />
<br />
[[Releasenotes-6.1|See the releasenotes]]<br />
<br clear=all><br />
----<br />
[[File:OpenPLi 6.2.png|frameless|right]]<br />
'''OpenPLi 6.2''' - Tweak and Tune.<br />
<br />
New receiver support for Zgemma support for the H9, Axas E4HD 4K Ultra, Qviart Linux / Linux3 4K. New drivers for the Xtend ET8000 / ET1000 Bugfixes and introduction of new features.<br />
<br />
'''Known Issues'''<br />
* TBD<br />
<br />
[[Releasenotes-6.2|See the releasenotes]]<br />
<br clear=all><br />
----</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=File:OpenPLi_6.2.png&diff=7876File:OpenPLi 6.2.png2018-04-15T12:20:42Z<p>Rick Hunter: OpenPLi 6.2 bootlogo</p>
<hr />
<div>OpenPLi 6.2 bootlogo</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7873Releasenotes-6.22018-04-15T12:08:23Z<p>Rick Hunter: /* New Receivers support: */</p>
<hr />
<div>[[File:OpenPLi 6.1.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
* Qviart - Linux / Linux3 4K<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7870Releasenotes-6.22018-04-15T12:07:05Z<p>Rick Hunter: /* New Receivers support: */</p>
<hr />
<div>[[File:OpenPLi 6.1.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
* Axas - E4HD 4K Ultra<br />
<br />
== Known issues: ==</div>Rick Hunterhttps://wiki.openpli.org/index.php?title=Releasenotes-6.2&diff=7867Releasenotes-6.22018-04-15T12:04:41Z<p>Rick Hunter: Created page with "right == Highlights: == * Improvements on Helptext messages * Show True/Flase as graphical switch * Updated languages translations * AVSwitc..."</p>
<hr />
<div>[[File:OpenPLi 6.1.png|frameless|right]]<br />
== Highlights: ==<br />
* Improvements on Helptext messages<br />
* Show True/Flase as graphical switch<br />
* Updated languages translations<br />
* AVSwitchVideoHardware - Add support for 'full' aspect ratio mode<br />
* Option Relevant PIDs routing<br />
<br />
== Other improvements: ==<br />
* Flashimage support<br />
* Plugins updates<br />
* Drivers updates<br />
* Flashimage code simplified<br />
* Autobackup<br />
* Autotimer version 4.4<br />
* PLi-Full HD cosmetic improvements <br />
<br />
<br />
== Security: ==<br />
<br />
== Bugfix: ==<br />
* VU+ Solo 4k DiSEqC fix<br />
* VU+ Solo 4k QuadPIP <br />
* Added missing Firmware for RTL8192EU<br />
* Added missing BRCM7439<br />
<br />
== New Receivers support: ==<br />
* Zgemma support for the H9<br />
<br />
<br />
== Known issues: ==</div>Rick Hunter