d today's version,
> radeon-20010417-i386-Linux.tar.gz thinking that it would fail today
> again But somehow, it works like a charm! I don't know who fixed
> this bug, but anyway good job! BUt I still have problems with it. At
> first, after returning to text mode,
Great news
Just after I posted those messages, I tried today's version,
radeon-20010417-i386-Linux.tar.gz thinking that it would fail today
again But somehow, it works like a charm! I don't know who fixed
this bug, but anyway good job! BUt I still have problems with it.
And I would like to know what is the difference between Raden DDR and
SDR from the software view point.
[EMAIL PROTECTED] wrote:
>
> I am the one who reported this issue on dri-users mailing list as John X
> says. This problem is that DRI works perfectly except that many 'random
> dots" appear o
I am the one who reported this issue on dri-users mailing list as John X
says. This problem is that DRI works perfectly except that many 'random
dots" appear on the screen and they flash as other portion of the screen
refresh. The DRIsetup program and glxinfo say DRI is correctly set
up. I had
Alan Hourihane <[EMAIL PROTECTED]> writes:
> On Fri, Apr 06, 2001 at 11:04:20AM -0400, Trond Eivind Glomsrød wrote:
> > When building the DRI tree with DRM module for the kernel, the default
> > location to look for headers should be (this is the way Linus started
> > recommending last summer, if
Getting the following (and tired of many lines of ? when I do a cvs up), I've
prepared some .cvsignore files for the trunk and mesa-3.5 branch of dri cvs.
make[4]: *** No rule to make target
`../../../../extras/Mesa/src/api_arrayelt.c', needed by `api_arrayelt.c'.
Stop.
Bill
--
Leave others the
Hello!
Are there known blending bugs in the mga-driver (g400)? When I render many
additive polygons on the top of each other with small alpha-value
(something like 0.05) the result is something it shouldn't be with g400.
With software-mesa it's correct as well as with nvidia's drivers.
If this
What's the current status for the ATI Rage Mobility driver?
Robert Johansson * [EMAIL PROTECTED] * +46 (0)7 39 8000 39
In pursuit of a M.Sc. in Computer Science
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/
On Mon, Apr 16, 2001 at 12:02:04PM -0700, Frank Worsley wrote:
> > Odd, I could swear there was one back on the 10th when I d/l'd them
> > last... I remember having to d/l it because I was getting a PCI bus
> > master symbol error in the r128 drivers
>
> Yes, there was an Extras package ther
On Tue, 17 Apr 2001, Keith Whitwell wrote:
> I haven't heard any reports of this working in a long time.
>
> The author is Sung-Ching Lin <[EMAIL PROTECTED]>; try and contact him. If we
> don't hear anything the driver should be disabled & removed from the supported
> cards list.
Hm...
Anybody
On Tue, 17 Apr 2001, Keith Whitwell wrote:
> > Any plans for SiS support? Anybody knows who did the actual work in the
> > kernel? Who is the maintainer? I would like to help in some way.
> >
> > Thanks in advance.
> >- Ademar
>
> I haven't heard any reports of this working in a long time.
>
"Ademar de Souza Reis Jr." wrote:
>
> Hello all.
>
> I'm trying to "play" with DRI support for SiS boards on xf-4_0_3 branch.
>
> After some work, everything is loaded and the log reports it's
> working, but when I try to start any app that uses it (ex. tuxracer
> or quake3), I get:
>
> SIS dr
Hello all.
I'm trying to "play" with DRI support for SiS boards on xf-4_0_3 branch.
After some work, everything is loaded and the log reports it's
working, but when I try to start any app that uses it (ex. tuxracer
or quake3), I get:
SIS driver : out of video memory
Fatal errors in sis_dri.so
13 matches
Mail list logo
