[gentoo-amd64] Re: 32-bit-app 3D acceleration on amd64

[Duncan]

Michael Kjorling posted <438f15e1.4a1f4b90@××××××××××××.com>, excerpted
below,  on Thu, 01 Dec 2005 15:25:21 +0000:

> On 2005-12-01 08:42 -0600, brett@××××.com wrote:
>> I guess I missed that part. If he is trying to run X in a
>> chroot32 environment, I am not sure. I run X in native 64
>
> X runs in native 64 bit mode, it's the 32-bit applications that are
> the exception, and 32-bit binary-only even more so. When I run
> glxinfo, it says (among many other things):
>
> 	direct rendering: Yes
> 	OpenGL renderer string: Mesa DRI R200 20040929 AGP 4x TCL
>
> So DRI is working in 64-bit mode (and 64-bit 3D applications, Tuxracer
> being one example, can use it just fine).
>
>
>> I was assuming the Xorg.0.log snippet he posted was from 64
>> bit mode, and that was what was having problems initalizing
>> DRI.
>
> The problem is with running the 32-bit binary (which needs 32-bit
> direct rendering support to run at a usable speed) in an otherwise
> 64-bit environment. It executes just fine, only dreadfully slow.

OK, I'm running extreme resolution dual monitors (1600x1200 or 2048x1536
x two monitors) so don't get 3D accel anyway, neither do I run many games
(or anything else) in 32-bit mode, so no personal experience here. 
However...

If 64-bit is working and 32-bit isn't, you obviously have something
missing for 32-bit mode.  Have you verified that you have all necessary
32-bit compatibility lib binaries merged?  This would be the
app-emulation/emul-linux-x86-* series of ebuilds.  In particular,
emul-linux-x86-xlibs would need to be merged.  If it's already merged,
then perhaps merge the others (using tab-completion or esearch or whatever
to figure out what's there to emerge), just to be sure.  You certainly
won't need all of them, but particularly when installing binary-only
32-bit stuff, it might be easier to simply merge all the 32-bit support
libraries and have them available, than to figure out what's missing.

There's also the possibility that xorg didn't build needed in 32-bit DRM
portions as well, but I wouldn't have the foggiest how to go about
figuring that out except by either doing the chroot 32-bit thing, or the
unfreedomware binary-only driver.  Of course, if you are already willing
to run slaveryware games...  Still, games are userspace, the drivers will
be kernelspace.  There's a big difference.

Anyway, with luck, the 32-bit emulation libs will solve your issue and you
won't have to worry about the other.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@g.o mailing list