Jump to content

The Linux compatibility thread!


Recommended Posts

http://bugs.kerbalspaceprogram.com/issues/684 [0.20] <- this has been closed on me

KasperVld says, "ArchLinux is not supported by Unity 4 and by extension also not supported by KSP."

http://blogs.unity3d.com/2012/11/22/linux-publishing-in-unity-4-0/

Unity Technologies says, "We currently only offer official support for Ubuntu Linux, version 10.10 or later. However, users are happily running games on a very wide range of linux distributions, including Arch Linux, Gentoo, Debian, and others."

While these popular Linux distributions are essentially the same and very easily, universally supported, Squad has chosen to take advantage of the support Unity is offering. I don't blame them. They're a small team and probably don't have the time. I recommend keeping non-Ubuntu bug reports out of their tracker and instead keep them on mailing lists, forums (here), and irc. The Linux support community is a very different beast than the corporate support community.

While I would not push Ubuntu on you, one option you have is to examine how Ubuntu does it (graphics libraries/drivers) and reconfigure your Arch to match. A chroot to Ubuntu as a testing environment would show you exactly what Ubuntu would do with your hardware -- and then if it works you can blame it on the unsupported differences in your distribution and make changes to suit Unity4. After all, Arch is very flexible and configurable.

Link to comment
Share on other sites

Yes. Using the number pad. + and - zooms in and out. You can also disable NumLock and use the number pad arrows for camera controls. I think 9 and 3 pan up and down in the VAB.

Panning can also be done using Pg Up and Pg Down

Link to comment
Share on other sites

Not sure if it is appropriate place to post bug reports, but I couldn't find better one, so:

KSP-0.20 crashes after I start new game (enter name, choose flag, pres "Start"). After few moments game exits and I see the following in the console, that started the game:

Set current directory to /mnt/delta/Games/KSP_linux

Found path: /mnt/delta/Games/KSP_linux/KSP.x86_64

Mono path[0] = '/mnt/delta/Games/KSP_linux/KSP_Data/Managed'

Mono path[1] = '/mnt/delta/Games/KSP_linux/KSP_Data/Mono'

Mono config path = '/mnt/delta/Games/KSP_linux/KSP_Data/Mono/etc'

Aborted (core dumped)

I have Mobility Radeon HD 5450 with OSS drivers. OS is Ubuntu 13.04. KSP install is a fresh one (deleted old KSP directory and unzipped 0.20 distribution). KSP-0.19.1 worked fine.

Can I help debugging this issue?

Hi kedder, I originally had this problem (or a similar one) too, and fixed it by installing Mono.

You can search 'mono-complete' in the Ubuntu software center, or follow instructions on their website http://mono-project.com/

Hope that fixes it!

dodrian

Link to comment
Share on other sites

KasperVld says, "ArchLinux is not supported by Unity 4 and by extension also not supported by KSP."

http://blogs.unity3d.com/2012/11/22/linux-publishing-in-unity-4-0/

Unity Technologies says, "We currently only offer official support for Ubuntu Linux, version 10.10 or later. However, users are happily running games on a very wide range of linux distributions, including Arch Linux, Gentoo, Debian, and others."

While these popular Linux distributions are essentially the same and very easily, universally supported, Squad has chosen to take advantage of the support Unity is offering. I don't blame them. They're a small team and probably don't have the time. I recommend keeping non-Ubuntu bug reports out of their tracker and instead keep them on mailing lists, forums (here), and irc. The Linux support community is a very different beast than the corporate support community.

While I would not push Ubuntu on you, one option you have is to examine how Ubuntu does it (graphics libraries/drivers) and reconfigure your Arch to match. A chroot to Ubuntu as a testing environment would show you exactly what Ubuntu would do with your hardware -- and then if it works you can blame it on the unsupported differences in your distribution and make changes to suit Unity4. After all, Arch is very flexible and configurable.

yes I understand that, and my response was indeed a bit harsh if one could say that. In the end I just wanted to gather information regarding this segfault, hence the link to the mesa bug. I'm not in touch with gdb or other debugging tools to do bughunts on my own - my guess was that ubuntu had a rather older mesa or other lib and this segfault might reoccour on some 'offically supported' OS. So I figured why not look into it now, instead of waiting until it effects a lot of people.

I don't honestly know how to 'tweak' archlinux to represent ubuntu* except from downgrading which is against how archlinux works. I can only say that arch is by design very close to upstream and that I expect that such bugs on arch (or gentoo in this context) will occour on other distros with slower update cycle unless fixed somewhere along the way.

*actually I will research this on the weekend

Link to comment
Share on other sites

Is there a list somewhere of the actual names used by the config file to map keys and buttons? I couldn't find any reference to mouse buttons, right-click, left-click, etc etc. The only section with Mouse involved is the AXIS_MOUSEWHEEL section. Is there a way to add in our own mouse button names, and scroll_up, scroll_down etc etc?

