Bug 567208
Summary: | KMS:RV635:HD3650 Thinkpad W500 LVDS broken when docked with DVI monitor | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nigel Jones <bugs> |
Component: | xorg-x11-drv-ati | Assignee: | Jérôme Glisse <jglisse> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | ehicks, jglisse, mcepl, xgl-maint |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | card_R600/mM | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-03 22:30:53 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: |
Additional notes: * other than the desktop issue the system is working (ie remotely) normally - no cpu spins etc * Following a reboot I notice the flickering always occurs on the primary panel (LVDS) whenever the DVI pabnel is active * The primary LVDS remains rather unresponsive (not as bad as 8s for the login screen, but just "wrong"). About to re-install the older kernel. 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 config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and system log (/var/log/messages; most of the activity is now in kernel, which is not covered by /var/log/Xorg.0.log) 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 395540 [details]
xorg log file from boot with DVI attached
Created attachment 395546 [details]
messages from a dvi boot
Created attachment 395548 [details]
kernel "dmesg" from boot attempt with dvi attached
Do the new attachments give you what's needed? still occurs with -70 2.6.32 update Seeing this on HP EliteBook 8530p as well. Attaching dmesg.gz & messages.gz - xorg.conf doesn't exist as it's a stock Fedora 12 setup using evdev. -70 update seemed to fix the LVDS problem I was seeing (so at least I can see *something* now when it's docked) but not output to the DVI via the dock. Dock DVI didn't work quite right under .31 either as the LUKS password screen would disappear after the 1st keypress but I would only rank that as "mildly annoying". Another suggestion I have would be to default to mirror mode at the GDM login prompt as there's no reason for split-screen at that stage and the default currently pushes the login prompt window over to the LVDS which, when docked and closed lid, is not visible. Thanks Created attachment 399148 [details]
HP EliteBook 8530p boot with 32-70 kernel - dmesg
Created attachment 399149 [details]
HP EliteBook 8530p boot with 32-70 kernel - messages
I'm no longer running F12, instead am using F13 alpha. I've installed the latest 2.6.33 kernel & radeon driver. Indeed on F13 the very latest driver appears to have made things worse, with the LVDS screen being unreadable when the system is booted DVI attached (W500, ati) Should I raise a seperate F13 report, modify this one, or just leave as-is. Booting with KMS disabled works better - until I want to suspend/resume :-( - so it looks like a kernel KMS issue introduced with -32 & -33 kernels (it was ok in -31) This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. |
Created attachment 395442 [details] xorg log file Description of problem: I have a thinkpad W500 with ati/radeon switchable gfx running F12 x86_64 with updates. The system is configured for discrete gfx (ati) I tried out the .32 kernel for - any improvements in acceleration on the V5700 - btrfs improvements - to see how .32 kernel was going (thinking of f13 alpha/beta) Version-Release number of selected component (if applicable): kernel-2.6.32.8-58.fc12.x86_64 xorg-x11-drv-ati-6.13.0-0.21.20100219gite68d3a389.fc12.x86_64 xorg-x11-server-Xorg-1.7.5-1.fc12.x86_64 (was using 1.7.4 then tried this to see if it made any difference -- it didn't) KMS is enabled Today I booted the system with ATI. On a single screen it was working fine. I suspended, traveled to office, resumed upon which time * Initially the regular login screen came up on the LVDS panel, but was somewhat unresponsive with increasing amount of flickery lines * The DVI panel powered up, but remained black * The LVDS screen faded until it was black with noise * I was able to flip to VT just fine * Flipping back to X the screen has a vague shadow of some old windows (behind a magenta stripey veil), which then gets overwritten by the login pabel, but with large 1" stripey cyan/magenta lines * Basically the screen is unreadable * I then typed my password and the DVI panel came up fine with my background * My primary panel then "drew" over about 8s - basically any change to the screen takes this long -- just moving the mouse. Eventually the picture renders clean, but is unusable. * Can't see anything particularly interesting in dmesg/Xorg.log The older 2.6.30 kernel was working fine (and I will revert to it now) Happy to try any other test you suggest. Will likely switch to F13 somewhere between alpha and beta, especially as I'm interesting to check out how the ati gfx is performing, and look at any progress on the switchable gfx (even if X has to be restarted) How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: