Posts by dtech

Quote from mfizz

Tbh, i wouldn't bother. We make the mistakes, so you don't have to. Disgusting behaviour from the manufacturers not only did they stop supporting it, they took all the support forum and everything offline so you can't even grab old files. Really wanted their Ubuntu minimal. The box wasn't cheap either. I think someone managed to salvage the tuner to be used in other hardware. It's the only thing is was good for.

Coreelec do have working drivers for 9.2.8 if that helps?

I already have a WP1 and a Core, so a WP2 can really fit next to the others. I've modified quite a lot of things in the v3.14 kernel, but in a pretty different way than the CE team. Without "trying", the story is not that simple. And I like to check in practice what I made.

Quote from chewitt

dtech I have another WP2 box lying unused at my parents in the UK, so if you don't find one via eBay I can always post that one to you when I visit them in mid-July.

Thanks chewitt. I managed to find one, now the bargain is coming. If by chance this fails, I will tell you right away. Thank you very much.

Quote from mfizz

Hi, i see you have not made a wetek play 2 build but did see you made an ad hoc for a user. Is it safe to assume that snapshot 3 is the one that should be used?

It hasn’t progressed since the last snapshot above (20220504), but since you are the third to find me with WP2, now I’m really trying to get one from somewhere (at a reasonable price).

ElecUY

I looked it back, for an earlier conversation, and if I saw it correctly, you have an M8S box. Somehow you need to determine exactly what variant you have, this would require a good quality photo of the PCB.

For example, this is my own:

It doesn’t explicitly run with any ROM, just its own, which I also found pretty hard to find in the past.

Quote from Ionman

UPDATE2: A fresh start with a new image solved all issues!

Running out of free space can produce a variety of errors. I'm glad it's resolved.

Quote from jim_p

Good thing you remembered all those details, because I remembered none

I remember we talked about it, but due to the specific data, I also looked back in this topic.

Quote from jim_p

Does anyone know if the black mxq supports 5ghz wifi? If not, how about the mxqpro 4k.

Different manufacturers equipped their devices under the same name with different wifi chips, so your question cannot be answered.

But since we have discussed the wifi chips in both of them before (in this topic), I can answer directly.

Your MXQ (S805) has this:

Bus 001 Device 003: ID 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network Adapter

RTL8188ETV -> The answer is that it is only capable of 2.4 GHz (802.11bgn).

Your MXQ-4K (S905) has this:

...
configuration: broadcast=yes driver=rtl8189es driverversion=3.14.29 firmware=N/A ip=192.168.1.136 link=yes multicast=yes wireless=IEEE 802.11bgn

RTL8189ES -> The situation is exactly the same, the only difference is that this chip connects to SDIO instead of the internal USB line: 2.4 GHz only (802.11bgn).

So, if you are going to install a wifi router (or AP) that only works in the 5 GHz band, it will not communicate with any of them.

Quote from wetek77

Neither my friend. I wonder if it is due to crazycats tuner driver. I saw other img. that have it, but this doesn´t

It is no coincidence that it is disabled. The crazycat and dvb-latest driver packages cannot be simply enabled or disabled. To make these work with my other images (including kernels 3.10 and 3.14), I had several weeks of work involved, including testing with various external USB tuners. The WP2 internal dvb driver was not originally included in any of them.

However, I am still waiting for your system log. I want to help, but that only works if I get answers to my questions.

Ygdrassil

The link in the first post no longer works.

Quote from Samui67

Is there no other way where it is not necessary to open the box? Maybe an USB to serial converter from the USB port of the box into the serial Port of the PC?

Only an Amlogic SDIO debug board would be an alternative to the physical UART port, but it also requires a TTL adapter.

wetek77

Round #3: http://libreelec.dtech.hu/snapshots/20220504/

If the tuner doesn't work with this either, I really have no further idea without the system log.

Quote from Samui67

Unfortunately now i am having a new problem. My box is booting with the image.

it is preparing the storage partition and rebooting fine again but then it stops at the Libreelec splash screen and not booting into Kodi.

Kodi is als not completely installed on the storage partition so i don't get any logs. If i put your original tar file into the update folder,

it is installing your system and after the reboot Kodi is starting up like it should.

How can i fix this trouble?

You will need an USB-to-TTL adapter for deeper analysis.

Quote from wetek77

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

Quote from wetek77

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.

Quote from gthebest

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:

cd /storage/.config/
wget https://github.com/dtechsrv/LibreELEC-AML/raw/master/projects/S8X2/devices/MXIII-Plus/filesystem/etc/amremote/remote.conf
reboot

But of course by answering your question: Yes, you can restore safely to the original MXIII-G image.

Quote from wetek77

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.

Quote from Samui67

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.

gthebest

Which image do you use on your box, the MXIII-Plus or the Universal-n200?

[   20.491487@1] F1 signature read @0x18000000=0x16044330
[   20.494313@1] F1 signature OK, socitype:0x1 chip:0x4330 rev:0x4 pkg:0x0

Based 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.

wetek77

Please try this snapshot image: http://libreelec.dtech.hu/snapshots/20220502/

Quote from gthebest

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. #500

Quote from wetek77

I 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.

Quote from Samui67

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.

Quote from One~

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.

Quote from xbmcking

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:

Quote from dtech

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.