Jump to content


Photo

OpenPLi Release Candidate 7.2


  • This topic is locked This topic is locked
237 replies to this topic

Re: OpenPLi Release Candidate 7.2 #61 FRAP

  • Senior Member
  • 334 posts

+23
Neutral

Posted 2 October 2019 - 15:41

WanWizard

Thank! I did not know that.


Alcohol for wimps. Strong people enjoy depression.


Re: OpenPLi Release Candidate 7.2 #62 djlaz

  • New Member
  • 3 posts

0
Neutral

Posted 2 October 2019 - 16:39

hello thanks fo all the works done 

i have a request can we have a restart openli button (blue for example) when we install plugins ?

between anyone know how to backup all the plugins after a fresh install (include the plugins out of the feed) ?


Edited by djlaz, 2 October 2019 - 16:42.


Re: OpenPLi Release Candidate 7.2 #63 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 17:50

Why would you want that? Which plugin requires that?

 

If you configure autobackup in the menu, you can also configure it should create an autoinstall file. This will contain all your installed plugins.

 

For manually installed plugins, you can copy the ipk files into the backup directory in the configured backup location, so they can be restored too after a flash.


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: OpenPLi Release Candidate 7.2 #64 djlaz

  • New Member
  • 3 posts

0
Neutral

Posted 2 October 2019 - 17:54

WanWizard Thanks for the informations i'm tired reinstalling all the plugins when i flash a new version



Re: OpenPLi Release Candidate 7.2 #65 djlaz

  • New Member
  • 3 posts

0
Neutral

Posted 2 October 2019 - 18:00

how to create auto install files ?



Re: OpenPLi Release Candidate 7.2 #66 Pike_Bishop

  • Senior Member
  • 1,140 posts

+74
Good

Posted 2 October 2019 - 18:23

Hi,

 

crash on vu ultimo 4k

 

Attached File  enigma2_crash_1569938098.log   48.99KB   8 downloads

 

 

regards

Pike


Receiver: VU Ultimo 4K, Octagon SF8008 4K, Gigablue Quad 4K

Image: OpenPLI-8.3


Re: OpenPLi Release Candidate 7.2 #67 nikos100

  • Senior Member
  • 25 posts

0
Neutral

Posted 2 October 2019 - 18:41

hello

 

crash network  xtrend 6500

 

OpenPLi Enigma2 crash log

crashdate=Κυρ Σεπ 29 23:18:13 2019
compiledate=Sep 29 2019
skin=PLi-FullNightHD/skin.xml
sourcedate=2019-09-28
branch=rc
rev=32e20d3
component=Enigma2

stbmodel=et6500
stbmodel=dm800se
kernelcmdline= bmem=216M ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs console=null consoleblank=0
nimsockets=NIM Socket 0:
imageissue=openpli 7.2-rc %h


[eDVBPESReader] ERROR reading PES (fd=52): Value too large for defined data type
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/Console.py", line 37, in finishedCB
  File "/usr/lib/enigma2/python/Components/Network.py", line 435, in checkNetworkStateFinished
  File "/usr/lib/enigma2/python/Screens/NetworkSetup.py", line 966, in checkNetworkCB
AttributeError: 'AdapterSetupConfiguration' object has no attribute 'iface'


dmesg

