Re: [Dri-devel] (no subject)

2004-04-02 Thread Alex Deucher

--- [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 files, I can't read them
all.

 How should I first help? More info about my computer and
 configuration? Test
 some settings specially?

From the looks of glxinfo it seems direct rendering is enabled.  what
seems to be the problem?  what fps are you getting in glxgears? 
rendering errors?  There are some issues with twister I was trying to
get worked this week.

Alex

 
 
 
 edie
 


__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-04-02 Thread edie
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 Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-04-02 Thread Alex Deucher

--- [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 - 3d driver

Although it varies somewhat depending on the hardware and the driver.

Alex

__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-26 Thread Dave Airlie

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 string of glBitmaps to
create its frontend, and after a bunch of these a HW_LOCK call
from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have
finished for some reason from the previous one, any ideas why this might
happen?

Dave.


 just happened to have blender here on my system, ran it on my test box
 boom .. kernel goes into a frenzy of (see below), machine stops responding
 to network and everything, kernel is alive (sysrq works for me )

 I'm running FC1 - their 2.4.22-1.2115.nptl kernel with top of CVS i810
 stuff...

 I'll take a look but I'm not exactly fully with the whole 3d graphics card
 and DRI mysteries yet :-)

 Dave.



-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-26 Thread Keith Whitwell
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 i830SpanRenderStart() and i830SpanRenderFinish() callbacks from 
swrast which do the locking now.

what blender seems to be doing is loading up a string of glBitmaps to
create its frontend, and after a bunch of these a HW_LOCK call
from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have
finished for some reason from the previous one, any ideas why this might
happen?
If dma hasn't finished, the worst that will happen is some of the uploaded 
bitmap on the screen will be corrupted.

Maybe the vast number of HW_LOCK calls is an issue?

Keith



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] (no subject)

2004-01-19 Thread Ian Romanick
[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 anything i do and goes to a really colourfull screen and goes crazy.  This never happend before so I am just letting you know if you can fix the problem. =)
Can you post a stack-trace or some other information about the crash? 
Without some data, there's not much we can do. :)



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] No Subject

2001-09-27 Thread Michael Lincoln

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-linux/bin/ld: cannot find -lXau
collect2: ld returned 1 exit status
make[4]: *** [XFree86] Error 1

[...]

A search on google for -lXau yeilds nothing and no one I talk 
to has any
idea what this library is.  

see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.

Well that directory is empty on both my pull of the CVS tree 
and the one
currently on sourceforge as of 1:00 PST.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
If that is the directory you are talking about.

As someone posted in a different reply on a similar problem,
due to restructuring/cleanup the whole tree is inconsistent
at presenet.


That's not true.  The tree IS consistent at present.  Having a full
installation of a recent XFree86 version is now a pre-requisite.  No
building hacks are required.  This is an intentional consequence of
pruning the DRI source tree.

David

May be the DRI compile guide needs updating with this infomation.  I got 
bit by this too and its turning  into a FAQ 8).

Mike




___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-26 Thread Alexander Stohr

 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]: *** [XFree86] Error 1
  [...]
   
   A search on google for -lXau yeilds nothing and no one I talk 
   to has any
   idea what this library is.  
 
  see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
  
 Well that directory is empty on both my pull of the CVS tree 
 and the one
 currently on sourceforge as of 1:00 PST.
 http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
 If that is the directory you are talking about.

As someone posted in a different reply on a similar problem,
due to restructuring/cleanup the whole tree is inconsistent
at presenet.

I would suggest getting this file from regular XFree86 sources or binaries.





___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] No Subject

2001-09-26 Thread David Dawes

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 find -lXau
   collect2: ld returned 1 exit status
   make[4]: *** [XFree86] Error 1
  [...]
   
   A search on google for -lXau yeilds nothing and no one I talk 
   to has any
   idea what this library is.  
 
  see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
  
 Well that directory is empty on both my pull of the CVS tree 
 and the one
 currently on sourceforge as of 1:00 PST.
 http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
 If that is the directory you are talking about.

