Nvidia beta drivers 1.0-9625 - with texture_from_pixmap !!

[piercey]

Ive managed to get AIGLX working with my 6600GT (PCIE) with XFCE4. Window moving and cube rotation is fine and fast, however, I have a lot of artifacts left on my screen when i maximize/minimize a window (of the window i minimized). Anyone else had these problems and found a workaround? Maybe it's somehow XFCE related, but it seems unlikely.

Same here in KDE. My only attempts at finding a workaround have been trying different snapshots of compiz - no luck so far.

Yeah me too. I don't want to try out beryl because you need to make a stupid startx script that runs as root, and I'm not sure if compiz-quinnstorm will fix the problem (and I'll have to mess about with overlays which is why I waited for AIGLX in the first place). I've posted the problem @ nvnews.net so maybe I'll get a responce there.

[irondog]

Portage's compiz generates a lot of messages of this kind:

Code: Select all

compiz: Couldn't bind redirected window 0x2200006 to texture
compiz: pixmap 0x2600163 can't be bound to texture

Is this a bug in the driver, or can this be solved?

[Matteo Azzali]

Yeah me too. I don't want to try out beryl because you need to make a stupid startx script that runs as root, and I'm not sure if compiz-quinnstorm will fix the problem (and I'll have to mess about with overlays which is why I waited for AIGLX in the first place). I've posted the problem @ nvnews.net so maybe I'll get a responce there.

hum...... the script you need to run as root isn't for beryl, is the fix for AIGLX scheduler issue. It is supposed to be a workaround until a patched version of X.org comes out, and is taken directly from XGL (nothing to do with compiz or beryl).

Read more carefully please, as treor stated above this "scheduler issue" is present with any version of compiz.
(being a bug in Xorg+aiglx / nvidia-drivers, is supposed to behave so....)

EDIT Ah, and that is not needed if you patch your xorg-server as wojtek described here or use aiglx-accelerator from sabayonlinux

[kshade]

To who's using this: how do OpenGL and SDL games/apps and mplayer work with aiglx? I remember they had
issues in XGL, does aiglx runs fine all of them?

Anyone already tried with beryl (the new name of compiz-quinnstorm)?

Yes, I did, works nicely.

[lxnay]

SabayonLinux x86/x86-64 miniEdition with both XGL and AIGLX support will be out tomorrow
Enjoy.

[UB|K]

I'm can't launch beryl (installed from sabayon overlay), it crashes X. Here's beryl.log:

Code: Select all

X connection to :0.0 broken (explicit kill or server shutdown).
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Error: unable to open display (null)
beryl: SmcOpenConnection failed: Could not open network socket
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

beryl: Couldn't open display :0.0
XGL Absent, checking for NVIDIA
Nvidia Absent, assuming AIGLX

If i try to run it inside Xgl i get the white screen pb.
Compiz (vanilla from portage) run's fine with aiglx/nvidia.
What could be the problem??

edit: here a strace output

[lxnay]

Code: Select all

Section "Files"


    #FontPath	"/usr/share/fonts/local/"
    FontPath	"/usr/share/fonts/misc/"
    FontPath	"/usr/share/fonts/Type1/"
    FontPath    "/usr/share/fonts/TTF/"
    FontPath	"/usr/share/fonts/75dpi/"
    FontPath	"/usr/share/fonts/100dpi/"
    FontPath 	"/usr/share/fonts/corefonts"

EndSection

# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************

Section "Module"

    Load	"dbe"
    Load	"glx"
#    Load	"ddc"
    Load	"type1"
    Load	"freetype"
    Load	"extmod"
    Load	"synaptics"

# Load "dri"

EndSection


# **********************************************************************
# Server flags section.  This contains various server-wide Options.
# **********************************************************************

Section "ServerFlags"

     Option 	"AllowMouseOpenFail" "true"
     #Option     "AIGLX" "true"

EndSection

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

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

Section "InputDevice"
    Identifier      "Mouse3"
    Driver          "synaptics"
    Option          "SendCoreEvents"        "true"
    Option          "Device"                "/dev/psaux"
    Option          "Protocol"              "auto-dev"
    Option          "HorizScrollDelta"      "0"
    Option          "SHMConfig"             "on"
    # Do you keep moving the mouse while typing? Try this trick.
    #synclient TouchpadOff=1 disable your synaptics touchpad
    #synclient TouchpadOff=0 enable your synaptics touchpad
EndSection


Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"
    
    Option	"AutoRepeat"	"500 5"
    Option      "XkbModel"      "pc105"
    Option	"XkbLayout"	"us"
    Option      "XkbRules"      "xorg"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"

    Option	"Device"	"/dev/psaux"
    Option	"Protocol"	"ImPS/2"
    Option "ZAxisMapping" "4 5"
     
EndSection

Section "InputDevice"
    Identifier	"Mouse2"
    Driver	"mouse"
    Option	"Protocol"	"ImPS/2"
    Option	"Device"	"/dev/input/mice"
    Option 	"ZAxisMapping" "4 5"
EndSection


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

# Any number of monitor sections may be present

Section "Monitor"

    Identifier	"Generic Monitor"
    #Option      "DPMS"

    VertRefresh	50 - 75        # multisync
    HorizSync	28 - 110
	
    ModeLine "1280x800" 83.91 1280 1312 1624 1656 800 816 824 841
    ModeLine "1600x900" 173.86 1600 1672 2032 2176 900 902 914 940 +hsync +vsync    
    Modeline "1280x720" 75 1280 1336 1472 1664 720 725 730 751
    Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
    Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
    ModeLine "1366x768" 88.03 1366 1424 1680 1816 768 770 782 808
    ModeLine "848x480" 31.5 848 864 952 1056 480 481 484 497
    Modeline "720x576" 14.881 720 781 829 960 576 606 610 646 interlace +hsync +vsync
    ModeLine "856x480" 31.7 856 872 960 1064 480 481 484 497
    ModeLine "1024x512" 41.3 1024 1056 1160 1296 512 513 516 531
    ModeLine "960x600" 60 960 968 1048 1264 600 601 603 625 +HSync +VSync
    ModeLine "1088x612" 81.57 1088 1136 1376 1472 612 614 626 652 +hsync +vsync
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    Modeline "1280x768" 81.59 1280 1280 1384 1688 768 769 774 791 

EndSection

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

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA"
    Driver      "vesa" # do not remove vesa
EndSection


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

Section "Screen"

# The Identifier, Device and Monitor lines must be present

    Identifier	"Screen 1"
    Device	"VESA"
    Monitor	"Generic Monitor"
    #Option "AddARGBGLXVisuals" "true"

# The favoured Depth and/or Bpp may be specified here

    DefaultDepth 24

    SubSection "Display"
        Depth		8
        ViewPort	0 0
        Modes		"1024x768" "800x600" "640x480"
    EndSubsection

    SubSection "Display"
        Depth           16
        ViewPort        0 0
        Modes		"1024x768" "800x600" "640x480"
    EndSubsection

    SubSection "Display"
        Depth           24
        ViewPort        0 0
        Modes		"1024x768" "800x600" "640x480"
    EndSubsection


EndSection


Section "ServerLayout"
# The Identifier line must be present

    Identifier	"Main Layout"
    Screen 0 	"Screen 1"
    InputDevice	"Mouse1" "CorePointer"
    InputDevice	"Mouse2" "SendCoreEvents"
    InputDevice "Mouse3" "SendCoreEvents"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Section "DRI"
    Mode 0666
EndSection

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

Just remove the "#" to Option "AIGLX", Option "AddARGBGLXVisuals" and #Option "Composite". Then setup your resolution and your video driver.
Be sure to emerge aiglx-accelerator and beryl-wrapper.
If you use KDM (never tried with GDM), substitute ServerCmd=/usr/bin/X (or /usr/bin/Xgl if you used XGL) with ServerCmd=/usr/bin/AIGLX. Then fire up X.Org again and start /usr/bin/beryl-wrapper as user.

If you use KDE and KDM, just open /usr/kde/3.5/bin/kdm/Xsession and before the words "case $session in" add this line:

Code: Select all

/usr/bin/beryl-wrapper $DESKTOP_SESSION &

.

Be sure to add dbus session support to this file, or copy my Xsession:

Code: Select all

#! /bin/sh
# Xsession - run as user

session=$1

# Note that the respective logout scripts are not sourced.
case $SHELL in
  */bash)
    [ -z "$BASH" ] && exec $SHELL $0 "$@"
    set +o posix
    [ -f /etc/profile ] && . /etc/profile
    if [ -f $HOME/.bash_profile ]; then
      . $HOME/.bash_profile
    elif [ -f $HOME/.bash_login ]; then
      . $HOME/.bash_login
    elif [ -f $HOME/.profile ]; then
      . $HOME/.profile
    fi
    ;;
  */zsh)
    [ -z "$ZSH_NAME" ] && exec $SHELL $0 "$@"
    emulate -R zsh
    [ -d /etc/zsh ] && zdir=/etc/zsh || zdir=/etc
    zhome=${ZDOTDIR:-$HOME}
    # zshenv is always sourced automatically.
    [ -f $zdir/zprofile ] && . $zdir/zprofile
    [ -f $zhome/.zprofile ] && . $zhome/.zprofile
    [ -f $zdir/zlogin ] && . $zdir/zlogin
    [ -f $zhome/.zlogin ] && . $zhome/.zlogin
    ;;
  */csh|*/tcsh)
    # [t]cshrc is always sourced automatically.
    # Note that sourcing csh.login after .cshrc is non-standard.
    xsess_tmp=`mktemp`
    $SHELL -c "if (-f /etc/csh.login) source /etc/csh.login; if (-f ~/.login) source ~/.login; /bin/sh -c export > $xsess_tmp"
    . $xsess_tmp
    rm -f $xsess_tmp
    ;;
  *) # Plain sh, ksh, and anything we don't know.
    [ -f /etc/profile ] && . /etc/profile
    [ -f $HOME/.profile ] && . $HOME/.profile
    ;;
