[Xpert]Re: Continuing Radeon DRI problems

2002-08-03 Thread Angus Wallace


 Message: 13
 Subject: Re: [Xpert]Re: Xpert digest, Vol 1 #2073 - 14 msgs
 From: Michel =?ISO-8859-1?Q?D=E4nzer?= [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Date: 01 Aug 2002 16:12:00 +0200
 Reply-To: [EMAIL PROTECTED]
 
 On Thu, 2002-08-01 at 09:34, Angus Wallace wrote: 
   Message: 4
   Subject: Re: [Xpert]Re: Radeon.o upgrade
   From: Michel =?ISO-8859-1?Q?D=E4nzer?= [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Date: 29 Jul 2002 23:59:55 +0200
   Reply-To: [EMAIL PROTECTED]
   
   On Sun, 2002-07-28 at 09:38, Angus Wallace wrote: 

I have XFree86 4.2.0 working on my Radeon VE with DRI (i.e. using
glxinfo to check). However, running a 3d game (like quake2 through wine)
provides the message that TCL will be disabled, and I should upgrade
from radeon.o 1.1.1 to 1.3.x. Added to this my DRI enabled server (I
have 2, one dual-head without DRI, and a single-head configuration with
DRI) is very unstable and crashes often. Even my non DRI-enabled server
is less stable than when I was only running single-head, no DRI...

I'd upgrade the driver, except that I can't find it. does it exist yet,
   
   Yes, in DRI CVS. The binary snapshots available from dri.sf.net (where
   did you get your DRI driver if not from there?) build and install it.
  
  I've done the upgrade, but I still get whinging about the driver,
 
 If you still get the same message, you haven't upgraded the kernel module.
 
 Anyway...
 
  and if I run a program such as glxgears of tux racer, X crashes instantly,
  taking the keyboard and mouse with it (although XMMS might continue to
  play). 
  I'm pretty sure I've configured XF86Config correctly, and suspect it
  might be a driver issue. Do other people run DRI on the radeon
  successfully? 
 
 Yes, but the current code in DRI CVS hangs on some VEs, this is probably
 related to the new support for hardware TCL. XFree86 4.2.0 or CVS should
 work though.
 
 
 -- 
 Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
 XFree86 and DRI project member   /  CS student, Free Software enthusiast
 
 
Hello again,

I'm still having problems, and am thinking that some more detailed
information would be in order.

I'm running Redhat 7.3 with the 2.4.18-3 kernel that comes with it. I've
recompiled that with AGPgart support, and modular support for DRI on the
Radeon. I've then downloaded the DRI drivers, and installed them. 

I think, actually, that my dual-head/no DRI layout is working fine, but
my single-head/DRI layout crashes whenever a program tries to use openGL
(such as glxgears.)

I've looked at the 'DRI user guide', and checked for things like the
presence of the driver, using lsmod, and looking in the log file created
by X, DRI is enabled. Similarly, glxinfo says that it is enalbed, also.

Does this mean I have a 'dud' VE that hangs on the current DRI code?
(with TCL added.)
I no longer get the message about TCL being disabled (that I got before
I compiled the kernel with modular Radeon support, and then upgraded the
module) but it hangs just the same.

Phew! This is seeming much more complicated than I'd anticipated. The
assistance has been greatly appreciated. Thanks a lot Michel!

Regards
-Angus Wallace

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Option accel question

2002-08-03 Thread Michel Dänzer

On Fri, 2002-08-02 at 19:23, Daniel Sheltraw wrote: 
 
 Is the accel option implemeted using PCI DMA. I do not really
 understand what accel is all about. Can someone please shed a
 little light on the subject for me :-) ?

Short answer: it depends on chip, driver and configuration. :)

Slightly longer answer: most accel is done with MMIO access to chip
registers.


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: Continuing Radeon DRI problems

2002-08-03 Thread Dr Andrew C Aitchison

On 3 Aug 2002, Angus Wallace wrote:

 I'm still having problems, and am thinking that some more detailed
 information would be in order.
 
 I'm running Redhat 7.3 with the 2.4.18-3 kernel that comes with it. I've
 recompiled that with AGPgart support, and modular support for DRI on the
 Radeon. I've then downloaded the DRI drivers, and installed them. 
 
 I think, actually, that my dual-head/no DRI layout is working fine, but
 my single-head/DRI layout crashes whenever a program tries to use openGL
 (such as glxgears.)

There are three versions of source for the Radeon DRI kernel module,
one comes with the kernel, one with XFree86 and one with the DRI
project drivers.

If I understand correctly, you need to use the source that comes
with the DRI project drivers, but you have to recompile it every time
you change the kernel or XFree86 version.

-- 
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED]   http://www.dpmms.cam.ac.uk/~werdna


___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: Continuing Radeon DRI problems

2002-08-03 Thread Michel Dänzer

