Linux - GamesThis forum is for all discussion relating to gaming in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm logged in as root so that I could install my software and scripts without haveing to type a password repeatedly.
once the game works I'm gona change the setup so that I can play it in a normal user account.
Other ideas:
-Is your loopback interface set up correctly? (that is, does ping localhost and ping 127.0.0.1 work)
-Try running program with strace and/or ltrace to see what happens before segfaults (also strace -e trace=file might be useful).
-Using fenris might also retrieve something out from the problem.
-Recompile the program with debugging information (-g) and run it under gdb to see where in the source crashes.
This is what I get for the loop back I'd say it works...
---------------------------------------------------------------------- PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.224 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.141 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.154 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.154 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.164 ms
64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.150 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.138 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=0.155 ms
64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=0.146 ms
64 bytes from 127.0.0.1: icmp_seq=10 ttl=64 time=0.164 ms
64 bytes from 127.0.0.1: icmp_seq=11 ttl=64 time=0.148 ms
64 bytes from 127.0.0.1: icmp_seq=12 ttl=64 time=0.143 ms
64 bytes from 127.0.0.1: icmp_seq=13 ttl=64 time=0.153 ms
64 bytes from 127.0.0.1: icmp_seq=14 ttl=64 time=0.133 ms
64 bytes from 127.0.0.1: icmp_seq=15 ttl=64 time=0.164 ms
64 bytes from 127.0.0.1: icmp_seq=16 ttl=64 time=0.153 ms
64 bytes from 127.0.0.1: icmp_seq=17 ttl=64 time=0.138 ms
64 bytes from 127.0.0.1: icmp_seq=18 ttl=64 time=0.161 ms
64 bytes from 127.0.0.1: icmp_seq=19 ttl=64 time=0.148 ms
64 bytes from 127.0.0.1: icmp_seq=20 ttl=64 time=0.160 ms
64 bytes from 127.0.0.1: icmp_seq=21 ttl=64 time=0.159 ms
64 bytes from 127.0.0.1: icmp_seq=22 ttl=64 time=0.142 ms
64 bytes from 127.0.0.1: icmp_seq=23 ttl=64 time=0.143 ms
64 bytes from 127.0.0.1: icmp_seq=24 ttl=64 time=0.164 ms
64 bytes from 127.0.0.1: icmp_seq=25 ttl=64 time=0.138 ms
64 bytes from 127.0.0.1: icmp_seq=26 ttl=64 time=0.178 ms
64 bytes from 127.0.0.1: icmp_seq=27 ttl=64 time=0.143 ms
64 bytes from 127.0.0.1: icmp_seq=28 ttl=64 time=0.145 ms
Well, that just crashes after reading some shared objects. There seems to be nothing wrong with the kernel interaction. ltrace might reveal something; it traces through the interaction with dynamic library calls.
I would compile the sources with -g to see what is actually wrong when system crashes. The datestamp older than two years indicates that there might be some library problem what could get fixed by just recompiling against newer libraries. With objdump -x you see what dependencies that binary has.
this is what i get when I try the new version of server.. I've tryed copyin the game over from my windows.. still wants to be stubborn about it though..
Are the files in correct case? (linux filesystems are case-sensitive).
"strace -e trace=file /usr/local/games/sof2/sof2ded" and you see what files it tries to access.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.