I assume you mean 2023 at the dates there... Anyway, I just saw the new images on github. I am off to update.
Oh, indeed 2023. I don't know why I wrote 2022. 
Posts by dtech
-
-
So the 9.2.8.10 is the fixed image? Or a newer one is on the way?
I revoked the first release (20220716) and released a new image (20220718) for S805 and S8X2 devices only. But the main version is not changed, it is still v9.2.8.10. (The release date is checked for the automatic update, not the major version number.)
Also, le-aml has automatic updates? What do I use then as custom url under the update settings?
In early June I was trying to teach my friend how to update it manually by downloading the right file and transfering it to the box...
Sometimes it's worth turning the page back to the leading post.
Automatic updates have been enabled for all devices except WeTek_Play because it had an update bug until v9.2.8.7.
NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices will automatically download and install it after restarting. If anyone has any issues with the update, please let me know in the comments.
You don't even need to use a custom url, just turn on the update and that's enough.
-
Does this mean it's a known issue? Do you want me to check something on my end too?
I will return the tvbox to the family tomorrow morning
Yes, but I found the root of the problem and fixed the image. If automatic update is enabled on your box, it will update to the fixed version.
-
That would be awesome, I don't expect anything but if its possible that's great!
In the meantime, I already found a workaround yesterday, but it was hidden in one of my answers, which I think you didn't notice.
Try this:
echo "echo \"audio_off\" > /sys/class/amhdmitx/amhdmitx0/config" >> ~/.config/autostart.sh
^ This disables the HDMI audio output immediately after each startup. I know it's not as convenient as setting it from the menu, but the end result is the same.
-
mdns does not seem to work
Now we just need to find out under which version it broke because the avahi-daemon won't start under any of my v3.10 boxes.
(However, it is flawless under all v3.14 devices.)
Code: avahi-daemonFound user 'avahi' (UID 495) and group 'avahi' (GID 495). Successfully dropped root privileges. avahi-daemon 0.7 starting up. Loading service file /etc/avahi/services/sftp-ssh.service. socket() failed: Permission denied socket() failed: Permission denied Failed to create server: No suitable network protocol available avahi-daemon 0.7 exiting.But if I start the daemon with the --no-drop-root argument, it works fine.
Code: avahi-daemon --no-drop-root
Display Moreavahi-daemon 0.7 starting up. Loading service file /etc/avahi/services/sftp-ssh.service. Joining mDNS multicast group on interface eth0.IPv6 with address fe80::c62a:feff:fe05:7078. New relevant interface eth0.IPv6 for mDNS. Joining mDNS multicast group on interface eth0.IPv4 with address 10.60.0.73. New relevant interface eth0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for fe80::c62a:feff:fe05:7078 on eth0.*. Registering new address record for 10.60.0.73 on eth0.IPv4. Server startup complete. Host name is MXQ.local. Local service cookie is 271343740. Service "MXQ" (/etc/avahi/services/sftp-ssh.service) successfully established.One question, how do I disable HDMI audio output as I use the analog output?
Try this:
echo "echo \"audio_off\" > /sys/class/amhdmitx/amhdmitx0/config" >> ~/.config/autostart.sh
^ This disables the HDMI audio output immediately after each startup. I know it's not as convenient as setting it from the menu, but the end result is the same.
-
The "new" version (2022) S805-based MXQ box has also arrived for me, and quite a lot points to an inconsistent design:
- The control of the blue LED (GPIOAO_13) is not handled by uboot, so a kernel patch is needed. Although the absence of a blue LED light when the box is turned on is rather an advantage.
- The remote GPIO pin is the same (GPIOAO_7), but something different happens during shutdown. When tested on UART, it seems that the device stays on even when turned off under Android, and simply restarts by pressing the button on the remote control. This is not exactly the best solution and indicates a lack of another uboot feature.
- The clock signal of the SDIO bus is limited from 50 MHz to 37.5 MHz. This may also be related your SD card R/W errors, IDK.
- The MAC address of the Ethernet is not burned into the efuse, so even under Android it gets a different address during every boot. This is quite annoying.
I originally planned a separate build for this device, but unfortunately it makes no sense. It would make more sense to compile a bootloader without the above issues.
PS: Regardless, the RTL8723AS wireless chip works perfectly, and it has already been included in the stable version 9.2.8.10. So now you can safely turn on the automatic update again.
-
Code
/home/user/LE9/libreelec-AML/build.LibreELEC-Amlogic_MX2.arm-9.2.8.10/libtool-2.4.6/build-aux/missing: line 81: makeinfo: command not found^ This is causing your problem, so try to install 'texinfo' package first:
sudo apt install texinfo
-
Yesterday all evening I tried to build an image according to this instruction, I built it on Ubuntu 18.04, I got stuck on a libtool error, I can’t figure out what is missing
You could cut a part of the error into a code block, it's hard to figure it out without it.
One question, how do I disable HDMI audio output as I use the analog output? I think coreelec had the option?
Under CE, there are quite a few special Amlogic-specific settings that they put into their system. This has not been necessary so far under LE, but I will see how complicated it is to solve, and I will make a patch if it can be solved easily. I'm asking for a little patience.
-
Hi all! Is there an image for Matricom G-Box Midnight MX2 on aml8726-mx?
qUE_ARM made support for it, you can find it in this topic:
-
I assume its normal with hardware video decoding active that the deinterlace method is greyed out?
If hardware decoding is enabled, the deinterlace method also works with a hardware algorithm, so in this case it is normal that you cannot choose between different deinterlace methods. When hardware acceleration is turned on, the built-in deinterlace filter is automatically activated when interlaced videos are recognized.
-
I have the same H96 pro + as rossig and have issue to boot from SD. I don't know where I can get the meson-gxm-tx9-pro.dtb.
I've created the image with LibreELEC USB-SD Creator using the following packages, but none them works for me :You don't need to get the indicated dtb, because it is already included in the image.
However, it seems to me that you are following the legacy (renaming) method, which has already changed since version 10+.
Please follow this description: https://wiki.libreelec.tv/hardware/amlogic#box-images
-
As I saw, there are versions of the T95M 4K equipped with S905 (gxbb) and S905X (gxl) and S905W (gxl) SoCs.
However, if your box really contains an S905 SoC (gxbb), try a dtb starting with meson-gxbb-. For example, try meson-gxbb-p200.dtb, if you have Gigabit Ethernet, or meson-gxbb-p201.dtb if you have a 10/100 Mpbs Ethernet.
Oh, and don't forget the toothpick method.
-
At first glance, it works well.
Did the driver load itself at boot, or did you start it manually with modprobe?
In the meantime, I backported the persistent journal option to 9.2.8.10, so you can now send me a full system log.
You can turn this on under Settings -> LibreELEC Settings -> System -> Logging.
This setting requires a reboot, after that please send a link generated by journalctl | paste. Thanks.
-
There is a new test version from my master branch that got a new version from the rtl8723as driver:
https://libreelec.dtech.hu/snapshots/20230629_master_65d9f35/ (Driver version: v4.1.11_12622.20141215_BTCOEX20140409_ver3.5)
If you have the opportunity, I would appreciate it if you could test it. Thanks.
-
Can this firmware be updated automatically through auto-update?
This is currently in a different branch, so please turn off auto-update for now until the final code is ready.
If you turn it on, it will update to a version that still lacks this driver, so it would be good to avoid this.
However, you can update the previous version with the tar on the link, so you don't have to make a new installation.
Just download the tar and copy it to the Update folder via Samba.
-
I added the missing module alias to the driver, please try to see if it loads the module automatically during boot:
Index of /snapshots/20230622_rtl8723as_c652eb6/
I also ordered a box, I'm waiting for it to arrive...
-
But you need to start it manually after a reboot.
For the moment, but this little problem will be solved.
-
It works.
Wow, that's good news, the driver seems to be working. Did you manage to connect to a Wi-Fi network?
I bought here: ...
I will try to get one and see what happens. Thanks.
