Ubuntu Server Guide: Replacing Qualcomm with Intel AX210

Ubuntu Server Installation: Giving Up on Qualcomm for Intel AX210

When my free n8n cloud tier ended, I decided to turn an unused Lenovo S145 into a Linux server. Its AMD Ryzen 3200U and a small memory upgrade seemed well suited to n8n automation. The laptop was already sitting unused, so putting that hardware to work felt like a sensible alternative to paying for another cloud service. Ubuntu Server installation brought an unexpected obstacle, though: the Qualcomm QCA9377 wireless card. It worked under Windows but wouldn’t cooperate under Linux.

A Record of My 5-Step “Wild Goose Chase” Trying to Fix the Qualcomm QCA9377

At first I treated this as an ordinary driver issue that persistence and the right software change would fix. Gemini was helping me work through possibilities, but the attempts became more like repeating unproductive work than learning something useful. Looking back, this is the sequence I went through before accepting that I needed another approach.

• The Firmware Decompression Struggle: Modern Ubuntu compresses firmware files into .zst format to save space. I hypothesized that the driver couldn’t read these files, so I installed zstd and manually decompressed every single file, but it made no difference.
• Forced Filename Matching: I followed rumors that the driver was looking for specific binary filenames, so I cloned board-2.bin and renamed it board.bin . Renaming the file didn’t persuade the system to connect.
• Blacklisting Hardware Conflicts: I found information suggesting the Lenovo-specific module ideapad_laptop was supposedly preventing wireless operation. I disabled it by putting it on the blacklist, expecting that to remove a conflict. Instead, the touchpad stopped working while the Wi-Fi problem remained. That was a particularly frustrating point: the change had affected the wrong part of the laptop and left the original fault unresolved.
• Software Unlocking: I must have typed rfkill unblock all repeatedly, to the point that it felt as though I’d entered it hundreds of times. The terminal said the device was unblocked, but the list of available networks still showed nothing. Seeing a successful-looking status without an actual connection was one of the most misleading parts of the troubleshooting.
• Kernel Log Analysis: I spent the night staring at dmesg logs, only to be met with the same cold “firmware load failure” message every single time.

The Truth from Reddit and My Escape to Intel AX210

After half a day staring at the screen, I turned to Reddit. Experienced Linux users described the Qualcomm QCA9377 and Ubuntu Server combination as something to stop fighting and replace. That advice finally made me reconsider whether persistence was helping. I ordered an Intel AX210 for about 20,000 KRW and decided not to keep forcing software changes while waiting for it to arrive.

Replacing the card took less than 5 minutes once it arrived. I opened the laptop, swapped Qualcomm for Intel AX210, and reassembled it. On startup, available Wi-Fi networks appeared without further setup. That was a relief, and a strong reminder of how much hardware compatibility matters on a Linux server.

Final Thoughts After the Hardware Swap

The logs finally showed “Intel Corporation Wi-Fi 6 AX210 successfully initialized.” After all the troubleshooting, that was the result I’d wanted. Persistence hadn’t compensated for an unsuitable component. If you’re repurposing an old laptop, check the wireless card’s Linux compatibility early rather than lose the same hours I did.