[gentoo-user] Help me reboot X

[gentoo-user] Help me reboot X

[Kevin O'Gorman]

>From time to time my X server will lock up, usually but not always
while I'm editing something in ooffice.  It's always something that's
pretty heavily graphical.  When this happens, the only thing that
still works on my desktop is mouse motion.  No clicks actually
register, and even the three-finger salutes (BS and DEL) are feckless.

However, I can SSH into the machine from elsewhere and pretty much do
anything else I want.  I usually have to reboot the machine, because I
haven't figured out how to restart X in gentoo.  I'm sure it's pretty
simple, but I can't seem to find documentation on this particular
thing and it's not like the usual init.d services.  Lots on startup, a
bit on shutdown, but nothing I see is about restart.

When this happens, sometimes X is using 100% of one of the CPU's, but
I don't always check and haven't recently verified my impression that
sometimes all CPU's are at an idle (I have 4 hyperthreads).

Can somebody help me stop and restart X?  I'm using kdm for login.

-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Stratos Psomadakis]

O/H Kevin O'Gorman έγραψε:
> From time to time my X server will lock up, usually but not always
> while I'm editing something in ooffice.  It's always something that's
> pretty heavily graphical.  When this happens, the only thing that
> still works on my desktop is mouse motion.  No clicks actually
> register, and even the three-finger salutes (BS and DEL) are feckless.
>
> However, I can SSH into the machine from elsewhere and pretty much do
> anything else I want.  I usually have to reboot the machine, because I
> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> simple, but I can't seem to find documentation on this particular
> thing and it's not like the usual init.d services.  Lots on startup, a
> bit on shutdown, but nothing I see is about restart.
>
> When this happens, sometimes X is using 100% of one of the CPU's, but
> I don't always check and haven't recently verified my impression that
> sometimes all CPU's are at an idle (I have 4 hyperthreads).
>
> Can somebody help me stop and restart X?  I'm using kdm for login.
>
maybe you can ssh to your machine and then:
ps -A | grep X
and see the pid of X...
and then kill [pid of X]...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]

Stratos Psomadakis wrote:
> O/H Kevin O'Gorman έγραψε:
>   
>> From time to time my X server will lock up, usually but not always
>> while I'm editing something in ooffice.  It's always something that's
>> pretty heavily graphical.  When this happens, the only thing that
>> still works on my desktop is mouse motion.  No clicks actually
>> register, and even the three-finger salutes (BS and DEL) are feckless.
>>
>> However, I can SSH into the machine from elsewhere and pretty much do
>> anything else I want.  I usually have to reboot the machine, because I
>> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
>> simple, but I can't seem to find documentation on this particular
>> thing and it's not like the usual init.d services.  Lots on startup, a
>> bit on shutdown, but nothing I see is about restart.
>>
>> When this happens, sometimes X is using 100% of one of the CPU's, but
>> I don't always check and haven't recently verified my impression that
>> sometimes all CPU's are at an idle (I have 4 hyperthreads).
>>
>> Can somebody help me stop and restart X?  I'm using kdm for login.
>>
>>     
> maybe you can ssh to your machine and then:
> ps -A | grep X
> and see the pid of X...
> and then kill [pid of X]...
>
>   

Or, you can do a /etc/init.d/xdm restart .  Either should work.

On another note, you may want to find out why it is locking up.  This
should not be happening.  Are you sure it is locked up or could it be
that what you are doing is just using all the CPU processes and it is to
busy to respond?

Maybe some serious guru will come in with a plan. 

Dale

:-)  :-)  :-)


-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.


