-
Notifications
You must be signed in to change notification settings - Fork 32
GPU Crashes with Wayland/Weston #33
Comments
Also, after some testing, without the hardware acceleration, the scroll lag was just horrendous. Huge CPU spikes on all four cores on the slightest scroll. Somehow I need to use the vc4 driver but without the crashing! It seems I'm in a bind. :-/ |
would QtWebEngine be a valuable solution ? It's HW accelerated on Xorg, but it needs node-worker instead of Electron. |
Investigating now. |
Well since switching back to config.txt
cmdline.txt:
So I'll close this. |
oh gosh ... I use gpu_mem=256 as minimum, no idea how your Electron even starts with 8MB of GPU ... are you sure you need the GPU at all ? |
From what I understand, the open-source vc4 driver used by So it seems to open vc4 driver itself isn't responding to anything in config.txt,. However, I can't boot up at all without something in I am no expert at all in any of this, but the config I have now has been working for about three days. Fingers crossed it keeps working. |
Uh oh!
There was an error while loading. Please reload this page.
Hi, I'm experiencing GPU crashes with BENJA (on Raspberry Pi 3) when the process has been running for a number of hours. Usually, if I leave it overnight the GPU will have crashed by the morning & the HDMI monitor no longer receives signal from the Raspberry Pi. This is the relevant journalctl logs for when wayland/weston starts:
and this is the log for when it crashes:
All after
pacman -Syu
updating everyuthing, latest Raspberry Pi firmware, etc.It appears to be a problem with the OpenGL drivers set with
dtoverlay=vc4-fkms-v3d
in/boot/config.txt
. I couldn't get weston to run any other way than the way you have it here, so I have had to use SDDM window manager/desktop & script BENJA to start over it.This may not be a BENJA issue per se, but since BENJA ships with this config for Waylad/Weston & the experiemntal vc4 drivers, & since I am coming from a non-graphical *nix background (FreeBSD servers actually) & have spent all day wading through a welter of graphics-related stuff that didn't solve much of this problem, I thought I'd bring it up here.
A couple of questions, then. Is there some way first of all to fix this while still using Weston? For instance, a way to get weston to work on Raspberry Pi without using the experimental drivers?
Secondly, since everything is working OK with SDDM/Xorg, how are you accomplishing the
touch reload
reloading of the app? It no longer works with the SDDm setup.The text was updated successfully, but these errors were encountered: