-
Notifications
You must be signed in to change notification settings - Fork 194
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
chromium-ozone-wayland doesn't run on raspberrypi4 (yocto/dunfell)? #513
Comments
Mind to report to the upstream instead? Thanks. |
You mean the chromium project? |
Exactly. |
Specifically, https://bugs.chromium.org -- you can also paste the bug number here so that we can subscribe to it and maybe CC the relevant people. |
Hi, I am also facing the same issue. |
unfortunately not |
For me it's working using the FKMS driver (although I have some issues with blotting/not-redrawing) |
Hello All i am facing similar issue for raspberry pi 5 can you please help |
Does |
Hello @MaxIhlenfeldt i am trying to run chromium on yocto https://github.com/ds-hwang/yocto-chromium i am following and facing issue can you please help me if you have any sample example for this please I have a Raspberry Pi 5. I want to get chromium to run on it. I want to build Linux via Yocto. IMAGE_FEATURES:append = " hwcodecs x11 x11-base" DISTRO_FEATURES:append = " opengl x11 systemd pam" VIRTUAL-RUNTIME_init_manager = "systemd" The build completes and linux boots on the pi, but when I try to run chromium with chromium --no-sandbox I get the following errors: This is the error which i am facing any inputs would be helpful. |
@Himaniyocto can you try running |
ok sure will try to run but can you have a look do i need to modify something inlocal.conf? |
Has anyone been successful in using chromium-ozone-wayland on a raspberrypi4? I'm trying to get it working in wayland for
core-image-minimal
on pokydunfell
.I have the following config that works on a RPi3 with MACHINE=raspberrypi3 but fails on a RPi4. Is it something I'm doing wrong? Or is there a bug? On the RPi4, wayland starts, but chromium does not launch correctly.
Any suggestions/advice much appreciated.
Command line and error output:
Chromium does not terminate, but appears to sit there indefinitely adding to this output.
My yocto/poky setup:
bblayers.conf:
local.conf (RPi3)
local.conf (RPi4) ... same but with these additions/changes
And have also tried when setting boot/config.txt to
dtoverlay=vc4-fkms-v3d
and rebooting, but the same result. Weston starts but chromium generates the same error output.The text was updated successfully, but these errors were encountered: