Jump to content


Photo

Howto build unofficial pli for your unsupported receiver

Started by Persian Prince, 30 Jan 2018 09:10

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

Re: Howto build unofficial pli for your unsupported receiver #2641 ndminion

  • Member
  • 5 posts

0
Neutral

Posted 16 November 2018 - 11:57

My plugins are not updated. In opkg registered links through which are not updated. Maybe new feeds for updates?
About the encoding, I asked only the opportunity to add a driver to dvb as done in the vu solo?

Re: Howto build unofficial pli for your unsupported receiver #2642 athart

  • New Member
  • 3 posts

0
Neutral

Posted 16 November 2018 - 17:04

OpenPLi 7 has arrived

Re: Howto build unofficial pli for your unsupported receiver #2643 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 16 November 2018 - 18:15

OpenPLi 7 has arrived

 

No, it hasn't.


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: Howto build unofficial pli for your unsupported receiver #2644 keos66

  • Member
  • 14 posts

0
Neutral

Posted 16 November 2018 - 20:24

 nope I mean the yellow loading bar graphics on the box little display,  after power on the the box tv show first boot picture and the yellow loading start to appear on the little display and stop after 50% loading and then noting more happening.

 

not possible to access from telnet/network think it hangs when loading the kernel

 

 

 

have make my first images and it says it was ok but have the the same results as Persian Prince - openpli-enigma2-pli-extras-dm800sev2_nfi, from 29/08 20018 is still freeze after ca  50% first boot loading.

someone have a god idea to find out way, is it possible to use usb service port to access  live kernel output?

 

Do you mean the 'progress bar' Enigma2 at startup? In that case it's probably not a kernel problem.

 

Check working telnet and FTP.

 

In case telnet is working, do:

init 4
ENIGMA_DEBUG_LVL=4 enigma2

And post output.

 


Re: Howto build unofficial pli for your unsupported receiver #2645 keos66

  • Member
  • 14 posts

0
Neutral

Posted 16 November 2018 - 20:31

 

Do you have an original dm800sev2 or a clone?

 

Orginal DM800seV2

 

 

This is way i try to find/build a working newer Pli images, if I have a clone boxes its lots of alternatives out there but for us with original boxes not so much chance to find a clean good images


Re: Howto build unofficial pli for your unsupported receiver #2646 ycf83

  • Senior Member
  • 53 posts

+2
Neutral

Posted 16 November 2018 - 21:41

hi all,

