• 0
skeevy

The Other Linux Thread

Question

The first thing you need to do is go and read the first page of the Unmodded Linux Thread. And I mean the entire first page of that thread. It contains a lot of good general information for KSP on Linux.

One thing the Unmodded Thread doesn't go into very well is your choice of disto, kernels, desktop environments, Steam quirks, and more. There are literally hundreds and hundreds of different Linux distors to choose from*; all with different window managers, desktop environments, ease-of-use for noobs, style of update, rolling or non-rolling release, and more.

*though in reality, there's only about 20 or 30 worth a crap ones; the rest are just clones, respins, or for very specific tasks; think email server, forensics, hacking, compiling code, media servers, HTPC, etc

So which distro is best for KSP?

Honestly, that's a hard question to answer. IMHO, the choice varies by your graphics hardware. If you have an Nvidia GPU, you can pretty much install whatever distro you're comfortable with because you'll have to use the Nvidia proprietary driver. If you have an Intel GPU, you need to be running a bleeding edge distro so you'll be able to use the updated software and drivers. If you have an AMD GPU, you actually have some choices -- you can pick whatever and go with the Catalyst Proprietary drivers or go bleeding-edge and use the Radeon Open Source driver. It should be noted that AMD plans to use the Radeon driver (renamed to amdgpu) as the base for both the free and Catalyst drivers within the next year.

Another thing to consider when picking your distro is if it's a rolling release or not. If you don't know, a rolling release distro is install once and as long as you keep is updated, you're always up-to-date. Non-rolling releases distros, like Ubuntu and Debain, will require you to either install a new version every so often** or for you to do a risky upgrade process that might potentially break the system (especially risky if you tweak a lot of stuff). Both styles have their respective pros and cons. For Rolling, the pros are always being up-to-date while the cons are one of those updates might break something. For Non-Rolling, the pros are you know you're running a stable system while the cons are you'll soon be out of date and you'll eventually have to reinstall or do an upgrade.

**every 6 months in Ubuntu's case; up to years for Debian (Debian Stable, while stable, is usually really out of date...you really don't want Debian Stable as a gamer's OS, IMHO)

Whatever Distros -- Ubuntu 14.04 (LTS), Mint 17, Debian Stable, SUSE, Fedora (all non-rolling)

More Up-To-Date -- Ubuntu 14.10, Debian Testing, Manjaro***, Debian Sid, Siduction (all rolling except Ubuntu)

Bleeding Edge -- Arch, Gentoo, Funtoo, Sabayon (all rolling)

***that's the distro I use

