A lot of Wayland compositors have a GLES 2.0 renderer which should be supported by ancient GPUs. If you try Vulkan based compositors you might be out of luck.
- 0 Posts
- 33 Comments
Joined 2 months ago
Cake day: September 13th, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
CPU overhead
I highly doubt you can conjure up a Wayland compositor that consumes more than 1% of your CPU, even eye-candy nightmares like Hyprland will not have any significant CPU usage.
In this case X11 is used as a fallback if wayland is not used.
It prefers X11, and Wayland can be enabled through the ozone layer.
21·2 days agoWhat does that even mean?
Btw, how do you do that in wayland?
You don’t have to do anything to use multiple monitors with different refresh rates in Wayland, besides plugging them in.
24·6 days ago“Hate speech is ok as long as it’s against the people I hate”
https://github.com/audacity/audacity/wiki/Roadmap
They’re only waiting for some code restructuring to release 4.0, which includes UI rework.
Well, freedesktop.org is now focused on Wayland (Xorg is not getting HDR, new synchronization protocols, or proper VRR (unless through XWayland), while Wayland is). RedHat RHEL marked Xorg as deprecated last year and will not even support it by next year (RHEL 10). KDE and GNOME also default to Wayland.
He says while using WIFI, phone calls, GPS, and who knows what else every single day.
You can’t escape US Sanctions, no matter what you choose. So it’s whatever.
Ok, lots of Russian trolls out and about.
It’s entirely clear why the change was done, it’s not getting reverted, and using multiple random anonymous accounts to try to “grass root” it by Russian troll factories isn’t going to change anything.
And FYI for the actual innocent bystanders who aren’t troll farm accounts - the “various compliance requirements” are not just a US thing.
If you haven’t heard of Russian sanctions yet, you should try to read the news some day. And by “news”, I don’t mean Russian state-sponsored spam.
As to sending me a revert patch - please use whatever mush you call brains. I’m Finnish. Did you think I’d be *supporting* Russian aggression? Apparently it’s not just lack of real news, it’s lack of history knowledge too.
Actually insane lol. But you can’t expect much from anybody who willingly takes money from IBM.
16·14 days agoThat’s not what this is about. He’s complaining about hardware developers putting more work on kernel developers by making them patch all the CPU vulnerabilities that are introduced by trying to increase performance.
FSR is an AMD technology and it’s not AMD exclusive. So one doesn’t imply the other.
This isn’t really driver related. It is the Wayland compositor’s job to properly handle multiple GPUs, which is lacking in some (a very popular, Wayland library that lacks proper multi-GPU support is wlroots) compositors. Vulkan drivers and DRM are already enough to properly handle multiple GPUs. I guess Wayland implementers just haven’t cared enough about the issue, or maybe are figuring out a “perfect” way to address it (a la 3 year long pull request on wayland-protocols repo incoming)
Doubt it’s a sway problem. You got it to work with waybar in plasma, or just in a terminal? Anyways, my setup is also sway+waybar so I’ll try to use cava later today.
Because it will always use X11 unless you tell it not to.