| Summary: | [Crestline] tty console resolution limited to 1024x768 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juergen Wieczorek <juergenw_> | ||||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 15 | CC: | ajax, elad, mcepl, xgl-maint | ||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | [cat:rendering] | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-07-20 16:02:10 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Juergen Wieczorek
2011-07-02 11:52:25 UTC
P.S.: though the desktop (KDE) is running with 1280x1024, I can push any window outside the viewable area over the left margin, but this may be a KDE related bug. 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. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 511030 [details]
dmesg output
Created attachment 511031 [details]
messages output
Created attachment 511032 [details]
new Xorg output
(In reply to comment #1) > P.S.: > though the desktop (KDE) is running with 1280x1024, I can push any window > outside the viewable area over the left margin, but this may be a KDE related > bug. Seems to be related to this bug, as I can push a desktop window outside the viewable area on the left screen border only in the 0-800 pixel range. (In reply to comment #6) > (In reply to comment #1) > > P.S.: > > though the desktop (KDE) is running with 1280x1024, I can push any window > > outside the viewable area over the left margin, but this may be a KDE related > > bug. > Seems to be related to this bug, as I can push a desktop window outside the > viewable area on the left screen border only in the 0-800 pixel range. P.P.S.: It has gotten worse on the desktop. Desktop apps start outside the viewable area and I have to drag them manually back to the viewable area or pin them by setting fixed window position values. I have switched back to F14 until this mess is over. Damn, I should have taken a closer look. There are Wrongly two displays detected on my py 1 = LVDS1 with 1024x768 (my asspumption of 800x600 was wrong) 2 = DVI1 with 1280 x 1024 I can disable LVDS1 at KD session start, but it is not permanent and has to be renewd with each log off. This bug is most certainly due to the fact that the display is connected via a combined vga+dvi plug This has already happenend in the past with F12 or F13. It's crap reloaded pt. II & II & IV, ad infinitum. Kernel mode setting is a mess with Fedora. (In reply to comment #8) > Damn, I should have taken a closer look. > There are Wrongly two displays detected on my py > 1 = LVDS1 with 1024x768 (my asspumption of 800x600 was wrong) > 2 = DVI1 with 1280 x 1024 > I can disable LVDS1 at KD session start, but it is not permanent and has to be > renewd with each log off. Why do you think LVDS should be disabled? > This bug is most certainly due to the fact that the display is connected via a > combined vga+dvi plug Why do you think this is relevant? (In reply to comment #9) > (In reply to comment #8) > > Damn, I should have taken a closer look. > > There are Wrongly two displays detected on my py > > 1 = LVDS1 with 1024x768 (my asspumption of 800x600 was wrong) > > 2 = DVI1 with 1280 x 1024 > > I can disable LVDS1 at KD session start, but it is not permanent and has to be > > renewd with each log off. > > Why do you think LVDS should be disabled? Because I amnot working on a laptop but on a small form factor pc. There is no internal display, only an external one. > Why do you think this is relevant? Because the combined DVI-I connector only throughs Fedora off track. It has never happened with Debian or Ubuntu, which I have/had installed on this system too. Meanwhile I did a parallel install of Debian-testing (xorg-7.6 with intel-2.15) and am having the same problems with this 'phantom' LVDS display being detected. It seems to be an Intel driver issue and is not Fedora related. We filed this bug in the upstream database (https://bugs.freedesktop.org/show_bug.cgi?id=39404) and believe that it is more appropriate to let it be resolved upstream. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. We would strongly encourage you to subscribe to the upstream bug as well (by logging in and adding yourself to the Cc list), so that you can provide whatever information required for the successful resolving of this issue. Thank you for helping to make free software better. Just in case: the Intel recommended workaround for this situtation is to add "video=LVDS-1:d" to the kernel line, to disable LVDS at boot, but have KMS still working. Situation is back to normal now. |