meta-webserver    = "HEAD:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
meta              = "HEAD:93dd2f9f3edf0584f9e806c629611d645dd72dbf"
meta-openpli      = "develop:e3c5d2f4c8c55e5321734e34516938bb22c502df"
meta-vuplus       = "HEAD:80d6038d7293cda9e1081052c01f5a5950405a10"
meta-xsarius.pli5 = "HEAD:e7672c2c5832180f49b429a52db095e039d23437"
meta-qviart       = "HEAD:9f2aa786cb7e6c93a285fb08bb85e5e947e6fb9a"
meta-xp           = "HEAD:b37b33a53422b822a89bea2ca1696ab72320674a"
meta-xtrend       = "HEAD:c964b8124d98e9e07f68a87ae294056f2f7f23c6"
meta-formuler     = "HEAD:e1d33c48edb119dcc3163855b0b1af510912ef52"
meta-gfutures     = "HEAD:dc85817308d6e140969b2736cb7d53d4bb46271a"
meta-xpeedc       = "HEAD:f12908a5573de8a6a06ad9f75081846a590511c4"
meta-zgemma       = "HEAD:f702fd1487909a2cced97c6d0339b8b67c2a7e1d"
meta-edision      = "HEAD:10331fd35051638029120cd92d24d3fdea577ce0"
meta-miraclebox   = "HEAD:d44871d4d1f357d5b38488ed505b48fa8c8feff3"
meta-spycat       = "HEAD:a19f11bbcdcad969e9f6f8d2c30df0653427d4cb"
meta-gi           = "HEAD:01fd1e8256f53d40371e65514e13a53ef53e400d"
meta-sab          = "HEAD:92262feb14e4005c8096150daac7313e9cb3d85a"
meta-gigablue     = "HEAD:3fb1f863c14047a7ac38fc9f7e1f30c6e03fc908"
meta-amiko        = "HEAD:b6416ddfc6130265e0b3054d144b96b59fdf7a03"
meta-axasuhd      = "HEAD:dfc1465665f504fdc4d6fc9a401e630b04123211"
meta-local        = "develop:e3c5d2f4c8c55e5321734e34516938bb22c502df"
meta-qt5          = "HEAD:c6aa602d0640040b470ee81de39726276ddc0ea3"
meta-ax           = "HEAD:d05194b8f2794de8ca1f03851a7fde1400db8ffc"
meta-azbox        = "HEAD:04ffbdd0afc7da134fb620f9edb5c56eb1607a18"
meta-blackbox     = "HEAD:ef54a26c8be6fe135dad54deb7f1421dfc475fbc"
meta-broadmedia   = "HEAD:c2e7ba19cf2454211cfd5dcb87697f579e11cf37"
meta-ceryon       = "HEAD:72a7570c224d9ae76864f44e0b3f9944197eeb34"
meta-clap         = "HEAD:06b2d9f9371073e6f91396ac350c228cad88ecb6"
meta-cube         = "HEAD:36a80488ab79fc61ae7dd8fb05e9ecf4c011a299"
meta-dags         = "HEAD:976a406f8e1e18e56f813127f9a044388a7c8f67"
meta-dinobot      = "HEAD:aa29916673104972161fa6294d63280623f28035"
meta-dream        = "HEAD:30aefb0a4bdc6507c307b0aff081f9b094ab16e0"
meta-ebox         = "HEAD:c171db6798e9d9a3c472ca1ce3878852022e1404"
meta-entwopia     = "HEAD:c43d8cb480fc2569995ba665810837580a6b30ba"
meta-fulan        = "HEAD:472086894eecd2cdd33817fd09319e0c182c2fb1"
meta-gb           = "HEAD:2e5acf294b78e208c71b7bfcc6a4ef536eef6784"
meta-hypercube    = "HEAD:aa135c99576a949d5f0c9ed2e289fec48f597781"
meta-ini          = "HEAD:8b33da9634aec53321f426cedd6d0f679f1972ab"
meta-ixuss        = "HEAD:850369eb5dd914410ac43e783c4147492f2af3b3"
meta-linkdroid    = "HEAD:397620d1bc765406dc039e9ba7174683aaef73c4"
meta-minix        = "HEAD:523180976e3eb73def124971c43d1f47e664b41e"
meta-octagon      = "HEAD:9cf5fd5e42a27cdd35e6be5df04ed6d849bd8d14"
meta-odin         = "HEAD:61e888e1df903a77ad181ee02b960263322826a5"
meta-odroid       = "HEAD:839fd7cc211bc97ace3140942d3e9e29a0f6a745"
meta-protek       = "HEAD:c7e6f9640bbf9e8a0c9a2a15d1cc2c71c4806a05"
meta-raspberrypi  = "HEAD:20e719195297e02be722e892cee4e18b63d04f22"
meta-tiviar       = "HEAD:1eb5a8ebf58f6c09fbaee14d01ee77f63bc2f871"
meta-tripledot    = "HEAD:92207d30300c653249849fe761419f352480b938"
meta-uclan        = "HEAD:45efffcdd6c4377e6b81ec0517a2b27545874c06"
meta-wetek        = "HEAD:9243173dfd8508c675ca64fab3a14d074356b2ba"
meta-xcore        = "HEAD:de404ff2e713398067b734f184c198a3cf5f0a4a"
meta-xt           = "HEAD:d449885f319ae7f8f580db0c84a46eaed0f8c0b6"
pli-extras        = "develop:be3950395f3d4270e13dbe1aa3a4cdec58b319d7"