[-- Attachment #2: Type: text/html, Size: 2325 bytes --]

Re: [gentoo-user] Help me reboot X

[deface]

[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]

' /etc/init.d/xdm restart '
This would restart your login manager, assuming your running one.  
(gdm/kdm/xdm/slim)

I would recommend on finding out the root of your X locking up,  
rather than actually trying to band-aid it.

deface

On Jun 3, 2007, at 8:22 PM, Dale wrote:

> Stratos Psomadakis wrote:
>> O/H Kevin O'Gorman έγραψε:
>>
>>> From time to time my X server will lock up, usually but not always
>>> while I'm editing something in ooffice.  It's always something  
>>> that's
>>> pretty heavily graphical.  When this happens, the only thing that
>>> still works on my desktop is mouse motion.  No clicks actually
>>> register, and even the three-finger salutes (BS and DEL) are  
>>> feckless.
>>>
>>> However, I can SSH into the machine from elsewhere and pretty  
>>> much do
>>> anything else I want.  I usually have to reboot the machine,  
>>> because I
>>> haven't figured out how to restart X in gentoo.  I'm sure it's  
>>> pretty
>>> simple, but I can't seem to find documentation on this particular
>>> thing and it's not like the usual init.d services.  Lots on  
>>> startup, a
>>> bit on shutdown, but nothing I see is about restart.
>>>
>>> When this happens, sometimes X is using 100% of one of the CPU's,  
>>> but
>>> I don't always check and haven't recently verified my impression  
>>> that
>>> sometimes all CPU's are at an idle (I have 4 hyperthreads).
>>>
>>> Can somebody help me stop and restart X?  I'm using kdm for login.
>>>
>>>
>> maybe you can ssh to your machine and then:
>> ps -A | grep X
>> and see the pid of X...
>> and then kill [pid of X]...
>>
>>
>
> Or, you can do a /etc/init.d/xdm restart .  Either should work.
>
> On another note, you may want to find out why it is locking up.   
> This should not be happening.  Are you sure it is locked up or  
> could it be that what you are doing is just using all the CPU  
> processes and it is to busy to respond?
>
> Maybe some serious guru will come in with a plan.
>
> Dale
>
> :-)  :-)  :-)
>
>
> -- 
> www.myspace.com/-remove-me-dalek1967
>
> Copy n paste then remove the -remove-me- part.


[-- Attachment #2: Type: text/html, Size: 2724 bytes --]

Re: [gentoo-user] Help me reboot X

[Dale]

deface wrote:
> ' /etc/init.d/xdm restart '
> This would restart your login manager, assuming your running one.
> (gdm/kdm/xdm/slim)
>
> I would recommend on finding out the root of your X locking up, rather
> than actually trying to band-aid it.
>
> deface
>
> On Jun 3, 2007, at 8:22 PM, Dale wrote:
>
>>
>> Or, you can do a /etc/init.d/xdm restart .  Either should work.
>>
>> On another note, you may want to find out why it is locking up.  This
>> should not be happening.  Are you sure it is locked up or could it be
>> that what you are doing is just using all the CPU processes and it is
>> to busy to respond?
>>
>> Maybe some serious guru will come in with a plan. 
>>
>> Dale
>>
>> :-)  :-)  :-)
>>
>>
>> -- 
>> www.myspace.com/-remove-me-dalek1967
>>
>> Copy n paste then remove the -remove-me- part.
>

If he does that, it will restart X.  I have also seen where a few others
made the suggestion too.  This has always worked for me at least.

Dale

:-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Kevin O'Gorman]

On 6/3/07, Dale <dalek@exceedtech.net> wrote:
> deface wrote:
> > ' /etc/init.d/xdm restart '
> > This would restart your login manager, assuming your running one.
> > (gdm/kdm/xdm/slim)
> >
> > I would recommend on finding out the root of your X locking up, rather
> > than actually trying to band-aid it.
> >
> > deface
> >
> > On Jun 3, 2007, at 8:22 PM, Dale wrote:
> >
> >>
> >> Or, you can do a /etc/init.d/xdm restart .  Either should work.
> >>
> >> On another note, you may want to find out why it is locking up.  This
> >> should not be happening.  Are you sure it is locked up or could it be
> >> that what you are doing is just using all the CPU processes and it is
> >> to busy to respond?
> >>
> >> Maybe some serious guru will come in with a plan.
> >>
> >> Dale
> >>
> >> :-)  :-)  :-)
> >>
> >>
> >> --
> >> www.myspace.com/-remove-me-dalek1967
> >>
> >> Copy n paste then remove the -remove-me- part.
> >
>
> If he does that, it will restart X.  I have also seen where a few others
> made the suggestion too.  This has always worked for me at least.
>
> Dale
>
> :-)  :-)  :-)
>
> --
> www.myspace.com/-remove-me-dalek1967
>
> Copy n paste then remove the -remove-me- part.
>
> --

