580 replies to this topic

[fpignon]

@fpignon,  flash the OpenPLi 9 nightly build because this has been fixed in it.

Thanks PR2. I originally flashed OpenPli 9 stable release from November 13 so I assume it should have the fix in it?
I've also installed latest updates (from November 19) but the crash is still occuring.

 

[helloween]

Hi, i bought a ax206 3,5 480x320 Display from aliexpress. With openpli 8.3 it worked out of the box.

 

With openpli 9 and openpli 9 dev i tested the new display and also my pearl 2,8" Display.

 

Nothing is working any more. Only my vu+ uno 4k se internal display is working.

Even with new empty openpli 9 install with no settings it wasn´t working.

 

On lcd4linux log i get dpf not found...

 

Any idea? Is this a problem of openpli 9 (python3) or lcd4linux? I have seen some comments, that lcd4linux should work with external usb displays?

 

So why is even my pearl 2,8 display not working?

Edited by helloween, 20 November 2023 - 23:06.

[littlesat]

I just discovered that some code is merged... so after a next finished build from develop it should be possible again to use your display.

[ghuss]

 

 

I have two problems after flash to 9.0 on my VuDuo2!

First, the Clock on LCD.window does not show up (black screen)

Second, LCD4Linux setting in Webif does not work for me

"Error 404: Not found The requested page doesn't exist", it says in my web browsers (Safari and Brave)

I have reflashed twice and the same result both times

The LCD4Linux plugin works as what I can see!

 

lcd4linux should work now, affter a software update and a reboot.

 

I can't confirm any web interface issues, the lcd4linux page works fine here, on the Duo2.

 

    great job    @WanWiard . thank you . lcd4linux works very well now on vu+duo2  

 

Dear

after flash to 9.0 on my  my  VU+ Duo2 

 

LCD4Linux  does not have LCD1 Type Internal VU+ Duo2 LCD 400x240

Used the LCD4Linux settings page in WEB-interface and checked the drop-down box for LCD 1 , LCD1 Type does not have  "Internal VU+ Duo2 LCD 400x240"

 

also couldn't find plugin for EPG translater.

[helloween]

I just discovered that some code is merged... so after a next finished build from develop it should be possible again to use your display.

Nearly every day my openpli 9 dev gets an online update.

 

So when i update my box today, will this new code from lcd4linux be included already? I can see updates for many packages, but lcd4linux i haven´t seen the last time on my update page.

[WanWizard]

You'll have to check. You can find the details of the change here: https://github.com/O...commits/develop

 

You will have to wait for a build to finish which started AFTER these changes. You can find the status of the build on our homepage, in the sidebar.

[WanWizard]

LCD4Linux  does not have LCD1 Type Internal VU+ Duo2 LCD 400x240
 
Used the LCD4Linux settings page in WEB-interface and checked the drop-down box for LCD 1 , LCD1 Type does not have  "Internal VU+ Duo2 LCD 400x240"

 
That sounds like you haven't got the latest version, given the fact this should be fixed.
 

also couldn't find plugin for EPG translater

 

If that was a third party EPG, you'll need to find a python 3 compatible version for it. Most plugins from 8.x are not compatible with python 3.

 

Let us know if you find a working version, so we can add it to the feed again for you.

[DimitarCC]

OE-A have py3 version of EPG Translator but i dont know is it the same....

[WanWizard]

I can't find EPG translator in any feed, so it must have been installed manually?

[DimitarCC]

There is EPG translator in OpenViX feed....

[rauldelavega]

 

 

OpenPli 9.0 release - EDISION OS Mega

I can't create back up. Backupsuite cannot create kerneldump and stops.

 

 

Did it work in 8.3 ? Any specific error messages?

 

Can you get the /tmp/BackupSuite.log file from the box and post it here as an attachment?

 

On version 8.3 it is OK. On 9.0 the system stops at creating kerneldump. Backupsuite log is not created.

 

 

I'm asking, I have the same problem..

 

*****  https://github.com/p...BackupSuite-PLi  ******

 

Plugin version     = 256d108

Back-up media      = /hdd

Filesystem                Size      Used Available Use% Mounted on

/dev/sda1               297.0G    106.6G    190.4G  36% /media/hdd

 

Back-up = 2023.11.20_13:36

Version = openpli 9.0-release 

Flashed = 2023.11.12_20:25

Updated = 2023.11.19_08:35

Drivers = os-dvb-modules-osmega - 4.11.0+20171106-r0.0

Enigma2 = 2023-10-27-release-9.0

 

 

Working directory  = /hdd/bi

Not Open Vision, OpenPLi or SatDreamGr maybe?

Destination        = /hdd/fullbackup_osmega/20231120_1336/osmega

 

RECEIVER = Edision OS mega 

MKUBIFS_ARGS = -m 2048 -e 126976 -c 4096 -F

UBINIZE_ARGS = -m 2048 -p 128KiB

KERNEL dimensione del backup:   8192 KB

ROOTFS dimensione del backup: 111252 KB

=TOTAL dimensione del backup: 119444 KB (= 116 MB)

Si prega di essere pazienti, un backup sarà eseguito e impiegherà circa: 7.57 Minuti

 

*** FIRST SOME HOUSEKEEPING ***

Remove directory   = /hdd/bi

Recreate directory = /hdd/bi

Create directory   = /tmp/bi/root

 

UBINIZE.CFG CREATED WITH THE CONTENT:

[ubifs]

mode=ubi

image=/hdd/bi/root.ubi

vol_id=0

vol_type=dynamic

vol_name=rootfs

vol_flags=autoresize

--------------------------

 

Creando: Kerneldump

Kernel resides on mtd0

[Dimitrij]