I recommend Manjaro. While it might not be the most noob friendly, it's just as easy to install as Ubuntu, and once configured, just as easy to maintain. With the way Manjaro is setup, it's really easy to change between the free and proprietary drivers (hint, hint AMD GPU users). Manjaro is also a hybrid rolling/non-rolling release. What Manjaro does is they snapshot the Arch Linux repos and call that Unstable, do some fixes called Testing****, do any other fixes and call that Stable. Manjaro gives you the bleeding edge of Arch Linux with scrutiny and fixes. If you've ever ran Arch, did a "pacman -Syu", and broke your system, you'll understand and appreciate that. You also have access to Arch's AUR (to an extent...do not use the graphics drivers or the kernels with proprietary drivers) which is access to almost every piece of Linux software available. Manjaro isn't all fun and games. It does require some terminal fixes from time to time (just check the Manjaro forums, you'll find the fix usually). On my first boot, my system was semi-broke and I had to do a bit of searching to fix it; all I had to run was "pacman -Syyuu" and reboot, but if ya didn't know what to search for or weren't used to Linux, something like that can really discourage further use and scare a new user off.

After Manjaro, my recommendations would be Debian Testing, Fedora, or Ubuntu 14.10 with the Xorg-Edgers PPA...actually, all Ubuntu users, regardless of version, that are primarily running Linux just to play KSP should be using the Xorg-Edgers PPA, especially Intel, Nvidia Proprietary, Radeon driver users...not as much if you use AMD's Catalyst driver. Siduction (a distro based on Debian Sid) is also a decent choice to use, but like Manjaro, might require the terminal from time to time.

Out of all the rest I listed above, they're good distros, but they come with steep learning curves and aren't recommended for new users to start with. Once some experience is gained and you have some free time, give Arch or one of the Too's a shot. You'll learn a lot starting with a terminal-only minimal system, configuring everything by hand, and building your system from the ground up.

To Steam or Not to Steam? That is the Question.

By that, I simply mean to launch KSP from within Steam, to run KSP from a script, or directly ran from the executable. For most of ya'll, you're going to want to run KSP with a script. Why? Because Steam uses old Ubuntu 12 libraries and KSP likes up-to-date libraries. Those old libraries are why so many Linux Steam KSPers post help questions. One exception to this is with Manjaro & Arch Linux's Steam-Native package that replaces the Ubuntu libraries with symlinks to your system libraries; which allows you to run KSP with Steam using your native system libraries versus using the old Ubuntu libs. Skip to the end of the post for my personal launch script.

Kernels

Just like the distro and KSP, this also depends on your GPU. Intel and Radeon users really want the most up-to-date kernel their distro supports so you'll be using the most up-to-date graphics driver for your respective GPU. Nvidia users, like stated above, you're locked into using the proprietary driver and therefore your choice of kernel isn't as much of a factor, still, newer shouldn't hurt. Regardless of your GPU, don't pick a low latency kernel. They're not the best for gaming and you might even lose some FPS if you pick one.

Desktop Environment

This is one of those "you should pick this yourself" things. But for gaming, you're going to want a DE like XFCE, LXQT, LXDE, & Enlightenment. With any of those, you'll be using less resources for the base system which means more resources for KSP and your games to use. Of the four, my personal favorites are XFCE and Enlightenment. There are even lighter options, but frankly, unless you pick a distro like Manjaro Openbox Edition or Arch Bang, you'll be in for a steep learning curve and you'll have to set up almost everything by hand. There are other popular desktops like KDE, Gnome, and Unity, but desktops like that use a lot of resources that you'd rather have for KSP. If you have a quad core or better CPU and 8GB or more of ram, you can pick whatever you want. If you have less that that, you'll be screwing yourself unless you pick a lightweight option. I have a quad-core with 8GB of ram, I run XFCE and Enlightenment (I swap between the two every few boots for a change of scenery).

With all the choices there are, a basic intro to Linux with a focus on KSP should be helpful to a newcomer. I just hope this gives a new user an idea of what to look for in a distro and why you might want to use a respin like LxUbuntu over Ubuntu or something more up-to-date like Manjaro, Arch, or Sid.

Start-up Scripts

For Quad Core PC's

#!/bin/sh

export LC_ALL=C
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
exec taskset -c 2-3 ./KSP.x86_64

For Single Core PC's

#!/bin/sh

export LC_ALL=C
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
./KSP.x86_64

To use these, create a blank document in your KSP directory named "ksp.sh" (don't use the quotation marks " " dammit). Copy and Paste the above into it and save. Next, mark it as executable, either by ticking the right tick-box in the right click properties menu or by opening a terminal to your KSP directory and using this command "chmod +x ./ksp.sh" (again, don't use the quotation marks). Now all ya have to do us just double click that script to play KSP.

If you notice, the only difference between those is "exec taskset -c 2-3". What that little snip does is tell KSP to use the 3rd and 4th CPU cores (0=1, 1=2, so on and so forth). If you have an 8 core, you could use "-c 6-7" to use cores 7 through 8 or "-c 3-7" to use cores 4 through 8. Run "man taskset" for more information. Currently, KSP only benefits when forced down to two cores. The script above uses those two cores because they run the lightest when nothing else is going on on my PC. Your results may vary, but any two cores other than the main/1st core is better than not doing anything at all.

Note for Intel users. I don't have an Intel GPU to test the LD_PRELOAD and export __GL_ commands. Those are helpful for Nvidia users and they've never given me negative performance with either the Radeon or Catalyst drivers with my AMD R7 260x. If you have issues, remove those two lines. If those issues still persist, you need an actual GPU or start praying that Intel makes you a decent driver (that's a wish in one hand, poo in the other situation).

Post here if you need some Linux specific help and you run a modded KSP.

I'll be updating posts 2 & 3 as more questions come in and fixes are found.

Edited by skeevy

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0
I'm having this weird problem where inputting values in a mod UI, like MechJeb or Crew Manifest, triggers action groups and other functions bound to that key. Is that a known Linux issue?

Remap your action groups to the numberpad keys, since they don't work for entering numbers anyway (yes, that's a bug).

Share this post


Link to post
Share on other sites
  • 0
Remap your action groups to the numberpad keys, since they don't work for entering numbers anyway (yes, that's a bug).

