FGLRX incompatible with gcc 5

[Allen Webb]

SRU Request:

[Impact]

The fglrx driver is not compatible with gcc 5.x. This causes the kernel module to crash on initialisation. As a result, users will boot into a black screen, as X will fail (except on Intel+AMD hybrid systems, where intel is used).

[Test Case]
1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
2. Reboot
3. Check the display, and the output of the "dmesg | grep fglrx" command (to see the actual crash)

Expected results: the system should be able to start X correctly.

Actual results:
The kernel module fails and X doesn't start.

[Regression Potential]
Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be replaced with the proper fix once AMD makes it available.

__________________________________________________________________________

With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am able to SSH into the machine. I booted the older kernel (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and using xserver-xorg-video-radeon I am able to get the graphics working, but even it has issues with my display port (The DVI ports are working correctly).

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
Date: Wed Sep 9 09:29:54 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-01-07 (1705 days ago)
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

[Allen Webb (vertago1-s)]

It looks like this has been reported upstream: http://ati.cchtml.com/show_bug.cgi?id=1189

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sascha Biermanns (skbierm)]

Same with the AMD Radeon 6600M and 6700M Series, even with the newest 4.2-10 version.

[Sascha Biermanns (skbierm)]

Workaround at the moment: Still booting up with the 4.1.0-3 kernel version.

[B. (b-deactivatedaccount-deactivatedaccount)]

Same problem on iMac15,1 with Radeon R9 M295X Mac Edition
and 4.2.0-7-generic (wily / 15.10)

Two partial workarounds:

- downgrade to 4.1.0-3-generic and install fglrx-updates
  but bluetooth will not work --broken with this kernel*
  http://www.spinics.net/lists/linux-bluetooth/msg64098.html

- use 4.2.0-7-generic but remove fglrx-updates (fglrx-amdcccle etc.)
  bluetooth will work but no radeon hardware acceleration (No Steam, etc.)

In my case I need to choose between bluetooth devies and 3d graphics (radeaon)

[mark (markrmiller)]

I don't have the older kernel available as a workaround and doesn't seem so easy to rollback otherwise. This going to be fixed before the release?

[mark (markrmiller)]

I got it working. Grabbed the 3 deb files I needed for 4.1 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-unstable/.

[Moritz Oberhauser (zomtir)]

fglrx falls back to xserver-xorg-video-ati when fglrx is installed, because the fglrx module can't be loaded on boot. If you force booting with fglrx by removing the x-org mesa packages, it freezes on boot.

My card is a Radeon R270X ITX on Ubuntu 15.10.

[Yusuf Ismail Bin Shukor (linkinpark-neon)]

Confirmed not working on Ubuntu 15.10 64bit with my AMD R9 390 on kernel 4.2.0-16.

Both fglrx and fglrx-updates will return a black screen of death upon reboot after installation. The only way to revive the system is to do a fresh install.

This will cause many people to break their systems when they choose to upgrade their systems to 15.10 with an AMD card and attempt to install Catalyst.

I'm going to try the Kernel 4.1 workaround now, see if it works or not.

[Yusuf Ismail Bin Shukor (linkinpark-neon)]

Just tried using Kernel 4.1.0-040100 and then attempted to install both fglrx and fglrx-updates. Both installed, and upon reboot there is a working desktop, but it's not the Catalyst driver that's running.

It's defaulting back to stock Mesa 11.0.2, even though Additional Drivers states that the fglrx driver is in use.

I do not know if this would be useful, but this is my dmesg file currently:
http://paste.ubuntu.com/12795659/

[RussianNeuroMancer (russianneuromancer)]

Since this will just give black screen after upgrade on affected systems I think this issue need to be highlighted in release notes, so people who could be affected by this bug switch to open driver or postpone upgrade to Wily until AMD release new fglrx.

[RussianNeuroMancer (russianneuromancer)]

https://phoronix.com/scan.php?page=news_item&px=Ubuntu-15.10-4.2-Cat-Not-Ready

[Paolo Rotolo (paolorotolo)]

Hey guys,
any ETA on this?

I'm on Ubuntu 15.10 since August and I can only use open source drivers with my AMD GPU.
Let me know if you need additional info.

[Zeioth (zeioth)]

I've fixed it downgrading the kernel as described in phoronix. Using "sudo apt-get purge linux-image-yourversionhere" and sudo "apt-get purge fglrx", then reinstalling the drivers again with "apt-get install fglrx" and "aticonfig --initial".

[Zeioth (zeioth)]

By the way I tried kernel 4.1 and I had problems entering to recovery mode > resume. Just stick with 3.19 meanwhile.

[Alberto Milone (albertomilone)]

@Paolo: not yet. We are going to fix this ASAP.

I have added an entry in the release notes for now.

Sorry for the inconvenience.

[xpris (xpris)]

Very strange. I use Ubuntu 15.04 and I install kernel 4.2.0 from ubuntu ppa kernel team and use kolasa patch https://github.com/kolasa/fglrx-core-15.201
and kernel and fglrx driver works fine.

Also in my second system I use Mageia 6 Cauldron (unstable) and have (from system repo) kernel 4.2 and new fglrx and works fine.
So why this fix can be backported to Ubuntu 15.10?

[Serge (sspapilin)]

I have AMD A4 APU. Boot freezes at splash screen with Ubuntu logo.

The open source drivers lead to black screen, just like it was in 15.04 and may be even earlier. So it's an illusion that the open source drivers are viable workaround for everyone.

[Daniel Svetlik (dsvetlik)]

I have a PITCAIRN PRO 7850 and boot freezes at splash screen. Could not access other ttys. Got in with laptop that upgraded fine with ssh and was able to get default monitor and display settings only, but cannot succesfully get open source drivers or fglrx working fully.

[Stephen Bochinski (stephenbochinski)]

This affects me and my card as well. I have an ATI R9 200x and cannot use fglrx with kernel 4.2.

[Đorđe (djole94hns)]

MSI Radeon R9 270 here, not working on kernel 4.2

Any news on the fix?

[Alberto Milone (albertomilone)]

On 22-10-15 17:44:52, xpris wrote:
> Very strange. I use Ubuntu 15.04 and I install kernel 4.2.0 from ubuntu ppa kernel team and use kolasa patch https://github.com/kolasa/fglrx-core-15.201
> and kernel and fglrx driver works fine.

Maybe there is something that we are missing in our patches (Kolasa
seems to have included some of our patches). It's hard to tell from the
build log. I'll look into this.

[Paolo Rotolo (paolorotolo)]

Kolasa patches from GitHub don't work anymore on Ubuntu 15.10: https://github.com/kolasa/fglrx-core-15.201/issues/2

Is there a PPA to test latest patched drivers on Wily?

[prashantm (prashant-mirjankar)]

Affects me too on Amd A4-5000 freezes at splash screen

[Luca Ciavatta (cialu)]

Same here, on a Radeon HD5450.

[xpris (xpris)]

So, look like some is wrong in Ubuntu 15.10, because in Ubuntu 15.04 kolasa patch working fine with kernel 4.2.0.

I try now install new fglrx and kernel 4.2 on Mageia 5 (stable but kernel from Cauldron) and kolasa patch don't want work. I must use this command before installation:
sudo cp /usr/include/linux/version.h /lib/modules/`uname -r`/build/include/linux/
Now installation is complete and all good.

So, Ubuntu 15.04 works with kolasa patch, Mageia 6 Cauldron works with driver from repository and Mageia 5 work if we use kolasa patch + one command line.

This command is from Fedora, see here: https://bluehatrecord.wordpress.com/2015/09/17/installing-the-proprietary-amd-catalyst-15-9-fglrx-15-201-driver-on-fedora-22-with-linux-kernel-4-1-6/

[EricDHH (ericdhh)]

Radeon r9-270, only console since upgrade

[ 9.106329] [<ffffffff817ef9f2>] ? entry_SYSCALL_64_fastpath+0x16/0x75
[ 9.106331] Code: df 00 00 00 48 89 54 24 08 89 4c 24 04 ff e6 0f 29 7b f1 0f 29 73 e1 0f 29 6b d1 0f 29 63 c1 0f 29 5b b1 0f 29 53 a1 0f 29 4b 91 <0f> 29 43 81 e8 76 96 fc ff 48 89 c7 e8 5e ae fd ff 44 89 e1 c1
[ 9.106357] RIP [<ffffffffc025d251>] firegl_trace+0x61/0x1e0 [fglrx]
[ 9.106415] RSP <ffff8800cd1a3a78>
[ 9.106438] ---[ end trace eae68d146e85ec62 ]---

[Serge (sspapilin)]

One of duplicate bugs contains a patch forcing compilation with gcc 4.9:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1501276/comments/3
The patch is confirmed to be working in a further comment.

[Vertago1 (vertago1)]

The patch in #29 worked for me.

[Dimitrij Krasovsky (kdi)]

Affects me on AMD A10-7870K.

Temporary using the open source driver, which works, but causes me to halt all OpenGL development and gaming (Steam).

[dualboot (guycarre)]

Hello

 Same issue with Wily embedded kernel 4.2 and AMD graphic card 7850.
My solution was to uninstall kernel 4.2.

 Hope a solution will be found soon.

Regards,

[Josef Andersson (northar)]

Same here of course. Thanks to all involved in reporting, and fixing--- Rant:How is it possible that 15.10 goes to release with a bug like this, affecting so many users (yes, the ubuntu releases should be tested on nvidia and amd moderna cards before release). Yes, I do love Ubuntu, and Yes I know it should be AMD releasing their source and specs, but still -- shouldnẗ this be a release blocker.

[Ian (superian)]

Yes - in the nicest possible way, HTF was this allowed to survive unfixed at release and WTF isn't this documented in the release notes for the Ubuntu-MATE flavour for one?

Just how bad does a bug have to be to block a release?

[L-Train (so1dieroffortune)]

It's puzzling that Ubuntu continues to release software that make the PC unusable for A LARGE subset of users. Several months ago, while using Ubuntu 15.04, a new kernel version was released that made it impossible to log in and it affected every single user with AMD video card that used binary drivers. And now this bug again appears to affect every single user with an AMD card/ binary drivers combo. I remember hearing Shuttleworth describing Cannonical testing environment and how everything is automated and how they put a lot of effort to perfect it, blah blah blah. But how can this be when Ubuntu routinely releases software that deterministically renders computer 100% unusable for everyone with an AMD video card? It just doesn't make any sense. How are these kinds of bugs not release show stoppers?

