nVidia 9xxx drivers and compiz with AIGLX

[Craig_Williamson]

Hi All,

I'm trying to get compiz working with the new nvidia 9625 beta drivers. The compiz ebuild I am using comes straight from the portage tree. I have tried the following sites to the letter to get it working but have had no success so far.

http://www.nvnews.net/vbulletin/showth ... p?t=77030

http://gentoo-wiki.com/Compiz


I have used the LD_PRELOAD=/usr/lib/opengl/nvidia/lib/libGL.so.1 linker when starting compiz but I don't get anything. Metacity disappears and compiz segfaults. I have used the compiz-aiglx command as well as making the compizrc file as listed in the nvnews site. Has anyone found some good how-tos to get compiz working with the new nvidia drivers. If anyone could help that would be greatly appreciated. Thanks.


Craig

[Ansorg]

HowTo: http://www.nvnews.net/vbulletin/showthread.php?t=77030

[Headrush]

HowTo: http://www.nvnews.net/vbulletin/showthread.php?t=77030

Nice answer, post a link to the how-to he mentioned he followed in the original question.

There are several threads about this already, have you checked them?

[Ansorg]

HowTo: http://www.nvnews.net/vbulletin/showthread.php?t=77030

Nice answer, post a link to the how-to he mentioned he followed in the original question.

Argh, sorry about that
I shouldn't try to be helpful that early in the morning, without even having a cup of coffee

[Craig_Williamson]

Hi Again,

I'll try and be a bit more specific. I am using the new 9625 beta drivers from nvidia. Here is my /etc/X11/xorg.conf file:

Code: Select all

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	RgbPath      "/usr/share/X11/rgb"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/misc"
	FontPath     "/usr/share/fonts/75dpi"
	FontPath     "/usr/share/fonts/100dpi"
	FontPath     "/usr/share/fonts/TTF"
	FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
	Load  "glx"
	Load  "extmod"
	Load  "xtrap"
	Load  "record"
	Load  "dbe"
#	Load  "dri"
	Load  "freetype"
	Load  "type1"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "keyboard"
	Option	    "CoreKeyboard"
	Option      "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mouse0"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Philips"
	ModelName    "107S66"
EndSection

Section "Device"
	Identifier  "Card0"
	Driver      "nvidia"
	Option	    "NoLogo" "true"
	VendorName  "nVidia Corporation"
	BoardName   "NV43 [GeForce 6600 GT]"
	BusID       "PCI:1:0:0"
	Option 	    "RenderAccel" "true"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	# Enable 32-bit ARGB GLX Visuals
    	Option "AddARGBGLXVisuals" "True"
	# If you are using an older version of compiz that
	# does not support rendering into the Composite
	# Overlay Window, you will need to disable clipping
	# of GLX rendering to the X Root window with this
	# option, or you will get a blank screen after
	# starting compiz:
	Option "DisableGLXRootClipping" "True"
	DefaultDepth 24
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes "1024x768"
	EndSubSection
EndSection

Section "Extensions"
	Option "Composite" "Enable"
EndSection

And here is the /usr/local/bin/compizrc file I created as part of the online docs:

Code: Select all

killall metacity &
export __GL_YIELD="NOTHING"; /usr/bin/compiz  --replace --strict-binding gconf &
/usr/bin/gnome-window-decorator

If I run the compizrc file without the LD_PRELOAD=/usr/lib/opengl/nvidia/lib/libGL.so.1 option I get a grey screen and nothing else. With that I can change the virtual desktop with the shortcut keys so it looks like compiz is starting. Also it is really slow, so I'm thinking that the mesa libs are trying to run compiz.

If I run the compizrc with the LD_PRELOAD=/usr/lib/opengl/nvidia/lib/libGL.so.1 option, metacity disappears for about one second and then reappears and compiz segfaults.

What am I doing wrong to get AIGLX and compiz working. Anyone had any success with the new nvidia beta drivers? If you can help it would be appreciated. Thanks and good luck.


Craig

