nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   GL doesn't work, need help (http://www.nvnews.net/vbulletin/showthread.php?t=23039)

shaggyoaf 01-03-04 04:41 AM

GL doesn't work, need help
 
GL applications on my machine do not work after installing this new driver (NVIDIA-Linux-x86-1.0-5328).
The output from UT (Unreal Tourniment, a gl app) is:
Quote:

...
Opening SDL viewport.
Bound to SDLGLDrv.so
Loaded render device class.
Initializing SDLGLDrv...
binding libGL.so.1
appError called:
Could not load OpenGL library
Executing UObject::StaticShutdownAfterError
Executing USDLClient::ShutdownAfterError
Executing USDLViewport::ShutdownAfterError
USDLGLRenderDevice::ShutdownAfterError
Signal: SIGIOT [iot trap]
Aborting.
Exiting.
Name subsystem shut down
It looks like it's not finding libGL.so.1 or possibly SDLGLDrv... I don't know what those things are or where they're supposed to be... *shrug*

Also, it appears that glx is getting run correctly when I startx, In /var/log/XFree86.1.log with regaurd to GLX I found this:
Quote:

(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.5328
Module class: XFree86 Server Extension
ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX

and then
grep NVIDIA XFree86.1.log
gives this:

Quote:

(II) Module glx: vendor="NVIDIA Corporation"
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA XFree86 Driver 1.0-5328 Wed Dec 17 13:56:09 PST 2003
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(--) Chipset NVIDIA GPU found
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xD8000000
(--) NVIDIA(0): MMIO registers at 0xDE000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 Ti 4200 with AGP8X
(--) NVIDIA(0): VideoBIOS: 04.28.40.21.00
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): CRT-1
(--) NVIDIA(0): Detected TV Encoder: Philips 7104
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 8 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 16 bpp: 350 MHz
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 32 bpp: 350 MHz
(WW) NVIDIA(0): The user specified HorizSync "50.000-130.000" has been
(WW) NVIDIA(0): adjusted to "50.000-72.000" (the intersection with
(WW) NVIDIA(0): EDID-specified HorizSync "30.000-72.000")
(II) NVIDIA(0): Generic Monitor: Using hsync range of 50.00-72.00 kHz
(II) NVIDIA(0): Generic Monitor: Using vrefresh range of 50.00-85.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz
(II) NVIDIA(0): Not using default mode "640x350" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x175" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "720x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "360x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using mode "1920x1440" (no mode of this name)
(**) NVIDIA(0): Validated modes for display device CRT-1:
(**) NVIDIA(0): Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(**) NVIDIA(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(**) NVIDIA(0): Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): Display dimensions: (320, 240) mm
(--) NVIDIA(0): DPI set to (101, 108)
(WW) NVIDIA(0): Failed to verify AGP usage
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): Setting mode "640x480"
and I don't see any problems in there.

So my question is: Why aren't GL apps accelerated? What have I done wrong?

SuLinUX 01-03-04 06:19 AM

It's a problem with the UT installer, your best off putting "UT Signal: SIGIOT [iot trap]" in a search engine and finding a solution for it as it's a common issue it've noticed.

I use WineX so I dont have that problem.

shaggyoaf 01-03-04 01:36 PM

That may be true of the UT installer but nothing GL works... Not glxgears, not anything under winex... nothing.

Papol 01-03-04 04:08 PM

Before you give up, take a look at this directory:

ls -l /usr/X11R6/lib/tls

and if you see files there, try moving the directory while you're playing ut2k3, and restoring it afterwards.

mv /usr/X11R6/lib/tls /usr/X11R6/lib/tls.sav

play ut2003

put tls back:

mv /usr/X11R6/lib/tls.sav /usr/X11R6/lib/tls


note: of course, if that actually worked, then slap those into some little shellscripts like bin/preut and bin/postut and invoke ut in a way that makes it all transparent. If it doesn't work, it was worth a shot ;)
--

This may be totally unrelated to your distro, but on some, X has Mesa installed and ut2003 will look there first, instead of heading for /usr/lib/tls (or wherever they're supposed to be on your distro). Another version of this is uninstalling any Mesa libs, but that's drastic considering that some apps are happier with them there, and other's like ut* and q3* aren't.

g/l

**edit**

as I reread your messages, I think the odds of this helping you are slim because glxgears doesn't even run. It shoud at least run, even if it runs poorly with either set of glx files.

melikamp 01-21-04 10:51 PM

I had this problem when I tried to update my 2.4.22 slackware kernel with 5328 driver. No matter how I configured my kernel, I always had

(WW) NVIDIA(0): Failed to verify AGP usage

in the logs, and whilst the X mostly worked, I had to startx twice (1st one always crashed), and the 3D acceleration lagged like hell. I tried building the driver against 2.6.1 kernel, but configuration failed.

I solved it by stepping back to 4496 and 2.4.22 kernel, which works fine for now. X started and UT and Quake are running fine :P

Mel


All times are GMT -5. The time now is 07:31 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.