what is glx?

[blobaugh]

i emerged armyops and when i ran it it exited due to server error and the error said could not find glx. what is that and where do i get it?

[gehidore]

Originally posted by blobaugh
i emerged armyops and when i ran it it exited due to server error and the error said could not find glx. what is that and where do i get it?

blobaugh,blobaugh,blobaugh,

you of all people!...


look (http://www.thelinuxdisease.com/links.htm)

[blobaugh]

thanks gehidore, i should have known you had it. but that still dont tell me what it is

[gehidore]

Originally posted by blobaugh
thanks gehidore, i should have known you had it. but that still dont tell me what it is

google? :p

[blobaugh]

google yourmom ;)

[gehidore]

Originally posted by blobaugh
google yourmom ;)

didnt find anything usefull (http://www.google.com/search?hl=en&ie=UTF-8&q=yourmom&btnG=Google+Search)

[blobaugh]

lol, that was a good one gehidore!

[mrBen]

for those actually wanting solutions when looking at this thread, glx is the opengl extension to X (as I understand it)

What you need to install will depend on your graphics card, although you may find that it is installed, but not enabled.

[comtux]

Glx is an X Module Loaded at boot for mesa support if i remember right.

e.g My XF86Config
-------------------------------------------

# ************************************************** ********************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# ************************************************** ********************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

EndSection

----------------------------------------------------
glx and dri are commented out as default.
Just make sure yours looks like mine and then reboot because these options are loaded at boot restarting X is not good enought.

Then if you have Mesa installed you should be ready to go....

A word of advise Americas Army is a very demanding game.

My System
--------------------------------
AMD Athlon 800
392 megs Ram
Rage 128 Pro Ultra 16 Meg Video Card.
32 Bit Philips Sound Card
Tv Card
Cdrw
Dvd Burner
17 Monitor
120 Gig Western Digital
--------------------------------

And americas Army is soo Slow on my system that it isn,t even playable..

Wolfenstein: Enemy Territory is a free, stand-alone multiplayer game in which players wage war as Axis or Allies in team-based combat.

link (http://www.happypenguin.org/show?Wolfenstein%3A%20Enemy%20Territory)

To everyone else this is how we help people out not by giveing smart *** comments :)

Good Day

[bwkaz]

Originally posted by comtux
Glx is an X Module Loaded at boot for mesa support if i remember right. Actually it's for OpenGL support. It's the piece of code that allows OpenGL-using programs to talk to your X server (through the publicly documented GLX extension).

The protocol is exactly the same no matter which video card driver you're using (as long as that driver supports some version of GLX), the difference is which features are supported, and how fast it goes.

and then reboot because these options are loaded at boot restarting X is not good enough. Since when?

That is most definitely not the case. Restarting X IS good enough, IF all that you need to do to get OpenGL support on your video card is load the proper X driver and the GLX extension module for your video card.

However, if you need to load a special kernel driver for your video card, or you need to load the AGP module, or something like that, then you will need to exit X, load the module, and restart X. Rebooting will only do this for you if you've already configured your system to load those modules on boot.

Take nVidia's binary drivers, for example. They provide an nvidia_drv.o file (an X video card driver), along with an nvidia.ko file (a kernel module to allow access to the card hardware). They also supply a libglx.so file (the GLX extension for X) and a libGL file (OpenGL for normal applications). The nvidia.ko file needs to be modprobe'd before you can use the various X drivers and extensions (though that driver now has support for both devfs and hotplug, so either opening /dev/nvidiactl or generating a hotplug event will load the driver). Then, the nvidia_drv.o file needs to be used as the X driver, and libglx.so needs to be loaded into X to support the GLX extension.

Then programs can link against nVidia's libGL file to get at the hardware accelerated OpenGL functions that they need to use.

And actually, with nVidia, Mesa's OpenGL library will provide only software acceleration (though that is not the case with your card or most other DRI cards; the problem with nVidia is that its driver & kernel module don't support DRI).

[comtux]

Hmm i smell a battle of wits.


---------------------------------------------------------
Actually it's for OpenGL support. It's the piece of code that allows OpenGL-using programs to talk to your X server (through the publicly documented GLX extension).

The protocol is exactly the same no matter which video card driver you're using (as long as that driver supports some version of GLX), the difference is which features are supported, and how fast it goes.
-------------------------------------------------------

:)
Thats kinda funny chuckel.............
Actually Mesa and OpenGL are the same thing.....
Mesa is they Open Source Implamentation of OpenGL

Second as i said before in my post i use slackware and when you enable glx you have to reboot because the glx module are loaded at run time unless you use a Gnu/linux version that has hardware detection that would support realtime loading of modules..

But i can only validate the case on if the glx modules are loaded in x apon restarting x or rebooting on my system and am just trying to help...
(Slackware 10 Custom Source Compile)
Now if i say changed my mouse ,Monitor Res etc etc
Then yes i would just ctl,alt,backspace to restart x and everything would be good to go.

But when i boot its right there when hotplug probes for new hardware loading x modules........

Update
I puchased 2 512 meg sticks of pc133 to day bringing me to a wopping 1024 did anyone know that haveing this much ram does very little for game performance if you have a crapy video card....
Looks like the next toy i buy will be a nice video card

Poor person we were trying to help so many options so many opinions..

My personal opinion is there is no right or wrong way just the way that works!!

[bwkaz]

Originally posted by comtux
Actually Mesa and OpenGL are the same thing..... No, they are not. OpenGL is a specification. Mesa is one implementation of that specification for Linux / DRI systems. Am I being pedantic? Probably. :D

If your video card does not work with DRI (nVidia, for example), then the Mesa OpenGL implementation will always run in software mode on your system. However, nVidia's OpenGL implementation will be able to run in hardware mode.

Second as i said before in my post i use slackware and when you enable glx you have to reboot because the glx module are loaded at run time unless you use a Gnu/linux version that has hardware detection that would support realtime loading of modules.. GLX is not implemented in a kernel module. It's an X (either XFree86 or X.org) extension library.

You do not need to reboot to get this extension to load. All you need to do is configure X (/etc/X11/XF86Config or /etc/X11/xorg.conf) and restart it. It will load the libglx.so or libglx.a library the next time it starts, and it will subsequently support the GLX extension. If 3D programs don't work after that, or if the GLX extension doesn't initialize properly, then it's because something else is wrong (likely that you don't have a required kernel module loaded -- but check your X logs).

And EVERY distro supports realtime loading of (kernel) modules. That's what /sbin/modprobe is there for. :) No, it's not automatic, but that's what the hotplug package does.

But i can only validate the case on if the glx modules are loaded in x apon restarting x or rebooting on my system Um, sorry, but I can't figure out what you mean by this sentence. Maybe the problem is that every time you say "modules" I think you are saying "kernel modules", and glx is not a kernel module. Or maybe it's something different, I'm not sure.

Could you try to reword that please?

Now if i say changed my mouse ,Monitor Res etc etc
Then yes i would just ctl,alt,backspace to restart x and everything would be good to go.

But when i boot its right there when hotplug probes for new hardware loading x modules... Again, I'm not quite sure what you're talking about here (as I have never used Slackware). Do you know what it's doing at this point in your bootscripts?

[EnigmaOne]

Originally posted by gehidore
didnt find anything usefull (http://www.google.com/search?hl=en&ie=UTF-8&q=yourmom&btnG=Google+Search)

Useful? Nope.

Interesting? http://yourmom.sh/ (Local sites)