Hide Forgot
Description of problem: Serial console (booting with additional kernel parameter " console=ttyS0,115200") does not work with DRM. Instead of the normal console messages, including drivel at boot, almost nothing comes over the serial line. Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-19.20110216git42c16ff.fc15.x86_64 How reproducible: every time Steps to Reproduce: 1. boot gfx_test_week_20110221_x86-64.iso with additional kernel parameter " console=ttyS0,115200" 2. 3. Actual results: Empty 25x80 light gray "console terminal" in upper left of screen, instead of usual rhgb graphical progress screen. Almost no console messages appear on serial line. The one line that does appear is [ 1.223128] [drm] nouveau 0000:01:00.0: Pointer to BIT loadval table invalid and the contents of that one line vary by model of video adapter. Expected results: No interference. ttyS0 is the serial line, tty0 (no 'S') is the vga console. Using only the serial line should have no effect on the vga console. If using both " console=ttyS0,115200 console=tty0" then it would be OK to disturb the vga graphics console (with the vga text console.) Additional info:
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. It would be interesting to know more about what's going on inside of the system, when this happens. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 482573 [details] /var/log/Xorg.0.log There is no /etc/X11/xorg.conf.
Created attachment 482574 [details] output of dmesg
Created attachment 482575 [details] /var/log/messages
Created attachment 482767 [details] [NVA5] /var/log/Xorg.0.log
Created attachment 482768 [details] [NVA5] output of dmesg
Created attachment 482769 [details] [NVA5] /var/log/messages
Same problem on a recent card: 01:00.0 VGA compatible controller [0300]: nVidia Corporation GT200 [GeForce GT 220] [10de:0a20] (rev a2) Adding "[NVA5]" to the Summary title.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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