

Just a hunch, but if you haven’t upgraded your PSU, it’s likely not able to power that card.
You say you’re getting a display at least, so that’s something. You should be able to boot your machine into safe mode and install the driver. You also don’t need to have the card inserted or enabled to install the driver, not sure where you read that.
One thing to help debug: boot a LiveUSB of something Fedora-based. See if you get to a desktop with the Nouveau driver at least.


I have this moon here if you’d like it?


Try setting the game to use the Steam Linux Runtime under the compatibility settings in Heroic. See if that works.


Wha? These have nothing to do with each other…not sure what you’re meaning to say.


If you really wanted to, yes. You’d have to be able to deal with the eventual inconsistency involved with overriding a distro default of sorts (Plasma), but it will run just fine and won’t be overwritten.
Your particular wants have nothing to do with the distro being immutable, but more that it’s a productized distro for a specific platform. Your complaint would also work for phones where you want to ditch Android for a stock Linux install. Sure, it’ll most likely run, but you need to deal with what all that entails when not built for the specific thing the device is built for, which is why the entire product platform exists in the first place.
https://dev.to/fstanis/how-to-install-cinnamon-on-your-steam-deck-1boe


You’ve kinda got it wrong a bit.
Any usermode changes you make don’t get reverted. Boot into Desktop mode, install whatever you want, and those stay.
Underlying OS changes won’t impact that because usermode is seperated from the OS space.


Never had an issue. You may want to turn off all of the bells and whistles that cause it to spike CPU when idle though, that might help.
Settings > Library > Enable ‘Low Performance Mode’


Steam Deck runs Arch at its core. The distro has nothing to do with it.
How you have Steam installed might though. Do you have it installed via Flatpak by chance?


It might be better to first learn about existing package managers: build some packages for rpm, apt, pac…etc.
The fundamentals would be easier to understand from there to figure out what you actually want to write and why.
At their core, packages are simply just bundles of flat files, and stages of scripts that get executed. That’s it. Like a zip file with scripts.
Package Managers on the other hand are just clients that deal with the metadata and contents of packages and decide what to do with them. They go way deeper.


Not really. If it was power efficient, MAYBE, but it’s not because it’s a super old chip AND a laptop. It’s a vampire device.
You can buy a 6W minipc for like $40 tat6would be more useful.
You won’t need a terminal unless you refuse to use the GUI tools that do the same thing.
If you want to use the terminal, go for it and use the default. If you eventually find it lacking THEN start investigating different options.
Just use everything as you normally would otherwise, and you shouldn’t notice a huge shift.


Well, no. Not to shoot down your comment or anything, but you’ve only learned a lot about Nix still in your example.
For instance, if someone presented you with an Arch system of some sort and asked why a certain systems unit wasn’t working, or why the speakers on their laptop don’t work but the headphones jack does, or why their Nvidia kmod modules aren’t loading.
Your experience with Nix is t going to help with some of the more basic functions of a traditional Linux system because of the abstractions in top of abstractions that you’re used to interacting with on Nix.
I’m not even digging on Nix, like I said, it was designed for a very specific purpose. I’ve run hundreds, if not thousands, of various build system permutations on Nix over the years, and even I wouldn’t even think about using it for really basic stuff like running a Desktop 🤣


If you simply just want to track config file changes, use a flat git repo, or something like Ansible.
That’s going to be a helluva lot simpler for you to learn and execute on.


Traditional and Immutable distros as working OSes are not knowledge compatible at all. The software that runs on it is the same, but everything else about how they run, are executed, managed, installed…etc, all different.
Nix is Immutable, and on top of that, has an entire configuration language you need to manage.
If you’re not familiar with a standard Linux OS, you’re going to have a bad time, I can tell you that.
As far as your concepts of “random commands” not being used as part of the running of a system, that is not quite correct. You will still to track adhoc changes to different services or configurations that would then need to also be applied and executed in a NiX config in the proper place to ensure proper order of execution.
Let’s just say it’s an advanced system that serves a purpose meant for repeatable testing and CI/CD type operations. It’s not really meant to be a user-friendly system to make managing your desktop easier, so. don’t misunderstand this one important fact.


Fatty fingers


If it just started out of nowhere, and you haven’t updated recently, then check your heat, power and memory.
If you’ve updated recently, check and see what got updated and go back to the previous versions.
This generally referred to as Key Rotation. It applies to everything from SSH keys, to API keys in running apps.
There are automated ways to do this with ease, but it’s very simple to do with a single script, and some sort of secure key/value store (bitwarden, Vault, etcd…whatever).
The process is basically something like:
/ssh_keys/host1-private-12.1.25and/ssh_keys/host1-public-12.1.25/ssh_keys/host1-private-12.21.25and/ssh_keys/host1-pub-12.21.25/ssh_keys/host1-private-currentYour script can clear the old keys if needed but simply validating them in the access change serves the same effect. Up to you.