esac

[ -f /etc/xprofile ] && . /etc/xprofile
[ -f $HOME/.xprofile ] && . $HOME/.xprofile

# launches a session dbus instance

dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
  eval `$dbuslaunch --sh-syntax --exit-with-session`
  export DBUS_SESSION_BUS_ADDRESS
  export DBUS_SESSION_BUS_PID
fi

/usr/bin/beryl-wrapper $DESKTOP_SESSION &

case $session in
  "")
    exec xmessage -center -buttons OK:0 -default OK "Sorry, $DESKTOP_SESSION is no valid session."
    ;;
  failsafe)
    exec xterm -geometry 80x24-0-0
    ;;
  custom)
    exec $HOME/.xsession
    ;;
  default)
    exec /usr/kde/3.5/bin/startkde
    ;;
  *)
    eval exec "$session"
    ;;
esac
exec xmessage -center -buttons OK:0 -default OK "Sorry, cannot execute $session. Check $DESKTOP_SESSION.desktop."

[sleipner]

i made ebuilds for beryl. link removed
and my launch script:

Code: Select all

#!/bin/sh
X :1 -nolisten tcp -ac -audit 0 -br & xpid=$!

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
    eval `dbus-launch --sh-syntax --exit-with-session`
fi

export DISPLAY=:1
export __GL_YIELD="NOTHING"
xfce-mcs-manager &
xftaskbar4 &
xfdesktop &
beryl-manager &
xfce4-panel

