linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Van Damme <frank.vandamme@student.kuleuven.ac.be>
To: linux-kernel@vger.kernel.org
Subject: stabilty problems using opengl on kt400 based system
Date: Sat, 12 Apr 2003 14:10:58 +0200	[thread overview]
Message-ID: <200304121410.58522.frank.vandamme@student.kuleuven.ac.be> (raw)

Hello,

I have stability problems with my computer when using OpenGl applications. 
First of all, this is the hardware I am using that may be responsible:

- Motherboard: Soltek sl-75fvr with a kt400 chipset
- Cpu: Athlon Xp 2000+
- Video card: Ati radeon 8500 retail, 64 MB ddr.

Software I am using:

- distribution: Debian Sid
- Xfree86: version 4.3, packaged in Debian packages by Daniel Stone
<http://capricorn.woot.net/~daniels/sid/i386/>
- Linux kernel: version 2.4.21-pre5-ac3
- Quake3 + urban terror, tuxracer (old version 0.6), xmms openGL plugins.

The symptoms are as follows. Linux boots fine, the "radeon" kernel module
inserts with no errors. X also starts without problems and runs stably in
day-to-day work and during cpu-intensive tasks such as compiling. However, 
if Istart running OpenGL applications (games) (quake,tuxracer or whatever) 
themachine will freeze in anything from 2 minutes to an hour. The last frame
remains on the screen, but I can still login over ssh and reboot.
The drivers of this card are only stable since the latest XFree86 release, 
butsince I had hours of crashless fun with that card on another motherboard 
(anepox 7kxa which is now broken), and since the agp features of the kt400 
chipsetare only supported since kernel version 2.4.21-pre1, I supposed that 
was thecause of my problems.

Unfortunately I am unable to provide any useful error messages. The kernel 
doesnot oops or panic, there are no messages on stdout/stderr, X's log file 
does notshow anything, idem for syslog. I find only positive messages in 
dmesg:
Mar 30 23:07:34 dionysos kernel: Linux agpgart interface v0.99 (c) Jeff 
HartmannMar 30 23:07:34 dionysos kernel: agpgart: Maximum main memory to use 
for agp memory: 203MMar 30 23:07:34 dionysos kernel: agpgart: Detected Via 
Apollo Pro KT400 chipsetMar 30 23:07:34 dionysos kernel: agpgart: AGP 
aperture is 64M @ 0xe0000000

Mar 30 23:07:44 dionysos kernel: [drm] AGP 0.99 on VIA Apollo KT400 @ 
0xe000000064MBMar 30 23:07:44 dionysos kernel: [drm] Initialized radeon 
1.7.0 20020828 on minor 0Mar 30 23:08:02 dionysos kernel: [drm] Loading R200 
Microcode

If there is anything I overlooked, further info I can provide, let me know.

Thanks in advance,

Frank Van Damme.

-- 
Frank Van Damme    | "Saying 8MB of RAM doesn't do as much anymore is
http://www.        | like saying a gallon of water holds more than it
openstandaarden.be | did in 1988."                    --George Adkins


             reply	other threads:[~2003-04-12 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 12:10 Frank Van Damme [this message]
2003-04-12 15:08 ` stabilty problems using opengl on kt400 based system Mark Watts
2003-04-12 18:10   ` Frank Van Damme
2003-04-12 18:20     ` Mark Watts
2003-04-12 19:26       ` Frank Van Damme
2003-04-13  8:17         ` Mark Watts
2003-04-13  5:52 ` Nuno Silva
2003-04-14  9:16 ` Denis Vlasenko
2003-04-14 13:50   ` Frank Van Damme

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304121410.58522.frank.vandamme@student.kuleuven.ac.be \
    --to=frank.vandamme@student.kuleuven.ac.be \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).