Page 1 of 1
debian stable Syscall ABI mismatch
Posted: Thu Nov 29, 2012 9:56 pm UTC
by epicdude
Unvanquished 0.8.0 i386 Nov 4 2012
debian stable
radeon, repository based closed drivers (with binary blob) fglrx
crashes when I start a map.
8Syscall ABI mismatch
recursive error 'Syscall ABI mismatch' after: Syscall ABI mismatch
OpenAL capture device closed.
recursive error 'Syscall ABI mismatch' after: Syscall ABI mismatch
tremulous works fine on this computer
Re: debian stable Syscall ABI mismatch
Posted: Fri Nov 30, 2012 8:34 am UTC
by Ishq
Unvanquished 0.8.0 i386 Nov 4 2012
For this version, we dropped the ".i386" extension. Make sure you are running "daemon" not "daemon.i386" or "daemon.x86_64"
Re: debian stable Syscall ABI mismatch
Posted: Fri Nov 30, 2012 8:51 am UTC
by epicdude
I use ./daemon and get same error
also its hard to make mistake, no such file...
~/Unvanquished$ ls
COPYING.txt download-pk3.sh librendererGL3.so uninstall unvanquished.png
daemon GPL.txt librendererGL.so uninstall.dat
daemonded lib32 main unvanquished
this works for trem:
$ file tremulous.x86
tremulous.x86: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, not stripped
this fails for unva:
$ file daemon
daemon: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, not stripped
Re: debian stable Syscall ABI mismatch
Posted: Fri Nov 30, 2012 1:31 pm UTC
by danmal
Verify that there's not an old vms-0.x.pk3 in either ~/.Unvanquished/main or ~/Unvanquished/main
Re: debian stable Syscall ABI mismatch
Posted: Fri Nov 30, 2012 2:22 pm UTC
by epicdude
was but deleting it in both dirs doesn't help
Re: debian stable Syscall ABI mismatch
Posted: Sun Dec 02, 2012 12:41 am UTC
by Anomalous
Let me guess…
Unvanquished 0.8.0 with vms-0.9.0.pk3? That'll never work.