Thanks for all the ideas.  I'll keep them handy for the next time (it
usually happens
about once or twice a month).

In the meanwhile, a couple of notes:
  1) Yes, it's REALLY locked up.  But there's always enough CPU left
for a non-X login from another machine.  It has to be another machine
because I can't even switch to a console terminal.
  2) I have no clue how to find out what's causing the lockup.  I'd
love to, because I usually lose a bunch of work in the crash.
  3) I don't see anything labeled "SysReq" on my keyboard, but it's
associated with the PrintScreen key on my wife's box.  Can I hope
alt-printscreen-K will work?  (I personally wonder about it since
_nothing_ else on the keyboard works, but maybe the kernel can see
it).

Again, thanks.  I'll say more when it happens again.

-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Guillermo A. Amaral]

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

On Sunday 03 June 2007 19:36, Kevin O'Gorman wrote:
> On 6/3/07, Dale <dalek@exceedtech.net> wrote:
> > deface wrote:
> > > ' /etc/init.d/xdm restart '
> > > This would restart your login manager, assuming your running one.
> > > (gdm/kdm/xdm/slim)
> > >
> > > I would recommend on finding out the root of your X locking up, rather
> > > than actually trying to band-aid it.
> > >
> > > deface
> > >
> > > On Jun 3, 2007, at 8:22 PM, Dale wrote:
> > >> Or, you can do a /etc/init.d/xdm restart .  Either should work.
> > >>
> > >> On another note, you may want to find out why it is locking up.  This
> > >> should not be happening.  Are you sure it is locked up or could it be
> > >> that what you are doing is just using all the CPU processes and it is
> > >> to busy to respond?
> > >>
> > >> Maybe some serious guru will come in with a plan.
> > >>
> > >> Dale
> > >>
> > >> :-)  :-)  :-)
> > >>
> > >> --
> > >> www.myspace.com/-remove-me-dalek1967
> > >>
> > >> Copy n paste then remove the -remove-me- part.
> >
> > If he does that, it will restart X.  I have also seen where a few others
> > made the suggestion too.  This has always worked for me at least.
> >
> > Dale
> >
> > :-)  :-)  :-)
> >
> > --
> > www.myspace.com/-remove-me-dalek1967
> >
> > Copy n paste then remove the -remove-me- part.
> >
> > --
>
> Thanks for all the ideas.  I'll keep them handy for the next time (it
> usually happens
> about once or twice a month).
>
> In the meanwhile, a couple of notes:
>   1) Yes, it's REALLY locked up.  But there's always enough CPU left
> for a non-X login from another machine.  It has to be another machine
> because I can't even switch to a console terminal.
>   2) I have no clue how to find out what's causing the lockup.  I'd
> love to, because I usually lose a bunch of work in the crash.
>   3) I don't see anything labeled "SysReq" on my keyboard, but it's
> associated with the PrintScreen key on my wife's box.  Can I hope
> alt-printscreen-K will work?  (I personally wonder about it since
> _nothing_ else on the keyboard works, but maybe the kernel can see
> it).
>
> Again, thanks.  I'll say more when it happens again.
>
> --
> Kevin O'Gorman, PhD
1) alt-printscreen-k should work
2) try 'killall X' via ssh and if that doesnt restart and bring the display 
back also do "killall kdm"
3) can you share a copy of you xorg.conf?
-- 
Guillermo A. Amaral, CSE
# Free & Open Source Advocate
& nick: guillermoamaral
@ blog: http://blog.guillermoamaral.com/
@ site: http://www.guillermoamaral.com/
$ irc: guillermoamaral@freenode
% gpg: http://downloads.guillermoamaral.com/public.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Help me reboot X

