I have a HD 6550M and it wouldn't wake up correctly with fglrx for several months.
There were different results when waking up:
1. nothing worked. Even the hard disk wouldn't spin up. And yes, it was fglrx because when booting with "nopat" fglrx used some own pat implementation and 1. didn't ever happen with nopat.
2. Just the graphical output being completely frozen and fglrx would write "ASIC hang happened" to the log.
3. X hanging with 100% CPU in R+ state with no error message.
Since I switched to the open source driver the notebook wakes up correctly about every time.
The xrandr compatibility was also kind of broken back when I used it: You need to have a X config with a Virtual Screen size big enough if you want to attach a second screen in before, otherwise you need to restart X (!!!) in order to attach a screen with its native resolution.
I also thought xrandr output like this was impossible until fglrx managed to report two preferred resolutions (even in wrong order):
That said the topic was more about OpenGL compliance/performance.Code:CRT1 connected 1400x1050+1600+12 (normal left inverted right x axis y axis) 433mm x 271mm 1400x1050 60.0*+ 1680x1050 60.0 + 1280x1024 75.0 60.0 1440x900 60.0 1280x960 75.0 60.0 1280x800 75.0 60.0 1152x864 60.0 75.0 1280x768 75.0 60.0 1280x720 75.0 60.0 1024x768 75.0 70.1 60.0 1024x600 75.0 70.1 60.0 800x600 72.2 75.0 60.3 800x480 72.2 75.0 60.3 640x480 75.0 72.8 67.0 59.9 640x350 60.0 70.1
There are some more topics one could discuss when it comes to sucking drivers. I am going to buy a notebook with a HD 7970M with AMD's optimus-like "Enduro". I'm not sure if this is a good idea but with GPU offloading already working it at least has a pretty good chance working in the not so far future if the proprietary AMD drivers fail. It will also be very interesting to see if the windows driver in a windows vm succeeds in using the dedicated card with vt-d and pci passthrough.
I use the closed source AMD driver as well as the NVIDIA closed source. NVIDIA has always been more stable even on Windows trust me. everyone was knocking ATI drivers back in the day. I also use laptops with <r300 cards that use the opensource xf86 drivers and they are more stable, although they run hot and performance isn't amazing (seriously unimpressive) . My main rig uses AMD proper and so far the only video crash (limited) was playing skyrim in Wine when switching between the loading screen and the main game display.
To those with tearing issues, you know you can force vsync right? Personally I limit my FPS in gaming and sync to avoid that issue. You would be amazed at how well ~30 FPS play when you have headroom up the wazoo as to avoid chokes.
Don't you need to setup things in Windows as well or am I missing your point? Why are there things like CCC if you're not meant to tweak things?
Last edited by nightmarex; 08-13-2012 at 12:07 PM.
As for the blame-game, I actually am of a different opinion: I see no reason why AMD should pour man-hours into their drivers to fix someone else's mess. They already have their hands full. And if anyone has issues with the OpenGL specs (too complex, obscure and what not), they should take them to the Khronos group, not AMD.
Now before I get jumped: there are most probably bugs in fglrx, like in any piece of software, especially of that complexity. BUT I really find people's habit of jumping to conclusions on how every problem has to be caused by fglrx "because it works with XYZ" totally disingenuous. Which is what that Slashdot entry is about.
I solved issues with proprietary drivers long long ago by simply not using them.
The only proprietary driver worth a damn in Linux any more is Nvidia's proprietary driver. If you don't mind running proprietary video drivers for performance and you are running anything but Nvidia you are doing it wrong. With ATI proprietary you are going to end up spending a lot more time and money to get the same performance and you still will have to deal with their shitastic drivers.
I don't understand why anybody bothers to punish themselves like this.
When everything works perfectly well on OSS Intel, OSS AMD, and proprietary Nvidia while proprietary ATI drivers are a pain to install and have application compatibility issues up the wazoo... then why assume that it's everybody else's problem except for proprietary AMD?
It's just silly.
There is absolutely no analytic value in the "It's fglrx' fault" mindset. None. It's merely comfy sheep behavior.
Last edited by PsynoKhi0; 08-13-2012 at 05:45 PM.