With regards to Arch based distros: Do you still need to read Arch news to spot potentially breaking updates and know how to diff pacsave/pacnew, etc. or have Garuda found a way to manage these things?
Most prompt customizers have an option for showing how long last command ran and whether it succeeded/failed or simply prompt timestamp, it's often default. I use Tide, there's also Starship and a number of others. You can also roll your own ofcourse.
Yes, it seems like there could be a weakness there, unless it's just a fluke. The test has a background I/O load designed to stress BFQ I/O.
I guess mileage might differ. I installed Tumbleweed and then the Nvidia drivers following the wiki instructions. Everything is going great. Running a 3060 with Wayland+Plasma on a 360Hz screen and gaming through Steam. I love Tumbleweed.
An alternative if just for benchmarking is EndeavourOS, you can choose proprietary Nvidia drivers as a boot option in the installer and then I believe it'll be installed with them without further ado. Downside is if you use it long term you have to read Arch News before updates to spot breaking/incompatible changes and be knowledagable of things like pacnew/pacsave files, etc.
Even Nvidia have embraced RISC-V, the general purpose controller embedded on their GPU's is RISC-V.
He wanted something that just works and have very straightforward updates. On Arch you should read Arch News and check the output from updates to make sure no manual intervention is required, you need to understand Pacsave/Pacnew files, etc. One can coast along for a while without this but one day things can suddenly get funny.
I used to use starship with eloquent prompts, including git information, etc. Somehow I tired of it, it's wasn't actually useful, so I just use a standard "name@host ~>" prompt with Fish.
Panel freeze is a known KDE bug on non-Intel GPUs. It's fixed in Plasma 6, avoid it on Plasma 5 by disabling window previews for the panel.
@ProtonBadger
@kbin.social