LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Hard lockup of X on exit after update to 07/03/07 *.tgz's (http://www.linuxquestions.org/questions/slackware-14/hard-lockup-of-x-on-exit-after-update-to-07-03-07-%2A-tgzs-537067/)

Eternal_Newbie 03-13-2007 08:23 AM

Hard lockup of X on exit after update to 07/03/07 *.tgz's - SOLVED
 
After applying the patches/packages/x11-6.9.0-i486-12_slack11.0.tgz update from 07 March 2007 for Slackware 11.0, I experienced several hard lockups of X11 on exit. The keyboard was unresponsive, waiting did not help, and I had to resort to a hard reboot.

Reverting to the previous X11 package resolved the problem , but I suspect it was an issue with the fglrx driver and changing the driver to radeon or vesa would also have worked.

Has anyone else experienced this particular problem?

Code:

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

    Load        "dbe"          # Double buffer extension
# 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        "freetype"
    #Load        "speedo"

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

    RgbPath        "/usr/X11R6/lib/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)
#
# 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/X11R6/lib/X11/fonts/local/"
    FontPath  "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath  "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath  "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath  "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath  "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath  "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath  "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath  "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath  "/usr/X11R6/lib/X11/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

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    "DontZoom"

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

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

    Option      "standby time"  "20"
    Option      "suspend time"  "30"
    Option      "off time"      "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option  "EstimateSizesAggresively" "0"
# May cause problems remove this and bpp if does
#    Option "Pixmap"  "32"

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"

# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.

#    Option    "AutoRepeat"    "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option    "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option    "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option    "XkbModel"      "pc102"
    Option    "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option    "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option    "XkbModel"      "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option    "XkbLayout"    "de"
#
# or:
#
    Option    "XkbLayout"    "gb"
#  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 X.Org
#
#    Option    "XkbRules"      "xorg"
#    Option    "XkbModel"      "pc101"
#    Option    "XkbLayout"    "us"
#    Option    "XkbVariant"    ""
#    Option    "XkbOptions"    ""

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier        "Mouse1"
    Driver        "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

#    Option    "Protocol"      "Auto"

# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
    Option "Protocol"    "IMPS/2"

# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/input/mice"
#  Option "Device"      "/dev/mouse"

#  Option "Device"      "/dev/psaux"
#  Option "Device"      "/dev/ttyS0"
#  Option "Device"      "/dev/ttyS1"

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

# Enable mouse wheel
  Option "SendCoreEvents"  "true"
  Option "Buttons"        "5"
  Option "ZAxisMapping"    "4 5"

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-50.0

    HorizSync  31.5-60.0

#    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 40-90

    VertRefresh 60-70
#    DispaySize 306 229
    Option "DPMS"
EndSection


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

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

Section "Device"
    Identifier  "9600XT"
    Driver      "radeon"
    # VideoRam    131072
    # Option "GARTSize" "64"
    # 0-64 Megabytes of gart (system) memory used.
    # Wrongly defaults to 8MB sometimes, see your logfile.
    # Bigger seems better.
    # Insert Clocks lines here if appropriate
EndSection

Section "Device"
    Identifier  "ATI"
    Driver      "fglrx"
    # VideoRam    131072
    # Option "GARTSize" "64"
    # 0-64 Megabytes of gart (system) memory used.
    # Wrongly defaults to 8MB sometimes, see your logfile.
    # Bigger seems better.
    # 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      "ATI"
#    Device        "9600XT"
    Monitor    "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#  DefaultDepth 8
#  DefaultDepth 16
  DefaultDepth 24

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

    Subsection "Display"
        Depth      8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth      16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth      24
        Modes "1024x768" "800x600" "640x480"
    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"
#  Group    "video"
#  Mode    0660
  Mode    0666
EndSection

XORG.0.log here.

NOTE: I just checked the Gentoo WIki and there was a warning about recent fglrx drivers blanking the screen after exit (They think the screen is a TV!) and a solution. I will try that.

ludist 03-13-2007 12:33 PM

Not the same, similar. After upgrade I couldn't start X. Bug in my graphic card. Changed DefaultDepth to 24: ok now.

GrapefruiTgirl 03-13-2007 12:40 PM

Just a suggestion, which I base on my recent experience getting my nVidia driver and card to work: I wonder if there is a driver or hardware conflict based on the contents of your xorg.conf file.
I also upgraded X but didn't have any problems..

You have 3 devices specified there, none of which have a BusID associated with them.
How many video cards do you have in the machine? I assume just one, in part due to the fact that I see just one Monitor section.. If so, remove the others and specify the BusID of the one you are actually using.
As well, verify that DRI works with your card; It likely does, but just make sure, because some cards/drivers don't like it.
Best of luck :)

GrapefruiTgirl 03-13-2007 01:00 PM

(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.31.2.1.2.3-driver-lnx-x86-x86_64-305837
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset RADEON 9600 PRO (RV360 4152) found

EDIT: OK, it seems you do have 2 cards, so..
This is from your xorg LOG.. You see there that the machine assigned the first device it found, with PCI BusID 1.0.0
The second device should have a line like:
BusID PCI:1:0:1
and also, how many monitors do you have? If only one, then you again should have only one device specified, otherwise the two devices are going to fight over the monitor.
Look here for more details, it is from my xorg.conf file. If you have only one monitor, you would remove everything that refers to the second screen, second device, and second monitor (the TV)
link: http://www.linuxquestions.org/questi...d.php?t=533514

Eternal_Newbie 03-13-2007 01:51 PM

I actually have a single card, it is dual-head, although I only use one monitor at the moment. I use multiple device sections because it makes it easier to switch. I have just added BusID line to my "ATI" device section, just in case it was getting stroppy about that.

Code:

Section "Device"
    Identifier  "ATI"
    Driver      "fglrx"
    BusID      "PCI:1:0:0"
    Option      "VideoOverlay" "on"
EndSection

I also updated the drivers. My usual policy with fglrx drivers is not to touch them, but as they were obviously broken by something, it couldn't hurt. Things seem to be running OK for now.

GrapefruiTgirl 03-13-2007 03:38 PM

Aha ok cool.. Mine is dual head as well.
On that subject, BOTH heads get addressed with the SAME PCI BusID, but with different Identifiers and Screen #'s.
Glad you got it working! One thing I did have to do after installing the X11 patch was re-install my card driver, because the X patch removed a symlink to some shared library. Otherwise, it was pretty simple.
Also, again on the subject of the dual heads, there are some very good tutorials out there, including some Gentoo-related ones like the one you said you were using. I did find however that none of them fully addressed all the issues I had had while learning how to implement the 2 screens I now use with my card, so that Xorg.conf I posted is partly based on the tutorials that came with my driver, and the remainder is the result of my own experimentation. Hopefully it will help you or someone else :) And for a VERY detailed README, the one that can be downloaded from nVidia is huge and excellent, and even though there is a lot of Nvidia-specific stuff in it, there is also a LOT of useful info about X itself.
Take care :)

XGizzmo 03-13-2007 05:10 PM

Anytime you upgrade X you should recompile/install your video card driver.
It may work without recompiling it, but in my experience it can hard lock X.


All times are GMT -5. The time now is 09:55 PM.