Posts by dtech

Quote from dvamg

Is installtointernal still heavily discouraged on random boards?

New LE even dropped the command.

This script was never present in the official LE images based on kernel 3.14, so according to the official statement it is not recommended. I do not see this situation as critical, but regardless, it cannot be guaranteed that there will be no problems.

It is a known issue that some boxes may have problems overwriting the dtb partition when booting from external storage, so the operation may need to be repeated one more time to successfully boot from internal eMMC/NAND Flash.

Quote from dvamg

Hey, is it possible to install your LE to eMMC on s905?

Sure, you can easily do this with the installtointernal script.

Quote from dvamg

If yes, would making a backup of eMMC with Armbian's ddbr or Khadas Rescue preserve the firmware and bootloader/config?

Unfortunately, I haven't used these yet, so I can't comment.

The uboot bootloader parameters can be checked with fw_printenv under my images. However, the installtointernal script does not modify the uboot bootloader or its parameters, it only modifies these partitions:

• /dev/boot: kernel partition,
• /dev/system: the SYSTEM file (root squashfs) goes here, it is mounted as /flash under LE,
• /dev/dtb: the DTB's partition,
• /dev/data: this is data particion, it is mounted as /storage under LE.

dvamg Thank you for the logs, although I don't see any significant difference, it's a good thing in this case.

Quote from dvamg

NOTE: for some reason, LibreELEC-Generic_S905.arm-9.2.8.18.img + gxbb_p200_1G_100M_RealtekWiFi.dtb now has operational wifi and eth - I have no explanation for this as it did not work before.
Either it was a hardware bug, or the fact that I rebooted to NAND and back before doing these batch of tests, or because I didn't have to trigger the boot recovery button push at all since it was already set up, possibly combo of all three and cheap hardware being goofy, or maybe something (drivers/hardware state) persisted between Android and all of these tests.

There could actually be several things causing it, but luckily it seems to have been resolved.

Quote from dvamg

I am using LE 9.X dtbs for LE of course! Those two dtbs are from LE and they work on my device (+wifi +eth).

There can be a difference in the dtb between two successive subversions. "LE 9.x" is not much information in itself, because there have been many community builds of 9.0, but I don't know of anyone else who has made 9.2 for AML. Moveover, I use the kernel modified by kszaq instead of the official legacy LE's amlogic kernel.

That's why I asked you that if you use v9.2.8.18, please use the dtb included with it. I wanted you to see this clearly, it's no coincidence that the dtb was also updated during the update process.

Quote from dvamg

I was only reporting to you that the box indeed has eth and wifi hardware that works when tested with another OS, because you talked about the device not reporting wifi hardware being present.

I didn't say that I don't see a wifi adapter at all, I just said that I don't see a Realtek SDIO wifi chip because the mt7601u is a chip manufactured by MediaTek, and it also connects via USB instead of SDIO, so the RealtekWifi dtb makes no sense.

Quote from dvamg

However, since I now have two dtbs to pick, do you want me to provide some logs of both to see if one works better than the other, or some other kind of test?

Meanwhile, I compared the p201 and gxbb_p200_1G_100M device tree sources, and their Ethernet parameters are exactly the same, so there can be no significant difference between them. Therefore, I don't understand why your Ethernet didn't work with the gxbb_p200_1G_100M_RealtekWiFi.dtb, unless it's because it comes from a different build (e.g. a different LE build or CE).

Quote from dvamg

I mentioned gxbb_p200_1G_100M_RealtekWiFi as this was working with old CE 9.X (both wifi and eth) so the hardware is in this device and it's operational.

I've went thru every generic LE 9.X dtb and found that these two work, both wifi and eth:
gxbb_p200_1G_100M.dtb
gxbb_p201.dtb

If you use external dtbs, I cannot provide any support for their operation.

Please use only the dtbs packaged with the image, which are located in the device_trees directory.

In fact, only use those included with the current version, because there may be differences even between previous versions.

Quote from dtech

I would have been happy if you had at least told me what device you have, because I'm not sure that you are using the right DTB for your device.

Unfortunately I didn't get an answer to this, although a device model name would be helpful. Unfortunately, I'm still not convinced that you are using the good DTB, especially because I don't see any Realtek SDIO wifi chip in the kernel log.

Regarding Ethernet, in the logs you sent, this doesn't look good:

[ 7.417077@3] stmmac_hw_setup: DMA engine initialization failed
[ 7.417091@3] stmmac_open: Hw setup failed

I think you should try a 1Gbit DTB first and ignore RealtekWifi, because it doesn't seem to be present.

