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 #2201 zildan

  • Member
  • 13 posts

+1
Neutral

Posted 17 August 2018 - 19:45

Thanks for your effort again, still stuck with the blue LED and logo on the screen.

Attached Files



Re: Howto build unofficial pli for your unsupported receiver #2202 kubi

  • Senior Member
  • 30 posts

+7
Neutral

Posted 17 August 2018 - 22:58

guard77, yes is not saved


Edited by kubi, 17 August 2018 - 23:01.

dm900 (triple tuner si2169c)


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

  • PLi® Contributor
  • 1,602 posts

+203
Excellent

Posted 18 August 2018 - 10:14

Yes indeed.

The problem is, the /etc/resolv.conf file is blanc after a reboot when DHCP is disabled.

 

I tried some changes to Busybox, but no luck so far.


Edited by Beeker, 18 August 2018 - 10:17.

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 #2204 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 18 August 2018 - 10:16

Thanks for your effort again, still stuck with the blue LED and logo on the screen.

Very strange, I used the same kernel, config, and dts that coreelec uses and still you can't boot.

You can boot coreelec without a problem, yes ?



Re: Howto build unofficial pli for your unsupported receiver #2205 zildan

  • Member
  • 13 posts

+1
Neutral

Posted 18 August 2018 - 10:20

With LibreELEC-S912.arm-8.2-8.2.2.3.img boot OK , no RC, only CEC .



Re: Howto build unofficial pli for your unsupported receiver #2206 zildan

  • Member
  • 13 posts

+1
Neutral

Posted 18 August 2018 - 10:26

https://kszaq.libreelec.tv/s912/8.2/



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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 18 August 2018 - 10:33

With LibreELEC-S912.arm-8.2-8.2.2.3.img boot OK , no RC, only CEC .

I suspect the problem is that we use fitimage for booting, and if the initramfs is large it causes these problems.

Maybe we should ditch the fitimage class and either use an Android kernel image like what Coreelec/Libreelec use or use a separate zImage, Uinitrd and dtb file and an aml_autoscript to load them independently.

 

Sadly I don't have time these days to do such a big migration, I will look into it later.

 

Regards



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

  • Senior Member
  • 77 posts

+24
Neutral

Posted 18 August 2018 - 13:02

S912 no OpenGL driver for linux thus at this time dont work with pli. İf Some body adaptive libhybrit driver. May be works or wait dreambox s912 out openatv source

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

  • PLi® Contributor
  • 1,602 posts

+203
Excellent

Posted 18 August 2018 - 13:25

I made a quick workaround for it.

Create a new  'nameserversdns.conf' file with the nameservers IP's.

And use that file when DHCP is disabled.

Actually it should use settings.xml to store the nameservers, but let's test this first.

 

Upload network.py to:

/usr/lib/enigma2/python/Components/

And restart enigma2.

 

This is the patch:

diff --git a/lib/python/Components/Network.py b/lib/python/Components/Network.py
index 34b8d7bf2..48a02538f 100644
--- a/lib/python/Components/Network.py
+++ b/lib/python/Components/Network.py
@@ -164,6 +164,10 @@ class Network:
 		for nameserver in self.nameservers:
 			fp.write("nameserver %d.%d.%d.%d\n" % tuple(nameserver))
 		fp.close()
+		fp = file('/etc/nameserversdns.conf', 'w')
+		for nameserver in self.nameservers:
+			fp.write("nameserver %d.%d.%d.%d\n" % tuple(nameserver))
+		fp.close()
 
 	def loadNetworkConfig(self,iface,callback = None):
 		interfaces = []
@@ -216,7 +220,13 @@ class Network:
 			# save configured interfacelist
 			self.configuredNetworkAdapters = self.configuredInterfaces
 			# load ns only once
-			self.loadNameserverConfig()
+			if ifaces[currif]["dhcp"] == True:
+				nameserverfilename = "/etc/resolv.conf"
+				self.loadNameserverConfig(nameserverfilename)
+			else:
+				nameserverfilename = "/etc/nameserversdns.conf"
+				self.loadNameserverConfig(nameserverfilename)
+				self.writeNameserverConfig()
 			print "read configured interface:", ifaces
 			print "self.ifaces after loading:", self.ifaces
 			self.config_ready = True
@@ -224,14 +234,14 @@ class Network:
 			if callback is not None:
 				callback(True)
 