[1ino1eum_4the_win]

I had the same problem as you . I did like you , modifing the /usr/bin/compiz-aixgl did'nt work.
The solution is to copy /usr/portage/x11-wm/compiz/ in you /usr/local/portage/
then edit the ebuild
and change the line :
econf --with-gl-libs="-Wl,-R/usr/$(get_libdir)/opengl/xorg-x11/lib/ -lGL" \
by
econf --with-gl-libs="-Wl,-R/usr/$(get_libdir)/opengl/nvidia/lib/ -lGL" \

trust me, that works

[Craig_Williamson]

Hi there,

Thanks for your help. Even though I trust that your suggestion works, I still couldn't get compiz to work . My xorg.conf file is listed above and the compizrc file is also listed above. Is that what you used to get compiz to work or have I done comething completely wrong? I'm not sure whether I should have followed nvidias way of setting up AIGLX or the Gentoo WIKI way. Also is the compizrc file setup correctly because it still segfaults when I try and run it. Any help would be appreciated. Thanks again and good luck.


Craig

[1ino1eum_4the_win]

here is my xorg.conf :

Code: Select all

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# 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 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

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.


# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/75dpi"
    FontPath   "/usr/share/fonts/100dpi"
#    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/Type1"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.


EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier  "Keyboard1"
    Driver      "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option     "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"   "xorg"
    Option "XkbModel"   "pc105"
    Option "XkbLayout"  "fr"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "IMPS/2"       # IntelliMouse PS/2
    Option "Device"      "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"  "Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"        "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"  "9600"
#    Option "SampleRate"        "150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "hitachi"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   24-80

#    HorizSync  30-64         # multisync
#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 56-75

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

#Section "Device"
#    Identifier "Standard VGA"
#    VendorName "Unknown"
#    BoardName  "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

#    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam   256

#    Clocks     25.2 28.3

#EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "NVIDIA 6600gt"
    Driver      "nvidia"
    VideoRam    131072
    Option     "AGPMode" "4"
    Option     "AGPFastWrite" "True"
    Option     "EnablePageFlip" "True"
    Option      "DPMS"
    Option      "NvAgp" "2"
    Option       "NoLogo" "True"
    Option "backingstore" "true"
    Option "RenderAccel" "True"
    Option "XAANoOffscreenPixmaps" "true"
 #   Option "DigitalVibrance" "integer"
    option "AllowGLXWithComposite" "True"
    # Insert Clocks lines here if appropriate
EndSection

Section "Extensions"
        Option "Composite" "Enable"
 #Option "RENDER" "Enable"
 #Option "DAMAGE" "Enable"
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "NVIDIA 6600gt"
    Monitor     "hitachi"
    DefaultDepth 24

# Enable 32-bit ARGB GLX Visuals
     Option "AddARGBGLXVisuals" "True"
# If you are using an older version of compiz that
# does not support rendering into the Composite
# Overlay Window, you will need to disable clipping
# of GLX rendering to the X Root window with this
# option, or you will get a blank screen after
# starting compiz:
#     Option "DisableGLXRootClipping" "True"
#    Subsection "Display"
#        Depth       8
#        Modes       "1280x1024" "1024x768" "800x600" "640x480"
#        ViewPort    0 0
#    EndSubsection
#    Subsection "Display"
#        Depth       16
#        Modes       "1280x1024" "1024x768" "800x600" "640x480"
#        ViewPort    0 0
#    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
# Option "AIGLX" "true"
EndSection

and here is my /usr/bin/compiz-aiglx

Code: Select all

# Start window decorator
gnome-window-decorator --replace &

# Start compiz
LIBGL_ALWAYS_INDIRECT=1 compiz --replace --use-cow --indirect-rendering --strict-binding gconf move resize minimize place decoration wobbly cube rotate scale switcher zoom fade screenshot water dbus

you got it while emerge compiz from portage

good luck

[-titan-]

I thik there error in your /usr/bin/compiz-aiglx. For me working file is:

Code: Select all