Quote from dvamg

gxbb_p200_1G_100M_RealtekWiFi (s905) has no ethernet in 9.2.8.18.

Don't know about earlier versions, since this is the 1st one I tried.

I know that eth and wlan both work with another OS.

I would have been happy if you had at least told me what device you have, because I'm not sure that you are using the right DTB for your device. (Maybe your device is equipped with a GXL SoC instead of GXBB, or you have a GBE, not just fast Ethernet.)

If the wifi is at least working, it would be nice to see the output of the pastekodi command.

Quote from eric74

hi, I'm using tvheadend 4.3.thanks

Sorry for the delay, but unfortunately there was some hardware issue in my server.

Please update the tvheadend server from the repo if it doesn't update automatically. (Current version of the add-on: v9.2.1.103.)

If you manage to test it, please let me know if this update solved your dependency problem or not. Thanks.

Quote from eric74

Hi, I tried to install the new img s912 9.2.8.19 and ffmpeg still gives me an error in tvheadend when I play live with the .mpd . output from ffmpeg-4.2.4: missing enable libxml2 , stidn pipe23 closed...

Wait, then you actually need libxml2 for the ffmpegx package. That's a bit more complicated, because it's a dependency for several addons, including tvheadend v4.2 and v4.3 as well.

Which tvheadend version are you using?

Quote from eric74

Hi, is there any way to get ffmpeg with libxml2 enabled so that it works in your img? Thank you

Sure, please check the latest snapshot images: https://libreelec.dtech.hu/snapshots/20250828_master_8c05159/

But please keep in mind that the version of ffmpeg has not changed.

Quote from Rizwan

I just switch ON my Wetekplay2 after few months, its working and opening Sat channels , but, I am unable to access Tvheadend by Box ip:9981 and nor webif to Oscam, something changed in last few months ?

Without a log or any other relevant information, it is quite difficult to answer this question.

There were changes during the last months that affected the system itself and TvHeadend v4.3 was also updated.

Please check if these are among the add-ons waiting to be updated. Due to a fairly significant update of the glibc package, the entire LE binary repository has been recompiled starting from version 9.2.8.17. So if your current add-ons start with version v9.2.0.*, they need to be updated, but if they start with v9.2.1.*, you are using the current version.

Quote from xixi22

As you say , this is in base kodi error and i ask for solution your or myself. LTS i mean is as is, then try help with solve this annoy issue with TV channel switching hang your build KODI compete but ssh still works.

The long-term support is for the system itself, not for Kodi. Unfortunately, Kodi developers don't provide short-term support either, so when a new version is released, there's usually no update for the old version, regardless of whether it runs on certain platforms or not.

If this bug is really the same as the one I linked earlier, then it should be backported, but the fix only arrived for versions 20 and 21. Since there were quite radical changes from 18 to 19 (dropping legacy amlogic support, replacing python2 with python3, etc.), so I wouldn't say that backporting to 18 is impossible, but it would certainly be a very looooong task.

Unfortunately, I don't have enough time to try to patch this at the moment, moreover I can't test it, because I don't have any television broadcasting source that uses ISA.

I will probably end LTS support with the release of the first stable version of Kodi Piers (v22).

Quote from suppenkasper

Do you see any chance to get this to work or can someone else help to find a working solution?

In the leading post of this topic, I also indicated under the description of the device:

Quote from dtech

5. Amlogic Meson6 (AML8726-MX) SoC on Linux kernel v3.10.108 (LTS):

• WeTek_Play | WeTek Play (a.k.a. WP1) with AML8726-MX SoC (1 GB RAM, 4 GB NAND) and a modular removable tuner:
  Working services: Power status LED, CPU temperature sensor, Analog+S/PDIF+HDMI audio output, 10/100 Mbps Ethernet, Wireless (2.4 GHz), Bluetooth, RF+IR combo remote control (HID+amremote), HDMI-CEC*, NAND boot**.

...

* On some TVs, this can cause instability, but in this case it is worth turning it off:

Settings -> System -> Input -> Peripherals -> CEC Adapter

Unfortunately, many features of the WeTek Play (and Meson6-based boxes in general) are far more unstable/unusable than even an S805/S8X2, even though they are based on the same kernel. These include the CEC service, but has also some audio and network based issues, including Bluetooth-related that are either unstable or can cause the box to freeze for no reason, which can only be helped by unplugging/replugging the power adapter.

Therefore, it can only be recommended for basic tasks. For example, WP1 may still be suitable for a headless tvheadend server.

Sorry for the late reply, but I was busy over the weekend.

