I have problems with Nexuiz on my new computer. Esteel and KadaverJack tried to help me this night, but the problem could not be solved. Anyway, thx for your help!

Hardware:
chip Intel core2 duo E6420
mainboard gigabyte 965P-DS3
ram Kingston 2GB Kit
vga MSI Geforce 8600 gts OC


OS OpenSuse 10.2
nvidia-driver 100.14.06 (seems to be installed correctly)


With Nexuiz20070514 i only get a black screen. Menue can not be loaded. That´s it.

With Nexuiz20070523 the game starts and everything looks normal. Sometimes i am able to create a game, but when i change a map Nexuiz crashes. Some times i get the following error message.

Code: Select all

Server: Nexuiz build 23:38:44 May 23 2007 (progs 13707 crc)

<===================================>

Soylent Space
CDAudio: Bad track number 0.
Gut_EateR entered the game
Gut_EateR connected
Gut_EateR is spectating now
Fake CD track 6 playing...
[BOT]Flatline connected
unconnected changed name to [BOT]Flatline
Received signal 6, exiting...
Client "Gut_EateR" dropped
Client "[BOT]Flatline" dropped
Couldn't write config.cfg.
OpenGL Backend shutting down
Received signal 11, exiting...
recursive shutdown
Speicherzugriffsfehler

Sometimes Nexuiz freezes the whole system ---> crash

As esteel suggested i started the game with "-save". The game runs normal without crash.

The last thing we tried this night was to start nexuiz in gdb, but my whole system crashed again.

Any ideas?

First of all, does the whole system really crash? Try Ctrl-Alt-Backspace.

Secondly, where did you get that nvidia driver from? The current version is 1.0.9755. 100.14.06 is a beta driver - it can very well happen that it crashes the system, after all, this driver is not stable yet. You should report the crash to nvidia then so they can make sure it doesn't happen in the final version of their driver.

Thirdly, if an application can make the whole system crash, it isn't the application's fault - only drivers and the operating systems are meant to be able to crash the system. Without administrator rights, it should never be possible to crash the system, or the OS or some driver has a bug. In this case, it's quite obviously the nvidia driver.

Gut_Eater wrote:OS OpenSuse 10.2
nvidia-driver 100.14.06 (seems to be installed correctly)

How did you install it? Make absolutely sure that it is properly installed.

Do not attempt to mix nvidia installers such as NVIDIA-Linux-x86_64-1.0-9755-pkg2.run with OpenSuSE packages such as provided by a repository mentioned on http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html as (in my experience) it results in significant instability, often making the desktop lock up, and rarely crashing the whole system.

Please do read that nvidia drivers on suse howto.

I just installed the current nvidia beta driver and got no crash when testing. Maybe I will get one later, but at the moment, it works fine.

So it probably is what LordHavoc suspects...

First i tried the "easy way" like it is discribed here http://en.opensuse.org/NVIDIA.
But that did not work. So i downloaded the driver 100.14.06 from nvidia.com and installed it the "hard way":

Code: Select all

sh NVIDIAxxx.run -q

Code: Select all

sax2 -r -m 0=nvidia

About 20 minutes ago i deinstalled the packages that i installed by going "the easy way" and tried to install nvidia drivers 1.0.9755. There were no error messages. But as i tried

Code: Select all

sax2 -r -m 0=nvidia

and sax tried to start x11 i got a black screen.
Now i am not able to start OpenSuse in text-mode. I always end up in the black screen.
(i am typing this on another pc)

Gut_Eater wrote:But as i tried

Code: Select all

sax2 -r -m 0=nvidia

and sax tried to start x11 i got a black screen.
Now i am not able to start OpenSuse in text-mode. I always end up in the black screen.
(i am typing this on another pc)

You can type in custom commandline options at the grub boot screen, such as these:

Code: Select all

vga=normal 3

vga=normal uses VGA text mode which always works, and the 3 by itself loads up text mode instead of X.

LordHavoc wrote:You can type in custom commandline options at the grub boot screen, such as these:

Code: Select all

vga=normal 3

vga=normal uses VGA text mode which always works, and the 3 by itself loads up text mode instead of X.

Ok, i was able to reinstall nvidia driver 100.14.06 and have my X back. Nexuiz crashed again with the error message of my first post.

I believe that there is something more wrong with my PC. I am not able to install neither WinXP nor W2k. During both tries setup stops with the error message ...INACCESSIBLE_BOOT_DEVICE...

I have to cry a bit.

Edit: the error message during windows installation seems to be a problem with S-ATA

Gut_Eater wrote:Edit: the error message during windows installation seems to be a problem with S-ATA

Windows is pretty clueless about boot devices, my dad had to disconnect his IDE drive to get windows to install on his SATA drive, and then reconnecting it triggered the windows reactivation thing because it couldn't seem to understand that SATA was bootable even if IDE was present (obviously it does work, it just freaked out about the drive order changing).