On Sat, 2002-08-03 at 12:41, Angus Wallace wrote:
 
  On Thu, 2002-08-01 at 09:34, Angus Wallace wrote: 

On Sun, 2002-07-28 at 09:38, Angus Wallace wrote: 
 
 I have XFree86 4.2.0 working on my Radeon VE with DRI (i.e. using
 glxinfo to check). However, running a 3d game (like quake2 through wine)
 provides the message that TCL will be disabled, and I should upgrade
 from radeon.o 1.1.1 to 1.3.x. Added to this my DRI enabled server (I
 have 2, one dual-head without DRI, and a single-head configuration with
 DRI) is very unstable and crashes often. Even my non DRI-enabled server
 is less stable than when I was only running single-head, no DRI...
 
 I'd upgrade the driver, except that I can't find it. does it exist yet,

Yes, in DRI CVS. The binary snapshots available from dri.sf.net (where
did you get your DRI driver if not from there?) build and install it.
   
   I've done the upgrade, but I still get whinging about the driver,
  
  If you still get the same message, you haven't upgraded the kernel module.
  
  Anyway...
  
   and if I run a program such as glxgears of tux racer, X crashes instantly,
   taking the keyboard and mouse with it (although XMMS might continue to
   play). 
   I'm pretty sure I've configured XF86Config correctly, and suspect it
   might be a driver issue. Do other people run DRI on the radeon
   successfully? 
  
  Yes, but the current code in DRI CVS hangs on some VEs, this is probably
  related to the new support for hardware TCL. XFree86 4.2.0 or CVS should
  work though.
 
 I'm still having problems, and am thinking that some more detailed
 information would be in order.
 
 I'm running Redhat 7.3 with the 2.4.18-3 kernel that comes with it. I've
 recompiled that with AGPgart support, and modular support for DRI on the
 Radeon. I've then downloaded the DRI drivers, and installed them. 
 
 I think, actually, that my dual-head/no DRI layout is working fine, but
 my single-head/DRI layout crashes whenever a program tries to use openGL
 (such as glxgears.)
 
 I've looked at the 'DRI user guide', and checked for things like the
 presence of the driver, using lsmod, and looking in the log file created
 by X, DRI is enabled. Similarly, glxinfo says that it is enalbed, also.
 
 Does this mean I have a 'dud' VE that hangs on the current DRI code?
 (with TCL added.)

Apparently.

 I no longer get the message about TCL being disabled (that I got before
 I compiled the kernel with modular Radeon support, and then upgraded the
 module) but it hangs just the same.

That's one of the problems with the new code, it seems to emit TCL
commands when it shouldn't. It will have to be debugged on one of those
machines.


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Option accel question

2002-08-03 Thread Daniel Sheltraw

Michel

Thanks for the reply and thanks for helping us get an answer
to our MB problem that Marc ultimately solved. 


  Is the accel option implemeted using PCI DMA. I do not really
  understand what accel is all about. Can someone please shed a
  little light on the subject for me :-) ?
 
 Short answer: it depends on chip, driver and configuration. :)
 
 Slightly longer answer: most accel is done with MMIO access to chip
 registers.

How does using the MMIO accelerate graphics? Confused. I just really
do not know what acceleration means.

Daniel







 
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Re: Option accel question

2002-08-03 Thread Mike A. Harris

On Sat, 3 Aug 2002, Daniel Sheltraw wrote:

Date: Sat, 03 Aug 2002 09:45:57 -0600
From: Daniel Sheltraw [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain
List-Id: General X Discussion xpert.XFree86.Org
Subject: Re: Option accel question

Michel

Thanks for the reply and thanks for helping us get an answer
to our MB problem that Marc ultimately solved. 


  Is the accel option implemeted using PCI DMA. I do not really
  understand what accel is all about. Can someone please shed a
  little light on the subject for me :-) ?
 
 Short answer: it depends on chip, driver and configuration. :)
 
 Slightly longer answer: most accel is done with MMIO access to chip
 registers.

How does using the MMIO accelerate graphics? Confused. I just really
do not know what acceleration means.

Video hardware acceleration is the implementation in the video 
hardware itself of common graphics primatives and operations.

Without hardware acceleration, the CPU has to do all the work.  
The CPU calculates the pixels when drawing lines, polygons, etc. 
and writes them into video memory.  The CPU does all the work.

With a 2D acceleration engine, like all video hardware has 
nowadays, instead of the CPU doing all this work, the CPU merely 
tells the video card draw a rectangle with these co-ordinates, 
then the video hardware's 2D acceleration engine draws that 
rectangle internally on the video card itself.  This moves the 
drawing logic off the host CPU and onto the video card.

There are all sorts of operations which are accelerated in 
hardware including line drawing, rectangles, fills, blitting 
images, etc.