I did that as a workaround, but it's still annoying. For instance, I can't prevent the del key from switching to docking mode without reassigning it.

Share this post


Link to post
Share on other sites
  • 0

@ChaosNicro:

I don't really see anything wrong with this picture, No swap being used, ~800MB free RAM & ~2.1GB cache, which should be freed as needed.

KSP is only using ~2GB at this point: 'VmRSS: 1966940 kB'

Mine, for reference (at the menu, more mods than you're running): 'VmRSS: 4825008 kB'

If the system is actually running out of RAM, what's using the rest of it? I find it hard to believe that that mod list would push KSP over ~4GB.

Do you have any other large processes running?

Do you have any ramdisks? i.e. /tmp mounted as tmpfs? tmpfs will use up to 50% of your physical RAM by default, if you have large files in /tmp it could be eating 4GB...

May be more illuminating to look at memory usage when it's actually swapping.

Firespitter hasn't caused any problems for me, despite the warning.

Edited by steve_v

Share this post


Link to post
Share on other sites
  • 0
@ChaosNicro:

I don't really see anything wrong with this picture, No swap being used, ~800MB free RAM & ~2.1GB cache, which should be freed as needed.

KSP is only using ~2GB at this point: 'VmRSS: 1966940 kB'

Mine, for reference (at the menu, more mods than you're running): 'VmRSS: 4825008 kB'

If the system is actually running out of RAM, what's using the rest of it? I find it hard to believe that that mod list would push KSP over ~4GB.

Do you have any other large processes running?

Do you have any ramdisks? i.e. /tmp mounted as tmpfs? tmpfs will use up to 50% of your physical RAM by default, if you have large files in /tmp it could be eating 4GB...

May be more illuminating to look at memory usage when it's actually swapping.

Firespitter hasn't caused any problems for me, despite the warning.

You're completely right, KSPs RAM usage is theoretically fine.

The mystery is that more than 2GB disappear upon startup. (not being used as cache or for KSP.).

The same amount is returned immediately after closing KSP and I have not the slightest of an idea what it is being used for.

According to my system I start out with pretty much 6GB (a tiny bit more) of free Ram before launching KSP. (with the script from OP)

I have a total of 8GB installed.

Share this post


Link to post
Share on other sites
  • 0
Hmm. @lodestar: You're not running FAR? That's a difference I can see right of the bat. Also, I recall that was an undocumented feature, but I don't offhand remember the workaround for it. I think it had to do with reassigning the function key since Linux OS keymapping to functions is obviously different from Windoze.

@gfurst: Your system is radically different from mine hardware wise. I'm off after the weekend so I'll have some time to really dig into this and test. I was a little off. My i5-2500K is OC'd to 4.4GHz. I Prime95-ed it for about 16 hours on mixed and it never missed a beat (though it did get hotter then I remember, with temps topping out around 69C), so I'm as convinced as I can be that the Proc/memory/IO/PS are stable.

I know this is somewhat thread derailing since it's clearly gone in another direction, but I wanted to update my progress.

This is SOLVED.

I disabled the Intel on-die video and also allowed Ubuntu to run its updates and was able to completely load my RSS modded KSP. Bolstered with this, I copied my gamedata and save game from the Windows partition over to another clean copy of KSP and it loaded up with zero issues. RAM usage is comparable to the Windows side at around 2.8GB at the VAB. I put Texture replacer in and it bumped up to 3.1GB with no issues, so I think I'm there.

With the open source AMD driver the performance was wildly varying. At the VAB it was very smooth, at the Mun base that has a heavy part count it went down to about 8 FPS. I installed the latest proprietary drivers (Catalyst 14.9) and that didn't improve the frame rate, though it did give me AA/AF so it looks better. I'm assuming at this point the deficient performance in comparison to Windows is due to the OpenGL rendering not being the best on the AMD card. Guess this will just force me to keep part counts low! :)

Anyway, after much experimentation I'm cooking with gas. Thanks guys for the help! I'll be around!

Share this post


Link to post
Share on other sites
  • 0

I wrote another shell script!

This one cleans up all but the latest version of ModuleManager (at least in the test cases I threw at it).

It assumes GNU coreutils + GNU parallel (because xargs is poorly documented on my system), and it deletes all but the most recent ModuleManager version, you have been warned!'

Usage: cd $KSPDIR && /path/to/fixmm.sh

#!/bin/bash
# fixmm.sh, released into the public domain by fm3d. Do whatever the heck you want with it.
# You don't even need to give me credit; in my (non-lawyer) opinion, it's not complex or creative enough to be copyrightable.
find . -type f -iname 'ModuleManager*.dll' -print0 \
| sort -z -r \
| tr '\0\n' '\n\0' \
| tail -n +2 \
| tr '\0\n' '\n\0' \
| parallel --no-notice -0 rm {}

Share this post


Link to post
Share on other sites
  • 0

Hi everyone

I decided to jump in feet first with manjaro (xfce edition) and everything seems to work fine with a stock KSP install. But when I start installing mods I come upon this problem: tlgmmND.jpg

That's the distant objects mod window there. If I install a bunch of mods, all mod windows look like that. I tried installing just FAR to see what would happen and that window displays just fine. So I installed distant object enhancement alongside FAR and now the DAE window doesnt work, while FAR still does. If I install more mods, all windows are broken. Strange.

Has anyone seen this before?

Edit: And what was voidi's script from that other thread supposed to do? I think it might be broken for .90 because the launcher it gives me with the pretty icon does nothing when I execute it.

Edit2: if this is something as simple as a missing fonts issue that would be really frustrating because I'm banging my head against a wall trying to install the fonts suggested in the other linux thread. Isn't there some package I can just install and be done with it? I basically need my hand held to do everyday things in linux :S

Edit3: Yes, it was the fonts...

Edited by pina_coladas

Share this post


Link to post
Share on other sites
  • 0

Hi.

I've spent the better part of the last week trying to play KSP on linux. I got a distro installed on a HDD partition (Manjaro 0.8.12, with Xfce 4.10). Got KSP installed, found out how to run it. su and sudo'd enough to drive a man mad. Figured out how to get the fonts to work. Though I could just take my save from the windows version and copy/paste it to the linux version. Nope. New game. Install the mods. Something's wrong. Re-install KSP. Re-re-install mods. And... it starts. And that's it. I don't even know what info to give anyone, or who to give it to. All I got is this screenshot:

Is this common? has this happened to someone else? How did you fix it?

I'm sorry I don't have specifics, but I don't even know where to start.

EDIT: On re-reading my post, I can imagine that the issue is not clear from this screenshot. None of the menu options are accessable, and are all dark colored.

Edited by Disco Pete

Share this post


Link to post
Share on other sites
  • 0

It looks like the window isn't getting focus. Tried alt-tabbing to it? Tried running it full-screen instead?

Afraid I've never had that issue; for me KSP just installed and ran without issue on Debian x64, initially using KDE but now in WindowMaker.

Share this post


Link to post
Share on other sites
  • 0

Got a crash that I believe is telling me i am using all 16gb of my ram which while I run a heavy mod setup is not possible I monitor my ram and it never exceeds 10gb here is my log if anyone can help. Let me know if you need more info.

Share this post


Link to post
Share on other sites
  • 0
Got a crash that I believe is telling me i am using all 16gb of my ram which while I run a heavy mod setup is not possible I monitor my ram and it never exceeds 10gb here is my log if anyone can help. Let me know if you need more info.

You ain't the only one, mate. At least me and 2 others have the same problem.

http://forum.kerbalspaceprogram.com/threads/109908-Frequent-crashes-during-modded-KSP-startup

Share this post


Link to post
Share on other sites
  • 0

Has anyone managed to run KSP over SSH? What command should I use?

If I try ./KSP.x86_64 I only get a brief flash of a black window which quickly disappears and nothing else happens.

The output in the console is

Set current directory to /home/shrx/.steam/steam/steamapps/common/Kerbal Space Program

Found path: /home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64

Mono path[0] = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed'

Mono path[1] = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono'

Mono config path = '/home/shrx/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc'

Share this post


Link to post
Share on other sites
  • 0

I really don't think that will work. While X forwarding over SSH does work, I don't think it's at all made to work with 3D acceleration.

Share this post


Link to post
Share on other sites
  • 0
This rig is a couple of years old and has been used almost exclusively as a platform for iRacing, though I have appropriated it for other tasks (like for instance, playing KSC!).

Anyway, Specifics if it helps are:

MB: Gigabyte GA-Z77-D3H

Proc: Intel i5-2500K Sandy Bridge (3.3GHz default, overclocked to 3.8GHz), cooled by a CORSAIR H60 water cooler

Memory: G.Skill Super Sniper blah blah blah DDR3 1866, 8GB (2x4GB)

Vid: XFX Radeon 7950 3GB

Associated case with enough airflow to start a CF56 turbofan engine. (CM Storm Enforcer, if you care)

As for proc temps, I have a windows app that monitors real time and trends (with alarm since I'm watercooling and if that turds itself things get real hot, real fast). Under load testing when new (to determine stable overclock), at present speed MAXIMUM ever attained temperature on any core was 49C. Under typical heavy use (running iRacing and associated ancillary programs, temps are around 41C. While playing KSC32 in Windows temps are about 38C. Idle baseline is between 26C and 30C once coolant is stabilized, depending on ambient temps.

In short, I seriously doubt I'm running into thermal related problems with Linux, though I haven't attempted to monitor temps within that OS. The fact that the game freezes at effectively the same place also makes me think this isn't a processor related issue. My general experience is with overclocked systems failures are a bit more "random" due to instability. There might be some credence to a memory issue, though again I've never had an issue in Windows and I would think if I had flaky memory it would have at some point started freaking out once I filled up the registers doing things other then KSP, regardless of platform. Also, using HTOP to monitor resources, I see that when KSP freezes it's at about 3.3GB of memory usage. Also, worth noting that it seems it's locking Unity, not Linux. Previously I had mentioned that I tried (and failed due to my stupidity) to SSH into the system from another computer, and it responded to me (told me to get bent, but it's a response) and it responded to pings, which tells me the OS is alive.

Just brainstorming, here are some things I am guessing about having potential issues. Please feel free to correct me, educate me and otherwise point me and punt me in directions you feel might be useful. Hell, if you're particularly masochistic, let me know if you want to shell into the damn thing and take a look see under the hood! Anyway, here goes.

The 7950 is feeding 3 screens. All three screens are identical. Two are being fed by the display ports via Startech MDP2DVIS display port to DVI active adapters. The third is connected directly via the DVI port on card. There is a 4th screen that is connected via the mainboard DVI adapter served by the Intel video adapter that is on the die of the i5 processor. I have DISABLED this screen in Ubuntu as it was causing all sorts of display issues. I have NOT disabled this adapter in BIOS (since Windows is using it, I don't want to have to go back and forth into BIOS to turn it on and off). I have not modified or changed the default video driver that Ubuntu installed. At present, Unity seems very happy serving these three screens and is having no apparent issues. When I ran stock KSP (In a window, not full screen. I've never run KSP full screen) I had no complaints about performance or smoothness. Is it conceivable that even though I have Linux ignoring the 4th screen on the Intel adapter that it is still somehow effecting the system?

In the realm of trying to do things that won't require me materially altering the system, I'll test the memory and back the clock down to stock speeds, just to eliminate those things from the equation. After that, I was toying with loading up xfce to see if maybe it's Unity puking on this...

If you have any other things you want me to try, I'm totally game. All I ask is that you explain what you're doing. I'm here to learn above all else, and trying to get this to work is an excellent opportunity to gain understanding!

And, thank you all! I'm amazed how much I've forgotten!

Seeing as you have the exact same AMD card as me, can you give me insight of KSP's FPS performance on your system? I have an identitical system to you, except using Ubuntu and have a Core i7 2700k, and I noticed that my performance is significantly lower than even Opengl on Windows.

Share this post


Link to post
Share on other sites
  • 0

I'd just like to comment, if I may, that Linux can be - has been on my PC - a case of 'install KSP and start playing'. The only thing I had to do was to turn the graphics quality ad aerodynamic effects down, and that only because my PC is an old second hand Dell box. And trust me - KSP still look splenty good enough even with the graphics texture settings on 1/4.

Also, I'm happy to report that CKAN on Linux is working perfectly, and makes mods that support CKAN an utter doddle to install.

My advice to any linux newbies would be to keep it simple - stick to one of the newbie-friendly distros the OP mentions, install KSP direct, rather than via Steam*, and if things run slow, crank the graphics settings down until things run OK. If you can't get KSP running acceptably well even on low graphics settings and you;re sure that your hardware is up to the job, that's the time to start looking into why and asking here for help. It used to be teh case that most distros would pretty much gurantee to get you a working desktop straight from install, but working 3D graphics might be another matter. These days, though, the newbie-friendly distros seem to do a grand job of auto-detecting graphcs cards (always remembering that bleeding-edge hardware may be unknown to the software) and installing the necessary 3D gubbins as well. You might be able to get better performance out of your kit if you;re prepared to do the research, ask in forums and tweak stuff; but that;s true no matter what operating system you;re using. It certaily isn't the case that using Linux requires that kind of fiddling, any more. (In fact, I left Windows for Linux at home simply because I found Linux gave me far fewer problems, and 'just worked' more often. Your mileage may vary, etc.)

*I've nothing against Steam, it does a good job of what it's for, but because it stuffs everything into its own sub-directory, it just means that if you like messing with mods, you've got even more folders and sub-folders to have to trawl through to get to where you want to be. And, Steam does add another layer of stuff that isn't strictly needed to play KSP. More stuff = more potential for things to go wrong. That said, I didn;t experience any problems during the period I was running KSP on Steam - I stopped playing it via Steam simply because of the added mucking about when adding/removing mods.

Share this post


Link to post
Share on other sites
  • 0

@esme:

I totally agree with every one of your words and am glad that someone points it out !

Running over smallband network (ssh), running in vm, installing arbitrary and undocumentet third party libraries (steam), overclocking the hardware out ... sure there'll be problems, thats no miracle. In many cases that's using the wrong tools for the job, expecting the super-cow.

I believe that many problems could simply be solved by installing the os (i'd recommend ubuntu or derivatives or plain debian for the connaisseurs) and setting up the correct graphics-driver and nothing else that's not fully documentet or can have unforeseen sideeffects.

Another thing probably is that that the 64bit version just runs under linux and the linux version has less memory problems (is that so ?) which could seduce people to play ksp in linux but on the other hand want to keep the windows environment. But you can't have everything. If you like the 64bit merits (which are probably smaller than one might think) get a second computer or install a dual boot system, which is pretty straightforward, just click "yes" when asked ... linux is not a beast (less then i'l better shut up :-))

Please let me add that the open source graphics driver for nvidia cards (called nouveau) isn't as sophisticated as the proprietary nvidia driver, downloaded from the nvidia site. I've heard (but no experience) that for the amd driver the same is applicable.

Risking all my rep

K

btw: i play ksp on a notebook with i3, intel hd4400 and 4gb ram. Modded with b9, kw, and a few others. Runs nicely on low graphics settings even for a station with several 100 parts (that i built on another pc i must admit, wouldn't want to dock with that station on this one ....)

Edited by kemde

Share this post


Link to post
Share on other sites
  • 0

If you bought KSP through Steam, you're quite welcome to copy the entire KSP folder out of Steam and somewhere else and run it directly. Just poke around in the Steam folder, usually under /home/yourusername/.steam , to find it. (A file or folder name starting with a dot is how Linux does hidden files, so you may need to enable showing them.)

As for graphics drivers, if you have an nVidia card you'll almost surely want the proprietary nVidia drivers, if you have an AMD card you might want the proprietary AMD drivers. In general to install programs on Linux you should get out of the Windows habit of downloading installers from websites, and use the package manager or software centre which is similar to the app stores on mobiles.

Share this post


Link to post
Share on other sites
  • 0

Uh huh, and what is one supposed to do with that scant information?

I assume the 'scrips' you refer to is in fact the bash script in the OP? Works fine for me.

Does it produce anything on STDOUT?

Do you have taskset? 'which taskset' in a terminal will tell you.

- - - Updated - - -

Has anyone managed to run KSP over SSH? What command should I use?

If I try ./KSP.x86_64 I only get a brief flash of a black window which quickly disappears and nothing else happens.

The output in the console is

KSP needs OpenGL with shaders, which you won't get with remote X, over ssh or otherwise.

KSP will run with VirtualGL, but bandwidth constraints and the performance of your graphical transport will limit framerate. VGL transport or TurboVNC over a LAN is your best bet in that regard, probably best to exclude the SSH overhead if you can too.

No promises on playability, but it does run.

isn't KSP, but it's a reasonable comparison of X11/GLX vs VGL. Performance can be surprisingly good :)

KSP even runs with VGL + X2go, but the only testing I have done is over a rather pathetic ADSL connection, so no comment on the performance of this configuration.

Edited by steve_v

Share this post


Link to post
Share on other sites
  • 0

Hey guys, can you help me out figuring this [thread=122529]weird graphical corruption issue[/thread]?

Share this post


Link to post
Share on other sites
  • 0

I tried installing the re-entry bug workaround from the unmodded thread, but it still won't work.

Share this post


Link to post
Share on other sites
  • 0
I tried installing the re-entry bug workaround from the unmodded thread, but it still won't work.
More information required.

Share this post


Link to post
Share on other sites
  • 0

A couple of notes for things I have discovered recently.

Having hard lockups, especially when trying to use Environmental Visual Enhancements? Running on an AMD graphics card? Try loading up the BoulderCo/Clouds PNG files in an image viewer. If you get a lock up on one or more of them, you've hit the same AMD Kernel driver bug I did. The only solution I could find was to replace my graphics with NVidia, since both the Catalyst and open source drivers use it. Now I have no issues. Fixed up Cities: Skyline, too.

Trying to run a heavily modded KSP under Steam, and find that you can load KSP fine if you navigate to the folder and run KSP.x86_64, but you run out of memory or fail to load when launching from Steam? Steam launches the 32 bit KSP.x86 instead of KSP.x86_64. Rename it and make a link KSP.x86 -> KSP.x86_64, and you'll get the 64 bit version we all love so much.

Share this post


Link to post
Share on other sites
  • 0
On October 30, 2015 at 10:05 AM, politas said:

A couple of notes for things I have discovered recently.

Having hard lockups, especially when trying to use Environmental Visual Enhancements? Running on an AMD graphics card? Try loading up the BoulderCo/Clouds PNG files in an image viewer. If you get a lock up on one or more of them, you've hit the same AMD Kernel driver bug I did. The only solution I could find was to replace my graphics with NVidia, since both the Catalyst and open source drivers use it. Now I have no issues. Fixed up Cities: Skyline, too.

Trying to run a heavily modded KSP under Steam, and find that you can load KSP fine if you navigate to the folder and run KSP.x86_64, but you run out of memory or fail to load when launching from Steam? Steam launches the 32 bit KSP.x86 instead of KSP.x86_64. Rename it and make a link KSP.x86 -> KSP.x86_64, and you'll get the 64 bit version we all love so much.

I just found the following fixes my EVE problems with lockups:

The following option (when running from a command line) fixes this:

export __GL_THREADED_OPTIMIZATIONS=1

I'll be posting a complete script for starting KSP on Linux soon, watch this thread for details

Edited by linuxgurugamer

Share this post


Link to post
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.