Totally Broken!

If you've had any problems with Nexuiz, or would like to report bugs, post here.

Moderators: Nexuiz Moderators, Moderators

Postby ds01 » Thu Apr 06, 2006 3:27 am

squimmy wrote:^7Linked against SDL version 1.2.9
^7Using SDL library version 1.2.8


That could be a problem. Try replacing the 128 with the 129.
ds01
Member
 
Posts: 47
Joined: Wed Mar 29, 2006 5:54 am
Location: Lvl 7

Postby squimmy » Thu Apr 06, 2006 4:26 pm

KadaverJack wrote:...
5) when nexuiz crashed, you will see the gdb input line again. enter "bt" and post its output here. (to quit gdb, press ctrl+d)



okay, done that and the result it...
Code: Select all
#0  0x0b76a6f0 in ?? ()
#1  0x08098ac4 in GL_Backend_CompileProgram (vertexstrings_count=1, vertexstrings_list=0xbfbcbdbc,
    fragmentstrings_count=1, fragmentstrings_list=0xbfbcbbb8) at gl_backend.c:759
#2  0x0812193c in r_shadow_start () at r_shadow.c:554
#3  0x081213d8 in R_Modules_Start () at r_modules.c:58
#4  0x08154cf4 in VID_OpenSystems () at vid_shared.c:943
#5  0x08155162 in VID_Start () at vid_shared.c:1025
#6  0x080b17a3 in Host_StartVideo () at host.c:880
#7  0x080b19cc in Host_Init () at host.c:1031
#8  0x0804afe5 in main (argc=2, argv=0xbfbcc214) at sys_linux.c:237




Okay, I am frightfully worried about touching my ati drivers. It was a total and utter pain in the ass to get them working at all, and I was only able to do that by getting some specially prepared package from mandriva. The best I can probally do is to uninstall sdl and try to compile it by hand and install like that. If the ati driver is most likely to be the problem, i guess it doesn't hurt to try reinstalling them (famous last words!).

Thanks for the help so far!
squimmy
Member
 
Posts: 15
Joined: Tue Apr 04, 2006 6:20 pm

Postby ds01 » Fri Apr 07, 2006 3:01 am

squimmy wrote:Okay, I am frightfully worried about touching my ati drivers.


The easiest thing that you could try then, would be to just compile the latest SDL and let it install into /usr/local - and then compile Nexuiz-SDL. 'sdl-config' should do all the magic-foo for you in choosing your new SDL version, because by default on Linux distros the /usr/local/bin path should override the other paths.

BTW I would be interested to know your X11 version, just do a:
Code: Select all
xdpyinfo | grep "version"
ds01
Member
 
Posts: 47
Joined: Wed Mar 29, 2006 5:54 am
Location: Lvl 7

Postby KadaverJack » Fri Apr 07, 2006 4:09 am

@ds01: installing a new SDL version won't help. Even the glx version crashed, so SDL is definitely not the problem.

@squimmy: i'm not an expert on this, but it looks like your ATI driver is causing the crash when the engine tries to compile OpenGL shaders. So upgrading your driver seems to be inevitable. There are a few commandline options to disable OpenGL shaders listed in darkplaces.txt, but i'm not shure whether they will help.
KadaverJack
Site admin and forum addon
 
Posts: 1102
Joined: Tue Feb 28, 2006 9:42 pm

Postby ds01 » Fri Apr 07, 2006 8:44 am

KadaverJack wrote:@ds01: installing a new SDL version won't help. Even the glx version crashed, so SDL is definitely not the problem.


While SDL is for the most part nearly always backwards-compatible, it is not psychic:
^7Linked against SDL version 1.2.9
^7Using SDL library version 1.2.8

It's probably the driver is built against an older release of X than the one squimmy uses, but from my personal experience with the ATI binary drivers on Linux and because those SDL games squimmy says work ok that's what I suggest (given also not wanting to mess with drivers). I say this because I've observed GLX progs failing to initialize while an SDL version [of same prog] inits fine on proprietary ATI.

