Hide Forgot
Description of problem: Perhaps 1 out of 20 bootups produces "shaky" output on my laptop, the display is basically unreadable, shaky, I see the mouse pointer in two different places, top bar might be in the middle of screen, etc. I'll attach X.org.log/dmesg/vbios.rom on both ok and shaky display. Version-Release number of selected component (if applicable): Fedora 15 + updates as of Jun 2.
Created attachment 502599 [details] xorg.log - ok
Created attachment 502602 [details] dmesg - ok
Created attachment 502603 [details] vbios.rom - ok
Created attachment 502605 [details] xorg.log - shaky
Created attachment 502606 [details] dmesg - shaky
Created attachment 502607 [details] vbios.rom - shaky
Taking the liberty to CC Alex who seems to be very active in upstream. Pardon me if this in inappropriate.
Hi Daniel, Apologies for the delayed response on this report, I was reviewing this bug, and based on the vbios.rom attachments I noticed the Power Cable not attached error message. Due to the age of this report I wanted to touch basis and see if this error is still persistent upon applying recent updates (either hardware or Fedora Software)? If so, this error may be related to a power feed issue to the Radeon graphics card itself...if the required power cable is properly connected to the Radeon card either the power supply may not have sufficient wattage to meet the card requirements or may be failing. If this error still occurs, please feel free to response to this inquiry on Bugzilla and I'll be happy to triage this bug for further review. Thanks! --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi Jason, thanks for looking into this. I'm not sure why vbios.rom says Power Cable not attached as I've certainly generated all the logs with the cable attached and I also see this issue with the cable attached. This issue is also present on F17 + 3.3 kernel, occurring irregularly as before. But to be honest I'm not sure how much effort we should put into resolving this as my laptop is a 5 years old model and if I'm the only person affected perhaps I can simply acquire a new laptop and we could consider the issue solved. But of course if someone sees something obvious in the logs I'd be happy to test any patches you might provide. Thanks.
Hi Daniel, I appreciate the repsonse, upon review of attached captures and reporter confirming bug continues to exist, marked report as Triaged for additional review. Thanks! --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.