[Aizuddin Zali (aizuddin-linux)]

my application wont display correctly with radeon driver due to needs of fglrx API. Hope this can be fixed soon.

[Blain Kristian Stocking (blain-s)]

R270X

none of my installed kernels worked:

4.2.0-16
3.19.0-31
3.16.0-34

purge fglrx has resolved issue for now

[Roger Barrett (roger-m-d-barrett)]

@northar: The general view seems to be that open source drivers must work, but not necessarily the closed source, except for LTS releases.

Personally I think the closed-source graphics card drivers are important enough that they should be fixed before release; it seems that every second release has problems for me.

On the positive side, the open source graphics stacks are catching up, and both AMD/NVidia seem to be paying more attention to their drivers, so perhaps these problems will diminish over time.

[Richard Ayotte (rich-ayotte)]

@so1dieroffortune Blame AMD, it's their closed source drivers that don't work. AMD does not support kernels greater than 3.19 as shown in their 15.9 release notes here http://support.amd.com/en-us/download/desktop?os=Linux+x86. The 4.0 kernel was released on April 12th, 2015 which is plenty of time for AMD to update their drivers. There's not way that AMD needs more than 6 months to make their drivers compatible with the 4.0 kernels. In fact, I would estimate that one of their engineers could make the compatibility fixes in less than week.

[Sergey Kislyakov (defman21)]

Compiling the fglrx-installer with gcc 4.9 fixed this problem, but it's a workaround and not the fix. (I guess).
You can get the patch here: https://launchpadlibrarian.net/219738583/fglrx-installer-15.201_force-gcc_4.9.patch
Don't forget to freeze the fglrx-* packages after installing the fixed debs or Ubuntu could update your drivers and replace them with the broken drivers.

[Alberto Milone (albertomilone)]

I am going to test the workaround here, and request an SRU for it. I will also involve AMD to see if we can get an actual fix for it.

[Yusuf Ismail Bin Shukor (linkinpark-neon)]

Thank you Alberto, I know it's not easy trying to get AMD to budge. We appreciate your efforts, looking forward to being able to use Catalyst on Ubuntu 15.10 soon :)

[Chiel Douwes (chieltbest)]

I was able to successfully apply the patch in #29, and I can confirm it working on kernel 4.2.0-16-generic, 7950 card.
After applying the patch I manually had to:
1. blacklist the radeon module.
2. execute aticonfig --initial.
3. freeze the installed packages.

[Sergey Kislyakov (defman21)]

Why you had to blacklist the radeon module?

[Nerdknight (nerdknight)]

The patch in #29 also works for me, with a 6700M card. If you install fglrx you must uninstall radeon drivers

[Alberto Milone (albertomilone)]

On 24-10-15 18:37:06, Nerdknight wrote:
> The patch in #29 also works for me, with a 6700M card. If you install
> fglrx you must uninstall radeon drivers
>

That is already dealt with by the package. I imagine gpu-manager
disabled fglrx when it failed.

[dazza5000 (darran-kelinske)]

Could someone please write how to apply the patch? Thank you!

[Sergey Kislyakov (defman21)]

cd /tmp/
apt-get source fglrx-updates
sudo apt-get build-dep fglrx-core
cd fglrx-installer-updates-15.201/
wget -O fix.patch https://launchpadlibrarian.net/219738583/fglrx-installer-15.201_force-gcc_4.9.patch
patch -p1 < fix.patch
dpkg-buildpackage -us -uc
cd ../
mkdir fglrx-driver
mv *.deb fglrx-driver/
cd fglrx-driver/
dpkg -i *.deb
sudo amdconfig --initial
sudo apt-mark hold fglrx-updates-core
sudo apt-mark hold fglrx-updates
OR
Download my deb packages here: https://www.dropbox.com/sh/m3hbyrs52gb09ur/AABCgiL56W3rQWO-rpyrClXia?dl=0

[Sergey Kislyakov (defman21)]

Ohh, of course you should sudo dpkg -i *.deb, sorry for my mistake :(

[Zeioth (zeioth)]

Personally I 've been using the open source drivers and I'm surprised of how good they are. All my games run at the same FPS than catalyst. Plus they will not break your computer.

[Sergey Kislyakov (defman21)]

Unfortunately I'm experiencing laggy interface with open-source drivers and about 15-20FPS when Firefox is opened and I'm moving some windows on the screen. And it's gone away with fglrx :\ My videocard is strong enough (R9 280X, 3GB GDDR5)

[Plaiasu Costin (cplaiasu)]

The patch also works for me!
AMD A8-3870 Radeon HD 6550D GPU and kernel 4.2.0-16-lowlatency

[L-Train (so1dieroffortune)]

@rich-ayotte I don't think it's fair to "blame AMD". They suck, but the question is what does Canonical do about the non-working AMD drivers? Canonical should detect the fact that the drivers don't work and do one of 2 things:

1) Postpone the release, or
2) When doing an upgrade - prompt a human being with a warning sign: "If you proceed with this upgrade your PC will not work since AMD binary drivers are known to be broken"

Whatever happened with the "Linux for human beings" slogan? Either you say "Blame AMD" or "Linux for Human Beings". You can't have it both ways. A Human being couldn't care less about which nerdy engineer made their PC unusable. What they do know however, is that Canonical decided to break their computer and NOT so by mistake since it was 100% known to Canonical that that the PC would break on the upgrade and they did nothing about it.

[QIII (qiii)]

Alberto --

This is the second time I have been involved in a major disaster affecting the fglrx driver. It took quite some time to fix the one that I reported a few months ago.

I asked that that bug be raised to "critical" as it affected an entire class of users.

I understand that the heat is not high on this because of the low number of users indicating they are affected, but I think it is clear that this is a big problem.

This time, would you get with your colleagues and get this one raised to critical?

Unless Canonical is interested in alienating all AMD graphics users, this needs to be fixed yesterday.

[Påvel Nicklasson (pavelnicklasson)]

AMD Radeon 6650M
It's this kind of bug that make you lose confidence in Ubuntu/Canonical.

[Hanmac (hanmac)]

falling back to radeon after some problems (i only got vesa)

runing /usr/bin/software-properties-gtk --open-tab=4
 (is part of my GPU)

says Trinity HD7660D
then it says Cedar Radeon HD 5000/6000/7350/8350 Series
(it changes each time i start software-properties-gtk which should not!!)

sometimes it does say its uses manual driver, sometimes it says it used recommend one

it says three greyed options (the driver)
and the only option which is manual, why cant i switch to the normal video-ati one?

also somehow not all my resolutions are supported :(

[Hanmac (hanmac)]

and it says LAPTOP about my sceene which is NOT!

[Hemal (rathod-hemal)]

I am too having problems with Ubuntu 15.10 and fglrx on my AMD HD7770 card.

I tried every fglrx package from amd site and from Ubuntu but when installed, on next boot screen hangs on purple screen

Then I need to reboot in recovery and unintelligible fglrx and default driver with 1024x768 resolution returns.

Any workaround?

[Luca Finzi Contini (lucafinzicontini-8)]

Hi all. I too had the problem, much the same way as I had with 14.04 LTS some months ago.
This time I followed this post and managed to uninstall fglrx-* packages and get my system to boot again:

http://askubuntu.com/questions/620869/15-04-installed-fglrx-amd-ati-drivers-wont-boot

But anyways, I agree with those who said that it's unpleasant to be faced with the issue of a non-functioning system basically within the last 3 releases or something. It could be OK for non-LTS releases, because you know you're about to get the bleeding edge software, but I hope that would not come again on the next LTS :)

In the meantime, a huge THANKS to all the people involved in the fix.

[RussianNeuroMancer (russianneuromancer)]

This is seems like GCC 5 incompatibility rather than Linux 4.2 incompatibility.

Alberto, maybe bug title and description should be corrected?

[Paolo Rotolo (paolorotolo)]

Even GCC patch doesn't work for me (AMD HD7790).
After boot I'm only able to see the cursor on a black screen.

[Paolo (vihochiamatiamici)]

Same problem here. I'm running Ubuntu 15.10 with 4.2.0-16-generic kernel on a Lenovo z50 (AMD). This laptop comes whit an AMD FX-7500 core and a AMD R7-M260DX graphic card. When installing fglrx-updates I could only obtain a black screen. I had to enter a root shell in recovery mode and uninstall the driver.

[Hemal (rathod-hemal)]

I can confirm that, the .deb files in comment #48 are working fine with me on dual monitor.

I am using Ubuntu 15.10, Kernel 4.2, AMD HD7770 and above said FGLRX files.

This might be the temporary solution.

Please be alerted about official patch release.

[Hemal (rathod-hemal)]

I am new here so just want to know this.

On this bug report, at top , it is stated that 'Fix Released'. But I cant find any fixed deb files.

I tried all deb files but was not working so I tried as per comment #48 and its working now.

But what does that 'Fix Released' sign means at top. And how can i find those fixed files.

[Robert Hutton (rwh-helms-deep)]

@Hemal: A fix was released for the release notes only. The bug on fglrx-installer is merely "Confirmed".

[Hemal (rathod-hemal)]

@Robert : Thank you for information.

[Billy (billyway)]

@Serge Thanks !
gcc 4.9 does work on my pc

I am too lazy to patch, just soft linking gcc to 4.9

sudo ln -sf /usr/bin/gcc-4.9 /usr/bin/gcc
sudo /etc/kernel/prerm.d/dkms 4.2.0-16-generic
sudo /etc/kernel/postinst.d/dkms 4.2.0-16-generic

and it works

http://ati.cchtml.com/show_bug.cgi?id=1189#c11

[Daniel Svetlik (dsvetlik)]

I am using xubuntu, and it requires 3 clicks from the release announcement to find any reference to this issue. You have to go to:

http://xubuntu.org/news/xubuntu-15-10-release/ then click to
https://wiki.ubuntu.com/WilyWerewolf/FinalRelease/Xubuntu and then click to
https://wiki.ubuntu.com/WilyWerewolf/ReleaseNotes#Known_issues

