[Bug 7178] New: Mesa 1.5, i810 1.6.0 and xorg-server 1.1.0 crash for any GLX app

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=7178 Summary: Mesa 1.5, i810 1.6.0 and xorg-server 1.1.0 crash for

[Bug 7178] Mesa 1.5, i810 1.6.0 and xorg-server 1.1.0 crash for any GLX app

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=7178 --- Additional Comments From [EMAIL PROTECTED] 2006-06-10 12:15 --- Creat

[Bug 7178] Mesa 1.5, i810 1.6.0 and xorg-server 1.1.0 crash for any GLX app

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=7178 --- Additional Comments From [EMAIL PROTECTED] 2006-06-10 12:16 --- Creat

[Bug 6085] Blender crashes on r300 when right clicking on an item

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=6085 --- Additional Comments From [EMAIL PROTECTED] 2006-06-10 14:53 --- Any

Doom3/r300 problems.

So last night I decided to give the new vertex programs on the r200 driver a shot and to see how doom3 stacked up with the r200 driver vs the fglrx driver now. With both drivers, I was getting approximately 12 FPS with demo1 (with the r200 renderer, of course). This morning I decided to give

Re: Doom3/r300 problems.

Adam K Kirchhoff [2006-06-10 17:54]: > This morning I decided to give the r300 driver a shot, but ran into some > problems: > > http://68.44.156.246/shot-current.jpg > > Everything is shiny and textures are all screwed up :-) I guess this is the same problem I reported earlier: http://marc.thea

Re: Doom3/r300 problems.

Adam K Kirchhoff wrote: > So last night I decided to give the new vertex programs on the r200 > driver a shot and to see how doom3 stacked up with the r200 driver vs > the fglrx driver now. With both drivers, I was getting approximately 12 > FPS with demo1 (with the r200 renderer, of course). >

Re: Doom3/r300 problems.

Rune Petersen wrote: > Adam K Kirchhoff wrote: >> So last night I decided to give the new vertex programs on the r200 >> driver a shot and to see how doom3 stacked up with the r200 driver vs >> the fglrx driver now. With both drivers, I was getting approximately >> 12 FPS with demo1 (with the r

Re: Doom3/r300 problems.

Adam K Kirchhoff [2006-06-10 18:33]: > Rune Petersen wrote: > > Adam K Kirchhoff wrote: > >> So last night I decided to give the new vertex programs on the r200 > >> driver a shot and to see how doom3 stacked up with the r200 driver vs > >> the fglrx driver now. With both drivers, I was getting

Re: Doom3/r300 problems.

Adam K Kirchhoff wrote: > Rune Petersen wrote: >> Adam K Kirchhoff wrote: >>> So last night I decided to give the new vertex programs on the r200 >>> driver a shot and to see how doom3 stacked up with the r200 driver vs >>> the fglrx driver now. With both drivers, I was getting approximately >>

Re: Doom3/r300 problems.

Rune Petersen wrote: > Adam K Kirchhoff wrote: > >> Rune Petersen wrote: >> >>> Adam K Kirchhoff wrote: >>> So last night I decided to give the new vertex programs on the r200 driver a shot and to see how doom3 stacked up with the r200 driver vs the fglrx driver now.

Re: Doom3/r300 problems.

Adam K Kirchhoff wrote: > Rune Petersen wrote: >> Adam K Kirchhoff wrote: >> >>> Rune Petersen wrote: >>> Adam K Kirchhoff wrote: > So last night I decided to give the new vertex programs on the r200 > driver a shot and to see how doom3 stacked up with the r200 driver