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! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