At least now I know to go back to open source drivers fully before upgrading in the future. Thanks to everyone here for the helpful info.

[Jhonny Oliveira (jhonny-oliveira)]

Same issue here with HD7850. Post #48 did not help, some modules still fail to compile at install stage... I will have a look at post #67 in the meanwhile.

[Hemal (rathod-hemal)]

@Jhonny

Don't compile
Just download ready made .deb files

[Tarmo Sergo (v-launchpad-d)]

HP DM-1 laptop with AMD E-350 APU is affected too.
fglrx or fglrx-updates does not work, hangs at spash screen as others have reported.
Without fglrx there are very much graphics glitches. I would say it is unusable.

I have not yet tried patches/debs posted here but I will give them a try.

Just a note to others. You do not need to reinstall to fix. At GRUB screen just select edit and add "single" to the end of kernel line. You will then boot to single user console mode and can uninstall/purge fglrx packages.

[Hemal (rathod-hemal)]

Great
Patch work is going on

[coldrain (raphaelsouza)]

The patch works on XFX R9 270?
Anyone?

Thanks.

[sheepky (sheepky)]

I also see this problem on

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff)

It's installed on Dell Latitude E6540

[Alberto Milone (albertomilone)]

I have just uploaded the workaround in Xenial (16.04). If you see the main task marked as fix released, that refers to 16.04. An SRU for 15.10 will follow.

Note: the packages for 16.04 will also work on 15.10, if you can't wait for the official update.

[Mikael Thurberg (mthurberg)]

I think this problem maybe is related when I had the fglrx installed on 15.04 and updated to 15.10 and it didnt work booting it correctly afterwards?

[Paolo Rotolo (paolorotolo)]

Thanks Alberto!
Last package for Xenial is still 2:15.201-0ubuntu1. Waiting for the update :)

[Jhonny Oliveira (jhonny-oliveira)]

@Hemal

I did try both ways!

[Hemal (rathod-hemal)]

@Jhonny
Then wait for patch release as said by Alberto

[Hemal (rathod-hemal)]

New packages now available on 16.04 channel

[Launchpad Janitor (janitor)]

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

---------------
fglrx-installer (2:15.201-0ubuntu2) xenial; 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> Mon, 26 Oct 2015 16:42:55 +0100

[Jhonny Oliveira (jhonny-oliveira)]

OK, it is working now. I previously forgot to manually install the gcc4.9 dependencies.

Just to summarize in case someone went through the same struggle:

1 - Installed Ubuntu 15.10
  -> Instead of being prompted for my disk encryption password I get a black screen! The screen actually goes of! This is related to my "AMD Radeon HD 7850"...
      -> Luckily it is possible to enter the password in the "dark" - Workaround: add "GRUB_GFXPAYLOAD_LINUX=auto" to grub.
2 - Obviously, if you buy this graphic card you kind of plan to use it, so I installed fglrx (updates and no updates)
  -> system no longer boots, and it is not possible to enter the disk encryption at all.
      -> To address the disk encryption issue had to remove "splash" from grub configuration, leaving it like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet", the previous (1) grub hack no longer works can be removed...
      -> the driver itself does no work, had to remove it after booting in single mode.
3. Installed the packages proposed on the previous post (updates)
      -> Together with the previous (2) grub hack everything is working again. I mean, not as good looking as it should but, it is working.

This was the reason I left Fedora 4/5 years ago!!!

[Jhonny Oliveira (jhonny-oliveira)]

Still, I will financially contribute the next Ubuntu release :-)!

[Đorđe (djole94hns)]

@Jhonny Oliveira
I guess you need a healthy dose of masochism to use any distribution of Linux. It's getting better with time though :)

[Luca Weiss (z3ntu)]

Great, that it is fixed!

[dolphy (dolphy-6)]

Comment #48 describes how to patch and rebuild the package manually. Can someone describe the steps to pull in the official package from 16.04 into a 15.10 installation?

[Jhonny Oliveira (jhonny-oliveira)]

One way to do it:

sudo apt-get install lib32gcc1 libc6-i386 gcc-4.9 gcc-4.9 gcc-4.9-base libasan1 libcloog-isl4 libgcc-4.9-dev

Then download:
https://launchpad.net/ubuntu/+archive/primary/+files/fglrx-updates_15.201-0ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+archive/primary/+files/fglrx-updates-core_15.201-0ubuntu2_amd64.deb
https://launchpad.net/ubuntu/+archive/primary/+files/fglrx-amdcccle-updates_15.201-0ubuntu2_amd64.deb

Then:

dpkg -i *.deb

[Đorđe (djole94hns)]

@Jhonny Oliveira

I've got some errors:

(Reading database ... 269976 files and directories currently installed.)
Preparing to unpack fglrx-amdcccle-updates_15.201-0ubuntu2_amd64.deb ...
Unpacking fglrx-amdcccle-updates (2:15.201-0ubuntu2) over (2:15.201-0ubuntu2) ...
Preparing to unpack fglrx-updates_15.201-0ubuntu2_amd64.deb ...
Unpacking fglrx-updates (2:15.201-0ubuntu2) over (2:15.201-0ubuntu2) ...
Preparing to unpack fglrx-updates-core_15.201-0ubuntu2_amd64.deb ...
Unpacking fglrx-updates-core (2:15.201-0ubuntu2) over (2:15.201-0ubuntu2) ...
dpkg: dependency problems prevent configuration of fglrx-updates-core:
 fglrx-updates-core depends on dkms; however:
  Package dkms is not installed.

dpkg: error processing package fglrx-updates-core (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of fglrx-updates:
 fglrx-updates depends on fglrx-updates-core; however:
  Package fglrx-updates-core is not configured yet.

dpkg: error processing package fglrx-updates (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of fglrx-amdcccle-updates:
 fglrx-amdcccle-updates depends on fglrx-updates; however:
  Package fglrx-updates is not configured yet.

dpkg: error processing package fglrx-amdcccle-updates (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.58ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (225-1ubuntu9) ...
Errors were encountered while processing:
 fglrx-updates-core
 fglrx-updates
 fglrx-amdcccle-updates

Should I ignore them?

[Đorđe (djole94hns)]

My attention span is minimal... All I had to do is install dkms.
Anyway, the driver works. Thanks!

[Luca Weiss (z3ntu)]

@Jhonny Oliveira works on HD7970! Thanks!

[Jason Smith (crestus)]

@Jhonny Oliveira

This works on Radeon HD 6620G. Thanks everyone for the hard work on this...I was holding off my upgrade to 15.10 for this as I need proprietary drivers for some stuff on wine, this works like a charm now!

[Mikael Thurberg (mthurberg)]

@Alberto Milone

Sorry to say but I cant get it to run properly.. Here is some additional info:

What I did is that I tried to run the commands in the terminal described in post #48.. could not execute all the commands, got stuck halfway somewhere.. so I downloaded the .deb files from the same post and installed them all..

Then it worked with fglrx!

BUT

Then software updater told me there was a update to the amd minimal core driver and amd driver something? (sorry dont remember what appeared, but it was 2 packages it wanted to update)..

After I installed that updates from the automatic software updater.. all I got after restart was a black screen :(

So I "sudo apt-get purge fglrx*" manually and after that was back to the desktop again with the regular drivers..

Then I tried install the fglrx-updates via system settings -> program and updates -> additional drivers..

That does not work.. only boots to a black screen for me..

I have amd hd 6450 card so I think it should be supported actually..

It did get to work with the .deb files in comment #48, but not when I do the install via system settings of fglrx-updates..

The drivers / amd update getting pushed out from automatic software updater did not work for me, maybe for some other also?

Just wanted to inform you.. Thanks for all your work everyone who contributed to this!
Have a great day! /Micke

[Joe Thorpe (thorpejoe4)]

@Mikael Thurburg

I believe that you have to prevent fglrx-updates from updating (along with fglrx-updates-amdcccle and fglrx-updates-core) for the immediate future, at least until the official fix is released for wily.

For me the best solution was #88 (make sure dkms is installed)

[Alberto Milone (albertomilone)]

@SRU team: please accept fglrx-installer_15.201-0ubuntu1~15.10.1 and fglrx-installer-updates_15.201-0ubuntu1~15.10.1 in wily-proposed.

@all: please wait for the update. We are going to need testers.

[Luca Finzi Contini (lucafinzicontini-8)]

I colud test it. My system is a AMD A10 6800K.
Il 27/Ott/2015 11:01, "Alberto Milone" <email address hidden> ha
scritto:

> @SRU team: please accept fglrx-installer_15.201-0ubuntu1~15.10.1 and
> fglrx-installer-updates_15.201-0ubuntu1~15.10.1 in wily-proposed.
>
> @all: please wait for the update. We are going to need testers.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1493888
>
> Title:
> FGLRX incompatible with gcc 5
>
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in fglrx-installer package in Ubuntu:
> Fix Released
> Status in fglrx-installer source package in Wily:
> In Progress
>
> Bug description:
> SRU Request:
>
> [Impact]
>
> The fglrx driver is not compatible with gcc 5.x. This causes the
> kernel module to crash on initialisation. As a result, users will boot
> into a black screen, as X will fail (except on Intel+AMD hybrid
> systems, where intel is used).
>
> [Test Case]
> 1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
> 2. Reboot
> 3. Check the display, and the output of the "dmesg | grep fglrx" command
> (to see the actual crash)
>
> Expected results: the system should be able to start X correctly.
>
> Actual results:
> The kernel module fails and X doesn't start.
>
> [Regression Potential]
> Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and
> will be replaced with the proper fix once AMD makes it available.
>
>
>
> __________________________________________________________________________
>
> With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
> able to SSH into the machine. I booted the older kernel
> (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
> using xserver-xorg-video-radeon I am able to get the graphics working,
> but even it has issues with my display port (The DVI ports are working
> correctly).
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.10
> Package: fglrx (not installed)
> ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
> Uname: Linux 4.2.0-7-generic x86_64
> ApportVersion: 2.18-0ubuntu9
> Architecture: amd64
> Date: Wed Sep 9 09:29:54 2015
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2011-01-07 (1705 days ago)
> InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> ProcEnviron:
> LANGUAGE=
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: fglrx-installer
> UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions
>

[Alberto Milone (albertomilone)]

Sorry, the actual versions are fglrx-installer_15.201-0ubuntu2~15.10.1 and fglrx-installer-updates_15.201-0ubuntu2~15.10.1

[Timo Aaltonen (tjaalton)]

Hello Allen, 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.1 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!

[Timo Aaltonen (tjaalton)]

Hello Allen, 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.1 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!

[Luca Weiss (z3ntu)]

@Timo Aaltonen, #88 works for me on HD7970. I think these are the same packages?

[Alberto Milone (albertomilone)]

On 27-10-15 10:42:01, Luca Weiss wrote:
> @Timo Aaltonen, #88 works for me on HD7970. I think these are the same
> packages?
>

Yes, they are the same packages (only with a slightly different
revision) but we need users to test the packages in wily-proposed (it's
the standard procedure)

[Luciano (jluciano)]

Not working - Ubuntu Mate 15.10
Hangs on
Oct 27 12:05:31 uby systemd[1]: Started Braille Device Support.

Oct 27 12:05:31 uby kernel: [ 18.417435] RIP [<ffffffffc1a38251>] firegl_trace+0x61/0x1e0 [fglrx]
Oct 27 12:05:31 uby kernel: [ 18.417508] RSP <ffff880220807a78>
Oct 27 12:05:31 uby kernel: [ 18.417542] ---[ end trace 68ad27100923cb3b ]---

CPU: Quad core AMD FX-7500 Radeon R7 10 Compute Cores 4C+6G (-MCP-) cache: 8192 KB
           clock speeds: max: 2100 MHz 1: 1100 MHz 2: 1300 MHz 3: 1300 MHz 4: 1300 MHz
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R6/R7 Graphics]
           Card-2: Advanced Micro Devices [AMD/ATI] Opal XT [Radeon R7 M265]

[Luciano (jluciano)]

Forgot to mention
Package tested fglrx-updates - 2:15.201-0ubuntu2~15.10.1

[Hemal (rathod-hemal)]

TESTED
fglrx-updates - 2:15.201-0ubuntu2~15.10.1

on my Ubuntu 15.10 with AMD HIS HD7770 and working fine with dual monitors.

[Paul FitzPatrick (2-launchpad-pfitz-fitzpatrick-cc)]

Tested and works for me now

ii fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.1 amd64 Catalyst Control Center for the AMD graphics accelerators
ii fglrx-updates 2:15.201-0ubuntu2~15.10.1 amd64 Video driver for the AMD graphics accelerators
ii fglrx-updates-core 2:15.201-0ubuntu2~15.10.1 amd64 Minimal video driver for the AMD graphics accelerators

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]

[Alberto Milone (albertomilone)]

@Luciano: can you reproduce the problem and attach the following files please?

1) the dmesg ouput
2) /var/log/gpu-manager.log
3) /var/log/Xorg.0.log