if [ $ROOTNAME != "rootfs.tar.bz2" -o $SEARCH = "h9" -o $SEARCH = "i55plus" -o $SEARCH = "i55se" -o $SEARCH = "hzero" -o $SEARCH = "h8" -o $SEARCH = "h8.2h" -o $SEARCH = "h9.s" -o $SEARCH = "h9.t" -o $SEARCH = "h9.2h" -o $SEARCH = "h9.2s" ] ; then
	log "Kernel resides on $MTDPLACE" 					# Just for testing purposes
	$NANDDUMP /dev/$MTDPLACE -qf "$WORKDIR/$KERNELNAME"
	if [ -f "$WORKDIR/$KERNELNAME" ] ; then
		echo -n "Kernel dumped  :"  >> $LOGFILE
		ls $LS1 "$WORKDIR/$KERNELNAME" | sed 's/-r.*   1//' >> $LOGFILE
	else
		log "$WORKDIR/$KERNELNAME NOT FOUND"
		big_fail
	fi
	log "--------------------------"
else

stop this

$NANDDUMP /dev/$MTDPLACE -qf "$WORKDIR/$KERNELNAME"

 

 

maybe

$NANDDUMP /dev/$MTDPLACE -q > "$WORKDIR/$KERNELNAME"

Edited by Dimitrij, 21 November 2023 - 19:07.

[helloween]

Sadly lcd4linux still doesn´t work with any of my external displays...

 

Log:

 

21:09:30 get DPF2 Device...
21:09:30 1. Vendor=1908 ProdID=0102 True
21:09:30 open DPF2 Device0...
21:09:30 DPF2 Device not found
21:09:45 get DPF2 Device...
21:09:45 1. Vendor=1908 ProdID=0102 True
21:09:45 open DPF2 Device0...
21:09:45 DPF2 Device not found
21:10:00 get DPF2 Device...
21:10:00 1. Vendor=1908 ProdID=0102 True
21:10:00 open DPF2 Device0...

 

 

Long Log with 2 external Displays:

 

21:15:31 open DPF2 Device0...
21:15:31 get DPF3 Device...
21:15:31 usb.core [<DEVICE ID 1908:0102 on Bus 006 Address 002>, <DEVICE ID 1908:0102 on Bus 003 Address 005>]
21:15:31 usb.core find
21:15:31 1. Vendor=1908 ProdID=0102 True
21:15:31 open DPF3 Device0...
21:15:31 DPF2 Device not found
21:15:31 DPF3 Device not found
21:15:34 Update...Qlen= 0
21:15:34 UpdateTime: 0.0009872913360595703
21:15:39 Update...Qlen= 0
21:15:39 UpdateTime: 0.000982046127319336
21:15:44 Update...Qlen= 0
21:15:44 UpdateTime: 0.0009582042694091797
21:15:46 get DPF2 Device...
21:15:46 usb.core [<DEVICE ID 1908:0102 on Bus 006 Address 002>, <DEVICE ID 1908:0102 on Bus 003 Address 005>]
21:15:46 usb.core find
21:15:46 1. Vendor=1908 ProdID=0102 True
21:15:46 open DPF2 Device0...
21:15:46 get DPF3 Device...
21:15:46 usb.core [<DEVICE ID 1908:0102 on Bus 006 Address 002>, <DEVICE ID 1908:0102 on Bus 003 Address 005>]
21:15:46 usb.core find
21:15:46 1. Vendor=1908 ProdID=0102 True
21:15:46 open DPF3 Device0...
21:15:46 DPF2 Device not found
21:15:46 DPF3 Device not found
21:15:49 Update...Qlen= 0
21:15:49 UpdateTime: 0.0010950565338134766

Edited by helloween, 21 November 2023 - 21:17.

[mimbel]

good evening my vupluszero 4K no longer starts it remains fixed on the startup screen solutions please

root@vuzero4k:~# ENIGMA_DEBUG_LVL=3 enigma2
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 11
ENIGMA_DEBUG_LVL=3
[MAIN] executing main
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/StartEnigma.py", line 27, in <module>
    from Screens import InfoBar
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 14, in <module>
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1, in <module>
  File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 33, in <module>
  File "/usr/lib/enigma2/python/Components/Converter/ServiceInfo.py", line 3, in <module>
    from Screens.InfoBarGenerics import hasActiveSubservicesForCurrentChannel
ImportError: cannot import name 'hasActiveSubservicesForCurrentChannel' from partially initialized module 'Screens.InfoBarGenerics' (most likely due to a circular import) (/usr/lib/enigma2/python/Screens/InfoBarGenerics.pyc)
root@vuzero4k:~# 

 

[Frenske]

Did you try to flash the box without restoring a previous backup? You can always restore that backup later if a fresh flash didn’t help. 
If a fresh flash worked there is something in your backup which causes this issue.

[littlesat]

Looks like a faulty designed plugin or skin replaces some code.

[mimbel]

yes apparently is a skin that has caused a lot of problems with youtubetv and the default skins. how can I at least manage to start the receiver? or at least recover the wifi driver and favorite channels by FTP?

[WanWizard]

You can telnet into the box, issue the command

init 4

to make sure Enigma isn't running, then edit /etc/enigma2/settings, and remove the config line with your selected skin. Then restart Enigma using

init 3

and it will fall back to the default skin.

[mimbel]

the problem unfortunately persists
how to recover favorite channels and wifi driver? I would like to do an installation but I do not have a network connection

[WanWizard]

Changes are your skin has overwritten enigma core files. You can try:

init 4
opkg install enigma2 --force-reinstall

to get the original core files back. If you have removed the skin config, this should make the box start again.

 

You can't extract drivers, if you flash the box, you can simply install them again? And to extract a channel list, you need the files *.tv and *.radio from /etc/enigma2.