View previous topic :: View next topic |
Author |
Message |
rubik-wuerfel n00b
Joined: 29 Sep 2004 Posts: 53 Location: Goettingen, Germany
|
Posted: Mon Aug 22, 2005 7:06 pm Post subject: OpenGL games freeze the whole system randomly |
|
|
Note: I'm not sure if this is the right forum, if I'm wrong, please move me to another place.
I don't know exactly with which nvidia driver this started but currently (latest stable nvidia-kernel and nvidia-glx, i.e. 6629) every works fine, except for sometimes... When playing games like vegastrike or scorched3d or some other full screen OpenGL Games, sometimes the whole system including the game freezes, completely irreproducible, sometimes quite soon after starting, sometimes only after some hours of play, sometimes never at all. The complete system hangs, it's not even pingable anymore, Ctrl+Alt+Backspace does't work, neither do CapsLock, Ctrl+Alt+Del or the MagicSysReqKeys show any reaction, while the hard disk seems to be in full action...
I usually run everything in stable x86, have a NVidia GeForce FX 5700, and the current 2.6.9 kernel, glxgears run fine and fast... Anyone else who has had this problem? I couldn't find anything similar in the forums. |
|
Back to top |
|
|
adsmith Veteran
Joined: 26 Sep 2004 Posts: 1386 Location: NC, USA
|
Posted: Mon Aug 22, 2005 7:52 pm Post subject: |
|
|
1. are you running Xcomposite? (transparency/shadow support) If so, disable it, as it is experimental and usually conflictswith opengl
2. this could easily be an overheating problem. Have you watched the CPU and GPU temp? |
|
Back to top |
|
|
moocha Watchman
Joined: 21 Oct 2003 Posts: 5722
|
Posted: Mon Aug 22, 2005 7:52 pm Post subject: |
|
|
What kernel version and patchset?
Are you using NvAGP or agpgart?
Do you perhaps have AGP fast writes enabled? Code: | cat /proc/driver/nvidia/agp/status | should tell you whether that's the case (and could you post the output?) _________________ Military Commissions Act of 2006: http://tinyurl.com/jrcto
"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin |
|
Back to top |
|
|
ChristyMcJesus Apprentice
Joined: 02 Oct 2004 Posts: 184
|
Posted: Mon Aug 22, 2005 7:52 pm Post subject: |
|
|
This happened to me for awhile, I never found out what was causing it. Upgrading to 2.6 fixed it, but since you're already using 2.6 I have no idea. |
|
Back to top |
|
|
rubik-wuerfel n00b
Joined: 29 Sep 2004 Posts: 53 Location: Goettingen, Germany
|
Posted: Mon Aug 22, 2005 8:52 pm Post subject: |
|
|
adsmith wrote: | 1. are you running Xcomposite? (transparency/shadow support) If so, disable it, as it is experimental and usually conflicts with opengl |
This was the first thing I thought about as well at first so: No, it's disabled
adsmith wrote: | 2. this could easily be an overheating problem. Have you watched the CPU and GPU temp? | I don't think so, as I said, it happens very irregularly, sometimes only after 10 minutes and sometimes after some hours... But maybe I shuld write a cronjob to log this. Or do you know if it is logged anyway already somewhere?
moocha wrote: | What kernel version and patchset? |
gentoo-sources-2.6.12-r-something, nothing else, nothing special.
moocha wrote: | Are you using NvAGP or agpgart? | I didn't specify anything special in the xorg.conf, so this should default to agpgart, right?
moocha wrote: | Do you perhaps have AGP fast writes enabled?[...] (and could you post the output?) | Sure, here it is:
Code: | Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled | so obviously: yes
And I'm glad that I'm not the only one, ChristyMcJesus
For completeness' sake, my xorg.conf:
Code: | # File generated by xf86config.
#
# Copyright (c) 2004, by the X.Org
#
# 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 X.Org shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# X.Org.
#
# **********************************************************************
# 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"
# Load "hyperpen"
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Extensions"
# Option "Composite" "Enable"
Option "RENDER" "Enable"
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/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/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.
# 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 "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 X.Org
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
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 "pen"
Driver "aiptek"
Option "Device" "/dev/input/event2"
Option "Type" "Stylus"
Option "Mode" "absolute"
Option "Cursor" "Stylus"
Option "USB" "on"
Option "KeepShape" "on"
Option "debuglevel" "10"
# Option "SendCoreEvents" "on"
EndSection
Section "InputDevice"
Identifier "cursor"
Driver "aiptek"
Option "Device" "/dev/input/event2"
Option "Type" "cursor"
Option "Mode" "absolute"
Option "Cursor" "puck"
Option "USB" "on"
Option "KeepShape" "on"
Option "debuglevel" "20"
# Option "SendCoreEvents" "on"
EndSection
Section "InputDevice"
Identifier "eraser"
Driver "aiptek"
Option "Device" "/dev/input/event2"
Option "Type" "eraser"
Option "Mode" "absolute"
Option "Cursor" "stylus"
Option "USB" "on"
Option "KeepShape" "on"
Option "debuglevel" "20"
# Option "SendCoreEvents" "on"
EndSection
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
VendorName "HWP"
ModelName "HP D8901"
# 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.
# Values given by monitor
# HorizSync 30-70
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.
# Values given by monitor
# VertRefresh 50-120
# Experimental Values
VertRefresh 65-120
# Modeline für "nv"-Treiber
# ModeLine "1280x1024" 108.00 1152 1232 1360 1600 864 865 868 900 +hsync +vsync
# ModeLine für "nvidia"-Treiber
ModeLine "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# Gamma-Farbeinstellungen
Gamma 1.1 1.1 1.1
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 "Nvidia Karte"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "GeForce FX 5700 Ultra"
VideoRam 131072
Option "RenderAccel" "true"
Option "AllowGLXWithComposite" "true"
# 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 "Nvidia Karte"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 16
Modes "1152x864" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1152x864" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents" and "AlwaysCore".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# A special Layout for the use of a graphic tablet
Section "ServerLayout"
Identifier "tablet"
Screen "Screen 1"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
# Now the tablet devices
InputDevice "pen" "AlwaysCore"
# InputDevice "cursor" "AlwaysCore"
# InputDevice "eraser" "AlwaysCore"
EndSection
|
|
|
Back to top |
|
|
MighMoS Guru
Joined: 24 Apr 2003 Posts: 416 Location: @ ~
|
Posted: Thu Aug 25, 2005 6:14 pm Post subject: |
|
|
I also have this problem. Let me guess? In your logs there are Xid: messages? If so, than its an nVidia problem, with no fix, yet. You could try giving them a bug report, but I did, and after telling me to disable fastwrites and SBA, they weren't really much help. _________________ jabber: MighMoS@jabber.org
localhost # export HOME=`which heart` |
|
Back to top |
|
|
BadSquishy n00b
Joined: 17 Jun 2005 Posts: 44 Location: Northern California
|
Posted: Mon Sep 05, 2005 8:58 pm Post subject: System Freeze during heavy 3D gaming [solved for me] |
|
|
Check bottom of post for explaination of solved for me
I think I'm having the same problem, (if you think my problem is different, let me know and I'll start a new thread).
Sometime in the last several weeks one of the updates must have had a very negative effect on my system. Gaming was rock solid and I could play UT2004 or Doom 3 for hours with no problem. Then I didn't play games for a few weeks, and during this time I was keeping my packages up-to-date a couple of times each week with the usual emerge --sync followed by emerge -avuD world.
Now when I play UT2004 or Doom3 the system completely freezes after just a few minutes of game play. It will get through the 2D parts of the game just fine (starting, loading, menus work, etc.) but when I am actually playing it will always freeze, sometimes within seconds of the game starting and sometimes it will work for a few minutes. When it freezes everything stops, whatever was on the screen at the instant of crash stays displayed and a very short burst of the current audio plays over and over, the keyboard and mouse stop working all together and I have to do a hard reboot.
Unfortunately I do not know what my "last known stable" configuration was, and I've been trying to fix it the wrong way all weekend (I've changed everything at least once).
I am using a GeForce FX 5900 video card and an Nforce 2 motherboard. I have tried every version of nvidia-kernel and nvidia-glx from the stable up to the current ~x86. I have stuck to using the ~x86 version of nforce-audio because it has worked fine for months and the stable version doesn't reproduce sound properly on my system. I am pretty sure my "last know stable" configuration was on kernel 2.6.12-r4, however since this problem appeared I have tried the 2.6.12-r4, 2.6.12-r9 and 2.6.12-r10 kernels and it still happens. Of course I emerge nforce-audio and nvidia-kernel every time I change the /usr/src/linux link.
Also, in case it helps:
Code: | meerkat pico # cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled |
If anyone has any idea it would be greatly appreciated. MighMoS mentioned Xid: messages in the logs, I am not finding anything like that, but I am not finding much of anything after startup and login, so I will research increasing system verbosity.
Edit: I found out what my problem was, I do not know if it applies to everyone else on this thread
For my system this was the beginning of a complete deterioration. I believed this was a Linux problem because when it first started I could still play 3D games if I booted to Windows XP, but soon all 3D gaming stopped working, then anything that stressed out the CPU, like ripping DVD's, stopped working as well. In Linux the system would continue to just freeze when you tried to do something. In Windows the computer had a tendency to just spontaneously reboot when under stress.
The problem was with my motherboard, my computer was suffering from capacitor plague
http://en.wikipedia.org/wiki/Capacitor_plague
Almost all of the larger capacitors looked just like those pictured in the article, I have replaced the motherboard and now I can play games again (at least in windows, I'm having trouble getting 3D and sound running again in Linux, but for reasons unrelated to capacitor plague). If you are suffering from random freezes, spontaneous reboot, or your computer is just suddenly completely dead, check out your capacitors, especially of your motherboard was manufactured in certain years (I think 2002 to 2004).
Hope this helps.
BadSquishy |
|
Back to top |
|
|
sulu Guru
Joined: 21 May 2002 Posts: 399 Location: Dornbirn/Austria
|
Posted: Wed Oct 26, 2005 10:06 am Post subject: |
|
|
Sorry for bumping this sleeping thread but i am experiencing exactly the same behavior in OpengGL games as the original poster described them in the first post of this thread.
UT2004 starts fine and plays well but suddenly the system is locked and very strange colors appear on the monitor.
Sometimes i can hear the sound of the game for a short time but then only a reset helps (no ssh-login possible from another box).
The last crash did not came that unexpected because a minute or so before dying i noted some false coloring of the textures.
I tried the new Nvidia-drivers (1.7XXX and masked for amd64) and this lead to an improvement insofar as the game takes longer to crash.
BadSquishy:
I did check my board for any sign of capacitor plague but could not find anything.
In order to confirm that my hardware (see signature for details) is ok i booted Win-XP and ut2004 just ran fine there.
It is the 32-Bit-Version of XP so it could be an AMD-64-Issue. _________________ AMD64-Phenom2 940, ASUS M4??-Deluxe-Board , 8 GB-RAM , 1*1TB SATA HDD , 1*750GB SATA Hd, NVIDIA GTX 260 |
|
Back to top |
|
|
Lord Spector Guru
Joined: 28 Oct 2003 Posts: 304
|
Posted: Wed Oct 26, 2005 6:21 pm Post subject: |
|
|
This is a long shot but did you by any chance overclock your card? _________________ It's all about open source |
|
Back to top |
|
|
sulu Guru
Joined: 21 May 2002 Posts: 399 Location: Dornbirn/Austria
|
Posted: Thu Oct 27, 2005 7:22 am Post subject: |
|
|
Quote: | This is a long shot but did you by any chance overclock your card? |
Nope. Totally vanilla.
You see for ut2004 this card has easily enough horse power.
Maybe it is a HW-issue but to rule that out i have to do some heavy gaming in Win-XP. _________________ AMD64-Phenom2 940, ASUS M4??-Deluxe-Board , 8 GB-RAM , 1*1TB SATA HDD , 1*750GB SATA Hd, NVIDIA GTX 260 |
|
Back to top |
|
|
groover n00b
Joined: 04 Jan 2004 Posts: 38
|
Posted: Wed Feb 15, 2006 1:43 pm Post subject: |
|
|
Hm, same problem here since a very long time...
My (current) hardware:
Athlon XP 3200+ (512kb cache)
Asus A7N8X-XE (NForce2)
nVidia NV43 [GeForce 6600/GeForce 6600 GT]
2 gigabyte OCZ DDR-RAM (PC3200, 2-3-5-2)
Creative Labs SB Live! EMU10k1
Notes:
During the time the problem first occured on my machine and today I switched almost all of that.
I changed the processor (Athlon XP 2600+ to XP 3200+). The problem resists.
After a while I changed the graphic board (overall I tested system stability with 5 different NVidia graphic boards). The problem resists.
I changed my memory and shortly after that my mainboard (switching from Via KT600 to NForce2).
Whatever I did regarding to hardware: The problem resists.
Mainly I want to play Enemy-Territory (which freezes my system completely), but the same behaviour is with almost any GL game, especially Q3- Engine- based games.
Software:
The problem came up with kernel 2.6.10, I think (I'm not really sure about that).
Currently I'm running Linux 2.6.16-rc2 with Nitro1 patchset.
nvidia-kernel: 1.0.8178-r3
nvidia-glx: 1.0.8178
It doesn't matter what I am trying about that. Any recent nvidia versions have this problem, any kernel. Vanilla from 2.6.10 up to morph 2.6.12, ck, cko, Nitro; any versions.
Software Setup:
AGP:
Code: | cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: NVIDIA
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled |
This is my *current* setup! It is not influenced by my settings, the nvidia.ko- module *autodetects* that.
I tried:
- using AGPGART: performance is too low
- using SBA disabled (as often mentioned here and in the NVidia docs)
- using Fast Writes and SBA enabled
- setting __GL_SINGLE_THREADED to 1 (NVidia docs)
- disabling local APIC on UP (NVidia docs)
... and everything vice versa.
The problem resists: OpenGL games randomly freezes my machine completely.
Is it possible that setting the RTC frequency is a reason for that? (sysctl -w dev.rtc.max-user-freq=1024)
My system runs really fine and stable, except GL games :(
I don't think that I have hardware problems at all (changing all and the problem resists).
I don't think, that this is X related (but I don't know for sure).
I can imagine this is a kernel problem... But I don't know how to start debugging my kernel configuration, and there is not much time for me to do this.
Additions:
I'm not using Xcomposite.
In games GPU heat is around 73 degrease celsius. CPU is at 52, 53.
There are no "Xid"- messages in my system logs.
No oops- messages at all.
I do not overclock my graphic board.
Next additions
Perhaps something with the soundcard? This is the only hardware I did not change in the last two or three years.
alsa-lib-1.0.11_rc3
alsa-headers-1.0.11_rc3
alsa-utils-1.0.11_rc2
are currently installed.
I used to do the following in /proc
Code: | echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
echo "et.x86 0 0 disable" > /proc/asound/card0/pcm0c/oss
|
Any help, ideas, whetever,
thanks a lot!
groover _________________ If I was you, I'd like to be me. |
|
Back to top |
|
|
groover n00b
Joined: 04 Jan 2004 Posts: 38
|
Posted: Sat Feb 18, 2006 1:19 am Post subject: |
|
|
Latest news
I tested another OpenGL- Game, Postal2, which runs really fine in 1600x1200 with Hardware 3D- accelerated sound and high graphic details.
Directly after playing about an hour GPU was at 53 degreese.
I'm not sure for now, it needs to be more testing, but:
I enabled my onboard sound chip (MCP2S) and setup Enemy-Territory using that device, and everything seems to work.
I'm going to do some more testing this weekend and let you know.
Regards,
groover _________________ If I was you, I'd like to be me. |
|
Back to top |
|
|
groover n00b
Joined: 04 Jan 2004 Posts: 38
|
Posted: Sun Feb 19, 2006 12:44 am Post subject: |
|
|
Latest news
I played about 3 hours now, yesterday two times about an hour, started Enemy-Territory a lot of times: No freeze.
Is there anything kwown about emu10k1 freezes a system?
More and more I think, it is my emu10k1 causing these freezes.
Any other experiences?
What about these guys here having the same problem? Do you use emu10k1 sound cards?
Regards,
groover _________________ If I was you, I'd like to be me. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|