Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
X.org Lockups (part 2)
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page Previous  1, 2, 3 ... 15, 16, 17 ... 35, 36, 37  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
JohnY
Guru
Guru


Joined: 26 Jul 2002
Posts: 305

PostPosted: Tue Aug 30, 2005 10:14 pm    Post subject: Reply with quote

Thanks Herman -

You're right, I've never used them. Good Education though. I see that gentoo-sources 2.6.13 is out today in unstable. I wonder if that will change the situation?


JohnY
Back to top
View user's profile Send private message
kmare
l33t
l33t


Joined: 20 Nov 2004
Posts: 619
Location: Thessaloniki, Greece

PostPosted: Tue Aug 30, 2005 11:31 pm    Post subject: Reply with quote

i'm running 2.6.13 22 hours now and it seems stable, no crashes... I just wanna see when the next freeze will happen... :D
Back to top
View user's profile Send private message
spitefulcrow
n00b
n00b


Joined: 18 Jul 2004
Posts: 44

PostPosted: Thu Sep 01, 2005 7:06 pm    Post subject: Reply with quote

kmare wrote:
i'm running 2.6.13 22 hours now and it seems stable, no crashes... I just wanna see when the next freeze will happen... :D

Don't hold your breath...
I switched to 2.6.13 a few days ago and I'm still crashing.

Also, I'm seeing a new issue with this system now:
X randomly segfaults (quits on signal 11) with no other information given. This time, it died and apparently scribbled all over memory because I couldn't start it again because fluxbox complained of a stack smashing attack (I use SSP/-fstack-protector in CFLAGS) and segfaulted it again.

This HAS to be an issue in the core X code and/or kernel bus drivers as well as X drivers. At this point, I'm using a kernel with all AGP options disabled and running the Xorg "nv" driver instead of nvidia (nvidia-* is entirely removed from my system) and I'm still getting hard locks and the aforementioned X segfaults.

This is frustrating me to no end because nobody can reproduce or document this obvious bug to get the kernel and X devs to FIX it! Hasn't anyone noticed the fact that the nVidia forum as well as Gentoo, Ubuntu, Debian, and who knows how many other distro support forums are going wild over this? Rumor has it that *BSD doesn't suffer from these issues, but I don't want to learn a new Unix, and I simply can't go back to using Windows after 5+ years.
_________________
Athlon XP 2600+ (1.9gHz)/1024MB DDR333/Asus A7V880/Samsung 160GB SATA HDD/Chaintech GeForce FX5500 256MB
Back to top
View user's profile Send private message
kmare
l33t
l33t


Joined: 20 Nov 2004
Posts: 619
Location: Thessaloniki, Greece

PostPosted: Thu Sep 01, 2005 7:14 pm    Post subject: Reply with quote

