Language Selection

English French German Italian Portuguese Spanish

How to Build a Linux Gaming PC

Filed under
Linux
Hardware
Gaming
HowTos

The free Linux operating system has been around for ages, but its inherent complexity and limited support has always relegated its use to extreme enthusiasts, programmers, and other hardcore types. That might be changing, though, as a lot of loyal PC enthusiasts are less than pleased with Windows 8, and gaming juggernaut Valve has thrown its hat into the ring by launching a Linux version of Steam, its popular online content delivery service. Given the lackluster reception of Windows 8 and the renewed popularity of Linux, we decided to build a Linux gaming box to see for ourselves whether the OS, at this time, could be a reasonable alternative to Windows for gaming.

Choosing the Hardware

Our Linux machine was built with a low target price of $650 because we wanted this project to be semi-easy to duplicate by anyone. With this in mind, we started with Intel’s Ivy Bridge Core i3-3220 processor, as it comes at a reasonable cost, gives us a great upgrade path, and its low TDP of 55W means we won’t need a massive CPU cooler or PSU. Our Asus P8Z77-V LE motherboard is also affordable while offering both SLI and CrossFire support, as well as two USB 3.0 ports. Power is provided by a CX430 Corsair power supply from the company’s low-cost Builder series. Given our modest build-out, we figured anything bigger than 430W would be overkill.

rest here




I can do better

I bought a factory refurbished HP XW8600 workstation with 32GB of memory and a 1TB drive on eBay for less than that. It has dual quad-core Xeons running at 3GHz too. I also got a GT520 graphics card with 1GB of memory. This thing rocks.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)