That is only from the recovery image, on the image itself you can flash any version ?
Pli 8,3_10.1.2024
Re: Pli 8,3_10.1.2024 #21
Posted 16 January 2024 - 14:58
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Pli 8,3_10.1.2024 #22
Posted 17 January 2024 - 09:06
Re: Pli 8,3_10.1.2024 #23
Re: Pli 8,3_10.1.2024 #24
Posted 17 January 2024 - 14:37
There are hardly ever any updates in an OpenPLi release image.
There is a warning out for updates, and appearently that code has not been checked or tested for a while, so the problem is rather the lack of an update .
So this needs looking at.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Pli 8,3_10.1.2024 #25
Re: Pli 8,3_10.1.2024 #26
Posted 17 January 2024 - 16:07
It has nothing to do with updates, or the update mechanism.
OpenPLi has a built-in warning system, where we can enable warnings for certain boxes and/or releases, to inform users not to update if there are issues, via a json file on our website.
A warning has been enabled for the SF8008, which might hang after an update due to a driver update issue. It is this enabling that is causing the green screen on both 8.3-release and 9.0-release.
I don't know what is causing the problem, and how to fix it, as I am not a Python developer. I've passed the issue on so it can be looked at.
In general, there is no need to ever update a release image, as the image itself hardly ever has updates. An update is only needed for stuff like picons, channel lists, or if you use the transponder xml for scanning.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Pli 8,3_10.1.2024 #27
Re: Pli 8,3_10.1.2024 #28
Posted 24 January 2024 - 22:25
Just to prevent the crash (Green Screen) :
1- Download the file : https://raw.githubus...VariableText.py
2- Change line-11:
From : self.message = text
To : self.message = str(text)
3- Copy the file to : /usr/lib/enigma2/python/Components/
4- Restart GUI.
Result: There will be no crash and a proper message will be shown.
Re: Pli 8,3_10.1.2024 #29
Posted 24 January 2024 - 22:37
Edited by littlesat, 24 January 2024 - 22:39.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Pli 8,3_10.1.2024 #30
Posted 24 January 2024 - 22:40
I'm sure PLi Team has the proper solution, but that was a temporary approach for me on both version.
Image : OpenPLi 8.3-release
Build Date : 2024-01-17
Tested on : Octagon SF8008
And, for v9.0, it is line-10 in : https://gitlab.openp...VariableText.py
Re: Pli 8,3_10.1.2024 #31
Re: Pli 8,3_10.1.2024 #32
Posted 25 January 2024 - 12:19
This is the correct fix: https://github.com/O...c9e3892fb9761e1
The problem exists because of a bug in the Python 2.7 version used in 8.3-release, in which json.load() returns a unicode string instead of standard string ( in python 3 terms, it returns str instead bytes ). This bug was not present in earlier versions, and corrected in later ones.
You can also fix it by updating on the commandline:
opkg update && opkg upgrade
or to flash the current 8.3-release with a backup/restore.
The change in VariableText is a hack, the problem should be fixed at source. Besides that, in Pyhton 3 str() won't work, as you need to encode/decode between str and bytes.
And downloading the develop version of the py and installing it in 8.3-release is very bad advice, that could lead to all kinds of trouble.
Edited by WanWizard, 25 January 2024 - 14:25.
correct typo
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Pli 8,3_10.1.2024 #33
Posted 25 January 2024 - 13:17
You should use, there is a small typo in WanWizard answer:
opkg update && opkg upgrade
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users