Open matt-hammond-001 opened 3 years ago
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. Do you get any solution to start chromium on raspberry pi 4 ?
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 chromium-bin --ozone-platform=wayland --use-angle=opengles --no-sandbox
work?
Does
chromium-bin --ozone-platform=wayland --use-angle=opengles --no-sandbox
work?
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. I'm using the Kirkstone branch of Yocto. My local.conf relating to chromium IMAGE_INSTALL:append = " xserver-xorg xf86-video-fbdev xf86-input-evdev glew freeglut" IMAGE_INSTALL:append = " kbd chromium-x11 xkeyboard-config-locale-en-gb"
IMAGE_FEATURES:append = " hwcodecs x11 x11-base"
DISTRO_FEATURES:append = " opengl x11 systemd pam"
VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" I build with the command bitbake core-image-minimal
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: [564:564:0423/091944.756707:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled. [564:564:0423/091944.871246:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091944.910644:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091944.932636:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091944.956266:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091944.991144:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091945.011115:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091945.036033:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091945.057275:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091945.085960:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=11 [564:564:0423/091945.086092:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't u
This is the error which i am facing any inputs would be helpful.
@Himaniyocto can you try running chromium-bin --ozone-platform=wayland --use-angle=opengles --no-sandbox
instead of chromium --no-sandbox
?
@Himaniyocto can you try running
chromium-bin --ozone-platform=wayland --use-angle=opengles --no-sandbox
instead ofchromium --no-sandbox
?
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.