Is hardware deinterlacing supported on A64+ ?
It is. Maybe there is some bug in driver and/or ffmpeg deinterlace filter using it.
Is hardware deinterlacing supported on A64+ ?
It is. Maybe there is some bug in driver and/or ffmpeg deinterlace filter using it.
I built and tested today's master branch and it works for me on PC2. According to your boot log the issue lies in initramfs. Specifically, init script can't be executed by /bin/sh. I have no idea why is that. You should examine build.LibreELEC-H5.arm-11.0-devel/initramfs folder for any obvious issue and packaged variant under build.LibreELEC-H5.arm-11.0-devel/build/linux-5.17.4/usr/initramfs_data.cpio
Tried with both libreelec 10.0.2 final and 11.0 developement releases, the result is the same. There were no errors during the compilation.
Are mentioned images build by you or did you download them from our server?
Ok, so this board has fixed voltage regulators, so there is probably no issues with them. Probably thermal driver has some bug, but that is outside of my expertise.
10.0.x will always use 5.10
I think only RPi is supported for HDR in nightlies.
HDR should be supported by RK too and AW technically support it, but only as 8-bit output.
GDPR-7 We don't update immediately, sometimes kernel is updated after more than 5 point releases. Most of the time point releases have only minor fixes, which don't have big impact overall.
mod81 can you post clear photo of T95 PCB? One developer noticed that some boards need to have AVCC power enabled for thermal sensor to work correctly.
Problem with hevc is that api is not finished yet in mainline kernel, so you need additional patches to make it work. This goes for all platforms that use request api hevc codec (rockchip, allwinner, rpi4, ...)
Doubt this is the right place. I'm looking for support on the Raspbian image for ALL-H3-CC H5 (Tritium) that I downloaded from Libre website.
We only support LE images here. For anything else, you have to find appropriate forum or ask in Allwinner community channels, like #linux-sunxi on IRC, although chances to get answer there is smaller.
You might have downloaded an LE image from the LE website, but you definitely didn't download a Raspbian image.
Actually, at some point it was very popular by board designers to hack Raspbian to run on Allwinner boards. I have no idea why. However, this is all off topic for this forum.
Tthere is also a command to install directly from LE based SD card, you just have to do a search in this subforum.
Is it possible to install LibreElec on EMMC?
yes
I've tried using mali utgard instead of mesa with no success. Therefore, these changes remained in the patch. I made a patch from my local git and didn't clean it up, so sorry.
No need to apologize, just curious. Why would you want to use binary driver? mesa should be better in all aspects.
By default, the console does not work via UART - there is silence. I had to do this following the example of the Samsung profile and the console now worked well.
Maybe only this parameter turn on console in UART: systemd.debug_shell=ttyS0
it's systemd.debug-shell=ttyS0 Note the hypen instead of underscore. I also usually add it at the end of the command line, but that shouldn't change anything.
Note that you also don't need to remove all other H3 boards, you can use UBOOT_SYSTEM=orangepi-lite to limit builds to this particular board.
I'm curious why did you add mali utgard driver patches? That's not used by mesa at all. Also, why did you change DEBUG_TTY="/dev/console" to DEBUG_TTY="/dev/ttyS0"? Serial console works without this change.
EDIT:
Libreelec's default settings have a setting that reserves 320MB of RAM for the graphics core.
This is not exactly true. CMA memory can be used by any core requiring continuous memory region. Kernel can even assign it for normal use (user space processes), with some limitations. So making this number bigger is not that problematic. By far heaviest user of CMA is VPU (video decoding) which is distinct from GPU.
Ah, if it has RTL8189ETV, then you're out of luck. There is no driver in mainline kernel and team decided against inclusion of any out of tree wifi driver, unless there is strong indication that it will land in kernel (no such indication for RTL8189ETV).
I couldn't find any method for reading SDIO IDs from running system, so opening up is simplest thing to do.
The Display only features DVI out in so I use an adapter to get a hdmi cable connected. How could I manually force the correct resolution?
What kind of adapter is that? I tested native DVI monitors in the past, but I didn't noticed any issues. Forcing correct resolutions is a bit tricky unless it's standard (720p or 1080p). If it's not, you have to find useful edid somewhere, create initrd from it, add it on SD card partition and update pxeconfig to load that initrd and add kernel parameter to use it. I've never done it, so I don't know exact steps.
Actually I have no wlan0 device at all, running iw wlan0 scan doesn't work therefor.
Your box either doesn't have same wifi as mine X2 or they rerouted some traces. I suggest you open up the box and check which wifi module is used.
I just tested wifi on my X2. Driver loads ok and I see wifi networks listed in LibreELEC settings. However, after some time they all disappeared. After running iw wlan0 scan over ssh, they appeared again and stayed there. I have no idea whose fault that is.
1024x768 resolution almost always means that EDID couldn't be read. I tested many non-standard resolutions on H3 and they worked, unless there was some issue with clocks, but that shouldn't happen anymore.
In any case, provide outputs of following commands:
pastekodi
cat /sys/kernel/debug/clk/clk_summary
edid-decode /sys/class/drm/card0-HDMI-A-1/edid
offbeat I converted NASA.x265.2160p60.ts to mkv with following command:
I can confirm that TS file indeed produces iommu errors but mkv with same data does not.
I already observed issues with TS files in the past, usually because they start in the middle of the stream, with B or P frames. Converting it to matroska takes care that stream starts with a key frame.
So as far as I can tell, there are three issues:
1. slow decoding loop in ffmpeg
2. rendering issue, probably DRM driver needs some improvement, possibly around YUV scaler (workaround is to use EGL rendering)
3. Cedrus needs to be more resilient to stream errors (mostly missing references for B and P frames)
I guess I'll only PR frequency fixes and leave iommu branch for now. I think it's more important to finish 10-bit HDMI output support and after that, add proper 10-bit output from Cedrus and Hantro (for VP9). EDIT: and of course proper VP9 10-bit support.
Thanks for report. Can you check if switching rendering method from "Direct to plane" to "EGL" avoids iommu issues? It does for me, at least for some videos.
EDIT: Actually, if ffmpeg decoding with -f null - works, I think issue might be in display driver or misreporting actual buffer information, like size or stride.