Not had time to report an upstream bug yet, but suffice to say that I installed the latest proprietary fglrx driver packages direct from AMD's site using the --buildpkg switch (file downloaded was called "amd-driver-installer-12-1-x86.x86_64.run") and I got a successful suspend/resume using this driver/module.
However, my main reason for wanting to use the proprietary fglrx driver was for VAAPI/XVBA, but having also installed the xvba driver and libva-glx1 and subsequently turning on GPU acceleration in VLC - X hard crashed out and dumped me back to the lightdm login screen the moment I loaded a video...
Not had time to report an upstream bug yet, but suffice to say that I installed the latest proprietary fglrx driver packages direct from AMD's site using the --buildpkg switch (file downloaded was called "amd-driver- installer- 12-1-x86. x86_64. run") and I got a successful suspend/resume using this driver/module.
However, my main reason for wanting to use the proprietary fglrx driver was for VAAPI/XVBA, but having also installed the xvba driver and libva-glx1 and subsequently turning on GPU acceleration in VLC - X hard crashed out and dumped me back to the lightdm login screen the moment I loaded a video...