The framework 13 definitely has a fingerprint reader. Top right corner power button, just like a Mac.
https://frame.work/products/fingerprint-reader-kit?v=FRANFF0001
Just as usable as the one on my old M2 Pro work laptop too.
Fwiw, I did the DIY and brought my own 32gb of ram and 2TB nvme to keep the costs down a bit.
You might want to check out distrobox. Nice way to access apps for other distros or package managers like they’re native.
I’m also on Garuda for my main box (Bazzite on the framework 13), and I have an Ubuntu distrobox for dev work with one dev project, another for general tools that are only released as .debs, one running fedora for things that “only support RHEL”, etc.
Windows was just the boat you already knew.
Now you have a new (more adaptable) one and don’t know all it’s squeaks and rattles. You’re neither dumb nor is something wrong. You just aren’t familiar with what it needs from you.
Give it some time (a week compared to how long in windows?) and attention and soon you’ll wonder why you ever second guessed it.
I would ask for a healthy margin above 100%, especially if you’re bringing an older PSU. There are a ton of variables for determining what is needed, but if your TDP on those 2 items is pushing 400W, we should be aiming for 500+ with an 80 Plus certification.
This definitely plays like a failing PSU to me as I experienced similar issues when mine started dropping on one of the 12V rails with similar hardware (fx8350, r9 290) several years ago.
I’d love to think so too, but I think our echo chamber is pretty tight.
I certainly think they’re ready for mainstream usage (I have one Bazzite install myself), but I don’t think there’s significant awareness beyond the dedicated fan base.
There aren’t really any actually useful metrics that I know of, but the only one of the 3 I’ve mentioned that broke into distrowatch’s top 100 is Bazzite, and that’s only in the last few months.
And for legal threats: I doubt any court in any country will give credence to that. Fedora is MIT licensed.
That’s certainly part of the motivation (see the 4th paragraph).
Yes, image based. No, not Bazzite specifically, but silverblue (and kinoite) under the fedora banner directly.
But that’s not really the point of the article. In order for those to go mainstream, flatpak and especially flathub have a lot of maturing to do first, and the author lays out a pretty good roadmap with thorough explanations.
It’s Nvidia that that jumps out in your question.
They are /were notorious for lackluster support on Linux and sleep/wake issues are /were significant.
IIRC you still need to configure a few bits to get it to work properly (maybe just a systems service enable?).
… And it looks like it’s still a constant issue.
Thread with various fixes and tweaks: https://gist.github.com/bmcbm/375f14eaa17f88756b4bdbbebbcfd029
Off the top of my head, I think sudo journalctl -xeb -1 should give you some useful error output for the previous boot (after rebooting from a failure).
There’s a --list-boots option if you’ve rebooted a couple times since but aren’t entirely sure.
Obviously you should relearn everything. Heck, pick up the Dvorak or Colemak keyboard layout while you’re at it!
/s
That toshy thing looks like the right way to go. Wild that this is such a complex issue.
I had to go the other direction (Linux -> apple) for a bit and ended up remapping the caps lock key to command so I could approximate “normal” reflexive (pinky-based) shortcuts. It did sort of simplify copy-pasting in terminals.
Dang, this was the first I heard about mobile justice shutting down.
It had been on my phone and thankfully unused for a long time.
Looks like this is the written version of the video:
https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/
Well that’s not good…
They seem to be reasonably active, so I would imagine that situation won’t last long.
Garuda is about the same.
Arch base, preconfigured for btrfs snapshots on Pacman updates (and they provide a handy garuda-update wrapper to that), many niceties already done for you.
I’ve used the snapshot feature a couple times and only because the Nvidia drivers botched something horribly and I went back to the same snapshot a couple times.
And I use distrobox (rootless podman FTW) for some crap too. Like that time I needed WebEx at a moment’s notice for a call (and they only provide a deb and rpm). Or spur of the moment dev environments when I don’t wanna futz around with vscode devcontainers.
But with arch-based stuff, you gotta read the Pacman output. If you don’t wanna, definitely reconsider immutable. Next time I can be bothered to reinstall, that’s where I’m headed. Heck, you can start a distrobox with Arch and install all the AUR shit you please without a major worry.
I take it a step further with distrobox to provide the tooling (like the preferred version of poetry and other cli tools). That ensures people can jump in with the right versions of tools easily, and changes to tooling can be disseminated with a commit (and container build).
But I agree. Get started and solve these problems when they are problems.
I wish them luck and hope they can find better ways to work with the existing maintainers.
I’d like to suggest that you take a different approach, though it looks like there is a workable suggestion already.
Consider using apt_preferences to pin your versions instead of scripting.
https://wiki.debian.org/AptConfiguration#apt_preferences_.28APT_pinning
Here’s a clip from one of my distrobox builds:
Package: python3.10
Pin: version 3.10.*
Pin-Priority: 999
Interesting. I’m on version 1.1.2 from F-droid, last updated 10 months ago.
Ah, looks like it’s a pre-nerdified cascadia! Not my personal style, but I know a few that love cascadia.
You can search the package database to determine which package(s) provide a file with
dpkg --search $file