David Smith <[EMAIL PROTECTED]> writes:
> Today I performed a fresh install of sid on an ultra1 200e creator
> and I upgraded the kernel to the CVS version of vger.samba.org. I
> couldn't find any reference to the bugs below in the database, has
> anyone else experienced these?
>
> 1) Running any
On Wed, 1 Aug 2001, David Smith wrote:
> not only given in the framerate difference (~350 vs. 60) but also in the
> XFree86.0.log (as you can see in the bottom of
> http://ultrasoul.com/ultra1/XFree86.0.log) when it creates the DRI GLX
> context:
> FFB: Allocated WID 1 for DRI window.
ok, i am no
Thus spake John Wood ([EMAIL PROTECTED]):
>
>
>
> i have found that i am unable to get any gl based x applications to use
> the hardware. i was mostly testing with xscreensaver-gl applications.
> later, i was able to get some results from the evas stuff, but only when i
> select something bes
hi david
On Wed, 1 Aug 2001, David Smith wrote:
> find any reference to the bugs below in the database, has anyone else
> experienced these?
yes and no. i have a ultra1/170 & creator 3d. i am running unstable with
vgers kernel as well.
> 1) Running any OpenGL program with DRI hardware acclerat
Today I performed a fresh install of sid on an ultra1 200e creator and
I upgraded the kernel to the CVS version of vger.samba.org. I couldn't
find any reference to the bugs below in the database, has anyone else
experienced these?
1) Running any OpenGL program with DRI hardware accleration enable
5 matches
Mail list logo