Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ATI cards are always a problem to get 3D working. Took me a long time to get DRI working on my laptop's radeon mobility U1. What kind of system do you have and what's the rest of the card's name? For this I'll assume Radeon.
1) First thing you'll want to do is recompile your kernel. In the video driver sections enable as built-in: AGP (provides agpgart) and DRM. Include NONE of the individual chipset drivers.
2) Next go to this site: http://dri.freedesktop.org/snapshots/
Get the latest radeon-* and in the archive folder get the latest common-*
3) Make sure ALL Mesa stuff is removed (may be tricky)
4) In /usr/X11R6/lib/modules/extensions make backups of libGLcore.a, libdri.a and libglx.a. These files will be replaced. For mine to work I had to still use the original libdri.a
5) Compile and install the common-*, then the radeon-* packages
6) Edit your xorg.conf to load "GLcore", "glx" and "dri"; in the graphics device section load the "radeon" driver; and at the bottom put:
Section "DRI"
Mode 0666
EndSection
The next time you go to check glxinfo login as root and don't grep. If direct rendering is still no, look at GL vendor. If it's SGI then you still have some Mesa stuff. When you get it working try as a user as there may be permission issues with the device in /dev. If so the easiest fix is to add the user to the group that owns the device.
My use of the name radeon was only as an example. If yours is a rage use rage. GL support will be included with the dri packages. For the mesa stuff I'll have to look through my notes and get back. I remember one filename - libMesaGL - I think it was in /usr/X11R6/lib. Yours might be /usr/X11/lib. Like I said I'll check my notes and get back.
Again what kind of system is this? Dekstop or laptop? And do you know the full name of the ATI card? Is it a Rage something M3?
I wouldn't worry about the extensions directory being empty. But before you get too far let's answer those questions. And always before you recompile a kernel make a backup of your current one. Just cp the file to something you'll know you won't overwrite or delete. That way if your new one doesn't work as expected you can restore it.
Riddick, I believe you need to update locate's database. It creates a db rather than search the hdd whenever you want to find something. In Slackware, "locate" is linked to "slocate", which uses "updatedb" to upgrade its database...I don't know about SuSe. Check the man page for locate and see what it says to do.
...oh, and by default, /usr/X11R6/bin isn't in root's PATH, but if you use the program's full location (/usr/X11R6/bin/glxinfo, perhaps), root should be able to run it. But why run glxinfo as root, anyway?
I just did that!
I deleted all those files, but there must still be something somewhere.
When I installed the two files, one said configuring and compiling kernel modules - do I need to do anything more than that, or do I have to do some sort of kernel recompile?
Sorry for the long wait. I found my notes. According to your recent posts you definitely will want the rage driver as opposed to the radeon. So you found the libOSMesa file and removed that. According to my notes you need to find three others: libGL, libGLU and libGLw. I found mine in either /usr/local/lib or /usr/X11R6/lib. The new driver will install new libGL and libGLU into /usr/X11R6/lib. Yours might go to /usr/X11/lib.
Running glxinfo as root will only be for verifying that DRI is enabled. If a user doesn't have appropriate permissions to the card in /dev glxinfo will report "direct rendering: no". That bugged me for a couple of days before I figured out it was a permissions issue.
Right... I have a question now... Those installation scripts say:
The script will use the following XFree86 directory:
/usr/X11R6
is that correct or shall I redirect them to /etc/X11 ?
I got rid of the files you said from /usr/X11R6 and now I get
ed@edslaptop:~$ glxinfo
glxinfo: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory
ed@edslaptop:~$
even after re running both installations scripts!
Also the rage driver fail to install the kernel modules:
Code:
make DRM_MODULES=r128.o modules
make[1]: Entering directory `/home/ed/rage128-20050718-linux.i386/dripkg/drm/linux-core'
make -C /lib/modules/2.6.12.5/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
make[2]: Entering directory `/usr/src/linux-2.6.12.5'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-2.6.12.5'
make[1]: Leaving directory `/home/ed/rage128-20050718-linux.i386/dripkg/drm/linux-core'
FATAL: Error inserting r128 (/lib/modules/2.6.12.5/kernel/drivers/char/drm/r128.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Thanks.
In conclusion there are 3 problems:
1. where do i tell the scripts to install
2. what happened to the thing that breaks glxinfo, and where does it go looking for it?
3. what's wrong with the kernel modules installation for the rage?
I think I just found an important key to this puzzle from a SuSE forum:
Quote:
On Wednesday 24 September 2003 05:52, Nick LeRoy wrote:
> I have a Dell Inspiron 4000 with a Mobility M3, and, for the life of me, I
> can't get DRI working on it.
This chipset needs the GATOS driver. I don't know the status of the GATOS
driver support in 8.2, but I don't think it works out of the box. My Inspiron
5000 didn't get hardware acceleration out of the box with 8.1 or 8.2. I
applied the patches when I was running 8.1 and it worked fine. I didn't
bother when I updated that machine to 8.2.
I guess the rage package is not what your card needs. I wouldn't worry about the glxinfo output. Thats because the libGLU file is not there anymore. If that actually needs to be replaced find the mesa package on your install CD or get a binary package that you can extract from.
You did make sure your kernel has agp and drm didn't you?
kernel has agp and drm built in.
I'm going to recompile without rage support.
So the GATOS driver above is the DRI package for M3s is that right?
I'm going to get it and see...
So: It seems to be the right thing, but it's for XFree86 versions of X,
versions 4.2.0 and 4.3.0... and I think I have XOrg... what shall I do!
I'm a bit confused - what should I be doing now?
Should the common dri package be installed?
What do i need to do in terms of GATOS?
How do I install GATOS!
Thanks for your continuous help,
Don't give up on me yet!
Riddick
As a second thought, is it not possible to use VESA and MESA to get 3d acceleration?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.