For instance, I know that my mouse (Logitech m570) uses the names 'button 5' and 'button 4' for scroll up and scroll down. Is there a way to add those into the settings.cfg file?

I've tried a couple variations of 'Scroll_up = Button4' and 'Scroll_up = Button 4' but they just get wiped from the settings file when the game starts, so I'm assuming I'm not using the correct format.

Link to comment
Share on other sites

I am running Linux Mint 14 (Nadia), using the Mate Desktop. I know that KSP is not officially supported on my platform, but since Mint 14 is basically Ubuntu, it should be able to make it work. Version 0.19.1 ran fine (after tweaking the start command to LC_ALL=C ./KSP.x86 or LC_ALL=C ./KSP.x86_64)

KSP starts up fine and I can get through the menu to create a new game. After naming it and selecting a flag it starts to show the nice new loading animation and then just closes. It also closes in the same way when entering the settings menu.

I tried running both, the 32 and 64 bit version, both with the LC_ALL=C... commands and without (only ./KSP.x86).

The result is the same for all my tries.

The console output is the same for all as well:


Set current directory to /home/user/bin/KSP_linux-0.20.0
Found path: /home/user/bin/KSP_linux-0.20.0/KSP.x86
Mono path[0] = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Managed'
Mono path[1] = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Mono'
Mono config path = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Mono/etc'
/dev/input/js0: driver version: 2.1.0 (20100)
/dev/input/js0: fd 3, buttons 12, axes 6, name Logitech Logitech Dual Action
/dev/input/js0: axis 0: raw 0, mapped 0.000000
/dev/input/js0: axis 1: raw 337, mapped 0.000000
/dev/input/js0: axis 2: raw 337, mapped 0.000000
/dev/input/js0: axis 3: raw 337, mapped 0.000000
/dev/input/js0: axis 4: raw 0, mapped 0.000000
/dev/input/js0: axis 5: raw 0, mapped 0.000000
Aborted

I have an Radeon 4870 HD graphics card and as I said before, 0.19.1 ran fine in both, 32 and 54 bit flavors.

Does anyone have an idea how to solve this?

Link to comment
Share on other sites

Sorry for pulling out old things, but I had to do this.

and neither did running as root.

DO NOT EVER RUN GAMES AS ROOT!!!

Edited by etam
Link to comment
Share on other sites

I am running Linux Mint 14 (Nadia), using the Mate Desktop. I know that KSP is not officially supported on my platform, but since Mint 14 is basically Ubuntu, it should be able to make it work. Version 0.19.1 ran fine (after tweaking the start command to LC_ALL=C ./KSP.x86 or LC_ALL=C ./KSP.x86_64)

KSP starts up fine and I can get through the menu to create a new game. After naming it and selecting a flag it starts to show the nice new loading animation and then just closes. It also closes in the same way when entering the settings menu.

I tried running both, the 32 and 64 bit version, both with the LC_ALL=C... commands and without (only ./KSP.x86).

The result is the same for all my tries.

The console output is the same for all as well:


Set current directory to /home/user/bin/KSP_linux-0.20.0
Found path: /home/user/bin/KSP_linux-0.20.0/KSP.x86
Mono path[0] = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Managed'
Mono path[1] = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Mono'
Mono config path = '/home/user/bin/KSP_linux-0.20.0/KSP_Data/Mono/etc'
/dev/input/js0: driver version: 2.1.0 (20100)
/dev/input/js0: fd 3, buttons 12, axes 6, name Logitech Logitech Dual Action
/dev/input/js0: axis 0: raw 0, mapped 0.000000
/dev/input/js0: axis 1: raw 337, mapped 0.000000
/dev/input/js0: axis 2: raw 337, mapped 0.000000
/dev/input/js0: axis 3: raw 337, mapped 0.000000
/dev/input/js0: axis 4: raw 0, mapped 0.000000
/dev/input/js0: axis 5: raw 0, mapped 0.000000
Aborted

I have an Radeon 4870 HD graphics card and as I said before, 0.19.1 ran fine in both, 32 and 54 bit flavors.

Does anyone have an idea how to solve this?

i think this is a segfault, as described in http://forum.kerbalspaceprogram.com/showthread.php/24529-The-Linux-compatibility-thread%21?p=381728&viewfull=1#post381728 I postet a bugreport but they do not support any linux other than ubuntu.

There is hope though as this might be an mesa upstream bug.

you can run 'gdb ./KSP.x86_64' and then '(gdb) run' which will print something about segfault - as far as I know you cannot do anything about this until the bug is found and fixed

Edited by birdspider
Link to comment
Share on other sites

Sorry for pulling out old things, but I had to do this.

DO NOT EVER RUN GAMES AS ROOT!!!

