The Linux compatibility thread!

[Garek]

Just got Manjaro up and running, and thanks to this thread, I got 64Bit KSP running without a problem. Thank you!

In fact, the longest part was finding out where to get xxd. In case another Arch Linux or Manjaro user out there doesn't know yet: there is a xxd package in the AUR, and apparently it's also contained in vim and gvim. Maybe I was just a bit dumb at searching for it.

Now get all the mods!

[kurja]

The patcher isn't working for me, and I just noticed that when I run it it displays "Using rsync-2.0.9" - I have rsync 3.1.0?? Does the patcher say 2.0.9 for everyone else too?

[sal_vager]

Make sure your patcher is up to date, or just forget it and get the full copy from the store, the patcher should work but so many things go wrong.

[kurja]

When I last ran the launcher, it said "downloading patcher" and seemed to download a new version of it, so I can only suppose that it is up to date. On it's store login window it says it's version to be 2.0.0.200.

Now I downloaded again from store, start menu screen says version to be .23.5.0 and buildID.txt contains "build id = 464 2014-04-01_17-04-22 Branch: master". Shouldn't there be a later version?!? Running the patcher behaves as before; pastebin of sync messages: http://pastebin.com/WU2DZasE

BTW when the patcher is downloaded, it comes without the +x mode flag so won't run until I chmod it.

[sal_vager]

Yeah the flag issue is a pain but it's not a major hassle, and build 464 is the current release, running the patcher won't get you any further at this time, sorry.

[kurja]

Hm. I thought there had been a couple fixes to the 23.5 release, like the eva ragdoll issue? According to file attributes of what I downloaded from the store moments ago, nothing has been modified since release date.

[sal_vager]

There were fixes, they came out quite soon after the release, the current version is build id 464

build id = 464

2014-04-01_17-04-22

Branch: master

[kurja]

Oh, okay. Thanks for clearing that up. I saw references to version numbers >.23.5.0 in some threads around here, like this one http://forum.kerbalspaceprogram.com/threads/75586-Master-Thread-Unresponsive-Kerbals-in-EVA?highlight=ragdoll

Do I need to check the correct version number in debug console or something?

[sal_vager]

The correct version number will be in the buildId.txt, this was found to be an easier way of updating the build Id instead of changing the number in-game or rewriting the readme every time.

As you can no doubt imagine, if we're on 464 now and 0.23 was build 395, there are a lot of builds between updates

[kurja]

Ooh right! Makes sense now =) It was the .0 at menu screen that was confusing me.

[humptydump]

You can force it via the driver itself, and set up a profile for KSP in your graphics cards own software but it won't work out of the box as far as I know.

Try the environment variable. Should work with the free NVIDIA drivers as well, as they are also based on the Gallium renderer.

> GALLIUM_MSAA=8 ./KSP.bla

[miceliux]

Try the environment variable. Should work with the free NVIDIA drivers as well, as they are also based on the Gallium renderer.

> GALLIUM_MSAA=8 ./KSP.bla

Thank you! It works for me with a Radeon card.

[brickmack]

I'm having an issue with the game crashing in the VAB. As soon as I place any parts, or if I pull up the debug screen, my whole computer freezes. No input is accepted from mouse or keyboard, and it doesnt unfreeze by itself. Only way to fix it is the hold down the power button. I'm not seeing anything that looks relevant in the ksp.log file. This seems to be a new issue with Ubuntu 14.04, as I had the ARM update working fine on 13.10. I did the memory address patch for 64 bit ksp, but that didnt help (and the game ran fine on 13.10 without the patch, so I dont think its a memory issue anyway). Ive looked through the last few pages of this and didnt see anything, anyone got any ideas?

[cantab]

To narrow down the problem a bit, have you tried:

Ctrl+Alt+F1? Give it a few minutes if need be, that should switch you to a text console. If it does, the problem is likely KSP hogging RAM or CPU.

Hold Alt+SysRq/Print Screen, hit R, E, I, S, U, B giving a few seconds between each key. That will reboot your computer in a somewhat more orderly fashion than hitting the power switch. If nothing else it'll help when you're troubleshooting this issue. If this doesn't work I believe the problem is probably down to your graphics drivers, consider changing them to a different version. Alternatively the Alt+SysRQ combinations may have been disabled, I don't recall Ubuntu doing that but it's worth checking.