Initialising tasks: 100% |#######################################################################################################################################################################################| Time: 0:00:27
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: enigma2-plugin-systemplugins-crossepg-0.8.6+gitrAUTOINC+cfc0403c5b-r0 do_package_qa: QA Issue: enigma2-plugin-systemplugins-crossepg: found library in wrong location: /usr/crossepg/libcrossepg.so [libdir]
ERROR: rtl8812au-5.1.5-r0 do_compile: oe_runmake failed
ERROR: rtl8812au-5.1.5-r0 do_compile: Function failed: do_compile (log file is located at /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/temp/log.do_compile.26278)
ERROR: Logfile of failure stored in: /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/temp/log.do_compile.26278
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 LINUX_SRC=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source KDIR=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source M={D}/lib/modules/3.2-dm500hd/kernel/drivers/net/wireless KERNEL_SOURCE=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source LINUX_SRC=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source KDIR=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source KERNDIR=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source KSRC=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source KERNEL_VERSION=3.2-dm500hd KVER=3.2-dm500hd CC=mipsel-oe-linux-gcc  -fuse-ld=bfd AR=mipsel-oe-linux-ar  LD=mipsel-oe-linux-ld.bfd
| make ARCH=mips CROSS_COMPILE=mipsel-oe-linux- -C /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source M=/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU  modules
| make[1]: Entering directory '/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source'
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_cmd.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_security.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_debug.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_io.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_ioctl_query.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_ioctl_set.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_ieee80211.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_mlme.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_mlme_ext.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_mi.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_wlan_util.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_vht.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_pwrctrl.o
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_wlan_util.c:1230:2: warning: '_exit_critical_bh' is static but used in inline function 'rtw_sec_camid_is_used' which is not static
|   _exit_critical_bh(&cam_ctl->lock, &irqL);
|   ^~~~~~~~~~~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_wlan_util.c:1228:2: warning: '_enter_critical_bh' is static but used in inline function 'rtw_sec_camid_is_used' which is not static
|   _enter_critical_bh(&cam_ctl->lock, &irqL);
|   ^~~~~~~~~~~~~~~~~~
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_rf.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_recv.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_ap.o
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.c:64:2: warning: '_exit_critical_bh' is static but used in inline function 'rtw_st_ctl_clear_tracker_q' which is not static
|   _exit_critical_bh(&st_ctl->tracker_q.lock, &irqL);
|   ^~~~~~~~~~~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.c:61:3: warning: 'rtw_list_delete' is static but used in inline function 'rtw_st_ctl_clear_tracker_q' which is not static
|    rtw_list_delete(&st->list);
|    ^~~~~~~~~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.c:60:11: warning: 'get_next' is static but used in inline function 'rtw_st_ctl_clear_tracker_q' which is not static
|    plist = get_next(plist);
|            ^~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.c:57:10: warning: 'get_next' is static but used in inline function 'rtw_st_ctl_clear_tracker_q' which is not static
|   plist = get_next(phead);
|           ^~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sta_mgt.c:55:2: warning: '_enter_critical_bh' is static but used in inline function 'rtw_st_ctl_clear_tracker_q' which is not static
|   _enter_critical_bh(&st_ctl->tracker_q.lock, &irqL);
|   ^~~~~~~~~~~~~~~~~~
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_xmit.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_p2p.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_tdls.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_br_ext.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_iol.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_sreset.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_btcoex.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_beamforming.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/rtw_odm.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/core/efuse/rtw_efuse.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/osdep_service.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/os_intfs.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/usb_intf.o
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/os_intfs.c:668:37: warning: 'rtw_excl_chs' is static but used in inline function 'rtw_regsty_load_excl_chs' which is not static
|     regsty->excl_chs[ch_num++] = (u8)rtw_excl_chs[i];
|                                      ^~~~~~~~~~~~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/os_intfs.c:667:12: warning: 'rtw_excl_chs' is static but used in inline function 'rtw_regsty_load_excl_chs' which is not static
|    if (((u8)rtw_excl_chs[i]) != 0)
|             ^~~~~~~~~~~~
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/usb_ops_linux.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_linux.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/xmit_linux.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/mlme_linux.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/recv_linux.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/rtw_cfgvendor.o
|   CC [M]  /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/wifi_regd.o
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.c:6076:68: warning: 'struct ieee80211_sta_vht_cap' declared inside parameter list will not be visible outside of this definition or declaration
|  static void rtw_cfg80211_init_vht_capab(_adapter *padapter, struct ieee80211_sta_vht_cap *vht_cap, u8 rf_type)
|                                                                     ^~~~~~~~~~~~~~~~~~~~~
| ERROR: oe_runmake failed
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.c: In function 'rtw_cfg80211_init_vht_capab':
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.c:6085:9: error: dereferencing pointer to incomplete type 'struct ieee80211_sta_vht_cap'
|   vht_cap->vht_supported = _TRUE;
|          ^~
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.c: In function 'rtw_cfg80211_init_wiphy':
| /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.c:6211:48: error: 'struct ieee80211_supported_band' has no member named 'vht_cap'; did you mean 'ht_cap'?
|     rtw_cfg80211_init_vht_capab(padapter, &bands->vht_cap, rf_type);
|                                                 ^~
| make[3]: *** [/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source/scripts/Makefile.build:305: /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU/os_dep/linux/ioctl_cfg80211.o] Error 1
| make[3]: *** Waiting for unfinished jobs....
| make[2]: *** [/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source/Makefile:1367: _module_/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/rtl8812AU] Error 2
| make[1]: *** [Makefile:130: sub-make] Error 2
| make[1]: Leaving directory '/home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work-shared/dm500hd/kernel-source'
| make: *** [Makefile:1838: modules] Error 2
| WARNING: /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/temp/run.do_compile.26278:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /home/d-ina/OpenPLI/openpli-oe-core/build/tmp/work/dm500hd-oe-linux/rtl8812au/5.1.5-r0/temp/log.do_compile.26278)
ERROR: Task (/home/d-ina/OpenPLI/openpli-oe-core/meta-openpli/recipes-connectivity/realtek/rtl8812au_5.1.5.bb:do_compile) failed with exit code '1'

 