-	def loadNameserverConfig(self):
+	def loadNameserverConfig(self, nameserverfilename):
 		ipRegexp = "[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}"
 		nameserverPattern = re.compile("nameserver +" + ipRegexp)
 		ipPattern = re.compile(ipRegexp)
 
 		resolv = []
 		try:
-			fp = file('/etc/resolv.conf', 'r')
+			fp = file(nameserverfilename, 'r')
 			resolv = fp.readlines()
 			fp.close()
 			self.nameservers = []

Attached Files


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 #2210 kubi

  • Senior Member
  • 30 posts

+7
Neutral

Posted 19 August 2018 - 00:03

now everything is fine, DNS is saved


dm900 (triple tuner si2169c)


Re: Howto build unofficial pli for your unsupported receiver #2211 boyz74

  • New Member
  • 2 posts

0
Neutral

Posted 19 August 2018 - 04:08

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "ubuntu-18.04"
TARGET_SYS        = "mipsel-oe-linux"
MACHINE           = "azboxme"
DISTRO            = "openpli"
DISTRO_VERSION    = "pli-extras"
TUNE_FEATURES     = "o32 fpu-hard mips32"
TARGET_FPU        = ""
meta-oe           
meta-filesystems  
meta-multimedia   
meta-networking   
meta-python       
meta-webserver    = "HEAD:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
meta              = "HEAD:93dd2f9f3edf0584f9e806c629611d645dd72dbf"
meta-openpli      = "develop:312916ba1a03ff73e8a1e6869684718d7822336b"
meta-vuplus       = "HEAD:d6f0477dc48bad742290f588efd4d9da604cfb29"
meta-xsarius.pli5 = "HEAD:306a17cf01ab85df09d7cfbf2bda2e8d21d50e1d"
meta-qviart       = "HEAD:8da348c2596ec2d5d1d67fe0bfd115671f5e4a9c"
meta-xp           = "HEAD:2f818d2ee1efbf0a4536d8384d716a0767cf7039"
meta-xtrend       = "HEAD:ac054abbe235f33f6a69e7a8ff0fa9a7efa84f59"
meta-formuler     = "HEAD:e1d33c48edb119dcc3163855b0b1af510912ef52"
meta-gfutures     = "HEAD:4015ce2bb7c46cd10574eff3100f67fb74c38bda"
meta-xpeedc       = "HEAD:f12908a5573de8a6a06ad9f75081846a590511c4"
meta-zgemma       = "HEAD:9c0ae72060437fb6951f82e64f1e0e882cf00f95"
meta-edision      = "HEAD:7af176f81a7aca30200d6958229d56c973cee393"
meta-miraclebox   = "HEAD:d44871d4d1f357d5b38488ed505b48fa8c8feff3"
meta-spycat       = "HEAD:a19f11bbcdcad969e9f6f8d2c30df0653427d4cb"
meta-gi           = "HEAD:01fd1e8256f53d40371e65514e13a53ef53e400d"
meta-sab          = "HEAD:92262feb14e4005c8096150daac7313e9cb3d85a"
meta-gigablue     = "HEAD:7e437da8e19274143229f2c52e62917cb33d9d1c"
meta-amiko        = "HEAD:eb5c966a3ba38388abdcda61ed07fb056e4d488b"
meta-axasuhd      = "HEAD:dfc1465665f504fdc4d6fc9a401e630b04123211"
meta-local        = "develop:312916ba1a03ff73e8a1e6869684718d7822336b"
meta-qt5          = "HEAD:c6aa602d0640040b470ee81de39726276ddc0ea3"
meta-amlogic      = "HEAD:2a004002048aab5a2df290554b696d3e7f023187"
meta-ax           = "HEAD:1d852b4eca365ed4560643cb2e3cba09a78a3d49"
meta-azbox        = "HEAD:df30c02b07f55c3b89e7b5808eb7aa126613423f"
meta-blackbox     = "HEAD:1ac8f7ff34539dba46212e195ca1425bf093466d"
meta-ceryon       = "HEAD:2f5d5982b1cce64600bb243790cff32d9e2ab57e"
meta-cube         = "HEAD:a391b50516232375048ecfcd8f9721e495d644c5"
meta-dags         = "HEAD:cee1d8c7e6f7d77ddec9f5fb7109938cc73a5449"
meta-dinobot      = "HEAD:7c74f262ff0e905f6edc917c0f970c77bb4250ed"
meta-dream        = "HEAD:238becab0268e0ca3343ea5d31ddb703ddc43e02"
meta-ebox         = "HEAD:7a4224974eb65e38ab4282831b7f37a0bd62ca3c"
meta-entwopia     = "HEAD:ea01aaff38031cc004c22ea4f57a5cbb0eadf311"
meta-fulan        = "HEAD:467fdad58e78f4258c9882ef95ee73774fabbed6"
meta-ini          = "HEAD:0fb405af5fc10ff23303d165012bddf66abed5c4"
meta-ixuss        = "HEAD:a5b6ab5c51a7e26c1d70fc6858304d73d3720432"
meta-octagon      = "HEAD:e9afb14d9cc978df98efcb04993c5900e1e88748"
meta-odin         = "HEAD:8e974d345b73a2067bf6ce22e753d8868796ab1c"
meta-protek       = "HEAD:65922f91045c2f62dd93e92fe38d1f32382c3401"
meta-raspberrypi  = "HEAD:be56334094a7c9bd570877ba2e6b3328b8b13d45"
meta-tiviar       = "HEAD:730f89b8bded4089a24e70a9992082c2811cb0d4"
meta-tripledot    = "HEAD:301f4a086d9e365362bc71715d2bf6d953927568"
meta-xcore        = "HEAD:3ed7062f5a476798a0bcbc6f3a472c26b5e44762"
pli-extras        = "develop:d478b126acec60575bd0127bbb0d3cd9bdb2f2af"

