Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Location: The edge of the world, peering down into the dark abyss
Distribution: Gentoo 2004.2
Hey, that's exactally what I did:
1. Download Drivers
2. Install kernel source
3. rpm -i --force <ati_driver>.rpm
(note: with me, the reboot hung, but it didn't affect the drivers)
6. run an Xscreensaver or tuxracer to see if it worked
7. alternately, type fglrxinfo at the konsole. If it says fglrx instead of mesa, then you installed them correctly
This should work on RH too. I think? Since it also is RPM based??
As far as slackware, I don't think that the drivers actually work. What I did, is I used rpm2tgz, then installpkg, but it didn't load the module. So I ran the build_mod/make.sh, but it couldn't find the linux sources. I fould the kernel sources, and created a link to them where the build_mod/make.sh file thought they were, but when it saw them, it said that one of the xfree files was the wrong version (whatever).
Anyhoo, I gave upon Slack and went back to Mandrake 9.1. Drake did it fine
Not to be repetetive ~ But Mesa is NOT installed right? These Mesa drivers can cause a whole world of pain.
A tailored kernel module just means that the module was adjusted to work with your hardware. I'm not too keen on how the ATI driver specifically works (whether it builds a unique module or edits the existing ATI driver), but I would assume tailored means it tweaks the ATI module that comes as part of the 2.4 kernel and gives additional support for newer ATI cards.
Now the only difference between your output on the install and mine is that failed at the end. Are you any good with modifying kernels? Run xconfig to make sure that your kernel actually has the module turned on for the ATI Radeon drivers (I turned on both ATI modules). Make sure any other DRM modules are also turned off (you should be able to get by just turning off any 3Dfx modules though if you're unsure about which are safe to turn off or not).
3Dfx modules can have conflicts with ATI modules, and as the ATI module is not truly stable installing them can cause all of these issues. Regretfully, ATI doesn't support Linux with their hardware, so all of their hardware drivers are half assed and don't run at their full potential
I apologize for getting a bit confused ~ I didn't realize how many people were having ATI issues in this forum; so some of my suggestions to you may have been directed at Enigma Z.
Before you go about tweaking the kernel (which you really shouldn't have to unless you've tweaked it before), I need to make sure you ran those two scripts that the fglrx install tells you to run? ./make.sh and ./make_install.sh? These are extremely important and do the actual building of the kernel for you. Again, sorry if this is a dumb question, I just got really confused.
If you've run that and you still have problems, when you installed your kernel, did you use an old kernel config or did you make a new one? Making a new one can be unsafe for a bewb if you're not quite sure what's necessary and what isn't. If you used an old config, then you might want to try tweaking the kernel. However, since this can have quite drastic side effects back everything up and make a boot disk if possible (I've never compiled a kernel that fit on a 3.5 floppy though, but try it anyways).
You don't have to be sorry and i appreciate everything you had helped me!
There isn't many pals like you who always answer questions with passion and bits of kindness.
For my configuration.
Yes, i had uninstalled Mesa long times ago and i am sure it wasn't in my system no more.
Also, i had download a update Mesa driver and demos from www.mesa3d.org
Is it necessary for me to installed it. The reason why was today i was trying to update my kde packages and it saids mesa wasn't installed while it's checking independences. It was Mesa-5.0.2
For the part about kernel. I had deal with kernel for a few months and i don't really under stand what you had said about turned on ATI modules and turn off other DRM modules?
Where can i go after the Linux Kernel Configuration window had appeared?
Under which section are u talking about?
Hmmm ~ The config menu is tough since I'm in the process of installing Gentoo on the Linux side of my machine right now so I can't get to it...try multimedia devices, I know that in the list of sections if it's not in that specific group it's in one of the ones listed nearby.
Once you open up a section you'll be presented with a list of features that the kernel has available to it. You can set these to Y/M/N. Y and N are obvious, however M stands for module. Yes would build the specific feature directly into the kernel while module would load it up as a separate module. The ATI drivers can only be loaded as modules. I've been meaning to find a good book on how the kernel works (anybody know of a good one) so that I can learn more about it, but at the moment I can't tell you how you would benefit from loading a module versus installing directly to the kernel.
That post and Gentoo installation is 100% of my experience with the kernel as of yet, however that guide should explain to you how to tweak the kernel to do what you'd like.
If you uninstalled Mesa and yet it still comes up under fglrxinfo then somehow it got reinstalled...I had this happen before, and, sorry to say, I was about to format the drive anyways so I never really fixed it. Try building Mesa from the source to see what kind of output you get. Somewhere inside your box, something's saying that mesa is installed. I believe if you type in glgears or something along those lines a Mesa demo should pop up, if it runs you know Mesa is definately installed (Could somebody post the command required to run Mesa Gears?).
Again ~ I don't believe this really has anything to do with your kernel specifically though. Read through Thetargos' kernel tutorial and maybe something was switched off (He also explains DRM modules in there). Your kernel _should_ work fine once you run those two shell scripts that are provided with the ATI driver. Are you getting any type of error running these? Or do they install fine?
Double-check these shell scripts don't have any error output. And find out where Mesa is installed. You may need to change the path veriable so KDE recognizes it.
This is going out on a limb, but I believe Mesa comes with KDE? If you're installing the updated KDE rpm's make sure you're running every single package at the exact same time. Every package for KDE depends on the others, so if Mesa is in there somewhere you won't have the dependency issue.
(I installed KDE 3.1.4 with rpm -Uvh a* k* q*)
Give those shell scripts a whirl and find out more about your Mesa libs before you jump into the kernel. Unless you're feeling brave
Yesterday, i was messing with the libraries and after i trying to uninstall the glibc. then it shows something was error and after that i can't exe a command such as "ls".
So, i was pissed and got my linux redhatlinux9.0 reinstalled. Under the condition of it seems that there was a library which seems to important to ati drivers wasn't available in my old system. I had just chose installed the whole thing in redhatlinux9.0. Somehow, when i had installed ati's driver 3.2.5. It shows no error in the process and i did already got ride of mesa. But still it shows
Since the beginning of this thread you've never said that you ran the provided shell scripts, just that you've installed the RPM. These are two completely separate steps, and installing the RPM does not install the shell scripts. Have you run them?
It doesn't matter how many times you run the RPM, or how many times you run fglrxconfig. Without these scripts installed you're going to run in circles.