Bug 84582 - NV11 hardware cursor broken, use swcursor by default instead
Summary: NV11 hardware cursor broken, use swcursor by default instead
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-02-19 05:53 UTC by Mike A. Harris
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-24 19:50:16 UTC

Attachments (Terms of Use)

Description Mike A. Harris 2003-02-19 05:53:02 UTC
A user in IRC reported that the hardware cursor on Nvidia GeForce 2 MX
is showing double cursor images, that go away with swcursor.

The chip is:

<Aether> 02:00.0 Class 0300: 10de:0110 (rev b2)
<Aether>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-

The cursor code in "nv" driver should be changed to default to swcursor
for all NV11 hardware for future erratum.

Comment 1 Mike A. Harris 2003-02-19 06:00:23 UTC
Note, he also indicated that 4.2.1-11 continues to have this problem.

Comment 2 Mike A. Harris 2003-02-20 01:29:37 UTC
This problem is currently only potentially planned for RHL 8.0 and 7.3
erratum.  Confirmation of the problem in 4.3.0 would be required before
making the change there though.  If anyone can test 4.3.0 with NV11
and confirm/deny here, that'd be appreciated.

Comment 3 Mike A. Harris 2004-09-24 19:50:16 UTC
I don't have NV11 hardware, so can't really test this.  It should
be filed in X.Org if it's still an issue I guess.  Someone with
the hardware would have to confirm that, and file it in X.org
bugzilla however, as we've no way to confirm.

Closing "WONTFIX"

Comment 4 Mike A. Harris 2004-09-24 20:02:48 UTC
If anyone experiences this with Fedora Core 2 or later, please
feel free to file a bug in X.org bugzilla and we'll track it
if you provide the URL.  http://bugs.freedesktop.org

Note You need to log in before you can comment on or make changes to this bug.