[Kevin O'Gorman]

On 6/3/07, Guillermo A. Amaral <me@guillermoamaral.com> wrote:
> On Sunday 03 June 2007 19:36, Kevin O'Gorman wrote:
> >
> > In the meanwhile, a couple of notes:
> >   1) Yes, it's REALLY locked up.  But there's always enough CPU left
> > for a non-X login from another machine.  It has to be another machine
> > because I can't even switch to a console terminal.
> >   2) I have no clue how to find out what's causing the lockup.  I'd
> > love to, because I usually lose a bunch of work in the crash.
> >   3) I don't see anything labeled "SysReq" on my keyboard, but it's
> > associated with the PrintScreen key on my wife's box.  Can I hope
> > alt-printscreen-K will work?  (I personally wonder about it since
> > _nothing_ else on the keyboard works, but maybe the kernel can see
> > it).
> >
> > Again, thanks.  I'll say more when it happens again.
> >
> > --
> > Kevin O'Gorman, PhD
> >
> >
> 1) alt-printscreen-k should work
> 2) try 'killall X' via ssh and if that doesnt restart and bring the display
> back also do "killall kdm"
> 3) can you share a copy of you xorg.conf?

Sure.  I've done very little with it for a very long time.  It still
mentions XFree, for
instance.  But mostly it works.

# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# 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 XFREE86 PROJECT 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 XFree86 Project 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
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) 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 Type1 and FreeType 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)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

    FontPath   "/usr/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/TrueType/"
#    FontPath   "/usr/share/fonts/freefont/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/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 <Crtl><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 <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><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"    "pc102"
# 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 XFree86

#    Option "XkbModel"    "pc101"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"


    Option "XkbModel"   "microsoft"
    Option "XkbLayout"  "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "PS/2"
    #KOSMANOR: for udev
    Option "Device"      "/dev/input/mice"
    Option "ZAxisMapping"       "4 5"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"        "256"

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

#    Option "Protocol"  "Xqueue"

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

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

# Emulate3Buttons is an option for 2-button Microsoft 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 XF86Config 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"
    # I made this up; at 1400-1050, it says it's running at
    #     H: 81.8 KHz, V: 75.0 Hz
    #     and just as H had to be at least 78.75 KHz (75 x 1050)
    #     so the dot clock has to be at least 114 MHz (81.8 x 1400)
    Identifier  "Westinghouse"
    HorizSync   20-120
    VertRefresh 40-120
EndSection

Section "Monitor"

    Identifier  "pionex"

# 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   30-70

#    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 47-130

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 xf86config:

Section "Device"
    Identifier  "ati-internal"
    Driver      "ati"
    #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  "Screen1"
    Device      "ati-internal"
    Monitor     "Westinghouse"
    DefaultDepth 16

    Subsection "Display"
        Depth       8
        Modes       "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1400x1050" "1300x1024" "1280x1024"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1400x1050" "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 "Screen1"

# 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




-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Alan McKinnon]

On Monday 04 June 2007, Kevin O'Gorman wrote:
>   2) I have no clue how to find out what's causing the lockup.  I'd
> love to, because I usually lose a bunch of work in the crash.

top will tell you which process is hogging the resources and also let 
you kill it with the 'k' hotkey

My X also locks up from time to time due to kde-type issues, the usual 
cause is konqueror and invaribaly I have to kill and restart kdeinit or 
even '/etc/init.d/xdm restart' in extreme cases. But I use 
enlightenment as the wm so that might not necessarily hold true for 
you.

When using kde as the desktop, I've also had this trouble with kicker

alan



-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Benno Schulenberg]

Kevin O'Gorman wrote:
>   1) Yes, it's REALLY locked up.  But there's always enough CPU
> left for a non-X login from another machine.

This kind of lockup is usually an error in the video driver, 
forgetting to drop a software lock after some operation and then on 
the next operation waiting endlessly for the lock to be dropped.  
Or it gave the video chip a wrong command that never ends, while 
holding a software lock.  In this latter case restarting X probably 
won't help, as the video chip is deaf.

>   2) I have no clue how to find out what's causing the lockup. 
> I'd love to, because I usually lose a bunch of work in the crash.

Check your video driver and see if there's a newer version 
available.

Benno
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Paul Sebastian Ziegler]

> Can somebody help me stop and restart X?  I'm using kdm for login.

Just in case your X-Server is still responding AT ALL you can always try
hitting Ctrl+Alt+Backspace to kill it. This will work up to a certain
level of "hanging".

Then simply restart it by typing "startx".

