• 0 Posts
  • 42 Comments
Joined 12 days ago
cake
Cake day: February 10th, 2025

help-circle


  • Dude, the number of times I’ve resorted to a reinstall are innumerable. You know a bit more than you did yesterday and that isn’t nothing.

    If you want to try a new project that’ll need tinkering with (but won’t break your existing install) look at gamescope.

    Currently it’s the only way to get HDR and variable refresh rate to work. It’s what Valve made to get those features into the Steamdeck.

    You just run it with

    gamescope -- %command%
    

    In your steam launch options. You’ll need to look up the options (otherwise it defaults to 720p@60hz). Ex:

    gamescope -w 2160 -- %command%
    

    For 4k. There’s a switch for HDR too but I don’t remember it without looking it up. You can use gamescope to enable FSR in any game, it can apply reshade shaders (so, things like anti aliasing in games that don’t have it natively).

    Other than that, any issues you have with a particular game can usually be solved by looking at protondb.com

    Keep using the GE-Proton builds of proton for best results.

    Have fun 🤓


  • Yeah, you have Vulkan and Mesa and the GPU drivers are in the kernel. That’s the whole stack (along with Proton).

    Before reinstalling completely, run a full system upgrade, I took this from system76s support page:

    sudo apt update
    # configure any packages partially setup 
    sudo dpkg --configure -a 
    # fix any missing package dependency 
    sudo apt install -f 
    # upgrade all packages and dependencies to newest in release 
    sudo apt full-upgrade 
    # make sure the `pop-desktop` meta package is installed 
    sudo apt install pop-desktop
    

    You’re also likely using some flatpak applications, so:

    flatpak update
    

    Then reboot.

    They want you to reinstall because walking you through a fresh install is just more time efficient for their support staff than trying to troubleshoot system configuration problems (imagine the possible things a random user could change x.x).


  • I just noticed my reply from my phone didn’t go through x.x

    This seems a lot like you’re missing some 32bit libraries. There isn’t a /usr/share/vulkan/icd.d/radeon_icd.i386.json listed in the vulkan logs.

    I have no idea how they’d be named in PopOS, but I’d look into vulkan first. You may have the vulkan-radeon 64bit drivers , but not the 32bit. Wine needs the 32bit libraries for the time being.

    Check

    dpkg -l | grep vulkan
    

    (or post all of dkpg -l if it isn’t too long)

    to see if you have the i386 version of the vulkan radeon drivers (for reference, in arch this is lib32-vulkan-radeon, possibly the same in PopOS)

    If not install them (apt search vulkan and look for something with vulkan, radeon and i386 in the file name)






  • It’s because your data is orders of magnitude more valuable if it has enough information to identify you as a person.

    They can’t sell it to data brokers for a lot of money if those data brokers can’t find any information to link that data with their existing profiles.

    Surveillance capitalism 101, companies obtain the most value by enabling other corporations to spy on every detail of your life.

    If you can’t use a service anonymously, without it being linked to your actual person, then you can either be okay with living with the panopticon, or don’t use the service.

    Discord has been slowing rolling this out over the years. It started being offered as a “spam protection” feature and eventually it’ll be a requirement to have an account.

    They depend on the masses of people who will trade all of their privacy in exchange for not having to learn how to use VoIP software, video streaming software or IM software.



  • No errors, that’s good and also not useful :/

    As an aside, this is likely not the problem, but a good tip in general, is to use protonup to install GE-Proton (https://github.com/GloriousEggroll/proton-ge-custom). It is a community fork which essentially Proton Experimental + community fixes. The System76 article I linked above has the instructions (TL;DR, install protonup (terminal) or protonup-qt (GUI) and they’ll grab it for you and put it in the right directory, restart Steam and select the new version from the Compatibility menu either globally or per-game).

    You essentially always want to be using the latest version of Proton unless something that was working breaks in a newer version.

    So, next step, more logs:

    You can enable proton logging by setting PROTON_LOG=1 as an environmental variable. You can do this per-game by right clicking a game -> Properties -> General and editing the launch options to say

    PROTON_LOG=1 %command%
    

    Launch the game and let it crash or whatever. There will be a steam-$APPID.log in your home directory.


  • Stay with experimental for now.

    Do other games show a similar behavior or is it limited to KSP?

    BG3 should work fine (was just playing it on Linux about 30m ago, but Arch, btw, etc).

    You can get some extra logging from steam, if you exit completely and the, in a terminal, run:

    steam -d
    

    It’ll start Steam but output a lot of info to the terminal. The bit we’re interested in isn’t the stuff that it generates while Steam is starting. We want the bit that happens when you press play on a game. It’ll output the information about the important bits (like the Vulkan device, driver versions, monitors, etc )

    Make sure there’s no obvious account info in the logs (there shouldn’t be, but always check) and post that.

    I’m off to bed but I’ll check in with you tomorrow



  • OP, I didn’t see if you’d confirmed that you’d enable Steam Play, see this article: https://support.system76.com/articles/linux-gaming

    Kerbal Space Program has a Linux native client and a windows client. By default, Steam will try to install the Linux native client, which is using OpenGL and, apparently, doing software rendering.

    You could try to troubleshoot why OpenGL is broken, you probably are missing an environmental variable or something to tell it to use a specific device and so it defaults to software. However, this is kind of a moot point. Development stopped on OpenGL in 2017 and so bugs and weirdness will continue to crop up and fixing it won’t resolve your core issue (Which may be that you’re just not using Proton).

    If you’re going to game on this system then you should do what most people do and enable Steam Play and let Steam download the Windows version of KSP and run it through Proton (aka Steam’s version of WINE). Often the Windows versions of games are more supported than the Linux native versions and WINE/Proton do an excellent job of translating the underlying windows system calls into Linux-ese. Proton is the primary reason why gaming on Linux works, because it lets you just play the Windows version of games.

    Your logs indicate that your graphics card is the default device for Vulkan and so it should just work as soon as you enable Steam Play. If you have any problems with other games (once you verify that you’re using your graphics card) you can look them up on Protondb (https://www.protondb.com/) and see if you need to make any setting changes. KSP looks to have a Gold rating and appears to work with Proton without any changes.