Description of problem: When booting from the Fedora 12 KDE Beta Live CD with KMS enabled it results in strange artifacts and wrong displaying of colors which can be seen in the attached screenshots. When disabling KMS with the nomodeset option, everything is displayed as normal. The KDM splash is displayed without problems. This problem does only occur in KDE an Qt applications, but not in Gtk applications (like the nm-applet) or the GNOME desktop. How reproducible: Boot Fedora 12 Beta Live CD with KDE and KMS enabled. Steps to Reproduce: 1. Insert disc 2. Boot from CD 3. Try to use the desktop. Actual results: Strange artifacts and colors Expected results: A normal KDE desktop Additional info: -I am using the radeon driver with an ATI Mobility Radeon HD 2600 XT - Restarting the X-Server, logging in again or switching to ttys and back to X does not help -The attached logs with the .normal suffix are the ones with KMS enabled, the ones with .nomodeset have KMS disabled
Created attachment 366335 [details] dmesg with KMS enabled
Created attachment 366336 [details] Xorg.0.log with KMS enabled
Created attachment 366337 [details] Xorg.0.log with KMS disabled
Created attachment 366338 [details] Smolt profile
Clearly a driver bug, reassigning.
Do you still have this issue with a more recent kernel and xorg-x11-drv-ati ?
I tried it with the latest Rawhide nightly build (kde-i386-20091103.16.iso) and nothing has changed as far as I can see. I also uploaded the screenshots to this directory: http://julian.fedorapeople.org/foo/reports/531348/ They were all taken without changing any options, always using the default "Air" theme.
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.]
This was tested with the Rawhide nightly build from 3rd November (kde-i386-20091103.16.iso)
Jerome: Hi, I've added myself to cc-list because I'm facing the same problem, but you've recently changed the summary to match only HD2600. I have HD 4570 card. 1) should I file another bug? or this card (r700) is not expected to work yet? 2) is output of rendercheck useful for these kind of problems?
Michal, i will test again KDE on R600/R700 hw see if i can reproduce, i generalized bug title because i believe you are experiencing same bug as Julian.
There is nothing to triage here. Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
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
*** Bug 537546 has been marked as a duplicate of this bug. ***
*** Bug 536779 has been marked as a duplicate of this bug. ***
Having same issue on HD3470. No problems in Gnome whatsoever, but artifacts in KDE. I'll happily test experimental builds of Qt, kernel, mesa-dri-drivers-experimental or KDE rpms if that is needed.
Is there any further information needed to help squash this bug?
*** Bug 540050 has been marked as a duplicate of this bug. ***
Does kernel -149 or newer helps ?
Created attachment 374060 [details] Screenshot showing rendering errors Example of rendering errors w/ kernel -151
Forgot to add a proper comment an the attachment screen... I tested with -151 and see improvement, but not (yet) perfection. The weird box effects - shown in comment #7 - are gone, but in it' s place are lines trailing a window when dragging. See the screenshot linked in #20 for an example. The previewer widget shown in the screenshot shows what seems to be a rendering error too (the box around the icon), but this is also there when KMS is disabled. I don't think it is related to this bug.
I can confirm comment #21 , same here. Displaying without desktop effects seems to work pretty well now though. Everything gets displayed correctly with desktop effects disabled as far as I can see (a minor glitch in XChat was the only thing a noticed).
I retested with a rawhide nightly build (kde-i386-20091227.19.iso) and it is all working flawlessly now with KMS enabled. Problem fixed at least for me (Radeon HD 2600)
I saw the behaviour resembling that pictured in #7 when I first installed F12 on my machine. When I installed mesa-dri-drivers-experimental and enabled compositing, those problems were largely fixed (though KDM still shows incorrect colouring in menus, presumably because it isn't running under compositing...). However, with compositing enabled I see the glitches when dragging Kwin windows, similar to those that are illustrated in #20. I suggest we might actually be seeing two different bugs here, so it might be useful for reports to note whether they're using the experimental DRI drivers package and / or compositing enabled under KWin (or if using another WM). FWIW I'm running with KMS enabled on kernel 2.6.31.9-174.fc12.x86_64
Mark, considering the title, this bug should be about rendering problems in KDE with KMS *enabled*. I am assuming everyone reporting here has KMS enabled for what they are describing.
Afaik Mark is talking about composition (3d drivers - mesa-dri-drivers-experimental) and not about KMS. Also this is known that when compositing is used, there are less (or none for happy users) graphic problems.
Although I did confuse things by redundantly mentioning I was using KMS enabled, my main point was indeed that some people here seem to be referring to bugs I see without compositing whilst others are showing bugs I only see with compositing. I think the graphical glitches left by moving windows are likely to be a different class of bug, only seen under compositing. In which case I wonder if they'd be better reported under mesa-dri-drivers-experimental or kwin so that they reach the right maintainers? I've done some more investigation into the artefacts left when moving windows. Having shadows switched on reduces the appearance of these artefacts enormously. Switching on wobbly windows reduces them even more. I've done this for a workaround (and it looks cool) but obviously it would be nice to resolve this as it's really the only troublesome glitch I'm now seeing in the (admittedly experimental) 3D support for desktop use (3D games often crash the X server but that's definitely unrelated to this bug report!).
Same thing happens to mee, too. I have an Toshiba A300. #lspci 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 06:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 06:06.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 06:06.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 06:06.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) Stock xorg.conf, desktop effect working only with mesa-dri-drivers-experimental
I updated to the latest driver today (version 7.7-2) The bugs seems completely fixed, the better test case I found is using the gimp (more precisely the cutter tool). It works perfectly. Thank you!
Confirmed: Artifacts fixed. The fact that my laptop now crashed every other minute is another bug, I suppose :P
Fixed for me too. I have installed a fresh F12+updates and it's OK.
Not working for me. The screen freezes after login in kdm. Kernel shows a bug handling NULL pointer defererence. ATI Technologies Inc Mobility Radeon HD 3650 Kernel 2.6.31.12-174.2.3.fc12.x86_64 mesa-dri-drivers-experimental-7.7-3.fc12.x86_64 mesa-dri-drivers-7.7-3.fc12.x86_64 xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12.x86_64 xorg-x11-server-Xorg-1.7.4-1.fc12.x86_64
Created attachment 387865 [details] Kernel crash after KDM login Kernel crash after KDM login
seems to be fixed (or at least significantly improved) for me (no crashes so far), but it's broken again when I use kernel 2.6.32.7-37.fc12 from updates-testing. Is it going to be broken with every new kernel or is it just a coincidence some problems are (more) visible with one kernel than with another one?
Most likely all the fixes didn't make their way into 2.6.32 ...
Is there any way I could download a Live CD that contains the updated packages? I want to try if it works before reinstalling. 10q
(In reply to comment #36) > Is there any way I could download a Live CD that contains the updated packages? > I want to try if it works before reinstalling. Yes, the latest packages can always be fetched with the Rawhide KDE nightly spin over here: http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ Just download the i386 (or x86_64) iso in that folder and try it. It will be the latest successful build.
(In reply to comment #37) > Yes, the latest packages can always be fetched with the Rawhide KDE nightly > spin over here: http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ Just to emphasize that this is Rawhide, so don't use it for production computers unless you REALLY know what you are doing. For testing it is fine, of course.
Now its working fine for me. ATI Technologies Inc Mobility Radeon HD 3650 kernel-2.6.31.12-174.2.19.fc12.x86_64 xorg-x11-server-Xorg-1.7.4-6.fc12.x86_64 xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12.x86_64 mesa-dri-drivers-experimental-7.7-3.fc12.x86_64 mesa-dri-drivers-7.7-3.fc12.x86_64 Kde 4.4.0 now from kde-testing. The other post was kde 4.3.x
It's working for me too but with a little observation: If I watch with a lot of attention I see some flickering on the display, like some pixels appearing and disappearing very fast, like a small noise.
I guess this can be closed now, or is anyone still experiencing this on F13?
I think so too.
Me is fixed :)
Ok closing