Created attachment 326750 [details] Xorg.0.log without the nomodeset This is a Supermicro X5DA8 with 2 Xeon 3.06 GHz CPUs and 2 GB of Ram with a Radeon 9600 (R350) video card and Viewsonic PT813 monitor. I upgraded from F9 to F10 using the final release DVD and then applied all current updates. The X display only allows 640 x 480 and 800 x 600 at 60 Hz refresh. Also switching to a VT via CTRL + ALT + Fn (n = 2-6) yields a blank display with no video to the monitor. Adding nomodeset to the kernel command line resolves the issue. Many display modes are available in X including the 1600 x 1200 @ 75 Hz. refresh that I like to run. Also, all VTs are available via the switch keys described above. This does not allow the new Plymouth flash screen during startup, but I guess that's to be expected with KMS disabled. One issue remains: If I switch to any VT while in a gnome session, when I come back to VT1 the gnome session has been killed and I have to log back in. Any work that was in progress is lost. I understood that F10 was supposed to have the R200 and up Radeons working. I have attached 2 Xorg.0.log files below. The first is without the nomodeset and the second is with nodeset on the kernel coomand line. The kernel I have been working with is 2.6.27.7-134.fc10.i686. How reproducible: Always happens without the nomodeset on kernel command line. Steps to Reproduce: 1. boot system without the nomodeset 2. System comes up with limited display modes and no VTs 3. Add nomodeset to kernel command line 4. System comes up normally. Actual results: Expected results: Additional info:
Created attachment 326751 [details] Xorg.0.log with nomodeset added to kernel command line
Created attachment 326752 [details] Xorg.0.log with nomodeset added to kernel command line
Created attachment 326753 [details] Xorg.0.log without the nomodeset
Hibbard, Does this still happen with 2.6.27.12-170.2.5.fc10 ? Please post full dmesg as uncompressed text attachment to this bug too. Thanks
Created attachment 331079 [details] Full dmesg from 2.6.27.12-170.2.5.fc10.i686 as requested. Yes, it still happens with this new kernel. If I remove the nomodeset from the kernel command line, the only resolution choices I'm offered in X are 640x480 and 800x600. With the nomodeset, everything works normally. The attached dmesg is with the nomodeset on the kernel command line. If you need a dmesg from the no nomodeset state, please advise.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.