Unfortunately, I can't help you with other distros, try their own forum.
Posts by dtech
-
-
This is the dtd patch in my release (v9.2.8.12) for the 3.10 kernel:
LibreELEC-AML/projects/S8X2/devices/M8S-Plus/patches/linux/M8S-Plus_KII.patch at master · dtechsrv/LibreELEC-AML'Just enough OS' for Kodi for some Amlogic TV boxes - dtechsrv/LibreELEC-AMLgithub.comBut it wasn't so hidden that it couldn't be found.
-
What is the purpose of searching for this dtd/dts? And which LE version are you trying?
-
Can I use LibreELEC-Generic_S805.arm-9.2.8.12.tar for update, or better use LibreELEC-HD18Q.arm-9.2.8.12.tar?
Yes, it can be used as an update from HD18Q, although you won't notice any added extras.
This image is especially beneficial for a new installation because it is created by merging the separate HQ18Q and m201d images.
I originally planned to replace these two images above with the Genecic_S805 image, but it turns out that some bootloaders don't handle multi-dtbs. But, in the case of your box, there is no such problem.
-
-
-
Statements like this make me regret trying le 11 even more
How did you manage to install LE11+ without this button?
And the reset button was supposed to solve all that compatibility mess.
If you press the button for a long time (10+ seconds), does Android recovery load? (This can take up to half a minute afterwards.)
-
What else can I do?
The aml_autoscript of LE 9.2 and the new LE11+ image are not compatible with each other. If that button really works, it should be able to load the current autoscript from the sdcard when it is pressed.
So, if this is not the case, then even though the button was eventually soldered in, maybe also missing a single bias resistor that needs to be connected in series with the button. (But this is just a guess.)
-
Don't be angry) did you know that because of this the console goes into reboot? let it lose connection, but rebooting is not a logical behavior for a TV set-top box when there is no connection
I'm not angry, I just sometimes feel that the time I spent on description is a waste of time.
Unfortunately, I can't/wouldn't like to touch the kernel driver for these reasons:
- Your device is in the 3rdParty category, which means I don't have such a device, so I can't test the functionality of the modifications,
- Minix X8* devices come with a kernel modified by datrh. There was an attempt to switch back to the kszaq's kernel, but several things did not work under the images, so it was discarded.
The reason for the restarts may even indicate a hardware error. Unfortunately, even the logs do not help to find this out.
My general recommendation is to use an Ethernet connection, but if that is not possible, I recommend the 2.4 GHz range if it works properly. -
The thread is 50 pages now. Should I close it? Users don't read the whole story anymore.
No one needs to read the whole thing, I was just referring to the very first post.
I don't want to close this topic yet, because I'm still adding minor updates to it.
Latest version: LibreELEC 9.2.8.11 (Release date: 2023-09-11)
^ In short, this topic is not completely dead yet.
-
Dtech, thanks for the quick response. I understand you. But there is another problem, and it is related to wi-fi. For some reason, when connected to 5G Wi-Fi, the TVbox periodically restarts itself and loses the network. On 2.5g there is no such problem - everything works stably. Maybe the problem is related to the Wi-Fi channels?
Why doesn't anyone read the leading post of this topic?
IMPORTANT NOTES - Please read them carefully before asking:
...
- I can't do miracles with the wifi and bluetooth drivers built into the kernel, so I can't do anything about "cannot connect", "the signal is weak" or "the connection is slow" errors either, so please don't expect a solution from me.
-
Hello dtech. I have a question about assembly for X8-X8H. I own a MINIX Neo X8-H device. It claims 2 GB of RAM, but in the system information I see that the system only detects 1553 MB of RAM. Is this how it should be? or do I need to configure something?
You will be surprised, but you are not the first to ask this. Kodi displays the amount of memory it can use as total memory.
If you run a dmesg, it also becomes clear to you that the device pre-allocates certain memory areas for some built-in purpose.
For example, it looks like this for the M8S-Plus:
Code
Display More[ 0.000000@0] physical memory start address is 0x200000 [ 0.000000@0] reserved_end is 20afffff [ 0.000000@0] [ 0.000000@0] Total memory is 2046 MiB [ 0.000000@0] Reserved low memory from 0x06000000 to 0x20afffff, size: 427 MiB [ 0.000000@0] mesonfb0(low) : 0x06100000 - 0x0c100000 ( 96 MiB) [ 0.000000@0] mesonfb1(low) : 0x0c100000 - 0x0c200000 ( 1 MiB) [ 0.000000@0] deinterlace0(high) : 0x7df00000 - 0x80000000 ( 33 MiB) [ 0.000000@0] mesonstream0(low) : 0x0c200000 - 0x0e200000 ( 32 MiB) [ 0.000000@0] vdec0(low) : 0x0e200000 - 0x1e200000 (256 MiB) [ 0.000000@0] ppmgr0(high) : 0x7bf00000 - 0x7df00000 ( 32 MiB) [ 0.000000@0] vdin00(low) : 0x1e200000 - 0x1e300000 ( 1 MiB) [ 0.000000@0] vdin10(low) : 0x1e300000 - 0x1f300000 ( 16 MiB) [ 0.000000@0] amlvideo20(low) : 0x1f300000 - 0x20b00000 ( 24 MiB)
In addition, a few other things require reserved memory, so in the end this will be the amount that can actually be used freely:
Code[ 0.000000@0] Memory: 64MB 16MB 1460MB = 1540MB total [ 0.000000@0] Memory: 1545608k/1545608k available, 31352k reserved, 1250304K highmem
I hope it's clear now.
-
It looks like a total mess what you're doing on the console.
Even though the binary doesn't start due to an error, the service is probably still running in the background. That's probably why you can't delete it because it's currently in use. First you need to stop that:
systemctl stop service.tvheadend43
But why do you want to delete this service file? I don't see any sense in this.
And, I don't even understand that symlinking. This will in no way lead to results.
Installing, deleting and updating binary addons without the GUI is a quite problematic.
-
ill install it later tongiht and report back, I hope it all works, or else my wetek simply imploded
Mainly because of the distance, I also recommend another addon, which is also available in my repo, and this is the VNC addon.
With this, you will also see the GUI, provided that there is a display on the box:
-
Ai, since I run the whole operation through cli, some 60 miles away, that is not an option unforutnately. What is the source of this 4.3 addon? Can I manually mine this repo? A link would be appreciated :))
Unfortunately, the directory index on my server is hidden under the package repositories (due to the search robots), so I can only provide a direct link to the binary at most:
-
Found this chip es7134lv in my carte mere wp2 I think it has to do with the sound . Could you be the cause of the problem? Because I removed it and turned on the device without it. The device works normally without it, nothing happened. I mean, as before, the sound and display work from Android et LE 9.2 but LE 11 screen DVI and not sound
This is a DAC chip, which is responsible for the stereo analog sound on the A/V output (4-pin 3.5mm Jack), so it was completely unnecessary to desolder it.
I think you should simply change the type of the input in the menu of your display (from DVI to HDMI) and there would be sound immediately.
I also ran into something similar on my 22" LG Personal TV, and when I set it to HDMI, the sound came on as well.
-
-
To me, hanging at 30-40% processor usage doesn't mean that the SoC is weak, but that the decoder is poorly optimized.
Maybe the newer version will bring more performance improvements, or maybe rav1d.Unfortunately, it is no coincidence that dav1d v1.0.0 was included, and not a newer version. Even for v1.0.0 it was not easy to backport and test the necessary ffmpeg modifications, but for v1.3.0 a lot of things would have to be modified. Since Leia's ffmpeg is an old version, even if I wouldn't call it an impossible task, it's not worth spending so much time, because I don't think the situation would improve much.
However, dav1d v1.3.0 is already present in the LE12 AMLGX image, so if you want to give it a try, I recommend you try that.
I want to keep using the old device so it doesn't end up in the trash, not buy a new one, if software solution is possible.
No one suggested throwing it into the trash, but compared to H.265, I don't know how much better the AV1 codec really is, especially because the hardware acceleration of HEVC is still available on S905. By the way, software decoding always causes unnecessary heat dissipation for the SoC, and knowing this, I no longer see the point, because it is no longer energy efficient anymore.