| Summary: | The desktop shows graphical artefacts when moving the cursor an dragging windows. | ||
|---|---|---|---|
| Product: | xorg | Reporter: | presidentnotsure.eo |
| Component: | Driver/intel | Assignee: | Chris Wilson <chris> |
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | major | ||
| Priority: | high | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
presidentnotsure.eo
2017-05-25 19:57:20 UTC
The HW cursor fails and is replaced by a swcursor (due to an issue in the display hardware) that is being mishandled by the compositor. The delay in rendering is due to a bug in mesa. To avoid the swcursor fallback, don't use pipe 2. Something like "xrandr --output HDMI2 --preferred --pipe 0" should do the trick. Still bizarre that an earlier application chose to configure it on pipe 2. $ xrandr --output HDMI2 --preferred --pipe 0 xrandr: unrecognized option '--pipe' (In reply to presidentnotsure.eo from comment #3) > $ xrandr --output HDMI2 --preferred --pipe 0 > xrandr: unrecognized option '--pipe' The option would be '--crtc 0'. Unfortunately it's not going to help because only pipe C (ie. crtc 2) can drive the HDMI output (port D). -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/141. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.