Resource id in failed request: 0x1600010

Technical support for all issues relating to Defcon Linux

Moderator: Defcon moderators

LePsy666
level0
Posts: 2
Joined: Tue Jul 05, 2011 7:01 pm

Resource id in failed request: 0x1600010

Postby LePsy666 » Tue Jul 05, 2011 7:08 pm

Hi everyone

I am trying to launch the linux version of Defcon bu I still get the same error :

Code: Select all

benoit@PSYKOZ-IV:~/games/defcon-v1.42$ ./defcon
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  137 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x1600010
  Serial number of failed request:  36
  Current serial number in output stream:  36
benoit@PSYKOZ-IV:~/games/defcon-v1.42$


My configuration is an Intel E6500 with GeForce 9500GT and 2GB RAM. I am currently runing a Debian Squeeze ( updated from a lenny one ) 32 bits with a 2.6.26-2-686 kernel

Can anybody help me ?

Regards, Benoît
User avatar
bert_the_turtle
level5
level5
Posts: 4796
Joined: Fri Oct 13, 2006 6:11 pm
Location: Cologne
Contact:

Postby bert_the_turtle » Tue Jul 05, 2011 8:41 pm

Looks like you forgot to reistall the evil binary blob GL driver from NVidia after your upgrade.
LePsy666
level0
Posts: 2
Joined: Tue Jul 05, 2011 7:01 pm

Postby LePsy666 » Sun Jul 10, 2011 2:40 pm

Hi, thx for the answer,

Looks like you forgot to reistall the evil binary blob GL driver from NVidia after your upgrade.


How should I do this ?

I've added :

Code: Select all

Section "Module"
    Load           "glx"
EndSection


to my xorg.conf and my X is starting without error but when I try to get the GLX configuration on the nvidia-settings tool ( I installed it with the driver from nvidia's website ), this tool crashes :

Code: Select all

root@PSYKOZ-IV:~# nvidia-settings
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 381 error_code 3 request_code 137 minor_code 4)
  (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.)
root@PSYKOZ-IV:~#


Any ideas ?

Return to “Linux Troubleshooting”

Who is online

Users browsing this forum: No registered users and 2 guests