Fingerprint readers, in general, also widely seem to be poorly supported.
Not sure if it technically counts as fingerprint readers but using my YubiKey Bio daily, for login on my desktop and WebAuthN and... 0 problem.
Fingerprint readers, in general, also widely seem to be poorly supported.
Not sure if it technically counts as fingerprint readers but using my YubiKey Bio daily, for login on my desktop and WebAuthN and... 0 problem.
voice actor, artist, and musician. My main concern is recording software and to a lesser extent, art software
Even if you are not based in Brussels where we have https://resonance-mao.be/ you might have a local equivalent, namely open source and open hardware music enthusiast and profesisonals who meet monthly at least to learn and jam. They know this domain a lot more than I do. There are a LOT of software for all that but I wouldn't go as far as advising you. That said yes it mostly likely will require a bit of re-training. Still IMHO you have done the hardest, namely you understand the concepts behind what the tools do. The interface will be different but how it is actually done should be the same. My advice is to find "your people" and discover together.
Regarding hardware Mint is based on Ubuntu which is based on Debian. I have an NVIDIA GPU and I play (and work) with it daily. Sometimes sleep/resume is buggy but pretty much never ever while actually working or playing. Regarding the Webcam, it's not super convenient but until it gets supported (hopefully) you might have to rely on an external camera.
Neat! Two quick things :
I’m not convinced Linux has comparable software I need).
Feel free to ask here. I might not know alternatives but others could, no matter how niche.
Samsung Galaxy Book 3 Ultra [...] didn’t play well unfortunately
Same advice. I don't have one of these but what fails and how? Any specific error message?
The lack of support seems very daunting at first.
I started thinking "Oh I wish I could transition to Linux, away from Windows, but what about the latest hardware or random gadget?"
The trick is to flip the question around, namely not "Does my current hardware work with Linux?" but rather "Am I sure my next hardware work well with Linux BEFORE I buy it?" then this remove 99% of headaches. It's typically 1 Web search away from either a lot of complaints or positive feedback... or not much, and then it's up to you to see if you are ready for an adventure. If there is not much but there is some standard interface, e.g. Bluetooth, and no need for a proprietary application, it's nearly sure the main features will work. If a proprietary application is needed, then safer to avoid.
So.... yes maybe surprisingly a LOT of hardware does work well with Linux!
What does not work for me, to give a random example, is the LED controller of my desktop case, which I bought several years ago while Windows was still my main OS. I didn't put a lot of effort into it, cf https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1683 but the recent article posted on this instance, namely https://lemmy.ml/post/32389687 makes me want to give it another go at some point!
Shit... kind of makes me want to learn Rust now!
Anyway, wonderful write up. No BS, both shortcuts if you just want to the code and in depth links e.g. https://www.beyondlogic.org/usbnutshell/usb1.shtml all written with a fun tone. Plenty of actually useful content showing us all that sure, it is not trivial to write a (USB) driver but it is also probably not as hard as we imagine. Particularly enjoyed the :
libusb and other drivers, namely that there is a myriad of points to start from already, not just writing reverse engineering bits in memory to the new device and hoping it'll workFocus on productivity and pleasure, so make the transition easier :
The entire process must be risk free and fun!
Start kdeconnect-app from a console and share what the actual error message is.
Thanks for sharing, always nice to learn alternative ways to do so!
To answer your question realistically I did history | sed "s/.* //" | sort | uniq -c | sort -n
which returned as first non standard command lr which from my grep lr ~/.bashrc is alias lr="ls -lrth"
Wish I could explain you in detail how that's not correct but I'm actually going to play Clair Obscur on my 2080ti on Debian, sorry!
PS: been playing for years with NVIDIA drivers, including VR games, and sure it's not 100% perfect but neither Windows drivers are. It sure is enough for me to keep on playing (and working) without major issue though. Anyway, gotta play!
require buying additional hardware.
Trade with someone?
Don't be too sad, I'm playing and working daily with an NVIDIA for years now and it's just working.