I think I experienced something like that on occasion on OrangePi PC2 (H5), so it could be driver issue (same driver as on A64). I'll look into it when I find time.
Posts by jernej
-
-
CVBS on H5 can be enabled, but Kodi doesn't support dual screen and there is no mirroring possible with current stack.
-
Kodi has nothing to do with boards. There is no plan, two reasons:
1. No team member has a board to test images (AFAIK)
2. There are only 3 major differences in comparison to OrangePi 3 - wifi, bluetooth and ethernet. As I already said, out of tree driver for wifi and bluetooth is not acceptable solution for LE team. Remains only ethernet...
-
No, no out of tree drivers are accepted for wifi & blueooth. Ethernet has slightly different configuration thant non-LTS version, so that needs work too... So LTS version is not really supported, unless you can live without network connection.
-
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=ttyS0it'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.