MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
Thanks for the response. I have Mandriva/Mandrake 10.1. Maybe, I am just confused. I would have thought Xserver would be included with my Mandrake installation. I thought X was the thing that displays the windows and graphics. I would think I have that because I am using a graphical user interface right now.
If I type "startx" or "X" it will display a message saying the server is already active.
is it possible to read the file "whatever.run" in a text editor, carefully if a binary file.
At least that might tell you what its looking for and where.
If text file change it to where your X server files are.
I couldn't read the file.. I tried opening it in emacs but nothing showed up and it lagged my system. I did download just the driver in an rpm package this time.
Here's what I tried:
[root@localhost dls]# rpm -iv fglrx*.rpm
error: Failed dependencies:
libexpat.so.1 is needed by fglrx_4_3_0-8.27.10-1
What in the world is going on? Why does Linux have to be so difficult?
It is telling you that the driver depends on another library in order to operate. It cannot see an RPM installed version of said library, so it is telling you to get it before it can complete the installation. If I recall correctly, expat is a regular expression parser library, which does seem a bit odd for a video driver. For best results, you should do as it says, and get the expat library and install it.
You are entering the world of 'dependency hell'. It is linux's way of keeping losers who can never let go of the Windows apron-strings away.
Originally Posted by PCalitrack
Should I be worried about the X Server not being found? And do rpm packages automatically overwrite my old video card drivers.
For non-RPM installations, you should probably be worried. Most RPMs will overwrite the old version. It's what you want, really.
Creating symbolic links to versions that purport to be what they really are not, isn't generally a good idea. Moreover, rpm will not find any installed libraries, other than what was installed by rpm. It wasnt't too hard to find expat rpms for Mandrake at rpmfind.net. Did you look there?
There is also the option of creating an rpm from source tarballs, although I sense that this isn't a place you want to go right now (or ever, probably).
Having re-read your original post, I'm rethinking the meaning of the 'X server not detected' message. I think it may simply mean that it is unable to detect which X server you are running. This may be harlmess. Just speculating, but it may be possible to tell the installer script something about the existing X server on the command line, like whether it is X.org or Xfree-86, and where it is installed in the filesystem.
Finally, since you do seem to have a working X server, what benefit do you expect to gain by installing another/different video driver? Perhaps the optimal solution is to simply leave well enough alone.
First of all, thanks for your response. I truely appreciate the help.
I have looked on several rpm sites, and I can't seem to find that specific file contained in any of the packages for Mandrake or others.
Right now my display is screwed up. This is especially evident when I run Mozilla. I get random lines drawn all over the screen and can't read anything because there is too much random crap created by my driver. Also, when I shut down my system, There are a ton of random error messages thrown about the display, and it sometimes displays the background as a blur of brownish color on shutdown.
Last edited by PCalitrack; 08-05-2006 at 12:41 AM.
Okay, mmy best suggestion with respect to the expat RPM issue is to get the latest expat rpm for Mandrake, and install that. I think it will give you a libexpat.so.1.XX. It should be safe to symlink that to a libexpat.so.1. Those RPMs are available at pbone and RPMfind, and probably several others. Try that, and let us know how that goes.
Alternatively, you could run the rpm installation with the --nodeps flag to force it to go ahead and install withouth regard to dependencies.
This is a fairly common problem, the solutions are a bit messy. What happens when you install a package by using RPM is that an entry for that package is made in a database that is maintained by RPM on your system. That is the only place that RPM looks to find out what is already there. It will not do the equivalent of 'whereis' to decide whether dependencies are met.
You can install libreadline.so.5 from an RPM. This is probably the easiest and best solution.
You can install libreadline.so.5 from a source RPM. This is probably the most difficult, but still a good option.
You can tell RPM to ignore dependency issues by using the --nodeps commandline option. This is okay as long as you know what you are doing. Ignoring ALL dependencies might be risky. I don't think there is any way to tell it to ignore only specified dependencies.