[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-11-12 Thread Roger 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 th

[Desktop-packages] [Bug 1510573] Re: fglrx should blacklist amdgpu

2015-11-12 Thread Roger Barrett
Do you remember to reverse the whole process when going from fglrx -> open source ? I can now switch from radeon to fglrx, but then it seems to prevent the open source radeon driver from loading when I switch back. See bug 1493888 Post #203 for details. -- You received this bug notification bec

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-11-12 Thread Roger Barrett
@Duncan I think it's still being tested, so its probably only in Wily-proposed at the moment. -- 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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-11-12 Thread Roger 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 Technolog

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-11-12 Thread Roger 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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-11-11 Thread Roger 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/blackl

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-10-27 Thread Roger 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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

2015-10-27 Thread Roger 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 c

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with kernel 4.2

2015-10-24 Thread Roger 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 ha

[Desktop-packages] [Bug 1501276] [NEW] No Screen or Blank Screen instead of Login Screen

2015-09-30 Thread Roger Barrett
Public bug reported: Release 15.10 Wily Beta 2. GPU R9 290. Hawaii Core. When switching to fglrx from radeon, I get no graphics. Scenario 1: Use the "Additional Drivers" push-button to change to fglrx ; do not create xorg.conf. Result: On reboot, both the Displayport and DVI screens turn off (