>> the subject says it: glxgears (and all other OpenGL-based programs)
>> abort with the message:
>> "drmR128SwapBuffers = -14"
>>
>> My configuration:
>> Kernel 2.4.6
>> XFree86 4.1.0
>> ATI AIW 128 Pro
>> newly compiled drm kernel modules, r128 XFree86 driver, r128_dri.so,
>> etc.
>
>Do you hav
On Thu, 4 Oct 2001 19:40, Dieter Nützel wrote:
> Hello all,
>
> after your latest fixes I've to report the following issues together with
> my Voodoo5 5500 AGP.
>
> First of all:
> Do I have to use the Mesa-4.0 CVS tree?
> Keith what was the name of the path variable, again?
No.
> 1. UT 436 sho
On Thursday 04 October 2001 12:30, you wrote:
> Hardly, as this thread is about incorrect rendering, not lockups.
Ooops... Could have sworn that it was about lockups (since I get that with
my wife's machine with gears...)- that's what I get for trying to pass the
time during compiles, etc. up
Hello all,
after your latest fixes I've to report the following issues together with my
Voodoo5 5500 AGP.
First of all:
Do I have to use the Mesa-4.0 CVS tree?
Keith what was the name of the path variable, again?
1. UT 436 show a mirror hall effect (it seems to me that there are some
redraw/f
On Fri, 2001-10-05 at 00:08, Nathan Hand wrote:
> XV is completely independent of V4L and the DRI.
This is true conceptually and was true implementation-wise until
recently. However, the r128 driver uses the DRM to transfer the XvImage
data now when possible, and Peter Surda has been bug^Wasking
On Thu, 2001-10-04 at 21:57, Steven P. Lilly wrote:
> Sorry to have bothered everyone. I downloaded the source to glxgears and
> found the problem. It wasn't setting up the viewport properly until the
> reshape function got called. With a window manager it gets called right away
> when the window
On Tue, Oct 02, 2001 at 05:39:25PM -0400, [EMAIL PROTECTED] wrote:
> With linux, it will say something along the lines of "works with Redhat
> 6.2". (take a look at many CAD packages, for example - they are _not_ very
> graphics intensive). Games are even trickier. I have not bought a single
> Lok
On Wed, Oct 03, 2001 at 10:47:08AM +0200, Michael Zayats wrote:
> I will present my problem in it's full, may be you will help me:
>
> I am grabbing frames from bt848 and should both store them for future reuse
> and get them on the screen. The box is i810 based and has many other tasks
> to do.
Sorry to have bothered everyone. I downloaded the source to glxgears and
found the problem. It wasn't setting up the viewport properly until the
reshape function got called. With a window manager it gets called right away
when the window is created without one it doesn't ever get called.
__
On Thu, 4 Oct 2001 12:55, Zephaniah E\. Hull wrote:
> On Thu, Oct 04, 2001 at 10:32:15AM -0600, Keith Whitwell wrote:
> > On Wed, 3 Oct 2001 19:19, Zephaniah E\. Hull wrote:
> > > The current mesa-3-5-branch code has a bug dealing with GL_QUADS,
> > > suffice it to say that it results in some, i
On Wed, 3 Oct 2001 19:19, Zephaniah E\. Hull wrote:
> The current mesa-3-5-branch code has a bug dealing with GL_QUADS,
> suffice it to say that it results in some, interesting, rendering bugs.
>
Actually I think the loop should read
for (i = start; i < count - 4; i+=4) {
ie. a less-th
On Wed, 3 Oct 2001 19:19, Zephaniah E\. Hull wrote:
> The current mesa-3-5-branch code has a bug dealing with GL_QUADS,
> suffice it to say that it results in some, interesting, rendering bugs.
Looks like a cut&paste bug. I'll commit the fix.
Keith
On Thu, 2001-10-04 at 17:58, Frank Earl wrote:
> On Thursday 04 October 2001 07:06, Michel Dänzer wrote:
> > On Thu, 2001-10-04 at 03:56, Steven P. Lilly wrote:
>
> > Everything else seems to work fine, which points at a glxgears bug?
>
> I encountered something very similar with glxgears when I
On Thursday 04 October 2001 07:06, Michel Dänzer wrote:
> On Thu, 2001-10-04 at 03:56, Steven P. Lilly wrote:
> Everything else seems to work fine, which points at a glxgears bug?
I encountered something very similar with glxgears when I was attempting to
get RagePRO DMA operation working for U
On Thu, 2001-10-04 at 16:28, Huber, Matthias 6667 SFA-31 wrote:
> the subject says it: glxgears (and all other OpenGL-based programs)
> abort with the message:
> "drmR128SwapBuffers = -14"
>
> My configuration:
> Kernel 2.4.6
> XFree86 4.1.0
> ATI AIW 128 Pro
> newly compiled drm kernel modules,
Take your kernel upto 2.4.10 and you'll be o.k.
Alan.
On Thu, Oct 04, 2001 at 04:28:33PM +0200, Huber, Matthias 6667 SFA-31 wrote:
> Hi,
>
> the subject says it: glxgears (and all other OpenGL-based programs)
> abort with the message:
> "drmR128SwapBuffers = -14"
>
> My configuration:
> Kernel
Hi,
the subject says it: glxgears (and all other OpenGL-based programs)
abort with the message:
"drmR128SwapBuffers = -14"
My configuration:
Kernel 2.4.6
XFree86 4.1.0
ATI AIW 128 Pro
newly compiled drm kernel modules, r128 XFree86 driver, r128_dri.so,
etc.
glxinfo works fine, showing direct ren
On Thu, 2001-10-04 at 03:56, Steven P. Lilly wrote:
> > > > > I just installed Slackware 8 with XFree86 4.1.0 and I've come across
> > > > > some weirdness with glxgears. When I'm running a window manager
> > > > > everything is fine but when I don't run a window manager I get a much higher
>fram
18 matches
Mail list logo
