28
Bluetooth problems on my Surface Go 1 running Fedora 39
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Dec 2023
28 points (91.2% liked)
Linux
48335 readers
441 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
My two cents; install uBlue's Microsoft Surface Images. Here you can find the (WIP) documentation on how it differs from other uBlue images. I'm sure the following lines should pique your interest:
For installation, either refer to the dedicated page on installation (from ISO) or follow instructions on how to rebase (from an existing Fedora Atomic installation).
My personal take on what uBlue is, would be that it's how Fedora would love to ship their Atomic variants if they could ship everything without worrying about those things they can't (like hardware acceleration, codecs etc). Furthermore, uBlue even has device-specific images; which is just fantastic if you happen to own such a device.
Last, but definitely not least; it's the best platform in which the transition to Ostree Native Container has been realized. As such, this allows some very unique ways to maintain a distro. For example; if something broke (for whatever reason) on vanilla Fedora Atomic, then... well, you (the uBlue-user) wouldn't even have noticed it. Because that breakage simply never hit your device. Instead, uBlue's maintainers noticed the issue -> somehow applied changes to the image so that the image doesn't ship the issue (by either not shipping the breakage inducing update of the specific package or by shipping the workaround/fix with the image) -> the very next time you update your system (which happens automatically in the background by default) you just go on with your life as if nothing had happened in the first place 😅. So, in a sense, your system is managed such that breaking changes/updates don't hit you; while they do hit non-uBlue users.
And I haven't even touched upon how uBlue enhances tinkering or how it allows one to manage (a fleet of) self-customized images etc.
In case you're still not sure if you'd like to use a derivative rather than the original, then it's at least worth noting that uBlue is mentioned in Fedora's documentation.
Thanks for the thorough answer. I’ll probably just try the surface kernel but I’ll look more into what ublue is.
It has been my pleasure. Though, most of it was part of the suggestion to use uBlue 😅. I hope you'll manage regardless of how you go about it 😊!
Fair.
I'm eager to help out if required 😜.