In 2019, I bought an HP laptop (Notebook 15 – Intel Core i5) running Windows 10 Home. I had only used it for about two years before upgrading to a different computer. Last week, I was looking for a Windows 10 replacement for my old computer and tried Linux Mint.
That installation failed, as did every other Linux distribution I tried to install. I received cryptic errors like “No root file system is defined” or “The efi file system creation in partition #1 of SCS12 (0,0,0) (sdb) failed.” For some, workarounds are available; others could be total hardware lockouts for Linux.
It reminded me that for first-timers, this could easily feel similar to the challenges they face with Windows 11 hardware requirements. The errors may vary, as noted in the table below. To avoid such bottlenecks, you should note certain requirements when purchasing a laptop for Linux.
|
Error message |
Trigger |
|---|---|
|
“This computer uses Intel RST (Rapid Storage Technology). You need to turn off RST before installing Linux Mint.” |
Hidden hard drive |
|
This kernel requires an x86-64 CPU, but it only detected an i686 CPU. Unable to boot — please use a kernel appropriate for your CPU.” |
Architecture mismatch |
|
“NMI watchdog: BUG: soft lockup – CPU#0 stuck for 23s! [swapper/0:0]” |
Driver conflict |
|
“Verification failed: (15) Access Denied” or “Secure Boot Violation” |
Digital lock |
|
“Mount is denied because the NTFS volume is already exclusively opened. The volume may be already mounted, or another software may use it…” |
Windows hibernation |
Architecture and CPU compatibility
Make sure the laptop’s processor can actually run mainstream Linux distros
There are several Windows “Copilot+” laptops running the Snapdragon X Elite (ARM) processors. While these are fast, efficient, and great for Windows, several Linux installers can’t boot from them because standard Linux ISOs are typically built for x86_64 (Intel/AMD).
If your goal is the classic procedure of downloading an ISO, writing it to a USB drive, and installing Linux, you’re best off with Intel Core or AMD Ryzen CPUs. To be safe, if a laptop listing doesn’t explicitly say the laptop supports Linux on ARM, avoid it if you plan on installing Linux.
Firmware, secure boot, and bootloader restrictions
Your laptop must let you boot from USB and install a different OS
Even when the hardware is perfect for Linux, the firmware may block you. Business-class “Secured-core” laptops typically lock down the boot order and may hide key UEFI options. This applies to a growing number of consumer models nowadays. It’s impossible to install Linux if you can’t rearrange the boot order and place the USB first, or if you can’t access the boot menu.
There are certain security policies governing Pluton-equipped “Secured-core PCs” that may further complicate Linux installation. For instance, if vendors aggressively disable the Microsoft third-party UEFI CA (certificate) by default, it creates a soft lockout for most standard Linux distributions that require it to boot.
Before making a purchase, you should search for the exact model number + “Linux BIOS” or “Can’t boot USB” to check for issues ahead of time. Avoid that laptop if you see several users hitting a wall with it.
Storage controller mode and NVMe configuration
Linux can’t install if it can’t see your drive
Several laptops ship NVMe drives in Intel RST/RAID mode because Windows uses them to optimize boot times. However, in this mode, Linux simply can’t see the drive.
You’ll generally be able to switch to AHCI to fix it, but certain manufacturers may entirely hide the AHCI/RST toggle. If this toggle is hidden, your Linux installer will show no drives, and there’s no workaround for it.
To find this out before buying the laptop, search for your laptop model plus “change RAID to AHCI” to confirm the BIOS doesn’t lock the SATA/NVMe mode.
Wireless chipset compatibility
Some Wi-Fi and Bluetooth chips simply have no Linux drivers yet
Wireless chipset compatibility is an issue you may face after installing Linux, and sadly, it’s a common one. During production runs, some vendors switch wireless modules. So, a given model might have Intel Wi-Fi in January, while the same model ships with Realtek in March.
Linux support for different chips varies, which means you may have perfect Wi-Fi while another person who buys the same model gets no internet. Here’s a quick cheat sheet that helps:
|
Manufacturer |
Linux support |
Verdict |
|---|---|---|
|
Intel (AX200/AX210/BE200) |
Excellent |
Recommended |
|
Qualcomm Atheros |
Good |
Generally safe |
|
MediaTek |
Mixed/inconsistent |
Research required |
|
Realtek |
Often poor |
Caution |
|
Broadcom |
Historically bad |
Not recommended |
GPU and graphics driver support
Graphics determine smoothness, battery life, and external display support
As long as you have no gaming plans and don’t intend on doing CUDA work, it’s safe to go for an all-Intel or all-AMD system. Their drivers ship inside the kernel, so you can generally assume they work.
NVIDIA, however, is a bit tricky. The support is much better than it was a few years ago, but if you use hybrid graphics (which switch between the iGPU and the discrete GPU), it may cause any of the following issues:
- Screen tearing
- Poor battery life
- External monitors failing to wake
- Wayland compatibility issues
None of this is catastrophic, but it will require some extra work. My advice for a new user is to stick to Intel- or AMD-only graphics. The GPU and graphics struggle is why some people don’t buy the idea that Linux is better than Windows.
The easiest way to avoid issues with Linux not installing or post-installation problems is by purchasing a machine that’s already known to work. Your top options are Ubuntu Certified Hardware, Fedora/Red Hat certified lists, and the Lenovo Linux Program. With any of these, you’ll get laptops with better privacy settings than Windows.
You can choose to buy outside this list, but you effectively become the firmware tester. It’s fine if that’s what you want, though several people would rather avoid the hassle.