MMIO is memory mapped IO, which maps the hardware's IO register 
space into the memory map.  This is one way of communicating with 
the hardware.


-- 
Mike A. Harris  Shipping/mailing address:
OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie,
XFree86 maintainer  Ontario, Canada, P6C 5B3
Red Hat Inc.
http://www.redhat.com   ftp://people.redhat.com/mharris

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Option accel question

2002-08-03 Thread Dr Andrew C Aitchison

On Sat, 3 Aug 2002, Daniel Sheltraw wrote:

Acceleration really means using the graphics hardware to perform
graphics primitives like draw line, fill triangle/rectangle, ...
NoAcceleration is basically: use the cpu to change every pixel
individually.

No doubt both those descriptions are technically wrong, and
misleading at some level, but they should give you some idea.

-- 
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED]   http://www.dpmms.cam.ac.uk/~werdna

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]problem with Xft and pango

2002-08-03 Thread Fred Heitkamp


I'm trying to compile the latest CVS pango version.
Is this possible?
Apparently it requires freetype 2 and Xft.
Xft wants to include freetype1 as far as I can tell
by looking at the Xft headers, specifically:

/usr/X11R6/include/X11/Xft/XftFreetype.h
..
#include X11/Xft/Xft.h
#include freetype/freetype.h
..

/usr/gcc-3.1.1/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -DPANGO_ENABLE_BACKEND
-DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\/drives/sg4/gnome2//etc\
-DLIBDIR=\/drives/sg4/gnome2//lib\ -DMODULE_VERSION=\1.0.0\
-DG_DISABLE_DEPRECATED -I/usr/X11R6/include -I/usr/X11R6//include
-I/usr/X11R6//include/freetype2 -I.. -g -O2 -Wall -D_REENTRANT
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -c
pangoxft-font.c -MT pangoxft-font.lo -MD -MP -MF .deps/pangoxft-font.TPlo
-fPIC -DPIC -o .libs/pangoxft-font.lo
In file included from pangoxft-font.c:27:
/usr/X11R6/include/X11/Xft/XftFreetype.h:73: parse error before '*' token
/usr/X11R6/include/X11/Xft/XftFreetype.h:74: warning: type defaults to
`int' in declaration of `XftFreeTypeOpen'
/usr/X11R6/include/X11/Xft/XftFreetype.h:74: warning: data definition has
no type or storage class
/usr/X11R6/include/X11/Xft/XftFreetype.h:77: parse error before
XftFontStruct
/usr/X11R6/include/X11/Xft/XftFreetype.h:79: parse error before '*' token
/usr/X11R6/include/X11/Xft/XftFreetype.h:80: warning: type defaults to
`int' in declaration of `XftFreeTypeGet'
/usr/X11R6/include/X11/Xft/XftFreetype.h:80: warning: data definition has
no type or storage class
/usr/X11R6/include/X11/Xft/XftFreetype.h:88: parse error before
XftFontStruct
/usr/X11R6/include/X11/Xft/XftFreetype.h:94: parse error before
XftFontStruct
/usr/X11R6/include/X11/Xft/XftFreetype.h:101: parse error before
XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:108: parse error
before XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:115: parse
error before XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:122:
parse error before
XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:129: parse error
before XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:136: parse
error before XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:143:
parse error before
XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:150: parse error
before XftFontStruct/usr/X11R6/include/X11/Xft/XftFreetype.h:157: parse
error before XftFontStructpangoxft-font.c: In function
`pango_xft_real_render':
pangoxft-font.c:317: structure has no member named `u'
pangoxft-font.c:330: structure has no member named `u'
pangoxft-font.c: In function `load_fallback_font':
pangoxft-font.c:717: structure has no member named `u'
pangoxft-font.c: In function `pango_xft_font_get_font':
pangoxft-font.c:766: structure has no member named `u'
pangoxft-font.c: In function `pango_xft_font_get_face':
pangoxft-font.c:842: structure has no member named `core'
pangoxft-font.c:845: structure has no member named `u'
make[3]: *** [pangoxft-font.lo] Error 1
make[3]: Leaving directory
`/drives/sg4/src/gnome2-test/tmp/gnome/pango/pango'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/drives/sg4/src/gnome2-test/tmp/gnome/pango/pango'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/drives/sg4/src/gnome2-test/tmp/gnome/pango'
make: *** [all] Error 2


Fred

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]problem with Xft and pango

2002-08-03 Thread Keith Packard


Around 14 o'clock on Aug 3, Fred Heitkamp wrote:

 I'm trying to compile the latest CVS pango version.
 Is this possible?

Yes, but you need to make sure you've added the FreeType2 header directory 
to the include path so that you get FreeType2 headers instead of FreeType1.

the xft.pc file installed with current XFree86 CVS Xft2 should point at
the right headers.

Keith PackardXFree86 Core TeamHP Cambridge Research Lab


___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert