How can i extract this
You need to log in to the box via SSH, and run the above command.
Other solutions: https://wiki.libreelec.tv/support/log-files
Posts by dtech
-
-
Hi, IR controller is OK, tunner does not work, tvheadend not recognizing it, neither i see the libreelec drivers pack that other builds come within.
Please send a link from dmesg | paste. I can't help without the log.
-
So if i try to install this image, the univesall n200 and something is going wrong, can I install again the old image to my mxiii-g tv box ?
This two images differ only in the wifi interface and the remote control configuration, so it will work for sure without any boot problem.
And this will definitely solve your wifi problem as well. All you have to do is set up the remote control via SSH:
Codecd /storage/.config/ wget https://github.com/dtechsrv/LibreELEC-AML/raw/master/projects/S8X2/devices/MXIII-Plus/filesystem/etc/amremote/remote.conf rebootBut of course by answering your question: Yes, you can restore safely to the original MXIII-G image.
-
Thanks, I am testing it, at the moment, IR controller does not work and i can not see the dvb tunner on the tvheandend configuration interface, is there any driver or file that i have to installa with the image?
I would like you to attach any log file next time, e.g. dmesg | paste.
Round #2: http://libreelec.dtech.hu/snapshots/20220503/
Maybe I have managed to solve the problem of the remote control and the tuner as well.
Previously, I thought it was also RF, like WP1 and Core, but instead it was infrared. The tuner was a bit more complicated, so I can only hope this works. Please test this new image.
-
Hi dtech,
thank you very much for your answer and support. Attached the complete log. I really hope it is possible to find the problem....
Commit: Fix building gold with gcc 10
But, I would recommend using older Ubuntu for LE9.x builds. I used Debian for my builds, so I can't propose a specific version of Ubuntu.
-
Which image do you use on your box, the MXIII-Plus or the Universal-n200?
Code: dmesg[ 20.491487@1] F1 signature read @0x18000000=0x16044330 [ 20.494313@1] F1 signature OK, socitype:0x1 chip:0x4330 rev:0x4 pkg:0x0Based on your previous dmesg, you have an AP6330 wifi chip, so wifi can only work with the Universal-n200-S812_2G-AP6330 image.
Please give it a try if you are using the MXIII-Plus image now, because it is 99% that it will work afterwards.
The situation was the same here: #471, and the answer (with installing the remote control config): #472.
Please try this snapshot image: http://libreelec.dtech.hu/snapshots/20220502/
-
Hello everyone. I have a MXIII-G with libreelec 9.2.8.3 installed. Today I try to connect my TV box with wifi by my smartphone Hotspot but unfortunately I can't see my wifi network to the connections menu. Anyone can help me ?
Unfortunately, there is no solution to most wifi connectivity issues, the wifi drivers integrated into the 3.10/3.14 kernel are obsolete.#500I need to know where can I download the last stable version of your build dtech that supports DVB-S tunner and works from the SD, for my Wetek Play 2. I can not see it in the s905 repository, as it only includes KI and similar receivers.
I didn't create an image for WP2, because unfortunately I don't have such a device. I will try to create an image, but I won't be able to test it.
i tried to build the system for my K1-Pro in Ubuntu 20.04 with g++ 10.3.0 and gcc 10.3.0. Unfortunately it stops with this error.
Unfortunately, a small part of the log is missing that tells which file and which line has the problem.
-
Huge Thanks for that pointer Chewitt !!
Looks like a great starting point for my efforts.
I recommend testing the HD18Q image on a sd card for the first time using the toothpick method on both boxes.
-
I have tried using the upgrade option from my old 8.2RC version to the version 9.2.8.3 and getting the error that hardware is not compatible.
The reason and the solution:
The reason for the incompatibility is that the device name is different.
You need to create an empty .nocompat file next to .tar in the update directory, and try again.
But honestly, I have never tried to update a main version on a box before, so I don't know what will happen, especially with the installed add-ons. I think a new installation is better, but if you try to updade, I definitely recommend a backup.
-
My raspberry pi supports the playback of 3D ISO in frame packing format (3D MVC) inder kodi 18.
Can you tell me if this would also be possible with my KI Pro box?
Unfortunately, I have absolutely no experience in 3D formats, I can't help it on the merits due to the lack of a compatible display.
I am new, and have reveived a OTT TV Box M8S+ with a sticker saying: S805 1G+8G
I tried multiple diffrent image's with the Toothpick method but after the first bootlogo (amlogic 8core, mali 450, ... M8S+) it goes to black screen and stays there..This is a "very" fake M8S+ box and I have one too. My box has this label on the back of the PCB:
This is actually a box called "M8Q" and requires the HD18Q image:
http://libreelec.dtech.hu/S805/LibreELEC-HD18Q.arm-9.2.8.3.img.gz
-
any help?
Unfortunately, I will not be able to help with your tuner and/or demod.
-
I have an old MXQPRO (not the 4k model)...
Unfortunately, this does not tell you exactly what kind of device you have. We didn't really know anything specific, not even the size of the memory or the SoC model.
I have carried out a forced update with the .nocompat option on all 3 images and they do install and run.
Do you mean you have tried the KI-Pro (S905D), KI-Plus (S905) and MXQ Pro 4K 2G (S905X) images? That doesn't make much sense.
It should be tested with another DTB based on SoC and memory size, from here: http://libreelec.dtech.hu/device_trees/
Random updates with ".nocompat" are dangerous, if possible, test on a new SD card first and only update if it is stable on your device.
If you are not using the right DTB, don't be surprised if the system is unstable on your box.
-
I wiped out everything again and started fresh from new git + PROJECT=S905 DEVICE=KI-Plus ARCH=arm make image and make fails at the exact same place
Google can help diagnose compilation issues, because in most cases these are related to the operating system or kernel, possibly gcc, or depends on a not-installed or conflicts with an installed *-dev package on your system. The number of options is quite a lot, so the easiest is to drop the resulting error into Google.
I searched for it too, and this is one of the possible reasons that the libfdt-dev package is installed on your system and conflicts with it. I used Debian 10.10 for the last build and I don't have this package installed.
Edit:
The libfdt-dev package was really causing the problem, but hopefully I was able to fix this issue:
packages/u-boot-tools-aml: fix build issues when libfdt-devel package… · dtechsrv/LibreELEC-AML@463a521… is installedgithub.com -
Build command (it's the only option for s905):
$ PROJECT=S905 ARCH=aarch64 DEVICE=KI-Plus make imageWell, that’s not the "only" option, in fact, it won't work either. Even LE9.0 did not support native 64-bit builds for amlogic devices.
Try this:
Code: cat build.sh | grep KI-PlusPROJECT=S905 DEVICE=KI-Plus ARCH=arm make image -j8 -
Patch applied: packages/kodi: fix scrollable fadelabels if smartredraw is enabled · dtechsrv/LibreELEC-AML@3f92b8a
Please check this snapshot: http://libreelec.dtech.hu/snapshots/20220202/
And the shy question: is it hard to update Leia to Matrix? And the Nexus is coming...
The migration to the mainline kernel is in progress. This is necesary because the code of the old kernels (3.14 and 4.9) is obsolete and it is no longer officially supported by Kodi since v19. The Matrix version will not be released from LibreELEC for Amlogic SoCs, but the Nexus is already in progress:
-
Got it to work by first installing the Libreelec 9.0.2 files from the zip and then upgrading to 9.2.8.
Sorry for the late reply, this is really only possible with this method.
-
Based on the logs, I see you have a clone box with AP6330. The remote control is different for the Uni-n200 and MXIII-Plus and therefore does not work. To install the appropriate remote.conf under the n200 image, follow these steps over SSH:
Codecd /storage/.config/ wget https://github.com/dtechsrv/LibreELEC-AML/raw/master/projects/S8X2/devices/MXIII-Plus/filesystem/etc/amremote/remote.conf rebootAfter the restart, the MXIII-Plus infrared remote control should work.
Comparing the dmesg in the image on the left is the version with the remote control working (MXIII Plus), on the right no (n200), but the external keyboard even if I don't see it at that point works with both.
It is present, but not in these lines.
Code[ 40.381404@3] input: Logitech Unifying Device. Wireless PID:4024 as /devices/lm1/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/input/input3 [ 40.384943@3] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:4024] on usb-lm1-1.2:1By installing everything in the emmc with the script I don't understand why then I find only 4 GB usable.
-
I meanwhile installed your LibreElec fork 9.2.8 on my Wetek Openelec Box (Play 1). It works surprisingly well, but I can "feel" that the device is a bit laggy. But this is nothing new. Compared to my other device (Wetek Play 2), the WP1 is indeed much slower.
Unfortunately, there is a 2-generation distance between the SoCs integrated into WP1 (M6) and WP2 (GXBB), so it is not only in clock speed and number of cores that WP1 lags significantly behind. Not even support for the mainline kernel would change that. As chewitt says, this SoC is unfortunately now obsolete.
- TV Play -> some channels become laggy after a few seconds, not sure yet why, could be because of mutex setting
In the Kodi 18.5, a significant change was made by the author to determine the interlaced signal and frame rate, which unfortunately is not really compatible with amcodec. I solved this with my own patch, but it takes 1-2 seconds after the channel change for the exact frequency to be determined. The lag is probably caused by this method, but without this patch, you had to watch a black screen for about 10 seconds after each channel change.
- Remote Control (official with the device) -> certain buttons needed to be re-configured using the Keymap add-on (e.g. Context Menu, Favourites, Mute button)
I used the official LE remote control keymap, but I found that it is not optimized for the remote control included with the OpenELEC version.
I noticed that the video player does not show the control buttons (stop, play, rewind, forward) and other options (movie info, settings) anymore when I pause the movie. I tried different skins (Amber and Confluence) but the behaviour is the same. Is there a specific interface/video setting to re-enable these buttons? I hope you know what I mean.
This is also related to the remote control, the same is true for WeTek Core. The keymap assigned to the WeTek remote itself overrides this behavior, but it already worked the same way in the official LE 9.0. There may have been a discrepancy in LE 8.2, but I've tried it so long ago that unfortunately I don't remember.