[mark (markrmiller)]

Worked for me from -proposed: 2:15.201-0ubuntu2~15.10.1

[Vertago1 (vertago1)]

I have tested the packages from both 16.04 and 15.04-proposed and they work on my system.

[Paolo Rotolo (paolorotolo)]

Works fine for me: Ubuntu 15.10 with AMD 7790.

[dolphy (dolphy-6)]

This worked for me from -proposed: 2:15.201-0ubuntu2~15.10.1

I am now able to install and activate the fglrx graphics drivers.

A new problem is that my multimonitor setup was working fine without the fglrx drivers, but now has been broken:
    Monitor 1 (connected to AMD card)
    Monitor 2 (connected to AMD card)
    Monitor 3 (connected to integrated intel controller)

Only the two monitors connected to the AMD discrete graphics card will work with fglrx installed. The monitor connected to the integrated intel graphics controller is not detected. Looking around, this seems to be a separate and unrelated problem to the fglrx issues this bug is written against.

[Paolo Rotolo (paolorotolo)]

UPDATE: I'm noticing some graphic artifacts using GNOME-Shell 3.16.
They occur only in Overview mode.

[Aivar Lindebaum (lime-l)]

This worked for me too - 2:15.201-0ubuntu2~15.10.1 and fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.1
Videocard - FirePro M5950

[Jan Zörner (jan-zoerner)]

Works also for me with

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM]

fglrx-updates 2:15.201-0ubuntu2~15.10.1
fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.1
fglrx-updates-core 2:15.201-0ubuntu2~15.10.1

Xorg log file: http://paste.ubuntu.com/12980984/

[Roger Barrett (roger-m-d-barrett)]

It both works and doesn't work for me.

The kernel module is fine, the X Server loads and seems to open the device correctly, but the screens stay blank, then turn off.
The attached tar file has dmesg output and the Xorg and gpu-manager log files. The only thing I can see is the gpu-manager log complains that /dev/dri is absent.

