Jump to content


Photo

Howto build unofficial pli for your unsupported receiver


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

Re: Howto build unofficial pli for your unsupported receiver #1561 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 7 July 2018 - 17:49

Maybe this can help you :)

We need to ovverwrite the mecool bb?



Re: Howto build unofficial pli for your unsupported receiver #1562 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 7 July 2018 - 18:01

I try to use Prince files but and moham bb but i receive

| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory

Also with libgcc into bb



Re: Howto build unofficial pli for your unsupported receiver #1563 jackk111111

  • Member
  • 10 posts

0
Neutral

Posted 7 July 2018 - 19:31

on wetek play 2 with tuner dvbt in the last two versions if I place myself on a channel it will restart everything


does it only happen to me?

Re: Howto build unofficial pli for your unsupported receiver #1564 takitr

  • Senior Member
  • 77 posts

+24
Neutral

Posted 7 July 2018 - 20:42

Look this patch. Add mecool linux.bb this line. May be help you

I try to use Prince files but and moham bb but i receive

| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory

Also with libgcc into bb


diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 4ed3188..db693e6 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
INC_PR = "r4"

DEPENDS += "xz-native bc-native"
+DEPENDS_aarch64 += "libgcc"

# A KMACHINE is the mapping of a yocto $MACHINE to what is built
# by the kernel. This is typically the branch that should be built,

Edited by takitr, 7 July 2018 - 20:43.


Re: Howto build unofficial pli for your unsupported receiver #1565 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 7 July 2018 - 21:39

Look this patch. Add mecool linux.bb this line. May be help you
 

I try to use Prince files but and moham bb but i receive

| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory

Also with libgcc into bb


diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 4ed3188..db693e6 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
INC_PR = "r4"

DEPENDS += "xz-native bc-native"
+DEPENDS_aarch64 += "libgcc"

# A KMACHINE is the mapping of a yocto $MACHINE to what is built
# by the kernel. This is typically the branch that should be built,

 

 

 

Also with add the libgcc i have this error



Re: Howto build unofficial pli for your unsupported receiver #1566 bumperbee

  • Senior Member
  • 284 posts

+10
Neutral

Posted 7 July 2018 - 22:20

Thanks very much Zeros & Everyone in this Meta-Dream Team

Best Regards



Re: Howto build unofficial pli for your unsupported receiver #1567 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 7 July 2018 - 22:51

Amlogic e2procfs source code gave by author CSylvain under libreelec forum

https://mega.nz/#!DI...p9c4qzqKxjdNdxw

 

 

 

Amlogic e2procfs source code gave by author CSylvain under libreelec forum

https://mega.nz/#!DI...p9c4qzqKxjdNdxw

 

Thanks a lot :)

 

Now it's on our git for future development: https://github.com/P...logic-e2-procfs

 

too bad this module will not work on new kernels 3.14.29, It requires the old kernel 3.10.x anyone with knowledge can port the module to the newer kernel ?



Re: Howto build unofficial pli for your unsupported receiver #1568 bumperbee

  • Senior Member
  • 284 posts

+10
Neutral

Posted 8 July 2018 - 01:32

Hi Zeros & Meta-Dream Team

It could be install but keep on restarting. Initially I chose not to restore setting for a couple of times, it restart each time. There is once I was too late to choose “No” to restore, and it’s still the same, it continue to restart. Please help

Thanks



Re: Howto build unofficial pli for your unsupported receiver #1569 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 8 July 2018 - 07:47

 

 

to MasterG and Persian Prince ... as this unoficial opli could you please make a liitle change like i already mentioned it in this topic https://forums.openp...very-important/
 
its about to make a update for epgcache in short time instead of 60min which is the default value ... :)


I will make this available for you but not as a global thing and probably with a switch or something.

 

 

Persian Prince you forgot about this ... please do it for dm520  :rolleyes: :rolleyes:

 

 

Done: https://github.com/P...22aea887753fe36

 

Example for dm520:

 

Change https://github.com/P...e/dm520.conf#L7 to

MACHINE_FEATURES += "libpassthrough recovery epgcache1"

Test image: http://www.mediafire...tfs.tar.xz/file (I'm not sure about the boot status of the image itself)

 

Others could use "epgcache1" feature too as it seems it's a good feature for EPG: https://forums.openp...very-important/

 

Good luck :)


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #1570 Beeker

  • PLi® Contributor
  • 1,602 posts

+203
Excellent

Posted 8 July 2018 - 09:17

Don't use autobackup. Delete backup directory or disconnect HDD.

 

