Installing the Proprietary AMD Catalyst 15.7 (fglrx 15.20) driver on Fedora 22 with Linux Kernel 4.1.3

Update:  See the next post in the series for instructions regarding the new Catalyst 15.9 (fglrx 15.201) driver and Linux Kernel 4.1.6.

Process Development Summary

Alrighty then.  I apologize for the iterations of the Linux kernel which went by without any accompanying guide from this site, but I thank Leigh Scott for jumping in and providing links to his RPM-Fusion-provided akmod package.  Though there is only a package for Fedora 21, Leigh reports that it works for Fedora 22 as well.  Additional thanks to the OpenSUSE team and the Manjaro team for continuing to provide patches for the Catalyst driver in support of the latest and greatest Linux kernel version.

For those of you who prefer to install the driver the old fashioned way (such as myself), I’ll continue to provide the instructions below.  I have consolidated the patches built up between kernel version iterations into a single patch below, as well.  That has included a slight correction to Leigh’s patch for the license which uses an escape character as a slash in “GNU\Proprietary,” (I have simply changed it to a forward slash) causing the installation process to throw an error.

Known Issues (Solutions In Progress)

  • TigerVNC has a problem with the driver; KDE crashes when attempts are made to enter the VNC server session.
  • SDDM (the Simple Desktop Display Manager; successor to KDM) crashes due to SELinux denials for sddm-greeter of the following nature:
    • audit[1528]: <audit-1400> avc:  denied  { unix_read unix_write } for  pid=1528 comm=”sddm-greeter” key=17908779  scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:system_r:xserver_t
    • audit[1528]: <audit-1400> avc:  denied  { unix_read unix_write } for  pid=1528 comm=”sddm-greeter” key=17908779  scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:system_r:xserver_t
  • Kscreenlocker crashes repeatedly in the following manner:
    • abrt-hook-ccpp[23786]: Not saving repeating crash in ‘/usr/libexec/kscreenlocker_greet’
    • audit[23787]: <audit-1701> auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=23787 comm=”kscreenlocker_g” exe=”/usr/libexec/kscreenlocker_greet” sig=1
  • QEMU throws the following error when an attempt to start a guest domain is made: error: internal error: process exited while connecting to monitor: /usr/bin/qemu-system-x86_64: error while loading shared libraries: failed to map segment from shared object
    • This is an SELinux issue, as well:
      • audit[5335]: <audit-1400> avc:  denied  { execmem } for  pid=5335 comm=”qemu-system-x86″ scontext=system_u:system_r:svirt_t:s0:c78,c390 tcontext=system_u:system_r:svirt_t:s0:c78,c390 tclass=process

Prerequisite Discussion

Universal Package Prerequisites

Remaining yet unchanged, the general prerequisites are:

  • 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.
    • Note this is the protocol version, and not the server version discussed above and below.

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 22 installation, perform the following command to acquire the requisite packages:

dnf install gcc kernel-headers kernel-devel

Fedora 22 Products and the Proprietary AMD Catalyst Graphics Driver

Update:  As Mike points out, it appears the Catalyst driver merely fails to work with GDM, but it will support GNOME if some additional installation steps are followed.  It appears all you must do is that which is documented in the “do not reboot after the installation” section and the subsequent “save it replace it” section.  I would look into this myself and integrate it into these instructions if I weren’t running the KDE Spin, but feel free to ask any questions that may arise during the process or confirm that it works for others as Mike did in the comments below.

But if you don’t want to do that, I encourage you to install the Fedora 22 KDE Plasma Desktop Spin (or any non-GNOME spin to your liking).

Installing KDE In Fedora 22

If you REALLY don’t want to reinstall your OS entirely, and you don’t want to try the GNOME solution above, you can execute

dnf group install "KDE Plasma Workspaces"

And it’ll probably work.  I haven’t tested this yet (I’ll spin up a Fedora 22 Workstation VM soon), but make sure you use SDDM (the successor to KDM) as your Desktop Manager ’cause the GNOME Desktop Manager (GDM) breaks with the Catalyst driver, as well (as addressed above).

