SlackwareThis Forum is for the discussion of Slackware 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.
I seem to have broken my graphics drivers again. I have a Radeon 9250, and was getting "API ERROR: could not register entrypoint for" messages. The libGL.so.2 fix worked originally, but now I'm back to the original problem and replacing the library won't save me any more.
The last thing I did that might have modified anything display-wise was the latest version of WINE. I suspected it may have been something to do with not having removed the previous version first. I've uninstalled both packages, and the API errors remain.
I'm not at my Linux box at the moment, so I can't try it. Shall investigate when I get home. Managed to fix the main problem anyway--just uninstalled the driver and then reinstalled and all is well again. Though now Wine keeps crashing out.
Quote:
What version of slackware?
10.2
According to fglxinfo (I think), direct rendering doesn't seem to be enabled, even though everything else is configured correctly. I've tried a few different directions on configuring X.org to enable it, but no luck as yet. Does the driver actually support direct rendering on a Radeon 9250?
I'm pretty sure I've followed everything in that post... minus the kernel recompilation, which I've not done at all yet. Is that a necessary step? I read the default kernel should work fine for this, but perhaps I need to recompile with extra stuff enabled?
did you verify check in your /etc/rc.d/rc.modules that this line is un-commented?
Quote:
/sbin/modprobe agpgart
tho, to be honest, I'm really not sure if it is required as I can toggle it on/off and I get DRI. Pat turns it on by default.
the stock kernel 2.4.31 should be fine, but maybe you need to verify that your agp is loaded, check that ATI manual it tells you how to verify that your AGP motherboard modules are loaded or not.
The Radeon 9250 is supported with dri natively in Xorg 6.9.
I do not know if the latest ati driver gives you more fps than the older driver in Xorg 6.9 but I get ~1300 fps on my Radeon 9250 which has never given me any trouble (well maybe once when I compiled a custom kernel and forgot to put agpgart in )
I always see alot posts from people who are having problems with the flgx. Although it may get you a few more fps It does not seem worth the effort unless you have a newer card without a native driver in Xorg. It also seems that it mucks up systems frequently and gives the NVidia crowd something to point at
The Radeon 9250 is supported with dri natively in Xorg 6.9.
Excellent. I'm in the process of downloading it now. I assume I need to remove 6.8 before installing, or is there a way of upgrading over the top of it?
for some reason they do not inlclude this text in the readme file's of later driver versions, which they probably should, it don't cost anything
Quote:
Version 2.6 kernels require a second kernel module in addition to agpgart, which should be named similar to the manufacturer of your motherboard AGP chipset. This error message should occur if the other agp module is not loaded.
This issue can be worked around as follows:
1. First make sure that agpgart is loading properly.
2. To find out which AGP controller your motherboard uses, issue the following command: lspci | grep AGP
3. To find a list of AGP related kernel modules installed on your machine, issue the following command and look for a module (*.ko file) that suits your AGP Controller: ls /lib/modules/`uname -r`/kernel/drivers/char/agp
4. Use the modprobe command (as root) to load the module. For example: On a motherboard using a VIAŽ AGP Controller, you would load the via-agp.ko using modprobe as follows (notice that the trailing.ko is omitted): modprobe via-agp
Check the modprobe manpage for more information on loading kernel modules.
5. To verify that the AGP module is already loaded, run lsmod as root. With the X server running and the connection established, the usage count of this module must be greater than zero.
If you cannot find a suitable agp module for your motherboard, then you may want to upgrade to the latest version of the Linux kernel, or check your motherboard manufacturer's website for more information.
root@jimslacker:/# ls /lib/modules/`uname -r`/kernel/drivers/char/agp
agpgart.o.gz
No .ko files, it would seem. I also ran locate *.ko from / but there were only a few results and none of them sounded useful.
Tried throwing an "Option" "NvAGP" "1" line into xorg.conf, which I read about at a couple of sites in relation to Nforce2, to no avail.
Quote:
Sorry I mixed up my version numbers.
Heh, don't worry about it. I'm probably gonna need to upgrade anyway when my 'new' [8 months and I still haven't been able to use it because of faulty parts] components return. The sooner I try it out, the better.\
Edit
Btw, I'm getting the following warnings when installing wine, and I think the ATI driver complained as well.
Code:
/sbin/ldconfig: /usr/lib/libGLU.so.1 is not a symbolic link
/sbin/ldconfig: /usr/lib/libGLw.so.1 is not a symbolic link
Could that have something to do with it? I don't recall what I did to cause it.
Solved! I was talking to another Slacker on MSN about the issue, and after a few possibilities that didn't work, he finally suggested installing the raw RPM, but tell it to ignore dependencies:
Code:
rpm -i --nodeps fglrx-etc.rpm
Replaced libGL.so.1.2, restarted X and boom! Instant DRI.
I also fixed those broken symlinks, but I don't remember how exactly. I think I deleted them and reinstalled X.
Wine is still crashing on a page fault, but that's a subject for another forum.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.