I can force the screens to stay on ( but still blank ) by running amdconfig --initilal. The main change then is that ukiOpenDevice returns 9 rather than 11 ( can't find any documentation for this function - assume it is proprietary ).

To add more strangeness, if I boot into recovery mode, and run 'startx' as the root user, I get an empty X desktop on display :1 that appears to be the Unity desktop without any menus/launchers, and no window manager. But I can run an X terminal and run gedit, eclipse, and firefox, from which I am writing this comment. However, the VTs that should be provided by fglrx do not work.

This is with a new 15.10 installation ( keeping personal files ), not an upgrade, using an R9 290. It clearly works as an X server, but configuration or permissions in the installation must be askew.

[Flavio Elawi (flavioelawi)]

TESTED on R9 285 and it works.
i had to manually do #1510573 to blacklist amdgpu and add the nomodeset flag for the kernel.

[Đorđe (djole94hns)]

The guide from comment #88 using Xenial packages worked for me (I'd add that dkms needs to be installed too), but when I restored a backup to before I installed those packages and tried installing the ones from wily-proposed trough terminal (with apt-get (package)/wily-proposed instead of downloading the packages manually and using dpkg -i) it didn't work. I might not used the process correctly, so I'll repeat the process again.

[Tom De Caluwé (tom-de-caluwe)]

Tested on a dual monitor setup with an AMD APU onboard and HD5450 card, but the splash screen hangs before I get to my desktop... I attached a trace I found in the syslog, which seems to be related.

[Đorđe (djole94hns)]

Update: FGLRX works from wily-proposed packages. I forgot to add /wily-proposed to all three packages when installing (fglrx-updates, fglrx-updates-core and fglrx-amdcccle-upgrades)

[Alberto Milone (albertomilone)]

On 27-10-15 18:11:26, Flavio Elawi wrote:
> TESTED on R9 285 and it works.
> i had to manually do #1510573 to blacklist amdgpu and add the nomodeset flag for the kernel.
>

Good point. That would be LP: #1510573

It should be fixed in Xenial (fglrx 2:15.201-0ubuntu3). I am working to
SRU that change too.

[Alberto Milone (albertomilone)]

On 27-10-15 17:47:55, Roger Barrett wrote:
> It both works and doesn't work for me.
>
> The kernel module is fine, the X Server loads and seems to open the device correctly, but the screens stay blank, then turn off.
> The attached tar file has dmesg output and the Xorg and gpu-manager log files. The only thing I can see is the gpu-manager log complains that /dev/dri is absent.
>

That is LP: #1510573

[Jhonny Oliveira (jhonny-oliveira)]

Version 15.201-0ubuntu3 also works fine.

Just a pity that in order to be able to enter my disk encryption I had to remove "splash" from grub, no other work around seems to deal with it. Same behaviour with the previous working version. :-(

[Mikael Thurberg (mthurberg)]

@Joe Thorpe

Thanks for the info!

@Alberto Milone & @Timo Aaltonen

I can help test the proposed package.. I have an older computer so that might be great for checking compatibility..

Sorry for asking about how to do it (im a bit new at using ubuntu)..

Is the only thing I need to do to test this is to in "software & updates" to just tick the box with the "proposed", then save, update / install and reboot?

Or is there any more commands I need to input via terminal you want me to check / do?

Right now my system is in the state it got when I did the "sudo apt-get purge fglrx*", have nothing more changed at the moment.

I would be happy to help see if it works if someone could provide info on the above questions.. Thanks

[Đorđe (djole94hns)]

@Mikael Thurberg

-In Software & Updates, tick "proposed"
-Create the file /etc/apt/preferences.d/proposed-updates with this content:

Package: *
Pin: release a=wily-proposed
Pin-Priority: 400

Just so you don't install proposed updates automatically, but selectively (so you can choose which to install)

-sudo apt-get update
-sudo apt-get install fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed
-reboot and you're done!

[Sergey Kislyakov (defman21)]

fglrx-updates:
  Installed: 2:15.201-0ubuntu2~15.10.1
  Candidate: 2:15.201-0ubuntu2~15.10.1
  Version table:
 *** 2:15.201-0ubuntu2~15.10.1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ wily-proposed/restricted amd64 Packages
The drivers works fine for me though. (PowerColor R9 280X) I just enabled wily-proposed in Software & Upgrades, then did `apt-get update` and then `apt-get dist-upgrade` (but before doing it I did `apt-cache policy fglrx-updates` to make sure there's a new version of the package and it's "2:15.201-0ubuntu2~15.10.1" and not something else).

[Mikael Thurberg (mthurberg)]

@Đorđe

Thanks, I will try that out!!

[Roger Barrett (roger-m-d-barrett)]

>>On 27-10-15 17:47:55, Roger Barrett wrote:
>> It both works and doesn't work for me.
>>
>> The kernel module is fine, the X Server loads and seems to open the device correctly, but the screens stay blank, then turn off.
>> The attached tar file has dmesg output and the Xorg and gpu-manager log files. The only thing I can see is the gpu-manager log complains that /dev/dri is absent.

>That is LP: #1510573

Yes, it is. Thanks.

So, other than blacklisting amdgpu, it worked as intended from wily-proposed.

[QIII (qiii)]

Before enabling -proposed, it might be worthwhile to review the documentation at https://wiki.ubuntu.com/Testing/EnableProposed.

[Đorđe (djole94hns)]

@Mikael Thurberg
No problem, man. Also, Just to add, if you encounter some dependency errors, install these:

sudo apt-get install lib32gcc1 libc6-i386 gcc-4.9 gcc-4.9 gcc-4.9-base libasan1 libcloog-isl4 libgcc-4.9-dev

sudo apt-get install dkms

[Luca Finzi Contini (lucafinzicontini-8)]

TEST OK on AMD A10-6800K.
I followed the steps in message #132 and IT WORKS on my system.
The system booted correctly into UNity and I have successfully opened AMD Catalyst Control Center.

My question is: shall I delete the /etc/apt/preferences.d/proposed-updates file or is it better to leave it in place until the fixed packages are delivered in the main 'channel'?
Thank you in advance to all the people who spent effort on this problem.

[Đorđe (djole94hns)]

 @Luca Finzi Contini
Delete the /etc/apt/preferences.d/proposed-updates file only AFTER you untick "proposed" updates from Software & Updates.

[Mikael Thurberg (mthurberg)]

@Đorđe

No dependency errors encountered (for me), was not necessary to install that.

----

Installed fglrx from the proposed-updates, so far everything seems to work fine here!

I post if I encounter any problem here..

Thanks everyone who have helped and contributed and worked with this!

[Cameron Stutsman (cameron-stutsman)]

Test and running.
Processor: AMD A8-5600K APU with Radeon(tm) HD Graphics × 4
Graphics: AMD Radeon HD 7560D

Thank you

[Adrian (adrianf0)]

Worked for me from -proposed: 2:15.201-0ubuntu2~15.10.1

Multi screen configuration -> Display Port MST works properly.

[David Rodríguez (david-1992-7)]

Works perfectly.

Graphics: AMD Radeon R7 270X

Thanks to everyone that made this ^^

[Paolo (vihochiamatiamici)]

It WORKS on a Lenovo z50 whit AMD R7-M260DX graphic card.
I installed:

"2:15.201-0ubuntu2~15.10.1" (Ubuntu:15.10/wily-proposed [amd64]) selezionata per "fglrx-updates"
"2:15.201-0ubuntu2~15.10.1" (Ubuntu:15.10/wily-proposed [amd64]) selezionata per "fglrx-updates-core"
"2:15.201-0ubuntu2~15.10.1" (Ubuntu:15.10/wily-proposed [amd64]) selezionata per "fglrx-amdcccle-updates"

from proposed repository.
But I had to blacklist amdgpu module in order to get this driver working. Should I report this behaviour on #1510573 ?
Thanks for your work.

[Zeioth (zeioth)]

Installed from proposed repository and all working with HD 5770.

[Timo Aaltonen (tjaalton)]

Hello Allen, 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!

[Timo Aaltonen (tjaalton)]

Hello Allen, 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!

[Allen Webb (vertago1-s)]

I ended up with two ubuntu one accounts for some reason, so I tested it in #108. Both the 16.04 packages and the packages in wily-proposed have fixed the problem for me. Versions:
ii fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.1 amd64 Catalyst Control Center for the AMD graphics accelerators
ii fglrx-updates 2:15.201-0ubuntu2~15.10.1 amd64 Video driver for the AMD graphics accelerators
ii fglrx-updates-core 2:15.201-0ubuntu2~15.10.1 amd64 Minimal video driver for the AMD graphics accelerators
ii fglrx-updates-dev 2:15.201-0ubuntu2~15.10.1 amd64 Video driver for the AMD graphics accelerators (devel files)

[tomjo78 (tommi-johnsson)]

Fglrx 2:15.201-0ubuntu2 from proposed repository works fine.

[Hamza (ckr-hamza)]

Using proposed update: works fine EXCEPT Entering to tty(Ctrl + Alt + F1, F2,..) shows a blank screen.

[Vertago1 (vertago1)]

Hamza, the tty problem is a different bug: see https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1162024

[coollmax (ice-max-007)]

Hi all. My card is Ati Radeon hd5650. And I have black screen. With old drivers. And catalyst not running.
I won't help.
First I need install priopritarian drivers from Ubuntu updates? And after switch updates???

[Michele Olivo (micheleolivo)]

fglrx-updates from the proposed repository works for me on AMD Radeon R9 270 (curacao pro) on an AMD A8-6600k system.

Installed enabling the proposed repository and using the "Repository and drivers" tool.

[coollmax (ice-max-007)]

Not workedddddddd. Still on INTEL card. I try do this sudo amdconfig --initial -f reboot
But still work Intel. And catalyst center not open
My hp pavilion dv6 hd5660

Help please. How correct change card???

[coollmax (ice-max-007)]

Have this:

00:02.0 VGA compatible controller: Intel corporation core processor integrated graphics controller rev 02

01:00.0 VGA compatible controller: advanced micro devices inc amd/ati Madison [mobility Radeon had 5660/5750 / 6530m/6550m

[coollmax (ice-max-007)]

And have error when I try open catalyst center:

Problems arise when the Linux version initialize catalyst control center it may be caused by the following reasons. And...............

[Luca Finzi Contini (lucafinzicontini-8)]

I just tested the driver playing PORTALS 2 with STEAM on this linux box and it played perfectly.
I also tried going to the tty with CTRL+F1 and then back to the X session with CTRL+F7 - all smooth and OK.
Thank you.

[Paolo (vihochiamatiamici)]

Hi to all,
tested new 15.201-0ubuntu2~15.10.2 version, from proposed updates, on R7-M260DX graphic card. It works fine.

[Hamza (ckr-hamza)]

Can't log out with wily-proposed update. The update may have a problem with gdm(I am using Ubuntu GNOME 15.10). Fedora 22 had the same problem with gdm but then they solved it by applying a different patch or disabling SELinux.

This can help: https://bluehatrecord.wordpress.com/2015/09/17/installing-the-proprietary-amd-catalyst-15-9-fglrx-15-201-driver-on-fedora-22-with-linux-kernel-4-1-6/

[Robert Hutton (rwh-helms-deep)]

The version in wily-proposed works successfully on a Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280].

fglrx-updates 2:15.201-0ubuntu2~15.10.2
fglrx-updates-core 2:15.201-0ubuntu2~15.10.2
fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.2

[Luciano (jluciano)]

@Alberto Milone (albertomilone)
@Luciano: can you reproduce the problem and attach the following files please?
Ill do it this weekend i have no time to spare atm.

Files are from 15.10 installation, note i am not able to log in into 15.10 any more the system enters in an inifinite loop, i mounted the partition and grabbed the logs files from last boot,
I will reinstall the system this weekend and perform another test.

dmesg.log
(Nothing has been logged yet.)

gpu-manager.log
http://pastebin.com/xxqVY0Sj

Xorg.0.log
http://pastebin.com/fBKWfh5F

[Alberto Milone (albertomilone)]

@Luciano: it seems to me that you have a dual AMD system. I don't see any signs of the problem mentioned in this bug report. Maybe it's a different problem.

[xpris (xpris)]

I have question. If I install this fglrx from Wily proposed repo, I can install also without patching new kernel like 4.3 or I need make some patch?

[Alberto Milone (albertomilone)]

On 29-10-15 17:00:28, xpris wrote:
> I have question. If I install this fglrx from Wily proposed repo, I can
> install also without patching new kernel like 4.3 or I need make some
> patch?
>

I haven't looked into adding support for Linux 4.3 to the driver, so the
package might fail to build (I haven't tested that yet).

[Luciano (jluciano)]

@Alberto Milone: is driver related, ill be back by sunday, cheers.

[Paulo Canedo (paulocanedo)]

worked fine for me

[Freihut (freihut)]

Works on AMD HD 7850:

fglrx 2:15.201-0ubuntu2~15.10.2
fglrx-core 2:15.201-0ubuntu2~15.10.2

[Jan Zörner (jan-zoerner)]

Current version on >>wily-proposed<< works for me too (with Radeon R9 270X).

However, there are some graphics/font glitches in basically every GNOME shell menu (see attachment) which shouldn't be related to the bug of this thread, but to the fglrx driver in general.

[Iuri Diniz (iuridiniz)]

Fix released with 2:15.201-0ubuntu2~15.10.2 doesn't work for me on kernel 4.2.0-17-generic, my card is Radeon R7 M260/M265. Kernel 4.1.6-040106-generic works fine.

----------------
iuri@ubuntu-Inspiron-5447:~$ dpkg -l | grep fglrx
ii fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.2 amd64 Catalyst Control Center for the AMD graphics accelerators
ii fglrx-updates 2:15.201-0ubuntu2~15.10.2 amd64 Video driver for the AMD graphics accelerators
ii fglrx-updates-core 2:15.201-0ubuntu2~15.10.2 amd64 Minimal video driver for the AMD graphics accelerators
iuri@ubuntu-Inspiron-5447:~$ lspci | grep -i amd
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (rev ff)
iuri@ubuntu-Inspiron-5447:~$ strings /lib/modules/4.2.0-17-generic/updates/dkms/fglrx_updates.ko | grep -i GCC
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3
GCC: (Ubuntu 4.9.3-5ubuntu1) 4.9.3

[Luciano (jluciano)]

@Iuri Diniz,do you have a dual graphics ??
FX-7500 AMD APU + R7
i have the same card with the specs above and the same issue.

[QIII (qiii)]

-proposed works like a champ on my R9 290X

[Aizuddin Zali (aizuddin-linux)]

I have some taint error while using fglrx-update from wily-proposed. Nevertheless, i can boot with the proposed driver. modinfo fglrx also shown nothing, maybe due to signature issue.

mymzbe@mylenovo:~$ dmesg |grep fglrx
[ 3.059130] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[ 3.108633] fglrx: module verification failed: signature and/or required key missing - tainting kernel
[ 3.180146] <6>[fglrx] Maximum main memory to use for locked dma buffers: 4615 MBytes.
[ 3.180164] <6>[fglrx] vendor: 1002 device: 9851 revision: 0 count: 1
[ 3.180556] <6>[fglrx] ioport: bar 4, base 0x3000, size: 0x100
[ 3.181122] <6>[fglrx] Kernel PAT support is enabled
[ 3.181151] <6>[fglrx] module loaded - fglrx 15.20.3 [Sep 8 2015] with 1 minors
[ 5.221140] <6>[fglrx] Firegl kernel thread PID: 922
[ 5.221267] <6>[fglrx] Firegl kernel thread PID: 923
[ 5.221369] <6>[fglrx] Firegl kernel thread PID: 924
[ 5.221520] <6>[fglrx] IRQ 43 Enabled
[ 5.229795] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000
[ 5.229803] <6>[fglrx] Reserved FB block: Unshared offset:fab4000, size:4000
[ 5.229806] <6>[fglrx] Reserved FB block: Unshared offset:fab8000, size:548000
[ 5.229808] <6>[fglrx] Reserved FB block: Unshared offset:3ffdd000, size:23000
[ 5.273775] <6>[fglrx] ATIF platform detected with notification ID: 0x81

[Cristina Franzolini (forkirara)]

Work for me.
fglrx-updates 2:15.201-0ubuntu2~15.10.2
fglrx-updates-core 2:15.201-0ubuntu2~15.10.2
fglrx-amdcccle-updates 2:15.201-0ubuntu2~15.10.2

AMD R9 270, Kernel 4.2.0-17-generic, gcc-5.2.1-3ubuntu1, dual monitor, gnome-session-flashback

Only amdcccle (admin) don't save new configuration about monitor position (if I restart, the monitor position go back).

[xpris (xpris)]

Works fine for me.

Mobile Radeon HD5650M.

[QIII (qiii)]

For those with dual graphics: Although it is not supposed to be required any longer, I answer this question often enough on the Ubuntu Forums that I recommend the following:

If you have fglrx installed and end up with a blank/black screen, go into recovery mode, mount your filesystem read/write. Issue the following command:

amdconfig --adapter=all --initial

and reboot.

If you have uninstalled it, reinstall it. Before rebooting, issue the amdconfig command.

[Matthäus G. Chajdas (anteru)]

Proposed also works fine for me, dual-monitor, Fury X.

[Luciano (jluciano)]

Just to say, reformated reinstalled and its working fine with dual graphics, thanks :)

[Florian Sievers (florian-sievers)]

15.201-0ubuntu2~15.10.2 doesn't work for me. I have a Radeon HD5770 and I still get a black screen and a constantly louder GPU Fan when booting with FGLRX. Also did a amdconfig --initial like I did in the past with many Ubuntu versions. But this time it won't help. Came to Wily from Vivid.

When booting with propertery driver and getting the blank screen, the system seems to be deadlocked. MagicSysRq (RAISUB) won't work and I had to push the hardware reset button.

Using Kernel 4.2.0-17-generic

[Jarl (jarl-dk)]

Tested with fglrx-updates version 2:15.201-0ubuntu2~15.10.2 from -proposed and it works.

[Michel Blanchet (mblanchet)]

Tested and working fine with Ubuntu Gnome 15.10, 4.2.0-16-generic and Radeon 6950 HD

[InQuieto (l-inquieto)]

Tested the proposed driver, working fine for me. Ubuntu 15.10, Unity, Radeon HD 7800

[carlos (nitrosito)]

Tested and NOT WORK for me. fglrx-updates Version: 2:15.201-0ubuntu1
Black screen (Kubuntu logo) freeze on startup.
AMD 6970 2GB Lighthing

Any fix?

[Vertago1 (vertago1)]

@carlos

Install fglrx-updates from the wily-proposed repositories. It has a fix. I am not sure why it hasn't be released from proposed yet. It should be version 2:15.201-0ubuntu2~15.10.1

[carlos (nitrosito)]

I've installed from the repositories of Kubuntu 15.10 no work.
And the fix #166 not work :(

[QIII (qiii)]

Did you follow the instructions at https://wiki.ubuntu.com/Testing/EnableProposed for enabling selective installation and then install all packages explicitly from there?

That is: fglrx-updates/wily-proposed, fglrx-amdcccle-updates/wily-proposed, fglrx-core-updates/wily-proposed?

[carlos (nitrosito)]

@Qlll

I have not used Proposed (now I try)

But is it safe to use Proposed? Much software will be updated very beta versions.

Thanks

[carlos (nitrosito)]

fglrx-updates version 2:15.201-0ubuntu2~15.10.1 not worked for me T_T

Kubuntu 15.10 , AMD 6970 2GB Lightning

[Vertago1 (vertago1)]

@Carlos

The safest thing to do would be to enable proposed just long enough to install the updated packages, then disable the proposed repo. Don't install other packages from proposed if you are worried about them breaking things.

[QIII (qiii)]

Ease follow the instructions in the link I provided to enable selective installation and install the packages explicitly from wily-proposed as I suggested. If you set selective installation, you will update only those packages.

[QIII (qiii)]

Please follow ...

[Vertago1 (vertago1)]

@Carlos

Some people had to blacklist the amdgpu kernel module to get it to work, see: #115

[carlos (nitrosito)]

Thanks Qlll , i finally fixed :

Adding wily-proposed as you suggested and install:

Thanks Qlll , i finally fixed :

Adding wily-proposed as you suggested

And install:

   fglrx-updates/wily-proposed fglrx-amdcccle-updates/wily-proposed fglrx-updates-core/wily-proposed

later remove wily-proposed

Thanks!

[Stephen Ranger (sanosuke001)]

wily-proposed boots fine but the following errors are in the xorg log

[ 48.168] (EE) open /dev/dri/card0: No such file or directory
[ 48.602] (EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[ 48.602] (EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[ 48.602] (EE) AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]

 (attached full log)

glxgears works, but there's still these errors which seem important. I've only noticed with Java/JOGL application so far but it did not happen in 15.04 with the 2:15.200-0ubuntu4.2 driver.

[Vertago1 (vertago1)]

@Stephen Ranger

Do you have gcc-4.9 and dkms installed?

[Stephen Ranger (sanosuke001)]

Yes, both are installed. Looking at the segmentation fault hotspot log from my java application, it says libwayland and mesa-egl are being loaded. I don't have gnome-session-wayland even installed and mesa shouldn't be loaded if fglrx is being used. I've attached the java log as well.

[belgianguy (wietse-jorissen)]

After applying updates from the wily-proposed repo, I can now boot into 15.10, kernel 4.2-17 with fglrx-updates.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870]

[Adrian Tritschler (ajft)]

Installing from wily-updates as per https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/comments/183 has my i7 / 4.2.0-17 / 5430 system working again. One pleasant surprise is that for the first time ever I can now drive my card/monitor at 1920x1080 whereas under previous fglrx versions it maxed out at 1776x1000.

[Tomáš Kalvoda (t-kalvoda)]

Fix applied using https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/comments/183 does not work for me. Before I got stuck with kubuntu logo, now I'm stuck with a black screen. Please, continue trying to fix it.
Using R9 280X GPU.

[Tomáš Kalvoda (t-kalvoda)]

Correction: black screen, unless I plug something in (USB drive to reinstall system :) ) then it shows [11.077735] usb 1-9: device description rad/all, error -110

[Eduard Santamaria (eduardsan)]

Driver from proposed working fine for me on a netbook with Intel and AMD Radeon 6600M gpus.

[David B Yentzen (dbyentzen)]

Thanks to all who reported, worked on, and fixed this bug! I've been waiting on this fix release and using the open source driver for my AMD/ATI:Carrizo. Without enabling 'Wily proposed', I've notice the video driver for the AMD graphics from fglrx-updates(proprietary) has moved up in the additional drivers GUI since the fix was released. Does this mean I can now try to use fglrx-updates in place of the open source without enabling 'Wily proposed'?
Using: AMD A10-8700P Radeon R6

[Mathew Hodson (mhodson)]

The fixed packages are still in the wily-proposed archive and have not been released yet. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

[LambdaFox (lambdafox)]

If you do not want to enable proposed, but do want fglrx, see here how I did it.

http://ubuntuforums.org/showthread.php?t=2299981&p=13383588#post13383588

[Paolo (vihochiamatiamici)]

Hi to all, I changed my distro from Ubuntu to Ubuntu Gnome cause I don't feel confortable with unity desktop. I've done exactly as I did on #135 but this time I'm not able to get the driver working. Am I missing some steps?

[Philip Gemmell (philip-gemmell-r)]

After my update, I had my computer freezing after starting lightdm. Going through recovery, I purged lightdm and xorg, so I could at least get to work with a tty terminal.

After having followed the instructions on adding wily-proposed to my repository list (using only command line arguments and nano for editing), I attempted to install using the command:
sudo apt-get install fglrx/wily-proposed fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed

However, installation could not be completed, as it complained about conflicts with fglrx-driver and xorg-driver-binary. Attempting to remove these packages, I am told that 'Virtual packages like xxx can't be removed'. Can anyone help me on where I've gone wrong?

[Alberto Milone (albertomilone)]

On 11-11-15 13:58:08, Philip Gemmell wrote:
> After my update, I had my computer freezing after starting lightdm.
> Going through recovery, I purged lightdm and xorg, so I could at least
> get to work with a tty terminal.
>
> After having followed the instructions on adding wily-proposed to my repository list (using only command line arguments and nano for editing), I attempted to install using the command:
> sudo apt-get install fglrx/wily-proposed fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed
>
> However, installation could not be completed, as it complained about
> conflicts with fglrx-driver and xorg-driver-binary. Attempting to remove
> these packages, I am told that 'Virtual packages like xxx can't be
> removed'. Can anyone help me on where I've gone wrong?

You should try installing either fglrx or fglrx-updates. You can't have
both at the same time.

[Philip Gemmell (philip-gemmell-r)]

Thanks, that fixed that problem - I installed fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed without any further problems, and also reinstalled lightdm, xorg and ubuntu-desktop. Unfortunately, this is leading to a blank screen on start-up - I can return to tty if I drop into recovery, then into root to purge the packages again before restarting.

I've got a Radeon R9 285 graphics card - are there any other potential fixes I could try to apply, or should I roll back to a 3.x kernel?

Thanks for the help thus far - I'm glad to know this is being looked at!

[Roger Barrett (roger-m-d-barrett)]

@Philip Gemmell

Not sure if the open source driver blacklist has made it into the fix yet - this caused my screen to be blank after updating.

See previous comments #114 #119 and #120.

I didn't need to change nomodeset, but I did need to add "blacklist amdgpu" to the end of /etc/modprobe.d/blacklist.conf

Then it worked fine for me on an R9 290.

[Mathew Hodson (mhodson)]

Roger or anyone else affected, there has been a new upload since your comment #114. The packages in wily-proposed should now blacklist amdgpu.

It would be good if you could verify that it is fixed in bug #1510573. Please follow the test case and instructions in the bug and mention the version of the package you tested.

[Philip Gemmell (philip-gemmell-r)]

@Roger Barrett, @Mathew Hodson

After having purged all of these files through recovery, and getting into tty, I performed the following steps:
sudo apt-get update && sudo apt-get upgrade (just to be sure)
sudo apt-get install --install-suggests fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed lightdm xorg ubuntu-desktop
sudo aticonfig --initial

I then looked into blacklist.conf, and couldn't see a line for blacklist amdgpu (there was one for amd76x_edac), so I added that line. I then restarted to a black screen. I restarted twice more to see if this was a problem that just required a few reboots, but no joy.

I rebooted into recovery (and re-purged the installed packages, and unblacklisted amdgpu), and the output for "dmesg | grep fglrx" is attached. Are there any further potential steps I can take?

[Roger Barrett (roger-m-d-barrett)]

@Mathew Hodson.

I removed the amdgpu blacklist entry I had manually added and used the "Additional Drivers" tab of Software and Updates to switch to the Open Source drivers.

This resulted in a fallback Unity desktop without GPU acceleration ( glxinfo reported gallium using llvmpipe, which is mesa's software implementation of OpenGL as far as I know ). It was usable but slightly laggy.

This process had left traces of fglrx-core and fglrx in the dpkg database. When I purged these, and rebooted, LightDM worked, but Unity hung on at ( first flickering, but eventually stable ) the desktop background, with no other screen artifacts.

Manually installing the fglrx-updates set of packages from wily-proposed then gave me the full binary driver accelerated desktop correctly without the need to blacklist anything.

Subsequently switching to the open source drivers still fails to give me GPU acceleration for X ( llvmpipe again ).

So something does not appear to be set or removed properly in the process of going from Proprietary to Open Source drivers. I'll see if I can find out what.

[Roger Barrett (roger-m-d-barrett)]

@Mathew Hodson.

OK, so when switching from AMD to Open Source drivers in the additional drivers tab, the fglrx-updates-core and fglrx-updates-dev are left installed. This means that on reboot, dmesg contains the following

[ 2.470360] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[ 2.470362] Disabling lock debugging due to kernel taint
[ 2.474696] fglrx: module verification failed: signature and/or required key missing - tainting kernel
[ 2.502797] random: nonblocking pool is initialized
[ 2.513664] <6>[fglrx] Maximum main memory to use for locked dma buffers: 31469 MBytes.
[ 2.514055] <6>[fglrx] vendor: 1002 device: 67b1 revision: 0 count: 1
[ 2.514697] <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
[ 2.515002] <6>[fglrx] Kernel PAT support is enabled
[ 2.515016] <6>[fglrx] module loaded - fglrx 15.20.3 [Sep 8 2015] with 1 minors

lsmod shows fglrx, with no users, but neither amdgpu nor radeon. Trying to load those modules with modprobe gives:

modprobe: ERROR: could not insert 'off': Function not implemented

Running gpu-manager gives:

last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
grep dmesg status 256
dmesg status 256 == 0? No
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? yes
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? no
Is radeon loaded? no
Is radeon blacklisted? yes
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? yes
Is nvidia kernel module available? no
Vendor/Device Id: 1002:67b1
BusID "PCI:2@0:0:0"
Is boot vga? yes
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Does it require offloading? no
last cards number = 1
I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for writing.
Error: can't write to /var/lib/ubuntu-drivers-common/last_gfx_boot

The Xorg.0.log file ( attached ) seems to try and fail a few alternatives before settling on FBDEV as the driver, which then causes AIGLX to degrade to software rendering.

To my little brain, this looks like fglrx doesn't get properly removed, and the open source modules are not removed from blacklisting.

[Paolo (vihochiamatiamici)]

Hi, i've been trying for some days to get the driver working, but whitout any result. I actually don't understand why it worked on Ubuntu and not working with Ubuntu Gnome?
I can just see the splash screen and black screen after that. No login manager displayed. I can log into tty1.
Does anyone have suggestion?

I attached my dmesg message.

[Duncan Fairley (duncanfy)]

Does "Fix Released" status mean I'll get it with a normal apt-get upgrade?

[Roger Barrett (roger-m-d-barrett)]

@Duncan

I think it's still being tested, so its probably only in Wily-proposed at the moment.

[Duncan Fairley (duncanfy)]

I upgraded to 15.10, couldn't get to login so I purged fglrx* and was then able to login with the open source drivers.
Then I added wiley-proposed and did the 'Selective upgrading from -proposed' thing.
Then I did update and install 'fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed'. Seemed to install successfully. Then I blacklisted amdgpu.

Then I rebooted, and experience the same black screen on startup. Next steps?

[Duncan Fairley (duncanfy)]

Okay I tried a second time - same steps with the addition of 'amdconfig --adapter=all --initial' after installing fglrx and it works now.

I have the same issue as #202 now with weird artifacts though.

[Roger Barrett (roger-m-d-barrett)]

@Duncan

I don't have odd artifacts; I meant that there is just a desktop background, no other screen items visible at all. But that is when I try to use the driver selection utility to revert to the Open Source driver, not when I'm trying to use the AMD binary driver, which works fine.

I think the switching process is all still a little bit confused as there now seem to be several possible drivers competing for the same hardware which need blacklisting/whitelisting appropriately every time you switch.

[xpris (xpris)]

Look like VAAPI not working correctly on "proposed" fglrx driver.

I have

"x@x-Aspire-7551:~$ vainfo
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
x@x-Aspire-7551:~$ "

and with this driver not working hw accelerate in Chromium DEV

look at bug:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514630

[Derf Skren (awron)]

I see some updates were released today including firmware. Does that mean it is safe to try the driver again?

In general how does one tell if the fix is now available for end user newbies like me? For instance the table at the top of the page - what order is it in?

[Matheus (matheus-boni-vicari)]

@Derf Skren

I'm not really experienced in the Launchpad/Bug reports system, but I think it's not in a stable version yet. Anyway, I'm also curious about the steps involved in this entire process.

[nipponicshell (thysnafy)]

Good day! When I install the Radeon HD 4200 driver Ubuntu 14.04.3 LTS, displays an error message, installed using --force installed and introduced error also ... complete installation and restart your notebook if I do not enter the system more, I that to uninstall fglrx, oh yes I can access the system, see the link below https://community.amd.com/servlet/JiveServlet/showImage/2-2681785-63657/20151103_010925.jpg

[QIII (qiii)]

AMD's fglrx does not support the HD 4200 in that version of Ubuntu. The last Ubuntu release supported by the AMD proprietary driver was 12.04.1.

Adapters prior to the HD 5000 series are not supported. This bug is not related to your issue.

[Launchpad Janitor (janitor)]

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

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for fglrx-installer-updates has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

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

[Matheus (matheus-boni-vicari)]

After the fix release, in order for the drivers to work properly do I still need to blacklist amdgpu or run the 'amdconfig --adapter=all --initial'? Cheers

[Philip Gemmell (philip-gemmell-r)]

I'm still have the same problems - after performing apt-get update and upgrade, installing fglrx-updates, fglrx-updates-core, fglrx-amdcccle-updates, lightdm, xorg and ubuntu-desktop, and then running amdconfig, I am greeted by a black screen upon restart (several restarts do not fix the problem). Purging fglrx*, lightdm and xorg return me to a command line interface.

Even if this problem is thus isolated to be separate to the problem in this thread, I am afraid I have hit a brick wall in troubleshooting this - does anyone have any advice on how I can track down the bug (and hopefully the solution!)?

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

@ SRU-Team comment #216 removed verification needed Nov.18.Nov2015

This package has to be seen in conjunction with bug #1510573 and vice versa

This package here is still in proposed-pocket as per TODAY and does not appear in

http://people.canonical.com/~ubuntu-archive/pending-sru#wily.html

https://launchpad.net/ubuntu/wily/+queue?queue_state=3&queue_text=fglrx

Pls. investigate and report to QC

[Anton Kozlovsky (kozlovsky-a-a)]

I've installed fglrx-updates driver and still can't get loaded UI.
So, get back to open drivers.

[Iulian (iulian-macare)]

I just installed fglrx-updates ( 2:15.201-0ubuntu2~15.10.2) on Ubuntu 15.10 and Radeon HD 7730M

[Anton Kozlovsky (kozlovsky-a-a)]

So, is there any solution?
I've tried to install various versions of drivers and kernels.
Neither fglrx nor fglrx-updates doesn't work with 4.1.x kernel and 4.2.x.

[Arnkell Logi Pétursson (logip)]

I'm having the same problems. I need the proprietary driver because the open source driver does not implement the computational part. Is there any timeframe for this bug fix?

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

@ Arnkell (logpip)

Timeline? see -> (https://wiki.ubuntu.com/StableReleaseUpdates) -> 3.6 Procedure

[Allen Webb (vertago1-s)]

I have been following another bug related to creating USB boot drives and it seems like they are having issues with gcc 5.0 because of a section alignment issue. I don't know whether or not that would effect compiling the wrapper for fglrx, but I figured I would bring it up incase it is linked to the root cause of the incompatibility with gcc. I know the boot issue with syslinux is different than the boot issue with fglrx, but if there is an issue created by a bug or change in gcc 5 it might give some light on other issues. See: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002/comments/6

[Mikael Thurberg (mthurberg)]

Just wanted to report that it has been working fine except one thing when I have been using the driver from the proposed..

Think I found a bug there, in amdccle where you can change your settings, I tried to enable so it updates the refreshrate of the screen so it is without tearing.. I tickled that box and I think I also did play around with changing the settings for the bit-depth on 8bit to automatically or vice versa.. then it asked for me to reboot but I did not do that, then I changed if it was the "without tearing" setting again and then the screen just did hang and stopped responding.. it have happend twice but I dont remember exactly how and in what order I did change that, but it was with the enable/disable tearing and bitdepth I changed and did not restart imedeately but did change the settings again somehow back and forth.. then that resultet in a hiccup of the system..

Otherwise the propsed driver have been working fine for me on a older slow computer with an amd hd6450 card.

If I disable the proposed and install the regular amd-updates, is that the same driver as it was in the proposed?

Thanks to you who have been working on this, it has been a pure relief to have been able to get the graphics working for me, thanks!

[Allen Webb (vertago1-s)]

@Mikael This probably isn't the right place to report something like that unless it doesn't happen when you use the same driver version without the gcc 5.0 fix. I am not sure where the best place is to report bugs in the proprietary driver it self but a quick google let me to: http://www.amdsurveys.com/se.ashx?s=5A1E27D23A3DE979

[Florian Sievers (florian-sievers)]

For users that still get a blackscreen on startup, try disable the bootsplash screen. That fixed it for me. Boot into recovery, remount your disk to be able to write to it. Remove 'splash' from the command line in /etc/default/grub and do an update-grub. After the next reboot, you should be able to see the login screen with the propertery driver.

[Derf Skren (awron)]

So is this actually fixed now? My only way to find out is to risk having to reinstall the whole OS.

[Thijs van Dijk (ametheus-deactivatedaccount)]

First of all, yes, this has been fixed in Wily; thanks, everyone!

Secondly, if it still somehow doesn't work for you, you can easily (for some value of "easy") revert by booting into a recovery shell in GRUB and simply executing `apt-get remove fglrx fglrx-updates`. See the wiki page "Recovery Mode" on the ubuntu wiki for more details:
https://wiki.ubuntu.com/RecoveryMode

[Derf Skren (awron)]

Thanks Thijs!

[Derf Skren (awron)]

Confirmed fixed for my Acer Travelmate 7750G with Radeon HD 6650M

[Luca Finzi Contini (lucafinzicontini-8)]

Anybody tried this with an AMD A10 PRO-7350B R6?

2015-12-02 12:21 GMT+01:00 Derf Skren <email address hidden>:

> Confirmed fixed for my Acer Travelmate 7750G with Radeon HD 6650M
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1493888
>
> Title:
> FGLRX incompatible with gcc 5
>
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in fglrx-installer package in Ubuntu:
> Fix Released
> Status in fglrx-installer-updates package in Ubuntu:
> Fix Released
> Status in fglrx-installer source package in Wily:
> Fix Released
> Status in fglrx-installer-updates source package in Wily:
> Fix Released
>
> Bug description:
> SRU Request:
>
> [Impact]
>
> The fglrx driver is not compatible with gcc 5.x. This causes the
> kernel module to crash on initialisation. As a result, users will boot
> into a black screen, as X will fail (except on Intel+AMD hybrid
> systems, where intel is used).
>
> [Test Case]
> 1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
> 2. Reboot
> 3. Check the display, and the output of the "dmesg | grep fglrx" command
> (to see the actual crash)
>
> Expected results: the system should be able to start X correctly.
>
> Actual results:
> The kernel module fails and X doesn't start.
>
> [Regression Potential]
> Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and
> will be replaced with the proper fix once AMD makes it available.
>
>
>
> __________________________________________________________________________
>
> With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
> able to SSH into the machine. I booted the older kernel
> (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
> using xserver-xorg-video-radeon I am able to get the graphics working,
> but even it has issues with my display port (The DVI ports are working
> correctly).
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.10
> Package: fglrx (not installed)
> ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
> Uname: Linux 4.2.0-7-generic x86_64
> ApportVersion: 2.18-0ubuntu9
> Architecture: amd64
> Date: Wed Sep 9 09:29:54 2015
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2011-01-07 (1705 days ago)
> InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> ProcEnviron:
> LANGUAGE=
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: fglrx-installer
> UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions
>

[Andy Bauer (knnniggett)]

In my case, Ubuntu created a trifecta of video driver show-stoppers, which prevented me from having a stable desktop while using a Radeon R9 380 and dual 1080p monitors. Each of the three drivers: fglrx, radeon, and amdgpu all had unique issues, and yes I'm aware that the issue with fglrx was in the release notes. I'm leaving out further details, because this post is about a solution that worked for me.

1) completely remove fglrx from your system
2) roll back to the 3.19 kernel used in the previous release of Ubuntu. Temporarily add the Vivid repo, add install the 3.19 kernel, boot off the 3.19 kernel, remove all other kernels from your system.
3) Modify the symlink /usr/bin/gcc to point to /usr/bin/gcc-4.9 instead of gcc-5
4) reinstall fglrx then reboot