<7>pcpu-alloc: [0] 0 [0] 1
<4>Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
<5>Kernel command line:  bmem=216M ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs console=null consoleblank=0
<6>PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<5>__ex_table already sorted, skipping sort
<6>Memory: 290404k/524288k available (6148k kernel code, 233884k reserved, 1528k data, 316k init, 0k highmem)
<6>Hierarchical RCU implementation.
<6>NR_IRQS:160
<7>Measuring MIPS counter frequency...
<6>Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
<6>Console: colour dummy device 80x25
<6>Calibrating delay loop... 401.40 BogoMIPS (lpj=200704)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 512
<6>SMP: Booting CPU1...
<6>CPU revision is: 0002a044 (Brcm4380)
<6>FPU revision is: 00130001
<4>Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
<4>Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
<6>SMP: CPU1 is running
<6>Brought up 2 CPUs
<6>devtmpfs: initialized
<6>NET: Registered protocol family 16
<6>USB0: power enable is active low; overcurrent is active low
<6>PCI2.3->SDRAM window: 512 MB
<6>bio: create slab <bio-0> at 0
<5>SCSI subsystem initialized
<7>libata version 3.00 loaded.
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Linux video capture interface: v2.00
<6>Advanced Linux Sound Architecture Driver Initialized.
<6>PCI host bridge to bus 0000:00
<6>pci_bus 0000:00: root bus resource [mem 0xd0000000-0xefffffff]
<6>pci_bus 0000:00: root bus resource [io  0x0400-0x83ff]
<6>pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
<7>pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
<6>PCI host bridge to bus 0000:01
<6>pci_bus 0000:01: root bus resource [mem 0x10510000-0x1051ffff]
<6>pci_bus 0000:01: root bus resource [io  0x8400-0x87ff]
<6>pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
<7>pci 0000:01:00.0: [14e4:8602] type 00 class 0x01010f
<6>PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
<7>pci 0000:01:00.0: reg 24: [mem 0x00000000-0x00000fff]
<7>pci 0000:01:00.0: reg 30: [mem 0x00000000-0x000007ff pref]
<7>pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
<6>pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
<6>pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
<6>Bluetooth: Core ver 2.16
<6>NET: Registered protocol family 31
<6>Bluetooth: HCI device and connection manager initialized
<6>Bluetooth: HCI socket layer initialized
<6>Bluetooth: L2CAP socket layer initialized
<6>Bluetooth: SCO socket layer initialized
<6>cfg80211: Calling CRDA to update world regulatory domain
<6>Switching to clocksource upg
<5>FS-Cache: Loaded
<6>NET: Registered protocol family 2
<6>TCP established hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>TCP: reno registered
<6>UDP hash table entries: 256 (order: 1, 8192 bytes)
<6>UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
<6>NET: Registered protocol family 1
<6>RPC: Registered named UNIX socket transport module.
<6>RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
<6>RPC: Registered tcp NFSv4.1 backchannel transport module.
<7>PCI: CLS 0 bytes, default 64
<5>NFS: Registering the id_resolver key type
<5>Key type id_resolver registered
<5>Key type id_legacy registered
<6>fuse init (API version 7.20)
<6>msgmni has been set to 567
<6>io scheduler noop registered
<6>io scheduler cfq registered (default)
<6>Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
<6>serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
<6>serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
<6>loop: module loaded
<7>sata_brcmstb 0000:01:00.0: version 4.0
<7>__clk_enable: sata [1]
<4>PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
<7>sata_brcmstb 0000:01:00.0: setting latency timer to 64
<6>scsi0 : sata_brcmstb
<6>scsi1 : sata_brcmstb
<6>ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
<6>ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
<6>Broadcom STB NAND controller (BrcmNand Controller)
<6>bcmemac: Broadcom STB 10/100 EMAC driver v3.0
<6>bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:16:b4:05:ff:f0)
<6>bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
<6>usbcore: registered new interface driver zd1201
<6>ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<7>__clk_enable: usb [1]
<6>ehci-brcm ehci-brcm.0: Broadcom STB EHCI
<6>ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
<6>ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
<6>ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<6>ehci-brcm ehci-brcm.1: Broadcom STB EHCI
<6>ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
<6>ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
<6>ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 2 ports detected
<6>ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>ohci-brcm ohci-brcm.0: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
<6>ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>ohci-brcm ohci-brcm.1: Broadcom STB OHCI
<6>ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
<6>ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 2 ports detected
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>mousedev: PS/2 mouse device common for all mice
<6>i2c /dev entries driver
<6>usbcore: registered new interface driver btusb
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>TCP: cubic registered
<6>NET: Registered protocol family 17
<6>Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>Bluetooth: HIDP socket layer initialized
<5>Key type dns_resolver registered
<6>EBI CS1: setting up NAND flash (primary)
<6>mtd->oobsize=0, mtd->eccOobSize=0
<4>NAND_CS_NAND_XOR=00000000
<4>B4: NandSelect=50000200, nandConfig=18152300, chipSelect=1
<4>brcmnand_read_id: CS1: dev_id=ecd35195
<4>After: NandSelect=50000200, nandConfig=18152300
<4>Block size=00020000, erase shift=17
<6>NAND Config: Reg=18152300, chipSize=1024 MB, blockSize=128K, erase_shift=11
<6>busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
<4>timing1 not adjusted: 5363444f
<4>timing2 not adjusted: 00000fc6
<4>eccLevel=15, 1Ksector=0, oob=16
<4>nbrBitsPerCell=2, cellinfo=0, chip->cellinfo=00000000
<4><--brcmnand_set_acccontrol: acc b4: d7ff1010, after: d7ff1010
<6>BrcmNAND mfg ec d3 Samsung K9F8G08U0M 1024MB on CS1
<6>
<6>Found NAND on CS1: ACC=d7ff1010, cfg=18152300, flashId=ecd35195, tim1=5363444f, tim2=00000fc6
<6>BrcmNAND version = 0x0302 1024MB @00000000
<4>B4: NandSelect=50000200, nandConfig=18152300, chipSelect=1
<4>brcmnand_read_id: CS1: dev_id=ecd35195
<4>After: NandSelect=50000200, nandConfig=18152300
<4>Found NAND flash on Chip Select 1, chipSize=1024MB, usable size=1024MB, base=0
<4>brcmnand_scan: B4 nand_select = 50000200
<4>brcmnand_scan: After nand_select = 50000200
<6>page_shift=11, bbt_erase_shift=17, chip_shift=30, phys_erase_shift=17
<6>Brcm NAND controller version = 3.2 NAND flash size 1024MB @00000000
<4>ECC layout=brcmnand_oob_bch4_4k
<6>brcmnand_scan:  mtd->oobsize=64
<6>brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
<6>brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
<4>-->brcmnand_default_bbt
<4>brcmnand_default_bbt: bbt_td = bbt_main_descr
<7>Bad block table Bbt0 found at page 0007ffc0, version 0x01 for chip on CS1
<7>Bad block table 1tbB found at page 0007ff80, version 0x01 for chip on CS1
<7>nand_read_bbt: Bad block at 0x02680000
<7>nand_read_bbt: Bad block at 0x13f80000
<7>nand_read_bbt: Bad block at 0x19320000
<4>Adjust partition complete size from entire device to 3ff80000 to avoid overlap with BBT reserved space
<4>Adjust partition rootfs size from entire device to 3f980000 to avoid overlap with BBT reserved space
<5>Creating 3 MTD partitions on "brcmnand.0":
<5>0x000000000000-0x00003ff80000 : "complete"
<5>0x000000000000-0x000000600000 : "kernel"
<5>0x000000600000-0x00003ff80000 : "rootfs"
<6>PM: CP0 COUNT/COMPARE frequency depends on divisor
<5>UBI: attaching mtd2 to ubi0
<6>ata1: SATA link down (SStatus 4 SControl 300)
<6>usb 2-1: new high-speed USB device number 2 using ehci-brcm
<6>hub 2-1:1.0: USB hub found
<6>hub 2-1:1.0: 4 ports detected
<6>ata2: SATA link down (SStatus 4 SControl 300)
<6>usb 2-1.2: new full-speed USB device number 3 using ehci-brcm
<5>UBI: scanning is finished
<5>UBI: attached mtd2 (name "rootfs", size 1017 MiB) to ubi0
<5>UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
<5>UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
<5>UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
<5>UBI: good PEBs: 8137, bad PEBs: 3, corrupted PEBs: 0
<5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
<5>UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1480973098
<5>UBI: available PEBs: 0, total reserved PEBs: 8137, PEBs reserved for bad PEB handling: 157
<6>ALSA device list:
<6>  No soundcards found.
<5>UBI: background thread "ubi_bgt0d" started, PID 49
<4>Warning: unable to open an initial console.
<5>UBIFS: background thread "ubifs_bgt0_0" started, PID 50
<5>UBIFS: mounted UBI device 0, volume 0, name "rootfs"(null)
<5>UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
<5>UBIFS: FS size: 518696960 bytes (494 MiB, 4085 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
<5>UBIFS: reserved for root: 0 bytes (0 KiB)
<5>UBIFS: media format: w4/r0 (latest is w4/r0), UUID ADFFF55F-E866-44E0-9430-69B59B1890C0, small LPT model
<6>VFS: Mounted root (ubifs filesystem) on device 0:10.
<6>devtmpfs: mounted
<6>Freeing unused kernel memory: 316k freed
<6>usbcore: registered new interface driver tpm
<4>dvb: module_layout: kernel tainted.
<4>Disabling lock debugging due to kernel taint
<6>Console: switching to colour frame buffer device 160x45
<6>input: dreambox remote control (native) as /devices/virtual/input/input0
<6>input: dreambox advanced remote control (native) as /devices/virtual/input/input1
<6>DVB: registering new adapter (dvb0)
<6>platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
<6>input: front panel as /devices/virtual/input/input2
<6>Console: switching to colour dummy device 80x25
<6>NET: Registered protocol family 10
<6>Installing knfsd (copyright © 1996 okir@monad.swb.de).

 



Re: OpenPLi Release Candidate 7.2 #68 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,494 posts

+397
Excellent

Posted 2 October 2019 - 18:57

Hi,
 
crash on vu ultimo 4k

attachicon.gifenigma2_crash_1569938098.log

regards
Pike

First try the default skin please.

Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: OpenPLi Release Candidate 7.2 #69 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 20:20

how to create auto install files ?

 

It will be created automatically when you have autobackup make a backup. It knows what was part of the image, and what you have installed later.


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: OpenPLi Release Candidate 7.2 #70 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 20:23

First try the default skin please.

 

And get rid of the ModifyPLiFullHD plugin.


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: OpenPLi Release Candidate 7.2 #71 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 20:23

hello

 

crash network  xtrend 6500

 

More information please. What where you doing when this happened? What network is used? LAN? Wifi? USB device?


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: OpenPLi Release Candidate 7.2 #72 Pike_Bishop

  • Senior Member
  • 1,140 posts

+74
Good

Posted 2 October 2019 - 21:05

 

Hi,
 
crash on vu ultimo 4k

attachicon.gifenigma2_crash_1569938098.log

regards
Pike

First try the default skin please.

 

 

Hi Frenske,

 

the default skin is a full hd-skin and it's a more beautiful skin :)

but i need a only hd-skin because several plugins which i use as example;

birthdayreminder

are not skinned for full-hd, also the filecommander plugin isn't skinned complete for full-hd i have seen, and so that looks not good (all is very small then).

 

 

 

 

First try the default skin please.

 

And get rid of the ModifyPLiFullHD plugin.

 

 

is it unstable ?

i use it only to change colors, and a font, you can see it in the followig picture;

 

Attached File  screenshot_2019-10-02_22-01-29.jpg   158.93KB   6 downloads

 

it looks good for me :)

 

 

regards

Pike


Edited by Pike_Bishop, 2 October 2019 - 21:06.

Receiver: VU Ultimo 4K, Octagon SF8008 4K, Gigablue Quad 4K

Image: OpenPLI-8.3


Re: OpenPLi Release Candidate 7.2 #73 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 21:13

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 190, in __init__
    p(reason=0, session=self)
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/plugin.py", line 31, in autostart
    ui.modifyskin.applyAutorun()
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/ui.py", line 517, in applyAutorun
    self.reloadSkin()
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/ui.py", line 544, in reloadSkin
    skin.loadSingleSkinData(enigma.getDesktop(0), root, path)
  File "/usr/lib/enigma2/python/skin.py", line 683, in loadSingleSkinData
  File "/usr/lib/enigma2/python/skin.py", line 286, in loadPixmap
SkinError: {PLi-HD1/skin.xml}: pixmap file window/top_left_corner.png not found!. Please contact the skin's author!

The plugin seems to do something the skin doesn't support, or visa versa.


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: OpenPLi Release Candidate 7.2 #74 nikos100

  • Senior Member
  • 25 posts

0
Neutral

Posted 2 October 2019 - 21:25

in the box sign in with cable lan


Edited by nikos100, 2 October 2019 - 21:26.


Re: OpenPLi Release Candidate 7.2 #75 nikos100

  • Senior Member
  • 25 posts