Re: Howto build unofficial pli for your unsupported receiver #2647 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 16 November 2018 - 21:51

Not supported on a 2.x kernel. There is a reason why we dumped those old 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: Howto build unofficial pli for your unsupported receiver #2648 keos66

  • Member
  • 14 posts

0
Neutral

Posted 17 November 2018 - 00:20

Not supported on a 2.x kernel. There is a reason why we dumped those old boxes.

 

You keep saying this type of words... but please tell me why is our old boxes with it´s antique kernel and low memory still supported on this build list and this forum area

If support now changed and stopped maybe time edit this build script and remove this boxes. For now, at least, I think it works to us it.

 

This is the list we support so far:

 

Dreambox:

  • DM7020HD
  • DM7020HD V2
  • DM7080
  • DM800
  • DM800Se
  • DM800Se V2
  • DM8000
  • DM500HD
  • DM500HD V2
  • DM520
  • DM820
  • DM900
  • DM920

Re: Howto build unofficial pli for your unsupported receiver #2649 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 17 November 2018 - 05:45

@keos66: read the subject of the topic:
‘Howto build unofficial pli for your unsupported receiver’.
This is a third party, based on Openpli homebuild images.

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz

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

  • PLi® Contributor
  • 1,604 posts

+203
Excellent

Posted 17 November 2018 - 09:15

@ycf83

 

Update and try again.

https://github.com/P...c10a13478994890

 

@keos66

Update and try again.

https://github.com/P...c6576e75769c765

 

Since other boxes with kernel 3.2 have no boot problem, is a wrong defconfig most likely the problem.

This is at least i can try, you never known.


Edited by Beeker, 17 November 2018 - 09:16.

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 #2651 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 17 November 2018 - 10:04

openpli-enigma2-pli-extras-dm900_web
openpli-enigma2-pli-extras-dm920_web
https://www.online.e...87-59bc757eccb6
17.11.2018 morning build. The online update works as well.

 

Thanks all involved! :)


DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz

Re: Howto build unofficial pli for your unsupported receiver #2652 keos66

  • Member
  • 14 posts

0
Neutral

Posted 17 November 2018 - 16:00

@keos66: read the subject of the topic:
‘Howto build unofficial pli for your unsupported receiver’.
This is a third party, based on Openpli homebuild images.

 

 

Knowing openpli does not support this old boxes anymore officially, But what I wrote it only applies to this forum thread and the whole idea of it.


Re: Howto build unofficial pli for your unsupported receiver #2653 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 17 November 2018 - 16:05

You keep saying this type of words... but please tell me why is our old boxes with it´s antique kernel and low memory still supported on this build list and this forum area

 