# Start window decorator
gnome-window-decorator --replace &

# Start compiz
compiz --replace --use-cow --strict-binding gconf

1) nvidia drivers (9xxx) use direct rendering (as i know), that why --indirect-rendering not needed there.
2) all parameters (plugins) after gconf not needed as well. Compiz take plugin sequence from registry (gconf-editor settings: apps->compiz->general->allscreens->options->active_plugins). And plugin sequense erroneous too. At least fade must be before cube. Sequence in my settings: gconf, place, move, resize, minimize, decoration, wobbly, fade, cube, rotate, scale, zoom, switcher, screenshot, dbus

Maybe i wrong, but it working for me (Nvidia TI4200, Xorg 7.1)
--------------------------------------
PS: Sorry fo my english.

[1ino1eum_4the_win]

well actualy, I didn't make any change to the /usr/bin/compiz-aiglx . It's the one deliver with the compiz ebuild in the official portage.
It has been made by Hanno , from this page :
http://www.hboeck.de/

actualy , I dont really understand what he says about ALWAYS_INDIRECT ... so I have'nt changed setting.
But i'm going to try your script and see if there is a difference

[1ino1eum_4the_win]

ok so I tryed without --indirect-rendering :
I have to say that it's seams better, because when I use indirect-rendering, and try to lauche the "rain" plugin , everthing goes really slow and I can't even move the windows... without "inderect-rendering", there is no more this problem, but the whole desktop seam more slow...

finalement , I dont know for what is for this :
LIBGL_ALWAYS_INDIRECT=1
and
--strict-binding gconf

Hanno says taht we should use it... and I dont see the difference, using it or not ...
bye the way, I'm with a 6600GT and 2,5GHZ, and I got about 1500 fps with glxgear
and I got about 250 or 300 when I move the cube.

I got juste about 30 when I move the cube and the --indirect-rendering is on . But it seams that the inpact is just on glxgear, not on the desktop .

if I dont used --indirect-rendering, glxgears is faster, but the whole desktop seams more slow

[-titan-]

About --indirect-rendering, i found it there: http://www.nvnews.net/vbulletin/showthread.php?t=77030

when using the NVIDIA graphics driver, you do not need to use the --indirect-rendering option; it limits the number of extensions exposed by the driver, disabling some plugins (e.g. water).

I think LIBGL_ALWAYS_INDIRECT=1 is the same option for libGL.so.

Now other problem: when compiz-quinnstorm will work with new nvidia driver? Because compiz can't change theme, and theme manager cgwm work only with compiz-quinnstorm as i know.
I trying to find portage-xgl overlay, but "layman -a portage-xgl" tell me what * Overlay "portage-xgl" does not exist.

[jonnevers]

About --indirect-rendering, i found it there: http://www.nvnews.net/vbulletin/showthread.php?t=77030

when using the NVIDIA graphics driver, you do not need to use the --indirect-rendering option; it limits the number of extensions exposed by the driver, disabling some plugins (e.g. water).

I think LIBGL_ALWAYS_INDIRECT=1 is the same option for libGL.so.

I was under the impression that you don't need AIGLX for compositing if you are using the nvidia drivers. Nvidia provides their own implementation of indirect rendering. AIGLX is for providing an indirect rendering API when driver's don't provide it.

I could be wrong.

[cerebroso]