0
Neutral

Posted 2 October 2019 - 21:37

Attached Files

  • Attached File  1.jpg   41.14KB   0 downloads

Edited by nikos100, 2 October 2019 - 21:39.


Re: OpenPLi Release Candidate 7.2 #76 nor50

  • Senior Member
  • 423 posts

+1
Neutral

Posted 2 October 2019 - 21:40

I get a new Ultimo 4K in a few days. Is it worth installing this? Is it stable?


VU+ Ultimo 4K, 19.2, 13, 4.8 E via switch on input/tuner 1. 1W. Inverto Unicable II LNB IDLU-32UL40 on input/tuner 2. OpenPLi 8.3


Re: OpenPLi Release Candidate 7.2 #77 nikos100

  • Senior Member
  • 25 posts

0
Neutral

Posted 2 October 2019 - 21:43

when i wait for about 4 seconds it opens lan

 

Attached Files

  • Attached File  2.jpg   36.15KB   7 downloads

Edited by nikos100, 2 October 2019 - 21:44.


Re: OpenPLi Release Candidate 7.2 #78 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 22:19

I get a new Ultimo 4K in a few days. Is it worth installing this? Is it stable?

 

It is a release candidate, issues are still being found and fixed, but so far nothing major.

 

If you don't mind flashing again once the release it out, it should work fine. We run it on most of our boxes...


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: OpenPLi Release Candidate 7.2 #79 WanWizard

  • PLi® Core member
  • 70,542 posts