well.. it seems stable for now.. the only change I made in the kernel over the previous kernels was to enable the preemptive scheduler since I read that there have been many bug fixes and improvements on it... I also switched to the cfq elavator.. I'm pretty sure that a freeze will come pretty soon but for now it didn't happen yet. I'll believe that the problem is fixed only when somebody will come out saying: found the problem there and the fix is that.. till then I don't think/believe we'll have our system 100% stable again.. i'm even thinking about buying a new pc only because of that.. :(
Back to top
View user's profile Send private message
spitefulcrow
n00b
n00b


Joined: 18 Jul 2004
Posts: 44

PostPosted: Thu Sep 01, 2005 7:36 pm    Post subject: Reply with quote

kmare wrote:
well.. it seems stable for now.. the only change I made in the kernel over the previous kernels was to enable the preemptive scheduler since I read that there have been many bug fixes and improvements on it... I also switched to the cfq elavator.. I'm pretty sure that a freeze will come pretty soon but for now it didn't happen yet. I'll believe that the problem is fixed only when somebody will come out saying: found the problem there and the fix is that.. till then I don't think/believe we'll have our system 100% stable again.. i'm even thinking about buying a new pc only because of that.. :(

Unless you absolutely have to have high-performance 3D acceleration, I'd suggest finding an old PCI graphics card somewhere and trying that first. If you don't get lockups with it, PLEASE post back here because it'll be proof that this is a bug in AGP drivers.
_________________
Athlon XP 2600+ (1.9gHz)/1024MB DDR333/Asus A7V880/Samsung 160GB SATA HDD/Chaintech GeForce FX5500 256MB
Back to top
View user's profile Send private message
Fenster
Apprentice
Apprentice


Joined: 26 Oct 2004
Posts: 172
Location: Purgatory

PostPosted: Fri Sep 02, 2005 12:11 am    Post subject: Reply with quote

Might the lockups be somehow related to using the Gnome Display Manager?

I had very frequent lockups using the GDM. I disabled it for the sake of it and found that my type 2 lockups went away. I've gone from an average of 6 hours uptime to a week.

Kernel: 2.6.12-gentoo-r8
Xorg: 6.8.2-r2
GDM: 2.8.0.2
_________________
photography - geekery
Back to top
View user's profile Send private message
JohnY
Guru
Guru


Joined: 26 Jul 2002
Posts: 305

PostPosted: Fri Sep 02, 2005 4:36 am    Post subject: Reply with quote

I'm approaching 7 days of no crashes at all both at AGP 2x and 4x, after changing from an ATI 8500le with radeon driver to a G400 16mb with xorg 6.8.99.15, 2.6.12-gentoo-r9, glibc 2.35-r1. Although I usually run gnome with some kde programs, I've also installed e17-cvs and run it with no problems during the past week. At least for now I'm stable with multiple audio and video streams, mozilla, tvtime, and emerges all going at the same time.

JohnY

an35n ultra nforce2
2.0 Ghz tbredb
512mb corsair value
sblive
symbios 825 scsi
hpIIcx scanner
kworld bt878 tvcard
wd 120GB
~x86
Back to top
View user's profile Send private message
yaneurabeya
Veteran
Veteran


Joined: 13 May 2004
Posts: 1754
Location: Seattle

PostPosted: Fri Sep 02, 2005 2:03 pm    Post subject: Reply with quote

JohnY wrote:
Thanks Herman -

You're right, I've never used them. Good Education though. I see that gentoo-sources 2.6.13 is out today in unstable. I wonder if that will change the situation?


JohnY


Running a vanilla kernel is better as it means that the sources for faults are lower, and you can patch your kernel as you see fit. But in the end you ultimately decide what you want to run, so...
Back to top
View user's profile Send private message
RaZoR1394
Guru
Guru


Joined: 09 Jan 2005
Posts: 356

PostPosted: Fri Sep 02, 2005 4:22 pm    Post subject: Reply with quote

I had my first "type 1" lockup today. I was installing Dungeon Siege 2. I alt-tabbed through some other windows and then I moved the installer window a bit which caused the lockup. The mouse was still movable, numlock was not responding but I could easily kill X via SSH.
_________________
http://en.wikipedia.org/wiki/Cell_(microprocessor)


Last edited by RaZoR1394 on Sat Sep 03, 2005 9:28 am; edited 1 time in total
Back to top
View user's profile Send private message
hielvc
Advocate
Advocate


Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca

PostPosted: Sat Sep 03, 2005 3:16 am    Post subject: Reply with quote

well with a gentoo-sources-2.6.13 and a new xorg config via " Xorg -configure" Ive been stable for 2 hrs. My system had gotten so bad that just running sylpheed-claws would freze me with in 3 seconds.then I would ssh in. Whats strange is that though I dont have nv drivers in my kernel, the new xorg config does, and is working fine. If I include the NV drivers in the kernel it wont even boot. Oh I had to make a new X config to get this working my old one wouldn't work.

Well I locked right after I posted :lol: out cone nv drivers in X config.
_________________
An A-Z Index of the Linux BASH command line
Back to top
View user's profile Send private message
eis
Apprentice
Apprentice


Joined: 05 Aug 2005
Posts: 161
Location: Stuttgart, Germany

PostPosted: Sat Sep 03, 2005 8:21 pm    Post subject: Reply with quote

Hi!

I am using ATI X300, and I guess its PCI slot. I have an Inspiron 6000 of DELL. And honestly I have tried most I can to get this stupid Xorg running.
I used "fglrxconfig" command creates the corg.conf file but after "startx" screen freezes. I tried it a couple of times. I think all the Info I gave was correct. Except my vertical and horizontal sync rate I do not know for sure. But I asked Dell personally and they said it would be the following for my WXGA Display (max. 1280x800):
" The horizontal sync rate is 75 Hz and the vertical refresh rate is 60 Hz"

So HOW CAN I GET X RUNNING???
If anyone has the same system as I do, please HELP!
Or tell me what the mistake might be. This is the raw xorg.conf which fglrxconf created. Except I adjusted the resolutions in the "screen" section. This, to be exact:

"Subsection "Display"
Depth 24
Modes "1280x768" "1024x768" "800x600""

Don't know if I did it the right way, but looks right to me.

eis


********************xorg.conf**********************
# File: xorg.conf
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.

# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# 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.
# **********************************************************************

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection

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

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. 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><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 "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"

# 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"
Identifier "Monitor0"
HorizSync 32-75
VertRefresh 40-60
Option "DPMS"

# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync

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

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=5460
Screen 0
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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x768" "1024x768" "800x600"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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 "Server 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.

Screen "Screen0"

# 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

### EOF ###

****************end xorg.conf**********************
Back to top
View user's profile Send private message
HermanR
Apprentice
Apprentice


Joined: 08 Jan 2004
Posts: 293
Location: The Netherlands

PostPosted: Sat Sep 03, 2005 10:35 pm    Post subject: Reply with quote

kmare wrote:
I'll believe that the problem is fixed only when somebody will come out saying: found the problem there and the fix is that.. till then I don't think/believe we'll have our system 100% stable again..

I'm pretty sure my lockups are over. I've been running my computer 24 hours a day for almost a week now and it has not even had a hickup. (Whereas before, I could be certain it crashed once or twice while I was working and for certain sometime during the night.) In the meantime, I switched from kernel 2.6.12 to 2.6.13, but that has nothing to do with it.

For me, the solution was to keep my PC running at its maximum CPU frequency; all my lockups occurred when my CPU was scaled down by the ondemand CPU frequency governor. My CPU can be idle, no problem with that, as long as it's operating at 2000 MHz. Therefore, the problem may be hardware (PSU?) related. I'm a happy man now... :D

I'm not saying this will solve everyone's problems. The problem is that the lockups have - as far as I can tell from reading all the stories here - very different symptoms and causes. There may be one or two mayor causes and some more minor ones, that's my guess. Some of these causes may be kernel- or X-related, others may be specific problems with optimization flags, Firefox crashing on some webpage, unstable software, graphics cards (AGP, like I had on my old Athlon Thunderbird), overclocking or other hardware. But every type of problem only affects a relatively small number of people (well, computers).

Sometimes the circumstances under which lockups occur can be misleading. For example: I noticed that my computer crashed only when running Linux, not in Windows XP. So I thought it must be Linux-related. But the fact is that I had Cool and Quiet working in Linux, and not in Windows. As soon as I figured out that the Cool and Quiet-thing must be the reason for my lockups, I understood why these didn't occur in Windows.
_________________
Gentoo (64 bits) on AMD64 X2 4400+, MSI K8T Neo2-FIR, 2 Gb RAM, 320 + 160 Gb SATA, nVidia Geforce 6600
Back to top
View user's profile Send private message
hielvc
Advocate
Advocate


Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca

PostPosted: Sun Sep 04, 2005 2:52 am    Post subject: Reply with quote

eis try
Quote:
Modes "1280x768" "1024x768" "800x600""
to
Modes "1280x768" "1024x768" "800x600"
and
# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
blaa
to
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fbdev"
BusID "PCI:1:0:0" # vendor=1002, device=5460
Screen 0
EndSection


Yes try it without all the other Options under the ATI section and just use fbdev driver.

Update after switching to fbdev no freezes for 11 hours.
_________________
An A-Z Index of the Linux BASH command line
Back to top
View user's profile Send private message
eis
Apprentice
Apprentice


Joined: 05 Aug 2005
Posts: 161
Location: Stuttgart, Germany

PostPosted: Sun Sep 04, 2005 10:04 am    Post subject: Reply with quote

DID IT
Failure:

"using config file> /etc/X11/xorg (or something like that)
using vt7
(EE) FBDEV(0): FBIOPUT_VSCREENINFO:Invalid argument
(EE) FBDEV(0): Mode init failed

Fatal server error:
AddScreen/ScreenInit failed for driver 0"
Back to top
View user's profile Send private message
fotisaueb
n00b
n00b


Joined: 21 Sep 2004
Posts: 36

PostPosted: Mon Sep 05, 2005 9:58 am    Post subject: Reply with quote

24 hours are not enough to be sure that lockups are gone.

If you read xorg lockups part 1 you will see that there are users that had the lockup after 3 days or more. I am one of those. Most configurations just prolong the frequency of a lockup.
After so many posts I'm pretty sure that Xorg 7.0 is our final hope.
I'm speaking only for the strictly defined xorg lockups like lockup with mouse unlocked being able to ssh 100% cpu usage .
Back to top
View user's profile Send private message
jspeybro
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 121
Location: Brussels

PostPosted: Tue Sep 06, 2005 10:32 am    Post subject: Reply with quote

eis, may I ask to post this in a seperate thread, this doesn't belong in this thread, as this thread is about the misterious lockups in X. this thread is already to big without posts like yours.

and to answer a few of te posted questions on the last pages, no it is not related to gnome display manager, it is not even xorg-related, as I had exactly the same in xfree86, it's also not distro-specific, it's been noticed in many distributions.

Johan
_________________
http://counter.li.org - Registered Linux user #295636
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Tue Sep 06, 2005 11:35 am    Post subject: Reply with quote

jspeybro wrote:

and to answer a few of te posted questions on the last pages, no it is not related to gnome display manager, it is not even xorg-related, as I had exactly the same in xfree86, it's also not distro-specific, it's been noticed in many distributions.
Johan

yes, but xorg and xfree are closely interrelated. btw there was a thread which i found on xfree lists (it was from 2004 i think), which described exactly type 1 problem (firefox locks the server with 100% and one could ssh) and resolving it with removing xinerama, but this didn't help me ::(((
But after all it seems it is a nasty bug in the xorg legacy code.
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
jspeybro
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 121
Location: Brussels

PostPosted: Tue Sep 06, 2005 11:49 am    Post subject: Reply with quote

yes, that's true, and as it seems to happen in both packages, it's probably something in the code of xfree that has been kept in xorg. I'm not hearing much new info lately. any news in isolating the bug?
_________________
http://counter.li.org - Registered Linux user #295636
Back to top
View user's profile Send private message
eis
Apprentice
Apprentice


Joined: 05 Aug 2005
Posts: 161
Location: Stuttgart, Germany

PostPosted: Tue Sep 06, 2005 12:44 pm    Post subject: Reply with quote

sure.

I just posted it in more than one thread beacause noone would answer...
And sorry for that interruption but I just don't know how to fix that...

These are the reasons why I have to have windows on my system...

bye,
eis
Back to top
View user's profile Send private message
x86usr
n00b
n00b


Joined: 06 Sep 2005
Posts: 2

PostPosted: Tue Sep 06, 2005 10:31 pm    Post subject: Reply with quote

I'm pretty sure that the bug is in the nvidia drivers. Everything worked fine with x.org or xfree86 until spring this year, so it should not be caused by old identical code. The lockups don't appear with any other drivers, I've never heard of a freezing nv driver. It also doesn't seem to affect 64bit systems.
Back to top
View user's profile Send private message
jspeybro
Tux's lil' helper
Tux's lil' helper


Joined: 06 Apr 2004
Posts: 121
Location: Brussels

PostPosted: Tue Sep 06, 2005 10:45 pm    Post subject: Reply with quote

It's happening with ati-drivers to if I'm not mistaken. it's not directly related to the drivers itself. it's more some underlying thing. I see agp mentionned often, although I never heard anyone confirming that he solved the problem by switching to a pci-card. I might as well try that if I get the chance.
I know nv-drivers are working, as that's the way I solved it for me.

Johan
_________________
http://counter.li.org - Registered Linux user #295636
Back to top
View user's profile Send private message
kmare
l33t
l33t


Joined: 20 Nov 2004
Posts: 619
Location: Thessaloniki, Greece

PostPosted: Wed Sep 07, 2005 12:27 am    Post subject: Reply with quote

x86usr wrote:
I'm pretty sure that the bug is in the nvidia drivers. Everything worked fine with x.org or xfree86 until spring this year, so it should not be caused by old identical code. The lockups don't appear with any other drivers, I've never heard of a freezing nv driver. It also doesn't seem to affect 64bit systems.


yeah????????? can anyone confirm that?? the truth is that I installed gentoo for a friend.. it's an amd64 with a geforce6800.. he has an uptime of more than 3 weeks playing world of warcraft, doom3, watching videos etc without a single freeze.. so maybe you're right.. only ppl with 32bit systems got the lockups. If that's true I'm gonna get a new amd64 sooner than I thought.. I'm really tired of those lockups

PS: since I switched to 2.6.13 I had no lockups... uptime for now is 153 hours.. and counting :)
Back to top
View user's profile Send private message
nbensa
l33t
l33t


Joined: 10 Jul 2002
Posts: 799
Location: Buenos Aires, Argentina

PostPosted: Wed Sep 07, 2005 3:51 am    Post subject: Reply with quote

xorg-x11-6.8.2-r2
gentoo-sources-2.6.12-r10 & 2.6.13
nvidia 1.0.6629 (GeForce2 MX200 - I couldn't get this card working with newer drivers)

I'm getting X locks (mouse moves but everything else is freezed) I still can ssh and kill X.

This website makes my box locks everytime: http://www.linuxart.com/ (browse photos to test your boxes)
Back to top
View user's profile Send private message
Nerdanel
Apprentice
Apprentice


Joined: 27 Apr 2003
Posts: 161
Location: Finland

PostPosted: Wed Sep 07, 2005 8:57 am    Post subject: Reply with quote

Just to remind people, there are lockups with the nv-driver too. I used to have them once a day but due to something I did the frequency had dropped a lot, to maybe once a week or even rarer.
Back to top
View user's profile Send private message
spitefulcrow
n00b
n00b


Joined: 18 Jul 2004
Posts: 44

PostPosted: Wed Sep 07, 2005 10:22 am    Post subject: Reply with quote

Still seeing lockups under the nv driver, but now something else is appearing.
I'm getting (seemingly random) segfaults of X apps and the X server. It usually starts with gkrellm2 dying, followed by the rest of my apps, then the server exits. Once it does this, X segfaults every time I try to restart it with startx. This sounds like something that could be easier to trace and report to developers, as it seems that whatever breaks scribbles on some part of memory to cause later crashes.
_________________
Athlon XP 2600+ (1.9gHz)/1024MB DDR333/Asus A7V880/Samsung 160GB SATA HDD/Chaintech GeForce FX5500 256MB
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page Previous  1, 2, 3 ... 15, 16, 17 ... 35, 36, 37  Next
Page 16 of 37

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