Do your windows leave some "trail" (pieces of the window borders) when they minimize? (I'm using the same plugin order as -titan-)

__edit: nevermind, changing the plugin order and putting decoration before minimize solves it

Can't wait until xgl-coffee is back and compiz-quinnstorm is fully working with aiglx!

[Craig_Williamson]

Hi Again,

Latest update. I still can't get compiz to work. I updated to the 0.0.13_pre20060928 ebuild and tried all your suggestions and still has no luck . I noticed that when I ran compiz-aiglx without gconf at the end it seemed to run ok (that is, there was no segmentation fault). And when I re-entered gconf the segmenation fault happened again. Is this a help to anybody? Thanks heaps for all the good work you have done so far.


Craig.

[1ino1eum_4the_win]

maybe try this :

as a normal user:

Code: Select all

gconftool-2 --recursive-unset /apps/compiz
gconftool-2 --install-schema-file /etc/gconf/schemas/compiz.schemas

[-titan-]

Do your windows leave some "trail" (pieces of the window borders) when they minimize? (I'm using the same plugin order as -titan-)

__edit: nevermind, changing the plugin order and putting decoration before minimize solves it

thank you! now much better

[Craig_Williamson]

Thanks for the reply. There are more options in gconf now but the compiz-aiglx script still seg faults. Here is the message it gives:

Code: Select all

/usr/bin/compiz-aiglx: line 5:  6970 Segmentation fault      LIBGL_ALWAYS_INDIRECT=1 compiz --replace --use-cow --strict-binding gconf

Any suggestions?

[Gusar]

It's been found out on the #beryl channel, that things work much better without strict bindings and I can confirm that. Also, according to nvidia, compiz can do more stuff with direct rendering.
So, remove --strict-bindings, LIBGL_ALWAYS_INDIRECT=1 and --indirect-rendering and see how it goes. Basically, try this:

Code: Select all

compiz --replace --use-cow gconf

Oh, and one more thing: nvidia does NOT use aiglx. Even with indirect rendering, nvidia uses it's own stuff.

[1ino1eum_4the_win]

if you got an nvidia graphic card, and use the compiz from portage, the last update add a new compiz-nvidia script.
It is much the same as the one on the nvidia forum.

[piranha2001]

Try this an be happy:

http://gentoo-wiki.com/Beryl

[iamarug]

The latest freedesktop (portage) compiz is supposed to have support for metacity window decorations (which it doesnt seem to have in portage) and probably a compiz-manager tool.

I guess the ebuilds havent been fully updated yet. But in my experience, the freedesktop compiz seems to be much faster.


edit: nvm I got the metacity decorations working but they are pretty much broken right now.

[piranha2001]

Hardware-accelerated Beryl is fast enough for me (Athlon 64 X2 with Nvidia onboard Nforce 430)...
So why should I take that Gnome-dependent stuff?

[Craig_Williamson]

Hi Again.

I still can't get it to work. My thinking now is that there is nothing wrong with compiz at all and something else is causing it to fail. I'll keep looking around and see if I can find anything that is out of the ordinary. If I find anything I'll let you guys know. Thanks so much for all your help. It's been great.


Craig

[jonnevers]

Hi Again.
I still can't get it to work. My thinking now is that there is nothing wrong with compiz at all and something else is causing it to fail. I'll keep looking around and see if I can find anything that is out of the ordinary. If I find anything I'll let you guys know. Thanks so much for all your help. It's been great.
Craig

i'm saying it again. so that you see it

you don't need AIGLX for compositing if you are using the nvidia drivers. Nvidia provides their own implementation of indirect rendering. AIGLX is for providing an indirect rendering API when driver's themselves don't provide it.

all you need is xorg 7.1 and 9xxx nvidia-drivers; i use compiz w/ the standard xorg-server too (XGL is no longer required).

when i used the compiz in portage, as it is in portage, I get a full white screen when I execute

Code: Select all

compiz --replace --use-cow gconf &

I solved that by modifying the ebuild to use the nvidia libs instead of xorg-x11. this was w/ compiz-0.0.13_pre20060921.ebuild.

there is a new compiz ebuild today named compiz-0.0.13_pre20060928.ebuild, this correctly (w/o my modification) linked against the nvidia libs

Code: Select all

host username # ldd /usr/bin/compiz
...
        libGL.so.1 => //usr/lib64/opengl/nvidia/lib/libGL.so.1 (0x00002b523c773000)
...

i created a shell script on my desktop for executing compiz (and another for reverting back to metacity), startcompiz.sh

Code: Select all

#!/bin/bash
# start compiz
gtk-window-decorator --replace &
compiz --replace --use-cow gconf &