Fedora 13 ATI Catalyst (fglrx) 10.11 Drivers Install/Uninstall - Comment Page: 2

I just read from my own blog about that the ATI propriety drivers is now working with Fedora 13 (thanks Jack). So I decided to test and install ATI Catalyst 10.11 (fglrx) proprietary drivers. And try new ATI Catalyst 10.11 Proprietary drivers with my ATI Radeon HD 3650 card. This is guide, howto install and uninstall ATI Catatlyst 10.11 (fglrx) Drivers. Installation is very easy with using RPMFusion Non-Free repository. But this installation guide also includes instructions, how to remove/uninstall ATI drivers. An remove/uninstall guide might be useful, if you have these problems with ATI drivers. Install ATI Catalyst (fglrx) 10.11 Proprietary Drivers on Fedora 13 1. Change root...

41 comments on “Fedora 13 ATI Catalyst (fglrx) 10.11 Drivers Install/Uninstall - Comment Page: 2

1 2
    1. Hi again JR, hi everyone,

      thought I’d ask here again, because this lovely blog with it’s guides helped me so much to get my ati radeon card running with fedora 13 in the first place. Maybe someone’s got a hint for me
      My problem is as follows:
      I’m still using fedora 13, 32bit,with the ati driver from rpmfusion. As everything worked just perfectly, I never really felt any need to upgrade to fedora 14 or later. Now I recently got some extra memory for my system, upgrading from 2gbs to 4gbs. For some reason fedora only seemed to recognize 3gbs of that memory with the non PAE kernel that I’ve been using so far.
      So, even though it says that the PAE kernel is only required for more than 4gbs of memory (and I have exactly 4gbs now, isn’t that odd?) I installed the PAE kernel. That fixed the memory problem but wrecked my video driver. When I try to start X with the PAE kernel, the screen just goes blank and the system completely hangs. The non-PAE kernel still works fine (though with 3gbs of memory). And no, I didn’t forget to install kmod-catalyst-PAE. I also read that ati propriety installer now also works for fedora, so I tried that approach. But the problem remains: I can install the latest release of the driver, buildthe module and so forth, but when I start the x server it goes all blank and hangs (yes, it hangs … can’t even access the system via ssh anymore).
      Now I’m pretty much at a loss on what to do now. Go and install the latest fedora, maybe even the 64bit one instead? I should add, I’m rather worried that a 64bit distro migth reduce performance or cause even more driver problems. Or do you have any hint on how to debug my problem? I tried to the x server output in a file, but alas, it hangs before any output is written. Any assitance would be greatly appreciated.

      Thanks,

      Jack

      @Andrew: did you check, if the driver kernel module is loaded properly (with glxinfo)? I’ve noticed that you can run the driver without, but then it’s slow as hell.

      Reply
      • Hi Jack,

        Try this:
        1. Boot to runlevel 3 without X. On Grub -> select PAE kernel and press ‘e’ -> select kernel row and press ‘e’ again -> add space and 3 end of kernel row -> press ‘enter’ -> and then press ‘b’.

        2. Install ATI drivers again with this guide.

        3. Reboot.

        And please let me know, what happens? :)

        Reply
        • Hi JR,

          don’t worry about grub, I’ve already set initdefault to 3 anyway. And I did remove and reinstall the driver a couple of times. The problem remains:
          the driver runs just perfectly with the non-PAE kernel, while I just get a blank screen with the PAE kernel. This result is exactly the same with the rpmfusion-kmod and the ati propriety installer.
          Do you happen to know, where the ati propriety driver kernel modules for each kernel are stored exactly? Maybe it just uses the wrong one. There should be 2 modules, right? One for the PAE and one for the non PAE kernel (the one I’m using right now, or I couldn’t even write this text).

          Thanks a lot in advance for any clues you might have.

          Reply
          • Hi Jack,

            Okey, what happens if you boot init 3 level and try to modprobe fglrx driver:

            
            modrpobe fglrx
            

            Then try to check is fglrx loaded:

            
            lsmod | grep fglrx
            
            Reply
    2. Hi JR,

      the module’s there, it’s just it’s not working, or something else’s not working, lsmod output:
      “fglrx 2461928 0”
      StillI’ve learnt one thing from trying as you suggested: obviuosly the ati installer exclusively places the module for current kernel into the corresponding directory. So, when I have the module, for the PAE kernel, the one for the non-PAE one is removed and vice versa. You’d need to run the installer again if you switch the kernel. However, that doesn’t seem to be the core of my problem. I can run the PAE kernel, load the module, and when I start the x server, the system crashes, while it works just fine with the “normal” kernel.
      Alas, duess, I either have to live with 1gb less memory, or I’ll have to switch to 64bits or some other distro where I don’t need that particular PAE kernel, unless you have any other suggestions? In any case thanks so much for all of your advice.

      Reply
      • Hi Jack,

        Try to check your errors on Xorg.*.log after X crash with PAE-kernel:

        
        grep "EE" /var/log/Xorg.0.log
        
        ## And/Or
        
        grep "EE" /var/log/Xorg.*.log
        
        Reply
        • Hi JR,

          I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
          For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
          just an empty file. I crashes so fast, that nothing get’s even logged or written.
          All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
          There’s one error in Xorg.9.log:
          “[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
          some old, non critical error, that has no relevance to my problem.

          Reply
        • Hi JR,

          I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
          For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
          just an empty file. It crashes so fast, that nothing get’s even logged or written.
          All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
          There’s one error in Xorg.9.log:
          “[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
          some old, non critical error, that has no relevance to my problem.

          Reply
          • Hi again Jack,

            This sounds very tricky problem, because you don’t get any errors to log. One thing what you could do is upgrade your Fedora and try to install PAE kernel and drivers on Fedora 14 or even Fedora 15.

            Reply
    3. […] Overall it can be quite the hassle to getting OpenGL work in Linux, especially if you are a newbie. However it’s absolutely worth the effort. I ditched Gnome3 because it’s absolutely bollocks. I use KDE with Compiz now on FC15 and it’s absolutely goregous. Suddenly MacOSX or Windows 7 feels like going by foot, while KDE 4.6.3. with a 2.8 Linux Kernel empowered by yum package management and backed by RedHat’s experience feels like riding a €3.500 Cube Full Suspension Bike. So good bye WindoZe and WackOSX, I am home. Links: Build Kernel Modules Official Xorg How-To fglrx interferes with radeon driver problem Fedora 13 ATI Catalyst (fglrx) 10.11 Drivers Install/Uninstall […]

      Reply
    4. Useful ! Definitely is hugely generous, pleased.

      Reply
1 2

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close