Bug 808710
| Summary: | llvmpipe driver doesn't render correctly on Dell Inspiron Mini 10 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jiri Eischmann <eischmann> | ||||||||||
| Component: | mesa | Assignee: | Adam Jackson <ajax> | ||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | ajax, mishu | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-04-09 18:13:39 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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 752650 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 574160 [details]
Screenshot of the problem
I think this will affect all users with GMA500 and similar cards which is why I'm proposing it as a blocker bug for Fedora 17. Created attachment 574191 [details]
Incorrect rendering in KDE
(In reply to comment #0) > Expected results: > Correct rendering via llvmpipe or blacklisting the driver and using another > driver, Poulsbo should have a working driver in kernel 3.3, right? Poulsbo has a driver in 3.3, yes. The question is whether it works. Do you see this corruption if you use forced-fallback mode in gnome? If so then this isn't llvmpipe's fault. You can set forced fallback in the System Info control panel, in the Graphics subsection. (In reply to comment #4) > (In reply to comment #0) > > Expected results: > > Correct rendering via llvmpipe or blacklisting the driver and using another > > driver, Poulsbo should have a working driver in kernel 3.3, right? > > Poulsbo has a driver in 3.3, yes. The question is whether it works. > > Do you see this corruption if you use forced-fallback mode in gnome? If so > then this isn't llvmpipe's fault. You can set forced fallback in the System > Info control panel, in the Graphics subsection. llvmpipe is used only when there is a compositor with "3D effects"? Because it was pretty much the same in KDE and Xfce which don't use 3D effects in Fedora by default. What is used then? Vesa or the Poulsbo driver in this case? I'll get back to that computer on Friday. Created attachment 575163 [details]
Xorg log
I looked at it today again. I tried to log out and in GDM the screen wasn't suddenly broken any more. When I logged into fallback mode, it worked, too. When I enabled GNOME Shell again and logged into it, it worked, too. Yes, the performance is horrible, but what else to expect from a netbook and software rendering. I will look at the PSB-GFX driver if it works well at least for 2D. Anyone knows what the driver is capable of in kernel 3.3? The psb driver in 3.3 is unaccelerated. Since it sounds like rendering is correct now I'm closing this out. Thanks for the report. |
Created attachment 574159 [details] Smolt profile Description of problem: Software rendering doesn't render properly on Dell Inspiron Mini 10. There are artefacts in both upper corners and there is a black bar on the bottom of the screen. It doesn't seem to be specific to any desktop environment. It behaved pretty much the same both in GNOME Shell and Xfce (tested on the build for soft-rendering test day) How reproducible: Just boot into one of display managers Actual results: Broken rendering Expected results: Correct rendering via llvmpipe or blacklisting the driver and using another driver, Poulsbo should have a working driver in kernel 3.3, right? Additional info: I'm attaching a smolt profile and screenshot.