Installing the Proprietary AMD Catalyst 14.12 (fglrx) Driver on Fedora 21

Update:  See the next post in this series for information regarding the installation of the fglrx 14.12 driver in Fedora 21 with kernel version 3.19.1-201.fc21.x86_64.

The release of Fedora 21 and the productization of the operating system has resulted in some new details to which an AMD GPU owner must pay attention:

Prerequisite Discussion

Universal Package Prerequisites

As stated by the “installer.html” document provided by the driver, the prerequisites are as follows:

  • GCC version 3.3.3 or higher.
  • Kernel headers or kernel sources matching version of the kernel you’re running.
    Please consult to documentation for your distribution how to get and install this.
  • XFree86 version 4.1.X, 4.2.X, 4.3.X, or XOrg version 6.8.X (Fedora 20 does not use XFree86) or higher.

Heed the warning:

  • If you have multiple version of X Window System installed on your computer the installer will try to detect the default X, and install the driver for the detected version. However, you could experience problems trying to run other versions of X after this. Also, if your X Window System is installed into a nonstandard location, installation of the driver could be either problematic or incomplete.

With a fully up-to-date Fedora 21 installation, perform the following command to acquire the requisite packages:

yum install gcc kernel-headers kernel-devel

Fedora 21 Products and the Proprietary AMD Catalyst Graphics Driver

So, as you are likely aware, the Catalyst driver does not work with GNOME.  As you may also be aware, Fedora 21 Workstation, the product designed for the purposes you’re most likely to have in mind if you’re using your system like a normal person, integrates GNOME into the OS more than previous Fedora iterations.  In fact, if you’re using Fedora 21 Workstation, you won’t even see the GNOME Desktop Environment group in yum – it’s hidden by default.  Removing the GNOME Desktop Environment from the Workstation implementation is difficult and attempts to install alternate Desktop Environments currently meet with package conflict issues.

Using GNOME with the AMD Catalyst Driver on Fedora 21

Thanks to reader Fox for directing me to Red Hat intern Levente Kurusa’s guide which allows users to install the Catalyst driver on a system running GNOME.  The problem is, as you might expect, it’s quite the burdensome process.  In my estimation, it’s easier to simply use KDE, but if you’re really attached to GNOME, you might give his method a try.

I’d also like to point out that he uses my exact patch (same timestamps and everything) without attribution, but here I am spreading the good word about his work.  NO HARD FEELINGS OR ANYTHING.  =)

Using KDE With Fedora 21

The best course of action for someone interested in running KDE in Fedora 21 is to either install the KDE Spin or upgrade from a version of Fedora 20 already using KDE with the nonproduct product option.

Now, if you’re like me and you accidentally upgraded to Fedora 21 Workstation (and therefore now have GNOME on your system), you’ll find that certain issues occur (see the link above) and changing Fedora 21 products is not easy.  I haven’t yet really dug into the product architecture so I don’t have the best answer regarding the move from Workstation to Nonproduct, but you can still install KDE (see the “changing Fedora 21 products is not easy” link above) and keep GNOME on your system for times during kernel upgrades (and therefore the required uninstallation and reinstallation of the Catalyst driver) when you need a GNOME fix or something.  Just make sure you use KDM as your Desktop Manager (I haven’t tested the procedure on Fedora 21, but I suspect it’s identical to the procedure I laid out in the original post on this subject way back in March of 2014 – let me know if it doesn’t work for you), ’cause the GNOME Desktop Manager (GDM) breaks with the Catalyst driver, as well.

Once you’ve set yourself up with KDE and KDM on Fedora 21, you’re in good shape to simply install the driver using a slightly modified version of the Fedora 20 procedure which has been presented on this site for some time:

Installation Instructions

1)  Download the AMD Catalyst 14.12 (fglrx) driver from AMD’s site.

2)  Change your working directory to your ~/Downloads directory and extract the file (it will extract into a directory named fglrx-14.501.1003 in the current working directory):

cd ~/Downloads

3)  Change your working directory to the fglrx-14.501.1003 directory and extract the driver file:

cd fglrx-14.501.1003/
sh --extract