I did this based on the previous comments in this bug report.

I've been running in this configuration a couple of weeks now with no issues. It's possible these changes could cause problems with something else expecting a newer kernel or gcc-5, but I have yet to experience any issues.

I plan to leave my system in this configuration until the next release of Ubuntu, next April.

[mookey41 (redguy41)]

My problem is with hybrid Intel/ATI graphics. WHen I try to use fglrx (installed on additional drivers, or command line) the booting reverts to Intel. ATI does not work.

Ubuntu 15.10. I'm using Lenovo z51-70 with ATI R9 R8900HD and Intel graphics.

Any suggestions?
Cheeers,

Gaj

[Matheus (matheus-boni-vicari)]

@mookey41:

I have the same issue. After a few weeks of working fglrx drivers and all, I tried to switch to Intel VGA and then back to AMD and the fglrx drivers are not working anymore.

[Stephan (sirstephanikus)]

Where is the fix? To roll back to Kernel 3.19 is not a fix, it is a downgrade of a whole OS!

Fgrlx makes trouble for years now. Even AMD stated that the catalyst suite is only working til 3.19 Kernel Version.

[mookey41 (redguy41)]

So if I enable willy proposed repository and do an update, do I just tick the AMD fglrx driver from the Additional Drivers tab, or do I need to install it through the command line? I have tried the former, and it doesn't work.
Using ubuntu 15.10 on a Lenovo AMD/Intel hybrid. AMD R9, HD8900.
The graphics works, but lags.