I get that its a bad practice and not advisable under most circumstances, but sometimes it can help debug, and player.log specifically mentioned possibly not having permission to do something. I'm at a different pc now so cant check what, but running as root did remove that particular error message, although not the general problem. A reply to a later post with the same problem points to segfaults as the probable cause =/

Link to comment
Share on other sites

etam, eddbc, It's safe to run KSP as root, I've done it myself a few times as it can generate a more thorough player.log, there's no other reason to run it as root though.

dodrian, I'd try the most up-to-date proprietary drivers myself, the x-swat repo has some later drivers.

kedder, I'd try the proprietary driver, as I have an AMD 7660D and it has trouble with KSP and the OS driver.

tacodrake95, I'll see if I can get KSP 0.20 working in Wine and let you know how to do it.

dr.phees, try deleting the settings.cfg, as it looks like it's breaking just after the joystick commands load, maybe the format has changed?

I have no idea on the segfaults yet, we need to figure out why it's happening, it's not happened to me yet though.

triffid_hunter, did you delete the settings.cfg and run with LC_ALL=C ./KSP.x86 ?

Link to comment
Share on other sites

dr.phees, try deleting the settings.cfg, as it looks like it's breaking just after the joystick commands load, maybe the format has changed?

Sadly this did not solve it. I did install in a fresh directory anyway.

Link to comment
Share on other sites

tacodrake95, I'll see if I can get KSP 0.20 working in Wine and let you know how to do it.

Thank you. It keeps crashing and saying to contact the maker of the game with the error.

EDIT: Here is a link to a .zip of the error folder. Hope this helps. https://www.dropbox.com/s/icp9omzpmjl8byk/2013-05-24_171500.zip

Edited by tacodrake95
Link to comment
Share on other sites

Hi Guys.

I have the problem that KSP ist completly unplayable for me under Linux. I have the follwing issues:

- I can't plug Rocketparts together in the editor

- Loaded Ships are invisible

- When I start a mission it only show the space. I don't start at Kerbin with my Rocket.

I made a video of it:

http://www.youtube.com/watch?v=eV0zgAllSAU

I'm using the latest version (v0.20) and have no mods installed. The game is fresh installed by Steam.

Under Windows 7 (on the same machine) it works perfectly :D

My system:

- Linux Mint 14

- 64 bit

- Steam for Linux

- Intel Core i5 CPU 760 @ 2.80GHz × 4

- GeForce GTX 560 Ti/PCIe/SSE2

- 8 GB Memory

Link to comment
Share on other sites

KSP seems to be working in Wine still, I am using PlayOnLinux and the latest Wine version, 1.5.28

Your logs show a memory access issue, this is rare on Linux so is hard to track down, but might be related to your Gfx card, as KSP on Linux has issues with ATI cards especially ones from the 4000 series and older.

I suggest you try POL though, as it can set up a wineprefix for you which will rule out any winetricks stuff you might have installed and forgotten about.

Link to comment
Share on other sites

I suggest you try POL though, as it can set up a wineprefix for you which will rule out any winetricks stuff you might have installed and forgotten about.

Already tried POL and it gave me the same error. How do I actually set it up with POL?

Link to comment
Share on other sites

Does anyone know where they are with the scroll problem? Are they considering a small patch to fix this before next major release? It is so frustrating having this great game and having played it for so long, and suddenly I can't play it anymore...

Link to comment
Share on other sites

Already tried POL and it gave me the same error. How do I actually set it up with POL?

You need to make sure you are using the latest version of Wine, that's pretty much it as KSP does not need any winetricks stuff or twiddling to run in Wine.

If it's still failing to work then it's likely not Wine, your log shows that KSP isn't getting enough RAM or is just running out, as can be seen here:

Unknown caused an Access Violation (0xc0000005)

in module Unknown at 0023:7a4b32ec.

Error occurred at 2013-05-24_171508.

Z:\home\jake\Desktop\KSP_win\KSP.exe, run by jake.

48% memory in use.

0 MB physical memory [2810 MB free].

0 MB paging file [3335 MB free].

0 MB user address space [0 MB free].

Read from location 0000013c caused an access violation.

It's hard to tell what the cause is, you might just not have enough RAM, seeing as you have an old Gfx card then I'd guess you have a 1gig PC:

Renderer: ATI Radeon HD 3200 Graphics

I'd need the log from the hardinfo application to know more.

Does anyone know where they are with the scroll problem? Are they considering a small patch to fix this before next major release? It is so frustrating having this great game and having played it for so long, and suddenly I can't play it anymore...

Don't worry, I'm going to bug the devs to fix this bug as obviously something changed in the Linux build, and Skunky said in IRC that a 0.20.1 is planned.

Link to comment
Share on other sites

Getting accustomed to using the numpad to move the camera. It's a bit slow to zoom, but not bad. Is there a way to speed up camera movement? Perhaps via editing config files directly?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...