Otherwise ssh into your box and use "ps -ax | grep X" or "ps -e | grep
X" to get X's PID and then kill it using "kill".
kill has a priority switch. So "kill [PID]" might not work. However
"kill -9 [PID]" will kill about anything on the spot. If the -9-switch
fails to kill X you are having more serious troubles.

My two cents
Paul

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Ken]

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

Kevin O'Gorman wrote:
>> From time to time my X server will lock up, usually but not always
> while I'm editing something in ooffice.  It's always something that's
> pretty heavily graphical.  When this happens, the only thing that
> still works on my desktop is mouse motion.  No clicks actually
> register, and even the three-finger salutes (BS and DEL) are feckless.
> 
> However, I can SSH into the machine from elsewhere and pretty much do
> anything else I want.  I usually have to reboot the machine, because I
> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> simple, but I can't seem to find documentation on this particular
> thing and it's not like the usual init.d services.  Lots on startup, a
> bit on shutdown, but nothing I see is about restart.
> 
> When this happens, sometimes X is using 100% of one of the CPU's, but
> I don't always check and haven't recently verified my impression that
> sometimes all CPU's are at an idle (I have 4 hyperthreads).
> 
> Can somebody help me stop and restart X?  I'm using kdm for login.
> 
If you have physical access to the machine and have support for the
Magic SysRq built into your kernel, you can kill the X server by
pressing ALT + SysRq + K. This will kill all processes running on the
current terminal.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGY2gK0PM4px2/kjgRAuHkAJsHNoreMVfLQ+O9N8Nd9WFbzs5lHwCfZLZl
lU7uNnnTQjLNFCK3kANELgo=
=fSzd
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

On Sun, 03 Jun 2007 21:16:58 -0400, Ken wrote:

> If you have physical access to the machine and have support for the
> Magic SysRq built into your kernel, you can kill the X server by
> pressing ALT + SysRq + K. This will kill all processes running on the
> current terminal.

If you are accessing via SSH, you can still use this with

echo k >/proc/sysrq-trigger


-- 
Neil Bothwick

I can see clearly now, the brain is gone...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Help me reboot X

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

On 6/18/07, Neil Bothwick <neil@digimed.co.uk> wrote:
>
> On Sun, 03 Jun 2007 21:16:58 -0400, Ken wrote:
>
> > If you have physical access to the machine and have support for the
> > Magic SysRq built into your kernel, you can kill the X server by
> > pressing ALT + SysRq + K. This will kill all processes running on the
> > current terminal.
>
> If you are accessing via SSH, you can still use this with
>
> echo k >/proc/sysrq-trigger


Nice.  However, I'm still wondering -- neither of my keyboards has a keytop
labelled sysreq.  What is it?

++ kevin

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 920 bytes --]

Re: [gentoo-user] Help me reboot X

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

On Monday 18 June 2007 12:22:59 Kevin O'Gorman wrote:
> On 6/18/07, Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Sun, 03 Jun 2007 21:16:58 -0400, Ken wrote:
> > > If you have physical access to the machine and have support for the
> > > Magic SysRq built into your kernel, you can kill the X server by
> > > pressing ALT + SysRq + K. This will kill all processes running on the
> > > current terminal.

Hrm, I thought this killed ALL processes, but I could be wrong.  Is that maybe 
Alt+SysRq+e or Alt+SysRq+i?

> > If you are accessing via SSH, you can still use this with
> >
> > echo k >/proc/sysrq-trigger
>
> Nice.  However, I'm still wondering -- neither of my keyboards has a keytop
> labelled sysreq.  What is it?

My laptop has a specific key for it.  IIRC, (my desktop is not in front of 
me), it shares a key with 'Print Screen'.  On both (again, IIRC) it's usually 
shortend to just 'SysRq'.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Help me reboot X

[Ken]

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

