| Summary: | nvidia: 3D games freezes after a short while (tried with enemy-territory, tuxracer) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Mieland <dma147> |
| Component: | [OLD] Unspecified | Assignee: | X11 External Driver Maintainers <x11-drivers> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | iyosifov, radek |
| Priority: | High | ||
| Version: | 2004.3 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Alexander Mieland
2005-03-23 00:41:07 UTC
btw: I've also reinstalled the whole gentoo, tried older versions of nvidia-(glx|kernel), xorg-x11, changed from udev to manually managed device nodes and back... nothing helps... Can't this be a temperature-related problem? Have you tried to run glxgears in fullscreen? I don't think that this is a temperature problem, because I've the following *maximum* temperatures (tested during builds) CPU: ~49 I don't think that this is a temperature problem, because I've the following *maximum* temperatures (tested during builds) CPU: ~49°C mainboard: ~32°C HDD1: ~29°C HDD2: ~31°C So I don't think that the graphics card could be more hot than these components. And, btw. it worked great a few weeks ago. Without any changes on the hardware. sorry, forgotten... No I've not tried to run glxgears in fullscreen... And I really don't want to need to install a new gentoo again, because some important files got lost during those tests. These temperatures are cold-as-ice compared to mine which means I have no idea what can be the problem... :-( What card do you have and how long have you had it? Also do you have...*wills self to say it*...Windows installed? Do you have any issues there if so? It's a Nvidia Geforce 5600 FX and it is one year old. I've had absolutly no windows since about five years now. So no chance to test it with windows. Sorry, forgotten... I've tested yesterday some other configurations and resolutions. It seems that I can play enemy-territory with 640x480 without problems. I've played it yesterday for about one hour and it did not crash again. But I've already played it with 1024x768 and other resultions without problems a few weeks ago... so it seems that the graphics card is out of order... That may be. One thing to try would be to play with graphics-related BIOS settings, such as AGP aperture, Fastwrites, VGA BIOS caching, etc... However, if other people have had the same problems, that may not be the case. Upping the resolution means that the drivers have to access more functionality of the card and thus may still be a driver issue. Try to play with some hardware settings and see what happens. I have the same problem with nforce2 integrated video, but have also tried AGP geForce 4Mx. The system is hanging if i launch any gl app for 2 or more times. glxgears don't hang even in fullscreen. I've tried a couple of linux kernels from 2.6.10 and different nvidia display driver versions (from 6111) - it crashes everytime. It worked fine on 2.6.8 with any nvidia-kernel version. emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3, glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r7 i686) ================================================================= System uname: 2.6.10-gentoo-r7 i686 Unknown CPU Type Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 17 2005, 17:45:58)] distcc[32550] (dcc_mkdir) ERROR: mkdir /var/tmp/portage/homedir/.distcc/state failed: No such file or directory [disabled] ccache version 2.3 [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.9.5, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 CCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=i686 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=i686 -O2 -pipe -fomit-frame-pointer" DISTDIR="/home/gentoo/distfiles" FEATURES="autoaddcvs autoconfig buildpkg distlocks prelink sandbox sfperms strict" USE="x86 X a52 aac aalib acpi acpi4linux activefilter alsa apache2 apm arts artswrappersuid audiofile avi bash-completion bitmap-fonts bluetooth cddb cdparanoia cdr crypt cups curl dga dv dvd dvdr dvdread eds emboss encode esd exif fam ffmpeg flacfoomaticdb gd gif gnome gphoto2 gpm gstreamer gtk gtk2 guile hal iconv imagemagick imlib innodb java jpeg jpeg2k junit kde kdeenablefinal libg++ libwww lm_sensors logitech-mouse lufsusermount lzo mad maildir mbox mikmod mjpeg mmx motif mozilla mp3mpeg mppe-mppc ncurses no-old-linux no_wxgtk1 nomotif nptl nptlonly odbc ogg oggvorbis opengl pam pcre pdflib pic png pwdb qt quicktime readline real rtc ruby samba sdl slang slp spell sqlite ssl symlink tetex threads tiff transcode truetype truetype-fonts unicode usb utf8 v4l v4l2 vcdimager vorbis wifi xine xml xml2 xv yv12 zlib linguas_ru userland_GNU kernel_linux elibc_glibc" This is a well known problem, its a problem with the nvidia driver which is discussed here. http://www.nvnews.net/vbulletin/showthread.php?t=49117&highlight=Xid Since the nvidia driver is "unified," meaning the same code is compiled for Linux BSD, Mac, Solaris, and Win it can effect any OS. On Linux the problem can be seen in your kernel log after the crash happens, you can try to switch terminals or ssh into your computer to view dmesg and you will see a bunch of errors about Xid, which basicly mean something screwed up with the video card(nvidia hasnt really said what they mean). Each release seems to help(most of my apps dont get it now and when one does its easy to kill) but it hasnt been fixed. For some reason running glxgears and then a game seems to make it go away. Try that and keep up with the latest nvidia drivers. How is 7676-r1 doing wrt this bug? no response, closing... |
