dumb this down - sorted.

Declan Moriarty junk_mail at iol.ie
Fri Feb 3 11:39:15 PST 2006

Recently, Somebody Somewhere wrote these words

> > I finally discovered paxctl, which allows you to fart about
> > with settings on a per-binary basis.
> If that is the case, then many of the problems are grsec
> related. (there are numerous problems with grsec, xorg, and
> other major programs in the past...its usually more of the other
> programs fault for not considering security or just being very
> old than it is grsec)

Pax evidently views the dri process as an execution attempt. I
have to run paxctl -m <binary> for every binary using dri. That's
the way it seems.

It also seems dri is a whole ball of <expletive deleted>.
> Perhaps trying a non-grsec kernel, may help weed out some
> problems, and recompiling the kernel means you only have to
> reboot to revert to the other system. (assuming you saved the
> other kernel image and modules in /lib/modules)

I have it here in a non grsec system, and I can't get DRI at all
> > 
> > paxctl -m /usr/local/bin/stellarium gets me a nice view of the
> Im not familiar with stellarium. What is this?  (something to do
> with space? (stellar))

A planetarium. You have a view of a cloudless sky at night, and
can zoom in on planets, & stars. It has a centre control which
brings your selected planet to centre screen before you zoom. It
really wants dri, but does not need speed.

> > outside world. A similar command even sorted glxgears.
> > 
> > glxgears is giving me a (fairly lousy) 580 fps, but it's early
> what does "glxinfo | grep render" return?

direct rendering: Yes
> Simply speaking, 500fps should never be a good value from
> glxgears.  I believe the desired minnimum is about 1200fps?
Yes. 580fps is strange. But I'm a novice with dri.
> It is possible, given $(numerous unfavorable opinions) in how
> much of the hardware accelerated code is, that vesa produces
> higher fps.
Yes. I haven't gone through the contortions of selecting vesa, and
I'm not for doom or quake. Something about the time, reaction
speed, and spilling of guts doesn't appeal to me. I believe I also 
lose 3d with vesa. I really don't care once about speed, once the 
3d function is operative. Faster is better, I suppose, but I'm not
worried yet.

The patch on http://bugs.freedesktop.org/show_bug.cgi?id=4197 is
applied. The (vitriolic) discussion there points to a speed penalty.
It was my intention to have this on a 'normal' system & compare, but
then I can't get the normal system functioning on dri :-/.
> You told me you had a radeon?  Instead of having "ati" try
> "radeon" or vice-versa.  If lucky, you'll find one of these
> (ati, radeon, vesa) three to produce higher fps..

I have a Radeon 7000. According to the docs, The ati cards
include (in order of age)
1. Mach 64
2. r128
3. radeon 7000 & higher
4. radeon 8500 & higher
5. radeon 9500 & higher

"ati" is for 1 & 2; radeon is for 3; r200 is for 4; r300 is for 5.
These drivers autoselect, (e.g. ati calls radeon if it finds a
7000 so the room for manouvre is limited.


	With best Regards,

	Declan Moriarty.

More information about the hlfs-dev mailing list