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 a persistent WiFi driver crash on Fedora Linux, specifically with the Realtek rtw88 driver. The error message you're seeing in the logs indicates a failure in the power management system: the driver is trying to exit "Deep Power mode" but isn't getting an acknowledgment from the firmware. This could be due to outdated drivers, firmware issues, hardware compatibility problems, or kernel bugs.
Don't worry—I'll guide you through troubleshooting and potential fixes step by step. These steps are based on common solutions for Realtek WiFi issues on Linux. Since you're on Fedora, we'll use its package manager (dnf) where possible.
Step 1: Gather More Information
Before fixing, let's confirm the details of your hardware and the issue. This will help pinpoint the problem.
-
Check your WiFi hardware: Run the following command to identify your WiFi card:
lspci -k | grep -i networkThis should show something like "Realtek Semiconductor Co., Ltd. Device xxxx" (e.g., RTL8822BE). Note the exact model, as it might be relevant for specific fixes.
-
Review the full logs: The error you provided is from the kernel log. Check for more details with:
journalctl -b -u NetworkManager | grep rtw88Or, for a broader view:
dmesg | grep -i rtw88Look for repeated errors or patterns. If you see other warnings, share them for more tailored advice.
Step 2: Update Your System
Outdated kernels or drivers are a common cause. Fedora releases updates frequently, so start here.
-
Update Fedora packages:
sudo dnf update sudo rebootThis will update your kernel, drivers, and firmware. After rebooting, test your WiFi to see if the crashes stop.
-
If you're on an older kernel: Check your kernel version with
uname -r. If it's not the latest (e.g., 6.1 or higher for recent Fedora), you might need to enable updates via Fedora's repositories or switch to the latest kernel using:sudo dnf install kernel-modules-extra sudo dnf update kernel sudo reboot
Step 3: Update or Install Firmware
The rtw88 driver relies on firmware files, which are separate from the driver itself. If the firmware is missing or outdated, it can cause exactly this kind of error.
-
Install the latest firmware:
sudo dnf install linux-firmwareThis package includes firmware for many hardware devices, including Realtek WiFi cards. After installation, reboot and check if the issue persists.
-
Verify firmware loading: After rebooting, run:
dmesg | grep rtw88Look for messages like "rtw88: firmware loaded" or errors indicating firmware failure. If it's still failing, you might need to manually download firmware from the Linux Firmware repository (e.g., from kernel.org) and place it in
/lib/firmware/. But let's try the above first.
Step 4: Disable Power Saving Features
The error is specifically about power mode changes, so disabling power management for the WiFi driver could be a quick workaround.
-
Temporarily disable power saving: Unload and reload the driver with power saving disabled:
sudo modprobe -r rtw88_core rtw88_pci # Unload the driver (adjust if your module is different) sudo modprobe rtw88_core disable_ps=1 # Reload with power saving disabledThen test your WiFi. If this works, make it permanent by creating a configuration file:
echo "options rtw88_core disable_ps=1" | sudo tee /etc/modprobe.d/rtw88.conf sudo depmod -a sudo reboot -
Alternative: Use iw to disable powersave per interface: First, identify your WiFi interface (e.g., wlan0) with
ip link show. Then:sudo iw dev <interface> set power_save offYou can add this to a startup script if it helps.
Step 5: Try Alternative Drivers or Workarounds
If the above doesn't work, you might need to experiment with other options.
-
Blacklist and reload the driver: Sometimes, forcing a reload or using a different driver version helps. First, blacklist the current driver:
echo "blacklist rtw88_core" | sudo tee /etc/modprobe.d/blacklist-rtw88.conf sudo depmod -a sudo rebootThis might not work if no alternative driver is available, but it's worth trying. On reboot, check if WiFi works or if another driver (e.g., from staging) kicks in.
-
Switch to a different kernel or driver source: If you're on an older Fedora version, consider upgrading to the latest (e.g., Fedora 38 or 39). You could also compile the rtw88 driver from source:
- Install build tools:
sudo dnf install kernel-devel gcc make git dkms - Clone the latest rtw88 driver:
git clone https://github.com/lwfinger/rtw88.git - Build and install: Follow the README in the repo (it involves
makeandsudo make install). This is advanced and could break things, so only do this if you're comfortable.
- Install build tools:
-
Test with a live USB: Boot from a Fedora live USB (from the latest ISO) to see if the problem persists. If it doesn't, it's likely a configuration issue on your installed system.
Step 6: If Nothing Works
If the crashes continue, it could be a hardware issue or a bug in the driver/kernel. Here's what to do next:
-
Report the bug:
- File a bug report on the Fedora Bugzilla (bugzilla.redhat.com) or the Linux kernel bug tracker (bugzilla.kernel.org). Include your hardware details, kernel version, and full log output.
- You can also check the rtw88 GitHub repository for open issues and report there if it's relevant.
-
Hardware troubleshooting: Test with a USB WiFi adapter to rule out a faulty internal card. Or, if your laptop has a switch for WiFi, ensure it's enabled.
-
Community help: Post on forums like Reddit (r/Fedora or r/linuxquestions) or Ask Fedora with your full logs and hardware details. Provide the output of
lspci -vnnanddmesg | grep rtw88for better assistance.
Final Notes
Start with Steps 1-3, as they're the least invasive. Most users resolve Realtek driver issues by updating firmware or disabling power saving. If you're not comfortable with command-line steps, consider seeking help from a tech-savvy friend or a Linux community.
If you run into any errors during these steps or need clarification, reply with the details, and I'll refine my advice! Stay patient—this is a common issue, and it's fixable. 😊
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.