Initialising tasks: 100% |#######################################| Time: 0:00:48
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: openpli-enigma2-image-1.0-r0 do_image_jffs2: Function failed: do_image_jffs2 (log file is located at /home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_jffs2.26037)
ERROR: Logfile of failure stored in: /home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_jffs2.26037
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_jffs2
| mkfs.jffs2: error!: root directory specified more than once
| WARNING: /home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/temp/run.do_image_jffs2.26037:1 exit 255 from 'mkfs.jffs2 --root=/home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/rootfs --faketime --output=/home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/deploy-openpli-enigma2-image-image-complete/openpli-enigma2-pli-extras-azboxme.rootfs.jffs2 -p 0x800 -e 0x20000 -n -lrm -f /home/carlos/openpli-oe-core/build/tmp/deploy/images/azboxme/*.bin'
| ERROR: Function failed: do_image_jffs2 (log file is located at /home/carlos/openpli-oe-core/build/tmp/work/azboxme-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_jffs2.26037)
ERROR: Task (/home/carlos/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_jffs2) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5522 tasks of which 5504 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/carlos/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_jffs2
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
carlos@carlos-desktop:~/openpli-oe-core/build$
 

 

Help.????



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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 19 August 2018 - 12:41

Thanks for your effort again, still stuck with the blue LED and logo on the screen.

OK to test if the problem is with the fitimage class I prepared boot files for the k3pro as separate files.

since you have a Uart connection I didn't bother to create update script for the bootloader as we are only testing, so I will give you the steps to test using Uart.

First delete all the files in the first partition of your sdcard (kernel.itb) and put the files in the following zip instead

https://drive.google...pZy9bhMzLJga_jT

then connect your Uart cable and open the application you use for Uart (e.g Putty) and make sure you can write and execute commands in it.

reboot the device(while the sd card is out) and while the cursor in putty keep pressing the enter key to stop autoboot until you get a command prompt like this

Hit any key to stop autoboot:  0 
gxb_p20x#
gxb_p20x#

of course the "gxbb_p20x" will be different for your box, now you need to enter this command to reset you u-boot environment

defenv;sleep 1; saveenv;reboot

the device will reboot, now insert the sdcard(with the new files) and reboot, also stop autoboot by pressing any key repeatedly.

when you get the u-boot prompt again enter this command to boot into openpli and paste the log:

fatload mmc 0 ${loadaddr} s905_autoscript;autoscr ${loadaddr}


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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 19 August 2018 - 12:43

S912 no OpenGL driver for linux thus at this time dont work with pli. İf Some body adaptive libhybrit driver. May be works or wait dreambox s912 out openatv source

I don't think enigma2 requires OpenGL, OpenGL is used for kodi, Also what dreambox s912 are you talking about?



Re: Howto build unofficial pli for your unsupported receiver #2214 zildan

  • Member
  • 13 posts

+1
Neutral

Posted 19 August 2018 - 15:34

