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.
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...
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?
hi, I'm using tvheadend 4.3.thanks
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.
hi.updated ffmpeg-tools and tvheadend43-ok.quick test-mpd works.thanks
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.
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.
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 a pastecode command.
Apologies, didn't know 9.X has same commands as new LE versions.
pastekodi -
dmseg -
pastecode - not found
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 failedI think you should try a 1Gbit DTB first and ignore RealtekWifi, because it doesn't seem to be present.
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:
Code[ 7.417077@3] stmmac_hw_setup: DMA engine initialization failed [ 7.417091@3] stmmac_open: Hw setup failedI think you should try a 1Gbit DTB first and ignore RealtekWifi, because it doesn't seem to be present.
Hey, really really sorry I didn't get back to you sooner, I was really busy.
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
What I don't really get why these two work is:
- how come p200 and p201 work, these should be different boards/dtbs for different boards?
- how come any xxx_RealtekWifi.dtb doesn't actually work, since that one works with CE?
Now which one of those two above mentioned dtbs should I use - just because they enable eth and wifi maybe doesn't mean they are the proper dtbs broadly speaking for the device (maybe something else isn't working properly with these dtbs but I just don't know it yet), so which one should I use?
If you need any more info lemme know!
these should be different boards/dtbs for different boards?
LE is not CE so in some scenarios CE 'fixes' result in something that works better on some piece of hardware. In other scenarios the absence of those 'fixes' results in LE working better. Roll dice 
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.
LE is not CE so in some scenarios CE 'fixes' result in something that works better on some piece of hardware. In other scenarios the absence of those 'fixes' results in LE working better. Roll dice
Thanks, that does makes sense.
Please see below for my final question about LE 9.
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.
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).
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.
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?
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.
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.
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).
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.
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.
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).
LibreELEC-Generic_S905.arm-9.2.8.18.img.gz ( 6d0cc2b786ead60972d5f3a0578932cdfd162a14eeb2b58cc142badb6b780fc9 ) is what I meant with LE 9.X abbreviation from the first page here, with it's own provided LE dtbs, and that's what I'm using.
CoreELEC-Amlogic.arm-9.2.8-Generic.img was only used as a starting point/"test bench", and it seems that I maybe got lucky why it works with it's own CE p200 RealtekWifi.dtb, or unlucky if you look at it from LE side with it's own same name dtb.
chewitt tagged because of my other thread, hope this helps, I'll do new LE tests too as discussed in dedicated thread.
dmesg pastes, I have been manually turning eth+wifi on/off just to make double sure it works:
CE 9.2.8 (CoreELEC-Amlogic.arm-9.2.8-Generic.img + gxbb_p200_1G_100M_RealtekWiFi.dtb) -
LE 9.2.8.18 (LibreELEC-Generic_S905.arm-9.2.8.18.img + gxbb_p200_1G_100M_RealtekWiFi.dtb) -
LE 9.2.8.18 (LibreELEC-Generic_S905.arm-9.2.8.18.img + gxbb_p200_1G_100M.dtb) -
LE 9.2.8.18 (LibreELEC-Generic_S905.arm-9.2.8.18.img + gxbb_p201.dtb) -
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.
dvamg Thank you for the logs, although I don't see any significant difference, it's a good thing in this case.
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.
dvamg Thank you for the logs, although I don't see any significant difference, it's a good thing in this case.
There could actually be several things causing it, but luckily it seems to have been resolved.
Thank you for your time!
Hey, is it possible to install your LE to eMMC on s905?
If yes, would making a backup of eMMC with Armbian's ddbr or Khadas Rescue preserve the firmware and bootloader/config?
