Updated FAQ (markdown)

NGnius (Graham) 2022-07-16 23:24:02 +00:00
parent 367ee621f4
commit 09cd11f8b2

11
FAQ.md

@ -1,7 +1,7 @@
# Functionality
## How does PowerTools work?
PowerTools interacts with the system in roughly the same way as outlined in the [README](https://github.com/NGnius/PowerTools#cool-but-thats-too-much-work).
PowerTools does not save any data; it reads and writes to the SteamOS system (mostly the Linux kernel).
PowerTools does not save any data by default; it reads and writes to the SteamOS system (mostly the Linux kernel).
Since no data is saved, a reboot will reset all PowerTools settings back to default.
## Why does PowerTools only let me select some values?
@ -11,13 +11,13 @@ There's a few reasons for this, depending on the values in question:
- Others: logical limits coming from the [specs of the Steam Deck](https://www.steamdeck.com/en/tech)
## How do I reset to default settings?
Restart your Steam Deck. Nothing in PowerTools is persistent.
Restart your Steam Deck. Nothing in PowerTools is persistent, unless you enable persistence (in which case: turn off the toggle, *then* restart your Deck).
## Why is X the default?
I don't know, ask Valve. Most of the defaults are pretty logical, so none of them should be too objectionable.
## What does disabling SMT do?
The SMT toggle in PowerTools doesn't actually disable SMT. Instead it disables every second CPU, since every group of two CPUs is one logical CPU core. Valve's SteamOS uses an older version of MangoHud (the performance overlay) which [crashes when CPUs are disabled like that](https://github.com/flightlessmango/MangoHud/issues/737).
The SMT toggle in PowerTools doesn't actually disable SMT. Instead it disables every second CPU, since every group of two CPUs is one logical CPU core.
# TLA (Three Letter Acronyms)
## CPU
@ -31,10 +31,7 @@ Simultaneous MultiThreading: The generic term for making one logical core act li
# Miscellaneous
## Can this damage my Steam Deck?
If you're responsible with how you use it, no. Generally, software can't damage hardware unless there are already existing issues. Of course, you can always set the fan to off (0 RPM) for too long and kill components from overheating; don't be surprised by a fresh hole in the wall when swinging a hammer at it.
## ;)
Clicking where you shouldn't be, I see...
Generally, software can't damage hardware unless there are already existing issues. Of course, always use responsibly; don't be surprised by a fresh hole in the wall when swinging a hammer at it.
## This is really great, how can I support you?
I already make enough money, thanks. If you really want, donate to some FOSS foundation and/or support a project that's mission critical.