Here, you’ll see a message which reads something like:  “Created directory fglrx-install.wIhzk3″ and then “Verifying archive integrity… All good.” followed by a “Uncompressing AMD Catalyst(TM) Proprietary Driver-14.501.1003″ followed by a lot of dots.

4)  Now, you should see a newly created folder called fglrx-install.whateveryourcomputernamedit (mine, for example, was fglrx-install.wIhzk3).  Change your working directory appropriately and apply the 3.17_kernel.patch:

cd fglrx-install.wIhzk3
mv ~/Downloads/3.17_kernel.patch ./          #this is not necessary, but I do it for sanity's sake
patch -p0 < 3.17_kernel.patch

If you are successful, you will see the following output:

patching file common/lib/modules/fglrx/build_mod/kcl_acpi.c”

5)  Now that you’ve patched the installation package, run the installation:

sudo ./ 14.501 --install

7)  Choose the “Install Driver 14.501 on X.Org 6.9 or later 64-bit” option from the Setup Wizard, and then simply follow the prompts.

Ensure that you do not select “Generate Distribution Specific Driver Package (Recommended)”.  This will only work if you use one of the officially supported Linux distributions listed on AMD’s site (Fedora is not included).

8)  Reboot your machine and enjoy!

This entry was posted in Information Technology and tagged , , , . Bookmark the permalink.

