Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xorg hangs on logout with fglrx and X800
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Fri Mar 24, 2006 9:23 pm    Post subject: Xorg hangs on logout with fglrx and X800 Reply with quote

xorg.conf:
Code:
Section "DRI"
   Mode 0666
EndSection

Section "ServerLayout"

# The Identifier line must be present
# 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.
# 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
EndSection

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.
#    RgbPath    "/usr/share/X11/rgb"
# 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/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.
#    ModulePath "/usr/lib/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"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
#    Load        "type1"
#    Load        "speedo"
# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
#    Load       "dri"
        Load  "dbe"     # Double buffer extension
        SubSection "extmod"
                Option      "omit xfree86-dga"   # don't initialise the DGA extension
        EndSubSection
        Load  "freetype"
#    Load        "xtt"
        Load  "dri"
        Load  "glx"
EndSection

Section "InputDevice"

# 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     "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"
        Identifier  "Keyboard1"
        Driver      "kbd"
        Option      "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
        Option      "XkbRules" "xorg"
        Option      "XkbModel" "microsoft"
        Option      "XkbLayout" "us"
EndSection

Section "InputDevice"

# Identifier and driver
# 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.
# 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"
        Identifier  "Mouse1"
        Driver      "mouse"
        Option      "Protocol" "Auto"   # Auto detect
        Option      "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
        Option      "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection

Section "Monitor"
        Identifier   "LCD"
        HorizSync       31.5 - 64.3
        VertRefresh     60.0 - 75.0
EndSection

Section "Device"
        Identifier  "X800 GTO2"
        Driver      "fglrx"
        BusID       "PCI:5:0:0"
EndSection

Section "Screen"
        Identifier "Screen 1"
        Device     "X800 GTO2"
        Monitor    "LCD"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection


DRI/Direct Rendering works. No problems there.

I'm using xorg-x11-7.0-r1, and ati-drivers-8.23.7. Also, my graphics card is a Sapphire X800 GTO2 softmodded to 16 pipes.

Xorg.0.log shows the card as:
Code:
(--) Chipset RADEON X850 PRO (R480 5D4F) found


Thanks
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Sat Mar 25, 2006 12:39 am    Post subject: Reply with quote

Bump;

Tell me what info is needed to solve this problem.
Back to top
View user's profile Send private message
killomatic
n00b
n00b


Joined: 17 Mar 2006
Posts: 38

PostPosted: Sat Mar 25, 2006 7:57 am    Post subject: Reply with quote

I had this problem with fglrx on amd64, and I had to do two things to fix it:
First, if you use gdm, add
AlwaysRestartServer=true
to your gdm.conf, or with kdm, add to kdmrc
TerminateServer=true


Secondly, unmask the unstable ati drivers in your package.keywords, and emerge them. This is a bug that seems to be fixed in the most recent version.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Sat Mar 25, 2006 4:07 pm    Post subject: Reply with quote

Thanks.

I've already using the newest drivers (unmasked), and I'm not running gdm/kdm. Someone on IRC suggested it was a problem with the drivers themselves. Is there a change that downgrading the drivers might help. BTW, the card I have is PCIe and not AGP.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Sat Mar 25, 2006 5:15 pm    Post subject: Reply with quote

I downgraded the drivers from 8.23.7 to 8.22.5 with no luck. Exact same thing happens. I'm running gentoo-sources-2.6.15-r7. What are the chances that downgrading the kernel would fix the problem?
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Mon Mar 27, 2006 1:15 am    Post subject: Reply with quote

Anyone interested in helping get to the root of this problem? I'm sure someone else has to be having it too.
Back to top
View user's profile Send private message
Admiral_Trigger_Happy
Guru
Guru


Joined: 05 Sep 2004
Posts: 337
Location: Australia

PostPosted: Mon Mar 27, 2006 1:21 am    Post subject: Reply with quote

There is a bug with the fglrx driver and the 2.6.15 kernel, that causes this.

I you downgrade your kernel to 2.6.14 it should be fine
_________________
Admiral Trigger Happy
-------------------------------
www.kiba-dock.org
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Mon Mar 27, 2006 2:37 am    Post subject: Reply with quote

I downgraded to 2.6.14-gentoo-r7. No luck.

I would try 2.6.13 but the ebuilds for gentoo-sources of these versions have already been removed.
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Mon Mar 27, 2006 9:06 am    Post subject: Reply with quote

I have the X700 card, and am seeing the same issues. I have found so far that the only kernel/driver combination that works for me is 2.6.14-gentoo-r7 and ati-drivers 8.14.13-r3.

Can you try this to confirm?

Cheers,
Andrew
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Mon Mar 27, 2006 9:10 pm    Post subject: Reply with quote

I tried that exact combination without success. fglrx refused to load with an error about ioctl32. I thought this was fixed. There is a patch for it in place. :?

