16GB is plenty, so just install whatever distro you want.

Re: Nvidia - They’re not dropping it entirely, meaning the drivers stop working, they’re just not going to be including fixes for older devices in the rolling releases anymore. Those cards are almost 10 years old, so that’s not shocking at all. For $40 you can get a card 2x as powerful as that one right there.

Lubuntu and AntiX are the two I hear most often, but there others. There are only a few geared for desktop usage.

Memory is going to be the big decider, and the GPU will be the weakest point for gaming. Nvidia is also probably dropping GTX hardware in the rolling driver updates next year-ish.

If you’re talking about gaming, all distros will be the same, as they are in any other metric aside from memory consumption (there are some tuned distros meant for low memory consumption). As long as it has 8GB of memory, any distro will be fine.

https://github.com/Quedale/OnvifDeviceManager

It’s your CPU almost certainly, but you can confirm by running a game and checking your CPU metrics on a resource monitor while in casual or something. One thing to test is adding the “-threads [threads_number]” for how many cores you have and see if that helps.

Also check ProtonDB for user performance tricks.

The big reason for CS2 getting laggy from CPU being weak is from the number of threads the game runs to keep the inputs from all the players as live as possible. Increasing the power or number of threads improves the perceived lag you’re seeing.

Nope, KDE doesn’t deal with anything at the driver level. Pretty sure it was a combo of removing the Nvidia packages, and then you probably got a kernel update which forced the kernel modules to rebuild and it detected and included your new AMD hardware.

This is normally done automatically, HOWEVER, if you have something like the Nvidia stack of drivers on your system, you can get weird behavior because the package maintainers pull all kinds of ugly tricks to force Nvidia bits and pieces to stick to where they need to be.

In the future, you can trigger a sort of rebuild with whatever your running kernel is like so to force changes: https://brandonrozek.com/blog/rebuildkernelakmod/

This is probably what happened when you did that update, and it refreshed the device table and made sure the AMD modules were loaded properly.

Fedora 100% has acceleration, you just seen to be missing something. Starting from a clean distro isn’t a good indication of where your issue is with your existing install.

Did you switch from an Nvidia card by chance? Did you check if you might have blacklisted AMD drivers?

Reboot and check dmesg for any obvious errors, and lsmod | grep amd to see what, if anything, is loaded. If nothing is loaded, I almost guarantee you have something blacklisted.

Yes, that’s what I’m saying. Running Android on Linux is one thing, and that only requires Waydroid and has nothing to do with Steam.

Having an SDK stack specifically for androidarm64 means there are extensions there to hook into the Steam client, meaning Android apps that use Steam platform for…something. This was never announced or discussed.

It has nothing to do with Frame specifically, because you don’t need an entire SDK entry point for one device that has nothing to do with Android anyway.

So it must mean that they intend to give the option to hook in to Steam for game devs that already have Android builds and distribution or something. Like Netflix games, Rockstar, Bethesda…etc.

Interesting…

I think we only knew about the arm64 but, but not androidarm64. Sounds like they’re leaving the option open for Android developers to make their APK distributions compatible with Steam to play on Frame.

Maybe you don’t understand how RTSP works, but it’s just a protocol for sending video and time information in a stream.

Try VLC if you just want to view the stream.

If it’s a generic controller without a known equivalent HID compliant profile (this one detects as a Switch), it’s likely not going to work well for a variety of reasons.

Maybe give this a shot: https://github.com/DanielOgorchock/joycond

It should make controllers aligned with Switch work with steam-input.

Just don’t run this version of Proton with this game.

The reason they make all versions of Proton available at all times is because the rolling Proton version may break game configs for various reasons, in this case it looks like a Vulkan rendering queue issue where the call is blocking: https://docs.vulkan.org/refpages/latest/refpages/source/vkQueuePresentKHR.html

You can check ProtonDB to see if anyone has a workaround for newer versions of Proton, but it’s mostly unnecessary unless there’s some specific features a specific point release you care about. Just pin the game to a working version and go.

I mean…once they have this going, there’s nothing stopping that. It’s essentially the same thing, except the hooks for Mac/Win for the desktop. Linux will already be ready to go. I just haven’t heard them mention it is a point of release is all.

I’m…not sure what you mean. They’ve just compiled SteamOS and it’s base for arm64. There was nothing stopping that from happening previously. The majority of the client code is closed, and that entire piece of SteamOS is weaved into the OS itself. So they’re just distributing arm64 builds if SteamOS with the client code, not commiting to a standalone client being distributed, unless you’ve seen that somewhere.

Support meaning in their build system. They’ve already added that as a build option awhile ago. Just means you can set a flag to build for more platforms now, and they have arm64 machine types to handle the builds.

Devs still need to do optimizations to support this in most cases. Some games based on open frameworks won’t have much to do but flip the switch.

No, they are building a translation framework for x86

Grammar and formatting, ma dude. This is painful to read.

If you’re reading reviews on Software Manager, you don’t want to be messing with jails.

Just use Flatpaks, and install Flatseal for permissions control over individual packages. They are sandboxed, but with permissive defaults set by the devs, so you can use Flatseal to lock them down, then set permissions you’re comfortable with. If it breaks something in that one Flatpak, then just reverse your permissions changes. Simple.

“We’re expecting console numbers this time, and then they developers will have to support it.”

I think you probably need to understand the underpinnings of what Valve accomplished over the past few years to understand why the Frame is useful.

Essentially, it’s a Deck strapped to your face. Same OS, same everything, just different hardware platform.

Valve spent the time to revamp SteamOS in order to make it more portable to various devices, which are now launching. Couple that with their efforts on Proton, and you have an entire ecosystem with very little in the way of preventing people from adopting these devices with their ease of use.

Steam Deck was just sort of the appetizer and test launch to gauge interest and build a fully functional hardware development and support vertical in the company, and it was wildly successful. I guarantee (if they can get the price right) that the Frame will sell WAY more units than the awful Vision Pro. I honestly think people might adopt this over buying another version of the Deck if it’s comfortable.

Some things I expect to happen with the Frame launch:

• A more expanded integration of Desktop features. If Valve doesn’t do it, the community will.
• Virtual screen management
• Theater mode for viewing media
• Virtualized VR input (like steam-input but VR)
• Pairing capabilities for multiplayer
• Half-Life 3 release (not joking)