If you have sn XP Service Pack 1 install, you will need drivers for s-ata controllers.

crud.. to late

I think I had a similar problem previously. Whenever I tried running Nexuiz it wouldnt load and say something about a path problem. I traced it down to the number of maps I had in my data dir.
I took some out and it worked again. Do you have a lot of downloaded maps?
I am curious if it is a numbers thing or size thing.

I thought I had a bad .pk3 file but as I removed them and added them say 5 at a time it became obvious that it wasnt the maps themselves but at some point I got the errors again.

It was a while ago now and details are sketchy so I hope I am not too far offtrack.

-Monstrosity

Hmm, it seems that winXP needs a floppy-disk with the SATA-drivers during installation. Unfortunately i dont have a floppy-disk in my PC.
So i have to take it from my old PC just for installation. What a crap. I would not install any Windows on my PC, but i wanna check, if i have the same problems with nexuiz (or the nvidia-driver) as on Linux.
I hope i get that done tomorrow.

@Monstrosity:
I did test nexuiz with no extra-maps installed.

@all
Thx for your replies!

Back to topic.

I started nexuiz in gdb like divVerent discribed in this thread: http://www.forums.alientrap.local/viewtopi ... ight=debug
I used nexuiz-linux-686-glx.

This is the output of gdb:

Code: Select all

<===================================>

Soylent Space
CDAudio: Bad track number 0.
ddPlayer entered the game
ddPlayer connected
ddPlayer is spectating now
Fake CD track 6 playing...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1212687808 (LWP 5114)]
0xb7f01410 in ?? ()
(gdb) bt
#0  0xb7f01410 in ?? ()
#1  0xbfc4c36c in ?? ()
#2  0x00000006 in ?? ()
#3  0x000013fa in ?? ()
#4  0xb7bca060 in raise () from /lib/libc.so.6
#5  0xb7bcb801 in abort () from /lib/libc.so.6
#6  0xb70f5785 in _nv000136gl () from /usr/lib/libGLcore.so.1
#7  0xb731d40b in _nv000130gl () from /usr/lib/libGLcore.so.1
#8  0x11584420 in ?? ()
#9  0x11584418 in ?? ()
#10 0x11584418 in ?? ()
#11 0x00000000 in ?? ()
(gdb)             

It seems, that some maps dont lead to a crash. I can play aggressor, downer or farewell like normal. But changing to warfare or soylent make nexuiz run like in slow-motion until it freezes or crashes. I can only see the sky then, not the map itsself.

I hope the gdb-output might help.

One step forward!!!

If i deactivate the OpenGL 2.0 shader in the menu, i am able to play as usual. No crashes or freezes or whatever.

Is there a problem with the GL_Version of nvidia-driver?

Code: Select all

^7checking for OpenGL 1.1.0...  enabled
^7GL_VENDOR: NVIDIA Corporation
^7GL_RENDERER: GeForce 8600 GTS/PCI/SSE2
^7GL_VERSION: 2.1.1 NVIDIA 100.14.06

Are more things than OpenGL 2 turned off, if i run nexuiz with "-safe", or is it the same?

-safe turns lots of features off.

If you are absolutely sure that you installed everything right, ask on the nvidia forum.

Gut_Eater wrote:One step forward!!!

If i deactivate the OpenGL 2.0 shader in the menu, i am able to play as usual. No crashes or freezes or whatever.

Well if its really the shaders that make it crash you should report that bug.. glsl shaders are not allowed to crash an application from what i gathered

divVerent wrote:If you are absolutely sure that you installed everything right, ask on the nvidia forum.

Well, i am not 100% sure, but it seems that the driver was installed correctly. I dont know how to prove the opposite.

I will report the issue in the nvidia-forum.

So let´s see ...

http://www.nvnews.net/vbulletin/showthread.php?t=92259

it seems to me like your pk3 is messed up. Try opening it in winzip or file roller or whatever.
also check to see if all your shaders are there/intact...

[TSA] Psychiccyberfreak wrote:it seems to me like your pk3 is messed up. Try opening it in winzip or file roller or whatever.

That's very unlikely, since a currupted pk3 should have cause errors while extracting nexuiz-<bla>.zip

also check to see if all your shaders are there/intact...

Even more unlikely, since the shaders are hardcoded in the engine binary...

[TSA] Psychiccyberfreak wrote:it seems to me like your pk3 is messed up.

No matter how messed up the PK3 is, the engine shouldn't be able to hang the whole system. If it does, the bug is on nvidia's (or maybe on Linux's) side. So IMHO it was right to report it on the nvidia site... and maybe the upcoming update will fix it for you.

My problem was fixed with the new version of the nvidia-driver (100.14.09).

Thx for your help!

omfg how I missed you my dearest!

I really miss you, too!!! But i hope i will be present more often in some days.