Bug 15920

Summary: [mach64] ATI Mobility M1 -- the mouse cursor garbles some underlying pixels
Product: xorg Reporter: Bryce Harrington <bryce>
Component: Driver/mach64Assignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium Keywords: NEEDINFO
Version: 7.3 (2007.09)   
Hardware: Other   
OS: All   
URL: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/194521
Whiteboard:
i915 platform: i915 features:

Description Bryce Harrington 2008-05-13 01:27:46 UTC 
I'm forwarding a bug from a Ubuntu user:

"Using -ati 6.8.0 on Sony with ATI Mobility M1

I observe a line of garbled pixels under the mouse cursor, for example on the initial login screen, and then they stay there no matter what is redrawn, like that they are "burned in". Moving mouse cursor keep these pixels on the initial location, and doesn't produce new, until something happens, when the "burned in" pixels appear somewhere else, but again under the current place of the cursor.

The effect never happens in Vesa mode. Here's conf:

Section "Device"
 Identifier "Generic Video Card"
 Boardname "ATI Rage Mobility"
 Busid "PCI:1:0:0"
 Driver "ati"
 Screen 0
 Vendorname "ATI"
 Option "MergedFB" "off"
EndSection

now, from all the observations, I'm quite sure that it's drawn by the same mechanism that draws the main "hardware cursor", and that what I see must be a second "hardware cursor" which "show flag" is unintentionally activated by some initialization and reinitialization procedure.

http://launchpadlibrarian.net/14062548/Xorg.0.log
http://launchpadlibrarian.net/14062622/SecondCursorDrop1.jpg
http://launchpadlibrarian.net/14062647/SecondCursorDrop2.jpg
Comment 1 Alex Deucher 2008-05-13 05:35:21 UTC 
Switching component.  M1 is mach64 based.
Comment 2 Matt Turner 2010-12-03 12:23:19 UTC 
Is this still a problem?
Comment 3 Adam Jackson 2018-06-12 19:10:18 UTC 
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.