I'm going to try 2.6.16 and 8.23.7.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Mon Mar 27, 2006 9:17 pm    Post subject: Reply with quote

I've just tried 2.6.16-gentoo and 8.23.7 (with patches for 2.6.16 from portage). Problem of a different kind surfaces.

glxinfo/fglrxinfo both return:
Code:
name of display: :0.0
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  143 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Serial number of failed request:  19
  Current serial number in output stream:  20


dmesg reveals:
Code:
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 1884 MBytes.
ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 50
[fglrx] module loaded - fglrx 8.23.7 [Mar  6 2006] on minor 0
NTFS volume version 3.1.
NTFS volume version 3.1.
[fglrx] free  PCIe = 51118080
[fglrx] max   PCIe = 51118080
[fglrx] free  LFB = 116322304
[fglrx] max   LFB = 116322304
[fglrx] free  Inv = 134217728
[fglrx] max   Inv = 134217728
[fglrx] total Inv = 134217728
[fglrx] total TIM = 0
[fglrx] total FB  = 0
[fglrx] total PCIe = 16384


I believe we can safely say that these do not work together. glxgears won't even run.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Mon Mar 27, 2006 9:36 pm    Post subject: Reply with quote

When using any of the 8.14.13 versions from portage (with the ioctl patches) I get the following upon modprobe:
Code:
fglrx: Unknown symbol verify_area
fglrx: Unknown symbol register_ioctl32_conversion
fglrx: Unknown symbol unregister_ioctl32_conversion
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Tue Mar 28, 2006 3:25 am    Post subject: Reply with quote

Can anyone else confirm that the ioctl patch for 8.14.13 isn't applied correctly? Could someone fix this?
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Tue Mar 28, 2006 5:38 am    Post subject: Reply with quote

Like I say, 8.14.13 works perfectly for me with a 2.6.14 kernel. It doesn't work for me with 2.6.15 (although I'm pretty sure it's not due to the ioctl problem), and I haven't tried it with 2.6.16 yet.

Andrew
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Tue Mar 28, 2006 7:47 am    Post subject: Reply with quote

Been testing suspend2-sources-2.6.15-r8 and ati-drivers-8.21.7-r1 with AlwaysRestartServer=true set in gdm.conf for a few days and had no problems yet.

Andrew
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Wed Mar 29, 2006 12:08 am    Post subject: Reply with quote

Are you running an x86 or x86_64 system?
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Wed Mar 29, 2006 5:25 am    Post subject: Reply with quote

|mattst88| wrote:
Are you running an x86 or x86_64 system?


x86

Gentoo Linux 2.6.15-suspend2-r8 i686 Mobile AMD Sempron(tm) Processor 3000+
Back to top
View user's profile Send private message
Zimyc
n00b
n00b


Joined: 06 Mar 2006
Posts: 6

PostPosted: Wed Mar 29, 2006 9:08 am    Post subject: Reply with quote

I've had this problem for a long time, but i finally fixed it by loading the correct agp module, i was loading the ati-agp module when i had an intel motherboard, but when i recompiled the kernel with the intel-agp, and loaded that instead, it worked fine.

But you have a PCIe card though, so i don't know.
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Wed Mar 29, 2006 10:13 am    Post subject: Reply with quote

Yep, mine is a PCIe card too, so that won't help. But as I said, the latest *stable* ati-drivers and the AlwaysRestartServer setting seem to be working well for me. Might try the latest unstable drivers later today to see if the problem comes back.

Cheers,
Andrew
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Wed Mar 29, 2006 7:22 pm    Post subject: Reply with quote

I think the problem might be more complex than I originally thought. I'm going to assume you are using vesafb-tng. This isn't available on AMD64 which only leaves vesafb for us ATI users. According to Documentation/fb/vesa.txt:

Quote:
The X-Server must restore the video mode correctly, or else you end up
with a broken console (and vesafb cannot do anything about this).
With vesafb-tng chances are that the console will be restored properly
even if the X server messes up the video mode.


Also:
Quote:
The VESA framebuffer driver comes in two flavors - the standard 'vesafb'
and 'vesafb-tng'. Vesafb-tng is available only on 32-bit x86 due to the
technology it uses (vm86). Vesafb-tng has more features than vesafb
(adjusting the refresh rate on VBE3.0-compliant boards, switching the
video mode without rebooting
, selecting a mode by providing its
modedb name, and more).


I'll go explore this further.
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Wed Mar 29, 2006 7:36 pm    Post subject: Reply with quote

|mattst88| wrote:
I think the problem might be more complex than I originally thought. I'm going to assume you are using vesafb-tng. This isn't available on AMD64 which only leaves vesafb for us ATI users.


Nope, I am using vesafb too. My ATI card didn't like vesafb-tng either, and my laptop wouldn't boot.