That said however, it's obvious ATI has problems with API seeing as they recommend using GLEW after devs railing on them about things not being exposed (besides the point tho).
ds01
Member
 
Posts: 47
Joined: Wed Mar 29, 2006 5:54 am
Location: Lvl 7

Postby squimmy » Sat Apr 08, 2006 3:28 pm

Unfortunately it isn't sdl. I downloaded and compiled all the sdl tests and they all worked perfectly. I also ran darkplaces-sdl which is linked to sdl 1.2.8 and it still didnt' work.


I'm pretty sure it's my ati drivers, god damn it!!!!

EDIT:: Interesting fact, on trying to ./configure supertux (I allready have it installed, this was just a test) it couldn't detect any opengl support!

and...
BTW I would be interested to know your X11 version, just do a:

Code: Select all
version number:    11.0
X.Org version: 6.9.0
squimmy
Member
 
Posts: 15
Joined: Tue Apr 04, 2006 6:20 pm

Postby ds01 » Sun Apr 09, 2006 1:05 am

If you look at the error in the [supertux] configure log it should tell you why the ATI GL is giving you problems.

If the reason you have problems installing newer ATI drivers is related to the kernel-module itself, just try the same driver version only choose the ones built against Xorg. This may save you from recompiling the kernel module if that is another issue for you.

They are available here:
http://www2.ati.com/drivers/linux/fglrx_6_8_0-8.20.8-1.i386.rpm

It may not solve the X11 versioning problems with GLX though, as you noted you are using Xorg-6.9 (and ATI only provides up to Xorg-6.8). Regardless they should be closer than the XF86-4.3 ever will be, and the fact those even work for you in Xorg are miracle.

As I noted in previous post there are issues building against the ATI GL itself which can be circumvented by reinstalling the X11-Mesa implementation. Un/Installing software in Linux is as simple as moving the files to a different location (and running ldconfig if dealing with libs), but the hard part as I'm sure you are well aware of is knowing which files. Solution: look inside the RPM files with mc (Midnight Commander). It uses vfs, so you can browse inside the packages to see the names of files and where they go. Just make sure when dealing with system files you su to root, so the permissions are saved.

You really should try getting the newer drivers to work, and if you don't know about it already try this place:
http://rage3d.com/board/
There is a Linux section to that forum that may be of use to you, with Linux ATI users there.

BTW the drivers don't support 32bpp or even 16bpp, only 24bpp and pseudo 8bit. That can be a problem sometimes (you may have noticed this).
ds01
Member
 
Posts: 47
Joined: Wed Mar 29, 2006 5:54 am
Location: Lvl 7

Postby squimmy » Mon Apr 10, 2006 10:37 am

I've updated my drivers, it went very smoothly and I pretty much doubled my fps on things which do work.


But it hasn't helped things which don't work. Damn it!
squimmy
Member
 
Posts: 15
Joined: Tue Apr 04, 2006 6:20 pm

Postby esteel » Mon Apr 10, 2006 10:52 am

squimmy wrote:I did that and it compiled fine with no errors (surprisingly). But when I run ./nexuiz-glx I get the same message as I did in my first post :(.

You mean the 'Fatal signal: Segmentation Fault (SDL Parachute Deployed)' message? I must confess i do not use linux for playing yet but i do not think this error message should be produced by the -glx version.. Are you sure it was the same message?
Last edited by esteel on Thu Aug 31, 2006 7:48 pm, edited 1 time in total.
esteel
Site admin and forum addon
 
Posts: 3924
Joined: Wed Mar 01, 2006 8:27 am

Postby squimmy » Mon Apr 10, 2006 11:06 am

No, for the glx version I get a different error, aren't I lucky!

I get
Code: Select all
^7Received signal 11, exiting...
^7OpenGL Backend shutting down



and the fact those even work for you in Xorg are miracle.


Would it help if I was to downgrade?


Typically, enemy territory works great however. Why do some work and some don't?
squimmy
Member
 
Posts: 15
Joined: Tue Apr 04, 2006 6:20 pm

PreviousNext

Return to Nexuiz - Support / Bugs

Who is online

Users browsing this forum: No registered users and 1 guest

cron