gsarducci

It seems Ubuntu is more widely adopted and there is much more guidance on how to resolve common issues, so for a hack like me who is trying to re-learn the nuances of this OS it's probably a good place to experience the least desire to see how a CPU fares against a Glock. I will make this work. Oh yes, I WILL make this work!

I certainly meant no disrespect at all. Text lacking inflection for the fail. I apologize. I am very grateful for all of your help you guys are giving me. after 20 years I have apparently completely lost my Linux mojo, but it's slowly coming back. Once I figured out how to parse the ldd output it made sense. The next problem was trying to get the dependency seen by the program. Before all that happened though, I let Manjaro do its updates (there were several hundred it kept hounding me about and I figured perhaps that might solve some problems). It proceeded to completely nuke itself, so I finally got fed up and reinstalled Mint. Trying to install the proprietary drivers using the instructions provided (essentially mkconfig and it compiles deb files, yadda yadda) resulted in bricking THAT installation, so now I've moved onto Ubuntu 14.04. Had to head back to work so didn't get to try to blow that up with new vid drivers, so I'll proceed in doing that tomorrow, at which point I will concede defeat and just deal with the limitations of the 32 bit Winblows app until such time as Unity gets its crap together with the 64 bit stuff.... Now I remember why I got out of the IT business. I have a 6 year old boy. My frustration reservoir meter is already solidly in the yellow.

So not sure what the heck is going sideways here... Ran from terminal. Got this: [guido@guidosw KSP_linux]$ ./KSP.x86_64 Set current directory to /home/guido/KSP_linux Found path: /home/guido/KSP_linux/KSP.x86_64 Mono path[0] = '/home/guido/KSP_linux/KSP_Data/Managed' Mono path[1] = '/home/guido/KSP_linux/KSP_Data/Mono' Mono config path = '/home/guido/KSP_linux/KSP_Data/Mono/etc' Aborted (core dumped) Ran ldd and got this: [guido@guidosw KSP_linux]$ ldd ./K*4 linux-vdso.so.1 (0x00007ffff73fe000) libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f1ef718a000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f1ef6f6e000) librt.so.1 => /usr/lib/librt.so.1 (0x00007f1ef6d66000) libGLU.so.1 => /usr/lib/libGLU.so.1 (0x00007f1ef6ae5000) libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f1ef684b000) libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f1ef6509000) libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f1ef62f7000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f1ef60ec000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f1ef5ee2000) libm.so.6 => /usr/lib/libm.so.6 (0x00007f1ef5bdd000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f1ef59c7000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f1ef5624000) /lib64/ld-linux-x86-64.so.2 (0x00007f1ef738e000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f1ef5315000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f1ef50eb000) libglapi.so.0 => /usr/lib/libglapi.so.0 (0x00007f1ef4ec1000) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f1ef4cbe000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f1ef4ab8000) libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0x00007f1ef48b6000) libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0x00007f1ef469c000) libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0x00007f1ef4497000) libxcb-dri3.so.0 => /usr/lib/libxcb-dri3.so.0 (0x00007f1ef4294000) libxcb-present.so.0 => /usr/lib/libxcb-present.so.0 (0x00007f1ef4091000) libxcb-randr.so.0 => /usr/lib/libxcb-randr.so.0 (0x00007f1ef3e83000) libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0x00007f1ef3c7b000) libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f1ef3a71000) libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0x00007f1ef386d000) libxcb-sync.so.1 => /usr/lib/libxcb-sync.so.1 (0x00007f1ef3666000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f1ef3444000) libxshmfence.so.1 => /usr/lib/libxshmfence.so.1 (0x00007f1ef3241000) libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x00007f1ef303b000) libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f1ef2e2e000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f1ef2c24000) libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f1ef2a20000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f1ef281a000) Not sure what any of it means but nothing show "not found" which is good. However, on the 32 bit side there are some missing: [guido@guidosw KSP_linux]$ ldd K*6 linux-gate.so.1 (0xf77a1000) libdl.so.2 => /usr/lib32/libdl.so.2 (0xf7751000) libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf7735000) librt.so.1 => /usr/lib32/librt.so.1 (0xf772c000) libGLU.so.1 => /usr/lib32/libGLU.so.1 (0xf76a6000) libGL.so.1 => /usr/lib32/libGL.so.1 (0xf7602000) libX11.so.6 => /usr/lib32/libX11.so.6 (0xf74cb000) libXext.so.6 => /usr/lib32/libXext.so.6 (0xf74b6000) libXcursor.so.1 => not found libXrandr.so.2 => not found libm.so.6 => /usr/lib32/libm.so.6 (0xf7468000) libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf744d000) libc.so.6 => /usr/lib32/libc.so.6 (0xf7295000) /lib/ld-linux.so.2 (0xf7780000) libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf719f000) libatiuki.so.1 => /usr/lib32/libatiuki.so.1 (0xf7183000) libxcb.so.1 => /usr/lib32/libxcb.so.1 (0xf715c000) libXau.so.6 => /usr/lib32/libXau.so.6 (0xf7158000) libXdmcp.so.6 => /usr/lib32/libXdmcp.so.6 (0xf7151000) So, I seem to be missing something, like for example: libXcursor.so.1 => not found So I do looking for it and lo and behold: [guido@guidosw lib]$ ls libxcursor* libXcursor.so@ libXcursor.so.1@ libXcursor.so.1.0.2* Dafook? So I have it, but it can't find it? My head assplode. This really shouldn't be this hard. Oh, I tried the whole "Not Found" trick. Amusingly: [guido@guidosw KSP_linux]$ ldd K*4 | "Not found" bash: Not found: command not found I think I've been punked.

