Bug 622052
| Summary: | Intel 82Q35 not working on primary display | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jos Vos <jos> | ||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 6.0 | CC: | jeast | ||||||||
| Target Milestone: | rc | Keywords: | RHELNAK, Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-07-12 18:57:42 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 662543, 842499 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Jos Vos
2010-08-06 21:48:38 UTC
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** This bug can be found upstream here: https://bugs.freedesktop.org/show_bug.cgi?id=29449 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 440407 [details]
dmesg output
Output of "dmesg" when booting (with an additional 1280x1024 monitor connected, besides the primary 1024x768 display that is attached to the system).
Created attachment 440408 [details]
/var/log/messages
Contents of /var/log/messages when booting (with an additional 1280x1024 monitor connected, besides the primary 1024x768 display that is attached to the system).
Created attachment 440410 [details]
/var/log/Xorg.0.log
Contents of /var/log/Xorg.0.log when booting (with an additional 1280x1024 monitor connected, besides the primary 1024x768 display that is attached to the system).
The 3 new attachments are logs from the normal boot situation with "drm.debug=0x04" (and without "rhgb quiet"), where the kernel output at some point switches to the secondary display (I think when modeset is done) and gives a graphical display there. In the meantime I've found a workaround for working with the VESA driver: specify "nomodeset vga=0x318" (without vga=0x318 this is NOT working, as the VESA driver then says it can't find a BIOS table or so) as kernel parameters and create an xorg.conf file specifying the "vesa" driver. Furthermore, I've not found a similar workaround to make a graphical install possible with anaconda using the primary screen. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. The DRM in RHEL 6.3 includes the upstream fix for this issue. |