Kevin O'Gorman wrote:
> On 6/18/07, *Neil Bothwick* <neil@digimed.co.uk
> <mailto:neil@digimed.co.uk>> wrote:
> 
>     On Sun, 03 Jun 2007 21:16:58 -0400, Ken wrote:
> 
>     > If you have physical access to the machine and have support for the
>     > Magic SysRq built into your kernel, you can kill the X server by
>     > pressing ALT + SysRq + K. This will kill all processes running on the
>     > current terminal.
> 
>     If you are accessing via SSH, you can still use this with
> 
>     echo k >/proc/sysrq-trigger
> 
> 
> Nice.  However, I'm still wondering -- neither of my keyboards has a
> keytop labelled sysreq.  What is it?
> 
> ++ kevin
> 
> -- 
> Kevin O'Gorman, PhD

It's the PrintScreen key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGdsTt0PM4px2/kjgRAklSAJwImm7vbI6Lq3F7zBNG4/sYeh4VIwCeKOdS
rid/NxIHpobjbFEg4KkboIM=
=H7WB
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Hemmann, Volker Armin]

On Montag, 18. Juni 2007, Kevin O'Gorman wrote:

>
> Nice.  However, I'm still wondering -- neither of my keyboards has a keytop
> labelled sysreq.  What is it?

print
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Guillermo A. Amaral]

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On Sunday 03 June 2007 17:16, Kevin O'Gorman wrote:
> From time to time my X server will lock up, usually but not always
> <snip>
> However, I can SSH into the machine from elsewhere and pretty much do
> anything else I want.  I usually have to reboot the machine, because I
> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> simple, but I can't seem to find documentation on this particular
> thing and it's not like the usual init.d services.  Lots on startup, a
> bit on shutdown, but nothing I see is about restart.
>
> When this happens, sometimes X is using 100% of one of the CPU's, but
> I don't always check and haven't recently verified my impression that
> sometimes all CPU's are at an idle (I have 4 hyperthreads).
>
> Can somebody help me stop and restart X?  I'm using kdm for login.
>
> --
> Kevin O'Gorman, PhD

If you are using KDM you can always do a "killall X" as root and KDM should 
bring it back up for you.

-- 
Guillermo A. Amaral, CSE
# Free & Open Source Advocate
& nick: guillermoamaral
@ blog: http://blog.guillermoamaral.com/
@ site: http://www.guillermoamaral.com/
$ irc: guillermoamaral@freenode
% gpg: http://downloads.guillermoamaral.com/public.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Help me reboot X

[Alex Schuster]

Kevin O'Gorman writes:

> Can somebody help me stop and restart X?  I'm using kdm for login.

/etc/init.d/xdm restart

	Alex
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Aleksandar L. Dimitrov]

On Mon, Jun 04, 2007 at 03:51:49AM +0200, Alex Schuster wrote:
> Kevin O'Gorman writes:
> 
> > Can somebody help me stop and restart X?  I'm using kdm for login.
> 
> /etc/init.d/xdm restart

Well, yes. But be aware of the fact that - depending on the
configuration, this *might* not work when issued inside an X session
(via an xterm or similar) or may at least lead to... undefined behaviour
;). But it is safe to issue from within a virtual terminal
([Alt][F1-F6]).

A magic key combination is [Alt][Ctrl][Backspace]. This immediately
kills the X-Session (if it is not disabled in the xorg.conf) - GDM and
KDM will then restart right away (KDM will do that forever, GDM only
about 3 times) though Slim for example wouldn't.

Regards, Aleks
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Philip Webb]

070603 Kevin O'Gorman wrote:
> From time to time my X server will lock up,
> usually but not always while I'm editing something in ooffice.
> It's always something that's pretty heavily graphical.
> When this happens, the only thing that still works on my desktop
> is mouse motion.  No clicks actually register
> and even the three-finger salutes (BS and DEL) are feckless.
> Can somebody help me stop and restart X?  I'm using kdm for login.

I've run into this too & had concluded it was minor defects in memory
brought about when the box heats a bit more than usual
(one memory bit's magnetism spills over into a neighbour).
I boot into a raw terminal, then start X with 'startx', 
so your problem probably has nothing to do with Kdm.

Your experience & a couple of earlier reports on the list
suggest there is an obscure bug somewhere in X ,
which would be very difficult to track down or even describe for bugzilla.
It seems unlikely to be a driver bug, as I've not changed cards recently.

I have just tested 'Alt-PrintScreen-K' -- press all simultaneously --
& it blanks the screen, after which I can use 'Ctl-Alt-F1'
to re-access the TTY, when 'Return' brings a terminal prompt
& I can restart X with 'startx' as usual (super-fast!);
this depends on enabling the 'magic SysRq' option in the kernel.
Of course, I don't know whether it will work next time X locks up (smile).

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Philip Webb]

