In November I swapped my desktop from Windows to an Arch-based CachyOS to test whether Linux can be a low-friction everyday alternative. The move followed a quick backup of my Windows image and a single evening install; the system booted under the Limine bootloader and recognized the existing Windows installation. Over the first week the setup covered work tasks, one brief gaming session, and a successful print job, with only a handful of quirky hardware puzzles. Overall the transition has been smoother than I expected, though a few compatibility gaps remain for specific apps and games.
Key takeaways
- The switch began in November; the installer completed the base CachyOS installation in roughly six minutes.
- I repartitioned a 4TB drive, shrinking one volume to 2TB, created a 2GB boot partition, and initially made a 100GB btrfs root that I later expanded to 1TB.
- GPU drivers installed automatically and Steam/Proton ran The Outer Worlds without issue; save sync worked via the cloud.
- A Mad Catz Cyborg RAT 7 gaming mouse exhibits a known desktop-click bug but functions normally inside games.
- Apps were installed from Cachy repositories, Flatpak/AUR and direct packages; Slack came from the AUR and 1Password briefly failed when its mirror was down.
- Minecraft Bedrock (the kids’ platform) lacked a straightforward native option, forcing workarounds like Android emulation or Proton-tested builds.
Background
Linux distributions are collections of components assembled around the Linux kernel; choices that are preselected on macOS and Windows are deliberately modular on Linux. Distros range from beginner-friendly, curated systems—Ubuntu and Mint—to DIY-focused projects such as Arch and its derivatives; CachyOS sits toward the modern-hardware-optimized end of that spectrum. For many users the largest practical hurdles have historically been driver support and application availability, but compatibility layers like Proton and universal packaging formats (Flatpak, Snap, AppImage) have narrowed those gaps for gaming and mainstream apps. Another operational reality is bootloader management: Windows updates can overwrite other bootloaders, so installing Linux on a separate physical disk is a common precaution.
The decision to test CachyOS was driven by a desire to minimize upfront configuration while keeping gaming straightforward. I used Ventoy to boot the live image and disabled Secure Boot in the machine firmware before launching the installer. Early choices during an Arch-based install are granular—bootloader selection, filesystem, and desktop environment among them—and those decisions shape later maintenance. Choosing KDE Plasma and btrfs reflected a preference for a polished desktop with modern filesystem features, but they also increased the surface area for small configuration tasks.
Main event
The install process began from a Ventoy USB image after Secure Boot was turned off and proceeded in two phases: live environment and installer. The installer presented multiple bootloader options; I selected Limine and installed CachyOS on a separate physical drive to avoid Windows update conflicts. Partitioning was manual: I shrank an existing 4TB partition to 2TB, created a 2GB boot partition, and allocated 100GB to an initial btrfs root volume before finishing the installer and rebooting into Limine.
After first boot many peripherals worked immediately: the distro automatically provided the recommended GPU driver, and monitor, speakers, and a Logitech webcam functioned without extra configuration. The one conspicuous hardware trouble was my Mad Catz Cyborg RAT 7 mouse: cursor movement was fine but desktop clicks failed. Unplugging the mouse allowed a trackball to work normally, and the bug appears limited to desktop input while gaming input remains functional.
Application setup used a mix of Cachy’s welcome-screen installer, Arch repositories, the Arch User Repository (AUR), and Flatpak where convenient. Slack was pulled from the AUR; Chromium, Discord, and Audacity installed from the distro’s flows and Flatpak channels. A 1Password package initially failed when its AUR mirror was down but installed later without further issue. For gaming the distro offers a one-click gaming bundle that installs Proton, Steam, and Heroic; after resizing the root partition to 1TB I downloaded and launched The Outer Worlds via Proton and confirmed cloud saves synced correctly.
Analysis & implications
The practical takeaway is that a modern, gaming-capable Linux desktop is feasible for a typical reviewer’s workflow without an extended pre-install deep-dive. Automatic driver detection and Proton’s maturity mean many Windows-era games will run with minimal intervention; The Outer Worlds was a quick proof point. However, software availability is still uneven: niche commercial clients (Arc browser, some desktop apps) remain macOS/Windows-first and often require browser-based fallbacks or community-built packages.
Hardware quirks persist at the edges: specific peripherals can have driver or configuration issues that are visible on the desktop but not inside games, as with my Mad Catz mouse. Those problems are usually solvable through configuration files or small workarounds, but they demand a willingness to troubleshoot—something many casual users want to avoid. Installing on a separate physical drive and using widely supported desktop environments like KDE or GNOME can reduce risk and simplify recovery.
For families and mixed-device households a key limitation is platform parity: Minecraft Bedrock Edition remains effectively unsupported on native Linux, which complicates multiplayer sessions with kids on iPads. Workarounds—Android emulation, MCPE Launcher attempts, or running the Windows build under Proton—are possible but not guaranteed. For professionals who must retain fluency across ecosystems, Linux can be a daily driver for many tasks, but dual-boot or secondary devices are still practical safety nets.
Comparison & data
| State | Boot/Partitions | Root (btrfs) |
|---|---|---|
| Before | Windows primary, 4TB data partition | — |
| Initial install | Limine bootloader, 2GB boot, separate drive | 100GB (later expanded) |
| After resize | Same bootloader, extra btrfs partition added | 1TB |
The table summarizes the disk layout progression: the original 4TB data volume was reduced to 2TB, a dedicated 2GB boot partition was created, and a 100GB root was increased to 1TB to accommodate games and additional software. Choosing btrfs offered snapshot and subvolume features that are useful for rollbacks but require familiarity. These sizing choices reflect a preference for separating Windows and Linux installations to avoid accidental bootloader overwrites by Windows updates.
Reactions & quotes
Community and official channels reflect cautious optimism: many users note that gaming on Linux is far more accessible than a few years ago, while others point to edge-case hardware or app gaps. Below are short representative statements with context.
“CachyOS targets modern hardware and prepackages gaming stacks to reduce setup time.”
CachyOS documentation (official)
This summarizes the distro’s positioning: streamlined installers, curated driver packages, and convenience tools aimed at contemporary desktops. That orientation explains why GPU drivers and basic peripherals worked out of the box in this trial.
“Proton now runs many Windows games with minimal configuration, but platform-specific titles can still require tweaks.”
Proton/Steam (official community guidance)
Proton’s rapid iteration has closed many compatibility gaps, but some titles—especially those tied to platform services—remain problematic. The Outer Worlds running and saving to the cloud is an encouraging example, while Minecraft Bedrock highlights a remaining shortfall.
“I had to resize partitions midstream, but once done the games and apps behaved as expected.”
Linux user report (community)
This echoes a common user experience: initial conservative partitioning can lead to resizing once disk demands become clearer, but resizing tools are accessible from live media when needed.
Unconfirmed
- Whether Minecraft Bedrock will run reliably via Proton on this hardware without further tweaks remains unconfirmed pending additional testing.
- The MCPE Launcher (Android-app wrapper) approach reported by some communities produced inconsistent results in initial trials and requires more validation.
- Compatibility and reliability of the ‘howdy’ Windows Hello equivalent with my specific webcam and KDE setup have not yet been verified.
Bottom line
For users willing to accept occasional tinkering, a modern Arch-based desktop like CachyOS can serve as a practical daily driver for work and casual gaming. Automatic driver detection, Proton compatibility, and universal packaging formats mean many common tasks are straightforward; printing, webcam use, and GPU acceleration worked with minimal intervention in this test. But there are trade-offs: specific commercial apps and family-focused titles such as Minecraft Bedrock still create friction, and some peripherals may need manual configuration.
If your priority is a low-maintenance, Windows-free desktop with strong gaming capability, Linux is increasingly viable—but keep a fallback plan. Installing on a separate physical drive, keeping a Windows image, or maintaining a secondary device will reduce risk while you resolve platform gaps. Over time, as Proton and packaging ecosystems mature further, those gaps should shrink, but expect a modest learning curve during the transition.
Sources
- The Verge: original report of this experiment (media)
- CachyOS documentation and wiki (official project site)
- Arch Wiki (community technical reference)
- Proton/Steam compatibility resources (official guidance)
- Ventoy (tool project site)