Hot answers tagged fglrx
When I used a EDID-blocking VGA KVM switch, I used a small script to fix the resolution after logging in: xrandr --newmode "1600x1200_60.00" 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync xrandr --addmode VGA-1 1600x1200_60.00 xrandr --output VGA-1 --mode 1600x1200_60.00 I think I got the mode line from xrandr somehow (with the monitor ...
A workaround without loosing VA would be to use the 12.6 AMD proprietary driver or prior. The tearing regression seems to start with 12.8. http://support.amd.com/us/gpudownload/linux/previous/Pages/radeon_linux.aspx Just enable execution permissions, run the script with root privileges and build a package and install it.
Could you add card model? I just tested on my test machine, and it surely accepted: Virtual 4096 4096 Can you add the output of 'xrandr'? Here's mine (HD5850, 09:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cypress LE [Radeon HD 5800 Series]) Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 4096 x 4096 DFP1 ...
Not every number can be used for the "Virtual" directive in case of fglrx. Not sure what the exact policy is, but "3600 1080" will not work. Try "3600 1200". If doesn't work, try "3600 3600" then "3600 1800" too. Don't worry about the numbers too much, xrandr will actually use a smaller area, but for some reason the driver expects "round" numbers.
The built-in support for ATI cards in ubuntu 9.04 is better. You shouldn't need the fglrx. I would suggest doing some kind of test clean-install, though perhaps the Live CD would be sufficient to verify that ubuntu default ATI drivers will work for your system. The reason I suggest clean install is that customizations for Video (e.g., directly using fglrx ...
check the directory /sys/class/drm/card0/power it has several files that modify the cards power, most will have to first have the module, "radeon", loaded with dynclks=1 should be able to echo "high", "mid", "low", or "auto" into the control file and change the clock speed
I figured out what the problem was, and thought I should post it here just in case it can help someone who may be having similar problems. The problem was that my graphics card was failing in interesting ways. My guess is that the on-card memory was becoming overheated and failing. This is why no errors came up in Memtest86+; it only scans the RAM and not ...
Experimental drivers are called "experimental" because they are unstable and not efficiently tested. As a result, weird problems, errors and glitches can result. With this in mind, I suggest you try an earlier stable version (i.e. the latest stable release, rather than the latest release in general) Good luck, hope this works! If not, leave a comment and ...
I have the same screenshot problem in Mint 13 x64 with Cinnamon. If this bug is the same issue, then it appears, "This is caused by AMD's proprietary driver. There's nothing [Ubuntu] can do about it." Not sure what driver version, but I installed it from the package repos, not from AMD. Here's a workaround I just found that has worked for several ...
Only top voted, non community-wiki answers of a minimum length are eligible