Thanks.

[Oscar Parada (oparada1988)]

Alright you guys, I don't know if im being stupid. Im using the Gnome version of Ubuntu, I select the propose updates, update the syste, install fglrs-updates and I see the gcc 4.9 will be installed... great, installed runs everything good. reboot, see splash screen.... then blank screen. am I doing something wrong? using an A8-6410. thanks

[Philip Gemmell (philip-gemmell-r)]

I'm still having the same problem - booting to blank screen unless I purge fglrx*, lightdm and xorg to get to a command line interface. If I only try removing fglrx*, I get a window telling me that I have to set-up my graphics card, etc., but I can't progress beyond that. I've edited /etc/default/grub to try and remove the splash screen, and commented out the only line that seemed appropriate:
#GRUB_CMDLINE_LINUX_DEFAULT="drm.debug=0xe plymouth.debug"
However, this lets me see that the system tries loading lightdm, but then falls down - at most, I get a single character cursor at the top left of the screen. All available updates are applied.

An abbreviated syslog is attached, but I'm afraid I don't know how to use this to track down the problem further.

[Allen Webb (vertago1-s)]

@philip-gemmell-r what version of fglrx-updates did you install? (the package version) I don't think the fix is actually released in the main repositories. They are still showing (2:15.201-0ubuntu1)