As someone posted in a different reply on a similar problem,
due to restructuring/cleanup the whole tree is inconsistent
at presenet.

That's not true.  The tree IS consistent at present.  Having a full
installation of a recent XFree86 version is now a pre-requisite.  No
building hacks are required.  This is an intentional consequence of
pruning the DRI source tree.

David
-- 
David Dawes  Email: [EMAIL PROTECTED]
Founder/President, Release Engineer
The XFree86 Project, Inc http://www.xfree86.org/~dawes

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-25 Thread Alexander Stohr

 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
 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]: *** [XFree86] Error 1
[...]
 
 A search on google for -lXau yeilds nothing and no one I talk 
 to has any
 idea what this library is.  

-l instructs the compiler to search for things like lib*.a (possibly
lib*.so as well)
in your case the postfix Xau completes to libXau.a which is
missing for some unknown reason. Maybe it was just not rebuild
or did not get symlinked into the XFree86 exports directory.

see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.

 Also one last problem.  When starting X with
 multible resolutions IE
Modes   800x600 640x480 1024x768 1280x1024
 It starts with a virtual screen bigger then phyiscal screen, 
 that i have to
 move around in to find the edge of.  This is not the behavior 
 selected in
 the config and it does not happen when I only select 1 resolution per
 depth.

When you have virtual screens enabled, the virtual screen area
is at least as big as your biggest X and Y resolution. In your
case you will spot 1280x1024 virtual area if your board has
the caps. Please try man XF86Config for turning virtual screens off.

Hint: you can order the resolutions as you want, i.e. you can start up
with highest and then decreasing by simply listing them reverse.

 Thank you in advance
 -Angel

I think you can advance your system with these hints.
Excuse me tha i am only adressing the basics - thats
the area where i supposed the help is needed for now.

Regards AlexS.




___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] No Subject

2001-09-25 Thread Angel



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 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.

Sorry about that it was late and i was getting frustrated.  I am running a
Matrox G400.

 
  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]: *** [XFree86] Error 1
 [...]
  
  A search on google for -lXau yeilds nothing and no one I talk 
  to has any
  idea what this library is.  
 
 -l instructs the compiler to search for things like lib*.a (possibly
 lib*.so as well)
 in your case the postfix Xau completes to libXau.a which is
 missing for some unknown reason. Maybe it was just not rebuild
 or did not get symlinked into the XFree86 exports directory.
 
 see ~/xc/lib/Xau for the sources, at least with X4.1.0 there it is.
 
Well that directory is empty on both my pull of the CVS tree and the one
currently on sourceforge as of 1:00 PST.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/lib/Xau/
If that is the directory you are talking about.

  Also one last problem.  When starting X with
  multible resolutions IE
 Modes   800x600 640x480 1024x768 1280x1024
  It starts with a virtual screen bigger then phyiscal screen, 
  that i have to
  move around in to find the edge of.  This is not the behavior 
  selected in
  the config and it does not happen when I only select 1 resolution per
  depth.
 
 When you have virtual screens enabled, the virtual screen area
 is at least as big as your biggest X and Y resolution. In your
 case you will spot 1280x1024 virtual area if your board has
 the caps. Please try man XF86Config for turning virtual screens off.
 

I should not have virtual screens enabled.  At least i can not find it if i
do.  The Virtual display option is not and set i have looked through the
XF86Config man page to no avail.  I can run at any resolution and it won't
turn on virtual screens unless there is more the one resolution for the
depth.

 Hint: you can order the resolutions as you want, i.e. you can start up
 with highest and then decreasing by simply listing them reverse.
 
  Thank you in advance
  -Angel
 
 I think you can advance your system with these hints.
 Excuse me tha i am only adressing the basics - thats
 the area where i supposed the help is needed for now.
 
 Regards AlexS.
 
 
 

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Mike Sessions



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 lot of problem reports from Mandrake 8 users on the FAQ comments.

I made some notes during my installation, I could possibly write something
of a howto if you think it would help.


