my wifi driver is contantly crashing on linux (fedora). i see this in the logs: firmware…
- User
my wifi driver is contantly crashing on linux (fedora). i see this in the logs: firmware failed to ack driver for leaving Deep Power mode kernel: WARNING: CPU: 1 PID: 12324 at drivers/net/wireless/realtek/rtw88/ps.c:105 rtw_power_mode_change+0xf4/0x130 [rtw88_core] how to fix it?
- Assistant
I understand you're dealing with repeated WiFi driver crashes on Fedora Linux, specifically with the Realtek rtw88 driver. The error message you're seeing in the logs indicates a problem with the firmware not acknowledging the driver's request to exit "Deep Power Mode." This is a known issue with some Realtek WiFi adapters, often related to power management conflicts, driver bugs, or firmware incompatibilities.
I'll walk you through a step-by-step troubleshooting and fix process. These steps are based on common solutions for rtw88 driver issues. Before we start, note that this involves command-line operations, so make sure you're comfortable with that or have someone to help.
1. Gather More Information About Your System
First, let's confirm the details of your hardware and software setup. This will help pinpoint the exact issue.
-
Check your WiFi adapter and driver:
lspci -k | grep -i networkThis will show your network card (e.g., something like "Realtek RTL8822BE") and the driver in use (e.g., rtw88_core).
-
Check kernel version and logs:
uname -r # Shows your kernel version journalctl -b -p err | grep rtw88 # Shows recent logs related to rtw88 dmesg | grep rtw88 # Another way to view kernel messagesLook for any additional errors that might provide more clues, like the exact firmware version or other warnings.
If your adapter is a Realtek model (e.g., RTL8821CE, RTL8822BE), the rtw88 driver is the stock one in the Linux kernel, so updates might come from kernel patches.
2. Update Your System
Many driver issues are resolved by updating Fedora, as newer kernel versions often include fixes for hardware compatibility.
- Run the following commands:
sudo dnf update # Updates all packages, including the kernel sudo reboot # Reboot to apply updates - After rebooting, check if the issue persists by monitoring the logs (as in Step 1).
If you're on an older kernel, consider switching to the latest one. Fedora typically uses the latest stable kernels, but if you're on a long-term support version, you might need to enable updates via
dnf.3. Disable Power Management Features
The error specifically mentions "Deep Power Mode," which is part of the WiFi adapter's power-saving functionality. This can cause crashes if the hardware or firmware doesn't handle it well.
-
Temporarily disable WiFi power saving: First, identify your WiFi interface (e.g., wlan0 or wlo1) using:
ip link showThen, disable power management for that interface:
sudo iwconfig <interface> power off # e.g., sudo iwconfig wlan0 power offTest your WiFi connection and see if the crashes stop. This change is temporary and will reset on reboot.
-
Make it permanent: Edit the module options for rtw88_core. Create or edit a file in
/etc/modprobe.d/:sudo nano /etc/modprobe.d/rtw88.confAdd the following line:
options rtw88_core debug=0 aspm=0 # Disables ASPM and some debuggingSave the file, then reload the driver:
sudo modprobe -r rtw88_core # Unload the driver (might disconnect WiFi) sudo modprobe rtw88_core # Reload it sudo reboot # Reboot to apply changesThis disables features like ASPM (Active State Power Management), which is often the culprit in these errors.
-
Alternative: Disable kernel-wide power management tweaks: Edit your GRUB configuration to add kernel parameters:
sudo nano /etc/default/grubFind the line starting with
GRUB_CMDLINE_LINUX_DEFAULTand addpcie_aspm=off(oraspm=off) to the quotes, e.g.:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off"Save, then update GRUB:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg sudo rebootThis globally disables ASPM for PCIe devices, which might resolve the issue but could slightly increase power consumption.
4. Update or Reinstall the Driver/Firmware
If updates don't help, the problem might be with the driver or firmware itself.
-
Check for firmware updates: Realtek firmware is often managed by the
linux-firmwarepackage. Ensure it's up to date:sudo dnf install linux-firmware sudo dnf update linux-firmwareReboot and check logs again. If the firmware is missing, you might see errors like "firmware not found." In that case, you can try installing additional firmware packages:
sudo dnf install kernel-modules-extra # For extra kernel modules -
Reinstall the rtw88 driver: The rtw88 driver is part of the kernel, so you might need to compile or update it manually if Fedora's version is buggy.
- First, check for DKMS (Dynamic Kernel Module Support) packages:
sudo dnf install rtw88-dkms # If available in your Fedora repos - If that's not available, you can try building the driver from source:
- Install build tools:
sudo dnf install kernel-devel kernel-headers gcc make git dkms - Clone the rtw88 repository (if needed):
This is more advanced and might not be necessary if your kernel is recent.git clone https://github.com/lwfinger/rtw88.git cd rtw88 make sudo make install sudo modprobe rtw88_core
- Install build tools:
- First, check for DKMS (Dynamic Kernel Module Support) packages:
-
Blacklist and test alternatives: If rtw88 is causing persistent issues, you could try blacklisting it and using a different driver (if available):
sudo nano /etc/modprobe.d/blacklist-rtw88.confAdd:
blacklist rtw88_coreSave, reboot, and see if your WiFi works with a fallback driver. However, for Realtek cards, this might not be an option, and you'd need to resolve the rtw88 issue.
5. Test for Hardware Issues
If the above steps don't work, the problem might be hardware-related:
- Try a different kernel: Boot into an older kernel version (if available) via your bootloader (e.g., GRUB) and see if the issue persists. You can also install a different kernel:
sudo dnf install kernel-lts # For a long-term support kernel - Test on another device or OS: If possible, boot into a live USB of another Linux distro (e.g., Ubuntu) or Windows to see if the WiFi works there. This could indicate a hardware fault.
- Reset or reseat hardware: If you're using a laptop, try resetting the WiFi card or updating your BIOS/UEFI firmware from your manufacturer's website.
6. Seek Further Help
If none of these steps resolve the issue:
- Check for known bugs: Search for your error message on:
- Fedora forums (e.g., ask.fedoraproject.org)
- Kernel bug tracker (bugzilla.kernel.org)
- Realtek or Linux Wireless forums For example, search for "rtw88 Deep Power Mode firmware ack" on Google.
- Report the bug: If it's a kernel issue, report it on the Fedora bug tracker or kernel.org. Provide your logs, kernel version, and hardware details.
- Community support: Post on Reddit (e.g., r/Fedora or r/linuxquestions) with your full logs.
Final Notes
- Backup first: Before making changes, back up important data in case something goes wrong.
- Safety: The steps above are generally safe, but if you're unsure, start with just updating and disabling power management.
- Expected outcome: In many cases, disabling power management or updating the kernel resolves rtw88 crashes. If your hardware is older or unsupported, you might need to consider a USB WiFi adapter as a workaround.
If you provide more details (e.g., the output of
lspci -kor your kernel version), I can give more tailored advice! -
- User
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter DeviceName: WLAN
Kernel driver in use: rtw_8821ce Kernel modules: rtw88_8821ce, wlthis is the output of lspci
- Assistant
Thank you for providing the output from
lspci -k. This confirms you're using a Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter, with thertw_8821cedriver (part of the rtw88 family) currently loaded. Thewlmodule listed as an available kernel module is typically for Broadcom devices, so it's not relevant here—stick with the rtw88 driver for your Realtek hardware.The error you're seeing ("firmware failed to ack driver for leaving Deep Power mode") is a common issue with RTL8821CE and similar Realtek adapters on Linux. It often stems from incompatibilities between the driver, firmware, and kernel power management features. Based on your setup, I'll refine the troubleshooting steps from my previous response to focus on this specific hardware.
Here's a step-by-step guide to fix or mitigate the problem. Start with the simplest steps and work your way down.
1. Update Your System and Kernel
Fedora regularly releases kernel updates that include fixes for driver issues like this. Newer kernels often have patches for rtw88-related problems.
- Run the following commands:
sudo dnf upgrade --refresh # Refresh and upgrade all packages, including the kernel sudo dnf install kernel # Ensure the latest kernel is installed sudo reboot # Reboot to apply updates - After rebooting, check if the crashes continue by monitoring the logs:
dmesg | grep rtw88 # Look for any rtw88-related errors journalctl -b -p err | grep rtw88 # Check recent boot logs - If you're on an older kernel (e.g., check with
uname -r), consider booting into a newer one if multiple options are available in your GRUB menu. If the issue persists, proceed to the next steps.
2. Disable Power Management for the WiFi Adapter
The "Deep Power Mode" error suggests power-saving features are causing conflicts. Disabling them is often the quickest fix.
-
Temporarily disable power saving: First, identify your WiFi interface (e.g., wlan0 or wlo1):
ip link show # Look for the wireless interface, e.g., wlo1Then, disable power management:
sudo iwconfig <interface> power off # Replace <interface> with your interface, e.g., sudo iwconfig wlo1 power offTest your WiFi connection and monitor for crashes. This change is temporary and won't survive a reboot.
-
Make it permanent: Edit the module options for the rtw88 driver:
sudo nano /etc/modprobe.d/rtw88.confAdd the following lines:
options rtw88_core aspm=0 debug=0 # Disables ASPM and some debugging features options rtw_8821ce powersave=0 # Specifically disable powersave for RTL8821CESave the file, then apply the changes:
sudo modprobe -r rtw_8821ce # Unload the driver (this will disconnect WiFi temporarily) sudo modprobe rtw_8821ce # Reload the driver sudo reboot # Reboot to ensure it takes effectAfter rebooting, check the logs again to see if the error is gone.
3. Update or Verify Firmware
The RTL8821CE requires specific firmware files, which are provided by the
linux-firmwarepackage. If the firmware is outdated or mismatched, it can cause the "ack" error.- Ensure the firmware is installed and up to date:
sudo dnf install linux-firmware # Install if not already sudo dnf upgrade linux-firmware # Update to the latest version - Check if the firmware is loading correctly:
If you see errors about missing firmware, it might mean the file isn't present. You can try reinstalling:dmesg | grep firmware # Look for messages like "rtw_8821ce: firmware: direct-loading firmware rtw88/rtw8821c_fw.bin"sudo dnf reinstall linux-firmware sudo reboot - If the issue persists, you might need to manually download and install the latest firmware from the Linux Firmware repository:
- Install git if you don't have it:
sudo dnf install git - Clone and copy the firmware:
git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git sudo cp linux-firmware/rtw88/*.bin /lib/firmware/rtw88/ sudo depmod -a # Update module dependencies sudo modprobe -r rtw_8821ce # Unload and reload sudo modprobe rtw_8821ce sudo reboot
- Install git if you don't have it:
4. Test with Kernel Parameters or a Different Kernel
If the above doesn't help, try tweaking kernel-wide settings or switching kernels.
-
Add kernel parameters to disable power management globally: Edit your GRUB configuration:
sudo nano /etc/default/grubFind the line
GRUB_CMDLINE_LINUX_DEFAULTand addpcie_aspm=offandrtw88_core.aspm=0inside the quotes, e.g.:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off rtw88_core.aspm=0"Save, then update GRUB:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg sudo reboot -
Try a different kernel version: Install a Long Term Support (LTS) kernel to see if it's more stable:
sudo dnf install kernel-lts # Installs an older, more stable kernel sudo reboot # Select the new kernel from the GRUB menu if it doesn't boot automaticallyTest and compare behavior. If the LTS kernel works better, you can stick with it or report the issue for the main kernel.
5. Advanced Options: Blacklist or Alternative Drivers
If the crashes continue, consider these more advanced steps:
-
Force the driver to load with specific options: You can try loading the driver with aggressive debugging or fixes:
sudo modprobe -r rtw_8821ce sudo modprobe rtw_8821ce debug=1 # Enables debugging for more logsThen, check
dmesgfor detailed output. However, if this doesn't help, revert it. -
Blacklist the driver (as a last resort): If rtw88 is unusable, you could try blacklisting it to force the system to fall back to another driver (though this is unlikely to work well for RTL8821CE):
sudo nano /etc/modprobe.d/blacklist-rtw88.confAdd:
blacklist rtw_8821ce blacklist rtw88_coreSave, reboot, and see if WiFi works (it might not). If it doesn't, remove the blacklist file and reboot again.
-
Consider a proprietary driver: Although not ideal, if you're desperate, you could try the
wlmodule (from Broadcom), but it's not designed for Realtek hardware and might not work:sudo modprobe wl # Try loading itCheck if WiFi functions, but expect instability. To make it persistent, you'd need to blacklist rtw88 as above.
6. Test for Hardware or Persistent Issues
If none of the above resolves the problem:
- Hardware check: The RTL8821CE can have issues with certain laptops or BIOS versions. Try updating your BIOS/UEFI from your manufacturer's website (e.g., Dell, HP). Also, test the adapter in another system if possible.
- Monitor and report: Keep an eye on logs with
journalctl -f | grep rtw88during usage. If the issue persists, search for "RTL8821CE rtw88 Deep Power Mode" on forums like Reddit (r/Fedora) or the Linux Wireless mailing list. Report the bug on the Fedora Bugzilla (bugzilla.redhat.com) or kernel bug tracker, including:- Your kernel version (
uname -r) - Full
lspci -koutput - Relevant dmesg/journalctl logs
- Your kernel version (
This should get you closer to a resolution. The RTL8821CE is generally well-supported, and disabling power management often fixes these crashes. If you run into any errors during these steps or need more details (e.g., output from commands), let me know!
- Run the following commands:
- User
someone suggested the following
- Assistant
It seems like your message got cut off— you mentioned "someone suggested the following" but didn't include the details of the suggestion. To provide the best help, I need to know what was recommended. For example, was it something like compiling a custom driver, using a specific kernel parameter, or installing additional software?
Once you share the full suggestion, I can evaluate it for your setup (Realtek RTL8821CE on Fedora), check if it's safe and effective, and guide you through it step by step. Common suggestions for rtw88 issues include things like:
- Disabling power management (which I already recommended).
- Updating firmware manually.
- Compiling the driver from source.
- Using kernel tweaks or blacklisting modules.
If you provide the details, I'll help you assess whether it's a good idea and how to implement it safely. For now, if you want to proceed with the troubleshooting from my previous response, let me know how that went or if you have any updates! 😊
- User
Create /etc/modprobe.d/rtw8852be.conf and write these lines:
options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y options rtw89pci disable_aspm_l1=y disable_aspm_l1ss=y options rtw89_core disable_ps_mode=y options rtw89core disable_ps_mode=y
- Assistant
Thank you for sharing the suggestion you received. It looks like someone recommended creating a modprobe configuration file to tweak options for the rtw89 driver, which is used for newer Realtek WiFi adapters (like the RTL8852BE). However, based on your hardware (Realtek RTL8821CE with the rtw88 driver), this configuration doesn't directly apply. Let me break this down and provide a tailored solution to avoid any potential issues.
Why This Suggestion Might Not Work for You
- Driver Mismatch: Your WiFi adapter uses the rtw88 driver (specifically rtw_8821ce), which is part of the older rtw88 family. The options in the suggestion (e.g.,
rtw89_pci,rtw89pci,rtw89_core) are for the rtw89 driver, which is designed for more recent Realtek hardware like RTL8852BE or RTL8852AE. Applying these to your system won't have any effect or could lead to errors if the modules don't exist. - Potential Risks: If you create this file as-is, it might not cause harm, but it could confuse the system or conflict with your actual driver. For example, if the rtw89 modules aren't loaded, these options will simply be ignored. Still, it's best to use configurations specific to your hardware to ensure stability.
Since your issue involves the rtw88 driver and "Deep Power Mode" errors, we should focus on options that target rtw88_core or rtw_8821ce. In my previous response, I already suggested creating a file like
/etc/modprobe.d/rtw88.confwith appropriate options for your driver. I'll refine that here based on common fixes for RTL8821CE.Recommended Steps for Your Setup
To address the crashing issue, let's create a configuration file tailored to the rtw88 driver. This will disable features like ASPM (Active State Power Management) and power-saving modes, which are often the culprits in these errors.
Step 1: Create the Configuration File
Instead of
rtw8852be.conf, we'll use a file namedrtw88.confto match your driver. Here's how to do it:-
Open a terminal and create the file:
sudo nano /etc/modprobe.d/rtw88.conf -
Add the following lines to the file. These options are based on known fixes for rtw88 drivers:
options rtw88_core aspm=0 debug=0 # Disables ASPM and reduces debugging output options rtw_8821ce powersave=0 # Disables power-saving mode for your specific adapter- Explanation of options:
aspm=0: Disables ASPM, which can cause the "Deep Power Mode" errors by preventing power state conflicts.debug=0: Reduces excessive logging, which might help stabilize the driver.powersave=0: Specifically turns off power-saving features for the rtw_8821ce module, addressing the firmware acknowledgment issue.
- Explanation of options:
-
Save the file (in nano, press Ctrl+O, then Enter, and Ctrl+X to exit).
Step 2: Apply the Changes
After creating the file, you need to reload the driver and reboot to apply the settings:
sudo modprobe -r rtw_8821ce # Unload the driver (this will temporarily disconnect WiFi) sudo modprobe rtw_8821ce # Reload the driver with the new options sudo reboot # Reboot to ensure everything takes effectStep 3: Verify and Test
Once your system reboots:
- Check if the crashes have stopped by monitoring the logs:
dmesg | grep rtw88 # Look for any rtw88-related errors journalctl -b -p err | grep rtw88 # Check recent boot logs - Test your WiFi connection under normal usage (e.g., browsing, streaming) to see if the issue persists.
- If the problem continues, run:
ip link show # Confirm your WiFi interface is up iwconfig <interface> # Replace <interface> with your WiFi interface (e.g., wlo1) to verify power management is off
If You Still Want to Try the Original Suggestion
If you're certain this suggestion was meant for your system (e.g., perhaps you have multiple WiFi adapters or the person misunderstood your hardware), you could create the file as suggested, but I strongly advise against it for the reasons above. Here's how, with caution:
-
Create the file:
sudo nano /etc/modprobe.d/rtw8852be.conf -
Add the lines you provided:
options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y options rtw89pci disable_aspm_l1=y disable_aspm_l1ss=y options rtw89_core disable_ps_mode=y options rtw89core disable_ps_mode=y -
Apply and test:
sudo modprobe -r rtw89_pci # If the module exists; this might fail if it's not loaded sudo depmod -a # Update module dependencies sudo rebootAfter rebooting, check the logs as above. However, if your system doesn't have the rtw89 modules, this will likely do nothing, and you should remove the file:
sudo rm /etc/modprobe.d/rtw8852be.conf sudo reboot
Final Advice
- Why This Might Help: For your RTL8821CE, the customized rtw88.conf I recommended is more likely to resolve the issue by directly targeting the power management problems you're seeing.
- Backup and Safety: Before making changes, back up any important data. If something goes wrong, you can revert by deleting the configuration file and rebooting.
- Next Steps if Unresolved: If the crashes continue after trying these steps, provide more details like the output of
dmesg | grep rtw88oruname -r(your kernel version), and we can dig deeper. You might also consider reporting this as a bug on the Fedora Bugzilla or checking for kernel updates.
Let me know how this goes or if you have any questions! 😊
- Driver Mismatch: Your WiFi adapter uses the rtw88 driver (specifically rtw_8821ce), which is part of the older rtw88 family. The options in the suggestion (e.g.,
- User
i get this error: modprobe: FATAL: Module rtw_8821ce not found. 6.14.4 (kernel)
- Assistant
It looks like you're encountering an error when trying to unload or load the
rtw_8821cemodule usingmodprobe. The message "modprobe: FATAL: Module rtw_8821ce not found" indicates that the kernel can't locate this module, which is part of the rtw88 driver for your Realtek RTL8821CE adapter. You also mentioned your kernel version as "6.14.4," but I suspect this might be a typo or shorthand—common kernel versions are like 6.1.x, 6.5.x, or 6.6.x. For example, it could be 6.1.4 or 6.4.14. Let's clarify and fix this step by step.Why This Error Might Be Happening
- Module Not Available: The rtw_8821ce module might not be compiled or installed for your current kernel. This can occur if:
- You're using a kernel version that doesn't include the rtw88 driver (though it's standard in Fedora kernels).
- There's a mismatch after a kernel update, or the module isn't loading properly.
- The module name is correct, but it's not present in your loaded kernel modules.
- Kernel Version Note: As of now, the latest stable kernels are around 6.6.x, and 6.14.4 isn't a standard release (it might be a custom or testing kernel). Please confirm your exact kernel version with
uname -rto ensure we're on the right track.
Here's how to troubleshoot and resolve this. Start with the basics and work through the steps.
Step 1: Confirm Your Kernel Version and Module Status
First, let's verify your setup to make sure we're dealing with the correct kernel and modules.
-
Run these commands:
uname -r # This will show your exact kernel version, e.g., 6.1.4-1.fc37 lsmod | grep rtw # Check if any rtw88-related modules are currently loaded modinfo rtw_8821ce # Try to get info about the module; if it's not found, this will confirm the error- If
lsmod | grep rtwshows something likertw88_core, the driver is partially loaded, butrtw_8821cemight be missing. - If
modinfo rtw_8821cealso says "module not found," we need to ensure the driver is installed for your kernel.
- If
Step 2: Update Your System
This is often the simplest fix. Fedora kernels include the rtw88 driver, but if your kernel is outdated or corrupted, the modules might not be available.
-
Run the following:
sudo dnf upgrade --refresh # Update all packages, including the kernel sudo dnf reinstall kernel-modules kernel-modules-extra # Reinstall kernel modules to ensure they're present sudo reboot # Reboot into the latest kernel -
After rebooting, check again:
uname -r # Confirm you're on the updated kernel lsmod | grep rtw # See if rtw_8821ce or rtw88_core appears modinfo rtw_8821ce # Verify if the module is now found
If the module still isn't found, proceed to the next steps.
Step 3: Load the Core Module and Try Again
The rtw_8821ce module is a sub-module of rtw88_core. Sometimes, you need to load the core first.
-
Try loading the core module:
sudo modprobe rtw88_core # Load the main rtw88 module sudo modprobe rtw_8821ce # Now try loading your specific module -
If this works, great! If not, and you still get "module not found," it means the driver isn't available for your kernel. In that case:
- Check for errors in the logs:
dmesg | grep rtw # Look for any rtw88-related errors journalctl -b -p err | grep rtw # Check boot logs - If you see errors like "firmware not found," go back to my previous suggestions for updating firmware.
- Check for errors in the logs:
Step 4: Reinstall or Ensure the Driver is Present
If the module is still missing, you might need to ensure the rtw88 driver is properly installed. For Fedora, this is typically handled by the kernel, but you can force a reinstall or build it if necessary.
-
Reinstall kernel packages:
sudo dnf reinstall kernel-devel kernel-headers linux-firmware # Reinstalls necessary components sudo depmod -a # Rebuild module dependencies sudo reboot -
If that doesn't work, try building the driver from source: This is more advanced but can be done if your kernel doesn't include the module. First, install build tools:
sudo dnf install kernel-devel kernel-headers gcc make git dkmsThen, clone and build the rtw88 driver:
git clone https://github.com/lwfinger/rtw88.git cd rtw88 make sudo make install sudo modprobe rtw88_core # Load the core sudo modprobe rtw_8821ce # Try loading your moduleIf this succeeds, the driver should now be available. You can make it persistent by adding it to DKMS if needed, but for now, test it.
Step 5: Test with a Different Kernel
If the issue persists on your current kernel (e.g., 6.14.4, which might be unstable or custom), try booting into a different one:
- Install a stable kernel if you don't have one:
sudo dnf install kernel-lts # Installs a Long Term Support kernel, e.g., 5.15.x sudo reboot # From the GRUB menu, select the new kernel if it doesn't boot automatically - Once booted, repeat Step 1 to check for the module.
Step 6: If All Else Fails
-
Check for Hardware Conflicts: Ensure your WiFi adapter is properly detected:
lspci -k | grep -i network # Confirm it's still showing as RTL8821CEIf it's not, there might be a hardware issue—try reseating the card or testing on another system.
-
Alternative Workarounds: If you can't get rtw_8821ce working, you could:
- Disable WiFi power management as a temporary fix (even without reloading the module):
sudo iwconfig <interface> power off # Replace <interface> with your WiFi interface, e.g., wlo1 - Use a USB WiFi adapter as a backup if this hardware is unreliable.
- Disable WiFi power management as a temporary fix (even without reloading the module):
-
Seek Community Help: This could be a kernel-specific bug. Report it on:
- Fedora Bugzilla: bugzilla.redhat.com
- Provide details like your kernel version,
lspcioutput, anddmesglogs.
Let me know the output of the commands above (e.g., from
uname -rordmesg | grep rtw), and I'll refine these steps further. We're getting closer—hang in there! 😊 - Module Not Available: The rtw_8821ce module might not be compiled or installed for your current kernel. This can occur if:
- User
rtw88_8821ce 12288 0 rtw88_8821c 98304 1 rtw88_8821ce rtw88_pci 40960 1 rtw88_8821ce rtw88_core 319488 2 rtw88_pci,rtw88_8821c mac80211 1912832 2 rtw88_pci,rtw88_core cfg80211 1511424 3 wl,rtw88_core,mac80211
- Assistant
Thank you for providing the output from
lsmod | grep rtw(or similar). This shows that the rtw88-related modules are indeed loaded on your system:rtw88_8821ce 12288 0 rtw88_8821c 98304 1 rtw88_8821ce rtw88_pci 40960 1 rtw88_8821ce rtw88_core 319488 2 rtw88_pci,rtw88_8821c mac80211 1912832 2 rtw88_pci,rtw88_core cfg80211 1511424 3 wl,rtw88_core,mac80211This is good news—it confirms that the driver modules for your Realtek RTL8821CE adapter are present and active. However, the error you encountered ("modprobe: FATAL: Module rtw_8821ce not found") suggests there might be a mismatch in the module name you're using. Based on your output, the correct module name is
rtw88_8821ce, notrtw_8821ce. This could be a simple typo or variation in how the module is referenced.Let me explain and guide you through fixing this so you can apply the configuration we discussed earlier.
Key Issue: Module Name Mismatch
- From your initial
lspcioutput: "Kernel driver in use: rtw_8821ce" and "Kernel modules: rtw88_8821ce, wl". - The
lsmodoutput confirms the module is loaded asrtw88_8821ce. - When you ran
modprobe rtw_8821ce, it failed because the system expectsrtw88_8821ce. This is a common gotcha with kernel modules—names can have subtle differences.
We'll correct this in your commands and configuration file.
Step-by-Step Fix
Let's revisit the configuration for your rtw88 driver and use the correct module name. The goal is to disable power management features to resolve the crashing issue.
Step 1: Edit the Configuration File with the Correct Module Name
We previously created
/etc/modprobe.d/rtw88.conf, but I suggested options forrtw_8821ce, which should be updated tortw88_8821ce.-
Open the file for editing:
sudo nano /etc/modprobe.d/rtw88.conf -
Update the contents to match the correct module name. Replace the file with this:
options rtw88_core aspm=0 debug=0 # Disables ASPM and debugging for the core module options rtw88_8821ce powersave=0 # Disables power-saving for your specific module- Save the file (in nano, press Ctrl+O, then Enter, and Ctrl+X to exit).
Step 2: Reload the Modules
Now, use the correct module name when reloading.
-
Unload and reload the modules:
sudo modprobe -r rtw88_8821ce # Unload the specific module (this will temporarily disconnect WiFi) sudo modprobe -r rtw88_core # Unload the core module if needed sudo modprobe rtw88_core # Load the core module first sudo modprobe rtw88_8821ce # Load your specific module -
If this succeeds without errors, your WiFi should reconnect. If you get any errors, check the logs immediately:
dmesg | grep rtw88 # Look for rtw88-related messages
Step 3: Reboot and Verify
-
Reboot to ensure the changes persist:
sudo reboot -
After rebooting:
- Check if the modules are loaded:
lsmod | grep rtw # Should show the same output as above - Monitor for crashes:
dmesg | grep rtw88 # Check for errors journalctl -b -p err | grep rtw88 # Check boot logs - Test your WiFi: Connect to a network and use it normally to see if the "Deep Power Mode" errors are gone.
- Check if the modules are loaded:
Step 4: Confirm Power Management is Disabled
To double-check that power saving is off:
- Identify your WiFi interface (e.g., wlo1):
ip link show - Verify the settings:
Look for "Power Management:off" in the output. If it's not off, you can force it:sudo iwconfig <interface> # e.g., sudo iwconfig wlo1sudo iwconfig <interface> power off
What If It Still Doesn't Work?
- If modprobe fails again: Double-check your kernel version with
uname -r. If you're on a non-standard kernel (like 6.14.4, which isn't official), consider switching to a stable one:sudo dnf install kernel-lts # Install a Long Term Support kernel sudo reboot # Select it from GRUB if needed - Firmware issues: If you see new errors in
dmesg, it might relate to firmware. Reinstall it as before:sudo dnf reinstall linux-firmware sudo reboot - Persistent problems: If the crashes continue, provide the full output of:
This will help pinpoint any deeper issues.uname -r dmesg | grep rtw88 lsmod | grep rtw
You're making progress—the modules are there, and correcting the name should resolve the modprobe error. Let me know how this goes or if you run into any new errors! 😊
- From your initial
- User
should i use the driver from https://github.com/lwfinger/rtw88
- Assistant
Yes, you could consider using the driver from https://github.com/lwfinger/rtw88 as a last resort if the built-in rtw88 driver in your Fedora kernel continues to cause issues (like the "Deep Power Mode" crashes). However, I generally recommend against it unless you've exhausted simpler fixes, as Fedora's stock kernel already includes the rtw88 driver, and using a custom version can introduce complications. Let me explain the pros, cons, and steps so you can make an informed decision.
Pros and Cons of Using the GitHub Driver
-
Pros:
- The repository is maintained by Larry Finger, a well-known contributor to Linux wireless drivers, and it often includes newer patches or fixes that haven't yet been merged into the main Linux kernel.
- It might resolve specific bugs with your RTL8821CE adapter, such as power management issues, if the stock driver is outdated or problematic for your kernel version.
-
Cons:
- Compatibility risks: This is an out-of-tree driver, meaning it's not part of your kernel. It could conflict with kernel updates, leading to boot issues or WiFi instability. Fedora's package manager might overwrite it during updates.
- Complexity: Building and installing it requires compiling from source, which involves dependencies and potential errors if your system isn't set up correctly.
- Not always necessary: Since your
lsmodoutput shows the rtw88 modules are already loaded, the problem might be fixable with configuration tweaks (as we've been trying) rather than replacing the driver. - Support: If something goes wrong, debugging a custom driver can be harder, and it might not be compatible with future kernel versions.
Before proceeding, try the configuration changes I suggested in my last response (e.g., editing
/etc/modprobe.d/rtw88.confand reloading modules). If that resolves your crashes, you don't need to go this route. Only build from GitHub if you're still facing issues.When to Use This Driver
- Use it if:
- You've confirmed the stock driver is buggy on your specific kernel (e.g., via error logs).
- You've tested with kernel updates, firmware reinstalls, and module options without success.
- Avoid it if:
- Your system is stable enough after the tweaks we've discussed.
- You're not comfortable with compiling software, as it could lead to errors.
If you decide to try it, follow the steps below carefully. Make sure to back up your system first!
Steps to Build and Install the Driver from GitHub
Here's a safe, step-by-step guide. This assumes you're on Fedora and have a basic understanding of the terminal. If any step fails, stop and share the error output for more help.
1. Prepare Your System
-
Update your system to ensure you have the latest tools:
sudo dnf update sudo dnf install git kernel-devel kernel-headers gcc make dkms patch # Install build dependencies -
Check your kernel version to ensure compatibility:
uname -r # e.g., 6.1.4 or whatever yours isThe GitHub driver should work with recent kernels, but if you're on an older or custom one (like 6.14.4, which isn't standard), consider switching to a stable kernel first:
sudo dnf install kernel-lts sudo reboot # Select the new kernel from GRUB if needed -
Backup: Before proceeding, back up important data and note that you might need to blacklist the stock driver temporarily.
2. Clone and Build the Driver
-
Clone the repository:
git clone https://github.com/lwfinger/rtw88.git cd rtw88 -
Build the driver:
make # Compile the driver (this might take a few minutes) sudo make install # Install the compiled modules- If you encounter errors during
make, it could be due to missing dependencies or kernel mismatches. Common errors include "No rule to make target" or compilation failures—check the output and ensure your kernel headers match your running kernel.
- If you encounter errors during
-
Load the driver:
sudo modprobe -r rtw88_8821ce # Unload the stock module if it's loaded sudo modprobe rtw88_core # Load the core module from the new driver sudo modprobe rtw88_8821ce # Load your specific module
3. Verify and Test
-
Check if the driver loaded successfully:
lsmod | grep rtw # Should show the rtw88 modules dmesg | grep rtw88 # Look for any errors or success messages -
Test your WiFi:
- Connect to a network and monitor for crashes.
- Run:
ip link show # Ensure your WiFi interface (e.g., wlo1) is up dmesg | grep firmware # Check for firmware-related errors - If the driver works, apply your previous configuration (e.g., disable power management) by editing
/etc/modprobe.d/rtw88.confas before.
-
Reboot and test again:
sudo rebootAfter rebooting, confirm the custom driver is in use and that the crashes are gone.
4. Make It Persistent (Optional)
- If the driver works, you can make it load automatically on boot using DKMS (Dynamic Kernel Module Support), which helps with kernel updates:
This ensures the driver rebuilds for new kernels. However, monitor for conflicts.sudo dkms add . # In the rtw88 directory sudo dkms build rtw88/1.0 # Adjust version if needed sudo dkms install rtw88/1.0
5. Uninstalling the Custom Driver
If things go wrong (e.g., WiFi stops working or you get new errors), remove the custom driver and revert to the stock one:
- Unload the modules:
sudo modprobe -r rtw88_8821ce sudo modprobe -r rtw88_core - Remove the installed files:
cd ~/rtw88 # Back to the cloned directory sudo make uninstall # Uninstall the driver sudo rmmod rtw88_core # Force remove if needed - Reboot and ensure the stock driver loads:
sudo dnf reinstall kernel-modules # Reinstall stock modules sudo reboot - If you used DKMS, remove it:
sudo dkms remove rtw88/1.0 sudo dkms ldtarball # Clean up
Final Advice
- Start simple: Before building from GitHub, confirm if the stock driver works with the corrected module options. If your WiFi is functional now after my previous steps, stick with that to avoid unnecessary risks.
- Monitor for issues: After installing the custom driver, keep an eye on system logs and test thoroughly. If you experience new problems, it's easier to revert.
- Seek help if needed: If you run into errors during building or testing, share the output (e.g., from
makeordmesg), and I'll assist. You could also report any ongoing issues on the Fedora forums or the GitHub repository's issues page. - Long-term solution: Ideally, wait for Fedora to update its kernel with fixes, or contribute your findings to the upstream kernel for better support.
Let me know if you'd like to proceed or if you have more details! 😊
-
- User
options rtw88_core aspm=0 debug=0 # Disables ASPM and debugging for the core module options rtw88_8821ce powersave=0 # Disables power-saving for your specific module vs sudo iw dev wlan0 set power_save off
- Assistant
Absolutely, I'll break this down for you step by step. You're comparing two approaches to address the WiFi driver crashes on your Realtek RTL8821CE adapter:
-
Editing the modprobe configuration file (
/etc/modprobe.d/rtw88.conf) with options like:options rtw88_core aspm=0 debug=0 options rtw88_8821ce powersave=0 -
Using the command-line tool to disable power save mode directly:
sudo iw dev wlan0 set power_save off
These methods both aim to disable power-saving features that could be causing your "Deep Power Mode" errors, but they work at different levels and have different implications. I'll explain the differences, pros and cons, and recommend how to proceed.
Key Differences
-
Level of Operation:
-
Modprobe options: These are kernel module parameters that configure the rtw88 driver itself when it's loaded. They target the driver's behavior at a low level:
aspm=0: Disables ASPM (Active State Power Management), a hardware feature that manages power states for PCIe devices like your WiFi card.debug=0: Turns off debugging logs, which can reduce system noise and potential overhead.powersave=0: Specifically disables power-saving modes in the rtw88_8821ce module, addressing the firmware acknowledgment issues you're seeing.- This method is applied when the driver loads (e.g., at boot), so it's more "permanent" and integrated into the driver's operation.
-
iw command: This uses the
iwtool to directly control the WiFi interface's power management settings at the hardware level. It tells the WiFi device (e.g., wlan0) to stop using power-saving features immediately, without altering the driver itself. It's a runtime adjustment, not a driver configuration.
-
-
Persistence:
- Modprobe options: Persistent across reboots. Once set, the driver will always load with these options.
- iw command: Not persistent. The setting will be lost after a reboot, network restart, or if the interface is brought down and up.
-
Scope:
- Modprobe options: Applies broadly to the driver, potentially fixing deeper issues like firmware interactions or kernel-level power management conflicts.
- iw command: Applies only to the specific WiFi interface (e.g., wlan0), making it a more targeted, quick fix for power save mode.
Pros and Cons
Here's a quick comparison to help you decide:
Aspect Modprobe Options (e.g., in rtw88.conf) iw Command (e.g., sudo iw dev wlan0 set power_save off) Pros - Persistent solution; no need to run commands manually.- Addresses driver-level issues, which might fully resolve crashes.- Reduces the chance of the problem recurring after reboots. - Immediate effect; no reboot required.- Easy to test without permanent changes.- Less intrusive if you're unsure about driver tweaks. Cons - Requires a reboot to take effect.- If the module fails to load, it might not apply (e.g., due to earlier errors).- Could have unintended side effects on power management if not configured correctly. - Not persistent; you'd need to automate it for long-term use.- Might only mask symptoms without fixing the root cause (e.g., firmware issues).- Depends on the interface name (e.g., if it's not wlan0, the command fails). When to Use Best for a long-term fix after confirming it works. Ideal for quick testing or as a temporary workaround. Ease of Use Moderate: Edit a file and reboot. Simple: Run a single command. Recommendation
-
Start with the iw command: It's less risky and allows you to test the fix immediately without rebooting or making permanent changes. This is especially useful for your situation, where the goal is to disable power-saving features quickly and see if it stops the crashes.
-
If it works, make it persistent: If the iw command resolves the issue, you can automate it to run on every boot. Then, if needed, add the modprobe options for a more robust solution.
Here's how to proceed step by step:
Step 1: Try the iw Command First
- Confirm your WiFi interface name (it might not be exactly "wlan0"; common alternatives are "wlo1" or "wlp2s0"):
ip link show # Look for the wireless interface, e.g., "wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP>" - Run the command with your interface:
sudo iw dev <your_interface> set power_save off # e.g., sudo iw dev wlan0 set power_save off - Test your WiFi: Connect to a network, use it for a while, and monitor for crashes:
dmesg | grep rtw88 # Check logs for errors journalctl -f | grep rtw88 # Monitor logs in real-time - If the crashes stop, great! This is a simple fix.
Step 2: Make the iw Command Persistent (If It Works)
If the iw command helps but the changes don't survive reboots, add it to your system's startup scripts:
- Create a script file:
sudo nano /etc/systemd/system/disable-wifi-powersave.service - Add the following content:
[Unit] Description=Disable WiFi Power Save After=network.target [Service] Type=oneshot ExecStart=/usr/sbin/iw dev <your_interface> set power_save off # e.g., /usr/sbin/iw dev wlan0 set power_save off [Install] WantedBy=multi-user.target - Save the file, then enable and start the service:
sudo systemctl daemon-reload sudo systemctl enable disable-wifi-powersave.service sudo systemctl start disable-wifi-powersave.service sudo reboot # Test after reboot
Step 3: Use Modprobe Options for a Deeper Fix
If the iw command doesn't fully resolve the issue (e.g., crashes return after some time), fall back to the modprobe options for a more permanent solution:
- Edit or create the file as before:
sudo nano /etc/modprobe.d/rtw88.conf - Add the lines:
options rtw88_core aspm=0 debug=0 options rtw88_8821ce powersave=0 - Reload and apply:
sudo modprobe -r rtw88_8821ce # Unload if possible sudo modprobe -r rtw88_core sudo modprobe rtw88_core sudo modprobe rtw88_8821ce sudo reboot # Reboot to apply - After rebooting, test as in Step 1.
Why This Order?
- The iw command is quicker and reversible, making it a good first step.
- If your problem is tied to driver-level power management (like the "Deep Power Mode" error), the modprobe options might be more effective long-term.
- You can even use both together for redundancy: Start with iw for immediate relief, then add modprobe for persistence.
Final Tips
- Monitor and Test: After trying either method, keep an eye on your system logs and WiFi stability. If issues persist, share the output of commands like
dmesg | grep rtw88oriw dev <your_interface> get power_savefor more tailored advice. - Potential Side Effects: Disabling power management might increase battery drain on a laptop, so test on AC power if possible.
- When to Stop and Seek Help: If neither works, consider the GitHub driver option we discussed earlier, or report the bug to Fedora (e.g., via bugzilla.redhat.com) with your full logs and setup details.
Let me know how this goes or if you have any questions—I'm here to help! 😊
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.