Assuming that you’ve set yourself up with KDE and SDDM in some fashion (just install the Spin), or you’re taking whatever measures necessary as described above to get around the GDM issue, you’re in good shape to simply install the driver as described below.

Installation Instructions

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

2)  Change your working directory to your ~/Downloads directory and extract the file:

$ cd ~/Downloads
$ unzip

3)  Extract the run archive:

$ 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-15.20.1046″ 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 Catalyst157-Kernel413.patch.

$ cd fglrx-install.wIhzk3
$ mv ~/Downloads/Catalyst157-Kernel413.patch.doc ~/Downloads/Catalyst157-Kernel413.patch  #WordPress does not permit me to upload a .patch file, so I add the .doc extension to lazily get around that restraint
$ mv ~/Downloads/Catalyst157-Kernel413.patch ./          #this is not necessary, but I do it for sanity's sake, to keep the patch file with the patched code as a reminder
$ patch -p0 < Catalyst157-Kernel413.patch

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

patching file common/lib/modules/fglrx/build_mod/firegl_public.c
patching file common/lib/modules/fglrx/build_mod/kcl_acpi.c
patching file common/lib/modules/fglrx/build_mod/kcl_str.c

5)  As Jacob Yates points out, one must copy the version.h header file into the build directory for the current kernel version:

$ sudo cp /usr/include/linux/version.h /lib/modules/`uname -r`/build/include/linux/

6)  Now that you’ve patched the installation package and copied the header file needed to build the module, run the installation:

$ sudo ./ 15.20 --install

7)  Choose the “Install Driver 15.20 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!

Properly Maintaining your Catalyst Implementation

Being a custom kernel module, you unfortunately must rebuild the Catalyst driver every time you upgrade the kernel version or, in some cases, other GPU-dependent packages (like mesa).  The surefire way to tell that you need to reinstall your driver is a notice from Steam (for example) that

OpenGL GLX context is not using direct rendering, which may cause performance problems.

The solution to this issue is to uninstall your driver, reboot, reinstall it, and reboot.  Don’t wait for this error to pop up after kernel upgrades, however, because you’ll probably just see a black screen and have to enter a CLI terminal to uninstall the driver.

General Guidelines

Before every kernel upgrade:

1.  Uninstall the driver

$ sudo aticonfig --uninstall

2.  Reboot

$ shutdown -r now

3.  Upgrade your system

$ sudo dnf upgrade

4.  Reboot

$ shutdown -r now

5.  Copy the header file necessary for the driver’s installation into the new kernel’s directory:

cp /usr/include/linux/version.h /lib/modules/`uname -r`/build/include/linux/

6.  Reinstall the driver

$ cd /driver/location/fglrx-install.wIhzk3   #Keep your patched driver files around and ready to go!
$ sudo ./ 15.20 --install

It’s not so bad, but it adds a little burden.  I hope to design a DKMS solution which automatically handles this for you, but I haven’t gotten to it yet.


Remember, if you see this message:

“Your Graphics adapter is not supported by this driver. Installation will not proceed”

Check out the post to which that link sends you for a potential resolution for your problem.  You probably have an Intel CPU with an on-die Haswell GPU combined with a Radeon GPU, but let me know if you don’t, or if you encounter an issue that that post doesn’t resolve.

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