Could you explain what you mean by the kernel modules are gzipped up?
Are you saying the modules are zipped in /lib/modules to save space and then get 
unzipped when needed by the kernel???

More or less. this is what my drm modules directory looks like now that I
have installed the 0.7 package...

-rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
-rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
-rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
-rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
-rw-r--r--1 root root   108222 May 16 19:15 radeon.o
-rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz



Also, the libGL.1.2.x hanging around is not a problem since we symlink libGL.so 
and libGL.so.1 to the correct library.
But maybe we should still try to remove/backup all old libGLs?
This is also a problem on Redhat were such a libGL sticks around in /usr/lib .. they 
get installed from the Mesa RPMS.

Well, I claim to be no genius... I remember something on my slackware
box though.. Quake3 for instance would run fine, but Unreal Tournament
would revert to software Mesa unless I removed all traces of libGL*
except those provided with whichever drivers I was using. If I remember
right it was this way with both the DRI drivers for my Radeon, and
Nvidia's driver for a GeForce card I have.


- Frank
ÿÿÿî/Ýz÷¥™¨¥Šx%ŠËC®/Ýz÷¥þX¬¶Ïì¢êÜyú+ïçzØm¶ŸÿþX¬¶Ïì¢êÜyú+ïçzßåŠËlþX¬¶)ߣ÷k‹÷^



___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Frank Worsley

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 what my drm modules directory looks like now that I
 have installed the 0.7 package...
 
 -rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
 -rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
 -rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
 -rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
 -rw-r--r--1 root root   108222 May 16 19:15 radeon.o
 -rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz
 
 

Wacko ... I've never seen anything like that. Then again, I've never used
Mandrake. Since a lot of people seem to run Mandrake (especially 8) it
would probably be worthwhile to add a check for something like this.

 
 Well, I claim to be no genius... I remember something on my slackware
 box though.. Quake3 for instance would run fine, but Unreal Tournament
 would revert to software Mesa unless I removed all traces of libGL*
 except those provided with whichever drivers I was using. If I remember
 right it was this way with both the DRI drivers for my Radeon, and
 Nvidia's driver for a GeForce card I have.

I dunno. If we relink libGL to the correct one in /usr/X11R6/lib it
shouldn't really be a problem.

- Frank


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] (no subject)

2001-05-17 Thread Mike Sessions


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 nice if you did that.


http://www.vvm.com/~sessions/linux/DRI.txt


 More or less. this is what my drm modules directory looks like now that I
 have installed the 0.7 package...

 -rw-r--r--1 root root29688 Apr 15 17:14 gamma.o.gz
 -rw-r--r--1 root root34815 Apr 15 17:14 i810.o.gz
 -rw-r--r--1 root root39383 Apr 15 17:14 mga.o.gz
 -rw-r--r--1 root root39627 Apr 15 17:14 r128.o.gz
 -rw-r--r--1 root root   108222 May 16 19:15 radeon.o
 -rw-r--r--1 root root25798 Apr 15 17:14 tdfx.o.gz



Wacko ... I've never seen anything like that. Then again, I've never used
Mandrake. Since a lot of people seem to run Mandrake (especially 8) it
would probably be worthwhile to add a check for something like this.


As long as the .gz module is there, it won't work... Someone new to Linux
is not going to know where to look or what to look for... Just that it
doesn't work.


 Well, I claim to be no genius... I remember something on my slackware
 box though.. Quake3 for instance would run fine, but Unreal Tournament
 would revert to software Mesa unless I removed all traces of libGL*
 except those provided with whichever drivers I was using. If I remember
 right it was this way with both the DRI drivers for my Radeon, and
 Nvidia's driver for a GeForce card I have.

I dunno. If we relink libGL to the correct one in /usr/X11R6/lib it
shouldn't really be a problem.

Like I said, I remember something, but I could be way off base... The more
I think about it, there may have been some rouge links somewhere and it
may have only affected the Nvidia drivers on my Slackware box which is not
an issue here :) It doesn't seem to hurt anything with it gone at any
rate.


___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel