Fedora General Troubleshooting
August 30 2024 10:47pm • Est. Read Time: 3 MINFramework has done a lot of work to ensure Fedora works upon installation Framework laptops. Some things can be done to make the day-to-day usage experience smoother.
This article will present you with proven techniques for troubleshooting some of the most common Fedora issues. And for anything that does not appear in this article, you will be ready to ask for help by providing all the needed details our community members would need to provide assistance.
(Insert feature) is not working as it once did
Anytime something isn't working when it worked previously, it's helpful to take a step back and consider the following:
- What changed? A software update, new kernel?
- Was a new peripheral, dock, or software application installed?
- If networking related, new VPN or firewall changes or additions?
Determining answers to these questions will make the next section much more productive for you and those trying to help.
Gathering logs effectively
We've recently revamped how we gather logs, thus making it easier to avoid the wall of text.
Features are as follows:
- Last X Minutes (How many minutes ago do you wish to gather logs from)
- Last 24 hours (As it says, 24 hours from this moment of logs)
- From a Specific time range
- Filter previously created log file (keywords or key phrasing)
Asking for help effectively
We recommend reaching out to our amazing Framework community when you're struggling with an Fedora issue. Odds are better than fair that someone who reads your post may have thoughts on what is happening to the cause issue you're experiencing. More often than not, Framework community members may have a solution.
To be effective in getting others to help you, it's essential to provide as much information as possible. Here are some tips to ensure you're able to get assistance quickly.
- Which version of Fedora are you using?
- Mention which desktop environment you're using—for example, GNOME, KDE, MATE, and XFCE. If you don't know, please indicate this.
- Which kernel are you running? This can be determined by opening a terminal window from your applications menu and typing uname -r to see which kernel is being used right now.
- Use bullet points like you see in this article. This prevents the "wall of text" that is difficult to read.
- Outline the course of events from when things were working to when they were not working. Please be specific and provide as much detail as possible. This allows those helping to discover the likely cause of your issue.
Now that we have that out of the way let's look at some common issues and resolutions you can address on your own.
Solutions for common Fedora issues
1. Audio troubleshooting guide
2. Bluetooth troubleshooting guide
3. Webcam troubleshooting guide
4. Wi-Fi troubleshooting guide
6. Optimizing Fedora Battery Life
7. Fedora Fingerprint Troubleshooting
8. Change Default Fedora Kernel
Solutions for protecting your data from loss and system restoration
1. Fedora Home Directory Backups
2. Fedora System Restore Root Snapshots Using Btrfs-Assistant
Docks vs Expansion cards
Our ability to troubleshoot a random dock is limited. We recommend using expansion cards when connecting HDMI or DisplayPort to multiple displays. We can troubleshoot these, replace them if they are not functioning (after additional testing to verify this isn't an operating system issue), and provide a better overall experience for our customers.
Test a Live USB of Fedora
The fastest, easiest way to spot whether or not this is a hardware issue is to try a Live USB of Fedora. Connecting to Wi-Fi for a Live USB install will tell us the following immediately:
- Tested WAP (wireless access point) as working, and your machine likely was able to connect to it.
- Tested headphones or speakers are likely working.
- Oddities with connecting HDMI or DisplayPort are not present when booted to Live USB of Fedora.
In short, if the error you're experiencing on Fedora isn't present on the Live USB installation, the issue isn't hardware is likely something that went sideways with one of the following:
- An update introduced a bug or regression with Fedora.
- A kernel change has been introduced, and there is an issue with that kernel change.