Seems a enigma2 problem.

Can you telnet to box and do

init 4
enigma2

And post output.


Dreambox dm920, Uclan Ustym4Kpro, Gigablue UHD TRIO 4K and Dreambox dm8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.


Re: Howto build unofficial pli for your unsupported receiver #1571 takitr

  • Senior Member
  • 77 posts

+24
Neutral

Posted 8 July 2018 - 11:12


Look this patch. Add mecool linux.bb this line. May be help you

I try to use Prince files but and moham bb but i receive

| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
| aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory

Also with libgcc into bb

diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 4ed3188..db693e6 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
INC_PR = "r4"

DEPENDS += "xz-native bc-native"
+DEPENDS_aarch64 += "libgcc"

# A KMACHINE is the mapping of a yocto $MACHINE to what is built
# by the kernel. This is typically the branch that should be built,


Also with add the libgcc i have this error

try this patch I think that fix issue libgcc.a
https://github.com/w...9793498ad62a51b

-libs-y += $(LIBGCC)

Re: Howto build unofficial pli for your unsupported receiver #1572 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 8 July 2018 - 11:46

 


try this patch I think that fix issue libgcc.a
https://github.com/w...9793498ad62a51b

-libs-y += $(LIBGCC)

 

 

 

Mh without this declaration i've error with function into libgcc like nand_read_logic_page



Re: Howto build unofficial pli for your unsupported receiver #1573 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 8 July 2018 - 12:20

Maybe our problem is "aarch64" and if we go 32bit it solves itself ...


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #1574 ledtou

  • Member
  • 18 posts

0
Neutral

Posted 8 July 2018 - 13:23

Maybe our problem is "aarch64" and if we go 32bit it solves itself ...

Anu news about kiii pro amlogic s912



Re: Howto build unofficial pli for your unsupported receiver #1575 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 8 July 2018 - 13:44

 

Maybe our problem is "aarch64" and if we go 32bit it solves itself ...

Anu news about kiii pro amlogic s912

 

 

I just fixed the build but what's the point?

 

We can't compile coreelec linux we can't use avl modules so what's the point of a test image?

 

As far as we can't compile a good kernel this is pointless and it's a waste of time.

 

Hese is the test image for k3pro: http://www.mediafire...sdcard.zip/file


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #1576 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 8 July 2018 - 15:30

 

 

Maybe our problem is "aarch64" and if we go 32bit it solves itself ...

Anu news about kiii pro amlogic s912

 

 

I just fixed the build but what's the point?

 

We can't compile coreelec linux we can't use avl modules so what's the point of a test image?

 

As far as we can't compile a good kernel this is pointless and it's a waste of time.

 

Hese is the test image for k3pro: http://www.mediafire...sdcard.zip/file

 

If we want to use the e2procfs posted on the libreelec forum then we can't use coreelec kernel anyways, We need to compile the 3.10 kernel  from here https://github.com/L.../amlogic-3.10.y



Re: Howto build unofficial pli for your unsupported receiver #1577 HFX

  • Senior Member
  • 323 posts

+8
Neutral

Posted 8 July 2018 - 16:20

after update  yesterday  and today my dreambox 920 ... somtimes restart my dm920  wile i looking tv

 

 

 
 

  

 
openpli homebuild dm920
 
dm920 login: root
Password:
root@dm920:~# init 4
root@dm920:~# enigma2
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
/dev/ci0: Device or resource busy
/dev/ci1: Device or resource busy
[MAIN] executing main
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
close failed in file object destructor:
IOError: [Errno 16] Device or resource busy
sh: !grep: not found
Killed
root@dm920:~#
root@dm920:~#
 

 

 
 
 


Re: Howto build unofficial pli for your unsupported receiver #1578 HFX

  • Senior Member
  • 323 posts

+8
Neutral

Posted 8 July 2018 - 16:32

Here the OpenPLi Enigma2 crash log

 
no restart now box is now ofline

Attached Files


Edited by HFX, 8 July 2018 - 16:33.


Re: Howto build unofficial pli for your unsupported receiver #1579 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 8 July 2018 - 17:46

This kernel

https://github.com/L...C/linux-amlogic

 

Is equal than OE Kernel?



Re: Howto build unofficial pli for your unsupported receiver #1580 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 8 July 2018 - 19:28

This kernel

https://github.com/L...C/linux-amlogic

 

Is equal than OE Kernel?

I don't understand you comment, but anyway After some digging I think that this kernel doesn't compile for arm64 so we're back to the coreelec 3.14.29




3 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users


    Bing (1)