If you want to get the fixed version you need to enable wily-proposed long enough to install fglrx-updates. Then you can disable wiley-proposed. For instructions see prior posts.

[Philip Gemmell (philip-gemmell-r)]

I've been installing from the main repositories, but had previously tried using the wily-proposed instances without success. However, I've tried again, using the following steps (based on reply #123):
1) Checked /etc/apt/sources.list, and it already includes the line "deb http://gb.archive.com/ubuntu wily-proposed restricted main multiverse universe"
2) Checked /etc/apt/preferences.d/proposed-updates, it exists and contains:
Package: *
Pin: release a=wily-proposed
Pin-Priority: 400
3) Run 'sudo apt-get update
4) Run 'sudo apt-get instal --instal-suggests fglrx-updates/wily-proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed lightdm xorg ubuntu-desktop'

However, following these steps, I am told "Release 'wily-proposed' for 'flgrx-<name>' was not found", where <name> is the remaining extension for the 3 packages. Have I managed to add the wrong repositories somehow?

[Mikael Thurberg (mthurberg)]

@Allen Web

Sorry for the late reply. Yes you might be right about that!
Did not think about that! Excuse me.

Thanks for the link!

[Philip Gemmell (philip-gemmell-r)]

I finally managed to solve my problem - it turns out to have been far simpler than expected: http://askubuntu.com/questions/692577/ubuntu-15-10-boot-hangs-when-starting-lightdm/692627#692627

[John Schroeder (jschroed)]

Thanks Philip. The link to Ubuntu 15.10 boot hangs when starting lightdm helped me too. I had my system set to auto login to my user account but I could not log out or disable the auto login without having lightdm hang on startup. Now I can logout again!

According to that link, in the Ubuntu 15.10 release notes, they said to uninstall fglrx before upgrading to 15.10. That would have avoided the problem lightdm hanging.

I still have an issue where Ctrl-Alt-F1 to F6 do not work for me when fglrx is installed but that is probably a separate issue.

[Victor Colta (colta-vicu)]

Affects me too

[Kaziev Nadir (kurah)]

AMD Radeon R9 380 4G
Affects me too

[Andrew Green (andyg54321)]

I hit this today when upgrading from 15.04 to 15.10 on Dell with hybrid graphics. It booted into safe graphics mode, offering a list of graphic operations to try. I didn't touch that and instead ssh'd into the system.

There I looked at /etc/apt/sources.list and saw that wiley-updates was represented.

Next I ran:
  $ sudo apt-get update

Which failed with:
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

So I played along:
  $ sudo dpkg --configure -a

This ran well and stopped to prompt me to replace or keep some ATI related files. I opted for replace in every case by answering "Y".

It installed a bunch of stuff and I saw it compile the fglrx module. After it completed I rebooted with:
  $ sudo shutdown -r now

It rebooted and graphics worked again. glxgears seems happy.

HTH

[Jason C. McDonald (codemouse92)]

I had this initially on my Toshiba back in October. I am hesitant to attempt an upgrade again, but 15.04 is no longer supported, so I'm between a rock and a hard place. Will the `do-release-upgrade` still have this issue, or is it safe to proceed and expect it to work normally?

[mtrsky (mtrsky)]

I had this problem upgrading from 15.04 to 15.10 with a Radeon 7570 card. Andrew Green's solution above worked for me!

[aamadis (aamadis)]

I downloaded the debs from #48 but it seems they're only for 64-bit architecture. Any debs for 32-bit users?