View Single Post
Old 04-05-05, 05:28 PM   #3
moon8dog
Registered User
 
Join Date: Aug 2004
Posts: 12
Default Re: glxinfo fails, BadLength

Here are the errors:


# glxinfo
name of display: :0.0
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 21 ()
Serial number of failed request: 9
Current serial number in output stream: 9


glxgears
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 21 ()
Serial number of failed request: 9
Current serial number in output stream: 9

# nvidia-settings
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 9 error_code 16 request_code 144 minor_code 21)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

I did have an old libglx.a, and renamed it so the nvidia stuff is loading, just don't know why it isn't working....
BUSID is set, as this card can run 4 heads, I have 2 running from one port.
DRI is disabled as well, as I was getting unresolved links from it.

Running Red Hat WS V4
Intel Processor 3.4GHz
NVIDIA QUADRO NVS400
2 NEC Displays
Drivers are 7167
moon8dog is offline   Reply With Quote