Re : R3XX lockup possible solution
pzubaj at gaya.sk
Sun Jun 25 04:43:33 PDT 2006
Use primary. Try to comment out every row in r300init.c which contains
0x0000140 (do not comment out already commented rows). This should
prevent screen corruption).
On Sun, 2006-06-25 at 15:26 +0400, Elie Morisse wrote:
> Le 24.06.2006 19:27:02, Jerome Glisse a écrit :
> > Attached is the possible initialization we lack for r3xx chipset, might also
> > be usefull for r4xx. I am still not 100% confident that this solve lockup but
> > i have been able to run things a lot longuer than before without lockup.
> > Thus i want other people to test this and report if this solve any lockup
> > they might experience with r3xx/r4xx and DRI.
> > To use this change the #define ADDR to your card ADDR (use lspci -v)
> > then gcc r300init.c -o initr300 quit any X, go the console run sync, launch
> > the program (as root) rerun X and test with app which used to lockup.
> > You will have to press several time a key to go over initialization
> > step in the program if it lockup your computer please report last
> > things you see printed.
> > Report your status.
> > PS: Sorry for cross posting but i wanted to have as many tester as possible.
> > best,
> > Jerome Glisse
> > To get the ADDR use lspci -v then this is second Memory at line of your
> > graphic card for example:
> > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 NJ
> > [Radeon 98 00 XT] (prog-if 00 [VGA])
> > Subsystem: Micro-Star International Co., Ltd.: Unknown device 9560
> > Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 177
> > Memory at f0000000 (32-bit, prefetchable) [size=128M]
> > I/O ports at c000 [size=256]
> > Memory at fe9f0000 (32-bit, non-prefetchable) [size=64K]
> > Expansion ROM at fe9c0000 [disabled] [size=128K]
> > Capabilities: <available only to root>
> Glimmer of hope didn't bright long enough :'( , this doesn't seem to fix any lockup for me. I tested Half-Life, Deus Ex, Hitman 2 and Jedi Outcast; differently to another feedback those games have always been working but lockup after a few minutes.
> However i noticed that lspci displays different ADDR for primary and secondary.. on bugzilla you were peeping out the secondary entry while on ml this is the primary one. Here's my lspci output :
> 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (prog-if 00 [VGA])
> Subsystem: ATI Technologies Inc Unknown device 0002
> Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 19
> Memory at d8000000 (32-bit, prefetchable) [size=128M]
> I/O ports at d000 [size=256]
> Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
> [virtual] Expansion ROM at e8000000 [disabled] [size=128K]
> Capabilities: <access denied>
> 02:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (Secondary)
> Subsystem: ATI Technologies Inc Unknown device 0003
> Flags: stepping, 66MHz, medium devsel
> Memory at e0000000 (32-bit, prefetchable) [disabled] [size=128M]
> Memory at e9010000 (32-bit, non-prefetchable) [disabled] [size=64K]
> Capabilities: <access denied>
> First i tried the primary one (e9000000), but it screwed up both text mode and X, when the second one(e9010000) worked with some "RD errors" but obviously makes no difference for the games above. Which one should be the correct one ?
> xorg mailing list
> xorg at lists.freedesktop.org
> Informacia od NOD32
> Tato sprava bola skontrolovana antivirovym systemom NOD32.
> [ Projekt gaya | www.gaya.sk ]
More information about the xorg