I give, What in the world is the trick with AIGLX?

[Oldman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

	Off and on I have tried starting compiz using the various "spells"
found here, and there, with little to no success.  I surely thought that
by now I'd get it working.

	The recommended menu starting system returns with a non informative
warning that compiz could not start.  Running the "desktop-effects"
provides a little useless information in the form:

compiz: No GLXFBConfig for default depth, this isn't going to work.
compiz: Failed to manage screen: 0
compiz: No managable screens found on display :0.0

Well I don't know what GLXFBConfig is or how to set it and googling did
no good in that regard.  I did try to change the default depth to 16
colors but there was no GLXFBConfig for that depth either and likewise
setting the screensize to 1024x768 (from 1280x1024) did not help either.

I should have explained that I have a 1.5Ghz lintel box with an nVidia
5600 series graphics card.  I have a list of cards that supposedly work
with AIGLX and this card is on it.

The only other thing that might be involved is an entry in Xorg.0.log"

[scott@ipmyownlilip ~]$ grep DRI /var/log/Xorg.0.log
(II) Loading extension XFree86-DRI
(EE) AIGLX: Screen 0 is not DRI capable

Two  other items of interest are that I downloaded a live CD that has
AIGLX and other features (including the latest nVidia driver) and that
does work well, though I was not too impressed with other facets of
Sabayon linux. The other is that an attempt to use livna's kmod-nvidia
module was a disaster, restarting X every time I accessed glx
(screensavers and glxgears).  AFAIK this module is not necessary (or
encouraged for that matter) to use AIGLX.  enclosed is my xorg.conf and
xorg.0.log in case that is any help.

Scott
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFFKsVV5mBKdb7VQEcRAsNiAJ4pKJ7Nay/FJ6gw3YROwx6OI/vl6gCfc9FZ
> h7bR/z3h6dbyyxbL3ZoH7gY=
> =NQGg
> -----END PGP SIGNATURE----- 
# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"

 ### Comment all HorizSync and VertSync values to use DDC:
#	HorizSync    30.0 - 81.0
#	VertRefresh  56.0 - 75.0
	Identifier   "Monitor0"
	ModelName    "Samsung SyncMaster 193P/CX910P (Analog)"
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nv"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1280x1024" "1280x960"
"1280x960" "1280x800" "1280x800" "1152x864"
"1152x864" "1024x768" "1024x768" "800x600"
"800x600" "640x480" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1280x1024" "1280x960" "1280x800"
"1152x864" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

[Jesse Keating]

On Monday 09 October 2006 17:55, oldman wrote:
>  (EE) AIGLX: Screen 0 is not DRI capable 
This is the key.  W/out DRI you can't do AIGLX.  In order to get DRI for your 
nvidia card, you'd have to use the closed source binary drivers.  Other video 
chips, such as intel, have opensource 3d rendering and thus can use AIGLX out 
of the box.

-- 
Jesse Keating
Release Engineer: Fedora

[Oldman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesse Keating wrote:
>  On Monday 09 October 2006 17:55, oldman wrote:
> > (EE) AIGLX: Screen 0 is not DRI capable
>  
>  This is the key.  W/out DRI you can't do AIGLX.  In order to get DRI for your 
>  nvidia card, you'd have to use the closed source binary drivers.  Other video 
>  chips, such as intel, have opensource 3d rendering and thus can use AIGLX out 
>  of the box.
>  
>   
	Thanks Jessie,  I was pretty sure that was the case, but didn't realize
that nVidia's driver will fix the problem.  Do you know if it's AIGLX
that is causing the error in xorg.log?  I don't see the error in my FC5
or Ubuntu (non-AIGLX)?

Scott


> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD4DBQFFKsyU5mBKdb7VQEcRAoAnAJisDpw0h8RNyyChFZaaMnwN3vR6AKCck0T+
> Qm/vdDXUYVcV3Jw5CEKcOA==
> =+Ai8
> -----END PGP SIGNATURE-----

[Adam Jackson]

oldman wrote:
>  	Thanks Jessie,  I was pretty sure that was the case, but didn't
> realize
>  that nVidia's driver will fix the problem.  Do you know if it's AIGLX
>  that is causing the error in xorg.log?  I don't see the error in my FC5
>  or Ubuntu (non-AIGLX)? 
Well, yes.  AIGLX is the piece that hooks up a DRI driver to the GLX 
rendering path in the X server.  There isn't one for the nv driver, so 
the AIGLX subsystem is just telling you it can't find one.

AIGLX is only included in X servers from Xorg 7.1 and later, which 
neither FC5 nor Dapper include.

- ajax

[Kristian Kristensen]

oldman wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  Jesse Keating wrote:
> > On Monday 09 October 2006 17:55, oldman wrote:
> >> (EE) AIGLX: Screen 0 is not DRI capable
> > This is the key.  W/out DRI you can't do AIGLX.  In order to get DRI for your 
> > nvidia card, you'd have to use the closed source binary drivers.  Other video 
> > chips, such as intel, have opensource 3d rendering and thus can use AIGLX out 
> > of the box.
> >
> >
>  	Thanks Jessie,  I was pretty sure that was the case, but didn't realize
>  that nVidia's driver will fix the problem.  Do you know if it's AIGLX
>  that is causing the error in xorg.log?  I don't see the error in my FC5
>  or Ubuntu (non-AIGLX)? 
Yes, the error message comes from AIGLX, that's why it's prefixed with 
'AIGLX'.  During the initialization, AIGLX checks that DRI is present.  If not 
it logs this error and fall back to software rendering.

Kristian

[Arjan van de Ven]

On Mon, 2006-10-09 at 18:04 -0400, Jesse Keating wrote:
>  On Monday 09 October 2006 17:55, oldman wrote:
>  > (EE) AIGLX: Screen 0 is not DRI capable
>  
>  This is the key.  W/out DRI you can't do AIGLX.  In order to get DRI for your 
>  nvidia card, you'd have to use the closed source binary drivers.  
or help out the nouveau guys to get their open source DRM driver for
nvidia finished!

[Kristian Kristensen]

oldman wrote:

>  I should have explained that I have a 1.5Ghz lintel box with an
> nVidia
>  5600 series graphics card.  I have a list of cards that supposedly work
>  with AIGLX and this card is on it. 
Where did you get that list of cards?  It's wrong and should be corrected; 
nvidia cards doesn't work with AIGLX.

thanks,
Kristian

[Marc Schwartz]

Kristian Høgsberg wrote:
>  oldman wrote:
>  
> > I should have explained that I have a 1.5Ghz lintel box with an nVidia
> > 5600 series graphics card.  I have a list of cards that supposedly work
> > with AIGLX and this card is on it.
>  
>  Where did you get that list of cards?  It's wrong and should be 
>  corrected; nvidia cards doesn't work with AIGLX.
>  
>  thanks,
>  Kristian 
You might want to take note that a few weeks ago, nVidia released a beta 
version of their driver, 9625, which supports TFP to enable AIGLX to work:

   http://www.nzone.com/object/nzone_downloads_rel70betadriver.html

and they have a sticky post on the nvnews forums regarding configuration:

   http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14

There have been mixed results and a fair number of bug reports, but many 
are using compiz/beryl on nVidia cards under AIGLX.

HTH,

Marc Schwartz