Feral Interactive's GameMode is supposed to be a free performance boost: the moment a game launches, it temporarily switches your CPU governor to performance, tweaks I/O priority, and (on supported GPUs) applies a small GPU performance nudge — then reverts everything when you quit. On Linux Mint 22 and 21.3, though, a very common complaint is that GameMode installs cleanly, shows up in Steam's launch options, and does absolutely nothing. No governor switch, no FPS gain, no log entry confirming it ever activated.
This happens because GameMode silently fails when it lacks permission to touch your CPU governor, when the launch command is malformed, or when the daemon simply isn't running as a systemd user service. None of these failures throw a visible error in Steam — the game just launches normally, minus the boost. This guide walks through every real cause and the exact terminal commands to fix it on Linux Mint.
What GameMode Actually Does (and Why It Silently Fails)
GameMode is a client/daemon pair. The gamemoded daemon runs as a systemd user service and listens over D-Bus. When a game calls gamemoderun (or links against libgamemode), it asks the daemon to apply optimizations for the duration of that process. Two things can silently break this pipeline on Mint:
- The daemon isn't allowed to change the governor because your user isn't in the
gamemodepermission group. - The launch command never actually invokes
gamemoderun, so the daemon is never asked to do anything.
Step 1: Confirm GameMode Is Installed and the Daemon Is Running
First check the package is present and see which version you have:
dpkg -l | grep gamemode
gamemoded -vIf it's missing, install it from Mint's repos:
sudo apt update
sudo apt install gamemodeNow check the systemd user service status:
systemctl --user status gamemodedIf it shows inactive, that's fine — GameMode's daemon is designed to start on-demand via D-Bus activation when a game requests it, not run persistently. What matters is that it starts and logs correctly when triggered, which you'll test in Step 4.
Step 2: Add Your User to the gamemode Group
This is the single most common cause of "GameMode does nothing" on Linux Mint. Without group membership, gamemoded refuses to change the CPU governor or renice your game process — and it fails silently rather than throwing a permission error you'd notice.
sudo usermod -aG gamemode $USERGroup changes require a fresh login session to take effect. Log out and back in, or simply reboot:
rebootVerify the group is applied:
groups $USER | grep gamemodeIf that returns nothing after rebooting, check whether the group actually exists — some Mint installs need it created manually if the package's postinst script didn't run properly:
getent group gamemode || sudo groupadd gamemode
sudo usermod -aG gamemode $USERStep 3: Fix the Launch Options in Steam, Lutris, and Heroic
GameMode only activates if the launch command actually wraps the game binary with gamemoderun. A surprisingly common mistake is placing it after the command placeholder instead of before it.
Steam: right-click the game → Properties → General → Launch Options, and set:
gamemoderun %command%If you're also using Proton with MangoHud for an FPS overlay, chain them in this order:
gamemoderun mangohud %command%Lutris: open the game's configuration, go to the System options tab, and enable the "Feral GameMode" toggle directly — Lutris has native support and doesn't need the manual wrapper.
Heroic Games Launcher: in the game's Settings → Other, enable "Enable FSR Hack" section's neighboring "Enable Feral GameMode" checkbox, or manually prepend gamemoderun in the advanced launch parameters field.
For non-Steam native Linux games launched from a terminal or a custom .desktop file, just prefix the binary directly:
gamemoderun ./YourGameBinaryStep 4: Diagnose with gamemode-simulate-game
Before blaming a specific game, confirm GameMode itself works using its built-in test utility, which mimics a game requesting optimizations without needing to launch anything:
gamemode-simulate-gameRun this in one terminal, and in a second terminal immediately check the governor:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorIt should read performance while the simulation runs, then drop back to powersave or schedutil afterward. If it doesn't change, check the daemon's live log output for the actual failure reason:
journalctl --user -u gamemoded -fCommon errors here include Denied "set" method call (a group permission issue — go back to Step 2), or Governor... unsupported, which usually points to a driver-managed governor (common on some AMD systems using amd-pstate-epp) that GameMode can't override with the classic cpufreq interface.
Step 5: Fix "Unsupported Governor" on AMD amd-pstate Systems
Modern AMD CPUs on Linux Mint 22 often default to the amd-pstate-epp driver instead of classic acpi-cpufreq, and GameMode's default configuration doesn't always know how to set an "epp" preference correctly. Check which driver you're on:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driverIf it reports amd-pstate-epp, edit GameMode's config to add an explicit governor override in the [cpu] section:
sudo nano /etc/gamemode.ini[general]
renice=10
[cpu]
park_cores=no
pin_cores=noThen set the energy performance preference manually as a custom start/end script inside the same file, which GameMode will run automatically:
[custom]
start=/usr/bin/bash -c "echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference"
end=/usr/bin/bash -c "echo balance_performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference"Since these commands need root, add a matching sudoers rule scoped only to that exact command so GameMode's daemon (running as your normal user) doesn't prompt for a password mid-game:
sudo visudo -f /etc/sudoers.d/gamemode-eppyourusername ALL=(ALL) NOPASSWD: /usr/bin/tee /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preferenceStep 6: Confirm the Fix Inside a Real Game
With everything configured, launch a game through Steam with the gamemoderun %command% launch option set, and overlay MangoHud to visually confirm the governor and clocks during play:
MANGOHUD_CONFIG=cpu_stats,cpu_freq,gpu_stats gamemoderun %command%You should see CPU frequency pinned near its boost clock instead of idling low between frames — that's the visible sign GameMode is actually doing its job rather than just being listed in the launch options.
When to Get Professional Help
If GameMode still won't activate after fixing group permissions, launch options, and the governor override — or if your system uses a laptop-specific power daemon like power-profiles-daemon or TLP that's fighting GameMode for control of the CPU governor — untangling the conflict between multiple power management services can take real diagnostic time. For gamers who'd rather spend that time actually playing, CloudHouse's pay-per-ticket Linux support can resolve GameMode, power-daemon conflicts, and other Linux Mint gaming performance issues with a single paid ticket, no subscription required.
Frequently Asked Questions
Why does GameMode show as installed but never actually activate?
The most common reason is that your user account was never added to the gamemode group, so the daemon lacks permission to change the CPU governor and silently does nothing. Run sudo usermod -aG gamemode $USER and reboot.
Do I need gamemoderun if I'm using Lutris?
No. Lutris has a native "Feral GameMode" toggle in each game's System settings tab that calls GameMode internally — you don't need to manually add gamemoderun to the launch command.
How do I know if GameMode is actually working during a game?
Run gamemode-simulate-game in a terminal and watch /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor switch to performance. During real play, a MangoHud overlay showing pinned CPU frequency is the clearest live confirmation.
Does GameMode actually improve FPS on Linux Mint?
The gain depends heavily on your CPU and power profile defaults. Systems that idle in a conservative governor like powersave or schedutil see the biggest benefit, since GameMode forces sustained boost clocks during gameplay; systems already running performance by default will see little to no change.
Why does GameMode fail specifically on AMD Ryzen laptops?
Many Ryzen laptops use the newer amd-pstate-epp driver instead of classic acpi-cpufreq, and GameMode's default config doesn't set the energy performance preference on that driver out of the box. You need a custom start/end script in /etc/gamemode.ini plus a scoped sudoers rule, as covered in Step 5 above.