AMD64 issues

["Raskólnikov ..." <magnicida at gmail dot com>]

It worked perfectly, and I used to play games such as Doom 3, Quake 3 (the
official binaries), Cube, Darwinia and others. It had been some time since I
last played Cube (I had mades some upgrades since them) and last time I
tried to play it I got that error message, and the same occurrs with any
other 32bits 3d app.

I have found this thread:
http://www.stanchina.net/~flavio/debian/fglrx-archive/msg00909.html<http://www.stanchina.net/%7Eflavio/debian/fglrx-archive/msg00909.html>
and I get exactly the same messages.

I have my chroot lib paths into my ld.conf file. If I run 32bits apps
outside the chroot they display no error message, but  it is because in that
case Mesa is used instead and FPS rates are very low (this is not a big
problem because it also happened when apps worked into the chroot. However,
i remember that long long ago it worked this way).

Thanx

On 1/10/06, Elmo Mäntynen <elmo13 at jippii dot fi> wrote:
> Raskólnikov ... wrote:
>
> > High, sorry for sending with such an ambigous subject but there are
> > two questions I want to do:
> >
> > a) When will Fglrx for amd64 go into Sid as it did for i386?
> >
> > b) Why can't run apps for 32bits in my chroot? It used to work but
> > know It does not. This is what it says:
> > libGL error: failed to open DRM: Operation not permitted
> > libGL error: reverting to (slow) indirect rendering
> > Previous versions used to work. I'm not sure if I've broken something
> > but I think its not my fault. I've been trying to solve this for a
> > long time but I can't. Both version of the driver installed in my
> > system and in the chroot are the same: 8.19.10-1. Is this solved in
> > 8.20? (read question 'a' :p)
> >
> > Lots of thanx in advance.
>
> You have really had DRI working from inside a 32bit chroot? I had the
> same complaint when trying some games, but when I linked /dev/dri to
> chroot/dev/,  incompatibility got in my way. That was in an Ubuntu amd64
> install. I did a search and ran into a mailing-list post which said that
> it wasn't supposed to work at the moment of the post, hard to do it
> said. It corresponded to some 4.x of xfree86, so I'm not sure if it
> could work now.