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.

There is more than just the kernel

This is a developer desktop. Its purpose is to develop software for the ARM architecture, therefore all you need for this machine is kernel support and development tools, all of which support ARM.

I don’t see the competitive advantage

What about being able to compile and test for the targeted architecture? For example, Ampere-based servers are increasingly being deployed, I don’t think there’s a car out there running x86, and Apple started a trend of ARM based laptops. There’s a new architecture in mainstream computing and those who have native ARM machines to test their products on have an advantage over those who don’t.

arm64 is very well supported by the Linux kernel. What makes you say it’s not?

https://wiki.hyprland.org/Configuring/Binds/#global-keybinds

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)

Lol. It’ll work eventually.

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.

They’re so done with NVIDIA they don’t even have the energy to attack them on a forum anymore

Interesting. Well it was worth trying I guess.

Try increasing the height of the bar to some insane value. Just to make sure it’s not cava being unable to scale down.

I didn’t know you could run kodi straight from the tty, sounds cool. And yes, kodi has Wayland support.

Running kodi on a cage session sounds like a nice idea. Cage’s whole purpose is to run 1 app maximized.

Yeah. Unfortunately most consumers buy NVIDIA, even though they only care about the enterprise sector.

Yes. Wayland protocols take too long to get merged. Actually, a few days ago some people (mostly Valve guys) got tired of it and took action by proposing changes[1, 2, 3, 4]to the way new protocols are handled. Hopefully it gets better. Also, if your compositor is based on wlroots, then you might get support for the new protocol very soon.

The screen capture protocol was merged a month ago. Support will come soon. wayvnc, grim (and by extension grimshot) already have support for it. No compositors have implemented it afaik, but wlroots is very close to it.

That is NVIDIA’s fault. They wanted everyone to use the inferior EGLStreams while knowing GBM is better. Everyone ignored them and moved on, so NVIDIA sucks on Wayland. They did change their mind recently so maybe you’ll get support at some point in the future. Unfortunately there’s nothing to do from the Wayland side to fix this, except for adopting EGLStreams which nobody will do.

There’s no protocol yet that allows apps to observe inputs. They just started working on it so it may be a while.