If you are using Nvidia video hardware with FC5test3 or later, and the mouse cursor is invisible, or has any visible mouse pointer corruption, please add a comment to the following bug report to confirm you are having the same problem, and attach your X server log file as an uncompressed file attachment:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
2 chips have been identified as experiencing this problem so far, so once people have updated the report with any other chips that have the problem, I am going to disable hardware cursors on those chips by default so that things work out of the box in FC5 for as many nv users as possible.
Once the upstream nv driver maintainer fixes the bugs in the driver, we'll update and drop the workaround. For those who want to track the issue in X.Org, the upstream bug is:
https://bugs.freedesktop.org/show_bug.cgi?id=3009
Thanks in advance.
On 2/25/06, Mike A. Harris mharris@redhat.com wrote:
If you are using Nvidia video hardware with FC5test3 or later, and the mouse cursor is invisible, or has any visible mouse pointer corruption, please add a comment to the following bug report to confirm you are having the same problem, and attach your X server log file as an uncompressed file attachment:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
2 chips have been identified as experiencing this problem so far, so once people have updated the report with any other chips that have the problem, I am going to disable hardware cursors on those chips by default so that things work out of the box in FC5 for as many nv users as possible.
I do *not* see any mouse pointer corruption on my system. x86_64 with a 6600 GT. From lspci: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)
The very end tip of the arrow does seem to have one pixel that seems to become about the opposite color of whatever is underneath it; mostly only noticable when the pointer is on a white background. I don't think that is what you are referring to, though : ).
Jonathan
Jonathan Berry wrote:
On 2/25/06, Mike A. Harris mharris@redhat.com wrote:
If you are using Nvidia video hardware with FC5test3 or later, and the mouse cursor is invisible, or has any visible mouse pointer corruption, please add a comment to the following bug report to confirm you are having the same problem, and attach your X server log file as an uncompressed file attachment:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
2 chips have been identified as experiencing this problem so far, so once people have updated the report with any other chips that have the problem, I am going to disable hardware cursors on those chips by default so that things work out of the box in FC5 for as many nv users as possible.
I do *not* see any mouse pointer corruption on my system. x86_64 with a 6600 GT. From lspci: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)
That's not a PCI ID, but a textual description of a video card. PCI ID is 2 32bit hex numbers of the form VENDOR:DEVICE
lspci -vn
It's the numerical value that matters from a programmatical standpoint. If it turns out 2 people have the same device ID, but one has no cursor, and the other works fine, that would be useful information to add to the X.Org bug reprot for the driver maintainer though.
HTH
On 02/26/2006 08:42 AM, Mike A. Harris wrote:
Jonathan Berry wrote:
On 2/25/06, Mike A. Harris mharris@redhat.com wrote:
If you are using Nvidia video hardware with FC5test3 or later, and the mouse cursor is invisible, or has any visible mouse pointer corruption, please add a comment to the following bug report to confirm you are having the same problem, and attach your X server log file as an uncompressed file attachment:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
2 chips have been identified as experiencing this problem so far, so once people have updated the report with any other chips that have the problem, I am going to disable hardware cursors on those chips by default so that things work out of the box in FC5 for as many nv users as possible.
I do *not* see any mouse pointer corruption on my system. x86_64 with a 6600 GT. From lspci: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)
That's not a PCI ID, but a textual description of a video card. PCI ID is 2 32bit hex numbers of the form VENDOR:DEVICE
lspci -vn
It's the numerical value that matters from a programmatical standpoint. If it turns out 2 people have the same device ID, but one has no cursor, and the other works fine, that would be useful information to add to the X.Org bug reprot for the driver maintainer though.
My cursor seems fine too (except for the point described by Jonathan). Added my info and lspci -vn to the bug.
Dariusz
___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
On 2/26/06, Mike A. Harris mharris@mharris.ca wrote:
Jonathan Berry wrote:
On 2/25/06, Mike A. Harris mharris@redhat.com wrote:
If you are using Nvidia video hardware with FC5test3 or later, and the mouse cursor is invisible, or has any visible mouse pointer corruption, please add a comment to the following bug report to confirm you are having the same problem, and attach your X server log file as an uncompressed file attachment:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
2 chips have been identified as experiencing this problem so far, so once people have updated the report with any other chips that have the problem, I am going to disable hardware cursors on those chips by default so that things work out of the box in FC5 for as many nv users as possible.
I do *not* see any mouse pointer corruption on my system. x86_64 with a 6600 GT. From lspci: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)
That's not a PCI ID, but a textual description of a video card. PCI ID is 2 32bit hex numbers of the form VENDOR:DEVICE
lspci -vn
It's the numerical value that matters from a programmatical standpoint. If it turns out 2 people have the same device ID, but one has no cursor, and the other works fine, that would be useful information to add to the X.Org bug reprot for the driver maintainer though.
Ahh, sorry. Here is the info from lspci -vn (looks like the PCI ID is two 16-bit numbers ; ) ): 05:00.0 0300: 10de:0140 (rev a2) Flags: bus master, fast devsel, latency 0, IRQ 12 Memory at e8000000 (32-bit, non-prefetchable) [size=64M] Memory at e0000000 (64-bit, prefetchable) [size=128M] Memory at ec000000 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at ed000000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [78] Express Endpoint IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting
Would you like me to add this to the RedHat bugzilla, the Xorg bugzilla, or both? Looks like most people have been adding to the RH one.
Jonathan