On Thursday 24 November 2005 20:18, Josh Babcock wrote:
> Stefan Seifert wrote:
> > Mathias Fröhlich wrote:
> >> On Donnerstag 24 November 2005 04:44, Ampere K. Hardraade wrote:
> >>> X Error of failed request:  GLXUnsupportedPrivateRequest
> >>>   Major opcode of failed request:  145 (GLX)
> >>>   Minor opcode of failed request:  16 (X_GLXVendorPrivate)
> >>>   Serial number of failed request:  30
> >>>   Current serial number in output stream:  31
> >>
> >> Well, as far as I can see and remember:
> >> The client libraries send a request to the 'display system' and the
> >> 'display system' bails out with an 'unsupported request'.
> >> The error message is somehow misslieading, since the problem happens
> >> when communicating with dri/drm instead of the X server - the reason I
> >> called it 'display system' above.
> >
> > I just wanted to note, that when it is clear, that it's a bug in ATI's
> > drivers, someone should post a bugreport in the ATI driver Bugzilla:
> > http://ati.cchtml.com/
> > This is actually a place where driver developers are watching and a good
> > chance that such bugs get fixed. Before posting, you should read the
> > instructions at: http://www.rage3d.com/board/showthread.php?t=33799828
> > which is btw. a thread in _the_ most useful forum for Linux using ATI
> > card owners: http://www.rage3d.com/board/forumdisplay.php?f=88
> >
> > Nine
> >
> > _______________________________________________
> > Flightgear-devel mailing list
> > Flightgear-devel@flightgear.org
> > http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > 2f585eeea02e2c79d7b1d8c4963bae2d
>
> I'm not sure if it's the same one, but I have been following this one:
> http://ati.cchtml.com/show_bug.cgi?id=232
> Doesn't seem to be any progress yet though.
>
> Josh


Ampere says that they are not the same bug.

Paul


_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to