Jump to content

ss32

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by ss32

  1. I think I'm good now, finally! Updated to 17, installed the newest drivers...again, and updated the kernel to 3.15. The graphics aren't as smooth as running in windows but I'll take it.
  2. Yeah I knew about the bash vulnerability. That "exploit" has been around for 22 years but I guess people just now figured out how to use it. Anyway, I guess I'll update to 17.....
  3. Reinstalled the drivers, no change. It froze in the rocket bay this time, didn't even make it to launch. http://pastebin.com/943dy1ei edit: I see errors about the graphics shader being in fallback mode.
  4. Well, I installed the newest driver, patched the executable, ran it using the script, and it still froze just like before. Log - http://pastebin.com/ZTqfumtQ Hmmm this is weird though. $ dmesg | grep fglrx | grep module [ 4.191446] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 4.198010] <6>[fglrx] module loaded -[B] fglrx 14.10.2 [Apr 17 2014[/B]] with 1 minors That should be updated shouldn't it?
  5. The old ones weren't that easy otherwise I wouldn't be complaining. For one, there wasn't a build for the most recent Debian/Mint/Ubuntu build at the time so I had to hack together an older build with a patch and then hope that x-server would start at boot. If not, edit grub with a switch to use a fallback x-server, delete the config, start over. Rinse and repeat until somehow it worked. I think that was version 13.XX. And what worked in Ubuntu for some reason didn't cooperate with Lubuntu, and running Lubuntu got me ~8% higher hash rates when mining, so it was kind of necessary. I'm not mining any more....
  6. When I bought the cards for mining it was such a PITA to get the drivers working properly that I haven't touched the configuration for probably 8 months. Do I need to uninstall the current one or will the new one just patch over? Thanks in advance for your help.
  7. Ok now I'm confused. 14.9 is their new beta but it looks like I'm running 14.10? $ dmesg | grep fglrx | grep module [ 4.146634] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 4.152738] <6>[fglrx] module loaded - fglrx 14.10.2 [Apr 17 2014] with 1 minors $ fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon R9 200 Series OpenGL version string: 4.4.12874 Compatibility Profile Context 14.10.1006
  8. Woah, thanks for all that. I'll give it a shot and get back to you. At least I know now that an AMD card can play with KSP without any issues. It didn't return anything, I have all the libraries.
  9. I'm having trouble with the 64-bit build freezing on me. I have an AMD card but aliasing is turned off and AMD mode on. I've tried running the 32-bit but it won't even run. A window opens then immediately closes; there isn't even a log file for it. This is on a freshly downloaded copy of 24.2 for both 64 & 32 bit. I've had the freezing trouble with earlier versions as well. Terminal output when trying to run 32-bit (the same thing happens whether I run the launcher or the game itself) $ ./Launcher.x86 Set current directory to /home/user/Downloads/KSP_linux Found path: /home/user/Downloads/KSP_linux/Launcher.x86 Mono path[0] = '/home/user/Downloads/KSP_linux/Launcher_Data/Managed' Mono path[1] = '/home/user/Downloads/KSP_linux/Launcher_Data/Mono' Mono config path = '/home/user/Downloads/KSP_linux/Launcher_Data/Mono/etc' And the log from the 64-bit run is here - http://pastebin.com/7dmr95w5 . It's fine until I try to launch for the most part. It froze once while building a rocket and another time I was able to launch but it froze ~20 seconds in. The computer is completely unresponsive and I have to remote in and reboot to get it back
  10. I'm running into an odd problem, it looks like it's something to do with another mod maybe. All of the kethane parts are there, but when I launch they won't scan. Also, when I first start the game I don't get the hex overlay on Kerbin. But if I install the kethane mod on a clean install of KSP it works fine.
×
×
  • Create New...