Recommended Free Tools
The safest fix is to identify the exact hardware and the layer that is failing before installing drivers or changing settings. Record your Linux release and kernel, identify the device and loaded driver, then use the branch for Wi‑Fi, sound, or graphics. A device that Linux does not detect needs hardware, firmware, kernel, or driver investigation; a detected device that does not work may only need unblocking, routing, mixer, display, or desktop configuration.
Start with evidence, not a guessed driver
“Old PC” is not a hardware specification. Two computers from the same year can use different wireless chipsets, audio codecs, or graphics generations, each requiring different kernel support and firmware. Distribution releases also ship different kernels, firmware packages, desktop tools, and configuration defaults. Capture the facts below while the machine is in the problem state.
As an Amazon Associate I earn from qualifying purchases.
- Record the distribution and release. Use your distribution’s system-information panel or its documented command. The release determines package names, kernel age, and available driver versions.
- Record the kernel. Run
uname -r. Keep the complete result, including any distribution suffix. - Identify PCI hardware and its driver. Run
lspci -nnk. The numeric vendor and device IDs are more useful than a marketing name. For each relevant device, note “Kernel driver in use” and “Kernel modules.” - Identify USB hardware. Run
lsusband copy the vendor and product ID for an external Wi‑Fi adapter, USB sound device, or USB display adapter. - Save kernel messages. Run
dmesgsoon after boot and preserve lines mentioning the device, firmware, driver, timeout, probe failure, or display initialization. On systems that restrict ordinary users from reading the kernel buffer, use the distribution’s approved administrator method. - Write down what “not working” means. Examples include no device listed, a wireless interface that cannot scan, sound hardware listed but silent, a monitor detected at the wrong resolution, a blank display, or a desktop that works without hardware acceleration. Those are different faults.
Linux Wireless documentation asks for exact software versions, the driver, PCI or USB hardware details, and kernel messages when a wireless problem is reported. That same evidence-first approach prevents you from applying a driver intended for a different revision.
Use the detection decision tree
| What you observe | Most likely layer | Next check |
|---|---|---|
The device is absent from lspci or lsusb |
Physical connection, firmware setup, disabled hardware, or a bus-level problem | Check firmware/BIOS settings, switches, cables, and whether the device appears in another operating system or live session |
| The device is listed, but no driver is in use | Kernel support, module loading, or firmware | Read the device’s dmesg lines and compare the exact ID with support for your kernel |
| A driver is in use, but the device is blocked or unavailable | Radio control, permissions, power management, or device state | Use the subsystem checks below, beginning with rfkill for Wi‑Fi and ALSA/output checks for sound |
| The device and driver are present, but the result is wrong | Desktop, routing, mode setting, or userspace configuration | Check the selected output, display mode, mixer, network manager, or graphics session |
Do not treat a successful desktop boot as proof that every graphics feature works. Likewise, seeing a network icon or a speaker icon does not prove that the kernel has initialized the underlying hardware.
#1 Best Overall
- 𝐋𝐨𝐧𝐠 𝐑𝐚𝐧𝐠𝐞 𝐀𝐝𝐚𝐩𝐭𝐞𝐫 – This compact USB Wi-Fi adapter provides long-range and lag-free connections wherever you are. Upgrade your PCs or laptops to 802.11ac standards which are three times faster than wireless N speeds.
- 𝐒𝐦𝐨𝐨𝐭𝐡 𝐋𝐚𝐠 𝐅𝐫𝐞𝐞 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧𝐬 – Get Wi-Fi speeds up to 200 Mbps on the 2.4 GHz band and up to 433 Mbps on the 5 GHz band for upgraded web surfing, gaming, and streaming. Performance varies by conditions, distance to devices, and obstacles such as walls.
- 𝐃𝐮𝐚𝐥-𝐛𝐚𝐧𝐝 𝟐.𝟒 𝐆𝐇𝐳 𝐚𝐧𝐝 𝟓 𝐆𝐇𝐳 𝐁𝐚𝐧𝐝𝐬 – Dual-bands provide flexible connectivity, giving your devices access to the latest routers for faster speeds and extended range. Wireless Security - WEP, WPA/WPA2, WPA-PSK/WPA2-PSK
- 𝟓𝐝𝐁𝐢 𝐇𝐢𝐠𝐡 𝐆𝐚𝐢𝐧 𝐀𝐧𝐭𝐞𝐧𝐧𝐚 – The high gain antenna of the Archer T2U Plus greatly enhances the reception and transmission of WiFi signal strengths.
- 𝐀𝐝𝐣𝐮𝐬𝐭𝐚𝐛𝐥𝐞, 𝐌𝐮𝐥𝐭𝐢-𝐃𝐢𝐫𝐞𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐀𝐧𝐭𝐞𝐧𝐧𝐚: Rotate the multi-directional antenna to face your router to improve your experience and performance
Fix Wi‑Fi that is missing or unavailable
1. Check the physical and software radio state
Look for a laptop wireless switch, sliding button, or function-key control. A hardware switch can override every software setting. Then run:
rfkill listA soft blocked device has been disabled by software and can often be re-enabled with the distribution’s network settings or an appropriate rfkill command. A hard blocked device is being held off by a physical switch or platform firmware. Installing another package will not clear a hard block; restore the switch or firmware state first.
2. Confirm the chipset, interface, and driver
Use lspci -nnk for an internal PCI or PCIe adapter and lsusb for a USB adapter. Do not assume the interface is named wlan0. Modern systems commonly use predictable names such as wlp2s0, and the exact name may differ after hardware changes. List interfaces with your network tools and use the name Linux actually reports.
In lspci -nnk, distinguish these cases:
- Device present, driver in use: the kernel has attached a driver; continue with radio state, firmware messages, scanning, and connection software.
- Device present, no driver in use: investigate kernel support, module loading, and firmware before changing network credentials.
- Device absent: check a physical switch, firmware setup, seating or power, and whether the adapter is disabled at the bus level.
3. Read firmware and initialization errors
Search the boot messages for the chipset name, driver name, and terms such as firmware, failed, timeout, or unsupported. A missing firmware file can leave a detected adapter unusable even when the kernel module exists. An older kernel may also lack support for a later revision, while a very old chipset may require a driver that current distributions no longer package by default.
Install firmware only from your distribution’s repositories and documentation, using the package manager and package name for your exact release. Do not copy a random firmware file from a forum or install a module built for another kernel. After installing the correct package, reboot if the distribution’s instructions require it, then re-check dmesg and lspci -nnk.
4. Separate driver failure from network-manager failure
If the adapter is enabled, has a driver, and reports an interface, test whether it can see networks. A failure to create an interface or scan points toward the driver, firmware, radio state, or regulatory setup. An interface that scans but cannot authenticate may instead involve the network manager, supplicant, credentials, encryption compatibility, or access point.
Rank #2
- AC1300 Dual Band Wi-Fi Adapter for PC, Desktop and Laptop. Archer T3U provides 2.4G/5G strong high speed connection throughout your house.
- Archer T3U also provides MU-MIMO, which delivers Beamforming connection for lag-free Wi-Fi experience.
- Usb 3.0 provides 10x faster speed than USB 2.0, along with mini and portable size that allows the user to carry the device everywhere.
- World's 1 provider of consumer Wi-Fi for 7 consecutive years - according to IDC Q2 2018 report
- Supports Windows 11, 10, 8.1, 8, 7, XP/ Mac OS X 10.9-10.14
Linux Wireless documentation recommends narrowing this distinction with the lower-level iw tool and, where appropriate, wpa_supplicant. Use the interface name shown by your system. These tests are diagnostic; stop any conflicting network manager connection attempt first if your distribution’s documentation says it is necessary, and restore normal management afterward.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteAvoid old tutorials built around iwconfig. It is deprecated for modern Linux wireless and can hide capabilities or produce misleading results. Prefer the current wireless tools supplied by your distribution.
5. Handle Intel wireless reports safely
The Linux Wireless guidance states: “Before reaching out to us, please make sure you have a supported Intel Wi-Fi device and that it is enabled.” For an Intel wireless bug report, include the relevant dmesg output and firmware version along with the exact device ID and kernel. Review the log before posting it publicly: wireless messages can contain sensitive identifiers, including a peer’s MAC address.
6. Decide whether replacement hardware is justified
Replace an internal adapter only after confirming that its exact chipset and revision lack usable support for your intended distribution and kernel. A USB Wi‑Fi adapter can be a practical fallback, but “Linux compatible” on a product page is not enough. Verify all of the following before buying:
- Exact chipset and revision, not merely the adapter’s retail model name
- Support in the target kernel version
- Firmware availability in the target distribution
- Physical connector, available USB standard, antenna requirements, and clearance around neighboring ports
- Whether the adapter will be used during installation, when network access may not yet be available
No single retail model is universally compatible across old computers and Linux releases. Keep the original adapter installed until the replacement is proven, and retain the chipset ID and kernel details for future troubleshooting.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix no sound after installing Linux
1. Establish whether ALSA sees a card
Linux audio begins below the desktop mixer. Inspect the ALSA information exposed under /proc/asound, starting with:
Rank #3
- AC600 Nano size wireless Dual band USB Wi-Fi adapter for fast and high speed Wi-Fi connection.
- Strong 2.4G/5G connection allows the user to use the Internet with lag-free experience.
- Sleek and miniature sized design allows the user to plug and leave the device in it's place.
- Industry leading support: 2-year and free 24/7 technical support
- This network transceiver supports Windows 11, 10, 8.1, 8, 7, XP/ Mac OS X 10.9-10.14
cat /proc/asound/cardsThis lists configured sound cards. The ALSA documentation also exposes card-specific details, PCM stream state and parameters, USB audio stream data, and codec information under the same hierarchy. A card listed here is evidence that Linux detected at least part of the audio stack; it does not prove that the desktop selected the correct output.
You can also enumerate playback devices with the ALSA utilities supplied by your distribution. If no card or PCM device appears, investigate hardware detection, the kernel driver, firmware, and boot messages before adjusting desktop volume controls. If a card and PCM device are present, continue with routing and mute checks.
2. Check the simple causes before changing drivers
- Open the desktop sound panel and verify the selected output device.
- Check both the master volume and individual mixer channels. A muted channel may be shown by a small mute indicator or an “MM” state in a terminal mixer.
- Disconnect headphones, HDMI cables, docks, and USB sound devices temporarily. The active output may have changed automatically.
- Test the built-in speakers, headphone jack, and any USB audio device separately. A failure on one output does not prove that the entire audio card is broken.
- Confirm that the application is sending audio to the same output selected by the desktop. Per-application routing can override the system default.
3. Treat HDMI and DisplayPort as a separate route
Digital audio over HDMI or DisplayPort depends on the graphics device, the display sink, and the audio route. Inspect the display’s ELD information in the ALSA data when the digital output is missing or silent. ELD describes what the connected display reports it can receive. A monitor may support video but expose no usable audio endpoint, or the desktop may continue sending sound to the analog device.
When troubleshooting, connect the intended display before booting or reconnect it and re-open the sound panel. Select the HDMI or DisplayPort profile only after the endpoint appears. If analog output works while HDMI does not, keep the analog route as a working baseline and investigate the graphics driver, display detection, and ELD rather than replacing the audio driver blindly.
4. Read kernel messages when the card is absent
Search dmesg for the codec, controller, USB audio device, and any firmware or probe errors. A missing controller can result from disabled firmware settings, a kernel regression, an unsupported codec, or a failed device. Compare behavior with an earlier kernel available in the boot menu if your distribution provides one; that is a diagnostic comparison, not proof that every older kernel is a permanent solution.
Do not delete configuration files as a first response. Save the current settings, make one change at a time, and record whether the card appears in /proc/asound/cards after each reboot.
Rank #4
- Fast 1300Mbps USB WiFi Adapter - Nineplus wifi adapter provides long-range and stable wifi connections,Upgrade your desktop or laptop wifi Technology with our AC1300Mbps usb wireless Adapter. Whether your desktop pc's wifi usb is malfunctioning or you’re looking to upgrade to faster dual-band 5GHz and 2.4GHz speeds, this pc wifi adapter is the ideal choice. It’s a budget-friendly way to extend your device’s life and experience the benefits of modern WiFi technology
- Dual-band 5.8GHz and 2.4GHz Bands - 5.8Ghz wifi Connection speed up to 867Mbps,2.4GHz 400Mbps,With these upgraded speeds, web surfing, gaming, and streaming online meeting is much more enjoyable without buffering or interruptions,Experience the High Wi-Fi speed of our AC1300Mbps wifi dongle delivers faster internet speeds and stronger, more reliable signal penetration over long distances. It's a high-speed dual-band wifi usb adapter for pc and easy for the modern user.
- Two 5dBi High Gain Wifi Antenna – The high gain antenna of the desktop wifi adapter greatly enhances the reception and transmission of WiFi signal strengths.Equipped with dual high-gain pc wifi antenna, our wifi dongle for desktop pc ensures accurate capture of WiFi signals, providing a stable and strong connection even at greater distances, ideal for overcoming poor signal issues in bedrooms. This computer wifi adapter, wifi card, and usb wifi antenna extend your coverage.
- Super Speed USB 3.0 - wifi adapter for desktop pc Connect speeds Up to 10x faster than USB 2.0 USB, Super USB3.0 delivers faster data transfer, a more reliable network connection, and improved compatibility for wifi adapter for pc. It fully supports the high-speed demands of AC1300 wireless adapter, ensuring peak performance. Plus, it's backward compatible with standard USB 2.0 ports for added flexibility.usb wifi adapter for desktop pc 3.0
- Compatibility Systems: This Wi-Fi usb adapter is compatible with Windows11/10/8.1/8/7/XP,not supports Mac OS or Chromebook or Linux. Most Windows 11/10 systems will automatically detect and install the drivers. If the system does not detect the driver, you will need to download it from our website. For Windows 7, you will need to manually install the driver for this wifi card.or you go to the website online-setup support,we do online-setup for you.
5. Use PCM debugging only for specialist cases
The kernel ALSA documentation says: “When the problem is related with PCM, first try to turn on xrun_debug mode.” This is specialist guidance for diagnosing buffer underruns and overruns, not a first-line command for ordinary silence. Use it only when the device is detected, routing and mute controls are correct, and the symptom points to PCM stream instability. Follow the documentation for your kernel because the parameter and logging behavior can vary.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Fix graphics that are blank, low-resolution, or slow
1. Identify the GPU and the kernel driver
Run lspci -nnk and record the graphics device, “Kernel driver in use,” and available modules. Then inspect dmesg for GPU initialization, firmware loading, display connectors, and errors. A desktop that reaches the login screen may still be using a fallback renderer, have incomplete acceleration, or fail when switching to a different display mode.
Classify the symptom before changing anything:
| Symptom | Layer to investigate first |
|---|---|
| No image on any display | Power, cable/input, firmware setup, kernel initialization, or display mode setting |
| Image appears but only at a low resolution | Monitor detection, mode setting, connector path, or driver support |
| Desktop is visible but 3D or video is slow | Acceleration, renderer selection, firmware, or desktop graphics userspace |
| Only HDMI/DisplayPort output fails | Connector detection, GPU display driver, cable/display negotiation, or mode setting |
2. Check initialization messages instead of guessing a driver
Look for the GPU driver name and messages that show whether the device initialized successfully. Firmware errors, failed probes, and repeated timeouts are more actionable than a generic “graphics driver not working” description. Save the complete relevant block, including messages immediately before and after the error.
AMD display debugging in the kernel documentation uses initialization messages in dmesg to determine which AMD driver components loaded. Follow that evidence: a missing firmware file, a failed display component, and a desktop compositor problem require different fixes.
3. Account for old Intel graphics generations
Do not assume every old Intel GPU uses the same driver or receives the same features. Kernel documentation describes the i915 driver as supporting integrated graphics chipsets with exceptions for some very early models and certain system-on-chip platforms. Some of those older platforms have basic support through gma500. The exact PCI ID and kernel version determine which path applies.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →If your device is one of the early exceptions, installing a newer i915 package cannot turn it into a fully supported modern GPU. Conversely, a supported GPU can still show poor acceleration if firmware or desktop userspace is incomplete. Verify the actual module in lspci -nnk and the initialization result in dmesg.
Best Value
- Wifi 6 High-speed Transmission: The WiFi adapter supports the new generation of WiFi6 technology with transmission speeds of up to 600 Mbps on 5 GHz + 287 Mbps on 2.4 GHz, enabling lightning-fast transmission of video at ultra-high speed and low latency
- Dual-band Connection: The AX900 USB WiFi adapter under the AX standard, the 5G band rate can reach 600Mbps, and the 2.4G band can reach 286Mbps. Note: Use WiFi 6 Router to achieve AX900 speed
- Built-in Drivers for Windows 10/11: The WiFi Adapter for Desktop PC just supports Windows 10/11 which CPU architecture is X86/X64, supports CD-free installation, no need to download drivers, saving time and worry. Please note this Adapter doesn't support MacOS/Linux/Win 8, 8.1, 7, XP
- Receive & Transmit Two in One: A desktop computer can connect to the WiFi wireless Internet by connecting it to a wireless network card. A networked computer can connect to the network card to transmit WiFi and share it with other devices
- Stay Safe Online: The wifi dongle supports WPA-PSK, WPA2-PSK, WPA/WPA2 mixed encryption modes. Note: Make sure that the distance between the adapter and router should be within 30ft
4. Separate display mode setting from acceleration
A monitor that is detected at the wrong resolution points first to connector and mode setting. Check the desktop display panel, the cable and input, and whether the monitor’s reported modes appear. A visible desktop with poor performance points instead to acceleration or renderer selection. Do not “fix” a mode-setting problem by installing an unrelated proprietary package, and do not call a successful mode change proof that 3D acceleration works.
When testing, change one variable at a time: use a known-good cable or display, boot with only one monitor, compare a text console with the graphical session, and compare kernels if an earlier one is available. Record which stage changes: boot image, display manager, desktop, video playback, or 3D application.
Distribution and kernel choices
Package names, firmware bundles, graphical controls, and default services differ between distributions and releases. Use the package manager and documentation for the release shown by your system-information command. Before a kernel change, ensure you have a working way to boot the current system and, if possible, a live USB or an older installed kernel for recovery.
- Prefer supported repositories. They provide files built for the distribution’s kernel and dependency set.
- Read release notes for old hardware. A newer release may drop a legacy driver, change firmware packaging, or change desktop audio and display defaults.
- Keep a recovery path. Do not remove the only bootable kernel or overwrite working configuration before testing the replacement.
- Upgrade deliberately. If the current kernel lacks support for a device, a supported newer kernel may help; if a regression appeared after an upgrade, testing the previous kernel can isolate it.
- Capture before-and-after evidence. Compare
uname -r,lspci -nnk,rfkill list, ALSA card output, and relevantdmesglines.
When a fix fails: recovery branches
Wi‑Fi still absent
- Confirm the adapter appears in
lspci -nnkorlsusb. - Check for a hard or soft
rfkillblock. - Check the exact firmware error in
dmesg. - Verify that a driver is actually in use and note the interface name Linux created.
- If an interface exists, test scanning with current wireless tools before debugging credentials.
- Only then evaluate a replacement adapter whose exact chipset is supported by the target kernel and distribution.
Sound card present but silent
- Confirm the card and PCM device under
/proc/asound. - Unmute the master and relevant channels.
- Select the correct analog, HDMI, DisplayPort, or USB output.
- Disconnect competing outputs and test one application or system sound.
- For digital output, inspect the display’s ELD data and graphics initialization messages.
- Use PCM-specific debugging only after ordinary routing and detection checks are complete.
Graphics desktop works but display or performance does not
- Identify the GPU ID and active kernel module.
- Read initialization and firmware messages in
dmesg. - Test one monitor, one cable, and a known supported mode.
- Determine whether the failure is no signal, wrong mode, or missing acceleration.
- Check whether the hardware generation belongs to an older driver family such as an early Intel platform with basic
gma500support rather than assumingi915. - Compare with a recovery kernel or live session and keep the working boot option available.
What to include when asking for help
A useful report lets someone reproduce the decision tree instead of guessing. Include the distribution and release, complete uname -r output, exact PCI or USB IDs, the driver or module shown by lspci -nnk, the interface name, and the relevant dmesg lines. For Wi‑Fi, include firmware version and rfkill list. For sound, include the ALSA card and PCM information and identify whether the failing output is analog, HDMI, DisplayPort, or USB. For graphics, state whether the screen is blank, limited to a low mode, or merely lacking acceleration.
Remove passwords, network names if sensitive, peer MAC addresses, serial numbers, and other identifiers before posting logs. The goal is enough technical detail to identify the failing layer without publishing information that does not help diagnose it.
How to choose between configuration, kernel, and replacement
| Evidence | Best next action | Why |
|---|---|---|
| Hardware is detected, driver is loaded, and the subsystem reports an endpoint | Fix routing, mute, radio state, display mode, or desktop settings | The kernel has reached the hardware; changing drivers may add risk without addressing the active configuration |
| Hardware is detected but firmware or probe fails | Use the distribution’s matching firmware package or a supported kernel | The device cannot complete initialization |
| Hardware is detected but no supported driver is available | Test a distribution/kernel with documented support or replace the component | Configuration cannot create missing kernel support |
| Hardware is not detected at all | Check physical controls, firmware settings, connections, and bus-level behavior | Package changes cannot fix a device absent from the hardware inventory |
| Only one output or display path fails | Test the cable, sink, connector, profile, and route | The component may work while a particular endpoint does not |
The reliable sequence is always the same: identify the exact component, prove whether Linux detects it, identify the driver and firmware state, read the kernel messages, and only then change packages or hardware. That approach works for Wi‑Fi not working after installing Linux, no sound after installation, and an old-PC graphics driver that appears broken, while avoiding fixes meant for a different chipset or release.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
