You can use pretty much any keyboard but I would recommended a keyboard that is not by a major company that has its own property software
I have a corsair k55 and the extra keys on the left they are useless because if your plug this keyboard into a PC that hasn’t corsairs icue installed it goes into " compatibility mode " aka the keyboard forgets your custom settings and keybinds
I haven’t tried Nobara, but I did use Fedora for a year or so and decided it wasn’t for me. My main complaint was how long release upgrades seemed to take. This was back when fedup was a thing (I think Fedora 17? Maybe DNF fixed that), and it took almost an hour just to do a release upgrade, which was 2-3x longer than a fresh install. I used Ubuntu before that and left for the same reason, but also because Ubuntu seemed to break something each major release.
So I switched to Arch, which worked much better imo and I used it for about 5 years. I got tired of periodic breakage (i.e. manual intervention every few months) but still wanted to keep the rolling release cycle, so I switched to openSUSE Tumbleweed. Breakage mostly went away, except for the odd NVIDIA driver screwup, but ever since moving to an AMD GPU things have been smooth. I’ve been on openSUSE Tumbleweed for a few years now and it’s still working well. You could very well have the opposite experience as me.
So I guess what I’m saying is, find something that works for you. Maybe that’s Nobara, maybe it’s Ubuntu, or maybe it’s something like Nix or Gentoo. Regardless, keep trying stuff until you find the right fit.
PlayOnLinux is not maintained consistently and hasn’t been for a couple of years. I have Diablo 2 on Lutris. It works great. However, I’m on Fedora 38, so there’s that. I don’t think that makes much of a difference, though. Your problem is probably related to PlayOnLinux being behind the times.
it’s not POL. It’s System Wine. Lutris has the same problem with system Wine (and some of it’s own Wine versions). All I’m trying to do is figure out the source and report upstream
seeing that issue spans across several games I didn’t want to post to appdb. I’ve re-jigged mynsetup to use lutris and forced wine version to be below 8.x and all is good. However my intent was not to find how to run those games, but what’s wrong? with 8.x Wine.
I’ve got Corectrl up and running with AMD Overclocking functioning on RDNA2 (6800 XT).
From yesterday’s limited testing I’m kinda blown away.
The card runs significantly more efficient under Linux so despite setting the same target clock as in Windows being 2700MHz, the cards actual clock when ruining games and not bouncing off of power limit is only 30MHz lower, on Windows it was usually around 60MHz lower.
But the major thing is that when bouncing off of the power limit I’ve seen the clock drop only by around 100MHz on Linux but on Windows it was usually a massive swing by 200-300MHz.
VRAM OC on Linux seems to be completely broken though, even increasing clock by 1MHz when on desktop will result in massive artifacts and eventual crash.
Voltage control and behaviour on Linux also seems to behave quite a bit differently than on Windows. Needs further testing though.
Looks super interesting! I read the inspiration but is it a survival game at its core? Possible to play creative like Minecraft? Thanks in advance! Hope to have the time to try it down the road!
I don’t know why so many are talking about Debian with distrobox I’m currently testing with bedrock Linux with a hijacked nobara for gaming and GNOME things. I also fetched a arch strata for anything else like window compositor waybar librewolf etc
ive gamed on just about every distro i’ve tried but i currently run debian sid its fine, linux is linux for the most part. kernel is recent enough so youre not gonna have to do any workarounds or anything.
Most of the time it isn’t about the kernel what is causing gaming problems it is most of the time other packages. I had problems with a few games on KDE neon what uses a ubuntu lts system as its base
I don’t use Sid, but testing, it’s working almost flawlessly. Each release (once every 2 years, I guess), I take few hours to check everything work; remove shader cache, etc.
My setup, right now (dirty, for authenticity) :
<span style="color:#323232;">$ cat /etc/apt/sources.list
</span><span style="color:#323232;">deb https://deb.debian.org/debian/ testing main contrib non-free non-free-firmware
</span><span style="color:#323232;">deb-src https://deb.debian.org/debian/ testing main contrib non-free non-free-firmware
</span><span style="color:#323232;">
</span><span style="color:#323232;">deb https://security.debian.org/debian-security/ testing-security main contrib non-free non-free-firmware
</span><span style="color:#323232;">deb-src https://security.debian.org/debian-security/ testing-security main contrib non-free non-free-firmware
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;"># bullseye-updates, to get updates before a point release is made;
</span><span style="font-style:italic;color:#969896;"># see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
</span><span style="color:#323232;">deb https://deb.debian.org/debian/ testing-updates main contrib non-free non-free-firmware
</span><span style="color:#323232;">deb-src https://deb.debian.org/debian/ testing-updates main contrib non-free non-free-firmware
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;"># add by me
</span><span style="color:#323232;">deb https://deb.debian.org/debian/ testing-backports main contrib non-free non-free-firmware
</span><span style="color:#323232;">deb-src https://deb.debian.org/debian/ testing-backports main contrib non-free non-free-firmware
</span><span style="color:#323232;">
</span><span style="color:#323232;">$ cat /etc/apt/sources.list.d/</span><span style="font-weight:bold;color:#a71d5d;">*
</span><span style="color:#323232;">deb http://download.opensuse.org/repositories/graphics:/darktable/Debian_Testing/ /
</span><span style="color:#323232;">deb </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;">signed</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">by=/etc/apt/keyrings/lutris.gpg</span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://download.opensuse.org/repositories/home:/strycore/Debian_Testing/ ./
</span><span style="font-style:italic;color:#969896;"># Uncomment these lines to try the beta version of the Steam launcher
</span><span style="font-style:italic;color:#969896;">#deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ beta steam
</span><span style="font-style:italic;color:#969896;">#deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ beta steam
</span><span style="color:#323232;">deb </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;">arch=amd64,i386</span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://repo.steampowered.com/steam/ stable steam
</span><span style="color:#323232;">deb-src </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;">arch=amd64,i386</span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://repo.steampowered.com/steam/ stable steam
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;"># Uncomment these lines to try the beta version of the Steam launcher
</span><span style="font-style:italic;color:#969896;"># deb [arch=amd64,i386] https://repo.steampowered.com/steam/ beta steam
</span><span style="font-style:italic;color:#969896;"># deb-src [arch=amd64,i386] https://repo.steampowered.com/steam/ beta steam
</span><span style="color:#323232;">
</span><span style="color:#323232;">
</span><span style="color:#323232;">deb </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;">arch=amd64,i386 signed</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">by=/usr/share/keyrings/steam.gpg</span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://repo.steampowered.com/steam/ stable steam
</span><span style="color:#323232;">deb-src </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;">arch=amd64,i386 signed</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">by=/usr/share/keyrings/steam.gpg</span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://repo.steampowered.com/steam/ stable steam
</span><span style="color:#323232;">deb </span><span style="font-weight:bold;color:#a71d5d;">[</span><span style="color:#323232;"> signed</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">by=/usr/share/keyrings/vscodium</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">archive</span><span style="font-weight:bold;color:#a71d5d;">-</span><span style="color:#323232;">keyring.gpg </span><span style="font-weight:bold;color:#a71d5d;">]</span><span style="color:#323232;"> https://download.vscodium.com/debs/ vscodium main
</span>
I play a lot, we just played Grounded with friend yesterday.
Instead of relying on testing directly, consider using named releases (in this case, trixie for testing). Then stay on the official release for a couple months as testing stabilizes and then go to the next testing release.
I did that in the past and it worked really well. Testing gets a lot of churn right after a release as packages get rapidly upgraded, so I find it’s usually better to wait a bit.
Testing goes stabler and stabler with time. Then testing move to release and the previous untesting (sid) move to testing. It’s a that moment that you can have surprise. This is the moment where I often wait one month or two, apply the updates and check my os is working as before, meaning running my day to day applications and game and see if things work. The only problem I had once was shader cache. I removed few things in .cache and I was good.
I’ve only played Chiv 2 on my desktop, but for EAC games I had to install EAC seperately. I’d assume the SteamDeck would do this for you, but maybe it didn’t install properly?
linux_gaming
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.