SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I found out the solution of this problem, you should downgrade module-init-tools package to previous version and video modules in huge package will be loaded fine. (tested with intel modules, module-init-tools version 3.6) Don't forger run "depmod -a" after downgrade the package.
Well we're getting somewhere now... Oddly, libGL is looking in /usr/lib/dri and /usr/lib64/dri for the DRI drivers, rather than /usr/lib64/xorg/modules/dri, which is where it is actually located on Slackware 64. Which makes me think that the libGL might also be left over from fglrx. Can you reinstall Mesa? If, after reinstalling Mesa, libGL is still checking /usr/lib/dri and /usr/lib64/dri, can you try 'LIBGL_DEBUG=verbose LIBGL_DRIVERS_DIR=/usr/lib64/xorg/modules/dri/ glxinfo' and see what the output is then.
I'm recompiling my kernel with CONFIG_PREEMPT_NONE=y and I'll give you feedback, but I think my problem is elsewhere:
I'trying to install fglrx 10-2 and it gives back error:
Unloading radeon module...
Unloading drm module...
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
AMD kernel module generator version 2.1
kernel includes at /lib/modules/2.6.33-smp/build/include do not match current kernel.
they are versioned as ""
instead of "2.6.33-smp".
you might need to adjust your symlinks:
[Error] Kernel Module : Failed to compile kernel module - please consult readme.
Do someone have the same problem?
The same problem.Do you get some method to solve it?
So ... after recompiling the 188.8.131.52 kernel and installing FGLRX I'm geting:
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
dlopen: /usr/lib/xorg/modules/drivers/fglrx_drv.so: undefined symbol: UpdateSpriteForScreen
(EE) Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
I always recommend radeon over radeonhd, however either driver should work with 2D and 3D acceleration as long as fglrx is completely purged from your system. Check earlier on this page and the previous page where I gave suggestions to gtludwig.