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'm using Slackware64 -current. Recently I've switched to Radeon the open source driver, since AMD dropped support for my RAdeon HD mobility 3470
Steps I did :
- aticonfig --uninstall (to remove the fglrx install)
-removed xorg.conf file
- took a kernel that I have for another linux system that has the radeon features enabled (kms and R600 binary blobs.
- installed the radeon_ucode for the latest firmware.
- I updated my Xorg-server to 1.12.2 and then rebuilt xf86-video-ati, xf86-input-keyboard and xf86-input-mouse
I've had some issues and I reinstalled kde (I know it's a stretch but it's always better starting fresh)
Now please look at the output of glxinfo:
Code:
$glxinfo
name of display: :0
glxinfo: symbol lookup error: /usr/lib64/libGL.so.1: undefined symbol: _XGetRequest
I thought that the issue was around Mesa which I've updated, buts till no luck
I do have a kde graphical environment but with no desktop effects on it and the mouse is moving too fast.
Here's the output of xorg.conf (That's Ive generated using X -configure)
Perhaps some residue is remaining from fglrx? You might try reinstalling all of the X packages (upgradepkg --reinstall x/*.txz) to see if that cleans things up.
You need reinstall xorg-server-1.12.2, and mesa to fix what fglrx changes.
I recommend that you upgrade your kernel to the 3.5 series, there is a great performance boost for the radeon driver, and use mesa-7.10.2-i486-1 from testing dir.
Are you mephisto on ##slackware? If so, I recall you talking about all sorts of Xorg problems you've had recently, where packages were installed but missing, you forced an update, had to rebuild the radeon driver... Frankly, I'd guess that your installation of Xorg and Mesa is pretty much borked. You probably have various older and newer Xorg development headers floating around causing problems.
You're pretty much right, I did exactly as you said, and that same problem was solved in my other system. The thing is that I had xorg-server 1.9.5 and couldn't remove it (neither with slackpkg nor with pkgtool) so I went ahead and installed 1.12.2
Yeah, when you remove a proprietary driver often you have to rebuilt almost everything library-wise with the X-Server sometimes. Drivers, Mesa, basic inputs, all can be tarnished by using proprietary drivers.
At best, because -Current is a developer/tester/unstable tree build that is always being updated on a regular basis, you shouldn't use a proprietary driver for this branch of Slackware. The proprietary driver is often best suited for stable branches that aren't receiving heavy updates and may require a proprietary driver for functionality.
I have an idea but in order not to *break* the system even further, I want some advice, I'm thinking about doing a
wget -m to the x/ directory from the -current branch and rebuild the whole thing.
If not then I'll go and upgrade the system as tty13 said
I have an idea but in order not to *break* the system even further, I want some advice, I'm thinking about doing a
wget -m to the x/ directory from the -current branch and rebuild the whole thing.
If not then I'll go and upgrade the system as tty13 said
(You should not rebuild anything. If you build, you compile source code to machine code. You should use precompiled slackware binary packages.)
So, it seems you have a mixture of slackware64-13.37 and slackware64-current. You are lucky that it works at all. You should either upgrade everything to slackware64-current or downgrade everything to slackware64-13.37. It can be tricky to downgrade. Upgrading to slackware64-current should work if you follow the instructions. It won't work if you just upgrade the x/ packages when all your other libraries are probably still from 13.37.
I did have an issue with the upgrade to current, now I've managed to delete the 13.37 stuff (unblacklisting aaa_elflibs) and running slackpkg clean-system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.