Then you can activate sid and install fglrx from there. There is a point release which works.Code:wget -NP /tmp http://kanotix.com/files/fix/oss-test/purge-binary-driver.sh sh /tmp/purge-binary-driver.sh
On openSUSE (which I've ben using since 11.1 or so, with fglrx):
Personally I don't blacklist radeon, I just switch to a tty and issue "init 3" as root prior to installing the drivers. Otherwise there is a conflict of some sort with the GL libraries, and 3D hardware acceleration doesn't work.
Last edited by PsynoKhi0; 08-12-2012 at 12:50 PM.
Does not tell me what the hardware looks like. This is part of why AMD bundled the "atigetsysteminfo.sh" script that should be located at "/usr/share/fglrx/"
However, some People would foolishly expect all media files to play regardless of system specifications. A desktop with 2.5gHz to 3.0gHz is useless if the System Memory is slow ( DDR2 or DDR memory).
It is impossible that fglrx 12-6 runs with debian wheezy without libpciaccess hack.
I think the OP is clueless and so are these other ATI/AMD fanatics. I checked out a Thinkpad T500 laptop and the suspend doesn't work. I can't help think graphics drivers has something to do with it. If one booted up Windows 7 with the same hardware and tried suspend (place the lid down and then lift it up), it would probably wake up properly. I guess people here who own ATI hardware just don't do anything with their computer. Maybe they just stare at it all day or play the odd game that doesn't require much or something.
ATI/AMD drivers suck quite a lot. I'm not sure what happens with Nvidia-driver equipped laptops but I admit, Nvidia is a POS too when it comes to the most recent Nvidia laptops. But, there's already those in the community bashing Nvidia. It seems that ATI/AMD has a ton of apologists defending them all the time while everyone jumps on the bash-Nvidia bandwagon. They both suck when it comes to Linux because support is abysmal for either one.
Doesnt work in what sense? Machine does not resume at all? Or just the screen is blank on resume? In the latter case you just needed to increase the brightness a bit to get it working. Annoying workaround : YES. But a bug report with proper description would help more dont you feel?
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.