this post was submitted on 30 Apr 2026
83 points (98.8% liked)

Linux Gaming

25711 readers
12 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

Help:

Launchers/Game Library Managers:

General:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
83
[Solved] Terrible performance in Linux Mint compared to Windows (piefed.ca)
submitted 1 week ago* (last edited 1 week ago) by PlzGibHugs@piefed.ca to c/linux_gaming@lemmy.world
28 comments fedilink hide all child comments
 

I have an older computer that I use for some simple games. Its I5-7400, GTX-1050, 12GB memory, and an SSD - not new by any standards, but most of the games I'm playing are a decade old or more. I switched to Linux Mint today, since I don't want to use Windows 11, but the performance on Mint is terrible compared to Windows 10. For example, in Portal 2's native Linux version, I get like 10 fps in the title screen. War Thunder doesn't even launch. The drivers are set to Nvidia's proprietary drivers via the GUI. Am I missing something? I'd really rather not switch back to Windows.

Edit: VulkanInfo is saying, "ERROR: [Loader Message] Code 0: loader_scanned_icd_add: Could not get 'vkCreateInstance' via..."

It also seems to only be showing my CPU, not gpu? Not certain, since I don't unstand a lot of the details, but it says, "deviceType = PHYSICAL_DEVICE_TYPE_CPU".

Edit 2: turning off secureboot fixed it.

you are viewing a single comment's thread
view the rest of the comments
[–] savvywolf@pawb.social 1 points 2 days ago

My gut reaction is that there are a lot of ways, once you have root access, to have your changes persistent. For example, modifying/replacing binaries, adding new ones before old ones in the path, adding startup scripts, modifying config files. Kernel modules seem to be an overcomplicated way to go about it, especially since (afaik) it would need to be compiled against the specific kernel version.