61 Responses to Installing the Proprietary AMD Catalyst 14.12 (fglrx) Driver on Fedora 21

  1. achalverson says:


    On a fresh install, the Catalyst installer exits with an error about pre-requisites not being installed. I have read your earlier tutorials, so I know which ones to install, but newer users might balk at this and/or not be able to find and install the dependencies. It would be helpful if you were to include them in this article.


  2. ilevex says:

    Hey there,

    Wow! I’m not sure how I forgot to attribute you, I’m very sorry about that! 😦 Fixing that ASAP!


    • Haha! No problem, man. In my original post with the patch, you can see that I got my understanding of the fix from a developer going by “Philm” on the Manjaro team. We all help each other out, and it’s nice to create a good web of connections between information. I was just making fun in a way that I didn’t figure you’d ever see, to be honest. =)

      Keep up the good work – it’s nice to have some software developers looking at this problem as well. I appreciate your efforts.

  3. Max Gonzih says:


    I’m trying to install catalyst on fedora 21 on macbook pro (early 2011 model) and have some issues. I tried to run it with kdm, lightdm, slim but everything fails during x start procedure.

    I’m getting error like:

    [fglrx:riregl_get_vbios_image] *ERROR* Invalid image size requested
    [fglrx:firegl_cail_query_parameter] *ERROR* CAIL_QueryParameter failed

    Not sure how to tackle this problem. Do you have any tips?

    • Well, I see that your Mac has both an Intel GPU (built into the CPU) and an AMD Radeon 6750M or 6490M, depending on the model. Others have had trouble getting systems with on-die Intel GPUs to work, but they’ve typically had trouble during installation, where the Catalyst installer doesn’t recognize that they have AMD GPUs. I hypothesized that the installer was seeing the Intel GPU and giving up, so one other reader tried my hypothetical solution of disabling the i915 driver using modprobe, leaving only the AMD hardware for the Catalyst driver to deal with, but he was unable to get that solution to work.

      It looks like someone on the Ubuntu forums had the same problem you have. That user was able to resolve the matter and he documented his solution. It looks like his solutions involve the use of the rEFIt boot manager, and I’m unfamiliar with the product so I can’t say much about it, but you should at least read through what he has to say. His notes at the end regarding the kernel parameters i915.modeset=0 and radeon.modeset=1 are pretty interesting to me given my previous hypothesis regarding the disabling of the Intel GPU with modprobe.

      See what you can figure out and let me know if I can help you further. Without a test system of my own, the best I can do is offer hypotheses.

      • gonzih says:

        Thank you for your reply.

        I tried modeset, does not help in case with proprietary drivers.
        Seems like digging in to rEFIt is only solution that also might brick my laptop in case of failure 🙂
        Anyway I tried to install catalyst because sleep functionality is broken with open source drivers. Maybe you have any idea why is that? I found few issues related to ubuntu, seems like they are not fixed yet.


      • Unfortunately, I just don’t use the open source drivers due to their many problems and inferior performance. I’m definitely interested in their development, and I hope they do well (I wish I had more bandwidth to help out), but I’m sticking to the proprietary drivers in the meanwhile. Let me know if you get that MacBook working – sorry I can’t be of more assistance!

  4. Gelidus says:


    while trying to execute your patch, I am getting this while it waits for input at the end. Any idea what I am doing wrong? Command I am using : patch -p0 < 3-17_kernel-patch

    (Stripping trailing CRs from patch; use –binary to disable.)
    can't find file to patch at input line 3
    Perhaps you used the wrong -p or –strip option?
    The text leading up to this was:
    |— common/lib/modules/fglrx/build_mod/kcl_acpi.c 2014-09-23 10:42:10.000000000 -0400
    |+++ common/lib/modules/fglrx/build_mod/kcl_acpi.c 2014-11-13 16:44:23.187112123 -0500
    File to patch:

    Thank you

    • Gelidus says:

      Just forgot to say: I am using newly installed fedora 21. Also, can graphic drivers help to adjust screen resolution. My screen has 1600×900 resolution but fedora can recognize just 1280×720 at this time.

      • Gelidus says:

        My bad, just realized I moved the patch to the fglrx folder but not to the newly created folder.

  5. Gelidus says:


    So I tried your tutorial, but my fedora 21 won’t boot correctly again. I ran yum update after the installation, and after that your commands. Can it be I haven’t met some prerequisites?

    This is all I’ve got

    I can’t boot rescue mode to see logs, it also stops there. Any idea what can be wrong?

    Thank you

    • denisgoddard says:

      Gelidus, the last line in your output says it’s starting the Gnome Desktop Manager (GDM). That should not be the case. You need to replace it with the KDE desktop manager.
      FWIW, in my case, installing Fedora with the KDE Spin was the easiest and most surefire solution.

  6. denisgoddard says:

    Well, using Fedora with the KDE Spin I was able to get everything working and everything was awesome for about 2 weeks. Then I accepted a Fedora update with lots of upgraded modules and didn’t do a backup first. Bad move. After the update, now the X system does not come up, I’m reduced to using the alt TTYs. I see this error in /var/log/Xorg.0.log :

    * DRI initialization failed *
    * kernel module (fglrx.ko) may be missing or incompatible *
    * 2D and 3D acceleration disabled *

    If I run “startx” manually (which I never had to do before), I get an X desktop briefly, and then a warning that something crashed.

    Some Googling leads me to believe that Xorg 1.16 Won’t Work with fglrx.ko ; is that the case? Do I need to downgrade Xorg to 1.15 and keep it there?

    • No, I don’t believe you need to downgrade your X server. I am running a fully-updated Fedora 21 installation with FGLRX in good working order. Did you perhaps perform a kernel update without uninstalling the FGLRX module first? Try from your TTY executing aticonfig --uninstall and let me know what happens. If you can successfully uninstall the module, a reboot should give you back your desktop, and you should then be able to simply reinstall.

      • danielripoll140 says:

        Hi again,

        Same thing happens to me, something in dkms is failing.

        Kernel 3.17.7-300
        Xorg 1.16.3

        AmdCCLE is not installed so GL-restricted apps (like QT creator) didn’t work 😦

        The computer is pretty near to a “clean” installation, gcc, headers and nothing more.

        I also tries the same patch with 3.18 and… Worst results

      • So Daniel, you can log into the system and reach a command line interface, right? If so, can you execute aticonfig --uninstall and see what happens? If the command succeeds, reboot and all should be well (you can then reinstall the Catalyst driver). If the command fails, post the output back here and we’ll figure out what to do.

        This issue occurs most commonly, in my experience, when you install a kernel update without first uninstalling the Catalyst driver. To resolve the issue, I have typically performed the steps I list above.

      • The issue happened with a clean installation (just requisites and kernel update, no catalyst driver before).

        Anyway, as you ask me I tried and still happens the problem… 😦

        Uninstall output:

        Install output:

      • Well, the only thing I can think of after looking at your files there is that the uninstall operation appears to run into errors, and if you don’t have a clean uninstallation, it may disrupt your installation attempt. Can you examine /etc/ati/fglrx-uninstall.log and try to manually perform operations it cites as having run into trouble?

        I’m not sure what’s going on, but I can say with certainty that my installation of Fedora 21 with all the latest updates works with the method I have provided, so it seems the issue must be particular to your system in some way.

      • difs says:


        First, thanks for the blog.

        The same is happening with me. I have tried with the newer kernel and the old one (clean install). Everything went well until the reboot.

        * Problem: X system does not come up, I’m reduced to using the alt TTYs.*
        * OS: Fedora 21 KDE
        * APU: A10-7850K
        * Motherboard: ASRock FM2A88X
        * Xorg.0.log Errors:

        [ 12.983] (EE) systemd-logind: failed to get session: PID 909 does not belong to any known session

        [ 13.933] (EE) fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible.
        [ 13.933] (WW) fglrx(0): ***********************************************************
        [ 13.933] (WW) fglrx(0): * DRI initialization failed *
        [ 13.933] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
        [ 13.933] (WW) fglrx(0): * 2D and 3D acceleration disabled *
        [ 13.933] (WW) fglrx(0): ***********************************************************

        * fglrx-install.log

        Supported adapter detected.
        Check if system has the tools required for installation.
        Uninstalling any previously installed drivers.

        Creating symlink /var/lib/dkms/fglrx/14.501.1003/source ->

        DKMS: add completed.

        Kernel preparation unnecessary for this kernel. Skipping…

        Building module:
        cleaning build area…
        cd /var/lib/dkms/fglrx/14.501.1003/build; sh –nohints –uname_r=3.18.3-201.fc21.x86_64 –norootcheck…..
        cleaning build area…

        DKMS: build completed.

        Running module version sanity check.
        – Original module
        – No original module exists within this kernel
        – Installation
        – Installing to /lib/modules/3.18.3-201.fc21.x86_64/extra/
        Adding any weak-modules


        DKMS: install completed.
        [Reboot] Kernel Module : dracut

      • So, your installation log looks identical to mine, but obviously something is going wrong with the installation process since your Xorg log indicates that there is a problem with the kernel module. Three suggestions:

        1) Make sure all your packages are completely up to date.
        2) Check your prerequisite packages and ensure that they are the latest versions, especially your kernel headers (I’ve seen some people who somehow have kernel headers for old kernels on their system, despite running the latest kernel).
        3) Execute aticonfig --uninstall and ensure the output reflects a clean operation with no errors. Then, restart, make sure everything looks ok, and retry the installation.

      • difs says:

        I have managed to install without any problems after a bios update. It is still working even after the system update and the newer kernel.

        I hope this can help.

        Cheers. Thanks again for the blog!

      • Hey, nice work! Good to know.

  7. Hi again my dear bitwiseoperator:

    I’m writing to letting you know some good news. As you already will know, with great problems usually come great (or at least crazy) solutions.

    Tired of trying to install catalyst on kernel 3.17.7 I just did the following (if someone is in the same situation):

    1) aticonfig –uninstall
    2) Check /etc/ati/fglrx-uninstall.log
    3) /usr/lib/modules/3.17.7-300.fc21.x86_64/extra/fglrx.ko wasn’t deleted by some stupid reason. I deleted it manually with a rm -rf /usr/lib/modules/3.17.7-300.fc21.x86_64/extra/fglrx.ko
    4) reboot and fallback to kernel 3.17.4
    5) upgrade kernel to 3.18.3-201.fc21.x86_64 and remove 3.17.7 which gave me, not only problems with catalyst but with virtualbox also.
    6) reboot again in the new 3.18.3
    7) Apply your patch but changing 3.17.0 for 3.18.0
    8) Everything seems ok
    9) reboot, got catalyst and amdcccle.

    Now everything works, including the Vbox.

    It’s weird but it looks that somehow the 3.17.7 has got some kind of crap or corruption, dunno why.

    Thanks for all man, as allways, keep up the good work going on.

  8. youmu says:

    Thanx for the patch. It works with 3.18.5 kernel. But I have another problem. I get “OpenGL GLX context is not using direct rendering, which may cause performance problems” when I run steam. How can I get it works?
    Fedora 21 x64 KDE; 3.18.5 kernel

    • Typically, this problem is a result of a faulty installation. Try:

      1) Execute aticonfig –uninstall.
      2) Restart your system.
      3) Fully update the system with yum update and restart.
      4) Install the Catalyst driver by following the instructions provided by this post.
      5) Restart your system.

      See if that fixes it. If not, we may need to investigate some log files to see if we can determine what’s going wrong.

  9. mizoguchi666777 says:

    On hybrid systems, for amd installer detecting radeon card do:
    nano /etc/default/grub

    add “radeon.runpm=0” to kernel command line

    grub2-mkconfig -o /boot/grub2/grub.cfg
    mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-old.img
    dracut /boot/initramfs-$(uname -r).img $(uname -r)



  10. oli says:

    thanks, also worked with fedora 21 and catalyst 14.12/kernel 3.18.7

  11. Must Die says:

    Supported adapter detected.
    Check if system has the tools required for installation.
    fglrx installation requires that the system have kernel headers for 3.7 release. /lib/modules/3.18.6-200.fc21.x86_64/build/include/generated/uapi/linux/version.h cannot be found on this system.
    One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver.
    Optionally, run the installer with –force option to install without the tools.
    Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended.

    • Can you post the output of yum list kernel-headers? It looks like you don’t have the right headers package. You may be able to remedy the situation simply by executing yum install kernel-headers. Make sure you have all the prerequisites outlined in this post.

  12. Choco says:

    Thanks again for this guide. You’ve helped me recover my netbook yet again. I appreciate the detail you put into it.

    One note: after step 5) of running the script, you mislabel the next step as 7). 🙂

  13. Thank you for writing this! I am on a mission to get Catalyst working with Linux. After numerous failures in Ubuntu, I thought I’d try a different distro. Just happened to pick Fedora KDE spin. After stumbling onto your blog, it feels like I’m on the right track!
    I’m new to using patches in Linux and I’m getting some errors.
    [root@localhost fglrx-install.WSoeoX]# patch -p0 < 3.17_kernel-patch
    bash: patch: command not found
    However I can test for a Man page for patch and that did come up just fine.
    [root@localhost fglrx-install.WSoeoX]# man patch

    Any suggestions?
    Thanks again!

    • Hey, glad I could help! I’m sure we can get you up and running. The patch executable you’re looking for is by default stored in /usr/bin/patch, so you can check to see if it’s there; it could be that your root account’s PATH variable doesn’t include /usr/bin, so the shell is not finding the executable when you type it in without fully qualifying its path. If you do find that /usr/bin/patch exists on your system, you can modify the root PATH variable or, more simply, just use the command “/usr/bin/patch -p0 < 3.17_kernel-patch" instead.

      The package which supplies the executable is, unsurprisingly, called "patch". If you execute yum install patch, you can note the output and determine what's going on, as well.

      • Thanks again for the prompt reply. Despite seeing a man page for patch, it did need to be installed. I was able to patch and start the installation process. Unfortunately, the installer gave me an error that “Your graphics adapter is not supported by this driver. Installation will not proceed.”
        I have an AMD A10-5750M APU with Radeon HD Graphics. I’m not sure which other driver I could use. AMD’s driver website points both the GPU and APU drivers for Linux to the same Omega 14.12 package. This A10 is supposed to be one of their better processors. It would be pretty lousy if they just didn’t bother supporting it.
        Any suggestions?

      • Well, as I just said to Fabio below, this could be an issue with the dynamic power management feature in the Linux kernel and Radeon cards. I’m surprised, though, that the GPU built into the APU would be undetectable by the Catalyst installer, so it doesn’t seem likely that this is the issue. I, too, use an A10 APU, but mine is not the mobility version and I’ve never known anyone to install this driver for your particular APU, so I can’t say for certain that it does work, but it sure seems like it ought to (by AMD’s own decree, even, as you found out on their site).

        Maybe give the power management feature solution a try? There aren’t too many steps involved, so you could roll back the effort pretty easily if it doesn’t help.

      • Thanks again. Earlier I was looking over the other thread you mentioned and I tried the nano/etc/default/grub command to which I got a no such file or directory error. I’m running this in a virtual machine which doesn’t have grub. Is there something else that could be edited to give the same result? If these graphics processors are just powered off and I can get them working, I did find some good news. “Both Unified Video Decoder (UVD) and Video Codec Engine (VCE) are present on the dies of all products and supported by AMD Catalyst AND BY THE FREE AND OPEN SOURCE GRAPHICS DEVICE DRIVER #ATI/AMD. …in strong contrast to Nvidia, which does offer its own proprietary driver similar to AMD Catalyst, but does not provide any support or assistance to any free graphics initiatives”
        It looks like the graphics processors I have are Radeon HD 8650G which should be supported by the opensource Radeonsi driver developed by AMD.
        Quotes above taken from Wikipedia if you want the links.

      • Ooooooh – you’re in a virtual machine! Well, I’m sorry to be the one to break it to you, but unless you have a motherboard that supports AMD-Vi and you’ve configured it properly to assign your GPU directly to a VM using hardware interrupt remapping, your VM won’t have the requisite access to either of your GPUs necessary to use the Catalyst driver.

        That’s your problem. There’s no way around it except to either run Fedora directly (i.e. without a hypervisor) on your laptop or with a hypervisor through the use of technology such as AMD-Vi.

  14. Fabio says:

    your tutorial was what i was looking for to try fixing my FC21 installation that had stopped working in gui mode (don’t know why, it was after installing a program called Stellarium).
    Unfotunately, at step 7) it says that “Your Graphics adaper is not supported by this driver. Installation will not proceed”. 😦
    My machine is a Lenovo notebook G50-70 and the graphic adapter is an AMD Radeon GHD 8550M/R5 M230 (rev ff)
    Any clue?

    • Hey man – looks like you’re running into a common problem; your system has not only a Radeon card, but also an Intel HD Graphics 4400 GPU built into the CPU. The Catalyst installer does not appear to handle this situation well.

      I had initially suspected that the issue was due to the AMD Catalyst driver installation application incompetently handling the detection of the Radeon card when it appears in conjunction with another GPU. However, another reader of the blog, mizoguchi666777, points us to another user solving a different, but related problem.

      The idea behind the solution appears to be that the dynamic power management feature introduced in kernel 3.13 is causing your Radeon card to be powered down and therefore undetectable by the Catalyst installation application. Starting the kernel by adding radeon.runpm=0 to its arguments in GRUB (which I would first try by simply editing the kernel line in GRUB at boot, if you’re comfortable doing that) should disable the power management feature and keep your card powered on and available to the Catalyst installation application.

      Since I don’t have a system on which to test this solution, I’d be very interested in your results. Like I said, I’d first try just modifying the GRUB line and booting, then attempting an installation of the driver, but if that doesn’t work, try using dracut to create a new initramfs as mizoguchi666777 points out in his comment. Let me know what you find!

      • Fabio says:

        Hi, I’ve taken your advice modyfing the GRUB’s kernel line at boot and it installed! Unfortunately, I’m still experiencing faults trying to start X server (caught signal 11, segmentatino fault). I’m trying wirth vaious versions of X server from 1.14 forward, with no luck until now.

      • Hmmm – good to know that the GRUB line modification actually does succeed in allowing the Catalyst driver to install properly. These X server segmentation faults – I presume they don’t occur when you don’t have the driver installed? What Desktop Environment and Desktop Manager are you using?

  15. I’ve been doing my best to research the AMD-VI feature. I’ve got part numbers for processor, motherboard and BIOS/UEFI version, but finding documentation for each item related to AMD-VI isn’t that great. Is there a bash command that could tell me if it’s enabled?
    As for the virtual machine, I’ve got a dual boot with Window’s 8.1 and Ubuntu 14.10. I specifically bought this laptop knowing I wanted to do a lot of virtualization so I’d really like to make sure this AMD-VI is properly set up.
    VM-Player running on Ubuntu gave me an error about Hardware graphics acceleration and 3D support not being available from the host. That along with Steam errors is what got me really digging into this Catalyst issue. After striking out with everything I tried, it occurred to me to try a different distro. Since Catalyst works great on the Windows side, I used it for the host and ran Fedora21 with KDE in Virtualbox. If everything works flawlessly in VirtualBox with Fed21, and I can’t get the same results with Ubuntu, I might switch my Linux partition to Fedora. I’m interested in learning more about Fedora either way.
    That issue with the power management features turning off the graphics processors could be effecting my Ubuntu and as that is loaded by Grub, I might try that tweak mentioned earlier.

    • Just to be clear: AMD-Vi is required for using IOMMU and hardware interrupt remapping to allow a virtual machine direct access to hardware such as graphics cards and other PCI devices. You can still virtualize Fedora without this sort of functionality. Of course, software which requires hardware graphics acceleration (such as Steam) won’t work, but using that software in a virtual environment is unusual. I once planned on virtualizing Windows 8 on my Fedora machine and using AMD-Vi to provide a GPU to that VM so that I could play Windows-only Steam games without having to boot into Windows directly, but that was almost more academic in interest than practical.

      I can’t tell what, exactly, you’re trying to do; it looks like you ran into issues with hardware graphics acceleration and 3D support in your Ubuntu partition when trying to use VM-Player, so you are attempting to address this issue by running Fedora in VirtualBox in your Windows partition to test its ability to work with your system. If I’m right about that, your troubleshooting method is introducing quite a lot of variables – Fedora on VirtualBox in Windows hardly suffices as any sort of a hardware compatibility test between Fedora and your laptop, if that’s what you’re attempting. You could use it to test Fedora’s ability to work with your GPU if you can get AMD-Vi configured properly, but currently VirtualBox doesn’t support hardware interrupt remapping in Windows (, so you’re out of luck there. Windows Hyper-V may support AMD-Vi, but I have never seen it done and a Google results in speculative dismissal of the possibility.

      Basically, if you are trying to simply get around the Ubuntu graphics acceleration problem, you should probably focus your energy on it more directly, rather than attempting to test OS-hardware compatibility virtually (which is almost insane, but if you were extremely technically talented, perhaps possible). You could also try installing Fedora on a USB drive and booting from that – you don’t need much space for a test OS.

      Let me know how I can help you further, or if I’ve presumed incorrectly anything above.

      • Thanks yet again. I don’t know why I didn’t try the USB install. I’ve done USB installs before but I didn’t realize how many variables the virtual machine was introducing. I’m a virtualization newbie and my Linux skills are average. I was first introduced to Linux around 1999. Been gradually using it more and more. I’m at a point now where I use Linux more than Windows, but editing kernels and grub files are a learning experience. I’m currently an IT student looking forward to becoming a more advanced user.
        After having trouble getting Catalyst to work in Ubuntu, my thought was to see if Ubuntu was the factor not working since Catalyst works great on the same machine running Windows. My intention was to substitute the Ubuntu factor for a different distribution. Adding more factors was unintentional. The USB stick install is a good idea. I also have 10GB unallocated space on my hard drive. I could put Fedora there. Then Grub and all other hardware factors would be identical to my Ubuntu partition.

  16. Johnny Chang says:

    Hello, I just updated the kernel to version 3.19 in my fedora 21 installation. Each time I do this I have to force install the catalyst driver. I have already patched this to work since it was released. But this time it give me an error and refuse to compile the modules. Below is the install log.

    Supported adapter detected.
    Detected a previous installation, /usr/share/ati/
    Installation with force option.
    Check if system has the tools required for installation.
    fglrx installation is being forced. Installation will proceed without the required tools on the system.
    Uninstalling any previously installed drivers.
    AMD Catalyst(TM) Proprietary Driver Uninstall is corrupt. Uninstall script ‘’ is missing.
    /usr/share/ati/ completed with 1
    [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
    doing Makefile based build for kernel 2.6.x and higher
    rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
    make -C /lib/modules/3.19.1-201.fc21.x86_64/build SUBDIRS=/usr/lib/modules/fglrx/build_mod/2.6.x modules
    make[1]: Entering directory ‘/usr/src/kernels/3.19.1-201.fc21.x86_64’
    CC [M] /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
    /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ‘kasSetExecutionLevel’:
    /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration]
    orig_level = __get_cpu_var(kasExecutionLevel);
    /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4820:38: error: lvalue required as left operand of assignment
    __get_cpu_var(kasExecutionLevel) = level;
    /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
    /usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
    static int KCL_fpu_save_init(struct task_struct *tsk)
    cc1: some warnings being treated as errors
    scripts/ recipe for target ‘/usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o’ failed
    make[2]: *** [/usr/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
    Makefile:1386: recipe for target ‘_module_/usr/lib/modules/fglrx/build_mod/2.6.x’ failed
    make[1]: *** [_module_/usr/lib/modules/fglrx/build_mod/2.6.x] Error 2
    make[1]: Leaving directory ‘/usr/src/kernels/3.19.1-201.fc21.x86_64’
    Makefile:88: recipe for target ‘kmod_build’ failed
    make: *** [kmod_build] Error 2
    build failed with return value 2
    [Error] Kernel Module : Failed to compile kernel module – please consult readme.
    [Reboot] Kernel Module : dracut

    By the way I am using an A10-7850k integrated graphics. Thank You in advance for any you can give to solve my problem.

    • Thanks for the log data – I am encountering what I believe to be the same issue and I am in the process of troubleshooting it. In the meanwhile, let me know if you make any headway, yourself.

      • Johnny Chang says:

        Installed KDMS and got similar result about being unable to compile kernel modules, albeit with a less detailed log. Thank You for your promt reply and any possible hint.

  17. Johnny Chang says:

    I meant DKMS and prompt, wishing for an edit in comments 😉

  18. Eder says:

    My kernel is 3.19 on fedora 21. Can I use the patch in this version?. If i can not, what I do?.

    • Yes! Just run through the steps as written and apply both the 3.17 and 3.19 patches (they are named according to the kernels which first introduce the issues they address). I should combine the patches into one and name it more appropriately, but I just haven’t gotten off my butt to do it yet.

  19. Kenguru says:


    Today i’m testing something 🙂
    Fedora 22 beta + fglrx 🙂

    Fedora 22 is using kernel version 4 . So I decided testing the stuff

    first run:
    fglrx install is failed, because
    firegl_public.c contain some old things (read_cr4 and write_cr4 functions )
    if i’m not make a big mistake and my knowledge is right these functions changed in the new kernel version, somewhere on the internet i’m find something about it…
    so i’m change some lines read_cr4 to __read_cr4 and write_cr4 to __write_cr4
    ok this solution is not a technically right solution, because i’m not using if statements and other really useful things.

    Second run:
    install failed again…
    BUT no more read/write_cr4 error \o/
    The kcl_str.c was the bad guy (line 172)
    “return strnicmp(s1, s2, count);”
    so i change it to something similar ( i read some patchfile, and i write these lines)

    return strnicmp(s1, s2, count);
    return strncasecmp(s1, s2, count);

    third run:
    no error, installation is complete, all things look so great

    but, after the reboot, i have a great blinking cursor, xorg log say something about oslookupcolor+0x139 but i'm give up for today, I'm too tired

    Ohh one more thing, sorry for my english, i'm start learning it again since a few months ago.

    • Wow, hey, thanks for the information – I’m glad you’re working on this before Fedora 22 is officially released. I’ve been waiting it out since the machine I use to test the driver is my production workstation and I kinda need it up and running. Your English is impressively legible for a few months’ practice – good work there, as well!

      • Kenguru says:

        Thank you for the great words 🙂

        i have more information, i don’t know this error is system side or driver side, but the uninstall script isn’t work correctly.
        I’m uninstall the driver with aticonfig –uninstall and now have graphic interface, but some files remains in the system, e.g. ati xorg.conf

        so now i’m re-install the whole system, write a patch file for 4.0 kernel, and i will try again :

  20. @Kenguru, what’s the update? 🙂

  21. froller says:

    Is there a patch for 4.0.4?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s