Jump to content


Photo

Pli 8,3_10.1.2024


  • Please log in to reply
32 replies to this topic

Re: Pli 8,3_10.1.2024 #21 WanWizard

  • PLi® Core member
  • 68,796 posts

+1,743
Excellent

Posted 16 January 2024 - 14:58

That is only from the recovery image, on the image itself you can flash any version ?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (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 satmario

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 January 2024 - 09:06

since yesterday's openpli 9 update
backup can be restored via backupsuite.
I am dealing with a different problem.
Every month I do a full Octagon backup via backupsuite.
Restoring backups works fine, but none can be updated.
Every attempt to update the software ends in a system crash.
Can you please advise where the problem is?
 
##############################################
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Screens/SoftwareUpdate.py", line 146, in checkTraficLight
  File "/usr/lib/enigma2/python/StartEnigma.py", line 302, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/StartEnigma.py", line 312, in open
    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/StartEnigma.py", line 255, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/StartEnigma.py", line 279, in doInstantiateDialog
    dlg.applySkin()
  File "/usr/lib/enigma2/python/Screens/Screen.py", line 240, in applySkin
  File "/usr/lib/enigma2/python/Screens/Screen.py", line 253, in createGUIScreen
  File "/usr/lib/enigma2/python/Components/GUIComponent.py", line 106, in GUIcreate
  File "/usr/lib/enigma2/python/Components/VariableText.py", line 24, in postWidgetCreate
TypeError: in method 'eLabel_setText', argument 2 of type 'std::string const &'
[ePyObject] (CallObject(<bound method MessageBox.left of <class 'Screens.MessageBox.MessageBox'>(Due to a driver issue it is possible the box will no longer start after an update.
Flashing the new image is not a problem, and neither is upgrading to 9.0-release.
 
Chcete zaktualizovat Váš přijímač?)>,()) failed)
 
 
dmesg
 
<4>[hi_dvb_ca_ioctl,609] detach descrambler fail
<6>[iframe_confirm:190] iframe confirm
<6>
<4>Enter DMX_OsiPcrChannelDetachSync 0 0
<6>[iframe_finish:208] iframe finish
<6>
<4>video[0] ready to play
<4>DmxPcrAcquire 0 -1073056816
<4>Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
<4>[08:28:19:710 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 467 Failed
<4>@si2166_i2c_gate_ctrl
<4>@si2166_i2c_gate_ctrl
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>[1;32mdvb video add event 17 - 7 0
<4>[m
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>FAT-fs (mmcblk0p3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<4>proc_vmpeg_0_dst_apply_write 1
<4>proc_vmpeg_0_dst_apply_write 1
<4>bestfit
<4>wol offpanscan
<4>panscan
<4>panscan
<4>panscan
<4>proc_video_videomode_50hz_write [1080i50]
<4>proc_video_videomode_60hz_write [1080i]
<4>proc_video_videomode_24hz_write [1080p24]
<4>panscan
<4>@si2166_i2c_gate_ctrl
<4>@si2166_i2c_gate_ctrl
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>hi_dvb_set_source [dmx: 0, tuner: 0, isvtuner: 0]
<6>[hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184
<4>@si2166_diseqc_set_voltage 18V(HORIZONTAL)
<4>send discq: E0 00 00 01 C4 A2, len:3
<4>send discq: E0 00 03 01 14 A3, len:3
<4>send discq: E0 10 39 F0 44 B3, len:4
<4>@OPS diseqc tone = 1(22K-ON)
<4>si2166_set_frontend [frequency:1744000,symbol_rate:29900000,is_id:255,pls_code:262143,pls_mode:3,isdbt_sb_segment_idx:0x00000000]
<4>si2166_set_frontend [stream_id:0xffffffff]
<4>fPLL_MHz 0, LPF_KHz 30400
<4>Filter_bw_control_bit = 24
<4>fPLL_MHz 1744, LPF_KHz 30400
<4>Filter_bw_control_bit = 24
<4>si2166_set_frontend end at 1744000 took 105 ms
<4>Enter DMX_OsiPcrChannelDetachSync 0 0
<4>******************************************VIDEO_GET_FRAME_RATE 25
<4>DmxPcrAcquire 0 -1073056816
<4>Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
<4>audio[0] ready to play
<4>Enter DMX_OsiPcrChannelDetachSync 0 0
<4>DmxPcrAcquire 0 -1073056816
<4>Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
<4>video[0] ready to play
<6>[1;32mdvb video add event 2 - 25 0 30 0
<6>[m
<6>[1;32mdvb video add event 16 - 0 1
<6>[m[1;32mdvb video add event 17 - 7 0
<4>[m
<4>[08:28:32:870 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 1 Failed
<6>[1;32mdvb video add event 16 - 1 0
<6>[m
<6>[1;32mdvb video add event 2 - 30 0 25 0
<6>[m[08:28:34:615 ERROR-HI_DEMUX]:DescKeyDetach[332]:Channel 5 has not attached any descrambler
<4>[hi_dvb_ca_ioctl,417] detach descrambler fail
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>Enter DMX_OsiPcrChannelDetachSync 0 0
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>[hi_dvb_ca_ioctl,609] detach descrambler fail
<4>[hi_dvb_ca_ioctl,609] detach descrambler fail
<4>[hi_dvb_ca_ioctl,609] detach descrambler fail
<4>video[0] ready to play
<6>[iframe_confirm:190] iframe confirm
<6>
<6>[iframe_finish:208] iframe finish
<6>
<4>@si2166_i2c_gate_ctrl
<4>@si2166_i2c_gate_ctrl
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>[1;32mdvb video add event 17 - 7 0
<4>[m
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>stStdTiming[h:1280, v:1024]
<4>stStdTiming[h:1600, v:900]
<4>stStdTiming[h:1152, v:864]
<4>stStdTiming[h:1680, v:1050]
<4>FAT-fs (mmcblk0p3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<4>proc_vmpeg_0_dst_apply_write 1
<4>proc_vmpeg_0_dst_apply_write 1
<4>bestfit
<4>wol offpanscan
<4>panscan
<4>panscan
<4>panscan
<4>proc_video_videomode_50hz_write [1080i50]
<4>proc_video_videomode_60hz_write [1080i]
<4>proc_video_videomode_24hz_write [1080p24]
<4>panscan
<4>@si2166_i2c_gate_ctrl
<4>@si2166_i2c_gate_ctrl
<4>@OPS diseqc tone = 0(22K-OFF)
<4>@si2166_diseqc_set_voltage OFF
<4>hi_dvb_set_source [dmx: 0, tuner: 0, isvtuner: 0]
<6>[hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184
<4>@si2166_diseqc_set_voltage 18V(HORIZONTAL)
<4>send discq: E0 00 00 00 44 E5, len:3
<4>send discq: E0 00 03 00 94 E5, len:3
<4>send discq: E0 10 39 F0 E4 E5, len:4
<4>@OPS diseqc tone = 1(22K-ON)
<4>si2166_set_frontend [frequency:1744000,symbol_rate:29900000,is_id:255,pls_code:262143,pls_mode:3,isdbt_sb_segment_idx:0x00000000]
<4>si2166_set_frontend [stream_id:0xffffffff]
<4>fPLL_MHz 0, LPF_KHz 30400
<4>Filter_bw_control_bit = 24
<4>fPLL_MHz 1744, LPF_KHz 30400
<4>Filter_bw_control_bit = 24
<4>si2166_set_frontend end at 1744000 took 100 ms
<4>******************************************VIDEO_GET_FRAME_RATE 0
<4>DmxPcrAcquire 0 -1073056816
<4>Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
<4>audio[0] ready to play
<4>Enter DMX_OsiPcrChannelDetachSync 0 0
<4>DmxPcrAcquire 0 -1073056816
<4>Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
<4>video[0] ready to play
<6>[1;32mdvb video add event 1 - 0 0 1920 1080
<6>[m
<6>[1;32mdvb video add event 2 - 0 0 30 0
<6>[m[1;32mdvb video add event 16 - 0 1
<6>[m[1;32mdvb video add event 17 - 7 0
<6>[m
<4>[hi_dvb_ca_ioctl,417] detach descrambler fail
<4>[08:35:54:304 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 1 Failed
<6>[1;32mdvb video add event 2 - 30 0 25 0
<6>[m
<6>[1;32mdvb video add event 16 - 1 0
<6>[mproc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
<4>proc_vmpeg_0_dst_apply_write 00000001
<4>
 


Re: Pli 8,3_10.1.2024 #23 satmario

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 January 2024 - 10:51

I use openpli in all boxes since 2019.
I don't remember as many updates as in recent years.
Somewhere there will be an error that continues with many updates.


Re: Pli 8,3_10.1.2024 #24 WanWizard

  • PLi® Core member
  • 68,796 posts

+1,743
Excellent

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 Pro (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 satmario

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 January 2024 - 16:02

I've never had a problem with an update even though a 2 month old backup was pulled.
This version is December 2023
Even if I use backup image openpli January 2024 same problem.
Green screen


Re: Pli 8,3_10.1.2024 #26 WanWizard

  • PLi® Core member
  • 68,796 posts

+1,743
Excellent

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 Pro (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 satmario

  • Senior Member
  • 39 posts

0
Neutral

Posted 17 January 2024 - 17:57

Thank you very much for the information friend and passing the problem on


Re: Pli 8,3_10.1.2024 #28 fatmate

  • Member
  • 4 posts

0
Neutral

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 littlesat

  • PLi® Core member
  • 56,417 posts

+692
Excellent

Posted 24 January 2024 - 22:37

Yes that is a solution…. But it is kind of egg/chicken…. And maybe better to and easier to flash 9.0 as you still can get the thing with the driver. Maybe we can consider to adapt here but then still a reflash is needed

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 fatmate

  • Member
  • 4 posts

0
Neutral

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 littlesat

  • PLi® Core member
  • 56,417 posts

+692
Excellent

Posted 24 January 2024 - 22:42

There was also a minor update from python involved here that causes a chicken/egg syndrome. That is naughty!

Edited by littlesat, 24 January 2024 - 22:43.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Pli 8,3_10.1.2024 #32 WanWizard

  • PLi® Core member
  • 68,796 posts

+1,743
Excellent

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 Pro (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 Pr2

  • PLi® Contributor
  • 6,086 posts

+258
Excellent

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
 



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users