070604 Philip Webb wrote:
> 070603 Kevin O'Gorman wrote:
>> From time to time my X server will lock up,
>> usually while I'm editing something heavily graphical.
>> When this happens, the only thing that still works on my desktop
>> is mouse motion.  No clicks actually register
>> and even the three-finger salutes (BS and DEL) are feckless.
> Your experience & a couple of earlier reports on the list
> suggest there is an obscure bug somewhere in X .
> I have just tested 'Alt-PrintScreen-K' -- press all simultaneously --

Well today, I've had  2  lock-ups !  Both involved Epiphany
-- which I find a bit faster & more convenient than FF/Konqueror -- ,
the 1st merely locking the browser, which I was able to kill
after going to another desktop with a Konsole & running Htop,
the 2nd just now involving a total lock-up as described above
& yes the 'Alt-PrintScreen-K' manoeuvre does act as a get-out-of-jail card:
you have to re-enter the TTY with 'Ctl-Alt-F1',
where there are a lot of msgs announcing that X has been killed
& you can restart it with 'startx' (my normal method).

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[b.n.]

Kevin O'Gorman ha scritto:
>> From time to time my X server will lock up, usually but not always
> while I'm editing something in ooffice.  It's always something that's
> pretty heavily graphical.  
> When this happens, the only thing that
> still works on my desktop is mouse motion.  No clicks actually
> register, and even the three-finger salutes (BS and DEL) are feckless.
>
> However, I can SSH into the machine from elsewhere and pretty much do
> anything else I want.  I usually have to reboot the machine, because I
> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> simple, but I can't seem to find documentation on this particular
> thing and it's not like the usual init.d services.  Lots on startup, a
> bit on shutdown, but nothing I see is about restart.


Run into that too. Exactly same situation -KDE, OO.org, heavy graphical
editing (resizing images in Impress etc.), mouse moving but nothing
responding, etc... Identical bug.

I attributed the cause to the Beryl SVN I'm always running, so I didn't
feel entitled to complain. If you are not running Beryl, however, it
would be nice to know more -so to find what bug is or to file one.

Thanks,
m.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Alan McKinnon]

On Monday 04 June 2007, b.n. wrote:
> Run into that too. Exactly same situation -KDE, OO.org, heavy
> graphical editing (resizing images in Impress etc.), mouse moving but
> nothing responding, etc... Identical bug.
>
> I attributed the cause to the Beryl SVN I'm always running, so I
> didn't feel entitled to complain. If you are not running Beryl,
> however, it would be nice to know more -so to find what bug is or to
> file one.

I doubt it's beryl. I get similar symptoms every now and again using 
xorg-7.2, enlightenment-17 (latest cvs) and open source radeon driver

alan

-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Dan Farrell]

On Sun, 3 Jun 2007 17:16:52 -0700
"Kevin O'Gorman" <kogorman@gmail.com> wrote:

> From time to time my X server will lock up, usually but not always
> while I'm editing something in ooffice.  It's always something that's
> pretty heavily graphical.  When this happens, the only thing that
> still works on my desktop is mouse motion.  No clicks actually
> register, and even the three-finger salutes (BS and DEL) are feckless.
> 
> However, I can SSH into the machine from elsewhere and pretty much do
> anything else I want.  I usually have to reboot the machine, because I
> haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> simple, but I can't seem to find documentation on this particular
> thing and it's not like the usual init.d services.  Lots on startup, a
> bit on shutdown, but nothing I see is about restart.
> 
> When this happens, sometimes X is using 100% of one of the CPU's, but
> I don't always check and haven't recently verified my impression that
> sometimes all CPU's are at an idle (I have 4 hyperthreads).
> 
> Can somebody help me stop and restart X?  I'm using kdm for login.
> 
Just find the offending process's id number and issue it a term signal.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Kevin O'Gorman]

