Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6429
--- Additional Comments From [EMAIL PROTECTED] 2006-06-25 01:03 ---
Hi,
I tested this on my card.
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE
[Radeon 9500 Pro] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]
Flags: bus master, stepping, 66MHz, medium devsel, latency 255,
IRQ 21
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
Hi,
Use primary. Try to comment out every row in r300init.c which contains
0x140 (do not comment out already commented rows). This should
prevent screen corruption).
Peter Zubaj
On Sun, 2006-06-25 at 15:26 +0400, Elie Morisse wrote:
Le 24.06.2006 19:27:02, Jerome Glisse a écrit :
Sorry, 0x0140 an not 0x140.
Peter Zubaj
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
On 6/25/06, Peter Zubaj [EMAIL PROTECTED] wrote:
Hi,
I tested this on my card.
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE
[Radeon 9500 Pro] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]
Flags: bus master,
On 6/25/06, Peter Zubaj [EMAIL PROTECTED] wrote:
Hi,
Use primary. Try to comment out every row in r300init.c which contains
0x140 (do not comment out already commented rows). This should
prevent screen corruption).
Try also by commenting out up to print S05, i think the initialization
Hi,
I've been looking at vertex shaders this weekend.
It would appear that attribs are broken. The most straight forward way
to test this it to compare progs/tests/arbvptest3 to progs/tests/vptest3
On my system I get different colors when I resize the window.
Can someone confirm this? (it
Le 25.06.2006 16:30:51, Jerome Glisse a écrit :
On 6/25/06, Peter Zubaj [EMAIL PROTECTED] wrote:
Hi,
Use primary. Try to comment out every row in r300init.c which contains
0x140 (do not comment out already commented rows). This should
prevent screen corruption).
Try also by
Rune Petersen [2006-06-25 16:31]:
I've been looking at vertex shaders this weekend.
It would appear that attribs are broken. The most straight forward way
to test this it to compare progs/tests/arbvptest3 to progs/tests/vptest3
On my system I get different colors when I resize the window.
Tilman Sauerbeck wrote:
Rune Petersen [2006-06-25 16:31]:
I've been looking at vertex shaders this weekend.
It would appear that attribs are broken. The most straight forward way
to test this it to compare progs/tests/arbvptest3 to progs/tests/vptest3
On my system I get different colors
First, I think, you shouldn't touch register 0x140, you write value 0x22
there. For my card there is 0x2D (this is power on default and is not
changed by fglrx). When value 0x22 is written there, I have got
corrupted console and X desktop too.
This is the MC_CNTL register. It contains some
On Sun, 2006-06-25 at 19:57 +0400, Elie Morisse wrote:
Nope, doesn't help :'(
It still get corrupted after i commented out the 0x0140 stuff. I
localized the nasty lines, though :
ptr[0x01F82] = 0x011A;
ptr[0x01FC2] = 0x151557FF;
ptr[0x01F82] =
--- Mike Mestnik [EMAIL PROTECTED] wrote:
The game always(mostly) loads under cedega 5.1.1, but I only get a
working setup now and then.
Mostly the screen is black and no-one seams to know how to test what
'black' means.
I am able to play some times and the game workes just fine!
14 matches
Mail list logo
