Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Can someone tell me how I would go about installing the ATI drivers for my Radeon 9800 Pro using the command line in Mandrake 9.2? I've already downloaded the drivers and will be installing them from a CD.
I'm trying to install these drivers because I'm unable to access the linux GUI without them. I'm guessing that since the file extension is i586, it's a self-extracting file? I've only installed one file via the command line so far and that was a .rpm file (the kernel, which someone walked me through), and am unsure of how to go about installing a file with this new extension.
My bad, it turns out that the file I had did have an extension of .rpm (was looking at it in WinXP where I don't have file extensions visible).
When I try to install the file, I get the following error:
file /usr/X11R6/lib/libGL.so.1.2 from install of fglrx-glc22-4.3.0-3.2.8 conflicts with (this next part is off the screen for some odd reason) from package libxfree86-4.3-23mdk
This is rather strange considering that I downloaded the driver that matches my version of XFree86 (v. 4.3-23mdk). Anyone have any ideas as to why there's a conflict if the drivers that I'm downloading are suppose to work (according to ATI) with my version of XFree86? I'm so confused. Maybe I should try downloading and installing older drivers? I really don't want to have to do that if at all possible. :/
Also, in your response to my last post, you used the command -uvh. Could you explain to me what this means? I had to use -ivh to get the file to install (-uvh wasn't recognized).
you can always do 'man any_command'
in this case, 'man rpm'
yeah rpms always conflict.
so i don't use rpms anymore.. just always compile from source.
you can just do --force
that's what i used to do when i used rpm.
didn't have much problem doing so.
if you are concerned, just get source version whenever possible
Originally posted by MentatMM I tried using the following command:
rpm -Uvh --force fglrx-glc22-4.3.0-3.2.8.i586.rpm
and the installation seemed to go fine, but then I got the following errors:
(WW) Radeon: No matching device section for instance (BusID PCI:1:0:1) found
(EE) No devices detected
Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
I'm at a loss. :/
run lspci from the command line.... and note the busid of your ATI card.
next edit the XF86Config-4 file (in the /etc/X11/ directory) use vi, scroll down and your will find the "BusID PCI:#:#:#" replace it (just the numbers after pci) with the bus id you got from lspci... my bus id was something like "PCI:00:01.1" replcae it and then you should be able to run startx
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.