+1,812
Excellent

Posted 2 October 2019 - 22:20

when i wait for about 4 seconds it opens lan

 

Looks like it takes a long time before the network is ready?

 

Cable issues? Switch negotiation issues? Slow DHCP server?


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: OpenPLi Release Candidate 7.2 #80 Pike_Bishop

  • Senior Member
  • 1,140 posts

+74
Good

Posted 2 October 2019 - 23:49

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 190, in __init__
    p(reason=0, session=self)
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/plugin.py", line 31, in autostart
    ui.modifyskin.applyAutorun()
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/ui.py", line 517, in applyAutorun
    self.reloadSkin()
  File "/usr/lib/enigma2/python/Plugins/Extensions/ModifyPLiFullHD/ui.py", line 544, in reloadSkin
    skin.loadSingleSkinData(enigma.getDesktop(0), root, path)
  File "/usr/lib/enigma2/python/skin.py", line 683, in loadSingleSkinData
  File "/usr/lib/enigma2/python/skin.py", line 286, in loadPixmap
SkinError: {PLi-HD1/skin.xml}: pixmap file window/top_left_corner.png not found!. Please contact the skin's author!

The plugin seems to do something the skin doesn't support, or visa versa.

 

 

ok now i have deinstalled the ModifyPLiFullHD plugin and changed the font and colors manually in the skin.xml to PLi-HD1 - that works similarly

(one plugin lesser) :)

 

@WanWizard -btw can you commit this for PLI-7.2rc please;

https://forums.openp...dpost&p=1091163

 

 

regards

Pike


Receiver: VU Ultimo 4K, Octagon SF8008 4K, Gigablue Quad 4K

Image: OpenPLI-8.3



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users