AMD Hybrid Graphics on Linux: Dedicated GPU Shuts Off After 5 Seconds

Gaming on Linux with AMD Hybrid Graphics: Five Seconds of Glory

Why does Windows move games to the dedicated GPU while Linux gives up after five seconds? An MSI GX70 3CC laptop, packed entirely with AMD hardware, tries to rise from the dead. The sequence repeats with clockwork precision: the game launches, the dedicated graphics card lights up its LED, and five seconds later it turns off. Identical results occur on Ubuntu, Zorin OS, and Pop OS. On Windows, the same machine works without drama. Its owner sums it up with an image worth more than a technical report: it is the equivalent of a Seat 600 with a Ferrari engine.

What Fails in the Hybrid Graphics of an MSI GX70

The laptop combines an integrated graphics card and a dedicated one, distributing work based on what is running. That distribution is what breaks. In Windows, the system switches when it detects a game; in the tested distributions, the dedicated GPU never takes full control. The LED that turns on and off is physical proof of a handover that never completes.

The detail that rules out hardware failure is simple: the same device plays without issues with Windows installed. There is no dead hardware, but rather a software chain—kernel, drivers, compatibility layer—that fails to understand this configuration. Several participants argue that hybrid graphics support has always been the Achilles' heel of free desktops.

The Kernel Parameter That Forces the amdgpu Module

The circulating solution for this family of cards involves blocking the old module and activating the modern one. Boot the system with radeon.si_support=0 amdgpu.si_support=1. If the bootloader is GRUB, place that line in /etc/default/grub within GRUB_CMDLINE_LINUX_DEFAULT, regenerate the configuration with grub-mkconfig -o /boot/grub/grub.cfg, and reboot.

The underlying argument, according to those who defend it, is that instructions are published on thousands of pages and no luck is needed. The counterargument carries equal weight: if playing requires editing the bootloader, half the potential audience has already left. A five-second LED is all the diagnosis received by someone who just wanted to install Steam.

How Many Distributions Must Be Tested Before Giving Up?

Ubuntu, Zorin OS, and Pop OS share ancestry, so testing three flavors of the same trunk is not testing three systems. One participant recommends switching to Fedora, openSUSE, or Mageia, sticking to major distros rather than derivatives with proprietary names and promises of miraculous performance.

The inventory of candidates is overwhelming. Between 15 and 20 different distributions have been counted by the affected user, including specific gaming editions. For veterans, almost all descend from a handful of trunks: Debian, Red Hat, Slackware, Arch Linux, and Gentoo. For newcomers, the landscape is a labyrinth where every voice recommends something different.

Vulkan 1.3 Revives Old AMD GPUs, Vulkan 1.4 Leaves Them Behind

While all this is discussed, the ecosystem moves underneath. Some older AMD graphics cards have received support for Vulkan 1.3, the minimum required by modern versions of Proton. These are exactly the ones that, according to this account, need to manually block the radeon module and use amdgpu: the GCN1/GFX6 and GCN2/GFX7 families.

The relief comes with an expiration date. The announcement of Vulkan 1.4 raises the bar: at least a GCN 3 GPU on AMD or a Maxwell on Nvidia will be required to run modern Proton versions. Those that just regained support are excluded due to physical silicon limits. An HD 7950 bought twelve years ago runs the latest Proton version again with Mesa 24.3. A victory with the expiry date printed inside.

Is It Last Century's Hardware or Lack of Support?

Here two narratives clash. One argues that a device of those years does not deserve the effort and that with decent hardware and some skill this flies. Another points to support, bringing better examples than the protagonist laptop: machines 13 years old with 8 GB of RAM, an SSD, and a GTX 1050 Ti running Resident Evil 2 Remake effortlessly and with ridiculous power consumption.

There is also proof that the problem is not Linux in the abstract. Some games hung on Windows and work with Proton, and vice versa cases exist. The result depends on the title, the graphics card, and the driver version. For those who do not want to fight, shortcuts remain: keep Windows on another disk or pay five euros a month for cloud gaming.

Conclusion

The laptop ended up using Linux for office tasks, and not even for that: a management role ended in Windows because the browser did not give access to the camera. Years later, the scene remains recognizable. Console, kernel parameter, reboot. And pray.