On 6/4/07, Dan Farrell <dan@spore.ath.cx> wrote:
> On Sun, 3 Jun 2007 17:16:52 -0700
> "Kevin O'Gorman" <kogorman@gmail.com> wrote:
>
> > From time to time my X server will lock up, usually but not always
> > while I'm editing something in ooffice.  It's always something that's
> > pretty heavily graphical.  When this happens, the only thing that
> > still works on my desktop is mouse motion.  No clicks actually
> > register, and even the three-finger salutes (BS and DEL) are feckless.
> >
> > However, I can SSH into the machine from elsewhere and pretty much do
> > anything else I want.  I usually have to reboot the machine, because I
> > haven't figured out how to restart X in gentoo.  I'm sure it's pretty
> > simple, but I can't seem to find documentation on this particular
> > thing and it's not like the usual init.d services.  Lots on startup, a
> > bit on shutdown, but nothing I see is about restart.
> >
> > When this happens, sometimes X is using 100% of one of the CPU's, but
> > I don't always check and haven't recently verified my impression that
> > sometimes all CPU's are at an idle (I have 4 hyperthreads).
> >
> > Can somebody help me stop and restart X?  I'm using kdm for login.
> >
> Just find the offending process's id number and issue it a term signal.
> --
> gentoo-user@gentoo.org mailing list
>
>
There's sometimes no obvious offending process.  Sending a term to X
doesn't always do much when this is going on.  I'll have to wait till
it happens again to be specific.

++ kevin

-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Help me reboot X

[Dan Farrell]

On Mon, 4 Jun 2007 18:52:35 -0700
"Kevin O'Gorman" <kogorman@gmail.com> wrote:

> On 6/4/07, Dan Farrell <dan@spore.ath.cx> wrote:
> > On Sun, 3 Jun 2007 17:16:52 -0700
> > "Kevin O'Gorman" <kogorman@gmail.com> wrote:
> >
> > > From time to time my X server will lock up, usually but not always
> > > while I'm editing something in ooffice.  It's always something
> > > that's pretty heavily graphical.  When this happens, the only
> > > thing that still works on my desktop is mouse motion.  No clicks
> > > actually register, and even the three-finger salutes (BS and DEL)
> > > are feckless.
> > >
> > > However, I can SSH into the machine from elsewhere and pretty
> > > much do anything else I want.  I usually have to reboot the
> > > machine, because I haven't figured out how to restart X in
> > > gentoo.  I'm sure it's pretty simple, but I can't seem to find
> > > documentation on this particular thing and it's not like the
> > > usual init.d services.  Lots on startup, a bit on shutdown, but
> > > nothing I see is about restart.
> > >
> > > When this happens, sometimes X is using 100% of one of the CPU's,
> > > but I don't always check and haven't recently verified my
> > > impression that sometimes all CPU's are at an idle (I have 4
> > > hyperthreads).
> > >
> > > Can somebody help me stop and restart X?  I'm using kdm for login.
> > >
> > Just find the offending process's id number and issue it a term
> > signal. --
> > gentoo-user@gentoo.org mailing list
> >
> >
> There's sometimes no obvious offending process.  Sending a term to X
> doesn't always do much when this is going on.  
You might try -KILL; that should do the trick.  KDM should restart the
server and revert to the logon screen, unless you changed that setting.
> I'll have to wait till
> it happens again to be specific.
> 
> ++ kevin
> 
Sorry, for some reason decided to send this message without scrolling
down to see whether anyone else had yet answered; it turns out they
did, and their answeres were much more complete.  
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Help me reboot X

[burlingk]

> -----Original Message-----
> From: Kevin O'Gorman [mailto:kogorman@gmail.com] 
> Sent: Monday, June 04, 2007 9:17 AM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] Help me reboot X
> 
> Can somebody help me stop and restart X?  I'm using kdm for login.
> 
> -- 
> Kevin O'Gorman, PhD
> -- 
> gentoo-user@gentoo.org mailing list
> 


Check out the kdm documentation.
GDM has a few commands for handling that sort of thing,
like gdm-stop, and gdm-restart.
KDM might have might have similar.  I am not sure.
--
gentoo-user@gentoo.org mailing list