Hi, 1.) Is DRI and EXA supposed to work on an M56 chip? Because my system freezes completely, shortly (2-5 sec.) after starting an 3D application. Removing EXA and using XAA (default?) and I can play World of Goo as much as I like! I.e. no system freeze, but having from time to time a few minor glitches in the game. radeonhd version is 1.2.4 build from git branch master, commit ad6c789a. libdrm version is 2.4.0-0.21.fc10 kernel is 2.6.29-rc4. 2.) Using 3D creates interrupt bonus After closing the 3D application, I see an increased interrupt activity from the radeon device. The device seems to fire at 60 HZ after the 3D application is closed. Is it possible to only have this 60 extra interrupts per second while using the 3D interface? Greets thomas -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
2009/2/22 Thomas Meyer <thomas@m3y3r.de>:
1.) Is DRI and EXA supposed to work on an M56 chip? Because my system freezes completely, shortly (2-5 sec.) after starting an 3D application. Removing EXA and using XAA (default?) and I can play World of Goo as much as I like! I.e. no system freeze, but having from time to time a few minor glitches in the game.
Known issue: http://bugs.freedesktop.org/show_bug.cgi?id=18097 No solution yet, unfortunately.
2.) Using 3D creates interrupt bonus After closing the 3D application, I see an increased interrupt activity from the radeon device. The device seems to fire at 60 HZ after the 3D application is closed. Is it possible to only have this 60 extra interrupts per second while using the 3D interface?
Interesting. I think this is the first time something like this has been reported. -- Yang Zhao http://yangman.ca -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Yang Zhao writes:
Known issue: http://bugs.freedesktop.org/show_bug.cgi?id=18097 No solution yet, unfortunately.
One thing I'm curious about though. A whole lot of work has gone into the r6xx-r7xx branch lately, some of which sounds like it might be related to this bug (which is pretty severe, it essentially means there is no usable 3D on r5xx cards). Have any of the changes to the newer hardware branch been relevant to the r5xx stuff (ie, in more general code not in the hardware-specific code)? Are any of the issues found and fixed in the r6xx-specific files also relevant to the r5xx files? Thinking that if they started as a copy of the older file then were tweaked to match the newer hardware, some of the bugs now fixed might also exist in their original, r5xx files. Alec -- Alec Habig, University of Minnesota Duluth Physics Dept. habig@neutrino.d.umn.edu http://neutrino.d.umn.edu/~habig/ -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
2009/2/22 Alec T. Habig <habig@neutrino.d.umn.edu>:
Yang Zhao writes:
Known issue: http://bugs.freedesktop.org/show_bug.cgi?id=18097 No solution yet, unfortunately.
One thing I'm curious about though. A whole lot of work has gone into the r6xx-r7xx branch lately, some of which sounds like it might be related to this bug (which is pretty severe, it essentially means there is no usable 3D on r5xx cards).
Have any of the changes to the newer hardware branch been relevant to the r5xx stuff (ie, in more general code not in the hardware-specific code)?
Everything that has gone into r6xx-r7xx-support has been hardware specific. -- Yang Zhao http://yangman.ca -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (3)
-
Alec T. Habig -
Thomas Meyer -
Yang Zhao