this post was submitted on 28 Nov 2023
17 points (90.5% liked)
Linux Questions
1149 readers
3 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What kind of computer stuff?
You want my whole resume or just the last 5 years? XD I've worked on stuff from Android OEMs to AAA game dev to SaaS products
The long and the short of it in this case is that peripherals on Linux are far more likely to use drivers that are not maintained by the OEM and thus behave differently under unexpected conditions.
If it worked on *nix but not Windows, or vice versa, I'd point at software first. But since it doesn't work on Mac (*nix based) and Windows (not *nix) but does on Linux (obviously *nix based) it's more likely to be the Linux drivers being probably community maintained and more resilient to faults
This is how I got a very free MacBook Air currently running Fedora Silverblue. Won't run MacOS and have a keyboard, runs every Linux I've ever tried on it just fine. I think I tried the NVRam thing, that vaguely rings a bell...