[    2.675397@0] c11084c0.serial: ttyS1 at MMIO 0xc11084c0 (irq = 58, base_baud = 1500000) is a meson_uart
[    2.685579@0] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: d0078000, ctrl: 0
[    2.793438@2] dwc_otg: Core Release: 3.10a
[    2.793473@2] dwc_otg: Setting default values for core params
[    2.797643@2] dwc_otg: curmode: 0, host_only: 0
[    2.813535@2] WARN::dwc_otg_core_reset:5150: dwc_otg_core_reset() HANG! Soft Reset GRSTCTL=80000001
[    2.813535@2] 
[    2.830880@2] WARN::dwc_otg_core_reset:5150: dwc_otg_core_reset() HANG! Soft Reset GRSTCTL=80000001
[    2.830880@2] 
[    2.846928@2] dwc_otg: Using Buffer DMA mode
[    2.846949@2] dwc_otg: OTG VER PARAM: 1, OTG VER FLAG: 1
[    2.850819@2] dwc_otg: Working on port type = SLAVE
[    2.855706@2] dwc_otg: Dedicated Tx FIFOs mode

Thanks for your effort again, still stuck with the blue LED and logo on the screen :(

Full log in atasament, with android log after

 

defenv;sleep 1; saveenv;reboot

 

 

Attached Files



Re: Howto build unofficial pli for your unsupported receiver #2215 sauna

  • Senior Member
  • 38 posts

0
Neutral

Posted 19 August 2018 - 17:49

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file



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

  • Senior Member
  • 77 posts

+24
Neutral

Posted 19 August 2018 - 18:09

:)
Look bb files
https://github.com/o...amlogic_r6p1.bb

https://github.com/o...amlogic_r4p1.bb
https://github.com/o...amlogic_r4p1.bb

S905 d w series use mali450 opengl driver for GUI
enigma need OpenGL driver for GUI( no need opengl video hw acceleration)
No puplic S912 linux fb t820 DRİVER
S912 use android mali t820 drivers

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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 19 August 2018 - 19:09

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file

You probably had a different issue, zildan's device is not even loading the initramfs



Re: Howto build unofficial pli for your unsupported receiver #2218 sauna

  • Senior Member
  • 38 posts

0
Neutral

Posted 19 August 2018 - 20:16

Well, yes. my message to the user starz wanted. he has k1plus.but who after boot black screen can try.



Re: Howto build unofficial pli for your unsupported receiver #2219 starz

  • Senior Member
  • 59 posts

+1
Neutral

Posted 19 August 2018 - 21:34

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file

 

 

 

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file

You probably had a different issue, zildan's device is not even loading the initramfs

 

 

 

Well, yes. my message to the user starz wanted. he has k1plus.but who after boot black screen can try.

Thanks dear sauna.I've looked into the files that you've given. "aaa" and "amlsetfb" files are from linkdroid-amlsetfb therefore it boots normally.I've already writen about it before and fixed black screen issue with using linkdroid-amlsetfb(and made some fix about resulation) on building.there's no problem with it. the problem is with mecool-amlsetfb.I'm trying to fix mecool-amlsetfb on k1plus because dear moham96 says "don't use linkdroid-amlsetfb" cause of some problems that I don't remember now.I was busy last week and couldn't dig in it.thanks a lot.

 

Regards.



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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 20 August 2018 - 05:56

 

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file

 

 

 

I already wrote about dark cskren on k1plus.so probably no one understood what the translator was translating what I wanted to say.you need these files to make a replacement and k1plus will load ok.you need to look for the boot problem in these files.replace all at once.

 

http://www.mediafire...6/init.zip/file

You probably had a different issue, zildan's device is not even loading the initramfs

 

 

 

Well, yes. my message to the user starz wanted. he has k1plus.but who after boot black screen can try.

Thanks dear sauna.I've looked into the files that you've given. "aaa" and "amlsetfb" files are from linkdroid-amlsetfb therefore it boots normally.I've already writen about it before and fixed black screen issue with using linkdroid-amlsetfb(and made some fix about resulation) on building.there's no problem with it. the problem is with mecool-amlsetfb.I'm trying to fix mecool-amlsetfb on k1plus because dear moham96 says "don't use linkdroid-amlsetfb" cause of some problems that I don't remember now.I was busy last week and couldn't dig in it.thanks a lot.

 

Regards.

 

Last night I faced a simillar problem where the screen didn't detect the hdmi from the tvbox, turns out the problem was that the bootloader was overriding the resolution we set in the mecoll-amlsetfb script. I've updated the script to use the hardcoded resolution instead of the one provided by the bootloader.

update and build again. and play with the resolution values ( my screen had problems when usin 50hz and I had to use 60hz to get it to work )

 

Regards




6 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users


    Bing (1)