(The commands are take Raw keyboard control, terminate all processes nicely, kill all processes without prejudice, sync the disk caches to the disks so you don't get filesystem corruption, unmount the disks, and reboot the computer.)

[brickmack]

To narrow down the problem a bit, have you tried:

Ive tried all of those with no success, except the graphics drivers. I will try that later tonight

[brickmack]

OK it seems to have been a problem with the fglrx drivers, ive reverted to the standard xorg one. Not seeing any crashes so far

[sal_vager]

I wish AMD would fix their driver :/

[paulkoan]

I'm having an issue with the game crashing in the VAB. As soon as I place any parts, or if I pull up the debug screen, my whole computer freezes. No input is accepted from mouse or keyboard, and it doesnt unfreeze by itself. Only way to fix it is the hold down the power button.

I had this exact issue with Gentoo + 64Bit KSP. If I kept things simple I could get as far as a launch, but it would always freeze at some point.

However, I was able to log in using ssh from another machine - have you tried this? When I did, and checked dmesg, messages, KSP.log, Player.log, Xorg.0.log nothing had any indication there was an issue.

However, if I tried to restart X (in my case, by restarting kdm) it would eventually lead to an "ASIC hung happened" error in dmesg. Not straight way, but after a minute or so. Then rebooting was still the only way to get it back up and running.

Eventually I realised that I had installed the 14.x beta drivers. Once I reverted to 13.2 drivers, everything worked. I suspect at 13.2 ati drivers are the only ones that work.

[paulkoan]

I am using KSP 64bit under gentoo with 13.2 ati-drivers.

This works well, I haven't hit any issues. Very smooth, audio works.

The only thing that isn't quite right is when re-entry atmospheric effects kick in, the frame rate drops dramatically. It picks up once the flames subside.

Is this common to ati-drivers or just me? I am running a recent Core i5 with 16GB ram. The CPU doesn't get particularly taxed.

[sal_vager]

The point light sources and shadow cascades can seriously impact performance during re-entry, so try reducing them

[Yoha]

I think it would be informative to run a poll of AMD/ATI vs Nvidia amongst users encountering bugs. I feel like ATI is really painful to work with on Linux.

[lambdafu]

KSP crashes reproducibly for me when launching ships and crossing 2.8km height on Intel HD4000 GPU under GNU/Linux (in my case: Fedora20 with stock or latest Intel drivers). I could work around it by setting aerodynamic effects to "minimal". I could also work around it by hacking the binary to re-enable shadow support on Intel cards, even if "aerodynamic effects" is not "minimal", but at highest setting. So I can confirm the following report:

In my case, this problem was fixed by the following the instructions for enabling (or rather preventing the disabling of) shadows under Intel graphics cards. This fixed the crashes in both the 64 bit and 32 bit binaries. I noticed some other posts mentioning that this fixed crashes for other people with these cards. Perhaps the OP could be changed to note that this fixes more than just shadows?

My Laptop is a Thinkpad T430s with:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])

Subsystem: Lenovo Device 21fb

Flags: bus master, fast devsel, latency 0, IRQ 42

Memory at d0000000 (64-bit, non-prefetchable)

Memory at c0000000 (64-bit, prefetchable)

I/O ports at 5000

Expansion ROM at <unassigned> [disabled]

Capabilities: <access denied>

Kernel driver in use: i915

Kernel modules: i915

xorg-x11-drv-intel: 2.99.907 Release 2.7

Mesa: 10.1 Release 6.20140305.fc20

[paulkoan]

The point light sources and shadow cascades can seriously impact performance during re-entry, so try reducing them

Where do you think this impact is coming from? Mono or ATI drivers? The same setup under Windows 7 works fine, no perceivable performance change during re-entry.

[Vulkan]

Is this common to ati-drivers or just me? I am running a recent Core i5 with 16GB ram. The CPU doesn't get particularly taxed.

I've hit driver problems as well since upgrading ubuntu 13.10->14.04. I was using the fglrx-updates driver and all was well. Since 14.04 that now causes the freezing described by brickmack. Tried the X.Org driver and KSP runs without crashing but the lag/framerate is hideous, about 6fps on the titlescreen and worse in flight. With the other fglrx driver KSP doesn't start at all and spits something about mono paths to the terminal, so no KSP for me until somehing gets fixed.

Hardware is i5 and Radeon 7870 with 8G ram, so not limiting. I had a large number of mods without too many issues before the ubuntu update.

[phoenix_ca]

I wish AMD would fix their driver :/

What's wrong with it?

I'm running Ubuntu 14.04 on an iMac 12,2 (Mid 2011, i7, AMD Radeon HD 6970M 1GB), with Catalyst Control Center 14.4 for linux, and it works wonderfully. Force Adaptive MSAA in the 3D settings (sudo amdcccle is enough to get by; I should probably use gksu but I couldn't get that working properly and sudo did launch CCC just fine), and you're golden. Might need to finagle the settings.cfg yourself but still.

Edit: To be fair, even if AMD drivers on Linux get crap performance vs Windows, it's the only way to run KSP without the 3.4GB limit in Windows. So, meh. Still the best way to play modded.

I will say this much though: Given the choice, I would never use an AMD GPU again. Not until they get their damn act together. Their drivers and software support are terrible all-around, not just on Linux, to say nothing of upcoming tech like G-SYNC. All they really have going for them is cryptocurrancy mining, not gaming.

TextureReplacer seems to be crashing my install of KSP though, for some damn reason. Need to poke that some more.

Edit: Something else is going on. Time to go diving through my GameData folder. *curses profusely*

Edit 2: Does anyone know how to invoke the equivalent of the -popupwindow argument on Windows KSP under Linux? I'm having trouble finagling that into existence. It'd be nice to have a borderless window so I don't have to use my laptop for everything else while playing. >.>

Edited May 4, 2014 by phoenix_ca