--- [EMAIL PROTECTED] wrote:
> sorry, now permissions are ok.
>
> don't know what is problem. can you give me description like this how
> things
> work:
>
> savage_hardware <-> kernel_drm <-> xfree_savage 2d or/and 3d
>
>
It looks something like this:
hardware <-> 2d driver
hardware <-> DRM
sorry, now permissions are ok.
don't know what is problem. can you give me description like this how things
work:
savage_hardware <-> kernel_drm <-> xfree_savage 2d or/and 3d
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linu
--- [EMAIL PROTECTED] wrote:
> I have aspire 1300, with s3 savage twister (8d02),
>
> http://62.44.212.64:8080/s3_ProSavage_KN133/
>
> look there. I compiled some time ago savage cvs and dri is now
> enabled, but I
> think it isn't still working.
>
You need to change the permissions on those f
Dave Airlie wrote:
Well I've traced this a bit, an operation appears to be hanging the
chipset,
Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK
or HW_UNLOCK defined for the i830 has something happened elsewhere that
makes these unnecessary,
There are the i830SpanRenderStar
Well I've traced this a bit, an operation appears to be hanging the
chipset,
Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK
or HW_UNLOCK defined for the i830 has something happened elsewhere that
makes these unnecessary,
what blender seems to be doing is loading up a s
On Mon, 19 Jan 2004, Ian Romanick wrote:
> > Hi. I have the Intel i810 video card and I have a problem. The 3D
> > application Blender(www.blender3d.org) is crashing the whole computer
> > when in 16 bit depth mode only. And 16 bit is the only way i can have
> > direct rendering enabled. When
[EMAIL PROTECTED] wrote:
Hi. I have the Intel i810 video card and I have a problem. The 3D application Blender(www.blender3d.org) is crashing the whole computer when in 16 bit depth mode only. And 16 bit is the only way i can have direct rendering enabled. When it crashes it doesn't respond to
David Dawes wrote:
>On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
>
>>>From: Angel [mailto:[EMAIL PROTECTED]]
>>>
>In a solution to this i decided to upgrade to
>the DRI-CVS, however when making World it ends with the
>following error.
>/usr/i386-slackware-li
On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
>> From: Angel [mailto:[EMAIL PROTECTED]]
>> > > In a solution to this i decided to upgrade to
>> > > the DRI-CVS, however when making World it ends with the
>> > > following error.
>> > > /usr/i386-slackware-linux/bin/ld: cannot
> From: Angel [mailto:[EMAIL PROTECTED]]
> > > In a solution to this i decided to upgrade to
> > > the DRI-CVS, however when making World it ends with the
> > > following error.
> > > /usr/i386-slackware-linux/bin/ld: cannot find -lXau
> > > collect2: ld returned 1 exit status
> > > make[4]: **
On Tue, 25 Sep 2001, Alexander Stohr wrote:
> Date: Tue, 25 Sep 2001 12:49:25 +0200
> To: <[EMAIL PROTECTED]>
> From: "Alexander Stohr" <[EMAIL PROTECTED]>
> CC: <[EMAIL PROTECTED]>
> Subject: RE: [Dri-devel] No Subject
>
> > I have been runn
> I have been running the X 4.1 release for a while now and
> quite frequently
> it has hard locked my box.
Sorry, but you dont mention what hardware and software you are using.
So far i found the current XFree86 core rather stable myselves.
> In a solution to this i decided to upgrade to
> t
On Thu, 17 May 2001, Frank Worsley wrote:
>First off, apologies all around for not putting in a subject line. I kinda
>forgot about that! ;)
>
>>
>> I made some notes during my installation, I could possibly write
>> something of a howto if you think it would help.
>>
>
>Yeah, it would be very n
First off, apologies all around for not putting in a subject line. I kinda
forgot about that! ;)
>
> I made some notes during my installation, I could possibly write
> something of a howto if you think it would help.
>
Yeah, it would be very nice if you did that.
>
> More or less. this is wh
On Thu, 17 May 2001, Frank wrote:
>> As far as the gotchas, Mandrake 8 has all the kernel modules gzipped up.
>> The install script didn't rename the original radeon.o.gz module. There
>> was also a libGL.1.2.030401 left hanging around in the /usr/X11R6/lib
>> directory.
>
>There have been a lo
15 matches
Mail list logo