Something seriously wrong with your eyes. We only support the DM8000 at the moment (see https://openpli.org/download/dreambox/) and that is only as long as it still builds.


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: Howto build unofficial pli for your unsupported receiver #2654 keos66

  • Member
  • 14 posts

0
Neutral

Posted 17 November 2018 - 16:08

Thanks for this help Beeker. It is greatly appreciated, I try again now

 

@ycf83

 

Update and try again.

https://github.com/P...c10a13478994890

 

@keos66

Update and try again.

https://github.com/P...c6576e75769c765

 

Since other boxes with kernel 3.2 have no boot problem, is a wrong defconfig most likely the problem.

This is at least i can try, you never known.


Re: Howto build unofficial pli for your unsupported receiver #2655 keos66

  • Member
  • 14 posts

0
Neutral

Posted 17 November 2018 - 16:17

Possibly it's wrong with my eyes, but I also do not claim that PLI officially support it either, just that THIS forum thread suggests that there is a 3djepart support and that's I want to work on my box and it clearly says it's supported for this kind of images to build yourself.

 

 

You keep saying this type of words... but please tell me why is our old boxes with it´s antique kernel and low memory still supported on this build list and this forum area

 

Something seriously wrong with your eyes. We only support the DM8000 at the moment (see https://openpli.org/download/dreambox/) and that is only as long as it still builds.

 


Re: Howto build unofficial pli for your unsupported receiver #2656 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 17 November 2018 - 16:23

This forum doesn't suggest anything.

 

OpenPLi is open source, so it is free for anyone to use it, and that includes on hardware we don't support. The only thing not allowed is call the result OpenPLi, as we own that name (which is heavily violated by that fake pli site with DMM images!). 

 

In this topic there are people that have created meta layers for hardware we don't support, so you can build your own image based on OpenPLi with their meta layers.

 

Neither we, nor they, provide support on such an image, if an image is available (they seem to post test images every now and then, presumably because they don't own the hardware), it is provided as is.


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: Howto build unofficial pli for your unsupported receiver #2657 ycf83

  • Senior Member
  • 53 posts

+2
Neutral

Posted 17 November 2018 - 16:32

@ycf83

 

Update and try again.

https://github.com/P...c10a13478994890

 

@keos66

Update and try again.

https://github.com/P...c6576e75769c765

 

Since other boxes with kernel 3.2 have no boot problem, is a wrong defconfig most likely the problem.

This is at least i can try, you never known.

 

 

thnk's for your great job bro, all okayy for me .


Re: Howto build unofficial pli for your unsupported receiver #2658 keos66

  • Member
  • 14 posts

0
Neutral

Posted 17 November 2018 - 16:52

Already know all that, and now you know i know it to. Can we please move on now so we might find a solution to my homebuild images work ok

This forum doesn't suggest anything.

 

OpenPLi is open source, so it is free for anyone to use it, and that includes on hardware we don't support. The only thing not allowed is call the result OpenPLi, as we own that name (which is heavily violated by that fake pli site with DMM images!). 

 

In this topic there are people that have created meta layers for hardware we don't support, so you can build your own image based on OpenPLi with their meta layers.

 

Neither we, nor they, provide support on such an image, if an image is available (they seem to post test images every now and then, presumably because they don't own the hardware), it is provided as is.


Re: Howto build unofficial pli for your unsupported receiver #2659 bzoli72

  • Member
  • 9 posts

0
Neutral

Posted 17 November 2018 - 16:57

Hi zeros!

How to use hbbtv in this image?
HBBTv plugin not found in plugin list.

 

Thanks: bzoli72

openpli-enigma2-pli-extras-dm900_web
openpli-enigma2-pli-extras-dm920_web
https://www.online.e...87-59bc757eccb6
17.11.2018 morning build. The online update works as well.

 

Thanks all involved! :)


Re: Howto build unofficial pli for your unsupported receiver #2660 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 17 November 2018 - 18:13

Already know all that, and now you know i know it to. Can we please move on now so we might find a solution to my homebuild images work ol

 

And my point is that there is no support to get there. You may get a response from another home builder, but that it about it. Or maybe not.

 

If the people behind pli-metas decide that want to start providing end-user support, then it's time for them to setup their own forum. We're not in the business of sponsoring non-official OpenPLi builds...


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.

Back to [EN] Third-Party Development

2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users

  1. Forums
  2. → PLi® Development
  3. → [EN] Third-Party Development