Currently running the unstable ati-drivers and AlwaysRestartServer=true with no problems as yet...

Cheers,
Andrew
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Fri Mar 31, 2006 8:54 pm    Post subject: Reply with quote

I must have tried everything by now. I've downgraded the kernel to 2.6.12.5, tried 8.14.13, 8.18.*, 8.20.*, 8.23.7, etc. I've recompiled x11-drm, xorg-server, mesa, and anything else related. Still crashes on logout or switching to a VT.

Btw, where is gdm.conf? /etc/X11/gdm contains no *.conf files but custom.conf. I tried symlinking gdm.conf to it, but it didn't change anything.

With the combination of 2.6.12.5, xorg-7, and 8.14.13-r3, upon startx is reports that fglrx has a version mismatch or something similar and that it was unable to locate and load glx. Could someone point me in the right direction?
Back to top
View user's profile Send private message
acturneruk
Apprentice
Apprentice


Joined: 06 Feb 2005
Posts: 162
Location: UK

PostPosted: Sat Apr 01, 2006 6:41 am    Post subject: Reply with quote

Code:
andrew@tranquillity ~ $ locate gdm.conf
/etc/X11/gdm/gdm.conf
/etc/X11/gdm/factory-gdm.conf
/etc/X11/gdm/gdm.conf~


My gdm.conf:-

Code:
# GDM Configuration file.  You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand.  Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about.  Rest is for special setups and distro specific
# tweaks.  If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
#   kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
#
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
#
# For full reference documentation see the gnome help browser under
# GNOME|System category.  You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
#
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line.  The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
#
# Have fun! - George

