Description of problem: X as included in current "rawhide" defaults to a resolution of 1280x1024 for the combination of an ATI Radeon X800 video card and a 21" CRT HP A4576A. However, the optimum resolution is 1400x1050 which, moreover, respects the aspect ration of 4/3 of the CRT. For standard operation without modesetting, adding "nomodeset vga=0x345" to the kernel boot options and a custom xorg.conf specifying a suitable mode 1400x1050 allow to use this preferred mode all the way up to the moment when GDM appears. After removing "nomodeset" from the kernel boot options, the screen stays dark during the boot procedure. After the usual boot delay during which disk activity gives some acoustic feedback, X comes up, but the mouse cursor is unresponsive. The systems is stuck and needs a hard reset in order to resume operation. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.12.1-4.fc11.x86_64 How reproducible: Always. Steps to Reproduce: 1. Boot with kernel options "rhgb quiet vga=0x345". Actual results: Screen stays black until X starts. At this point, X is locked up. Expected results: System boots up with a graphical interface, and the graphical login manager allows users to log in. Additional info: This never used to work in the past, i.e. for F10, but plymouth needs a way to be told a preferred resolution. Otherwise, a seamless boot procedure is hardly possible when X does not know how to determine the optimum video mode, or the administrator has chosen a different default mode.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual uncompressed text/plain file attachments using the bugzilla file attachment link below. You can retrieve them by booting into runlevel 3 with just "3" in the kernel command line. Also, could you please try the following test : First, boot into runlevel 3 without KMS by adding this to the kernel command line : nomodeset 3 and then run the following commands : modprobe -r radeon drm modprobe drm debug=1 modprobe radeon modeset=1 At this point, please save dmesg and add it to this bug if at all possible. init 5 At this point, please upload Xorg.0.log (ssh'ing to the machine if at all possible). Any partially run test is useful if you can get the logs. We will review this issue again once you've had a chance to attach this information. Thank you in advance. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 338460 [details] custom xorg.conf for ATI Radeon X800 and 21" CRT HP A4576A
Created attachment 338461 [details] Output of dmesg after booting with modesetting and vga=0x345
Created attachment 338462 [details] Tail of /var/log/messages after booting with modesetting and vga=0x345 There is an error message near the end of the log file. I don't know whether this is meaning anything relevant: "localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id" . At the end of the boot procedure, only a cursor in ssen on top of an entirely black screen. Input is frozen, and the system needs to be powered off.
Created attachment 338463 [details] Xorg.0.log after booting with modesetting and vga=0x345
Created attachment 338472 [details] Output of dmesg for the case "drm debug=1" Installed packages include: - kernel-2.6.29.1-52.fc11.x86_64 - xorg-x11-drv-ati-6.12.1-8.fc11.x86_64 - xorg-x11-server-Xorg-1.6.0-17.fc11.x86_64
Created attachment 338474 [details] Tail of /var/log/messages for the case "drm debug=1" X actually starts up with a black screen but a visible cursor which is animated at first. It is possible to move the pointer a couple of times albeit extremely sluggishly. Then it does not respond to mouse movements anymore. The keyboard gives acoustic feedback when typing ctrl-alt-del.
Created attachment 338475 [details] Xorg.0.log for the case "drm debug=1"
does it work if you don't put vga= in? really don't do that anymore.
It definitely does w/o "vga=0x345". But the point of this bug report is actually this specific case which is nowhere forbidden. Moreover, the reason for doing so was outlined in the initial report: the lack of being able to indicate a preferred mode to plymouth. A kms mode of 1280x1024 on a 21" CRT exhibiting an aspect ratio of 4/3 is annoying, and the avoidance of unnecessary mode switches was advertised as one major aim of kms.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
For a fully updates F11, the system does come up in KMS mode with kernel option "vga=0x345" but the screen remains black except for the mouse pointer which is visible and which actually responds to mouse movements now.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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
Improving summary. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers [This triage is part of collective effort done by students of University of Rijeka Department of Informatics.]
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.