Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBefore installing or removing anything, identify the device, the Linux kernel version, and—where applicable—the driver currently bound to the device. Then check whether the problem is detection, driver binding, firmware, a disabled radio, or a desktop audio/display setting. Those causes need different fixes, and the right instructions depend on your distribution, release, and hardware.
What should you check first?
Record your distribution and release, kernel version, exact device model, and what changed just before the problem began. A kernel or distribution update can be relevant, but it does not by itself show which component failed.
As an Amazon Associate I earn from qualifying purchases.
-
Check the kernel version with
uname -r. -
For a PCI or PCIe device, run
lspci -k. Find the relevant device entry and note whether it appears, what it says underKernel driver in use, and which modules are listed underKernel modules.Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
For a USB device, run
lsusband note whether the device appears. Not all internal hardware uses PCIe; wireless devices may use PCI, PCIe, SDIO, USB, or another interface. -
After reproducing the failure, inspect kernel messages with
dmesg. On systems that restrict access to that command, use your distribution’s supported method for viewing kernel logs. Look for the device name and nearby messages, not just one isolated error line.
If the hardware does not appear in the relevant device listing, a driver package may not be the first issue to address. If it appears but no driver is shown as in use, that is different from a device that has a driver but fails during initialization or operation. The Linux kernel’s issue-reporting guidance recommends identifying the device and its driver and directing problems to the relevant driver or subsystem.
Why is my Wi-Fi not working on Linux?
Check that the adapter is detected and supported
Identify the adapter and its bus, then check whether the driver for that device supports it on your kernel. The Linux Wireless driver list covers different wireless drivers and bus types, but support and capabilities vary by driver. A driver’s presence in a general list does not guarantee that every device using a similar name or chipset revision works on your particular distribution and kernel.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesCheck whether the radio is blocked
Run rfkill list. A software block and a hard block are not the same: a hard block can reflect a laptop switch or platform control that has disabled the radio. If the output reports a hard block, check the computer’s wireless switch, function key, or manufacturer-provided platform control. Do not blacklist platform modules without device-specific evidence; that can conceal the control rather than fix it.
Look for firmware errors
A kernel driver and device firmware are separate components. Some devices need firmware loaded into an onboard microcontroller before they can operate. Check kernel messages for firmware load failures or crashes, then consult the package guidance for your distribution and release. Intel Wi-Fi firmware is commonly provided by a package called linux-firmware or an equivalent, but package names and installation steps differ by distribution. Avoid manually copying firmware from an unrelated system or source.
Rank #2
For an Intel Wi-Fi firmware crash, Linux Wireless recommends providing the complete relevant dmesg output and recording the firmware version. Review logs before posting them: debugging output may expose an email address or nearby devices’ MAC addresses.
Consider Windows Fast Startup in a dual-boot setup
If the computer also runs Windows and Linux Wi-Fi fails during initialization, check whether Windows Fast Startup is enabled. Linux Wireless documents it as one possible cause of Intel Wi-Fi initialization problems. This is a targeted check for some dual-boot cases, not a general explanation for every wireless failure.
When a USB Wi-Fi adapter is a fallback
If the built-in adapter remains unsupported or unusable, a USB adapter may be an option—but verify the exact chipset, Linux driver, required firmware, bus interface, and compatibility with your target kernel and distribution before buying. Linux Wireless lists USB-capable driver families; that does not establish compatibility for any particular retail model.
What should I do when a Linux graphics driver is not working?
Identify the GPU and the active driver
For a PCI or PCIe graphics device, use lspci -k to confirm that the GPU appears and see which kernel driver is bound to it. Record the GPU model, uname -r output, and kernel messages from the failed startup or display session. If the issue began after an update, keep the previous and current kernel versions in your notes if both are available.
Use instructions for your GPU, distribution, and release
There is no universal “install the proprietary driver” fix. The appropriate graphics stack depends on the GPU vendor and generation, the distribution’s packaging, and whether the fault is in kernel-driver binding, firmware, the display server, or graphics acceleration. Follow the current driver-management guidance for your installed distribution and release rather than copying generic commands or old community-wiki steps. Instructions written for another release can change packages or configuration that your system does not use.
Rank #3
If the GPU is detected but the driver is not bound, include that fact in a support request. If a driver is bound but the display still fails, provide the relevant kernel messages and describe what fails—for example, whether the problem occurs at boot, when starting a graphical session, or only in an application. These symptoms point to different layers of the graphics stack.
Free tools Windows power users keep installed
One-click scans. No signup required.
What should I check if Linux has no sound after an update?
Start with the output path
-
Check that speakers or headphones are connected to the intended jack or port and that powered speakers are switched on.
-
Confirm that the desktop is sending sound to the intended output device; a connected monitor, headset, or dock may be selected instead.
-
Run
aplay -lto see whether ALSA lists a playback device. -
Open the system mixer or audio controls and check that the relevant output is not muted and its level is raised.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Separate missing hardware from a desktop audio problem
If aplay -l lists no playback hardware, record the audio device model and inspect kernel messages for detection or initialization errors. If ALSA lists a device but the desktop produces no sound, check the selected output and mixer state before changing drivers or packages. The Ubuntu Community Help Wiki describes these as basic diagnostics, but some of its audio instructions are historical and release-specific.
Do not start by replacing the desktop audio stack, compiling a driver, or editing module configuration. Older Ubuntu instructions include package and configuration changes that may not apply to a supported release and can affect unrelated desktop components. Check the current support guidance for your own distribution and version before making changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What information should you include when asking for help?
Give the support channel enough information to identify the device and route the issue to the right subsystem. Include:
-
Your distribution and release, plus the kernel version from
uname -r.What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
The exact device model and, when available, its PCI or USB ID.
-
The relevant
lspci -korlsusbentry, including the active driver if one is shown. -
What you observed, when it began, and any update or configuration change immediately beforehand.
-
The relevant kernel-log context after reproducing the problem; for Intel Wi-Fi firmware failures, include the firmware version when available.
DriversOutdated Drivers Are Slowing You DownPerformanceWindows Errors? Fix Them Before They SpreadDriversCrashes, No Sound, or Screen Glitches?Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
For Wi-Fi, the output of
rfkill list, with personal or identifying details reviewed before sharing.
Kernel logs and wireless debug output can contain identifying information, including email addresses or peer MAC addresses. Redact sensitive details before posting publicly, while retaining the device and error information needed to diagnose the fault.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
