Description of problem: System lockup occurs after application of xorg updates: xorg-x11-server-Xorg-1.5.1-10 xorg-x11-server-common-1.5.1-10 xorg-x11-drv-ati-6.9.0-21 This was occurring previously and adding the "AllowEmptyInput" allowed a workaround, but that doesn't seem to be helping now. The only way I am able to access the system is to boot in single-user mode. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.5.1-10 xorg-x11-server-common-1.5.1-10 xorg-x11-drv-ati-6.9.0-21 How reproducible: System locks after login during an X session. Same result whether I use GNOME or KDE. Steps to Reproduce: 1. Boot system normally 2. Login using X 3. Actual results: System locks up Expected results: Normal operation Additional info:
Created attachment 319781 [details] Xorg Log when failure occurs
Created attachment 319782 [details] xorg configuration file when failure occurs
Does putting nomodeset on the kernel command line help?
No, unfortunately not. I am currently using nomodeset since I have a ATI R200. If I do not specify the screen resolution is too large. Before the latest updates I was encountering the issue I reported in: 464921 which was distortion on the right side of the screen. With the latest updates I cannot use X at all, with or without the "nomodeset" parameter.
OK, just a workaround -- would switching to vesa help (via edit of xorg.conf or system-config-display).
No, changed to vesa and still have the same issue. System locks up a few moments after login.
Shut, vesa should really work.
This isn't an r200 at all its an Xpress 200M rs485. i.e. its the worst piece of crap ATI ever produced. but we should try and get you running again. In theory modesetting should work fine on that chip. I'm going to rebase kernel/ati today so we'll see if they help the problem at all.
Applied: xorg-x11-drv-ati-6.9.0-25 kernel-2.6.27-0.398.rc9.fc10 Same issue, no improvement whether I have vesa or radeon specified in xorg.conf
Applied: xorg-x11-drv-ati-6.9.0-28.fc10.x86_64 kernel-2.6.27.3-27.rc1.fc10.x86_64 xorg-x11-server-Xorg-1.5.2-7.fc10.x86_64 xorg-x11-common-1.5.2-7.fc10.x86_64 Looks like booting without "nomodeset" parameter correctly identifies proper screen size, resolution... however, still getting lockup a few moments afer starting kde or gnome. Same result whether or not I use nomodeset or vesa in place of radeon. I've attached latest xorg.0.log and dmesg. Let me know if there is any additional information I can provide to assist in getting this resolved. Thank you.
Created attachment 320950 [details] Xorg.0.log
Created attachment 320951 [details] results of dmesg
Found an issue with yum where errors were being received with PackageKit, appears some type of corruption was occuring. Manually deleted the packages and reinstalled. Now X session no longer locking, however receiving large text much the same as reported in: Bug 435216 - F9 - ATI Driver - Text too large.
Workaround: As per Bug 435216: Add statement to Section "Monitor" ---> DisplaySize 289 210 Add statement to Section "Device" ---> Option "Monitor-LVDS" "Monitor0" Please advise when further testing can be done so I can remove the workaround and validate. Thanks!
Lockup problem still occurring, just not immediately after login. Please advise type of information which may be helpful to collect.
Opened bug: Bug 467983 - F10 - ATI Driver - Text too large to track large text problem. This bug will remain for lockup issue.
*** This bug has been marked as a duplicate of bug 435216 ***
Incorrectly closed. This is not a duplicate of 435216. This bug is related to a lockup situation which I am currently testing. 435216 was opened by me for a large text issue related to the F9 beta. I've opened up another bug for the F10 beta to track this issue which is currently occurring.
Appears lockup issue resolved with updates applied in comment 10, with further issues being resolved by manual circumvention of issue regarding packagekit referenced in comment 13. Closing.