77 Responses to Installing the Proprietary AMD Catalyst 15.7 (fglrx 15.20) driver on Fedora 22 with Linux Kernel 4.1.3

  1. Pietro Pesci Feltri says:

    I just try installing the driver following your instructions. It worked well, including the the work with AMD OpenCL SDK.


  2. derekk says:

    It works! Thank you bro!

  3. hckr says:

    Having not realized the new kernel upgrade, I broke the system. After uninstalling the driver in rescue mode, I re-installed it using the guide above. Now my system works with fedora 22+kernel 4.1.3+GNOME+gdm(auto-login enabled).

    Thanks again.

  4. Akshay says:

    I did exactly as mentioned on Fedora 22 Kernel 4.1.3-201 but it does not work. Installation is successful but when I reboot then SDDM login screen just does not come up and SDDM never loads. I had to then boot into text mode and uninstall the driver to get KDE working again. Any idea what I could be missing.

    • Did you see the note about the SELinux failures for SDDM? Some people have resolved the issue by mashing the audit2allow utility repeatedly (four or five times, apparently) until the system works as expected. I intend to try to develop a bit more of an elegant solution, but for now, give that a try.

      • Akshay says:

        Ok I upgraded to 4.1.4-200 and re-installed the driver. But same problem. The error I see is:

        type=AVC msg=audit(1439255791.529:500): avc: denied { sigchld } for pid=1450 comm=”abrt-hook-ccpp” scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
        Was caused by:
        Missing type enforcement (TE) allow rule.

        You can use audit2allow to generate a loadable module to allow this access.

        I tried using audit2allow but that won’t work. Any pointers?

  5. Muresan Mihai says:

    Thank you! with this patch I was able to install the driver on Fedora 22 KDE Kernel 4.1.4

  6. baktolio says:

    looks like 4.1.4 is out… will wait on the new patch i guess…

  7. amadren says:

    Worked perfectly on Fedora 22 with kernel 4.1.4, thanks !

  8. Sev says:

    Most recent Kernel update with current guide and switch to lightdm from gdm still working great 🙂

  9. Ed says:

    Thank you. Works fine for Fedora 22 with 4.1.4-200.fc22.x86_64 and X.Org X Server 1.17.2 !

    One addition to the General guidelines before every kernel upgrade:
    Before step 5, do not forget to copy the header file:
    cp /usr/include/linux/version.h /lib/modules/`uname -r`/build/include/linux/

  10. Ignasi says:

    Hey guys, I need to install amd drivers for a Firepro D500 (W7000 equivalent) in a macpro6,1 (late 2013 trash-can), running fed22 k4.1.4.
    I first tried the unified firepro drivers from
    but the installer didn’t recognize my card, so it complained.
    I also tried to install the Catalyst drivers, following this guide and the installation goes flawless, without any error message. But it freezes after the first reboot.
    Do you have any experience with a d500?

    • Well, unfortunately, I have no experience with the FirePro drivers (I had never even heard of them until you just pointed them out). However, it may be that the installer doesn’t recognize your card because the radeon driver is powering off the card when it’s not being used. Did you try this method for resolving that potential issue? It might not be the problem since I would expect the same issue to afflict your attempt at installing the Catalyst driver, but it’s perhaps worth a shot.

      Regarding the freezes after installing Catalyst, at what point does your system freeze?

      • Ignasi says:

        Yes I tried diabling the radeon PM, as sugested, but it still complains.
        It freezes just before the log-in.
        The install log seem sane to me, though. let me know if you need me to show you any screenshots of upload the log.
        Thanks man!

  11. Kris says:

    This tutorial also works for new kernel 4.1.5-200. I follow the steps and it is work in my computer.

  12. derekk75j says:

    works fine in 4.1.5 kernel too!! Thanks!!

  13. g1ra says:

    KDE spin on Fedora 22 with kernel 4.1.5 does not work . I got a white login screen . I wrote my password blind. The KDE desktop appeared, but all the windows shifted right with ~500px.

    Do you think I might success with older drivers? Like 14.12 ?

    • Well, it does seem to work for me and other users.. The white login screen is the result of an AVC denial (SELinux) against SDDM. I’m working on a simple resolution to it, but for now, entering your password semi-blind (I can see some visual feedback in the form of a fugly pink box indicating that I’m typing) should suffice (that’s what I’ve been doing since I haven’t sat down to develop the solution yet).

      Regarding your pixel shift, did you try making use of an old Xorg.conf file as I pointed out in my instructions? My displays were stubbornly misconfigured as well until I made use of an older config file which I had used successfully with previous iterations of the driver. If you can’t do that (maybe you haven’t successfully used the driver in the past on your current system), I’d be glad to try to help you to fix it manually.

  14. Mo says:

    The steps also work with kernel 4.1.6

  15. Asdas says:

    I just noticed that there is a mistake in the step 5 of “Before every kernel update”. The name of the folder is written with capital L (*/Linux/) while it should be */linux/

  16. MC says:

    Hi, recently was released a new kernel 4.2, and it contains a lot of changes connected with asm/i387. I have a problem with build the drivers. Can you try to fix it?

    • stretchxfce says:

      From ubuntu wily i found and edited a bit this patch file ( i managed to install catalyst with kernel 4.2 and Debian Stretch 64-bit, but Xorg caused segmentation fault at boot):

      — common/lib/modules/fglrx/build_mod/firegl_public.c
      +++ common/lib/modules/fglrx/build_mod/firegl_public.c
      @@ -191,9 +191,17 @@

      #include “firegl_public.h”
      @@ -1698,6 +1706,9 @@ void ATI_API_CALL KCL_SetCurrentProcessState(KCL_ENUM_ProcessState state)

      #if defined(__i386__)
      #ifndef __HAVE_ARCH_CMPXCHG
      +#ifndef __xg
      +#define __xg(x) ((volatile long *)(x))
      static inline
      unsigned long __fgl_cmpxchg(volatile void *ptr, unsigned long old,
      unsigned long new, int size)
      @@ -1734,7 +1745,11 @@ unsigned long ATI_API_CALL kcl__cmpxchg(volatile void *ptr, unsigned long old,
      unsigned long new, int size)
      #ifndef __HAVE_ARCH_CMPXCHG
      +#if defined(__i386__)
      return __fgl_cmpxchg(ptr,old,new,size);
      +#elif defined(__x86_64__)
      + return cmpxchg((unsigned long*)ptr,old,new);
      /* On kernel version 2.6.34 passing a variable or unsupported size
      * argument to the __cmpxchg macro causes the default-clause of a
      @@ -6430,21 +6445,36 @@ static int KCL_fpu_save_init(struct task_struct *tsk)
      struct fpu *fpu = &tsk->thread.fpu;

      if(static_cpu_has(X86_FEATURE_XSAVE)) {
      +#if LINUX_VERSION_CODE state->xsave.xsave_hdr.xstate_bv & XSTATE_FP))
      + copy_xregs_to_kernel(&fpu->state.xsave);
      + if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP))
      return 1;
      } else if (static_cpu_has(X86_FEATURE_FXSR)) {
      + copy_fxregs_to_kernel(fpu);
      } else {
      asm volatile("fnsave %[fx]; fwait"
      +#if LINUX_VERSION_CODE state->fsave));
      + : [fx] “=m” (fpu->state.fsave));
      return 0;

      +#if LINUX_VERSION_CODE state->fxsave.swd & X87_FSW_ES)) {
      asm volatile(“fnclex”);
      return 0;
      return 1;
      @@ -6456,8 +6486,12 @@ static int KCL_fpu_save_init(struct task_struct *tsk)
      void ATI_API_CALL KCL_fpu_begin(void)
      #ifdef CONFIG_X86_64
      + __kernel_fpu_begin();
      #ifdef TS_USEDFPU
      struct thread_info *cur_thread = current_thread_info();
      struct task_struct *cur_task = get_current();
      @@ -6502,7 +6536,11 @@ void ATI_API_CALL KCL_fpu_begin(void)
      void ATI_API_CALL KCL_fpu_end(void)
      + __kernel_fpu_end();

      /** Create new directory entry under "/proc/…."


  17. Mohamed A. Farouk says:

    Hey, I wanna thank you so much for this. Great Work! .. It works on 4.1.6-200 kernel. About the white login screen I tried switching SELinux to Permissive mode and it’s gone. Everything seems to be working really sweet now 😀

  18. Jabber says:

    Thx, works fine with 4.1.6-200.

  19. skilletliquor says:

    Seemed to install ok, but on reboot system hangs at ‘Stopped User Manager for UID 42’.

    Can’t boot into safe mode.

    Any advice?

  20. Sev says:

    Not able to uninstall the radeon driver keep

    • Sev says:

      Apologies, holding my daughter and she decided to hit reply :D. Either way here is the error I’m getting when trying to uninstall.

      *** AMD Catalyst(TM) Proprietary Driver Uninstall Log 2015-08-27 22:04:53 ***
      md5sum integrity check failed for /usr/lib64/xorg/modules/drivers/
      One or more files have been altered since installation.
      Uninstall will not be completed.

      To force uninstall, removing all installed files without verification,
      run /usr/share/ati/ –force.

      Forcing uninstall is not recommended and may cause system corruption.

      Anyone have any luck force uninstalling or any tips for getting it done.

      Thanks in advance to any help other’s can provide.


  21. timsoft says:

    after forcing uninstall you probably have to reinstall mesa (in text mode). this should restore the opensource opengl libraries. ( You may also have to remove the module blacklisting as well, but that is less likely.) I have had to do that a few times (with success).

  22. Nall White. says:

    Hello, I’m new to Linux and Fedora. I tried this and keep getting “bash: patch: command not found”. I’m running desktop 22 wth kernel 4.1.6. Please help. Thanks.

  23. R4v3nPr0 says:

    To get GDM and SDDM working well, you only need to modify /etc/selinux/config to disable selinux

  24. Istvan Meszaros says:

    Excellent guide, many-many thanks! Of course, it works (Fedora 22, 4.1.6)!

  25. Sameer Dhar says:

    First of all thanks to your effort i have a successful install of the ati drivers.
    A strange thing happened, first time I installed it went without any problem and no white log in screen, perfect install. second time around (I had crashed my system), it gives me the white screen on the log in screen. My major problem is that i use Cinnamon as the desktop manager, first time it installed and I logged in into Cinnamon, everything worked fine. Could you find a work around for the white screen.

    Thanks for the effort.

    Regards Sameer

  26. Sameer Dhar says:

    Sorry, totally forgot, SeLinux in permissive mode sorts it out. Thanks once again.

  27. vergil says:

    cant do the 5th step no such directory

  28. spookyfox says:

    hi, i screwed up and updated the kernel without uninstalling catalyst first, but if I log in safe mode and do “sudo aticonfig –uninstall” it says aticonfig is not a command.

    Please help? I can’t log into my fedora at all, I’m stuck with windows

    • Kris says:

      you can find this /usr/share/ati/ or /usr/share/ati/ and use it to uninstall fglrx driver.
      Just boot with init 3 mode from grub and execute one of the above command. Sometimes you have to add –force or similar options. That command will tell you if you have use –force options or not.

  29. galladhan says:

    Working perfectly with kernel 4.1.6-201 here. Thank you very much! 🙂

      • Nall White says:

        Is there any order to install these? I’ve downloaded these files. Thanks.

    • Mariano says:

      Does it work on F22 kernel 4.1.6?

    • Mariano says:

      I downloaded all files I found for x86_64, and it does not install claiming catalyst-kmod-common is not available. Is that one missing?

      • Leigh Scott says:

        xorg-x11-drv-catalyst provides it

      • Mariano says:

        Thank you for answering! When I tried to install all parts at once, I got the following:
        nothing provides kernel-uname-r = 4.1.7-100.fc21.x86_64 needed by kmod-catalyst-4.1.7-100.fc21.x86_64-1:15.9-2.fc21.x86_64

        Since I’m running on F22 with kernel 4.1.6-201, I’m at a loss of what I could do (unless I try a dirty trick, by setting an alias for “uname” command).

      • Ah, your command syntax seems to have been incorrect. Paste it in a comment so I can help if you can’t figure it out, but you should write (and can copy and paste from the post):

        sudo cp /usr/include/linux/version.h /lib/modules/`uname -r`/build/include/linux/

        Those are backticks around the `uname -r` part.

      • Mariano says:

        I don’t think so, as I copied version.h using the discrete pathname (/lib/modules/4.1.6-201.fc22.x86_64/source/include/linux/). I also tried by installing using the repository, as Leigh said, and following instructions to make it work with Gnome, but after reboot I got the error message AFTER login credentials on lightdm (grey screen with ugly face). So I uninstalled everything and reverted to radeon module. If I can find a way to make it work around the error mentioned here (that “nothing provides kernel -uname”), I’ll try again tomorrow (I need to sleep, it’s 3:15AM…). Thank you!

      • Hm, I was inferring that from the presence of the “kernel-uname-r” text in the error you reported, but now I see that the kernel version doesn’t match the one you have installed (whatever throws that error seems to be looking for materials relevant to kernel 4.1.7-100.fc21 and you’re running 4.1.6-200.fc22). Are you installing from Leigh’s Fedora 21 RPMFusion package, I take it? If so, the information you have provided might be sufficient for him to assist with the issue. Or, you could always try following my process.

    • Alex says:

      Leigh, thanks again for providing this. I am on Fedora rawhide/ 23 Beta and added your repo
      I tried installing akmod-catalyst but it didn’t work. I also tried installing the xorg-x11-drv-catalyst-devel-15.9-1.fc21.x86_64.rpm because I am on devel release I reckoned, but didn’t work out either. Am I doing anything wrong? Are you interested in errors/ logs (where would I find those?)?

    • Romain says:

      Hi Leigh,

      thx for this!
      The manual install works fine for me but not able to use your packages for some reason :

      – akmod builds and installs fine according to the akmod log.
      – kernel module is loaded at boot
      – no apparent error in Xorg.0.log (although it didn’t initially find so to get further along i symlink’ed it from /usr/lib64/dri/

      glxinfo says the screen is not DRI2 capable :

      romain@desktop:[/data/romain]$ LIBGL_DEBUG=verbose glxinfo | head -n20
      libGL: screen 0 does not appear to be DRI2 capable
      libGL error: failed to load driver: swrast

      direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
      server glx vendor string: ATI

      client glx vendor string: Mesa Project and SGI

      Everything works fine if i manually install the patched driver but it has to be rebuilt on each kernel update which is a bit of a pain…

      • Romain says:

        Actually i think i figured it out. it was linking against the standard mesa*
        I’ve added /usr/lib64/catalyst in front of my LD_LIBRARY_PATH and re-sourced the shell config.

        glxinfo now picks up the correct libGL.
        Not having to reinstall at each kernel update will be nice.

      • Alex says:

        “Actually i think i figured it out. it was linking against the standard mesa*
        I’ve added /usr/lib64/catalyst in front of my LD_LIBRARY_PATH and re-sourced the shell config.

        glxinfo now picks up the correct libGL.
        Not having to reinstall at each kernel update will be nice.”
        Wow, you actually did it?? Congratulations! Bitwiseoperator should know this. Can you give me exact steps? That would be really nice. For example I don’t know what re-sourcing the shell means. Also, can you share some info about the problem? I’m just curious. Thanks Romain!

  30. Leigh Scott says:

    Try the f21 packages (they work fine on f22), xorg-x11-drv-catalyst* packages aren’t compiled code so will run on any fedora version.
    akmod-catalyst compiles once installed so is ok a well.

    sudo dnf install akmods kernel-devel
    sudo dnf –releasever 21 –enablerepo rpmfusion-nonfree-updates-testing install akmod-catalyst xorg-x11-drv-catalyst-libs.i68b8

    • Mariano says:

      Thanks for replying, Leigh. Just one question: will that work with Gnome, or should I also follow the additional steps mentioned earlier in this post (about gdm and lightdm)?

  31. jacuzzi says:

    echo -ne ‘/amd_xversion’ | dd conv=notrunc bs=1 count=13 seek=$offset

    this command gives. dd: invalid number ” error every time tried in 15.9 and 15.7, gnome 4.16 kernel

    • I get the same problem. I just tired this install and it failed. Fortunately, for me, I make a backup image with Clonezilla before I attempt anything like this. I just finished a restore of my original image. I want to attempt this again, but there seems to be a few bugs.

  32. But what about >4.20 kernel versions? Does it make sense to switch to new Fedora 23?

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 )

Google photo

You are commenting using your Google 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 )

Connecting to %s