Quote from thadrumr

My lockup is definitely related to the Ethernet port. It must not like either the multicast traffic it's receiving or possibly the LLDP it's receiving. It was connected to a Mikrotik CRS125 switch that is broadcasting LLDP on all ports and there is some multicast traffic on there as well.

I've experienced similar network anomalies before, as I have multiple MikroTik devices on my network, including the main router. Although I've only had issues with some IP cameras and DVRs, it wasn't easy to track down the source.

Quote from thadrumr

This MXQ has a SPDIF output to my Yamaha receiver to maintain digital connection. I just use one of those standard 1/8" to dual RCA cables and use the left (White) RCA cable for the SPDIF connection to my receiver.

I created a media converter for it so that I could use it with Toslink. (S/PDIF 3.5 mm Jack -> RCA -> Toslink)

Quote from xixi22

I mean locate issue in ISA default konfig. My issue is in TV PVR switching channels and this use plugin managed streams over Input stream adaptive, seems default config have issue. Change to manual 1080 and now no crash.

Unfortunately, I can't really comment on that, since it's an add-on, and the last version released for Leia is already outdated.

I also suspect that this bug isn't specifically Amlogic specific, but has existed on all platforms. IDK.

Edit: I found a fairly similar bug on GitHub: https://github.com/xbmc/inputstream.adaptive/issues/1362

Quote from thadrumr

Question I have a MXQ HD18q box running the latest 9.2.18 patch. I am having issues with it randomly locking up. I have tried a factory reset and it's still locking up. I am wanting to use it as a Airplay 1 receiver for Apple Music to get full lossless audio. I have it connected up with HDMI and Ethernet only. It will boot up and run fine. The CPU will hover around 60-65 degrees C which doesn't seem to hot. I have also tried to stream a movie and it will do that fine. If I leave it alone will will eventually lock up. This was with it sitting idle with only an SSH connection into it. One time I was streaming music to it using airplay and it locked up mid song. Can you think of anything that would cause this or is it time to retire this old thing?

Unfortunately, I don't have any Apple stuff, so I've never personally used the Airplay feature. It's a good question whether this could be the cause of the instability issues, or if there's something else going on. (E.g. an unstable addon, a weak power supply, an overheating issue, a dying SD card, etc.)

A pastekodi output would be nice, maybe it will reveal something...

Quote from xixi22

Hello, im new here , then sorry when exist simmilar Q . Longtime i use kszaq Krypton as perfect working on my Tanix S905X. Now i some time testing more variants of newer, but all have issues . I hope this Leia is better, but my test with latest .18 release isnt success. Box boot works ok , but as other on some playing manipulaions totaly hangs and cant reboot any way (ssh too) when in lockup state. Only power off hard.

Is this known issue , hope have some solution? Pls help.

My plan is upgrade from 17 to 18 with same stability. 17 works still perfect , but PVR sclient is old ...

The situation is similar to that of the previous colleague, because I have no idea what could be causing it, and based on your description, the circumstances of the error's occurrence are unfortunately not entirely clear.

"some playing manipulaions" -> What does this mean in this context?

I would be happy to see a pastekodi output, although if the box really just freezes, I'm not sure the log will reveal anything.

Quote from Yorker

Sorry this might be a dumb question but i recently got a Wetek Core (S812) device and was looking into what i can i do with it apart from Kodi

The question is a bit strange because this box is primarily suitable for media playback, but boxes equipped with this SoC are also popularly used for game emulator purposes. In addition, background services can also be run on it, for example using Docker even under LE.

However, due to difficulties running the mainline kernel on n200C devices, only the legacy 3.10 kernel is functional at the moment.

pets

Pulseaudio package has been updated because too many patches were needed to fix this bug, but the next version (v13.0) includes all of them.

The snapshot image is available here: https://libreelec.dtech.hu/snapshots/20250520_master_803f533/

Please try it and report back if the problem is really solved. Thanks.

Quote from Ionman

Is there a download for the VNC server which will run on my Wetek Core? I don't seem to be able to browse https://libreelec.dtech.hu/packages/

The packages directory and its browsing are hidden on the server for security reasons, but you can find it in the LibreELEC Add-ons repository, among the services, under the name Amlogic VNC Server.

Quote from pets

pulseaudio[2118]: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse/module-alsa-card.so: /usr/lib/pulse/libalsa-util.so: undefined symbol: pa_alsa_ucm_device_update_available .
Seems related to e.g. https://bugs.gentoo.org/700870 . (see also #937).

Any chance of getting that corrected?

I will check, thanks for letting me know.