Bug 701190
| Summary: | cannot escape CRT's preferred mode (resolution on cmdline is ignored) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Felix Miata <mrmazda> | ||||||||||||||||
| Component: | xorg-x11-server-utils | Assignee: | Jérôme Glisse <jglisse> | ||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 23 | CC: | anaconda-maint-list, dshea, g.kaviyarasu, jglisse, jonathan, jzeleny, mcepl, vanmeeuwen+fedora, xgl-maint | ||||||||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i386 | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | [cat:rendering] | ||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2016-12-20 12:07:27 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
The text interface resolution is managed by kernel, so if you see kernel switching the tty to an undesired resolution (note: this probably happens at the moment when the anaconda loader probes modules) it is probably a kernel bug. As for the X server resolution: this is handed by anaconda itself. I see in your log files that you used resolution=... which is supposed to set the desired resolution in X using xrandr. Your program.log shows xrandr was indeed run you mention it failed to change the resolution. (it works on my old dell machine however) Reassigning this bug to xrandr. (In reply to comment #1) it works on my old dell machine however As it happens the rv200 in the logs is an OEM AGP card from a Dell GX260, a machine with onboard i845G video, but installed in a self-built K7 system. Created attachment 501525 [details]
anaconda.xlog
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 add drm.debug=0x04 to the kernel command line, restart computer, and 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 501541 [details]
/etc/X11/xorg.conf
/proc/cmdline
ro root=LABEL=H16Afedora15 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nodmraid resolution=1152x864 video=1152x864 3 drm.debug=0x04
Created attachment 501542 [details]
/var/log/Xorg.0.log
/proc/cmdline
ro root=LABEL=H16Afedora15 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nodmraid resolution=1152x864 video=1152x864 3 drm.debug=0x04
Created attachment 501543 [details]
output of the dmesg command
/proc/cmdline
ro root=LABEL=H16Afedora15 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nodmraid resolution=1152x864 video=1152x864 3 drm.debug=0x04
Created attachment 501545 [details] /var/log/messages /proc/cmdline ro root=LABEL=H16Afedora15 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nodmraid resolution=1152x864 video=1152x864 3 drm.debug=0x04 This was reported as an installation problem. Did you really mean to ask that I install again using drm.debug=0x04 on cmdline? I hope using drm.debug=0x04 on an already installed system somehow helps to solve the reported anaconda/installation problem, since as noted in comment 0, using xorg.conf solves the problem for post-installation use. (In reply to comment #0) > Post-installation, video=1152x864 on cmdline produces expected results, and so > does setting PreferredMode to something other than 1600x1200 in xorg.conf. So, this is an issue only with Anaconda? Once the system is installed everything works as expected? I am not sure I understand your original problem correctly. Also (but that might be unrellated): [ 364.856] (EE) AIGLX error: dlopen of /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: cannot open shared object file: No such file or directory) [ 364.856] (EE) AIGLX: reverting to software rendering [ 364.856] (EE) AIGLX error: dlopen of /usr/lib/dri/swrastg_dri.so failed (/usr/lib/dri/swrastg_dri.so: cannot open shared object file: No such file or directory) [ 364.856] (EE) GLX: could not load software renderer Could I get an output of command rpm -Va mesa-dri-drivers\* please? Thank you (In reply to comment #9) > (In reply to comment #0) > > Post-installation, video=1152x864 on cmdline produces expected results, and so > > does setting PreferredMode to something other than 1600x1200 in xorg.conf. > So, this is an issue only with Anaconda? As indicated in comment 0, unless there's something else involved during installation besides Anaconda, yes, but I suspect an installation kernel issue at least as regards the ttys during installation while Anaconda has control over the GUI. > Once the system is installed everything works as expected? That's what I wrote in comment 0, so yes. >I am not sure I understand your original problem correctly. There are two basic classes of people who choose to use a big display: 1-people who want lots of space for lots of little stuff 2-people who need stuff to be big This bug is about class two, a usability issue. Known cmdline directives for producing the user's choice of (larger/legible) text size on both the ttys and X/Anaconda are being ignored if the display used has functional EDID. Furthermore, I believe bug 693995 and possibly by implication bug 692293 have the same roots, cmdline video specification parameters being ignored by a KMS kernel that finds imperfect or missing EDID. IOW, looking at bug 693995 and this bug together, the kernel insists on imposing 1024x768 if bad EDID, and hardware-preferred resolution if good EDID. > Could I get an output of command > rpm -Va mesa-dri-drivers\* Output from that command on the rv200 system is null. Output from 'rpm -qa | grep mesa' is: mesa-libGL-7.11-0.6.20110412.0.fc15.i686 mesa-libGLU-7.11-0.6.20110412.0.fc15.i686 Problem remains in F17. Remains on Nvidia and Intel as well. No improvement in the new installer. Created attachment 655547 [details]
1920x1440 screenshot - anaconda started with no video parameters on cmdline
This is what F18beta looks like even when I use resolution= and/or video= and/or vga= on cmdline to try to get 1024x768 or 1280x1024. To see what I see real size your screen needs to be or emulate 12" and 1200px in height.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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. No material improvement evident since this was filed. And anaconda still isn't a display driver. Anaconda uses xrandr to set the resolution from inst.resolution= in graphical mode, and the text mode resolution is up to the kernel. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 496139 [details] .tgz of installation logs (on rv200) Description of problem: Using rv200 or i845G video with P275 Trinitron ('21"' IBM) to HTTP install from gwdg.de or mirrors.kernel.org, and for several weeks at least, none of: vga=[791,0x318,etc] or [resolution,video,display]=[1024x768,1152x864,1280x960x1400x1050] on cmdline cause installation with native driver to not use 1600x1200 on either the ttys or Anaconda. Most cause a desired mode initially, but kernel modeset kick-in always switches to to the display's preferred mode, resulting in text too small to read comfortably without sticking my nose too close to the screen for back or peripheral vision comfort. Post-installation, video=1152x864 on cmdline produces expected results, and so does setting PreferredMode to something other than 1600x1200 in xorg.conf.