[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=

# Timed login, useful for kiosks.  Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30

# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/usr/sbin/gdmsetup --disable-sound --disable-crash-dialog

# The chooser program.  Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/usr/libexec/gdmchooser

# The greeter for local (non-xdmcp) logins.  Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
Greeter=/usr/libexec/gdmgreeter

# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/usr/libexec/gdmlogin

# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libdwellmouselistener:/usr/lib/gtk-2.0/modules/libkeymouselistener

# Default path to set.  The profile scripts will likely override this
#DefaultPath=/bin:/usr/bin:/usr/bin
# Default path for root.  The profile scripts will likely override this
#RootPath=/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin

# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
AlwaysRestartServer=true

# User and group used for running gdm GUI applicaitons.  By default this
# is set to user gdm and group gdm.  This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=gdm
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
#KillInitClients=true
LogDir=/var/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/etc/X11/gdm/PostLogin/
PreSessionScriptDir=/etc/X11/gdm/PreSession/
PostSessionScriptDir=/etc/X11/gdm/PostSession/
DisplayInitDir=/etc/X11/gdm/Init
# Distributions:  If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
#FailsafeXServer=
# if X keeps crashing on us we run this script.  The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/etc/X11/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
#RebootCommand=/usr/bin/reboot;/sbin/reboot;/sbin/shutdown -r now;/usr/sbin/shutdown -r now
#HaltCommand=/usr/bin/poweroff;/sbin/poweroff;/sbin/shutdown -h now;/usr/sbin/shutdown -h now
#SuspendCommand=
# Probably should not touch the below this is the standard setup
ServAuthDir=/var/gdm
# This is our standard startup script.  A bit different from a normal
# X session, but it shares a lot of stuff with that.  See the provided
# default for more information.
BaseXsession=/etc/X11/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM.  Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
#SessionDesktopDir=/etc/X11/sessions/:/etc/X11/dm/Sessions/:/usr/share/gdm/BuiltInSessions/:/usr/share/xsessions/
# This is the default .desktop session.  One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used.  You can use syntax ~/ below
# to indicate home directory of the user.  You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories.  Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/bin/X
# The maximum number of flexible X servers to run.
#FlexibleXServers=5
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on.  Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=5
# the X nest command
Xnest=/usr/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation.  Right now only works on Linux.  This way
# we force X to use specific vts.  turn VTAllocation to false if this
# is causing problems.
#FirstVT=7
#VTAllocation=true
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true

# If true then the last login information is printed to the user before
# being prompted for password.  While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false

# Program used to play sounds.  Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play

# These are the languages that the console cannot handle because of font
# issues.  Here we mean the text console, not X.  This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh

# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false

# This determines whether gdm will send notifications to the console
#ConsoleNotify=true

[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=true
# If you want to be paranoid, turn this one off
AllowRemoteRoot=true
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user.  Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# Maximum size of a file we wish to read.  This makes it hard for a user to DoS
# us by using a large file.
#UserMaxFile=65536
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server).  It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
#DisallowTCP=true
# By default never place cookies if we "detect" NFS.  We detect NFS
# by detecting "root-squashing".  It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default.  Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true

# XDMCP is the protocol that allows remote login.  If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that).  You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser.  Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off.  It is never a safe thing to leave
# out on the net.  Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host.  Otherwise we just log the user in locally.
#HonorIndirect=true
# Maximum pending requests
#MaxPending=4
#MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
#MaxSessions=16
# Maximum wait times
#MaxWait=15
#MaxWaitIndirect=15
# How many times can a person log in from a single host.  Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host.  This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
#DisplaysPerHost=2
# The number of seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# The port.  177 is the standard port so better keep it that way
#Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id.  But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it.  You could for example send load,
# or mail details for some user, or some such.
#Willing=/etc/X11/gdm/Xwilling

[gui]
# The specific gtkrc file we use.  It should be the full path to the gtkrc
# that we need.  Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/usr/share/themes/Default/gtk-2.0/gtkrc

# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter.  Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow.  These must be the names of the
# themes installed in the standard locations for gtk themes.  You can
# also specify 'all' to allow all installed themes.  These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all

# Maximum size of an icon, larger icons are scaled down
#MaxIconWidth=128
#MaxIconHeight=128

[greeter]
# Greeter has a nice title bar that the user can move
#TitleBar=true
# Configuration is available from the system menu of the greeter
#ConfigAvailable=true
# Face browser is enabled.  This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=false
# The default picture in the browser
#DefaultFace=/usr/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login.  Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login.  Excluded
# users will still be able to log in, but will have to type their
# username.  Users should be separated by commas. 
#Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,gdm,postgres,pvm,rpm,nfsnobody,pcap
# By default, an empty include list means display no users.  By setting
# IncludeAll to true, the password file will be scanned and all users
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID.  Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments.  The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
IncludeAll=true
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/usr/share/pixmaps/faces/
# File which contains the locale we show to the user.  Likely you want to use
# the one shipped with gdm and edit it.  It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
#LocaleFile=/etc/X11/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/usr/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password.  Kind of cool looking
#Quiver=true
# The Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser.  None of
# these is available if this is off.  They can be turned off individually
# however
#SystemMenu=true
# Should the chooser button be shown.  If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host.  Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language.  Note that %n gets
# translated to the hostname of the machine.  These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 Note to distributors, if you
# wish to have a different Welcome string and wish to have this
# translated you can have entries such as "Welcome[cs]=Vitejte na %n".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=Welcome to %n
# Don't allow user to move the standard greeter window.  Only makes sense
# if TitleBar is on
#LockPosition=false
# Set a position rather then just centering the window.  If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
#SetPosition=false
#PositionX=0
#PositionY=0
# Xinerama screen we use to display the greeter on.  Not for true
# multihead, currently only works for Xinerama.
#XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
#BackgroundType=2
#BackgroundImage=
#BackgroundScaleToFit=true
#BackgroundColor=#76848F
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
#BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter.  Perhaps
# something like an xscreensaver hack or some such.
#BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
#RunBackgroundProgramAlways=false
# Show the Failsafe sessions.  These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
#ShowGnomeFailsafeSession=true
#ShowXtermFailsafeSession=true
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used.  If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field.  Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter.  Circles is the standard
# shipped theme.  If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true.  Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
GraphicalTheme=AproachOne
#GraphicalThemes=circles/:happygnome
GraphicalThemes=circles
GraphicalThemeDir=/usr/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input.  If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=

# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/usr/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/usr/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course).  You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=true

[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog.  However it
# can be useful in determining when something is going very wrong.
Enable=false

[servers]
# These are the standard servers.  You can add as many you want here
# and they will always be started.  Each line must start with a unique
# number and that will be the display number of that server.  Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux and freebsd.
# Don't add any vt<number> arguments if VTAllocation is on, and set FirstVT to
# be the first vt available that your gettys don't grab (gettys are usually
# dumb and grab even a vt that has already been taken).  Using 7 will work
# pretty much for all linux distributions.  VTAllocation is not currently
# implemented on anything but linux and freebsd.  Feel free to send patches.
# X servers will just not get any extra arguments then.
#
# If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname
#
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser

## Note:
# is your X server not listening to TCP requests?  Perhaps you should look
# at the security/DisallowTCP setting!

# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/bin/X -audit 0
flexible=true

# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/bin/X -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing).  You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false

# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true.  This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter.  When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 422

PostPosted: Sat Apr 01, 2006 10:16 pm    Post subject: Reply with quote

Thanks for your replies. I tried your gdm.conf, still no luck.

I think the problem has to do with ati-drivers and amd64. :(
Back to top
View user's profile Send private message
Pitr-
n00b
n00b


Joined: 15 May 2003
Posts: 18
Location: Sweden

PostPosted: Tue Apr 04, 2006 8:38 pm    Post subject: Reply with quote

And just by making x11 restart if you try to exit isn't really a solution. You'll only make it more troublesome to get out to the console and you'll still end up with a "blackscreen of no visuals" if you try.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum