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 471537
| Summary: | Serious problem with rendering | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Lisý <pavel.lisy> |
| Component: | xorg-x11-drv-i810 | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10 | CC: | bughead, gordon.messmer, idht4n, imc, jryden, kk_konrad, lpierfederici, masao-takahashi, mcepl, mnowak, moneta.mace, oxben, pali, wally, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-20 10:21:46 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: | |||
|
Description
Pavel Lisý
2008-11-14 06:37:08 UTC
Created attachment 323538 [details]
rendering problem of intel 810i driver
I found workaround but it is not solution. When you set from menu: System -> Preferences -> Look and Feel -> Appearance Tab: Fonts, Rendering: Subpixel smoothing (LCDs) and then I can see whole font letters again. I don't know how can I change this for login screen (GDM) But some rendering problems are still there. I.e. when I switched to different tab in Appearance dialogue I didn't see icons of themes. But this happens only sometimes. You need switch with keyboard (Ctrl-Tab) instead of mouse click to see it 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) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 323660 [details]
/etc/X11/xorg.conf
Created attachment 323661 [details]
/var/log/Xorg.0.log
same problem here. see screenshot at bug 461829 comment #40-42 Thanks, Konrad Created attachment 323668 [details]
/var/log/Xorg.0.log, Without config
with Option "AccelMethod" "XAA" I dont have font corruption so far. X w/o xorg.conf seems to select EXA. (Intel Corporation 82865G Integrated Graphics Controller (rev 02)) Greetings, Konrad I can confirm it. With this option rendering and redrawing is OK. But system-config-display didn't set it. This can be serious problem for many users. I have the same problem. The "intel" driver with AccelMethod XAA works without corruption AFAICT. The i810 driver doesn't work at all... says "No screens found" when I select that driver from system-config-display. The vesa driver works without corruption. Here is the smolt profile for this system: http://www.smolts.org/client/show/pub_f24c96f9-7884-4d14-a298-63a2847d0c0e This system works fine with i810 and vesa in fedora 8 and X crashed frequently in fedora 9 (https://bugzilla.redhat.com/show_bug.cgi?id=449460). Do other people see the "no screens found" problem with i810? After today's updates the "intel" driver appears to work without having to set Option "AccelMethod" "XAA" manually. I have the 82852/855GM card in a Dell Latitude 505 laptop. Desktop effects do not work though and just produce a white screen before reverting. I can confirm David's observation that the i810 driver doesn't work at all and just give a "no screens found" Pavel? Could you confirm comment 12? Could we close this bug? I can confirm it. It is working now without Option "AccelMethod" "XAA". Has X been changed so that it selects XAA by default or has EXA made working? (did not try w/o xorg.conf) Yesterday I tried EXA (selected in xorg.conf) for a few seconds only and observed something: When typing in one long line of text in KDE konsole some amount of the already typed characters got displayed somewhat more or less bold. Difficult to explain, they were not in real bold font but they changed their perceived grey level somewhat while typing. Using XAA there was no such effect. The font corruption (only parts of characters visible) did not happen yesterday. Created attachment 324252 [details]
screen shot to demonstrate "boldness" of characters
see the bottom line. it got more black after entering some 'd' s.
I am experiencing the same problem as Konrad, having 82852/855GM graphics. EXA being auto-on. One can see it in rxvt (whole lines) and thunderbird (beginnings of lines). Not sure about XXA. But the former rendering problem is fixed. Created attachment 324294 [details]
Image after mouse moved down
Created attachment 324295 [details]
Image after mouse moved up
I am confirming problem with "boldness" of characters. It is changing even if I move with move over window. I've sent two images. You can see difference in one line, but it was the same on all lines before I've made these screenshots. (removing the needinfo flag, we received Pavel's feedback) This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I also see the problem with "boldness" of characters. And also, I've: - some random graphic corruptions on gtk controls (button) when I move my mouse over them. (They can't be captured, They don't appear on screen capture) - graphic corruptions in windows menu bars in the form of series of white characters (often 'F') appearing above the menu bar when the window opens. See attachment below. Intel chipset 82865G. Driver: i915? How do you determine the "AccelMethod" used by the driver? Created attachment 324871 [details]
Menubar corruption
Here is the kind of graphic artifact I get on menubar very often when a new window is opened.
Following the advices from the comments above, I have: * Installed system-config-display to generate a xorg.conf file * Added Option "AccelMethod" "XAA" * Restarted X Tada! No more display artifacts and font rendering looks a lot better. Thanks for the tips. I still can't use Compiz or any apps the require 3D-accelerated OpenGL but I think it belongs to another bug report. (In reply to comment #16) > Created an attachment (id=324252) [details] > screen shot to demonstrate "boldness" of characters > > see the bottom line. it got more black after entering some 'd' s. My bug (473140 https://bugzilla.redhat.com/show_bug.cgi?id=473140) seems to be the same like this one. *** Bug 473140 has been marked as a duplicate of this bug. *** I have tried a unstable git version of xf86-video-intel-2.6.99 from git server of freedesktop. The newest version of xf86-video-intel seems to resolve this problem. No bold face and no artifacts. Created attachment 330743 [details]
another corrupted screenshot
About 80% of the way down the screen there is corruption.
xorg-x11-drv-i810.i386 2.5.0-4.fc10
Created attachment 330745 [details]
another screenshot with some bold characters
About 55% down the screen, there is a line with noticeably bolder characters
than those on adjacent lines.
Created attachment 330746 [details]
yet another form of screen corruption
While I was using eog to look at an earlier corrupt screen shot, I noticed a bunch
of vertical tick marks below the menu bar. They went away after I forced a refresh.
For what it's worth, installation of f11 alpha had horrible screen corruption problems. I didn't get through more than a few screens before my computer hung completely, but it was obvious that f11 still has major problems with intel graphics support. On a somewhat related question, how active is the development of this driver? Ever since fedora 6 (when the driver worked flawlessly), I've had nothing but trouble with this graphics card (which came with my IBM ThinkCentre). I've reported and watched several bugs, but several have been ignored and others have not been fixed. I've easily wasted $400 of time reporting bugs, trying workarounds, etc. Should I just get my company to buy a $100 Nvidia or ATI graphics card and punt on Intel? I'm willing to try a few more things to provide feedback on f10 or f11 alpha, but I'd like to know that it's actively being worked on. FYI - I filed a new bug report for the f11 alpha intel X corruption and hang: https://bugzilla.redhat.com/show_bug.cgi?id=484276 vesa works without corruption in f10 and works without the corruption and the X hang in f11. Yup, I have the random changes-in-boldness of fonts when typing into an input field too, and Accelmode XAA fixed it (as well as making glxgears seem to go a bit faster). Unfortunately there's now occasional stray lines on the screen when I move windows around - it's a case of which is the worst of two evils... xorg-x11-server-Xorg-1.5.3-15.fc10.i386 xorg-x11-drv-i810-2.5.0-4.fc10.i386 Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, including Intel driver, which may have resolved this issue. To be more precise, Intel has undergone a major rewrite during Fedora 10, 11 and 12 cycles, and whole driver is working a lot better now. Users who have experienced this problem are encouraged to retry with at least Fedora 12 Beta and see if the issue is still relevant. Please, if you experience this problem on Fedora 12 Beta or up-to-date system running Rawhide, 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. We hope to see how many older bugs in Intel driver are still relevant today, in hope that most of them were fixed in rewrite process. [This is a bulk message for all open Fedora 10 i810-related bugs (39 of them are still open). 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 message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 I think it's safe to say that this isn't an issue on F12, thank goodness for small mercies. (Neither the font corruption nor the random stray lines have appeared so far in testing.) Thank you for letting us know. |