-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New AEMHF Build / GLIBC_2.29 / RPi4 #344
Comments
Is it important for you to use Buster? I've updated builds to use Bullseye in bca2809 because it simplifies the stuff. Also Buster will be unsupported next year. |
Allow 32-bit builds on Buster. This has some advantages regarding supported HW accelerations in UltraGrid, eg. h264_omx is not supported in higher versions of the system. It is not enabled by default but can be enabled easily by switching the value in YAML file. refers to GH-344
I could be wrong but I believe Bullseye changed the HEVC video drivers. What version of bullseye and firmware are you using that still has access to Note on the video driver change noted here |
I can confirm that I don't have Just for the curiosity, do you have have an idea, which package actually influences this – raspberrypi-kernel? Because I have a Buster installation using Bullseye kernel (in order to easily switch between Buster/Bullseye/Bookworm) and the device isn't present there, neither. |
ARMHF AppImage is already rebuilt on Buster. |
The most recent build of the Linux armhf build appears to has broken running RPI4 with Raspbian GNU/Linux 10 (buster)
Verified the issue exists with a clean OS install
The text was updated successfully, but these errors were encountered: