The extreme left and extreme right spaces have a lot in common. Purity tests and instant bans for anyone not sharing the same groupthink is probably the biggest things.

New people don’t realize that Linux is really a soap opera with a small software project attached.

Let’s say such a change happens and at that time there’s a bit of time pressure and the capacity on the rust maintainers is thing for whatever reasons. Will they still happily swallow that change or will they start to discuss if it’s really necessary to do that change? And suddenly, the C-maintainer has a political discussion on top of the technical issue they wanted to solve.

This situation could occur even if the code using the API was written in C.

If an API change breaks other downstream kernel code, and that code can’t be fixed in time then they have a conversation about pushing the changes to the next build.

In the end, Linus has already chosen to accept the extra development overhead in using Rust. I think this situation was more about a maintainer, who happens to disagree with the Rust inclusion, using their position to create unnecessary friction for other maintainers.

No, you can’t find any copyrighted text inside the model’s weights.

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)

99664.262:00d4:00d8:err:xrandr:xrandr14_get_adapters Failed to get adapters

Hmmm, this gets some hits. It seems like it isn’t able to figure out which driver to use.

You can specify the driver that Vulkan should use by adding an environmental variable VK_ICD_FILENAME set the the json file for your card.

Try editing a game and changing the launch options to:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

In machine learning, that task is referred to as classification

I had all of these problems with Jellyfin and then I discovered Netflix (www.netflix.com/totallynotareferral)

Maybe they don’t want to clean up a fresh install of Windows, maybe they don’t own a computer, maybe they don’t have arms, maybe they can’t read

https://xkcd.com/927/

The walls get hot, you absorb the heat from the walls with a fluid. You use the fluid to heat water, you use the steam to drive a turbine, you use the turbine to turn a permanent magnet inside of a coil of wire. In addition, you can capture neutrons using a liquid metal (lithium) which heats the lithium, which heats the walls, which heats the water, which makes steam, which drives a turbine, which generates electricity.

If you poured water onto them they wouldn’t explode. 100 million degrees Celsius doesn’t mean much when the mass is so low compared to the mass of the water.

Until you see companies selling liquid nitrogen generators, you’re not going to have to worry about anyone pushing quantum chips on the average consumer.

It prints in white text on a black background

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

sometimes nvidia drivers are in a state that breaks display reinit on wake from sleep

That happens so often that I’ve just bound a hotkey in Hyprland to poke my monitors config (toggling VRR off and on again) in order to force a mode change and wake up the display.

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.

TempleOS is all anyone needs