I do not understand how this fixed it but it did. I am now using fglrx without hard freezes or display corruption. 3D does not work but I don't care. I only need 2D as this is a development workstation.
I did 3 things. As stated I used the gnome screen res control panel to change to 1280x1024.
secondly I manually edited xorg.conf and replaced vesa with fglrx instead of using the restricted manager to do it for me.
finally and this seems to be what fixed it (and why I am so puzzled about how this fixed it) I edited my monitor description.
I commented out the HorizSync and VertSync lines that came default and replaced them with these lines for my Dell 2001FP
I then reset the X server and logged in. Switched the resolution in gnome back to 1600x1200 and now all is well.
Strangest bug I have ever run in to. I ran in to this same issue with feisty beta and could never resolve it. Went back to edgy at that time. Anyway I hope this helps anyone else who runs in to this bizzare issue. I frankly have no idea how this fixed the problem but all is working fine now.
fixed it.
I do not understand how this fixed it but it did. I am now using fglrx without hard freezes or display corruption. 3D does not work but I don't care. I only need 2D as this is a development workstation.
I did 3 things. As stated I used the gnome screen res control panel to change to 1280x1024.
secondly I manually edited xorg.conf and replaced vesa with fglrx instead of using the restricted manager to do it for me.
finally and this seems to be what fixed it (and why I am so puzzled about how this fixed it) I edited my monitor description.
I commented out the HorizSync and VertSync lines that came default and replaced them with these lines for my Dell 2001FP
HorizSync 31 - 80
VertRefresh 56 - 76
DisplaySize 408 306
I then reset the X server and logged in. Switched the resolution in gnome back to 1600x1200 and now all is well.
Strangest bug I have ever run in to. I ran in to this same issue with feisty beta and could never resolve it. Went back to edgy at that time. Anyway I hope this helps anyone else who runs in to this bizzare issue. I frankly have no idea how this fixed the problem but all is working fine now.