CPU paste will become brittle over time, but generally unless something else happens it should last the life of the fan. Which brings me to "the life of the fan". How old is that CPU fan? Don't assume that when you peer into the chassis and see that fan turning that it will continue to do so. I've seen fans do funky things when they get old (had one actually start running in reverse... No idea how that was even possible but there it was)... Overheat problems tend to lead to more overheat problems and the damage is cumulative. By the time you trip most motherboard thermal safety protocols your processor is WELL into potential meltdown temps.. CPUs change temperatures almost instantaneously, so spot checking the core after rebooting won't tell you anything useful. You really need to have something that watches the trend and throws an audible alarm when you hit a certain threshold. Old school techniques to try: Reseat the RAM and cards. Blow out the system with compressed air. Ensure your power supply fan is still working...

I was running the latest flavor of Mint before this. KSP was working sort of, but would grenade when I started adding mods. I also couldn't get the video driver to play nice with multi-screen. Instead of trying to sort out what was going pear shaped there I saw that the OP had great success with Manjaro so I went ahead and slapped that on there (I'm only messing with Linux for experimenting with KSP, so reinstalls and the such aren't showstoppers). I'm sure it's something stupid that I'm overlooking so thank you ahead of time for occasionally pointing out the obvious.

Indeed. I had to run out the door for work so I will do this tonight or tomorrow morning. @Gfurst Never assume anything with me! Last time I did battle with Linux a GUI was nothing but an amusement, and a FUNCTIONAL GUI was the punchline to a joke! To say I'm rusty is an insult to rust.

So here's one for ya. I went ahead and installed Manjaro 0.8.10, got the proprietary drivers for my Radeon 7950 working with multi screen (and re-learned a lot of how to deal with CLI again in the process), exracted KSP into my /home/user directory (leaving it bone stock at the moment), created the ksp.sh shell file as per the OP (for quad core procs, I have an i5), made it executable, executed it and..... nothing. Literally. No errors, no "hey, get bent we aren't running that" ..... boxes. a little blip of R/W from the HD and the quiet whirring of my chassis fans. Task Manager confirms that there's nothing KSP related running. Undeterred, I tried to execute KSP.x86_64 directly and still got nothing. Didn't even puke out a logfile. Just for turds and giggles I tried running both as root. Nada. So, since Linux isn't even throwing me a bone here as to where to look to see where it's gone pear shaped, I got no ideas how to even START to troubleshoot this one... After spending several hours simply relearning how to crawl around in Linux, this wasn't quite the carrot I was hoping for in the end. Nice reminder of the old axiom my buddy and I had stuck to the top of our old RedHat webserver several decades ago: "It's not that Linux isn't user friendly, it's just very particular about who its friends are". Help me, Obi-Wan.

You're in better shape then me. All links on the OP are porked, so far as I can tell. Lead to an empty page. Sad panda.

I had a ship and a rover eaten by the Hell Kracken when I linked the two with KAS. Bill walked up, attached the pipe and suddenly there was nothing left but a small puff of dust! It was actually quite amusing. What wasn't was when I bracketed over to the wayward ship and it immediately killed Bill, who was just sitting on the surface of Minmus minding his own business... alt+f4, rinse, repeat. c'est la vie.

Update: Rolled it back to 0.8.2 and everything started working again. No other changes.

Definitely something broke. I had an array of existing apparatus that was mining K just fine. Update to 0.8.3 = no workie no more.