problem with ubuntu gutsy and nvidia drivers

[HGL]

Hi regnum fellows!

The problem started when i upgraded from (ubuntu) Feisty to Gutsy.
In Feisty Regnum worked like a charm, but now in Gutsy it doesnt. If i use Kde i can make regnum to start but the starting demo runs WAAAYY to fast. And the game runs about 1-5 fps. Even when i toyed with setups and turned all 'eye candys' off i still didnt got any major improvement.I didnt got any backtraces or error reports so hard to say what was the problem in there.
But in Gnome the game wont even start and will give me this. I hope some one gets something out of it.
backtrace.txt (http://koti.mbnet.fi/hege/regnumlogs/backtrace.txt)

My computer details:
OpenGL renderer string: GeForce 7800 GS/AGP/SSE2/3DNOW!
OpenGL version string: 2.1.1 NVIDIA 100.14.11

model name : AMD Athlon(tm) 64 Processor 3500+
cpu MHz : 2419.838
MemTotal: 1035376 kB (1Gb)

i hope this helps

-worse than satan- :fury:

[Froste]

show me output of

glxinfo | grep -i direct

and if you're using an agp card, show me output of

cat /proc/driver/nvidia/agp/status

[magnet]

See older post, launch the game using

MALLOC_CHECK_=0 ./rolauncher

Hope it helps.

[HGL]

Froste, 'direct render' is yes. And i use agp card. Here's the agp/status:

:~$ cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled


magnet, done that. Same result :S

I even tried other games, if the problem is there too, but nope. All other games ran nice and smoothy.

[arlick]

post the output of glxinfo please.

i dont know but... nvidia needs tmpfs file system mounted? i need it.

try adding this to your fstab:

tmpfs /dev/shm tmpfs defaults 0 0

and then:

sudo mount -a

[HGL]

I dont want to be a sceptic but i'm pretty sure glxinfo doesnt help u much. But i still link it to here. And i tried to mount tmpfs with no help.
glxinfo.txt (http://koti.mbnet.fi/hege/regnumlogs/glxinfo.txt)

[arlick]

the agp module is loaded?

try lsmod | grep agp

[Froste]

show me output of

ls -l /usr/lib/libGL.so*

[HGL]

i hope this helps :)

:~$ lsmod | grep agp
amd64_agp 13700 1
agpgart 35016 2 nvidia,amd64_agp



:~$ ls -l /usr/lib/libGL.so*
lrwxrwxrwx 1 root root 10 2007-09-14 03:59 /usr/lib/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root 18 2007-09-14 03:59 /usr/lib/libGL.so.1 -> libGL.so.100.14.11
-rwxr-xr-x 1 root root 608400 2007-09-14 03:59 /usr/lib/libGL.so.100.14.11

[Froste]

are you using the 64bit client or the 32bit client?

[HGL]

Both are 32bit :) Kernel and regnum client.

[HGL]

I installed Debian Lenny for alternate OS. Regnum works greate in this system. So the the problem cant be the driver. I think its elsewhere. Gutsy uses very latest libraries and cpp and so on. So i think there is something mismatches between Ngd's compiler/libraries and gutsys.

[arlick]

your glib version?

in both system

[Froste]

but with a mismatch it wouldn't start at all...

do ldd on the regnum binary

[HGL]

ii libglib2.0-0 2.14.0-2 ..same in both system.


ldd rolauncher
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7f8e000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7f89000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7bcf000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7b3f000)
libGL.so.1 => /usr/lib/libGL.so.1 (0xb7aa9000)
libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0xb7aa4000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb7a96000)
libXt.so.6 => /usr/lib/libXt.so.6 (0xb7a45000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7951000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb792c000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7921000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb77d7000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb771a000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7702000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb76c4000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb75d3000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7598000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7594000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb7591000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xb7589000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7573000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7550000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7530000)
/lib/ld-linux.so.2 (0xb7fc6000)
librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7527000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb751e000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb751a000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb7517000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb7512000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb74f7000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb74f3000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb747d000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb7451000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7449000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb7441000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb743b000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb7432000)
libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0xb6a99000)
libnvidia-tls.so.1 => /usr/lib/tls/libnvidia-tls.so.1 (0xb6a97000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb6a94000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xb6a7c000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6a77000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb6a48000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb69d9000)



I hope these helps :)

..and sorry about delay

[Froste]

Just to make things clear, the game does run, it just runs a little bit slower than you expect? At least when it comes to agp/debian/nvidia, if you update the package libmesa-glx it will overwrite the /usr/lib/libGL.so symlink and point it to the mesa one instead of the nvidia one, which will result in that agp gets disabled, and you experience jerks and extreme choppiness every 3-5 seconds, I was hoping this would be the case but obviously it isn't, and everything you have looks just fine, so, I'm left with the really obvious question:

Are you perhaps running the game in such a stupidly high resolution that your computer and graphics card just can't cope?

What happens if you play in a lower (much lower) resolution?

[HGL]

first, the game runs fine in feisty, lenny but no in gutsy. And yeah i run it "stupidly high resolution" (2560x1600) xD ..but my gfx card handle it well, and there wasnt any difference at lower resolution.
Second, the difference between feisty/lenny > gutsy is not "little", its alot. 60-120fps > 2-10fpses. And funniest part is, other games runs fine in gutsy.. like Nexuiz (first person shooter). I got even higher fps than before.

i hope this starts to work when Gutsy is completly ready. :)

[jata]

hello!

I have the same trouble with rolauncher..

Gutsy with NVidia graphic card..

but now I updated system to latest update, so I check situation after reboot..

other games which use OpenGL works fine [like Enemy Territory, Word of Padman and similar..]

p.s.
sry for my english...

[trash]

I've pretty much stopped upgrading my k/x/ubuntu machines UNTIL the finished release of each new version comes out, you've got to expect problems if you choose to use an unfinished version of an OS. Downgrade back to Feisty and wait till the finished release I'd advise..

[DeepThought]

Have you tried installing the new NVIDIA-driver v. 100.14.19?

It works great for me in Gutsy (well, at least with MALLOC_CHECK_=0 ./rolauncher).

[HGL]

I have to try. Now i'am using 100.14.11.. i'll tell a result later ;)

[Franz1789]

if I use malloc_check, I don't have (apparently) problems with Gutsy. Will the client be updated soon?

[arlick]

if I use malloc_check, I don't have (apparently) problems with Gutsy. Will the client be updated soon?

no man ;)

this option only take effect in the console session, if u close the console this variable will leave your computer

[Tabris]

no man ;)

this option only take effect in the console session, if u close the console this variable will leave your computer

So write:

MALLOC_CHECK_=0 ./rolauncher &

And you won't need the console anymore :P

[Titaniumwolf]

If any of you know some programing, what would we need to do so we could set that as the launcher and run it that way.

I tried with
#!/bin/sh
cd "/home/wolf/regnum"
MALLOC_CHECK_=0 ./rolauncher
but I have no idea what I'm doing. So could one of you please post a little script we could use to launch it?

[klixon]

Titanium: That's the spirit :clapclap: It should work like that.

A bit more traditional:
#!/bin/bash
MALLOC_CHECK_=0
RO_PATH=/path/to/regnum
cd ${RO_PATH}
./rolauncher
And don't forget to chmod u+x that script ;)