You are not logged in.
But that involves simply disabling HW acceleration for FF - do you actually have to do any of the other steps?
No probably not, but I haven't ruled out a better solution to this, as the temps are still pretty hot even with HWA off. I thought it would be better to explicitly set outputs to 8bpc, just in case. Out of curiosity, do you use a different YouTube client/frontend?
Offline
temps are still pretty hot even with HWA off.
Because the poor CPU has to do all the work now.
Since we're down to FF as the problem, what's the current value of "media.ffmpeg.vaapi.force-surface-zero-copy" (in about:config) and what if you change that?
(Obviously w/ HW acceleration re-enabled) - 0 disables it, 1 enables it an 2 is the "default" (ie. FF rolls a dice on your hardware or whatever )
Offline
Setting 'media.ffmpeg.vaapi.force-surface-zero-copy' to 0, 1, or 2 causes a crash.
Offline
"fuck"
X11 still works?
Have we ever tried a wayland compositor that's not hyprland? Weston or sway?
Offline
X still works, tested on an EndeavourOS live env, with HWA and VA-API enabled. Sway crashes like Hyprland.
Offline
Let's see whether we can break X11, start the server w/ "Xorg … -depth 10"
The server is either started by xinit in which case the xserverrc can be used to control parameters or by some DM which typically all have session setup scripts where you can edit that.
The alterntive would require to write an X11 config w/ a screen section.
Offline