Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 504540
| Summary: | Graphics corrupted on Fedora 11 (preview) KDE Live CD | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard Cavell <richardcavell> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | fedora, fedora, gort.klaatu, itamar, jreznik, kernel-maint, kevin, lorenzo, ltinkl, rdieter, smparrish, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-26 17:06:07 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: | |||
|
Description
Richard Cavell
2009-06-08 02:51:43 UTC
This is more likely a KDE/X/Intel issue than only related to the live images. So I'm re-assigning it to kdebase-workspace first, to get some more KDE folks in. In the meantime: Could you please try to boot the live image with the boot option "nomodeset"? (Press tab at the boot menu and enter nomodeset there, then press enter) Looks like an Intel KMS (kernel modesetting) bug to me, the corruption starts even before X11 is started. As this is the preview, it may already be fixed though. I'd suggest trying the final release tomorrow. (The release is already made, it's being mirrored as we speak, so waiting that one more day before doing more testing won't change how and when this will be fixed.) Hi, guys. I booted the Live Preview and entered the nomodeset option, as requested. (there were many other options on the command line and I just added it) It stated in text: couldn't find an input interrupt endpoint, with some additional text. I'll have to reboot a few times to capture the text if you want me to. Now the screen enters what is obviously a text mode. Three status bars crawl from left to right and I have 'Fedora 10.92' in the lower right hand corner. Then I boot into KDE. I am now typing this within Konqueror. (By the way, I got a couple of errors in '/home/liveuser/.local/share/akonadi/db_data/mysql.err' while booting from the Live CD. Should I be worried about this?) So thanks for fixing it... BUT! Today I downloaded the final version (not the preview). Fedora 11, KDE Live disc. And it's back to its old tricks. I tried entering nomodeset. memtest was the default option, and I just deleted that and entered nomodeset. It did no good. Now that I now what the splash screen is supposed to look like, I confirm that it definitely bugs out somewhere in the splash screen. I get a corrupted mouse pointer, which can still be moved around, and a corrupted splash screen, and a corrupted wavy-line-that-is-supposed-to-tell-you-the-progress. Yet, I can still cause it to react to me in some ways. I can press my power button and it does a little disk activity, implying that it's still working in some way. But it won't leave the splash screen and it won't give me the KDE desktop. Richard By the way, is this related to Bug 488824 or bug 505058? It looks like Fedora is having a bad trot with the Intel GMA 950 chipset. Richard I am also seeing this bug on my Macbooks. (In reply to comment #5) > I am also seeing this bug on my Macbooks. Klaatu, can you confirm that the preview works for you with nomodeset and the final release does not work, whether nomodeset or not? Richard We have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. |