| View previous topic :: View next topic |
| Author |
Message |
mody
Apprentice
Joined: 01 Oct 2004
Posts: 176
|
 Posted: Wed Jan 10, 2007 10:16 am Post subject: X11 resets when I switch terminals. |
 |
|
Hi,
My x11 resets when I switch terminals with ALT+Function keys and gets back to gdm. I looked a bit for any similar problems but didnt come up with anything.
My kernel version is linux-2.6.18-gentoo-r6
I've selected as modules the intel drives.
lspci | grep VGA: | Code: | | Intel Corporation 82865G Integrated Graphics Controller (rev 02) |
Heres my xorg.conf: | Code: | # 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/TTF/"
# FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
# 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" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
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
# 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 "My Monitor"
# 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 31.5 - 48.5
# 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 50-70
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 "** Intel i810 (generic) [i810]"
Driver "i810"
# Driver "i915"
VideoRam 8192
# Insert Clocks lines here if appropriate
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 "** Intel i810 (generic) [i810]"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "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"
EndSection
Section "DRI"
Mode 0666
EndSection
|
|
|
| Back to top |
|
 |
nightshade2069
Tux's lil' helper
Joined: 08 Dec 2006
Posts: 140
|
| Posted: Wed Jan 10, 2007 7:18 pm Post subject: |
|
|
| I noticed you are using a generic Video driver. Try running xorgconfig and select the correct driver for your video card. or you can use the ' vesa ' drivers which should work. I use those drivers on 3 systems right now and no problem with the gdm |
|
| Back to top |
|
|
mody
Apprentice
Joined: 01 Oct 2004
Posts: 176
|
| Posted: Thu Jan 11, 2007 2:44 am Post subject: |
|
|
| nightshade2069 wrote: | | I noticed you are using a generic Video driver. Try running xorgconfig and select the correct driver for your video card. or you can use the ' vesa ' drivers which should work. I use those drivers on 3 systems right now and no problem with the gdm |
Hi that 'vga' is just another profile.
I'm using the i810 dirver:
| Code: | Section "Screen"
Identifier "Screen 1"
Device "** Intel i810 (generic) [i810]"
Monitor "My Monitor"
DefaultDepth 24 |
I've got hardware acceleration working.
But when I switch terminals the GUI Screens reset X server causing gdm to reload.
I'm not sure what I've done wrong. |
|
| Back to top |
|
|
kraix
Tux's lil' helper
Joined: 20 Jun 2005
Posts: 93
|
| Posted: Thu Jan 11, 2007 3:14 am Post subject: |
|
|
| have you tried this with the xdm login manager? |
|
| Back to top |
|
|
mody
Apprentice
Joined: 01 Oct 2004
Posts: 176
|
| Posted: Thu Jan 11, 2007 4:21 pm Post subject: |
|
|
| kraix wrote: | | have you tried this with the xdm login manager? |
I havent, good point, will try it first thing in the morning,
Thanks. |
|
| Back to top |
|
|
PCnity
n00b
Joined: 23 Dec 2005
Posts: 41
|
| Posted: Sat Jan 20, 2007 11:17 pm Post subject: |
|
|
I have the same problem.
If i switch to some console from the desktop for just a short time [5s] and back to VTY7 nothing happens. But if i switch to a console for some longer time, the GDM login screen apears, it takes the focus. I mean that i can be writing something in MC but "it switches to vty7" and there i see the login screen.
If I login back the session is lost. All applications restarts.
I am using XGL, Beryl & GDM. |
|
| Back to top |
|
|
Mgiese
Veteran
Joined: 23 Mar 2005
Posts: 1610
Location: indiana
|
| Posted: Sun Jan 21, 2007 12:48 pm Post subject: |
|
|
| PCnity wrote: | I have the same problem.
If i switch to some console from the desktop for just a short time [5s] and back to VTY7 nothing happens. But if i switch to a console for some longer time, the GDM login screen apears, it takes the focus. I mean that i can be writing something in MC but "it switches to vty7" and there i see the login screen.
If I login back the session is lost. All applications restarts.
I am using XGL, Beryl & GDM. |
nearly same problem here: beryl works (3d cube ect)
but when i switch to console (alt-strg-f1 as example) and then go back to F7 i just have a blank screen  everthing else seems to work
_________________
I do not have a Superman complex, for I am God not Superman 
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
| Back to top |
|
|
PCnity
n00b
Joined: 23 Dec 2005
Posts: 41
|
| Posted: Sun Jan 21, 2007 1:37 pm Post subject: |
|
|
| Mgiese wrote: | | PCnity wrote: | I have the same problem.
If i switch to some console from the desktop for just a short time [5s] and back to VTY7 nothing happens. But if i switch to a console for some longer time, the GDM login screen apears, it takes the focus. I mean that i can be writing something in MC but "it switches to vty7" and there i see the login screen.
If I login back the session is lost. All applications restarts.
I am using XGL, Beryl & GDM. |
nearly same problem here: beryl works (3d cube ect)
but when i switch to console (alt-strg-f1 as example) and then go back to F7 i just have a blank screen everthing else seems to work |
Yes I also know this... It happens when the system is under heavy load. The solution is to kill emerald from the console, it starts automaticly and everything is OK.
My problem:
I raised the crash time limit of GDM to 60s (GdmXserverTimeout=60), but still no good result.
I saw now some strange things... My GAIM was running and amarok playing music; i switched to vty1; after a while [10 - 20s] the music stopped playing and the screen switched automaticly to vty7 where the f**** gdmgreeter wanted me to log in. Someone sent me an ICQ message AND it was blinking over the greetrer. When i clicked on it, i saw it normally, but i can't move the GAIM window... Like there was no window manager. It was strange i also had that feeling there is my desktop blinking from behind for a very very short time.
I think it is also something with the window manager... All the programs are running.
I will do some experimenting... BUT i am a Linux newb... Is there someone who has some idea? Where to start?
I will just try to AUDIT my XGL & Beryl installation, read all related conf. files a try to find that f**** error. |
|
| Back to top |
|
|
Mgiese
Veteran
Joined: 23 Mar 2005
Posts: 1610
Location: indiana
|
| Posted: Sun Jan 21, 2007 5:17 pm Post subject: |
|
|
| PCnity wrote: | | Mgiese wrote: | | PCnity wrote: | I have the same problem.
If i switch to some console from the desktop for just a short time [5s] and back to VTY7 nothing happens. But if i switch to a console for some longer time, the GDM login screen apears, it takes the focus. I mean that i can be writing something in MC but "it switches to vty7" and there i see the login screen.
If I login back the session is lost. All applications restarts.
I am using XGL, Beryl & GDM. |
nearly same problem here: beryl works (3d cube ect)
but when i switch to console (alt-strg-f1 as example) and then go back to F7 i just have a blank screen everthing else seems to work |
Yes I also know this... It happens when the system is under heavy load. The solution is to kill emerald from the console, it starts automaticly and everything is OK.
|
at first dont use the f word, it does not look that your quiete professional 
and then for me it wasnt a problem of heavy system load i just did the follwing | Code: | | in beryl settings manager uncheck sync to vblank which is under general options, also turn off detect refresh rate and set the refresh rate to 200 under numerical values for best performance. |
have fun
_________________
I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
| Back to top |
|
|
PCnity
n00b
Joined: 23 Dec 2005
Posts: 41
|
| Posted: Sun Jan 21, 2007 8:26 pm Post subject: |
|
|
Testing... Edit in 10min.
Still the same problem. |
|
| Back to top |
|
|
di1337
n00b
Joined: 17 Nov 2005
Posts: 16
|
| Posted: Tue Nov 20, 2007 7:30 pm Post subject: |
|
|
Hi,
About 1,5 months ago my laptop started to have this problem.
Did this error ever get resolved? I'm having the exact same problem, and I don't seem to find any information about it everywhere. To reiterate:
-I log on to an X server.
-I log on to a second session or a vty.
-I do a bit of work, wait a few minutes. (otherwise it does not happen)
-I switch back to the first X session, but this crashes, I see vty1 for a moment, and then gdm reinitializes the first X display. So, I see a gdm login screen instead of my session.
I'm trying to locate the problem for a long time now. At first i thought gdm was causing problems, but even startx sessions suffer from it, so gdm probably has nothing to do with it. I also suspected gnome-screensaver and xscreensaver, but even without these the bug still occured.
Today I tried the vesa driver instead of the I810 driver. This resolves the problem, but this isn't ideal, since I don't have access to DRI anymore.
Does anyone have a solution? Thanks! |
|
| Back to top |
|
|
|
|
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
|
|
Desktop Environments
