Description of problem: Garbage on screen during boot of 9-9 test day ISO on T60p with multihead Version-Release number of selected component (if applicable): 9-9 test day ISO How reproducible: Always Steps to Reproduce: 1. Boot off 9-9 ISO CD on ThinkPad T60p with two monitors attached 2. 3. Actual results: Garbage just before X screen shows. There are strong horizontal black lines and vertically-patterned white noise. After a few seconds the login screen appears normally. Expected results: No display garbage. Additional info:
I suspect this is KMS-related, but to be sure, can you test booting with 'radeon.modeset=0' kernel parameter and see if it happens there too? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I will do so shortly. I'm also getting similar garbage appearing when coming back from suspend in F11 (both multihead and singlehead). I wonder whether it is related.
Several tests using the Snap 2 ISO: 1/ Single head with radeon.modeset=0: Crawl comes up in low-res, as expected. No garbage appears. 2/ Two heads with radeon.modeset=0: Crawl comes up in low-res on both monitors, as expected. No garbage appears. 3/ Two heads without the parameter: Crawl comes up in high-res on both monitors, as expected. About five seconds of garbage on both monitors. 4/ Single head without the parameter. Crawl comes up in high-res, as expected. No evidence of garbage.
right, about what I expected. thanks. kernel is technically the right component, but the devs prefer KMS bugs to be assigned to the X driver, it's easy to track. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 522690 has been marked as a duplicate of this bug. ***
*** Bug 522698 has been marked as a duplicate of this bug. ***
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
*** Bug 523062 has been marked as a duplicate of this bug. ***
Issue is that we get crtc set mode with null fb which seems somethings we allow. What we need is to force to black all output when we get such request. Can you test patches against Dave's drm-next linux free ? Or do you prefer rpm ? (rpm tooks me longer to build).
I can test it on Radeon 9550 and Radeon IGP 330M/340M/350M. I only test with live images - so I can test only rpms.
Just a short question: Why is it either garbage or blanking the framebuffer? Is there really no way how to make the transition smooth (keeping the image generated by Plymouth intact) even in multi-head configuration (as it worked in F11)? I understand that there have been some changes in the KMS infrastructure since F11, but these changes should make it actually easier (since the Plymouth draws the image on each head separately now, it is not cloning the output in hardware). Even without this, if you can blank the framebuffer, you can also quickly blit the correct image there. Or am I totally mistaken?
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Well, the previous question on this bug is from me in comment #11, but nobody bothered to answer. BTW: The bug is still present in an updated Fedora 12 in dual-head KMS configuration as of 2010-02-26.
I am also still getting garbage on my T60p when an external monitor is attached (currently a Dell Trinitron monitor). The visuals during boot are: Boot "Visuals" Time after Poweron No External Monitor Thinkpad Screen 3 sec Black Screen 5 sec Fedora animated "balloon" 12 sec Login Screen 28 sec External Monitor (Dell Trinitron) Thinkpad Screen 3 sec Black Screen 5 sec Fedora animated "balloon" 12 sec Black Screen 28 sec Garbage Screen 30 sec Login Screen 32 sec - external monitor "resets" several times during process This is under kernel 2.6.31.12-174.2.22.fc12.i686 and Gnome.
This bug is still present with desktop-i386-20100418.17 on Radeon 9550.
Also present with desktop-i386-20100418.17 on Radeon X1600Pro.
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
This problem is still persisting when booting from an F14 live USB stick. If anyone cares, I can do some more investigation after I return from travelling.
Please try the latest rawhide kernel (2.6.37-rc5) and let us know if its fixed there (and upstream.) regards, Kyle
Is there a live "CD" for rawhide at the moment? Alternatively, is there an easy way to install rawhide from scratch? (I'm a bit leery of using a rawhide kernel on a production machine.)
http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ (but I'm having no problem running rawhide kernels on F14, atm. Well, it breaks sound on this particular laptop. But no permanent damage. :>)
Much better with this kernel. Of course, some of the debugging stuff interferes with a clean video startup, so I can't tell whether everything is completely beautiful. I'll try to participate in the video week tests. Hopefully there will be a non-debugging version of the kernel, etc., for that week so that the boot visuals can be completely checked out.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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