#xterm
killall dbus-daemon
kill $xpid

seems to work okay here.. bit slow though..

[Matteo Azzali]

i made ebuilds for beryl. ......
......
seems to work okay here.. bit slow though..

Ehm, please read Request to not ebuild Beryl until is released ,
and IF your version is slow expecially when having some cpu-high-load task running,
please read above about how to patch xorg-server for aiglx scheduling issue
(this patch is taken from XGL code so should be safe , another way is to use aiglx-accelerator from sabayonlinux overlay)

@UB|K: at the moment beryl is not ready for the masses, that's why the developers asked to not ebuild it....

[pussi]

I dunno if anyone has mentioned this before but they are in portage now (hard masked of course)

[Matteo Azzali]

Just a note: both beryl ebuild mentioned here are missing the gnome dependancies
(that are required for non-gnome users : kde-enlightenment-fluxbox,etc.etc.) .CARE!

EDIT: at least libwnck is required to compile emerald (needs to be in DEPEND ).

[sleipner]

Ehm, please read Request to not ebuild Beryl until is released

ok.. removed link. don't really see whats the idea not releasing ebuilds though..

[Matteo Azzali]

Ehm, please read Request to not ebuild Beryl until is released

ok.. removed link. don't really see whats the idea not releasing ebuilds though..

They are moving things fast so they would like only experienced users try the pre-release code.
So unexperienced users will not create huge amount of unneeded bugreports/complaints.

[baigsabeeh]

Well, I'm getting a stupid x11-drivers syntax error when I try to digest it. What to do about this?

[The_Oak]

I also got nvidia beta driver working fine with texture from pixmap support. Compiz runs smoothly, however, MPlayer doesn't play videos full screen anymore. They just freeze when maximized to full screen though they appear to be moving while spinning the cube. Anyone else had similar kinds of problems and perhaps a solution?

[onlinepancakes]

I also got nvidia beta driver working fine with texture from pixmap support. Compiz runs smoothly, however, MPlayer doesn't play videos full screen anymore. They just freeze when maximized to full screen though they appear to be moving while spinning the cube. Anyone else had similar kinds of problems and perhaps a solution?

I had a similar issues with Xine and Mplayer doing that a couple of weeks ago with the 8774 drivers. All I had to do was reemerge them with USE flag set to nvidia and now they work perfectly fine at full screen..

[Matteo Azzali]

I also got nvidia beta driver working fine with texture from pixmap support. Compiz runs smoothly, however, MPlayer doesn't play videos full screen anymore. They just freeze when maximized to full screen though they appear to be moving while spinning the cube. Anyone else had similar kinds of problems and perhaps a solution?

They freeze or they pause? Go in general options and try to change state to "Unredirect Fullscreen Windows".

[Tonglebeak]

Nice to see everyone else is fine :S

I get the "unknown gpu" error when trying to start xdm, had to downgrade back to 8774 (I have a 6600gt).

Anyone know what would cause the unknown gpu error?

EDIT: Nvm, guess it would help if I actually had the correct kernel loaded (and here I thought I had cp'd that bzImage a couple weeks ago >_>)

[onlinepancakes]

Does the new beta drivers come with the new Nvidia-Settings or are you stuck with the old one in portage?

[sleipner]

Does the new beta drivers come with the new Nvidia-Settings or are you stuck with the old one in portage?

yes nvidia-settings comes with beta drivers but ebuild doesn't install it cause its provided by nvidia-settings ebuild..

[Matteo Azzali]

Does the new beta drivers come with the new Nvidia-Settings or are you stuck with the old one in portage?

we are stuck,for now. the package of the sources should be the 1.0 at the real src_uri, a mirror
is needed to ebuild it.

[lucida]

I dont know why all recent nvidia-drivers ebuilds strip the nvidia-settings program...totally nonsense.

Anyway, just extract the binary driver package and get it.

[capkanada]

I just have a single question to ask..

Have any brave souls tried any of this with Gnome 2.16's compositor-enabled Metacity?

Just wondering. If it works...well...compiz/beryl is nice and all, but...well...knowing this would be nice. ...And knowing is half the battle!

...Or something like that.

--CK

[sylware]

I just have a single question to ask..

Have any brave souls tried any of this with Gnome 2.16's compositor-enabled Metacity?

Just wondering. If it works...well...compiz/beryl is nice and all, but...well...knowing this would be nice. ...And knowing is half the battle!

...Or something like that.

--CK

I created an overlay with a metacity with its compositor enabled. Then the build asks for libcm which I got from gnome CVS. Unfortunately, I was unable to compile libcm due to missing functions in nvidia glx header (maybe they are missing short).

[sanmartin]

Someone on the forum a few months ago said that the libcm compile problem was because libcm required a cvs version of Mesa to build. I think a new version of Mesa has been released since then, but maybe give it a shot? I'm pretty sure the xgl-coffee overlay has a cvs ebuild in it. note: i'm trying to do this myself in my spare time but I haven't got it yet either.