fglrx should blacklist amdgpu

This bug was fixed in the package fglrx-installer - 2:15.201-0ubuntu3

---------------
fglrx-installer (2:15.201-0ubuntu3) xenial; urgency=medium

  * debian/rules:
    - Blacklist the amdgpu driver, so that fglrx can be loaded
      on the systems where the GPU is supported by amdgpu (LP: #1510573).

 -- Alberto Milone <email address hidden> Tue, 27 Oct 2015 15:45:21 +0100

This bug was fixed in the package fglrx-installer-updates - 2:15.201-0ubuntu3

---------------
fglrx-installer-updates (2:15.201-0ubuntu3) xenial; urgency=medium

  * debian/rules:
    - Blacklist the amdgpu driver, so that fglrx can be loaded
      on the systems where the GPU is supported by amdgpu (LP: #1510573).

 -- Alberto Milone <email address hidden> Tue, 27 Oct 2015 16:49:58 +0100

Hello Alberto, or anyone else affected,

Accepted fglrx-installer into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fglrx-installer/2:15.201-0ubuntu2~15.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Alberto, or anyone else affected,

Accepted fglrx-installer-updates into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fglrx-installer-updates/2:15.201-0ubuntu2~15.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Could somebody add the SRU information [1] to the bug description. Specifically a test case so the fix can be verified.

[1] https://wiki.ubuntu.com/StableReleaseUpdates

Do you remember to reverse the whole process when going from fglrx -> open source ?

I can now switch from radeon to fglrx, but then it seems to prevent the open source radeon driver from loading when I switch back.

See bug 1493888 Post #203 for details.

@Roger: that would be a problem with the restricted drivers manager. You really need to remove the packages.

This bug was fixed in the package fglrx-installer-updates - 2:15.201-0ubuntu2~15.10.2

---------------
fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed; urgency=medium

  * debian/rules:
    - Blacklist the amdgpu driver, so that fglrx can be loaded
      on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer-updates (2:15.201-0ubuntu2~15.10.1) wily-proposed; urgency=medium

  * debian/control.in,
    debian/dkms.conf.in,
    dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
    - Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
      This prevents fglrx from dying on initialisation (LP: #1493888).
      Credit for finding out the actual problem and for suggesting a
      workaround goes to David Burrows.
      Note: this is only a workaround, and it will be dropped as soon
      as a proper fix from upstream is available.

 -- Alberto Milone <email address hidden> Wed, 28 Oct 2015 13:21:21 +0100

This bug was fixed in the package fglrx-installer - 2:15.201-0ubuntu2~15.10.2

---------------
fglrx-installer (2:15.201-0ubuntu2~15.10.2) wily-proposed; urgency=medium

  * debian/rules:
    - Blacklist the amdgpu driver, so that fglrx can be loaded
      on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer (2:15.201-0ubuntu2~15.10.1) wily-proposed; urgency=medium

  * debian/control.in,
    debian/dkms.conf.in,
    dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
    - Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
      This prevents fglrx from dying on initialisation (LP: #1493888).
      Credit for finding out the actual problem and for suggesting a
      workaround goes to David Burrows.
      Note: this is only a workaround, and it will be dropped as soon
      as a proper fix from upstream is available.

 -- Alberto Milone <email address hidden> Wed, 28 Oct 2015 13:19:25 +0100

@ SRU-Team: Package is still in proposed pocket as per today 20.11.

Has to be ssen in conjunction wt bug #1493888

They are like siamese-twins not going nowhere w/o each other...

This bug hindered user wt newer AMD to use the Upgrade. It was mentioned int the Release-Notes -so they would just endup with a black-screen. The severity has to be judged as highly critical. The culpürit was in this case AMD not beeing ready for the swift to GCC-5. This doesn't interest a user in the 1st place. The publisher of software in general has a responsibilty not to leave a user w/t a unfunctional system. A Standard user will judge his HW borked & broken on Linux. So this does not even hurt Ubuntu's-Image but the Image of the movement in a whole. This happens over and over in the last years. And people are feed with this.

Options:

1. Delay release date until fix is tested and implemented.
2. Ubitquity the Installer has the option to add a comment not to tick "yes" when it comes to the questions - Do you want to install 3rd partie Drivers.

This is a pitfall beyond believe – and it makes people turn away. Pls see also bug #1493888, reported on 9.9.2015

Hopefully this will lead to a blueprint for improvement?